Bug 96824 – <object> elements do not get re-evaluated when their attributes have changed and have been removed from/added back into the DOM

• Status: RESOLVED
• Resolution: WONTFIX
• Component: Plug-ins

[Jon Lee]

Created attachment 164224 [details]
Test case

Loading a Flash movie, and then having a button that removes the object element from the DOM, changes the object's parameters to load an image, and then inserts it back, does not render an image.

According to WHATWG spec, http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#the-object-element

-----

Whenever one of the following conditions occur:

1. the element is created,
2. the element is popped off the stack of open elements of an HTML parser or XML parser,
3. the element is not on the stack of open elements of an HTML parser or XML parser, and it is either inserted into a document or removed from a document,
4. the element's Document changes whether it is fully active,
5. one of the element's ancestor object elements changes to or from showing its fallback content,
6. the element's classid attribute is set, changed, or removed,
7. the element's classid attribute is not present, and its data attribute is set, changed, or removed,
8. neither the element's classid attribute nor its data attribute are present, and its type attribute is set, changed, or removed,
9. the element changes from being rendered to not being rendered, or vice versa,

...the user agent must queue a task to run the following steps to (re)determine what the object element represents.

-----

Compare the attached test case with Firefox. Load the test, then click on the button. It should switch to a static image.

[Alexey Proskuryakov]

Mass closing plug-in bugs, as plug-in support has been removed from WebKit.

Please comment and/or reopen if this still affects WebKit in some way.