W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2011

[whatwg] Javascript: URLs as element attributes

From: Philip Jägenstedt <philipj@opera.com>
Date: Mon, 16 May 2011 09:59:53 +0200
Message-ID: <op.vvkdt3ztsr6mfa@kirk>
On Sat, 14 May 2011 00:34:36 +0200, Ian Hickson <ian at hixie.ch> wrote:

> On Mon, 14 Feb 2011, Philip J?genstedt wrote:
>>
>> For the record, I removed Opera's "support" (I assume it was an
>> unintended side-effect) for <object data="javascript:..."> along with
>> the rest at the time when I wrote my previous mail in this thread. This
>> intentionally doesn't match what the spec says. (Disclaimer: this is
>> only my opinion on something that isn't really my area of expertise, so
>> others at Opera might decide that the spec is great and push in the
>> opposite direction. It seems unlikely at this point, though.)
>>
>> [...]
>>
>> Of what has been brought up so far, javascript: as an inline resource is
>> not very useful at all, so IMO the only reason to keep it would be for
>> legacy compat. I'll follow up on this again once the change to block
>> inline javascript: URLs in Opera has been in the wild for a while,
>> hopefully reporting that no compat issues have arisen.
>
> Since only Firefox now supports this, I've removed support for it from  
> the
> spec. (It's just commented out for now; we can put it back if someone
> makes a compelling argument.)

Great! I can report that the changes to block inline javascript: URLs went  
into Opera 11.10 and so far I'm not aware of any site compat issues having  
being caused by it.

-- 
Philip J?genstedt
Core Developer
Opera Software
Received on Monday, 16 May 2011 00:59:53 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:06 UTC