this post was submitted on 04 Jul 2023
216 points (98.6% liked)

Firefox

17302 readers
143 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
216
Firefox 115 released (www.mozilla.org)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
all 25 comments
sorted by: hot top controversial new old
[–] [email protected] 53 points 1 year ago (6 children)

Certain Firefox users may come across a message in the extensions panel indicating that their add-ons are not allowed on the site currently open. We have introduced a new back-end feature to only allow some extensions monitored by Mozilla to run on specific websites for various reasons, including security concerns.

What is this bullshit? Feel like this will lead to adblocks being blocked for certain websites under the guise of "security", aka: we don't have to justify shit to you.

[–] [email protected] 21 points 1 year ago (2 children)
[–] [email protected] 3 points 1 year ago (1 children)

1st thing to do on every release from now on.

This is a step too far for me. My device, my choice of browser and I am adult enough to make my own decisions.

[–] [email protected] 12 points 1 year ago (1 children)

Oh come on, it's still a free and open source browser. As seen in the other comments, it's a badly worded security feature for firefox internal pages and mozilla pages.

It's not going to kill adblock, it won't send your data everywhere and it can be disabled through an option as well as by simply building firefox yourself.

Everybody should stop being so negative towards open source developers.

[–] [email protected] 3 points 1 year ago

Did everyone in this thread drink the conspiracy theory kool-aid or something? The accusations here are wild.

[–] [email protected] 11 points 1 year ago (1 children)

“Security concerns” is such a bullshit reason. If an add on is such a security concern, why host it in the first place?

I’m disappointed Mozilla is going down this path, but not surprised.

[–] [email protected] 2 points 1 year ago

To me it sounds more like they plan on blocking all addons (other than some whitelist of "trusted" addons) on important pages (like the Google login page maybe?).

[–] [email protected] 11 points 1 year ago (1 children)

Is there even some way to see which addons this applies to on which websites? Or am I just going to find out randomly while browsing?

[–] gears 25 points 1 year ago* (last edited 1 year ago) (2 children)

I was curious as well so I looked at the git tree. I'm not familiar with Firefox code, but I'm assuming I found the list:

pref("extensions.webextensions.restrictedDomains", 
"accounts-static.cdn.mozilla.net,accounts.firefox.com,
addons.cdn.mozilla.net,addons.mozilla.org,
api.accounts.firefox.com,content.cdn.mozilla.net,
discovery.addons.mozilla.org,install.mozilla.org,
oauth.accounts.firefox.com,profile.accounts.firefox.com,
support.mozilla.org,sync.services.mozilla.com");

From here

So it looks like it's mostly to do with the account system of Firefox. I'm not sure why their websites would need special protection, but whatever. It's not malicious, for now

[–] [email protected] 22 points 1 year ago

Thanks! Nicer list:

  • accounts-static.cdn.mozilla.net
  • accounts.firefox.com
  • addons.cdn.mozilla.net
  • addons.mozilla.org
  • api.accounts.firefox.com
  • content.cdn.mozilla.net
  • discovery.addons.mozilla.org
  • install.mozilla.org
  • oauth.accounts.firefox.com
  • profile.accounts.firefox.com
  • support.mozilla.org
  • sync.services.mozilla.com
[–] [email protected] 20 points 1 year ago

Makes sense. You don't want Addons to navigate to the addons page and install other addons. You also don't want to give them access to the firefox sync data through your account to do the same from that end.

[–] [email protected] 4 points 1 year ago

I just hope that Librewolf will remove this.

[–] [email protected] 4 points 1 year ago

It's not going to inconvenience you that much, and the proof for that is that this has always been the case: extensions would never run on e.g. addons.mozilla.org. This makes sense; you don't want extensions to trick you into installing other extensions, for example, or to hijack your sync password.

It looks like the main change is that this actually loosens this restriction: it looks like some trusted extensions from now on will be allowed.

[–] [email protected] 3 points 1 year ago

at least it can be disabled in the prefs for now

[–] [email protected] 12 points 1 year ago

Of particular note: This is the last version that will support macOS 10.12 (Sierra), 10.13 (High Sierra), and 10.14 (Mojave). They'll get an extended support release of Firefox 115 that'll receive security updates for ~1 year. Source: mozilla.org

[–] [email protected] 9 points 1 year ago (1 children)

What happened to the cookie banner reduction? I can't find it in the release notes.

[–] [email protected] 0 points 1 year ago (1 children)

I think they hit some snags that it wasn't working satisfactorily yet, so hopefully in a future release 🤞

[–] [email protected] -1 points 1 year ago

Ah man, this was the main feature I was hyped for. Thanks for the info!

[–] [email protected] 2 points 1 year ago (1 children)

On Linux, middle clicks on the new tab button will now open the xclipboard contents in the new tab. If the xclipboard content is a URL then that URL is opened, any other text is opened with your default search provider.

Mega useful!

[–] [email protected] 0 points 1 year ago (1 children)

Why is this not on Windows. This sounds actually cool.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

Because Windows doesn't have two different copy/paste mechanisms like X does.

(X has "highlight text to copy"/"middle-click to paste" and "ctrl-c to copy"/"ctrl-v to paste", which have completely different origins (homegrown Unix vs. copying Windows) and don't even share the same clipboard. Frankly, although it can be useful it's also kind of a mess.)

[–] [email protected] -1 points 1 year ago

Agreed. It’s a huge mess.

[–] [email protected] 0 points 1 year ago

Most important for some of us

Hardware video decoding is now enabled for Intel GPUs on Linux.

Yey! Test it by starting intel_gpu_top and than playing video in firefox, if row "Video" goes over 0.0% it is working!

intel-gpu-top: Intel Coffeelake (Gen9) @ /dev/dri/card0 -  921/ 925 MHz;  38% RC6
    1.78/10.41 W;      813 irqs/s

      IMC reads:     3883 MiB/s
     IMC writes:     1632 MiB/s

         ENGINES     BUSY                                         MI_SEMA MI_WAIT
       Render/3D   12.82% |████▊                                |      0%      0%
         Blitter    0.00% |                                     |      0%      0%
           Video   27.99% |██████████▍                          |      0%      0%
    VideoEnhance    0.00% |                                     |      0%      0%

   PID              NAME   Render/3D      Blitter        Video      VideoEnhance  
   578       RDD Process |            ||            ||███         ||            |
 32431       firefox-bin |▊           ||            ||            ||            |
  2301    elogind-daemon |▌           ||            ||            ||            |
  4151        pcmanfm-qt |            ||            ||            ||            |
  4153         keepassxc |            ||            ||            ||            |
  4154         pasystray |            ||            ||            ||            |
  4521             slack |            ||            ||            ||            |
  6067            chrome |            ||            ||            ||            |
 29222       jcef_helper |            ||            ||            ||            |

Of course, you need second monitor, it goes down to 0 if video is not visible, since Firefox is not rendering it.