API: TOOLBAR_ALWAYS_VISIBLE is ignored on desktop browser
See original GitHub issueDescription
The option TOOLBAR_ALWAYS_VISIBLE: true
in interfaceConfigOverwrite
seems to be ignored on desktop browser.
Current behavior
Toolbar is dismissed after the number of milliseconds specified with TOOLBAR_TIMEOUT, even when TOOLBAR_ALWAYS_VISIBLE is true.
Expected Behavior
Toolbar should never be dismissed when TOOLBAR_ALWAYS_VISIBLE is true.
Environment details
Tested with Firefox 74 and Chome 80 on Fedora.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:7
Top Results From Across the Web
Do browsers ignore window parameters when opening new ...
With window restrictions in place, the status bar cannot be turned off for any window created by the window.open method; it is always...
Read more >Firefox 76.0 javascript window.open() parameters ignored ...
The old trick to show the full toolbar and tabs bar (dom.disable_window_open_feature.toolbar => true) no longer has any effect in Firefox 76 ...
Read more >Issues: Find and fix problems - Chrome Developers
Use it to find solutions to problems detected by the browser, such as cookie issues and mixed content.
Read more >Microsoft Edge Browser Policy Documentation
BlockNotifications (2) = Don't allow any site to show desktop ... This policy setting is ignored (and Basic is always forbidden) if the ......
Read more >The trick to viewport units on mobile | CSS-Tricks
Viewport units have always been controversial and some of that is ... you get past a piece of the browser interface, like the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue is still present, should be reopen.
Can confirm on 83.0.4103.97. It’s a mayor problem for us since “moving the mouse in the iFrame to see the controls” is not instinctive understandable for some user