May 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13620) Port the RichFaces 5 re-write of xml attribute to interfaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13620?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13620: ------------------------------- Original Estimate: 1 day, 4 hours (was: 3 hours) Remaining Estimate: 1 day, 4 hours (was: 3 hours) > Port the RichFaces 5 re-write of xml attribute to interfaces > ------------------------------------------------------------ > > Key: RF-13620 > URL: https://issues.jboss.org/browse/RF-13620 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 day, 4 hours > Remaining Estimate: 1 day, 4 hours > > In RichFaces 5 we re-wrote the xml attribute definitions as Interfaces to support type safety. This issue addresses backporting that fix to RichFaces 4.5. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-11741) ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely

by Ronald Brill (JIRA)

[ https://issues.jboss.org/browse/RF-11741?page=com.atlassian.jira.plugin.s... ] Ronald Brill commented on RF-11741: ----------------------------------- This should be fixed in CSSParser 0.9.14 (released yesterday). Please for the future, report your problems to the CSSParser project. > ECSS parser is too aggressive when encountering non-standard CSS properties: selector omitted entirely > ------------------------------------------------------------------------------------------------------ > > Key: RF-11741 > URL: https://issues.jboss.org/browse/RF-11741 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Affects Versions: 4.1.0.CR1 > Reporter: Karsten Wutzke > Labels: ecss, parsing, skinning > Fix For: 5-Tracking > > > When defining rules like > {code} > .shadow > { > -webkit-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > -moz-box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > box-shadow: 4px 4px 5px '#{richSkin.additionalBackgroundColor}'; > } > {code} > in an ECSS file to create skin-dependent drop shadows, RF 4 will omit the above rule entirely and no shadows will be rendered. BTW it would be better to just omit the invalid properties instead of the entire selector (box-shadow: ... alone works). > Most browsers don't support the box-shadow yet, so defining proprietary properties *must* be possible. Note, this applies to a lot more properties than the above. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-12178) Resource plugin: duplicate css atribute get twice the 1st one

by Ronald Brill (JIRA)

[ https://issues.jboss.org/browse/RF-12178?page=com.atlassian.jira.plugin.s... ] Ronald Brill commented on RF-12178: ----------------------------------- Why do you not report this kind of problems to the CSSParser project? > Resource plugin: duplicate css atribute get twice the 1st one > ------------------------------------------------------------- > > Key: RF-12178 > URL: https://issues.jboss.org/browse/RF-12178 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.2.0.Final > Reporter: Nicolas Daniels > Fix For: 5-Tracking > > > An parsed ecss containing: > background:"-moz-linear-gradient(center top, #CCCCCC, #CCCCCC 2%, #8E8E8E)" repeat scroll 0 0 transparent; > background:"-webkit-gradient(linear, left top, left bottom, from(#CCCCCC), to(#8E8E8E))"; > is resulting to: > background: "-moz-linear-gradient(center top, #CCCCCC, #CCCCCC 2%, #8E8E8E)" repeat scroll 0 0 transparent; > background: "-moz-linear-gradient(center top, #CCCCCC, #CCCCCC 2%, #8E8E8E)" repeat scroll 0 0 transparent; > The 1st background attribute is written twice while the webkit-gradient disapeared. I know I could use richfaces gradient but I want to be able to get css from anywhere and have the advantages of Richfaces resources optimization. > I tried with <compress>false</compress> or <compress>true</compress> with same result. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13627) Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13627?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13627. -------------------------------- Resolution: Done > Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute > ---------------------------------------------------------------------------------- > > Key: RF-13627 > URL: https://issues.jboss.org/browse/RF-13627 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > RF-12957 introduced the handlerClass attribute in the RichFaces CDK. RichFaces 5 components were ported to use this new attribute. The RichFaces 4.5 components should also use these attributes. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13627) Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13627?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13627: ------------------------------- Sprint: 4.5.0.Alpha3 - Sprint 2 > Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute > ---------------------------------------------------------------------------------- > > Key: RF-13627 > URL: https://issues.jboss.org/browse/RF-13627 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > RF-12957 introduced the handlerClass attribute in the RichFaces CDK. RichFaces 5 components were ported to use this new attribute. The RichFaces 4.5 components should also use these attributes. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13627) Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13627?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13627: ------------------------------------ I cannot find a github commit nor a jira issue that addresses this change in RF 5, despite the fact that the code shows it's changed. > Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute > ---------------------------------------------------------------------------------- > > Key: RF-13627 > URL: https://issues.jboss.org/browse/RF-13627 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > RF-12957 introduced the handlerClass attribute in the RichFaces CDK. RichFaces 5 components were ported to use this new attribute. The RichFaces 4.5 components should also use these attributes. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13627) Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute

by Brian Leathem (JIRA)

Brian Leathem created RF-13627: ---------------------------------- Summary: Refactor the RF 4.5 components to make use of the type-safe handlerClass attribute Key: RF-13627 URL: https://issues.jboss.org/browse/RF-13627 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Leathem Assignee: Brian Leathem Fix For: 4.5.0.Alpha3 RF-12957 introduced the handlerClass attribute in the RichFaces CDK. RichFaces 5 components were ported to use this new attribute. The RichFaces 4.5 components should also use these attributes. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13587) rich:autocomplete - suggestion box doesn't show up at all

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13587?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13587: ------------------------------- Labels: needs-qe richfaces (was: richfaces) > rich:autocomplete - suggestion box doesn't show up at all > --------------------------------------------------------- > > Key: RF-13587 > URL: https://issues.jboss.org/browse/RF-13587 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Implementation: JSF-2.2.6 mojarra, Mojarra 2.2.5 > Server: WebLogic 12.1.2.1, WildFly 8.0.0.Final > Browser: Chrome 33, Firefox 27 > Java: 1.7 > Reporter: Amit Tikoo > Labels: needs-qe, richfaces > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I am using a <rich:autocomplete> component but the suggestion box just doesn't show up. Here is a simple case I'm trying: > XHTML: > {code} > <h:form id="amit" prependId="false"> > <rich:autocomplete mode="ajax" minChars="1" autofill="true" var="station" autocompleteMethod="#{segmentationBean.autocomplete1}" > > <rich:column styleClass="sexy"> > #{station} > </rich:column> > </rich:autocomplete> > </h:form> > {code} > JAVA: > {code} > public List<String> autocomplete1(String request){ > List<String> suggestions = new ArrayList<String>(); > suggestions.add("test 1"); > suggestions.add("test 2"); > suggestions.add("test 3"); > suggestions.add("test 4"); > return suggestions; > } > {code} > This shows up in logging (using <a4j:log/>) > {code} > error[14:47:03.644]: Received 'error@malformedXML' event from > error[14:47:03.644]: [status=200] During update: javax.faces.ViewState not found > {code} > Also i can see the suggestion if i switch the mode to "Client" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13587) rich:autocomplete - suggestion box doesn't show up at all

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13587?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13587: ------------------------------------ [~ppitonak] would you please re-verify this with the latest 4.5 build? Many of the JSF 2.2 fixes from RF 5 have been backported (RF-13584). > rich:autocomplete - suggestion box doesn't show up at all > --------------------------------------------------------- > > Key: RF-13587 > URL: https://issues.jboss.org/browse/RF-13587 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.5 > Environment: Implementation: JSF-2.2.6 mojarra, Mojarra 2.2.5 > Server: WebLogic 12.1.2.1, WildFly 8.0.0.Final > Browser: Chrome 33, Firefox 27 > Java: 1.7 > Reporter: Amit Tikoo > Labels: needs-qe, richfaces > Fix For: 4.5.0.Alpha3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I am using a <rich:autocomplete> component but the suggestion box just doesn't show up. Here is a simple case I'm trying: > XHTML: > {code} > <h:form id="amit" prependId="false"> > <rich:autocomplete mode="ajax" minChars="1" autofill="true" var="station" autocompleteMethod="#{segmentationBean.autocomplete1}" > > <rich:column styleClass="sexy"> > #{station} > </rich:column> > </rich:autocomplete> > </h:form> > {code} > JAVA: > {code} > public List<String> autocomplete1(String request){ > List<String> suggestions = new ArrayList<String>(); > suggestions.add("test 1"); > suggestions.add("test 2"); > suggestions.add("test 3"); > suggestions.add("test 4"); > return suggestions; > } > {code} > This shows up in logging (using <a4j:log/>) > {code} > error[14:47:03.644]: Received 'error@malformedXML' event from > error[14:47:03.644]: [status=200] During update: javax.faces.ViewState not found > {code} > Also i can see the suggestion if i switch the mode to "Client" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13612) Document styling attributes for rich:dataTable

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13612?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13612: ------------------------------- Assignee: Michal Petrov > Document styling attributes for rich:dataTable > ---------------------------------------------- > > Key: RF-13612 > URL: https://issues.jboss.org/browse/RF-13612 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-tables, doc > Affects Versions: 4.3.6 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha3 > > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > There are several attributes that can be assigned to a dataTable such as {{headerCellClass}} or {{firstColumnFooterClass}} (see [AbstractTableRenderer|https://github.com/richfaces4/components/blob/maste...]). The renderer is set to process them but they are not documented. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 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 May 2014