October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13241) ECSS: Not possible to define one property multiple times

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13241?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-13241: ---------------------------------- Assignee: Brian Leathem (was: Pavol Pitonak) > ECSS: Not possible to define one property multiple times > -------------------------------------------------------- > > Key: RF-13241 > URL: https://issues.jboss.org/browse/RF-13241 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > all environments > Reporter: Pavol Pitonak > Assignee: Brian Leathem > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/skinning/ecss.xhtml > # open rf13241.ecss in developer tools > expected: > {code} > html { > background: red; > background: -webkit-linear-gradient(bottom, red 0%, white 100%); > } > {code} > was: > {code} > html { > background: red; > background: red; > } > {code} -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12802: --------------------------------- Juraj, generally the API looks great from my point of view. I would like to see information hiding in form of providing interfaces and their implementation. @ImplementedBy(RichFacesCalendar.class) public interface Calendar {} Could you please list additional features which we haven't discussed before?: e.g.: * ability to choose between JS API and interactive manipulation with a widget (setting/obtaining value) * advanced interactions Have you implemented automatic detection of the widget in the page? E.g. rich:calendar can be find by ".rf-cal" in case there is just one instance in the page (or in the context of user-defined fragment). > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13241) ECSS: Not possible to define one property multiple times

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13241?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13241: ------------------------------------ According to CSS validator, it's perfectly valid. One of use-cases is the one in this issue when you need to specify some non-standard property for all browsers, such as gradients. You need to do following: {code} html { background: linear-gradient(bottom, red 0%, white 100%); background: -webkit-linear-gradient(bottom, red} 0%, white 100%); background: -o-linear-gradient(bottom, red 0%, white 100%); background: -moz-linear-gradient(bottom, red 0%, white 100%); background: -ms-linear-gradient(bottom, red 0%, white 100%); background-attachment: fixed; } {code} Event this CSS is valid: {code} html { background: red; background: blue; } {code} > ECSS: Not possible to define one property multiple times > -------------------------------------------------------- > > Key: RF-13241 > URL: https://issues.jboss.org/browse/RF-13241 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > all environments > Reporter: Pavol Pitonak > Assignee: Pavol Pitonak > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/skinning/ecss.xhtml > # open rf13241.ecss in developer tools > expected: > {code} > html { > background: red; > background: -webkit-linear-gradient(bottom, red 0%, white 100%); > } > {code} > was: > {code} > html { > background: red; > background: red; > } > {code} -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13224) RF 4.5 build fails to render optimized resources

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13224?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13224: --------------------------------- Afaik the mime-types should be loaded from [mime.types|https://github.com/richfaces/richfaces/blob/master/build/build...] file, but it's not seem to be used in the project. It wasn't used in 4.3 branch either, so I'm not sure whether it's loaded dynamically by any of associated tools in Resource Optimizer toolchain. > RF 4.5 build fails to render optimized resources > ------------------------------------------------ > > Key: RF-13224 > URL: https://issues.jboss.org/browse/RF-13224 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.5.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha1 > > > -I believe it's caused by:- > https://github.com/richfaces/richfaces/commit/46b03d226ae420bcbc8abd7f79e... > This is no longer an issue. > Current issues: > * packed.js is not generated, .js files do not seem to be handled by the plugin at all > * some images are not rendered, e.g. gradientA.png (used in several components for background), it is not defined in resource-mappings.properties -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12822) Create fun tests for JSF AJAX submission and JavaScriptService callbacks

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12822?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12822: --------------------------------- Thanks for the test implementation, Juraj, good job. > Create fun tests for JSF AJAX submission and JavaScriptService callbacks > ------------------------------------------------------------------------ > > Key: RF-12822 > URL: https://issues.jboss.org/browse/RF-12822 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 4.3.0.Final > Reporter: Lukáš Fryč > Assignee: Juraj Húska > Fix For: 5.0.0.Alpha2 > > -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Juraj Húska edited comment on RF-12802 at 10/4/13 3:17 AM: ----------------------------------------------------------- {{TheFirstAccordion}} is an inner class of that very same showcase class. That should be the way an user of page fragments for switchable components should go: # Define concrete Page Objects for all of his accordion panels - e.g. {{TheFirstAccordion}} # Page Fragment for Accordion will enable him to switch between the panels # Also it enables initializing that page object for him, the user will be able to get the content, see {{accordion.switchTo("First accordion").getContent(TheFirstAccordion.class);}} was (Author: jhuska): {{TheFirstAccordion}} is an inner class of that very same showcase class. That should be the way an user of page fragments for switchable components should go: # Define concrete Page Objects for all of his accordion panels - e.g. {{TheFirstAccordion}} # Page Fragment for Accordion will enable him to switch between the panels # Also enable to initialize that page object for him, the user will be able to get the content, see {{accordion.switchTo("First accordion").getContent(TheFirstAccordion.class);}} > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

by Juraj Húska (JIRA)

[ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s... ] Juraj Húska commented on RF-12802: ---------------------------------- {{TheFirstAccordion}} is an inner class of that very same showcase class. That should be the way an user of page fragments for switchable components should go: # Define concrete Page Objects for all of his accordion panels - e.g. {{TheFirstAccordion}} # Page Fragment for Accordion will enable him to switch between the panels # Also enable to initialize that page object for him, the user will be able to get the content, see {{accordion.switchTo("First accordion").getContent(TheFirstAccordion.class);}} > Move page fragments from repository qa to richfaces5 > ---------------------------------------------------- > > Key: RF-12802 > URL: https://issues.jboss.org/browse/RF-12802 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha2 > > > As discussed on community meeting on Feb 12, we should move page fragments for RichFaces components to richfaces5 repository so that they are distributed with framework. > We should find out how to prepare them so that they are easy to use for community members. RichFaces QE/dev need to test internals of components, community members will probably test only high-level functionality of components. One possible solution would be to create package "internal" in which there would be page fragments extending those from "public" package. QE team would then use "internal" implementations. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-12891) Datatable with ExtendedDataModel ajax call

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12891?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12891: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 (was: RichFaces 4.3.4 Sprint 1, 5.0.0.Alpha2 - Sprint 2) > Datatable with ExtendedDataModel ajax call > ------------------------------------------ > > Key: RF-12891 > URL: https://issues.jboss.org/browse/RF-12891 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-tables > Affects Versions: 4.3.1 > Environment: apache-tomcat-7.0.34, servlet-weld 1.1.11. > Reporter: tehackio teha > Labels: ExtendedDataModel, UIDataAdaptor, a4j:commandLink, datatable > Fix For: 5-Tracking > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > If one ajax call inside column of datatable(org.ajax4jsf.model.ExtendedDataModel) to render outside, method walk is called many times; > On org.richfaces.component.UIDataAdaptor.requiresRowIteration(VisitContext context), context.getFacesContext().getAttributes().get("javax.faces.visit.SKIP_ITERATION") returns "null", therefore "false". -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13052) popupPanel: @visualOptions isn't fully implemented

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13052?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13052: ------------------------------- Sprint: RichFaces 4.3.4 Sprint 1 (was: RichFaces 4.3.4 Sprint 1, 5.0.0.Alpha2 - Sprint 2) > popupPanel: @visualOptions isn't fully implemented > -------------------------------------------------- > > Key: RF-13052 > URL: https://issues.jboss.org/browse/RF-13052 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Jiří Štefek > Fix For: 5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Setting @visualOptions doesn't work. Tried both settings from https://issues.jboss.org/browse/RF-2464 or https://issues.jboss.org/browse/RF-5239 > e.g.: 'left:1px' > OR > Is this attribute a leftover from older versions of RF (RF-3) and was replaced by attributes @*width, @*height and @style* ? > ALSO UPDATE VDL-DOC in both cases. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13168) 3rd party JSF component disappears on RichFaces ajax refresh

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13168: ------------------------------- Sprint: 5.0.0.Alpha2 - Sprint 3 > 3rd party JSF component disappears on RichFaces ajax refresh > ------------------------------------------------------------ > > Key: RF-13168 > URL: https://issues.jboss.org/browse/RF-13168 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: compatibility, component-a4j-core > Reporter: Frank Langelage > Assignee: Brian Leathem > Labels: interop, jsf22 > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable. > This does not work with WildFly build from current sources. > Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow. > I'll attach a small project showing the problem. > The mojarra datatable works fine, is refreshed every 10 seconds. > The openfaces datatable below disappears on first refresh. -- 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

12 years, 3 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 October 2013