I wish it would be based on the site's html lang attribute instead of an OS/browser locale. Also the user can't even just type something like "20190504" to get 2019-05-04, because for some reason it accepts six characters for the year part and it becomes 201905-04-
I'd also recommend turning off auto-updates for extensions (which is possible in Firefox). You also get a page with pending and recent updates, complete with release notes if the addon author provides them.
Even the triangular cursor path thing could probably be done with just CSS, a short-lived extra element in the childnav that starts transforming away on hover, making the next nav item accessible if the intent turns out not to be to move to the submenu.
Meanwhile the site has a fixed header taking away vertical space, like many others. Maybe interface design should accomodate the fact that every single desktop user uses a widescreen display and start putting navigation on the side.
Vertical tabs and taskbars can also be done in most browsers and OSes. There would probably be a lot of friction if vendors made that the default, but it's still easier than replacing every monitor in existence.
It's a great thing to do if you want to learn. Not so much if you want to release a game and make money.
Even if you want some very special engine-level feature, you can find an engine extendable enough and just add what you need.
Wow, I thought the controls are exposed in browser preferences. This makes even less sense, why would these be only controllable by extensions? (Though they are accessible in about:config at least)
I'm not sure how allowing extensions to change privacy settings is going to increase user privacy.
And while it's becoming easier to manipulate any website you visit, with basically nothing stopping a malicious extension from stealing user data or just taking over any online account, actually extending the browser UI, the original goal of many former extensions, is extremely limited.
This usually happens from node_modules, marked as a library folder, so it's indexed and might even be relevant, but it shouldn't really be a better match than the one in the source. And it's not even consistent.
Hope they'll get their shit together, it used to be a pretty great IDE before these annoyances started piling up.
It also has 6000+ unresolved issues reported, a lot of them open for 3-4 years with little hope of getting fixed. They keep rolling out half-baked support for the trendiest new JS frameworks, while basic parts of the IDE are falling apart every day. (For example, when opening the mentioned "Search Everywhere" dialog, sometimes it just doesn't receive focus. Good luck with that productivity.)
Meanwhile, after launch, the IDE grabs focus about six times while loading. Symbol navigation sometimes picks up random unrelated functions from ignored folders instead of the one sitting right beside the file, because it has the same name. Want autocomplete for that vertical-align's value? It just throws up every possible value for any CSS property.
Pretty bad when code editors running in a browser engine are getting more usable than your paid product.
Having a computer and radio in your brain doesn't mean you have to expose access to anything via the radio link. Even if you want to, there has to be software in between the connection to the meat and any APIs you provide for controlling your body, mapping intentions to raw signals for the neurons. This would have some form of access-control and safety features.