[Bug 25365] New: About trusted="false" in two event orders
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <[email protected]/Bugs/Public/> |
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25365
Bug ID: 25365
Summary: About trusted="false" in two event orders
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: DOM3 Events
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected]
In two event orders:
https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#events-activation-event-order
https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#legacy-uievent-event-order
we have trusted="false", but what is trusted? Should not be isTrusted
attribute?
If yes, then the other site, why in this orders click is not treated as
trusted? For example, in FF and IE, when we move focus to <button> and press
'Enter' or 'Space' we get synthesized click event with isTrusted="true". In FF
the same will be for synthesized DOMActivate. Chrome doesn't support isTrusted
property.
Simple test:
<button id="btn">Move focus to this button and press Enter/Space</button>
<p style="color: blue;">Detailed information for the captured events:</p>
<p id="info"><p/>
<script>
var btn= document.getElementById("btn");
var info = document.getElementById("info");
function readInfo(e){
var data = "Interface: " + e
+ "<br>" + "e.type: " + e.type
+ "<br>" + "e.target: " + e.target
+ "<br>" + "e.isTrusted: " + e.isTrusted + "<br><br>";
info.innerHTML = info.innerHTML + data;
}
btn.addEventListener("keydown", readInfo)
btn.addEventListener("DOMActivate", readInfo)
btn.addEventListener("click", readInfo)
</script>
--
You are receiving this mail because:
You are on the CC list for the bug.