You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Kent Tong (JIRA)" <de...@myfaces.apache.org> on 2007/12/28 04:12:43 UTC

[jira] Created: (TOMAHAWK-1173) Allow plain html markup inside

Allow plain html markup inside <t:datalist>
-------------------------------------------

                 Key: TOMAHAWK-1173
                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1173
             Project: MyFaces Tomahawk
          Issue Type: Improvement
          Components: Data List
    Affects Versions: 1.1.5
            Reporter: Kent Tong
            Priority: Minor


Currently, a <t:datalist> only allows JSF components in its body. This makes it very difficult to
render a <table> like:

<t:datalist>
<tr>
<td><h:outputText.../></td>
<td><h:outputText.../></td>
<td><h:outputText.../></td>
</tr>
</t:datalist>

For a <table> one could use the datatable, but one may not want to have such a heavy weight
component or may need to output a <dl>.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (TOMAHAWK-1173) Allow plain html markup inside

Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/TOMAHAWK-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554812 ] 

Andrew Robinson commented on TOMAHAWK-1173:
-------------------------------------------

Why not just use:
<t:datalist>
<h:panelGroup><tr>
<td><h:outputText.../></td>
<td><h:outputText.../></td>
<td><h:outputText.../></td>
</tr></h:panelGroup>
</t:datalist> 

> Allow plain html markup inside <t:datalist>
> -------------------------------------------
>
>                 Key: TOMAHAWK-1173
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1173
>             Project: MyFaces Tomahawk
>          Issue Type: Improvement
>          Components: Data List
>    Affects Versions: 1.1.5
>            Reporter: Kent Tong
>            Priority: Minor
>
> Currently, a <t:datalist> only allows JSF components in its body. This makes it very difficult to
> render a <table> like:
> <t:datalist>
> <tr>
> <td><h:outputText.../></td>
> <td><h:outputText.../></td>
> <td><h:outputText.../></td>
> </tr>
> </t:datalist>
> For a <table> one could use the datatable, but one may not want to have such a heavy weight
> component or may need to output a <dl>.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (TOMAHAWK-1173) Allow plain html markup inside

Posted by "Kent Tong (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/TOMAHAWK-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554881 ] 

Kent Tong commented on TOMAHAWK-1173:
-------------------------------------

That will not work either.

However, I realized that this is not a limitation of datalist, but the limitation of JSF: If a JSF component is going to render itself body, it can only contain JSF component and nothing else, so HTML code will not be allowed.

> Allow plain html markup inside <t:datalist>
> -------------------------------------------
>
>                 Key: TOMAHAWK-1173
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1173
>             Project: MyFaces Tomahawk
>          Issue Type: Improvement
>          Components: Data List
>    Affects Versions: 1.1.5
>            Reporter: Kent Tong
>            Priority: Minor
>
> Currently, a <t:datalist> only allows JSF components in its body. This makes it very difficult to
> render a <table> like:
> <t:datalist>
> <tr>
> <td><h:outputText.../></td>
> <td><h:outputText.../></td>
> <td><h:outputText.../></td>
> </tr>
> </t:datalist>
> For a <table> one could use the datatable, but one may not want to have such a heavy weight
> component or may need to output a <dl>.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.