[JBoss JIRA] (RF-13113) org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13113?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13113:
-------------------------------
Sprint: RichFaces 4.3.4 Sprint 1
> org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0
> -----------------------------------------------------------------------------
>
> Key: RF-13113
> URL: https://issues.jboss.org/browse/RF-13113
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: cdk
> Reporter: Tomas Repel
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Description of problem:
> org.richfaces.cdk.parent depends on older org.jboss.spec.jboss-javaee-web-6.0:3.0.1.Final-redhat-1, which is available only in jboss-eap-6.0.1-maven repository.
> This causes failure when building Seam distribution from sources. In EAP 6.1 repository there is available org.jboss.spec : jboss-javaee-web-6.0 : 3.0.2.Final-redhat-3
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13117) ExtendedDataTable Sorting resets $(window).resize Events
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13117?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13117:
-------------------------------
Sprint: RichFaces 4.3.4 Sprint 1
> ExtendedDataTable Sorting resets $(window).resize Events
> --------------------------------------------------------
>
> Key: RF-13117
> URL: https://issues.jboss.org/browse/RF-13117
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Environment: Tomcat 7
> JBoss 7.1
> Reporter: Thomas Zuberbuehler
> Priority: Critical
> Labels: regression
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Sorting removes other resize events.
> At some point following code is called:
> {code}
> // extendedDataTable.js
> deActivateResizeListener: function() {
> $(window).off(this.resizeEventName);
> }
> {code}
> Notice that this.resizeEventName is undefined.
> Before code is invoked (Chrome JavaScript console)
> {code}
> $._data(window,'events').resize
> [Object, Object]
> {code}
> After invoking
> {code}
> $._data(window,'events').resize
> TypeError: Cannot read property 'resize' of undefined
> {code}
> http://stackoverflow.com/questions/18045891/how-to-check-if-onresize-meth...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13060) Issue in initializing the list of selected items in a Picklist
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13060?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13060:
-------------------------------
Sprint: RichFaces 4.3.4 Sprint 1
> Issue in initializing the list of selected items in a Picklist
> --------------------------------------------------------------
>
> Key: RF-13060
> URL: https://issues.jboss.org/browse/RF-13060
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.2
> Reporter: Jean-Noel Colin
> Assignee: Brian Leathem
> Fix For: 4.3.4, 5-Tracking
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> A picklist uses two list of items: a list of available items and a list of selected items. If this second list has to be initialized, it has to contain the same object instances as those in the available items. So both lists can't be built from two separate DB queries, since they would refer to distinct objects, and in this case, the list of selected items would always be empty. Upon request of Brian Leathem, I have created this JIRA issue after providing a sample application that illustrates the problem.
> /Items.xhtml is the frontend
> Item is the element to be displayed in the list
> ItemBean is the managed bean that builds the available and selected lists
> ItemConverter is the converter
>
> As you see in ItemBean's constructor, depending on the way I build the selectedList, it gets displayed properly or not
>
> the project is using ivy for dependencies, and is build using ant tasks
> ant resolve-dependencies
> ant package
>
> should build the war file in /dist
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13035) Simpleapp Archetype: mobile version shows modal dialog
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13035?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13035:
-------------------------------
Sprint: RichFaces 4.3.4 Sprint 1
> Simpleapp Archetype: mobile version shows modal dialog
> -------------------------------------------------------
>
> Key: RF-13035
> URL: https://issues.jboss.org/browse/RF-13035
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 4.1.0.Final, 5.0.0.Alpha1
> Reporter: Jan Papousek
> Priority: Critical
> Labels: regression
> Fix For: 4.3.4
>
> Attachments: modal-iphone.png, richfaces-simpleapp-jee6.war, simpleapp-modal.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> When the simpleapp archetype is built with "-Dmobile-optimized=true", the welcome page shows modal dialog (see screenshot).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13038) Command button/link: attribute tabindex missing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13038?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13038:
-------------------------------
Sprint: RichFaces 4.3.4 Sprint 1
> Command button/link: attribute tabindex missing
> -----------------------------------------------
>
> Key: RF-13038
> URL: https://issues.jboss.org/browse/RF-13038
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.2, 5.0.0.Alpha1
> Reporter: Pavol Pitonak
> Priority: Minor
> Fix For: 4.3.4
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> Components command button and command link don't have attribute "tabindex", however, when it's set on the component, it's rendered correctly. This issue is similar to one for accesskey attribute (RF-12846).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months
[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13046:
-------------------------------
Sprint: RichFaces 4.3.4 Sprint 1
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 3 months