[ http://issues.apache.org/jira/browse/MYFACES-744?page=comments#action_12355663 ]
sean schofield commented on MYFACES-744: ---------------------------------------- Why not just put it in its own filter? Why does extension filter have to do everything? Personally I am not a fan of this functionality to begin with. I would hate to see the "fix" interfere with normal operations of the extension filter (a risk this approach would seem to be taking.) > 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
