Bug 18101 - REGRESSION node.innerHTML doesn't escape > in strings
Summary: REGRESSION node.innerHTML doesn't escape > in strings
Status: RESOLVED DUPLICATE of bug 18976
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All OS X 10.5
: P2 Normal
Assignee: Nobody
URL: http://turtle.dojotoolkit.org/~bill/i...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-25 21:44 PDT by Bill Keese
Modified: 2008-05-14 22:24 PDT (History)
1 user (show)

See Also:

Attachments
little test case. the alert should show > but instead shows > (214 bytes, text/html)
2008-03-25 21:45 PDT, Bill Keese 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Keese 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.
Comment 1 Bill Keese 2008-03-25 21:45:45 PDT 
Created attachment 20074 [details]
little test case.  the alert should show &gt; but instead shows >
Comment 2 Alexey Proskuryakov 2008-03-28 03:00:38 PDT 
We do escape '<' and '&' - what is the reason to escape '>'?
Comment 3 Bill Keese 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.
Comment 4 Alexey Proskuryakov 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.
Comment 5 Alexey Proskuryakov 2008-05-14 22:23:49 PDT 
Reopening to close as a duplicate - this was fixed, after all.
Comment 6 Alexey Proskuryakov 2008-05-14 22:24:01 PDT 

*** This bug has been marked as a duplicate of 18976 ***