Closed
Bug 962747
Opened 11 years ago
Closed 10 years ago
Hide Window.openDialog from content
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 789261
People
(Reporter: sicking, Unassigned)
References
()
Details
(Keywords: dev-doc-needed, site-compat)
I think Window.openDialog is a gecko-specific thing. If so we should attempt to hide it from web content. I don't think it was ever intended to be used by the web but I can't see anything obvious that prevents it from being callable from the web. And the fact that window.openDialog tests true might affect future web standards as well as pollutes the global scope of the page.
Reporter | ||
Comment 1•11 years ago
|
||
Hmmm.. Window.webidl says that openDialog is [ChromeOnly]. However |typeof window.openDialog| returns "function" even in content pages?
Comment 2•11 years ago
|
||
Yeah, that's the XPIDL one you're seeing.
Comment 3•11 years ago
|
||
Ms2ger is right. Once we finish moving Window to webidl, this will be fixed.
If we really wanted to we could try to do something with removing this from the xpidl, but then we have to make xrays work somehow....
Blocks: 789261
Updated•11 years ago
|
Updated•11 years ago
|
Comment 4•10 years ago
|
||
Fixed by moving Window to WebIDL.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•