January 2013 - richfaces-issues - Jboss List Archives

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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12703?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12703: ---------------------------- Assignee: (was: Lukáš Fryč) > 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 > Priority: Blocker > Labels: regression > Attachments: chromeDaDJSError.png, ffDaDJSError.png, visualStateOfPAge.png > > > 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

11 years, 10 months

1
0
0 / 0

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

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12703?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč reassigned RF-12703: ------------------------------- Assignee: Lukáš Fryč > 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 > Attachments: chromeDaDJSError.png, ffDaDJSError.png, visualStateOfPAge.png > > > 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12708) rich:jQuery: wront VDL documentation of selector attribute

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12708?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12708: ---------------------------- Fix Version/s: (was: 4.3.0.CR1) > rich:jQuery: wront VDL documentation of selector attribute > ---------------------------------------------------------- > > Key: RF-12708 > URL: https://issues.jboss.org/browse/RF-12708 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: doc > Reporter: Lukáš Fryč > Labels: vdl > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > {quote}Selector for query. The "selector" attribute uses defined by w3c consortium syntax for CSS rule selector with some jQuery extensions.{quote} > should be similar to rich:hotkey docs: > {quote}The CSS selector of the DOM root from which key events should be handled. When no value provided, events are handled for whole document. ID selectors starting with hash sign (#) will be expanded from componentId to clientId form. (e.g. #component is expanded to #form:component in case that component is nested in form){quote} -- 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, 10 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-12712: ------------------------------ Description: 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 was: While testing Metamer 4.3.0.CR1, I found some isseue 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 > 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 > Priority: Blocker > > 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

11 years, 10 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: ------------------------------------ 2029 out of 5192 tests failed on Tomcat 7. Most of these failures can be fixed by Mojarra upgrade. [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-release-met... > 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 > Priority: Blocker > > While testing Metamer 4.3.0.CR1, I found some isseue 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

11 years, 10 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-12712: ------------------------------ Description: While testing Metamer 4.3.0.CR1, I found some isseue 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 was: While testing Metamer 4.3.0.CR1, I found some isseue caused by Mojarra 2.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 > 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 > Priority: Blocker > > While testing Metamer 4.3.0.CR1, I found some isseue 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

11 years, 10 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 updated RF-12712: ------------------------------- Summary: Upgrade to Mojarra 2.1.17 (was: Upgrade to Mojarra 2.17) > 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 > Priority: Blocker > > While testing Metamer 4.3.0.CR1, I found some isseue caused by Mojarra 2.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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12714) Showcase and rich:dataTable: sorting in Arrangable demo doesn't work

by Jan Papousek (JIRA)

Jan Papousek created RF-12714: --------------------------------- Summary: Showcase and rich:dataTable: sorting in Arrangable demo doesn't work Key: RF-12714 URL: https://issues.jboss.org/browse/RF-12714 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: regression Affects Versions: 4.3.0.CR1 Environment: JBoss AS 7.1.1, Java 1.7.0_10, Firefox 16.0.2 Reporter: Jan Papousek -- 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, 10 months

1
0
0 / 0

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

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12712?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-12712: ------------------------------- Priority: Blocker (was: Major) > Upgrade to Mojarra 2.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 > Priority: Blocker > > While testing Metamer 4.3.0.CR1, I found some isseue caused by Mojarra 2.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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (RF-12713) Listeners don't work inside panels

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-12713: ---------------------------------- Summary: Listeners don't work inside panels Key: RF-12713 URL: https://issues.jboss.org/browse/RF-12713 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core, regression Affects Versions: 4.3.0.CR1 Environment: RichFaces 4.3.0.CR1 Metamer 4.3.0.20130109-CR1 Mojarra 2.0.7 JBoss AS 7.1.1 Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux Chrome 23.0.1271.97 @ Linux x86_64, Firefox 17 Reporter: Pavol Pitonak Priority: Blocker # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jActionListener/all.xhtm... # click "Invoke listener by binding" result: * message "Bound listener called" should be displayed but nothing happens * it is reproducible inside these components: accordion, collapsible subtable, extended data table, collapsible panel, tab panel and popup panel -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2013