Details
Description
If a component renders incorrect markup (say, omits a closing tag) this can be very difficult to debug because the page corruption is not immediately obvious. A debug feature in DOMResponseWriter would be useful for detecting and analyzing this.
Activity
Ted Goddard
created issue -
Ted Goddard
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Ted Goddard [ ted.goddard ] |
Ted Goddard
made changes -
Salesforce Case | [] | |
Fix Version/s | 3.2 [ 10338 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #31441 | Fri Oct 12 09:36:51 MDT 2012 | jack.van.ooststroom | Fixed JIRA |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/core/src/main/java/org/icefaces/impl/context/DOMResponseWriter.java
|
Migration
made changes -
Assignee | Ted Goddard [ ted.goddard ] | Jack Van Ooststroom [ jack.van.ooststroom ] |
Migration
made changes -
Assignee Priority | P3 [ 10012 ] |
Migration
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Icefaces Administrator
made changes -
Security | Private [ 10001 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P3 [ 10012 ] |
One technique would be to make use of the fact that the component instance is passed in as an argument to most ResponseWriter calls:
writer.startElement(HTML.SPAN_ELEM, uiComponent);
It should be possible to use the component hierarchy together with the DOM hierarchy to detect problems.