Re: [whatwg] behavior

Tue, 26 Jan 2010 01:46:05 -0800

On Mon, 25 Jan 2010 20:36:27 -0500, Ian Hickson <i...@hixie.ch> wrote:

On Thu, 10 Dec 2009, Michael A. Puls II wrote:
> >
> > Also see <https://bugzilla.mozilla.org/show_bug.cgi?id=90268#c68>.
> > Should probably add a note in the spec that the css overflow and
> > position properties don't affect instantiation/destroying etc.
> > (might as well add visibility too). And, after that, it'd probably
> > be best to note that css in general doesn't affect
> > instantiation/destroying (to avoid having to keep on adding CSS
> > properties to the list)
> >
> > Something like this:
> >
> > Note: The above algorithm is independent of CSS. For example, it
> > runs even if the element is hidden or out-of-view because of the
> > 'display', 'position', 'visibility' and 'overflow' properties.
> >
> > Further, changing the value of any CSS property does not cause the
> > above algorithm to run again on the element. For example, changing
> > the element's 'display' property from 'inline-block' to 'none' does
> > not destroy the loaded resource.
>
> Fair enough. Done something like the above.

That'll work. Could you make the change for <embed> and <applet> too
when you have time?

It appears I have already done so.

Thanks.

Please see the note in the <object> element section. It has more detailed info. The embed and applet elements have the old, less-detailed note.

--
Michael

Reply via email to