ISSUE-52: unsafe attribute requires every handler to check

unsafe DOM API

unsafe attribute requires every handler to check

State:
CLOSED
Product:
UI Security
Raised by:
Brad Hill
Opened on:
2013-04-25
Description:
abarth: requiring every handler to check unsafe makes it difficult to write the correct code. better would be to be able to provide a wrapper function that filters or intercepts all unsafe events so they can be acted on wherever they are generated.
Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

Closed after review on list. These events can be caught and handled globally by the root element of the DOM as they propagate, no changes to spec text needed.

Brad Hill, 25 Nov 2013, 22:33:32

Display change log ATOM feed


Daniel Veditz <dveditz@mozilla.com>, Mike West <mkwst@google.com>, Chairs, Wendy Seltzer <wseltzer@w3.org>, Samuel Weiler <weiler@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 52.html,v 1.1 2020/01/17 08:52:36 carcone Exp $