Bug 18101

Summary: REGRESSION node.innerHTML doesn't escape > in strings
Product: WebKit Reporter: Bill Keese <bill>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: OS X 10.5   
URL: http://turtle.dojotoolkit.org/~bill/innerHTML.html
Attachments:
Description Flags
little test case. the alert should show &gt; but instead shows > none

Bill Keese
Reported 2008-03-25 21:44:47 PDT
By way of example, getting innerHTML on <button>&gt;</button> will return > whereas it should return &gt; (like on Safari 3.0, FF, and IE). See attached test case.
Attachments
little test case. the alert should show &gt; but instead shows > (214 bytes, text/html)
2008-03-25 21:45 PDT, Bill Keese 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Bill Keese
Comment 1 2008-03-25 21:45:45 PDT
Created attachment 20074 [details] little test case. the alert should show &gt; but instead shows >
Alexey Proskuryakov
Comment 2 2008-03-28 03:00:38 PDT
We do escape '<' and '&' - what is the reason to escape '>'?
Bill Keese
Comment 3 2008-04-11 03:57:45 PDT
(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.
Alexey Proskuryakov
Comment 4 2008-04-11 04:13:05 PDT
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.
Alexey Proskuryakov
Comment 5 2008-05-14 22:23:49 PDT
Reopening to close as a duplicate - this was fixed, after all.
Alexey Proskuryakov
Comment 6 2008-05-14 22:24:01 PDT
*** This bug has been marked as a duplicate of 18976 ***
Note You need to log in before you can comment on or make changes to this bug.