[
https://issues.apache.org/jira/browse/TRINIDAD-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663250#action_12663250
]
havis edited comment on TRINIDAD-1342 at 1/12/09 11:28 PM:
-------------------------------------------------------------------
For example inputText is rendered for read-only state differently inside the
table and out of table. Inside the table is missing parent tag, which defines
state skin selector. That's why state skin selectors not working for inputText
component inside table cell.
- DOM output for inputText outside table (state selector p_AFReadOnly rendered
correctly):
<table class="af_inputText p_AFReadOnly" ...>
<tr>
<td class="af_inputText_label" nowrap>Label</td>
<td valign="top" nowrap class="AFContentCell">
<!--Start: org.apache.myfaces.trinidad.Input["_id11"]-->
<div id="_id11" class="af_inputText_content">Some text
</div>
</td>
</tr>
<!--Start: org.apache.myfaces.trinidad.Input["_id11"]-->
<tr>
<td></td>
<td class="AFComponentMessageCell">
<!--Start: org.apache.myfaces.trinidad.Input["_id11"]-->
<span class="OraInlineErrorText">
</span></td>
</tr>
</table>
- DOM output for inputText inside table (state selector p_AFReadOnly is
missing):
<!--Start: org.apache.myfaces.trinidad.Input["_id19"]-->
<div id="_id13:22:_id19" class="af_inputText_content" title="Type
to change 'submittedValue'">
</div>
<div>
</div>
<!--Start: org.apache.myfaces.trinidad.Input["_id19"]-->
<span class="OraInlineErrorText">
</span></td>
This is the problem described in TRINIDAD-1118 issue. When no response with
that, I've tried to solve this problem with defining custom skin selectors for
different DOM element output for that situation, when inputText is included
inside the table. That's mean, when read only inputText is inside table, div
element is rendered. So I've tried to define div.af|inputText::content skin
selector, but this is not rendered as input.af_inputText_content as I assume,
but in different "wrong" way as div.af_inputText div_content.
Well, my priority here is to solve TRINIDAD-1118 issue.
was (Author: havis):
For example inputText is rendered for read-only state differently inside
the table and out of table. In the table is missing parent tag, which defines
state skin selector. That's why state skin selectors not working for inputText
component inside table cell.
- DOM output for inputText outside table (state selector p_AFReadOnly rendered
correctly):
<table class="af_inputText p_AFReadOnly" ...>
<tr>
<td class="af_inputText_label" nowrap>Label</td>
<td valign="top" nowrap class="AFContentCell">
<!--Start: org.apache.myfaces.trinidad.Input["_id11"]-->
<div id="_id11" class="af_inputText_content">Some text
</div>
</td>
</tr>
<!--Start: org.apache.myfaces.trinidad.Input["_id11"]-->
<tr>
<td></td>
<td class="AFComponentMessageCell">
<!--Start: org.apache.myfaces.trinidad.Input["_id11"]-->
<span class="OraInlineErrorText">
</span></td>
</tr>
</table>
- DOM output for inputText inside table (state selector p_AFReadOnly is
missing):
<!--Start: org.apache.myfaces.trinidad.Input["_id19"]-->
<div id="_id13:22:_id19" class="af_inputText_content" title="Type
to change 'submittedValue'">
</div>
<div>
</div>
<!--Start: org.apache.myfaces.trinidad.Input["_id19"]-->
<span class="OraInlineErrorText">
</span></td>
This is the problem described in TRINIDAD-1118 issue. When no response with
that, I've tried to solve this problem with defining custom skin selectors for
different DOM element output for that situation, when inputText is included
inside the table. That's mean, when read only inputText is inside table, div
element is rendered. So I've tried to define div.af|inputText::content skin
selector, but this is not rendered as input.af_inputText_content as I assume,
but in different "wrong" way as div.af_inputText div_content.
Well, my priority here is to solve TRINIDAD-1118 issue.
> HTML tag custom skinning
> ------------------------
>
> Key: TRINIDAD-1342
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1342
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Skinning
> Affects Versions: 1.0.10-core
> Reporter: Tomas Havelka
>
> Cannot skin generated HTML elements with specificly generated component skin
> selector.
> For example, I want to skin inputText component, but renderer renderes its
> skin selector af_inputText_content to different output HTML elements for
> different situations. What I need here, is to render css selector like
> input.af_inputText_content in generated css file, but I can't do that,
> because skin selector input.af|inputText::content is rendered in wrong way.
> I've tried to solve issue TRINIDAD-1118 with this approach, but I cannot.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
