Closed
Bug 1460732
Opened 7 years ago
Closed 1 year ago
Turn off remote XUL outside the IsInAutomation() and the "dom.allow_XUL_XBL_for_file" case
Categories
(Core :: XUL, enhancement, P5)
Core
XUL
Tracking
()
RESOLVED
FIXED
People
(Reporter: bgrins, Unassigned)
References
(Blocks 2 open bugs)
Details
This is spun out of the 'The future of "remote XUL"' thread: https://groups.google.com/d/msg/firefox-dev/GEDBHOUaVlM/VbeiBlWcCQAJ.
I believe there was a consensus in that thread that the remote XUL feature is going to continually break in various ways as we do cleanups post-57. Rather than letting that happen, we could explicitly remove support which would simplify the platform and make doing those types of cleanups easier.
I'm not sure if this can ultimately happen in a single bug or if we'll have to break it down further, so just going to get this one on file for now.
|
||
Updated•7 years ago
|
Priority: -- → P5
|
||
Updated•2 years ago
|
Severity: normal → S3
|
||
Comment 1•1 year ago
|
||
dom.allow_XUL_XBL_for_file was removed in bug 1843742.
Should this bug be closed or repurposed?
Flags: needinfo?(smaug)
Flags: needinfo?(bgrinstead)
|
Reporter | |
Comment 3•1 year ago
|
||
(In reply to Gregory Pappas [:gregp] from comment #1)
dom.allow_XUL_XBL_for_file was removed in bug 1843742.
Should this bug be closed or repurposed?
Chatted with smaug about this, I think this bug can be closed since https://searchfox.org/mozilla-central/rev/a7e33b7f61e7729e2b1051d2a7a27799f11a5de6/dom/base/nsContentUtils.cpp#6962-6972 requires automation. Thanks for taking Bug 1843742 and for the nudge here.
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(bgrinstead)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•