W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2010

trusted property

From: Hallvord R. M. Steen <hallvord@opera.com>
Date: Wed, 03 Mar 2010 15:30:26 +0000
Message-ID: <20100303153026.oufzgbu2ggs4880g@staff.opera.com>
To: www-dom@w3.org
I'm not sure what the use case is for exposing a "trusted" property to  
normal scripts. It also seems rather draconian to say that "All other  
untrusted events must behave as if the Event.preventDefault() method  
had been called on that event". This comes right after a sentence  
saying "should not trigger default actions". So is this a "should" or  
a "must" requirement for an implementor?


Also, it may need to say that setting properties directly on the event  
object should change event.trusted to false? E.g. some browsers let me  
set event.keyCode for a key event. Having done that the event is  
presumably no longer "trusted"?

Hallvord R. M. Steen
Core tester, Opera Software
Received on Wednesday, 3 March 2010 15:30:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:36:56 UTC