[JBoss JIRA] Created: (RF-11392) rich:collapsibleSubTable - can't scroll in Mojarra
by Jan Papousek (JIRA)
rich:collapsibleSubTable - can't scroll in Mojarra
--------------------------------------------------
Key: RF-11392
URL: https://issues.jboss.org/browse/RF-11392
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.1.0.Milestone2
Environment: RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79
Metamer 4.1.0.20110910-M2 r.22701
Mojarra 2.1.2-FCS
Apache Tomcat 7.0.16
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.112 Safari/534.30
RichFaces 4.1.0.20110910-M2 r.0d4276b62c8366e0eaa1b7cd1c350d373e65ed79
Metamer 4.1.0.20110910-M2 r.22701
Mojarra 2.1.2-FCS
Apache Tomcat 7.0.16
OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux
Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0
Reporter: Jan Papousek
Open Metamer page in */faces/components/richCollapsibleSubTable/scroller.xhtml*:
*The First Problem*
- User can't move to the page 3 using the button *»*.
- Number buttons work properly.
*The Second Problem*
- Move in the *Men* section to the second page
- Move in the *Women* section to the second page.
- The first page in the section *Men* is displayed (wrong).
----
Using MyFaces everything is OK.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-11833) Label for calendar results in non-valid markup
by Pavol Pitonak (Created) (JIRA)
Label for calendar results in non-valid markup
----------------------------------------------
Key: RF-11833
URL: https://issues.jboss.org/browse/RF-11833
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.1.0.Final
Reporter: Pavol Pitonak
The code in first code snippet results in markup below which is not valid. The for attribute of the label element must refer to a form control, e.g. the actual input inside calendar (that with ID dateForm:fromDateInputDate).
{code:xml}
<h:outputLabel value="From date" for="fromDate" />
<rich:calendar id="fromDate" .../>
{code}
{code:xml}
<label for="dateForm:fromDate">From date</label>
<span class="calendar" id="dateForm:fromDate">
<span id="dateForm:fromDatePopup" style="white-space: nowrap;">
<input class="rf-cal-inp " id="dateForm:fromDateInputDate" name="dateForm:fromDateInputDate" readonly="readonly" style="vertical-align: middle; " type="text" value="Nov 19, 2011" />
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-11884) Multiple Errors with IE8/9
by Friedhelm Kuehn (JIRA)
Friedhelm Kuehn created RF-11884:
------------------------------------
Summary: Multiple Errors with IE8/9
Key: RF-11884
URL: https://issues.jboss.org/browse/RF-11884
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-panels-layout-themes, component-tables, component-tree
Environment: Windows 7 64, Tomcat 7.0.23, Mojarra 2.1.3, IE8/9 (all errors), Chrome 16.09 (one problem), PrimesFaces 2.2.1 (ChartGraphics only, problems still persist when RF is removed)
Reporter: Friedhelm Kuehn
Priority: Critical
Problem 1: Shaded TabbedPane Tabs, not changing color when tabbing. Big spacing area below tabs (height about 20 px, should be 2px).
Problem 2: Content of not-popped-up Popup-Panel is not visible, but an area is claimed on screen.
Problem 3: <a4j:commandlink> with icon: Icon is surrounded by dark border
Problem 4: No Horzontal-Scroller in ExtendDatatable (with Chrome also).
Problem 5: Use of IconCollapsed/..Expanded creates double Icons in TreeNode
Problem 6: Javascript Error in ExtendedDataTable.js
Biggest Problem: We have to deliver our application in a few weeks. Support for IE8/9 is hard customer requirement.
I have a made a documentation for each problem, but don't find a way to attach a PDF to this issue - ??
Please help !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 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 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
13 years, 9 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... 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
13 years, 9 months