Summary: | object with object cause double kpart creation | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Koos Vriezen <koos.vriezen> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | Keywords: | triaged |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: |
Description
Koos Vriezen
2009-01-18 17:30:33 UTC
Hi Koos. Are you sure it actually displays the second one, and not just creates the part? And as for loading, the question is when it shouldn't create both parts, because in this: <object data="a.html" id="a"> <object data="b.html" id="b"> </object> </object> <script> function test() { var a = document.getElementById("a"); var b = document.getElementById("b"); alert(a.contentDocument.documentElement.innerHTML); alert(b.contentDocument.documentElement.innerHTML); } </script> <body onload="test()"> ... Both documents are supposed to be loaded (woops, need to commit a fixed contentDocument for <object> though, as well as a parser bug with <head> needs tweaking, but that's besides the point) I'm not sure about displaying the second, but w/ kmplayerpart I get two constructions and two openUrl calls. So it starts two mplayer processes. Well.. The point is if the objects were for html, we would have to create both parts, so I am not sure as to why that shouldn't be the case here. Thank you for the bug report. As this report hasn't seen any changes in 10 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |