If you go to browserleaks.com/firefox/, you'll see that resource:// is leaked for the locale and greprefs.js. Waterfox Classic does not leak this info.
Is the following backported?
https://bugzilla.mozilla.org/show_bug.cgi?id=863246
Resource Leak in v2.53.1
-
- Posts: 1361
- Joined: December 15th, 2015, 1:20 pm
Re: Resource Leak in v2.53.1
No it is not in. Stumbled over it previously but this probably breaks add-ons so it will not go into 2.53.x
-
- Posts: 76
- Joined: March 10th, 2017, 3:48 pm
Re: Resource Leak in v2.53.1
If you're interested in how Waterfox patched that up, here's their Github issue:
https://github.com/MrAlex94/Waterfox/is ... -387634960
https://github.com/MrAlex94/Waterfox/is ... -387634960
-
- Posts: 1361
- Joined: December 15th, 2015, 1:20 pm
Re: Resource Leak in v2.53.1
They "fixed" it by backporting the Bug.
They also backported this which breaks a ton of classic add-ons:
https://bugzilla.mozilla.org/show_bug.cgi?id=1326520
For some reason they are pretty unconcered about this. We are not.
Mostly I am with Tobin and Moonchild with this one. And this does not happen frequently
https://forum.palemoon.org/viewtopic.ph ... js#p182212
We could rename the prefs file but it would be pointless. Tracker code could just adjust for the new name.
FRG
They also backported this which breaks a ton of classic add-ons:
https://bugzilla.mozilla.org/show_bug.cgi?id=1326520
For some reason they are pretty unconcered about this. We are not.
Mostly I am with Tobin and Moonchild with this one. And this does not happen frequently
https://forum.palemoon.org/viewtopic.ph ... js#p182212
We could rename the prefs file but it would be pointless. Tracker code could just adjust for the new name.
FRG
Last edited by frg on April 14th, 2020, 1:34 am, edited 1 time in total.
-
- Posts: 76
- Joined: March 10th, 2017, 3:48 pm
Re: Resource Leak in v2.53.1
Gotcha. Thanks for the rationale behind your reasoning, frg.
I found a workaround using a modified version of No Resource URI Leak over at the ghacks.js Github repo: https://github.com/ghacksuserjs/ghacks- ... issues/191
This works on SeaMonkey 2.53.1.
I found a workaround using a modified version of No Resource URI Leak over at the ghacks.js Github repo: https://github.com/ghacksuserjs/ghacks- ... issues/191
This works on SeaMonkey 2.53.1.