W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 12949] click() shouldn't have special powers over dispatching click event manually

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Aug 2011 23:28:35 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QrICR-0000vw-9X@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12949

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #29 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-10 23:28:34 UTC ---
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: 

As others have said, it is the responsibility of the code (UA or script) that
dispatches the event to ensure that a default action, if any, is performed.
Indeed, the default action could differ based on how is firing the event. For
example, one could have an event target to which one dispatches a "foo" event,
and if it isn't canceled, one then pops up an alert... but some other code
could instead dispatch a "foo" event, and if it isn't canceled, adds text to a
console.

Historically, browsers have had exceptions to this — different exceptions in
each browser. But we're moving away from this as a rationalisation of the
platform.

Now given this model, we do need a mechanism by which one can invoke the
default activation behaviour of an element, e.g. to click a button, open an
input file dialog, or whatnot. And that's what click() does.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 10 August 2011 23:28:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:16 UTC