- From: <bugzilla@jessica.w3.org>
- Date: 2014年4月16日 12:17:53 +0000
- To: www-dom@w3.org
- Message-ID: <bug-25365-4009@http.www.w3.org/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: travil@microsoft.com Reporter: crimsteam@gmail.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org 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.
Received on Wednesday, 16 April 2014 12:17:55 UTC