Closed Bug 902013 Opened 11 years ago Closed 11 years ago

CPOWs should be preffed off by default

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla26

People

(Reporter: benjamin, Assigned: evilpie)

References

Details

Attachments

(1 file, 1 obsolete file)

In bug 868859 CPOW support landed for Firefox desktop experiments in making addons compatible. But they should not be available to B2G at all, so they should be behind a pref which is off by default and only enabled on the e10s desktop branch currently.
Attached patch v1 (obsolete) — Splinter Review
Something like this?
I think CPOWs should be enabled if this pref is set OR if browser.tabs.remote is set. Also, we'll have to change the CPOW tests to set this special pref.
Well the way I did this is that the pref is always on when on Desktop. Because if we enable it automatically with browser.tabs.remote, we can't really test with remote tabs and CPOWs disabled. And because it would always be enabled on Desktop we don't have to bother with any special code.
Comment on attachment 788302 [details] [diff] [review]
v1

Review of attachment 788302 [details] [diff] [review]:
-----------------------------------------------------------------

Not sure if you can review this?
Attachment #788302 - Flags: review?(wmccloskey)
Comment on attachment 788302 [details] [diff] [review]
v1

Review of attachment 788302 [details] [diff] [review]:
-----------------------------------------------------------------

David should probably review this, since he wrote the original code here.

However, the reason the bug was filed was to ensure that CPOWs are disabled by default, even on desktop. I'd rather we do it the way I suggested in comment 2. Is there a reason we would want to test e10s with CPOWs disabled? If we just want to find places where CPOWs are used when we don't expect, I've found it useful to dump the stack whenever we send a CPOW message. That seems easier than disabling them and seeing what breaks.
Attachment #788302 - Flags: review?(wmccloskey) → review?(dvander)
Attachment #788302 - Flags: review?(dvander) → review+
Attached patch v2Splinter Review
So I guess this is more what Bill has in mind. We could even remove the force-disabled based on his feedback.
Attachment #788302 - Attachment is obsolete: true
Attachment #792873 - Flags: review?(dvander)
Comment on attachment 792873 [details] [diff] [review]
v2

Review of attachment 792873 [details] [diff] [review]:
-----------------------------------------------------------------

lgtm
Attachment #792873 - Flags: review?(dvander) → review+
https://hg.mozilla.org/mozilla-central/rev/bf471c1e49ba
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: