Open
Bug 674696
Opened 14 years ago
Updated 2 years ago
Please remove proprietary extensions to Event or standardize them
Categories
(Core :: DOM: Events, task, P3)
Core
DOM: Events
Tracking
()
NEW
People
(Reporter: annevk, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: site-compat)
Everything at https://searchfox.org/mozilla-central/source/dom/webidl/Event.webidl#64-88 really ought not to exist at all.
Updated•14 years ago
|
Component: DOM: Core & HTML → DOM: Events
QA Contact: general → events
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
https://bugs.webkit.org/show_bug.cgi?id=65283 is the WebKit bug.
Comment 3•14 years ago
|
||
originalTarget and explicitOriginalTarget are necessary for XBL 1 - they expose shadow content event targets.
Comment 4•14 years ago
|
||
We can maybe remove getPreventDefault once we implement defaultPrevented, unless sites are sniffing and relying on it, in which case it probably needs to be standardized as an alize for defaultPrevented.
The prevent* stuff has been deprecated for a while and I suspect can go.
The original target stuff is indeed needed for XBL1, but I wonder whether we can expose it to system-principal code only like we do baseURIObject and nodePrincipal. That ought to be good enough for our uses.
The various constants might need standandizing. Not sure.
Comment 5•14 years ago
|
||
(In reply to comment #4)
> We can maybe remove getPreventDefault once we implement defaultPrevented,
We already do, bug 656954.
Updated•14 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → Trunk
Reporter | ||
Comment 6•7 years ago
|
||
There's still a few members left: https://searchfox.org/mozilla-central/source/dom/webidl/Event.webidl#63.
Comment 7•7 years ago
|
||
The four *_MASK constants we should try to figure out whether anyone uses in the wild; I'm not quite sure how to do that. We can scrub them from our code pretty straightforwardly. It's not clear to me what exactly in-the-wild uses would look like, since you can't do anything with these constants directly.
That leaves originalTarget and explicitOriginalTarget. We could pretty easily restrict these to chrome-or-xbl, I expect. The question is whether anyone uses them on the web. I guess we could try adding telemetry for non-chrome-or-xbl uses...
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Updated•5 years ago
|
Blocks: proprietary-dom
Updated•5 years ago
|
Keywords: site-compat
Updated•5 years ago
|
Type: defect → task
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•