10899 2010-09-30 20:34:52 +0000 DOMActivate is deprecated in DOM L3 Events 2010-10-18 17:01:41 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All CLOSED FIXED http://dev.w3.org/html5/spec/content-models.html#interactive-content-0 P3 normal --- 1 adrianba ian bugs dbolter ian jonas mike mjs public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 40291 0 adrianba 2010-09-30 20:34:52 +0000 The spec says: "This triggers a sequence of events dependent on the activation mechanism, and normally culminating in a click event followed by a DOMActivate event, as described below." Firing DOMActivate should be a MAY requirement because it is deprecated in DOM L3 Events. See http://www.w3.org/TR/DOM-Level-3-Events/#event-type-DOMActivate, which says: "The DOMActivate event type is defined in this specification for reference and completeness, but this specification deprecates the use of this event type in favor of the related event type click. Other specifications may define and maintain their own DOMActivate event type for backwards compatibility." See also, for example, http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0004.html 40974 1 ian 2010-10-12 06:27:31 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Either something should happen everywhere or it shouldn't. Unless browsers are willing to drop support for it, the spec should require it. If they are, then we should drop it from all specs, not just pretend to frown on it in some places or make it an optional feature. 41098 2 zcorpan 2010-10-12 12:53:30 +0000 Opera has already dropped support for it. It seems Mozilla and WebKit still support it, but maybe they're willing to drop it too. I don't know what IE9 beta does, maybe Adrian can comment on that. 41163 3 ian 2010-10-12 19:41:01 +0000 sicking, mjs: Will Gecko and WebKit drop support for DOMActivate? 41185 4 adrianba 2010-10-12 23:55:15 +0000 IE doesn't support DOMActivate and we have no plans to add it. 41188 5 jonas 2010-10-13 00:55:16 +0000 I'd tentatively say that we're willing to try. It's too late to experiment with Firefox 4, but once that branches (in a matter of few weeks, maybe even days), I'd like to give it a shot. 41217 6 bugs 2010-10-13 11:57:21 +0000 Yeah, I think we could remove DOMActivate pretty soon from Gecko (trunk). 41244 7 ian 2010-10-13 18:13:34 +0000 Awesome. 41323 8 contributor 2010-10-14 09:07:22 +0000 Checked in as WHATWG revision r5628. Check-in comment: Drop DOMActivate http://html5.org/tools/web-apps-tracker?from=5627&to=5628 41324 9 ian 2010-10-14 09:07:33 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given above Rationale: DOMActivate? What DOMActivate? 41493 10 adrianba 2010-10-18 17:01:41 +0000 Thanks.