See url, you see plugin placeholders where you should see some flash text. I'll attach a testcase to this bug that shows the bug.

Two embeds in the testcase, one directly in the page, one dynamically created. The dynamically created one gives the plugin placeholder, that should not happen. This works fine on current branch builds.

Biesi: This sounds likely related to your rewrite.

hmm. this is an interesting one. We start loading the object when you the src attribute is set, and find out that we can't handle application/octet-stream. We ignore changes to the type attribute after we started loading the object. Unfortunately I can't reproduce this on the original site, but bug 347736's patch may significantly reduce the impact of this.

Is there any point in starting the load before we're in the document? I know we do for images, but that is partially web-compat to allow pages to preload images.

why wait until we're inserted into the doc?

Can we deal with all types of chages, such as to the type attribute, if we've already started loading? There's also the issue that we could get a different baseURI when inserted into a parent.

we handle the base URI change correctly, we do check for a changed URI when the plugin is inserted into the doc. we could extend that to types I suppose...

jonas convinced me to only start loads once we get inserted into a document. note that if we start the load before that, and it is a plugin, then we will not really be able to use that data because we don't have a frame yet, so we'd have to start the load again. waiting until we get inserted avoids that problem.

Comment on attachment 272908 [details] [diff] [review] patch Hmmm. Yeah, I guess this makes sense... If you wanted to, you could also add a check for whether DoneAddingChildren() got called here. Might not matter, though.

hm... is it really possible that aNotify is true, mDoneAddingChildren false, and SetAttr is being called?

Yes, of course. Consider an <object> with a <script> child which sets attributes on that <object>. Pretty stupid thing to do, but certainly possible. ;)

OK, check mIsDoneAddingChildren

Checking in content/html/content//src/nsHTMLObjectElement.cpp; /cvsroot/mozilla/content/html/content/src/nsHTMLObjectElement.cpp,v <-- nsHTMLObjectElement.cpp new revision: 1.104; previous revision: 1.103 done Checking in content/html/content//src/nsHTMLSharedObjectElement.cpp; /cvsroot/mozilla/content/html/content/src/nsHTMLSharedObjectElement.cpp,v <-- nsHTMLSharedObjectElement.cpp new revision: 1.87; previous revision: 1.86 done