Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Please remove proprietary extensions to Event or standardize them

NEW
Unassigned

Status

()

Core
DOM: Events
6 years ago
6 years ago

People

(Reporter: annevk, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Specifically, everything in http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/events/nsIDOMNSEvent.idl except isTrusted really ought not to exist at all.

Updated

6 years ago
Component: DOM: Core & HTML → DOM: Events
QA Contact: general → events
(Reporter)

Comment 1

6 years ago
See also: http://lists.w3.org/Archives/Public/www-dom/2011JulSep/0039.html
(Reporter)

Comment 2

6 years ago
https://bugs.webkit.org/show_bug.cgi?id=65283 is the WebKit bug.
originalTarget and explicitOriginalTarget are necessary for XBL 1 - they expose shadow content event targets.

Comment 4

6 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.
(In reply to comment #4)
> We can maybe remove getPreventDefault once we implement defaultPrevented,

We already do, bug 656954.
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.