Last Comment Bug 674696 - Please remove proprietary extensions to Event or standardize them
: Please remove proprietary extensions to Event or standardize them
Status: NEW
:
Product: Core
Classification: Components
Component: DOM: Events (show other bugs)
: Trunk
: All All
: -- normal with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-27 14:15 PDT by Anne (:annevk)
Modified: 2011-10-18 22:02 PDT (History)
7 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Anne (:annevk) 2011-07-27 14:15:25 PDT
Specifically, everything in http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/events/nsIDOMNSEvent.idl except isTrusted really ought not to exist at all.
Comment 1 Anne (:annevk) 2011-07-27 14:22:56 PDT
See also: http://lists.w3.org/Archives/Public/www-dom/2011JulSep/0039.html
Comment 2 Anne (:annevk) 2011-07-27 14:29:03 PDT
https://bugs.webkit.org/show_bug.cgi?id=65283 is the WebKit bug.
Comment 3 Alex Vincent [:WeirdAl] 2011-07-27 15:04:31 PDT
originalTarget and explicitOriginalTarget are necessary for XBL 1 - they expose shadow content event targets.
Comment 4 Boris Zbarsky [:bz] 2011-07-27 18:15:42 PDT
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 :Ms2ger 2011-07-28 02:15:38 PDT
(In reply to comment #4)
> We can maybe remove getPreventDefault once we implement defaultPrevented,

We already do, bug 656954.

Note You need to log in before you can comment on or make changes to this bug.