Re: SecurityPolicyViolation DOM events.

On Tue, Mar 19, 2013 at 10:29 AM, Mike West <> wrote:
> I've updated the spec in
> and
> Hopefully
> that makes things a little less vague and strange. Thanks again, Anne, for
> the pointers!

So it's completely unclear when this event is dispatched. What task
source is used, how does it relate to other events that fire when the
violation occurs, etc.

I have the feeling the right long term solution is tight integration
with to solve problems such as this. I
don't have an immediate suggestion on how to fix this, but I think we
should at least point out in the specification that this is not


Received on Wednesday, 20 March 2013 13:14:34 UTC