web_responsive overhaul feeler

Open
  • Is something wrong?
#3,387 12 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ljmnoonan is already working on this.

Since Oct 12, 2026.

  • #3703 by @ljmnoonan — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, scss
Domain
frontend

Research direction

The issue discusses web_responsive, web_dark_mode (#3324), web_quick_start_screen, app menu structure, and sticky list and form headers, but names no files or tests. Read the discussion in #2684 and this issue’s comments to find whether maintainers agreed on a direction and which changes remain in scope. Done would require an agreed plan for the overhaul, target branch, and PR split; the payload does not specify an implementation task.

Written by the indexing model from the issue text.

Description

enhancement

While working on trying to make my web_dark_mode work with web_responsive I have realized that it may be time for a bit of an overhaul.

However, before spending any time doing so I'd like to get the consensus of the users and maintainers of this module to see what I should and shouldn't do. Here are the main points:

Lack of Direction

Two themes for the app screen as well as 3 different search modes. I have read all the discussion on #2684 where this was introduced and feel like there should have been an agreement reached before going forward rather than just keeping all options. The two themes, especially, make implementing dark mode confusing and inconvenient.

As far as search modes go, my personal preference would be odoo command palette, but keep the search bar. I could possibly modify the css to line it up with the search bar in order to seem more coherent. In any case, I would not get rid of the search bar as it is the only thing allowing searches from mobile.

Getting rid of these options would also eliminate the need for the little drop icon in the navbar. If we cannot agree on a single mode + theme, I would like to also suggest moving this to the user preferences section as I don't see any real reason for it to be in the navbar.

Outdated Code

In 18.0 list view headers are sticky by default and in 19.0 form status bars are sticky too. Maybe other features too?

File Structure

Not really a big thing, but the file structure does not follow web. primary_varables.scss for instance are tucked away in a legacy folder. Also, everything to do with the home menu would be under webclient and probably not split between apps_menu and apps_menu_item. If there are no objections, I would like to reorganize this.

Redirect to Home

I like this feature, but it seems a bit out of place. Could it be incorporated into web_quick_start_screen? I would also like to add a little home button to the navbar and could have sworn that I have actually seen that done already somewhere. Anyway, not really the subject of this issue.



Lastly, the big question: should I start these modifications on 19.0 of 18.0 and would you prefer it be broken up into multiple PRs, or just one?

Thank you all!

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.