31 ms·

> I'm curious how this behaves in relation to blocking third-party cookies via Settings→Privacy→Accept third-party cookies It doesn't. The option you mention i

> I'm curious how this behaves in relation to blocking third-party cookies via Settings→Privacy→Accept third-party cookies It doesn't. The option you mention is about cookies acceptance on a first-party vs. third-party policy; trackingprotection is about blocking regular http requests on a blacklist basis. > Also, I wonder what this would catch that uBlock Origin wouldn't? I assume that if it's "good enough" then it's probably the better solution to use in Firefox, especially with the new extension format and multi-process (e10s) coming eventually in Firefox. I perceive it as exactly this too, a "simple and good enough" solution. Get uBlock Origin (or any other blocker) if you want the bells and whistles and more {white/black}list control. Nit: e10s has no problems with uBlock Origin at all, it's still working within my e10s-enabled Developer Edition 44.0a2.

aorth 11y ago
Ah, you're right about the cookies thing. Regarding uBlock Origin and e10s, you've never gotten the dialog "uBlock Origin is making Firefox run slowly" or similar? I believe that's related to e10s...
- ronjouch 11y ago
  In a sense, this feature/dialog is "close" to e10s as it's under the same umbrella at Mozilla, the "Snappy" [1] effort to work on performance. But it's not the same: - e10s is about making each browser tab an independent process [2]. Some addons have glitches with it, but uBlock Origin is not one of them. - The feature you saw just proactively tells users about addons degrading performance and help them disable them or adjust their expectations. See [3]. EDIT hmmm, you are right, actually! The bug explicitly mentions the goal to "identify add-ons that are causing jank because of their CPOW usage", and CPOW is an e10s thing [4]. TIL, thanks :) [1] https://wiki.mozilla.org/Performance/Snappy https://wiki.mozilla.org/Performance/Snappy [2] https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1071880 https://bugzilla.mozilla.org/show_bug.cgi?id=1071880 [4] https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Cross_Process_Object_Wrappers https://developer.mozilla.org/en-US/Firefox/Multiprocess_Fir...

aorth 11y ago

Ah, you're right about the cookies thing. Regarding uBlock Origin and e10s, you've never gotten the dialog "uBlock Origin is making Firefox run slowly" or similar? I believe that's related to e10s...

ronjouch 11y ago
In a sense, this feature/dialog is "close" to e10s as it's under the same umbrella at Mozilla, the "Snappy" [1] effort to work on performance. But it's not the same: - e10s is about making each browser tab an independent process [2]. Some addons have glitches with it, but uBlock Origin is not one of them. - The feature you saw just proactively tells users about addons degrading performance and help them disable them or adjust their expectations. See [3]. EDIT hmmm, you are right, actually! The bug explicitly mentions the goal to "identify add-ons that are causing jank because of their CPOW usage", and CPOW is an e10s thing [4]. TIL, thanks :) [1] https://wiki.mozilla.org/Performance/Snappy https://wiki.mozilla.org/Performance/Snappy [2] https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1071880 https://bugzilla.mozilla.org/show_bug.cgi?id=1071880 [4] https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Cross_Process_Object_Wrappers https://developer.mozilla.org/en-US/Firefox/Multiprocess_Fir...