Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: 3.0.1, EE-3.0.0.GA
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces3
Description
Looking at ICE-7778 we can see that inputTextarea renders a textarea tag with the text being a child text node. This is different from inputText which uses a value attribute to store its text. When rendering accented characters, the ResponseWriter escapes the accented characters for the textarea, so that the text node actually contains ampersand hash number semicolon sequences. Then, the next lifecycle, when the exact same text is rendered, and the new dom is differenced to the old dom, the old dom then just contains the unescaped original accented characters, while the new dom has the escaped characters, so a difference is detected. But nothing different has been rendered. There's just something happening when loading the old dom that unescapes the strings. This doesn't break anything per se, but is less performant.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Mark Collette
created issue -
Ted Goddard
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Ted Goddard [ ted.goddard ] |
Ted Goddard
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Fix Version/s | EE-3.0.0.GA [ 10262 ] | |
Resolution | Fixed [ 1 ] |
Ted Goddard
made changes -
Summary | Text node unescaping on old dom restore | Textarea value requires input escaping |
Salesforce Case | [] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 3.0.1 [ 10282 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |