By way of example, getting innerHTML on <button>></button> will return > whereas it should return > (like on Safari 3.0, FF, and IE). See attached test case.
Created attachment 20074 [details]
little test case. the alert should show > but instead shows >
We do escape '<' and '&' - what is the reason to escape '>'?
(In reply to comment #2)
> We do escape '<' and '&' - what is the reason to escape '>'?
Hmm, well I filed this ticket because it's causing one of our product's unit tests to fail (and since Safari 3.1's behavior was different than all other browsers I tested) but as far as practical issues, I can't think of anything... OK I will close the bug.
Thank you for filing this bug - having seen it will make practical problems caused by this easier to recognize, if we ever encounter any.
Not escaping '>' makes the code slightly faster, so I hesitate to "fix" this pre-emptively.
Reopening to close as a duplicate - this was fixed, after all.
*** This bug has been marked as a duplicate of 18976 ***