* [FIX][web_m2x_options] Fix Qweb templates.
They were trying to replace non-existing elements, and this was being logged to console:
Can't find "a.oe_m2o_cm_button" when extending template FieldMany2One
Can't find "span.badge" when extending template FieldMany2ManyTag
* Raise version correctly.
* [FIX] Make many2many_tags tag deletion work again
* Correct replacement of event
Instead of overwriting all events from upstream widget, better just overwrite the one you need and inherit the rest.
- Add static/description/index.html
fix: use include instead of extend in js function inheritance.
fix: not overwriting the existing object references with the result of the include
fix: update name according to new module name.
fix: error when displaying many2many field without options defined.
* Bump version
* Change all openerp to odoo
* Fix qunit suite injection
* Remove jQuery require
* Change to new selectors:
* `oe_leftbar` to `o_sub_menu`
* `oe_logo` to `o_sub_menu_logo`
* `oe_footer` to `o_sub_menu_footer`
* `oe_secondary_menus_container` to `o_sub_menu_content`
* Add style to hide oe_footer instead of remove to not break `support_branding`
* Add note in ReadMe explaining override of `support_branding`
* Set top margin of app drawer title to 0 to fit v10 proportions
* Fix notification badge positioning
* Add o_web_client class to body to fix overlaps
* Scroll control panel with page
* Change navbar z-index to not be overlapped by buttons
* Raise z-index on header to raise over buttons
* Handle layered notifications via z-index
* Remove `#` from navigation links HREF to prevent history littering
The 'colors' and 'options' fields are not supported by the RelaxNG
schema of the <tree> element. Remove the support until we find a
good solution for this.
The index at 0 in the following code:
var colorField = this.arch.attrs.colors.split(';')
.filter(color => color.trim().startsWith('color_field'))[0]
Was failing on such valid xml:
<tree string="Buffer monitor"
colors="red:procure_recommended_qty > 0">
It is important to let users decide their default dialog size. Some have ultrawide monitors and this module does more harm than benefit.
Here I add such task to roadmap, to avoid forgetting about it.
@Tecnativa
