The latest news and developments on Firefox and Mozilla, a global non-profit that strives to promote openness, innovation and opportunity on the web.
You can subscribe to this community from any Kbin or Lemmy instance:
Related
While we are not an official Mozilla community, we have adopted the Mozilla Community Participation Guidelines as far as it can be applied to a bin.
Always be civil and respectful
Don't be toxic, hostile, or a troll, especially towards Mozilla employees. This includes gratuitous use of profanity.
Don't be a bigot
No form of bigotry will be tolerated.
Don't post security compromising suggestions
If you do, include an obvious and clear warning.
Don't post conspiracy theories
Especially ones about nefarious intentions or funding. If you're concerned: Ask. Please don’t fuel conspiracy thinking here. Don’t try to spread FUD, especially against reliable privacy-enhancing software. Extraordinary claims require extraordinary evidence. Show credible sources.
Don't accuse others of shilling
Send honest concerns to the moderators and/or admins, and we will investigate.
Do not remove your help posts after they receive replies
Half the point of asking questions in a public sub is so that everyone can benefit from the answers—which is impossible if you go deleting everything behind yourself once you've gotten yours.
It's still innovative, and the only browser with total cookie protection and a large amount of other anti-tracking measures.
In the nightly, they are working on allowing the user to get rid of all the "click accept for cookies" once and for all.
It has much better plugins, much better ad blocking etc.
What does chrome have?
Yeah the article is specific to a recent change. FF browser is still awesome
Update to the bug I filed that was introduced in Firefox 116 - apparently, it isn't a bug:
I don't think this is a bug, its a side effect of the behavior for the ctrl|cmd + shift + T shortcut changing in 116 to reopen the last closed tab or window, in the order closed.
Technically, you closed a window when you dragged the tab out to a window, and then back to the original window. The exact same behavior happens if you use repeat those steps and use the ctrl|cmd + shift + N shortcut to reopen the last closed window.
There's an open needinfo for the author of the regressor, so I don't have much of a comment, but... it is very clearly a bug and very clearly a regression - Chrome doesn't do this (and actually has the newly claimed Firefox behavior) -- and neither did Firefox before it regressed.
It still introduces features Chrome doesn't