18101 2008-03-25 21:44:47 -0700 REGRESSION node.innerHTML doesn't escape > in strings 2008-05-14 22:24:01 -0700 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) All OS X 10.5 RESOLVED DUPLICATE 18976 http://turtle.dojotoolkit.org/~bill/innerHTML.html P2 Normal --- 0 bill webkit-unassigned ap oldest_to_newest 75261 0 bill 2008-03-25 21:44:47 -0700 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. 75262 1 20074 bill 2008-03-25 21:45:45 -0700 Created attachment 20074 little test case. the alert should show > but instead shows > 75611 2 ap 2008-03-28 03:00:38 -0700 We do escape '<' and '&' - what is the reason to escape '>'? 77269 3 bill 2008-04-11 03:57:45 -0700 (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. 77270 4 ap 2008-04-11 04:13:05 -0700 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. 80460 5 ap 2008-05-14 22:23:49 -0700 Reopening to close as a duplicate - this was fixed, after all. 80461 6 ap 2008-05-14 22:24:01 -0700 *** This bug has been marked as a duplicate of 18976 *** 20074 2008-03-25 21:45:45 -0700 2008-03-25 21:45:45 -0700 little test case. the alert should show > but instead shows > innerHTML.html text/html 214 bill PGh0bWw+Cjxib2R5IG9ubG9hZD0iYWxlcnQoZG9jdW1lbnQuZ2V0RWxlbWVudEJ5SWQoJ2J1dHRv bicpLmlubmVySFRNTCkiPgoJVGhpcyBpcyBhIHRlc3Qgb2YgaW5uZXJIVE1MIHRvIHNlZSBpZiBp dCBjb252ZXJ0cyBzcGVjaWFsIGNoYXJzIGxpa2UgJmd0OyB0byBlbnRpdGllcy4KCTxidXR0b24g aWQ9ImJ1dHRvbiI+Jmd0OzwvYnV0dG9uPgo8L2JvZHk+CjwvaHRtbD4KCg==