[RESOLVED] 2.5.8rc2 regr: allowed site opens as not allowed

[al_9x]

Fx 16.0.1, NS >= 2.5.8rc2, new profile

1. Mark the following sites as indicated
   1. mediaplex.com - untrusted
   2. dell.com - allowed
   3. dealspl.us - allowed
2. open http://dealspl.us/dell-coupons/530548
3. click on the coupon code (flash is involved)
4. this opens a popup windows and navigates the tab to dell.com which is not allowed

To narrow this down to a reproducible state I had to bisect my large untrusted list (to find mediaplex.com) which was a pain without an untrusted list editor (domains are repeated thrice in the untrusted config). For this and other reasons, an untrusted editor would be very helpful.

[therube]

Confirmed.

So how is it that mediaplex.com plays into this, or is that the crux of the issue?
And seems that dealspl.us is necessarily needed to be allowed?

This must be the same issue, 2.5.8 failing.

[Tom T.]

... For this and other reasons, an untrusted editor would be very helpful.

Agreed, and IIRC it's been requested before. However, as an advanced user, you could use NS Export button (the main one at the bottom, not under "Whitelist" tab), edit the text file of "untrusted" entries as desired, then Import back in. Much faster than that tiny window in about:config.

[Giorgio Maone]

This must be the same issue, 2.5.8 failing.

No, they're two distinct issues, the heaviest affecting older Firefox versions (3.x), but maybe originating from the same change working around regressions caused by Firefox 18 and above.
The rapid release cycle is starting to hurt
Hope to have a fix today or tomorrow at most.

[FRANK712]

The rapid release cycle is starting to hurt

Indeed !

[Giorgio Maone]

Should be fixed in latest development build 2.5.9rc2, please confirm, thanks.

[Tom T.]

The rapid release cycle is starting to hurt

Is this the time for me to say "I told you so" (to MZ, not to Giorgio), having whined repeatedly about the whole philosophy of "rapid release" ever since MZ started down that path?

[Thrawn]

The rapid release cycle is starting to hurt

Is this the time for me to say "I told you so" (to MZ, not to Giorgio), having whined repeatedly about the whole philosophy of "rapid release" ever since MZ started down that path?

AFAICT, not really, because all recent evidence (Android-native interface, thawing XPCOM interfaces, etc) indicates that they don't really care about breaking addons...

But when that attitude causes Fx to be abandoned in favor of Chrome/Chromium, then you can say you told them so!

Btw, have you tried the Pale Moon fork?

[al_9x]

Should be fixed in latest development build 2.5.9rc2, please confirm, thanks.

fixed

[Tom T.]

The rapid release cycle is starting to hurt

Is this the time for me to say "I told you so" (to MZ, not to Giorgio), having whined repeatedly about the whole philosophy of "rapid release" ever since MZ started down that path?

AFAICT, not really, because all recent evidence (Android-native interface, thawing XPCOM interfaces, etc) indicates that they don't really care about breaking addons...

But when that attitude causes Fx to be abandoned in favor of Chrome/Chromium, then you can say you told them so!

A few years ago, Fx was gobbling up IE market share, with the peak for Fx apparently being around 2009 -- which would still be F3 and "slow release", or "release when actually needed", in decimal bumps, not integer bumps with the major internal structural changes that are plaguing Giorgio and other add-on devs.

Now, the statistics gathered on browser usage have shown that for several years, Chrome has been gaining market share, at the expense of both IE and -- Firefox.

So I think that it's time.

re: Pale Moon: I, and probably many others, might be interested in hearing the pros and cons of it, keeping in mind that Giorgio guarantees NS support only for Fx and SM. Do you wish to start a topic in Extras > Web Tech regarding Pale Moon? ... and especially, are they equal in security vigilance, finding and patching flaws?


@ al_9x: Marked as Resolved, thanks.