Zagrebian @ Zagrebian @fedia.io Posts 5Comments 14Joined 2 yr. ago
The solution is to set browser.urlbar.resultMenu.keyboardAccessible to false on the about:config page.
When a user comments that keyboard use in Firefox is not as efficient as they’d like in terms of the number of key presses, it’s not a good idea to suggest something that is even less efficient because it requires moving a hand.
How do I remove the (…) buttons on the right side of suggestions in the URL field drop-down?
For some reason, the default keyboard command Alt+P, which is Option+P on macOS, did not work for me, but I remembered that there’s a way on about:addons to “manage extension shortcuts”, so I changed it to Shift+Control+P, and now it works.
I filed a bug here: https://bugzilla.mozilla.org/showbug.cgi?id=1848049
The screenshot shows that the code word !important is broken in Firefox Nightly. This never happens in other browsers. Resize the browser window and check if that word breaks.
Can somebody reproduce? Go to https://github.com/w3c/csswg-drafts/issues/7535 and resize the browser window
Could Firefox not delay the update until the user actually restarts the browser?
I’m not “doing updates”. I’m just using Firefox normally.
I shared a screenshot, so I was not able to add text to the post. Maybe it’s possible, I don’t know. If there was a text box to add more text to the post, I would have explained the problem.
OP here. Most of the comments completely missed the point, but whatever.
No, it’ just a macOS application. Firefox updates itself automatically on macOS.
The problem is that the user should not be prevented from browsing the web just because a new update is ready. The user should choose when to update. If the user has multiple important tabs open, they should be able to finish their work, but if Firefox refuses to load any new tabs, then the user cannot continue working normally.
you're running multiple profiles of Firefox at the same time (so restarting one with a queued update writes the changes to disk, throwing the other profile instances out of alignment).
In that case, launching a different profile in a new window should not use the new version. In other words, Firefox should not do anything with the pending version until the user actually restarts the entire browser. Having the second window run in the new version just because there was a pending version seems like a bad approach.
Heh, if only browsers showed video controls for GIFs. That would be so useful. Maybe one day.