W3C home > Mailing lists > Public > public-webappsec@w3.org > March 2013

Re: SecurityPolicyViolation DOM events.

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 19 Mar 2013 07:12:37 -0400
Message-ID: <CADnb78jzZEeCqh0Hyu3q-Sgm+myG=f_Ar_N+i0ecwL3PXUU-Cw@mail.gmail.com>
To: Mike West <mkwst@google.com>
Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>, "dveditz@mozilla.com" <dveditz@mozilla.com>, Adam Barth <w3c@adambarth.com>, "Hill, Brad" <bhill@paypal-inc.com>
On Tue, Mar 19, 2013 at 6:22 AM, Mike West <mkwst@google.com> wrote:
> In https://dvcs.w3.org/hg/content-security-policy/rev/0c7cb63e2e48, I've
> stubbed out an initial pass at a SecurityPolicyViolationEvent interface. I'd
> appreciate some feedback on both the content and the language used to
> describe it. I tried to steal context from other specs, but none really did
> exactly what I wanted. Ah well.

Event.cancelable is already false by default so you don't have to say
that. You also need to initialize all the other members. See
http://xhr.spec.whatwg.org/#concept-event-fire-progress for an
example.

You also need to define an event constructor, see
http://xhr.spec.whatwg.org/#interface-progressevent for an example.


-- 
http://annevankesteren.nl/
Received on Tuesday, 19 March 2013 11:13:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:00 UTC