Repository navigation
Conversation
The 19.0 migration kept the 16.0 stylesheet, which Odoo 19 no longer matches: - Navbar, buttons, links, statusbar, selected list rows, smart buttons and inputs now set the CSS variables Odoo 19 reads (--NavBar-*, --btn-*, --link-color, --o-stat-*, --o-input-border-color, ...) instead of overriding rules Odoo 19 no longer uses. - The generated stylesheet is plain CSS (no nesting), so it is valid without Sass compilation. - Only the colour groups a company sets are styled; empty hover and text colours are derived from the chosen colour instead of purple. - Cover the other widgets Odoo compiles with its brand colour (focus rings, switches, open search toggles, date picker, pagination, progress bars, kanban/settings highlights, properties fields, ...). - Company stylesheet links are built per request; mutating the cached asset links leaked one company's colours into other companies. - Phone browser toolbar (theme-color) follows the navbar colour. - Logo colour detection no longer crashes on fully white, black or transparent logos. - Expose the submenu colour field in the company form. The migration regenerates existing stylesheets; saved colours are kept. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Publish the active company's button colours as --web-company-color-primary and --web-company-color-primary-hover so other modules can follow the company theme from their own stylesheets, with their usual colour as fallback. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Member
|
Check https://github.com/pypa/pip/blob/main/AI_POLICY.md to perform the needed changes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by yasir
The 19.0 migration of
web_company_colorkept the 16.0 stylesheet. In Odoo 19 most of those selectors no longer match, so the colours a company sets only partly apply. The rest of the UI keeps Odoo's purple: smart buttons, the statusbar, selected list rows, focus rings, switches, the open Filters toggle, the date picker and others.What this changes
--NavBar-*,--btn-*,--link-color,--o-stat-*,--o-input-border-color, …). They no longer override rules that Odoo 19 doesn't use.web/Bootstrap widgets that Odoo compiles with its brand colour are now covered. These include focus rings, switches, open search toggles, the date picker, pagination, progress bars, kanban and settings highlights, and properties fields.theme-colormeta tag follows the navbar colour.[IMP]): the company palette is published as--web-company-color-primaryand--web-company-color-primary-hover, so other modules can follow the company theme.A
19.0.1.1.0migration regenerates existing company stylesheets. Saved colours are kept.How to test
Screenshots
Before/after screenshots will follow in a comment.
🤖 Generated with Claude Code