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


           Summary: click() shouldn't have special powers over dispatching
                    click event manually
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: Olli.Pettay@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,

Right now the spec says that click() may cause the default action
to happen, but dispatching click manually doesn't have the same
I don't understand why. Gecko and webkit (if I read the webkit code correctly),
for example, seem to just dispatch click event when click() is called.
Default handling is bound to the elements in the event target chain through
which the event is dispatched. Default handling happens right after the event
has propagated through the chain.

Gecko has one special case for input.click() but I see that as a bug.

I see click() as a leftover from Netscape2/3/IE3 times, or as a 
helper method to dispatch untrusted click event.

(It is however clear that not all default handling should be
processed when handling untrusted event. Both click() and manual dispatching
do dispatch untrusted events.)

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 Monday, 13 June 2011 23:26:01 UTC