[whatwg] Test suite: Embedded content
Simon Pieters
zcorpan at hotmail.com
Mon Nov 28 16:23:17 PST 2005
Hi,
From: Ian Hickson <ian at hixie.ch>
> > > (<object> is less efficient to implement because the UA has to wait
> > > til it knows what the content type is before it can know how to render
> > > the element.)
> >
> > Also when there's a type attribute?
>
>The attribute is only a hint.
So the hint is only for the UA to decide whether or not to load the
resource?
> > Opera:
> > If plugins are enabled, render all <embed>s and hide all <noembed>s, and
>parse
> > <noembed> as CDATA. If plugins are disabled, hide all <embed>s and
>display all
> > <noembed>s, and parse <noembed> as #PCDATA.
> >
> > Firefox:
> > I can't find a way to disable plugins, so they are treated as Opera's
>"plugins
> > enabled" behaviour.
> >
> > IE:
> > Same as Firefox.
>
>Wow, pretty reasonable interoperability. I guess Opera's behaviour is what
>we should head for, then, making disabling of plugins optional.
Alright.
Regards,
Simon Pieters
More information about the whatwg
mailing list