[jira] Commented: (MYFACES-1350) selectOneRadio renders extra /tr after each option if layout=pageLayout

[Tiago Rinck Caveden (JIRA)]

[ 
https://issues.apache.org/jira/browse/MYFACES-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489851
 ] 

Tiago Rinck Caveden commented on MYFACES-1350:
--

We also noticed that in our project here. It's causing us some issues too.

 selectOneRadio renders extra /tr after each option if layout=pageLayout
 ---

 Key: MYFACES-1350
 URL: https://issues.apache.org/jira/browse/MYFACES-1350
 Project: MyFaces Core
  Issue Type: Bug
Reporter: Peace Software
Priority: Minor

 org.apache.myfaces.renderkit.html.HtmlRadioRendererBase is rendering an extra 
 /tr after each option if layout=pageDirection.  The encode end method has 
 a line which says if (pageDirectionLayout) writer.endElement(HTML.TR_ELEM); 
 even though it hasn't started a tr.
 This is causing page layout issues for us.

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

[jira] Created: (MYFACES-1059) inputText doesn't work inside a dataTable with scroll

[Tiago Rinck Caveden (JIRA)]

inputText doesn't work inside a dataTable with scroll
-

 Key: MYFACES-1059
 URL: http://issues.apache.org/jira/browse/MYFACES-1059
 Project: MyFaces
Type: Bug
  Components: Tomahawk  
Versions: 1.1.1
 Environment: Windows 2000 or XP
Firefox or IE.
Reporter: Tiago Rinck Caveden


There seems to be a problem using inputText inside dataTables that have a 
scroll component.

Independent of how I scrolled on the list, the value of the inputTexts remained 
to be the same of the values that should be in the first page only. (the first 
values of the query)
Not understanding what was going on, I started trying everything. When I trade 
from an inputText to an outputText, then it started working. More interesting: 
if I let some columns with outputText, and others with inputText, then only the 
formmer would change with the navegation, the latter would remain always with 
the first values.

Another detail that might be interesting (or not): I've notice that somthing 
might be (wrongly?) cached in memory, because just changing the component 
wouldn't make any difference, I had to redo the query (which was kept in the 
session) in order for the difference to come.

-- 
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