- From: Bogdan Brinza <bbrinza@microsoft.com>
- Date: Wed, 15 Oct 2014 00:40:05 +0000
- To: "public-webapps@w3.org" <public-webapps@w3.org>
Hi,
I'm Program Manager in Internet Explorer Layout team and while investigating one of the compatibility issues, we've encountered a situation that I'd like to clarify with the working group.
The behavior we see in Chrome is different from IE/Firefox - the messages generated by script trigger default actions (see [1] below). Looking at the specification we believe this is specified here: http://www.w3.org/TR/DOM-Level-3-Events/#trusted-events
Namely:
"Events that are generated by the user agent, either as a result of user interaction, or as a direct result of changes to the DOM, are trusted by the user agent with privileges that are not afforded to events generated by script through theDocumentEvent.createEvent("Event") method, modified using the Event.initEvent() method, or dispatched via theEventTarget.dispatchEvent() method. The isTrusted attribute of trusted events has a value of true, while untrusted events have a isTrusted attribute value of false.
Most untrusted events SHOULD NOT trigger default actions, with the exception of the click event. This event always triggers the default action, even if the isTrusted attribute is false (this behavior is retained for backward-compatibility). All other untrusted events MUST behave as if the Event.preventDefault() method had been called on that event."
This does affect interoperability between browsers and we would want to find the way to improve interoperability in this case. Can you please clarify what behavior is the right in this case and I'll follow up with either Chromium or IE/Firefox on this issue.
[1] - http://jsfiddle.net/jpjjxt70/3/
Received on Wednesday, 15 October 2014 00:40:34 UTC