Re: Scripts that are in noembed or noscript containers at the time of attempted run from Simon Pieters on 2009-07-15 (public-html@w3.org from July 2009)

From: Simon Pieters <simonp@opera.com>
Date: Wed, 15 Jul 2009 13:59:31 +0200
To: "Jonas Sicking" <jonas@sicking.cc>, "Henri Sivonen" <hsivonen@iki.fi>
Cc: "public-html@w3.org WG" <public-html@w3.org>
Message-ID: <op.uw3x9hyzidj3kv@simon-pieterss-macbook.local>

On Fri, 10 Jul 2009 19:12:04 +0200, Jonas Sicking <jonas@sicking.cc> wrote:

> On Fri, Jul 10, 2009 at 1:12 AM, Henri Sivonen<hsivonen@iki.fi> wrote:
>> It seems (from source) that Gecko prevents script execution if at the  
>> time
>> of attempted run, the script is in a noframes, noembed or iframe  
>> container.
>>
>> http://mxr.mozilla.org/mozilla-central/source/content/base/src/nsScriptElement.cpp#148
>>
>> Might matter for XHTML5.
>
> I think the current thinking is that this is just a leftover from
> olden days when we implemented the no* elements differently. I'd be
> all for removing that as I doubt any significant number of sites will
> be affected.

I remember this being brought up a few years ago on the WHATWG list, with  
the same explanation. IIRC Opera and WebKit do run the scripts.

-- 
Simon Pieters
Opera Software

Received on Wednesday, 15 July 2009 12:00:27 UTC