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

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

From: <bugzilla@jessica.w3.org>
Date: Sun, 03 Jul 2011 10:21:50 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QdJoE-0000i7-65@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12949

--- Comment #16 from Jan Varga <jan.varga@gmail.com> 2011-07-03 10:21:49 UTC ---
(In reply to comment #3)
> Ok, so smaug pointed out to me that for calling click() firefox generally
> doesn't actually activate most elements, which at least for <a>.click() appears
> to be the case. (though <input type=file>.click() does bring up a file picker,
> but I think that's an exception).
> 
> The thing that I care most about is that the spec doesn't say that dispatching
> an event using the EventTarget interface should run what is usually that events
> default action. But if that's not what the spec says then I'm fine.

actually it seems that only <a>.click() doesn't activate, because the click
event is untrusted

http://www.whatwg.org/specs/web-apps/current-work - 4.6.1

now I wonder, how can <a>.click() trigger the command action when it fires
untrusted event

-- 
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 Sunday, 3 July 2011 10:21:55 UTC

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