[ http://issues.apache.org/jira/browse/MYFACES-744?page=comments#action_12355656 ]
Simon Kitching commented on MYFACES-744: ---------------------------------------- As people have mentioned on the email lists, updating every renderer to check for this flag and render "cleaner" output if it is set is a lot of work. It will also clutter the renderer classes with unnecessary code. The ExtensionsFilter already buffers the entire output. I suggest that the ExtensionsFilter therefore check for the flag, and if set run the buffered page through some cleanup library like JTidy or NekoHTML: http://jtidy.sourceforge.net/ http://people.apache.org/~andyc/neko/doc/html/index.html This will clean up not just the JSF component renderer output but the whole page. > PRETTY_HTML option is not being universally honored > --------------------------------------------------- > > Key: MYFACES-744 > URL: http://issues.apache.org/jira/browse/MYFACES-744 > Project: MyFaces > Type: Improvement > Components: Tomahawk > Versions: 1.1.1 > Environment: Tomahawk component running on a MyFaces JSF implementation > Reporter: Brendan Conner > Priority: Trivial > > MyFaces recognizes the following context parameter: > <context-param> > <param-name>org.apache.myfaces.PRETTY_HTML</param-name> > <param-value>true</param-value> > <description> > If true, rendered HTML code will be formatted, so that it > is "human readable," > i.e. additional line separators and whitespace will be > written that do not influence the HTML code. > Default: "true" > </description> > </context-param> > However, not all the component renderers are honoring this setting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
