1265803 - [e10s] security indicator and window caption not updated when switching tabs, with noscript

Status: RESOLVED DUPLICATE of bug 1246349

(Firefox :: Extension Compatibility, defect)

Description

[Kurt Roeckx]

When multi-process is enabled, various things don't update properly anymore when switching tabs:
- In the URL bar in case of https there is an indication of the organization you're connected to, now it says "Mozilla Foundation (US)", and it's indicated in green.  But when I switch to a different site not related to mozilla, it keeps saying that.
- The caption of the window doesn't show.  It currently says "Enter Bug: Firefox - Mozilla Firefox", but when switching to a different tab it keeps saying that.

All this is works properly when I disable multi-process.

Comment 1

[:Gijs (he/him)]

Does this reproduce on a clean profile?

Because I've never seen this in my testing, which makes me suspect something funky is going on in your profile, either in terms of settings or in terms of add-ons or something.

Comment 2

[Kurt Roeckx]

I seems I can only reproduce this with noscript enabled.   Disabling it I couldn't reproduce it.

I would also like to add that you might need to open or close a few tabs before it starts happening.  I doesn't happen all the time, something seems to trigger it but I have no idea what.

Comment 3

[:Gijs (he/him)]

(In reply to Kurt Roeckx from comment #2)
> I seems I can only reproduce this with noscript enabled.   Disabling it I
> couldn't reproduce it.
> 
> I would also like to add that you might need to open or close a few tabs
> before it starts happening.  I doesn't happen all the time, something seems
> to trigger it but I have no idea what.

Giorgio, can you help?

Comment 4

[Giorgio Maone [:ma1]]

I'm working on it, but I've been slowed down by the effort to stuff as many NoScript-related features/fixes as possible into the WebExtensions API before the 48 release window closes.
I should be able to release a work-around for this one by the end of next week.

Comment 5

[:Gijs (he/him)]

(In reply to Giorgio Maone [:mao] from comment #4)
> I'm working on it, but I've been slowed down by the effort to stuff as many
> NoScript-related features/fixes as possible into the WebExtensions API
> before the 48 release window closes.
> I should be able to release a work-around for this one by the end of next
> week.

Does workaround mean there's a Firefox bug here? :-)

Comment 6

[Giorgio Maone [:ma1]]

(In reply to :Gijs Kruitbosch from comment #5)

> Does workaround mean there's a Firefox bug here? :-)

Not exactly, it's more like Firefox's e10s shims for add-ons not working as expected in a corner case and a proper fix in NoScript (replacing *all* the shims reliance with ad-hoc code) being anti-economic, considering the WebExtensions porting effort. So my current strategy is creating ad-hoc e10s work-around bits as they're needed, while focusing on WebExtensions for the long run.

Comment 7

[:Cykesiopka]

Looks like Bug 1246349 is already filed for this.