Skip to content

[19.0][FIX] web_responsive: keep the apps menu above the view when installed as an app - #3814

Merged
OCA-git-bot merged 1 commit into
OCA:19.0from
chrisandrewmann:19.0-fix-web_responsive-apps-menu-standalone
Nov 19, 2026
Merged

OCA-git-bot merged 1 commit into
OCA:19.0from
chrisandrewmann:19.0-fix-web_responsive-apps-menu-standalone

Conversation

@chrisandrewmann

Copy link
Copy Markdown

Foward port of #3805

Since odoo/odoo@1a0f283c8e, the navbar is position: sticky when Odoo runs as an installed app (https://github.com/media (display-mode: standalone)). A sticky element creates a stacking context, and the apps menu of this module is rendered inside the navbar, so its z-index: 1000 only applies within it.

As a result, when Odoo is installed as an app, the positioned elements of the current view (form sheet, control panel, dashboard items) are painted over the full screen apps menu, and the apps can only be reached by searching them. It does not happen in a regular browser tab.

This raises the navbar while the apps menu is open (.o_apps_menu_opened), so its stacking context sits above the view. Once the menu is closed the navbar keeps z-index: auto.

To reproduce: install Odoo as an app from the browser, open any form view and open the apps menu.

Steps to reproduce:

  1. Install Odoo as an app (Chrome/Edge "Install app", or Android "Add to home screen").
  2. Open a form view and open the apps menu.
  3. Before: view content is drawn over the menu. After: the menu sits fully above the view.

…d as an app

Since odoo/odoo@1a0f283c8e, the navbar is sticky when Odoo runs as an installed app (display-mode: standalone). A sticky element is a stacking context, and the apps menu is rendered inside the navbar, so its z-index only applies within it: the positioned elements of the current view (form sheet, control panel, dashboard items) were painted over the apps menu, and the apps could only be reached by searching them.

Raising the navbar while the apps menu is open puts that stacking context above the view.
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hi @Tardo, @SplashS,
some modules you are maintaining are being modified, check this out!

@pedrobaeza pedrobaeza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems this has reached 19.0 now, so let's fast-track it to fix it.

/ocabot merge patch

Should we put it already in 20 as well?

@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 19.0-ocabot-merge-pr-3814-by-pedrobaeza-bump-patch, awaiting test results.

@OCA-git-bot
OCA-git-bot merged commit 44c720f into OCA:19.0 Nov 19, 2026
8 checks passed
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at b25d75b. Thanks a lot for contributing to OCA. ❤️

@chrisandrewmann

Copy link
Copy Markdown
Author

It seems this has reached 19.0 now, so let's fast-track it to fix it.

/ocabot merge patch

Should we put it already in 20 as well?

Thanks @pedrobaeza
Agree it probably needs to port to 20.0 too, but I don't have time at the moment to test if it's affected or port it.
I use 19.0 daily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants