Yeah... this was a recent regression; it's now fixed on both branch and trunk. Thanks for the bug report, Pieter! *** This bug has been marked as a duplicate of 137428 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
Wow, that was quick! And great that it is fixed already. My apologies for not seeing the duplicate (I missed it in my search on cloneNode, I guess I did not search correctly.) Thank you!
No, you did search correctly. The summary didn't have cloneNode in it until a couple minutes before Boris duped the bug. I asked him to add cloneNode to the summary of the original and then dupe this one (which I could not find either). Verifying duplicate.
Status: RESOLVED → VERIFIED
Yep. What Christopher said. I was an idiot and didn't add cloneNode to the other bug's summary at the right time (like when I figured out it was caused by cloneNode.... :) )
Component: DOM: Core → DOM: Core & HTML
QA Contact: stummala → general
You need to log in before you can comment on or make changes to this bug.