"Anne van Kesteren" <[EMAIL PROTECTED]>
http://www.w3.org/TR/2006/WD-xbl-20060619/#eventxbl introduces
EventXBL.trusted which basically has to be implemented by all objects
implementing the Event object. Given that this information might also make
sense outside of XBL perhaps we should lift the text and put it on Event
directly?
if it can be suitably defined, then I think it should be on Event directly
if at all, however I have reservations of how it can be defined and
implemented. User agents will need to provide API's for their plugins that
can distinguish between the 2 cases of user and non-user provided events -
an Access Technology must be producing events that are trusted, or it would
hobble AT's.
There's also a lot of development of AT's that are simply scripts included
in the page, these would have no mechanism of creating trusted events, and
would in effect hobble these scripts entirely. Is that really worthwhile
considering the use cases of this trusted attribute? What are the use
cases?
In an action taken upon that discussion it was suggested to
http://www.w3.org/mid/[EMAIL PROTECTED] defer this feature
indefinitely. The WG hasn't discussed the outcome of this action.
It seems a good result :-)
Jim.
