web_theme_classic: as user setting, instead of global on/off?

Open
#3,234 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by reading the web_theme_classic addon and the user preference implementation for web_chatter_position, which the issue names as a model. Work out how the theme is currently enabled and where user preferences are applied; done means each user can choose the classic theme independently while the existing theme behavior remains clear.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem?
Some people prefer the new Odoo style, others the old, especially those with restrictions in their eyesight.

Describe the solution you'd like
How about making the "classic theme" a setting on the user preference page, just like web_chatter_position

Describe alternatives you've considered
Using an accessiblity module like https://apps.odoo.com/apps/modules/18.0/odoo-allinoneaccessibility,
but no OCA solution exists currently on this?

Additional context
/

Dominant language
JavaScript
Stars
1.2k
Forks
2.2k
Avg merge
3d 15h
Merged PRs (30d)
30

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OCA/web

All issues in OCA/web

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.