Closed Bug 946739 Opened 9 years ago Closed 8 years ago

https-everywhere and requestpolicy (0.5.28 and 1.0beta) breaks browser.tabs.remote

Categories

(Core :: DOM: Content Processes, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
e10s m4+ ---

People

(Reporter: shawnlandden, Assigned: cpeterson)

References

Details

(Keywords: addon-compat, Whiteboard: [testday-20131206])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20131205030207

Steps to reproduce:

turn on  browser.tabs.remote restart FF

debian sid with nightly on amd64



Actual results:

no content in tabs, or xml error


Expected results:

multi-process ff
Same build, confirmed.

Web pages don't show up, URL disappears.

about:home says there is  XML Parsing Error: undefined entity  in  <title>&abouthome.pageTitle;</title>

about:newtab and about:config work.
Blocks: e10s
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [testday-20131206]
Component: Untriaged → IPC
Product: Firefox → Core
Target Milestone: --- → mozilla28
Why is this nommed for tracking? It's not a config we're shipping at all.
Flags: needinfo?(twalker)
ok, clearing.
Flags: needinfo?(twalker)
Is this Australis specific?
WFM now with the same build:
2013-12-05-03-02-07-mozilla-central-firefox-28.0a1.en-US.linux-x86_64
2013-12-05-03-02-07-mozilla-central-firefox-28.0a1.ru.linux-x86_64

But broke with the profile I used then.
Worked in safe mode.
Broke with all extensions disabled and RequestPolicy 1.0b enabled.
Worked with RequestPolicy 1.0b also disabled.
Broke with all non-RequestPolicy extensions enabled. ???

Broke when I installed RequestPolicy 1.0x on a new profile and then enabled .remote (couldn't install with .remote enabled).
Still broken with the same profile in 2013-12-08-03-02-04-mozilla-central-firefox-28.0a1.en-US.linux-x86_64.
I can confirm that last comment. If I start nightly in a new profile then browser.tabs.remote works, even with Australis. (commenting from it right now) 

Adblock-plus and https-everywhere also work with browser.tabs.remote.
Scratch part of that last comment. The offending add-on is https-everywhere; while adblock-plus, cslite, refcontrol, greasemonkey, and stylish work with browser.tabs.remote. Now I can use my original profile.
Summary: browser.tabs.remote broken → https-everywhere breaks browser.tabs.remote
Confirmed: HTTPS Everywhere and RequestPolicy 0.5.28 each do it, too.
Summary: https-everywhere breaks browser.tabs.remote → Each of https-everywhere and requestpolicy (0.5.28 and 1.0beta) breaks browser.tabs.remote
Summary: Each of https-everywhere and requestpolicy (0.5.28 and 1.0beta) breaks browser.tabs.remote → https-everywhere and requestpolicy (0.5.28 and 1.0beta) breaks browser.tabs.remote
While "both" could be used here to make a complete sentence, and you correctly used "breaks" with each, each is superfluous and awkward without a generic pronoun, like "Each add-on that W, such as X and Y, breaks X."
Blocks: e10s-addons
No longer blocks: e10s
Mass tracking-e10s flag change. Filter bugmail on "2be0fcce-e36a-4e2c-aa80-0e3d33eb5406".
tracking-e10s: --- → +
Blocks: 1014986
No longer blocks: e10s-addons
Component: IPC → DOM: Content Processes
Target Milestone: mozilla28 → ---
See Also: → 1055709
See Also: → 1055711
Duplicate of this bug: 1055711
Duplicate of this bug: 1055709
Duplicate of this bug: 1066249
Duplicate of this bug: 1066249
This bug is receiving a lot of dupes. We might want to address this bug sooner than planned.

btw, HTTPS Everywhere devs have already fixed most of their e10s bugs upstream.
Keywords: addon-compat
Version: 28 Branch → Trunk
Assignee: nobody → cpeterson
I can't reproduce the blank pages described in comment 0, so I'm closing this bug WFM.

I can still reproduce "HTTPS Everywhere breaks HTTP redirects" bug 997808 and a RequestPolicy UI bug, but those are unrelated to this bug report.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.