Zagrebian

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.

I filed a bug here: https://bugzilla.mozilla.org/show_bug.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.

OP here. Most of the comments completely missed the point, but whatever.

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.

Heh, if only browsers showed video controls for GIFs. That would be so useful. Maybe one day.

An upcoming Firefox feature that automatically rejects or accepts cookie banners for the user.

When scrolling the page to hide Firefox’s address bar, the svh bar should remain small (smaller than the height of the page). When scrolling back up to show the address bar again, the vh and lvh bars should remain large and become cut off on the bottom.