[whatwg] <object> behavior

Michael A. Puls II shadow2531 at gmail.com
Fri Sep 18 01:57:27 PDT 2009


On Mon, 14 Sep 2009 08:42:10 -0400, Boris Zbarsky <bzbarsky at mit.edu> wrote:

>  We (Gecko) consider it a bug that a display:none <object> in a document  
> doesn't instantiate the plug-in.

BTW, what is the reason for considering it a bug? Is it because:

{
visibility: hidden;
width: 0;
height: 0;
padding: 0;
margin: 0;
line-height: 0;
font-size: 0
border: 0
}

is insufficient and or a pain when you want to load a plug-in but  
completely hide it so it's as if it's not there layout-wise?

Or, is there some other reason(s)?

Do you know of any sites that would work better if the bug was fixed? Know  
any sites that'd break or begin to unexpectedly load a bunch of <object>'s  
that weren't meant to be loaded yet?

If the change is trivial, maybe someone can throw up an experimental FF or  
webkit binary with the fix. (Or, provide it as an about:config option in  
the trunk builds like the HTML5 parser option is).

Then, I can test how things work and give feedback.

Thanks

-- 
Michael



More information about the whatwg mailing list