Closed Bug 914430 Opened 11 years ago Closed 11 years ago

There is not "dom.messageChannel.enabled" as visible preference.

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: tetsuharu, Unassigned)

References

Details

Why is there not "dom.messageChannel.enabled" as visible preference?
Depends on: 677638
Why should there be?
MessageChannel and MessagePort are disabled on purpose, for now, and if someone really wants to
enable them for testing creating a new pref is easy.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
(In reply to Olli Pettay [:smaug] from comment #1)
> Why should there be?
> MessageChannel and MessagePort are disabled on purpose, for now, and if
> someone really wants to
> enable them for testing creating a new pref is easy.

Other experiments features have their preferences (e.g. dom.promise.enabled). I seem that we should add the pref of MessageChannel and MessagePort.

If there are some reasons which are spec stabilities or other issues about whether we introduce experimental feature flags, I understand your decision.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.