January 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12707) rich:calendar - setValue(...) method from javascript API doesn't work correctly

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12707?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-12707: ------------------------------ Environment: RichFaces 4.3.0-SNAPSHOT Metamer 4.3.0-SNAPSHOT JBoss Application Server: Weld Integration 7.1.1.Final JBoss AS 7.1.1.Final Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux Firefox 16.0 @ Linux x86_64 > rich:calendar - setValue(...) method from javascript API doesn't work correctly > ------------------------------------------------------------------------------- > > Key: RF-12707 > URL: https://issues.jboss.org/browse/RF-12707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Environment: RichFaces 4.3.0-SNAPSHOT > Metamer 4.3.0-SNAPSHOT > JBoss Application Server: Weld Integration 7.1.1.Final > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_10-b18 @ Linux > Firefox 16.0 @ Linux x86_64 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12707) rich:calendar - setValue(...) method from javascript API doesn't work correctly

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12707?page=com.atlassian.jira.plugin.s... ] Jan Papousek reopened RF-12707: ------------------------------- Brian: I've built RichFaces components with your commit (https://github.com/richfaces/components/commit/39718206d80d49118d2bee7d1d...) and Metamer and I don't think it's fixed. I don't see any update after clicking on "setValue('Oct 10, 2012 12:00')" button (page http://localhost:8080/metamer/faces/components/richCalendar/simple.xhtml). I've also tried to set @showApplyButton to false and the behaviour is the same. > rich:calendar - setValue(...) method from javascript API doesn't work correctly > ------------------------------------------------------------------------------- > > Key: RF-12707 > URL: https://issues.jboss.org/browse/RF-12707 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Brian Leathem > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12695) rich:select incorrect behavior on IE9 with many selectItems

by kevin 2 (JIRA)

[ https://issues.jboss.org/browse/RF-12695?page=com.atlassian.jira.plugin.s... ] kevin 2 updated RF-12695: ------------------------- Summary: rich:select incorrect behavior on IE9 with many selectItems (was: rich:select incorrect bevior on IE9 with many selectItems) > rich:select incorrect behavior on IE9 with many selectItems > ----------------------------------------------------------- > > Key: RF-12695 > URL: https://issues.jboss.org/browse/RF-12695 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.1.0.Final > Environment: Internet Explorer 9, Windows 7 > Reporter: kevin 2 > Assignee: Pavol Pitonak > > rich:select component has incorrect behavior on IE9 when it contains many items. > {code:html} > <rich:select id="selectId"> > <f:selectItems value="#{select.hugeList}"/> > </rich:select> > {code} > When you scroll up and down few times, try to select a value in the bottom of the list, then the scrollbar moves down indefinitely so the hovered value cannot be selected. > The problem seems to appear with a list of 100 elements or more. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12715) richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12715: --------------------------------- Here is functional test which tests behavior source re-targeting: https://github.com/richfaces/components/blob/develop/input/ui/src/test/in... > richfaces.js searchForComponentRootOrReturn doesn't recognize non-richfaces components > -------------------------------------------------------------------------------------- > > Key: RF-12715 > URL: https://issues.jboss.org/browse/RF-12715 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.0.CR1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The searchForComponentRootOrReturn function in richfaces.js was created to correct the source element of jsf events to jsf components. However the check of whether an element belongs to a component fails for non JSF components. > A concrete example of this failure can be seen when an event generates from a nested _f:ajax_ tag. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12616) Event re-targetting for correct javax.faces.source support in case where event doesn't originate on component's DOM root

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12616?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12616: --------------------------------- Here is functional test which tests this issue: https://github.com/richfaces/components/blob/develop/input/ui/src/test/in... > Event re-targetting for correct javax.faces.source support in case where event doesn't originate on component's DOM root > ------------------------------------------------------------------------------------------------------------------------ > > Key: RF-12616 > URL: https://issues.jboss.org/browse/RF-12616 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.3.0.M3 > > Attachments: autocomplete-event-retargeting.png > > > When processing events from components, attached AJAX behaviors propagates calls to: > {code} > jsf.ajax.request(source, event, options); > {code} > The ID of source element is then propagated to {{javax.faces.source}} as behavior event source. > However when a source of a event wasn't root of the component's DOM, then {{javax.faces.source}} isn't equal to {{clientId}} of component and thus behavior decoding fails. > ---- > This issue can be fixed by incorporating interceptor for {{jsf.ajax.request}}, which will re-target source to the root of the component's DOM (which has attribute{{id}} equal to {{clientId}} of component). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12712) Upgrade to Mojarra 2.1.17

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12712: --------------------------------- In that case I suggest to upgrade to Mojarra 2.1.17 and stay on Mojarra 2.1.16-jbossorg-1 - this version should be patched or upgraded in EAP. > Upgrade to Mojarra 2.1.17 > ------------------------- > > Key: RF-12712 > URL: https://issues.jboss.org/browse/RF-12712 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > While testing Metamer 4.3.0.CR1, I found some issues caused by Mojarra 2.1.16. Here is an example: > # deploy Metamer (tomcat7-mojarra classifier) to Tomcat 7 > # open http://localhost:8080/metamer-mojarra/faces/components/richDataGrid/scrol... > # set @elements attribute to 5 > # go to the second page (in data scroller) -> it resets @elements value -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12703) showcase - drag and drop - JS error with default dragIndicator

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12703?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-12703. ------------------------------ Verified in Metamer > showcase - drag and drop - JS error with default dragIndicator > -------------------------------------------------------------- > > Key: RF-12703 > URL: https://issues.jboss.org/browse/RF-12703 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-drag/drop, showcase > Affects Versions: 4.3.0.CR1 > Environment: Firefox, Chrome > JBoss AS 7.1.1.Final > Tomcat 7 > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Blocker > Labels: regression > Fix For: 4.3.0.CR1 > > Attachments: chromeDaDJSError.png, ffDaDJSError.png, visualStateOfPAge.png > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > When hovering the item over the target a JS error is thrown. The dropping functionality is *broken* too. > Please check out the attachment to see the *broken* visual state of the page once it is thrown. > There are also screenshots of the errors, both from Firefox and Chrome. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12712) Upgrade to Mojarra 2.1.17

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12712: ------------------------------------ Changing bean's scope from view to session solves problems. > Upgrade to Mojarra 2.1.17 > ------------------------- > > Key: RF-12712 > URL: https://issues.jboss.org/browse/RF-12712 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > While testing Metamer 4.3.0.CR1, I found some issues caused by Mojarra 2.1.16. Here is an example: > # deploy Metamer (tomcat7-mojarra classifier) to Tomcat 7 > # open http://localhost:8080/metamer-mojarra/faces/components/richDataGrid/scrol... > # set @elements attribute to 5 > # go to the second page (in data scroller) -> it resets @elements value -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12712) Upgrade to Mojarra 2.1.17

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12712: --------------------------------- There is change log for Mojarra {{2.1.17}}: http://java.net/jira/browse/JAVASERVERFACES/fixforversion/16239 However I can't see anything which was fixed there related to this issue other than ViewScoped fixes: http://java.net/jira/browse/JAVASERVERFACES-2656 http://java.net/jira/browse/JAVASERVERFACES-2638 http://java.net/jira/browse/JAVASERVERFACES-1706 Pavol is investigating if changing holding attributes in SessionScoped with {{2.1.16}} fixes the issue. > Upgrade to Mojarra 2.1.17 > ------------------------- > > Key: RF-12712 > URL: https://issues.jboss.org/browse/RF-12712 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > While testing Metamer 4.3.0.CR1, I found some issues caused by Mojarra 2.1.16. Here is an example: > # deploy Metamer (tomcat7-mojarra classifier) to Tomcat 7 > # open http://localhost:8080/metamer-mojarra/faces/components/richDataGrid/scrol... > # set @elements attribute to 5 > # go to the second page (in data scroller) -> it resets @elements value -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (RF-12712) Upgrade to Mojarra 2.1.17

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12712: --------------------------------- Even with fix of RF-12715, Mojarra {{2.1.16}} suffers from the the problem described in Description of this issue. Upgrade to {{2.1.17}} fixes it. > Upgrade to Mojarra 2.1.17 > ------------------------- > > Key: RF-12712 > URL: https://issues.jboss.org/browse/RF-12712 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: regression > Affects Versions: 4.3.0.CR1 > Reporter: Jan Papousek > Assignee: Lukáš Fryč > Priority: Blocker > Fix For: 4.3.0.CR1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > While testing Metamer 4.3.0.CR1, I found some issues caused by Mojarra 2.1.16. Here is an example: > # deploy Metamer (tomcat7-mojarra classifier) to Tomcat 7 > # open http://localhost:8080/metamer-mojarra/faces/components/richDataGrid/scrol... > # set @elements attribute to 5 > # go to the second page (in data scroller) -> it resets @elements value -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2013