-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
web_easy_switch_company: menu items wrapping #116
Comments
Hi, thanks for reporting this bug. Can you indicate the version you use ? 7.0 / 8.0 ?
|
Hi, we are using the module on 8.0 and I did not notice anything wrong. Can you post a small screenshot or video illustrating the issue? |
Hi, I confirm that this happens sometimes when you update browser page, switching for example the company, but I don't have an exact trace. |
@antiflu : Could you realize a PR with your fix ? |
It feels like an ugly workaround but at least it works for my client. In my experience this only occurs in 8.0, in Chrome, and only when there are a lot of menu items obviously. Also, the problem disappears when you somehow resize the screen (eg by opening the Javascript console or moving the window). That's also the nature of this workaround it triggers a resize event after things are rendered |
Was this fixed in OCA? |
No news, so I close. |
Syncing from upstream OCA/web (10.0)
Remove unused PO file to reduce docker image size
I've noticed an issue that when the "easy switch company" menu item is inserted into the top bar, the other menu items don't "contract" to make space for this new item, and thus the new item wraps to the next line.
However, on screen resize the "menu_bound" event is executed and the size of the section with normal menu items is recalculated, some items are shifted to the "More" menu, and it all fits again.
I've found a workaround which is to add the following code to instance.web.UserMenu.init in switch_company.js,
It doesn't seem to be the cleanest solution, but at least it works. Anybody else has noticed the same?
The text was updated successfully, but these errors were encountered: