- From: <bugzilla@jessica.w3.org>
- Date: Fri, 14 Oct 2011 20:17:40 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14471 Summary: "An algorithm is allowed to show a pop-up if: ..." is not compatible with the implementations 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: bzbarsky@mit.edu, mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org Blocks: 14427 "An algorithm is allowed to show a pop-up if: - it is running in the context of an activation behavior or of the dispatching of a click event, and - The click events that led to the triggering of the activation behaviors, if any, and the click events of any event dispatching that indirectly led to the algorithm being invoked, if any, are all trusted." Testcase http://mozilla.pettay.fi/moztests/popup.html All the browsers open a new tab Since webkit doesn't support <a>.click() the test case is a bit hacky and uses <input> element to dispatch click. I could have of course just dispatched click using createEvent/initMouseEvent/dispatch (I'm not quite happy with the test case, since it relies on the implemented "activation behavior", not the totally different thing what the spec defines.) But anyway, the point is that implementations usually allow popups *while* handling a trusted click event. Inside the event listener one can dispatch/handle other events, but that doesn't affect to the popup blocking. Manually dispatching and handling an event is effectively just a (synchronous) function call. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Friday, 14 October 2011 20:17:46 UTC