[Bug 14427] New: Investigate if click()'s click-in-progress should apply to user and/or script initiated clicks

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14427

           Summary: Investigate if click()'s click-in-progress should
                    apply to user and/or script initiated clicks
           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,
                    public-html@w3.org


Currently if user clicks <a href="http://www.w3c.org" target="_blank"
onclick="this.click()">foo</a>
that will per spec open two new browsing contexts.
That is how Gecko works.

IE9 and Opera have different behavior. They seems to set click-in-progress flag
also when user clicks. But they don't handle that in the same way.
https://bugzilla.mozilla.org/show_bug.cgi?id=679566#c17
IE sets the flag only to event target, Opera also to ancestors, or something
like that.

IE's behavior is very error prone, so either the spec should stay as it is, or
it should follow what Opera does.

(Webkit doesn't have a.click())

-- 
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 Tuesday, 11 October 2011 11:37:28 UTC