[JBoss JIRA] Created: (RF-1107) Scrollable dataTable. Header scrolled badly on TAB button.
by Ilya Shaikovsky (JIRA)
Scrollable dataTable. Header scrolled badly on TAB button.
----------------------------------------------------------
Key: RF-1107
URL: http://jira.jboss.com/jira/browse/RF-1107
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Environment: FF 2.0.0.6
Reporter: Ilya Shaikovsky
Assigned To: Konstantin Mishin
Fix For: 3.2.0
Two use-cases failed:
"case - 1.png"
frozenColCount=0
all …
[View More]the columns with inputs
last columns aren't in visible part
When I use TAB key - columns scrolled to be displayed (good) but headers jsut stays (Wrong!)
"case - 2.png"
frozenColCount=2
all the columns with inputs
last columns aren't in visible part
I use TAB key. Focused inputs changed one by one only in "frozen zone" (seems good), but after I press TAB on the last input - the focus jumps to non frozen column input and frozen columns - scrolled and shifted down(Wrong!). But headers still aren't scrolled (good in this case).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years, 9 months
[JBoss JIRA] Created: (RF-6026) PickList doesn't accept comma in string value of SelectItem
by Andrzej Haczewski (JIRA)
PickList doesn't accept comma in string value of SelectItem
-----------------------------------------------------------
Key: RF-6026
URL: https://jira.jboss.org/jira/browse/RF-6026
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: WebLogic 10, JSF 1.2, RichFaces 3.3.0, Hibernate JPA, Facelets 1.1.14
Reporter: Andrzej Haczewski
When you use a List<SelectItem> where SelectItems are …
[View More]created like this:
new SelectItem("SOME STRING,CONTAINING COMMA", "A nice string to show in list")
as a PickList <h:selectItems>, and use List<String> as PickList value, then PickList doesn't validate when you add that item to target list.
The reason is that UISelectMany is trying to validate values "SOME STRINGS" and "CONTAINING COMMA" with available items.
The exact point is the UISelectMany.matchValue() method, which returns false on validation of that PickList.
Sample code:
--- BackingBean.java
class BackingBean {
private List<SelectItem> picklistItems;
private List<String> result;
public BackingBean() {
picklistItems = new ArrayList<SelectItem>();
picklistItems.add(new SelectItem("SAMPLE,EXAMPLE", "Sample example"));
}
// then comes getters and setters for picklistItems and result
}
--- PickList.xhtml
<rich:pickList value="#{backingBean.result}">
<h:selectItems value="#{backingBean.picklistItems}">
</rich:pickList>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years, 11 months
[JBoss JIRA] Created: (RF-7351) Regression: "messages: globalOnly does not work properly"
by Joseph Miller (JIRA)
Regression: "messages: globalOnly does not work properly"
---------------------------------------------------------
Key: RF-7351
URL: https://jira.jboss.org/jira/browse/RF-7351
Project: RichFaces
Issue Type: Bug
Components: component, regression
Affects Versions: 3.3.1
Environment: Windows / JBoss 4.2.2.GA / Seam 2.1.1.GA / RichFaces 3.3.1.GA
Reporter: Joseph Miller
Looks like a regression of RF-615...…
[View More] I've upgraded my Seam project to sue RF 3.3.1, in order to fix a number of other bugs, but now messages intended for a single UI component (via the for= ) are appearing in the global messages list at the top of my page.
My page template has:
<rich:messages globalOnly="true" id="page-messages">
...
</rich:messages>
and the controls have:
<rich:message for="my-control-id" id="my-control-id-message">
...
</rich:message>
I can switch the rich:messages to h:messages, and it behaves as it should. Also reverting back to the RichFaces 3.2.2.SR1 jars makes the problem go away, but I get the other older bugs back :(
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
12 years, 11 months