duplicate ID dom damage

Sometimes it is useful to switch two DOM objects with each other, and to reassign their ID's to make the process transparent. But in Safari and Safari alone, assigning an ID which already is being used does something bad. One of the objects can no longer be retrieved via document.getElementById, ever.

Test page Workaround is included
Reported by: Scott Lindsey.

Safari | Reported on 22 August 2007.

This site is no longer maintained. I’m sorry, but it’s just too much work for too little return. You can continue to browse old bug reports, though.

Search reports by browser:

Atom RSS


(Add your own)

1 Posted by Brian LePore on 22 August 2007 | Permalink

Any idea what version(s) of Safari this doesn't work under? This works for me on Win Safari using a nightly build.

2 Posted by ppk on 23 August 2007 | Permalink

Oops, should have added a note. This bug is solved in Safari 3, but it occurs in 1.3 . Don't know about 2.