[ https://issues.apache.org/jira/browse/TOBAGO-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008076#comment-16008076 ]
Hudson commented on TOBAGO-1721: -------------------------------- SUCCESS: Integrated in Jenkins build Tobago Trunk #884 (See [https://builds.apache.org/job/Tobago%20Trunk/884/]) TOBAGO-1721 Optimize HTML output when two renderer are involved * fix images for tc:selectOneRadio in a dropdown (hnoeth: [http://svn.apache.org/viewvc/?view=rev&rev=1794965]) * (edit) tobago-trunk/tobago-core/src/main/resources/scss/_tobago.scss TOBAGO-1721 Optimize HTML output when two renderer are involved * fix checkstyle (hnoeth: [http://svn.apache.org/viewvc/?view=rev&rev=1794959]) * (edit) tobago-trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/renderkit/css/TobagoClass.java > Optimize HTML output when two renderer are involved > --------------------------------------------------- > > Key: TOBAGO-1721 > URL: https://issues.apache.org/jira/browse/TOBAGO-1721 > Project: MyFaces Tobago > Issue Type: Bug > Components: Core > Affects Versions: 3.0.3 > Reporter: Henning Noeth > Assignee: Henning Noeth > > A renderer produce HTML code without consider the environment. > For example: > The InRenderer always generate a <span/> around children. > If a button has children, the ButtonRenderer always generate a <span/> > element around the button and its children. > So if a <tc:button> is inside a <tc:in>, two <span/> elements would be > generated. > In this case, the renderer should work together, to only generate one <span> > element. > The generated code is more compact. > It's more the way of bootstrap. > And because of that, there are less problems to solve with CSS. -- This message was sent by Atlassian JIRA (v6.3.15#6346)