W3C home > Mailing lists > Public > public-webapi@w3.org > June 2006

Re: [DOM3EV] introduce Event.trusted? (ISSUE-10)

From: Jim Ley <jim@jibbering.com>
Date: Mon, 26 Jun 2006 02:24:50 +0100
Message-ID: <005001c698bf$52f8a440$0302a8c0@Sniff>
To: "Web APIs WG \(public\)" <public-webapi@w3.org>

> The current use cases in Gecko are, in addition to the above:
>
> 1)  Allowing browser extensions to decide whether to listen to all events
>     or only trusted ones; whatever their reasons for it.
> 2)  Only allowing middle-mouse paste into an editor if the middle-click
>     event is trusted.
> 3)  Some XForms stuff I'm not familiar with.
> 4)  Some XBL stuff.
> 5)  Text input and textarea only respond to trusted events (not sure why;
>     would need to dig in the CVS history).
> 6)  Anchor default actions (showing text in the status bar and following
>     the link) only happen for trusted events; I believe the status bar
>     part was why this was done...
> 7)  Untrusted events do not put the popup blocker into the "user actually
>     did something like clicking a button, which means he may want a new
>     window" mode.

My one problem with these, is that they're all User Agent reasons for 
wanting it, very good ones, none of them provide reasons for exposing it 
outside of the user agent, which is what we're doing here, I assume some of 
the XBL stuff is doing it.

As you've shown though Mozilla has a viable model for it, so I'm pretty 
happy with adding it.

Cheers,

Jim. 
Received on Monday, 26 June 2006 01:24:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:55 GMT