August 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13770) Output panel: onkeydown, onkeyup and onkeypress don't work

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13770?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-13770. ------------------------------ Thanks for fast fix. Verified. > Output panel: onkeydown, onkeyup and onkeypress don't work > ---------------------------------------------------------- > > Key: RF-13770 > URL: https://issues.jboss.org/browse/RF-13770 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Priority: Critical > > Attributes onkeypress, onkeydown and onkeyup of a:outputPanel stopped working. Affects all browsers - it's not rendered in html. > It's a *regression* since it worked fine in 4.5.0.Alpha3. > It's questionable how useful these attributes are since it's not possible to fire these events in common ways, only using JavaScript/Selenium. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13770) Output panel: onkeydown, onkeyup and onkeypress don't work

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13770?page=com.atlassian.jira.plugin.s... ] Michal Petrov resolved RF-13770. -------------------------------- Assignee: Michal Petrov Resolution: Done The EventsKeyProps interface had badly defined event names, previously the components were defining their own attributes and overriding it which I removed. (RF-13686) > Output panel: onkeydown, onkeyup and onkeypress don't work > ---------------------------------------------------------- > > Key: RF-13770 > URL: https://issues.jboss.org/browse/RF-13770 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output, regression > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavol Pitonak > Assignee: Michal Petrov > Priority: Critical > > Attributes onkeypress, onkeydown and onkeyup of a:outputPanel stopped working. Affects all browsers - it's not rendered in html. > It's a *regression* since it worked fine in 4.5.0.Alpha3. > It's questionable how useful these attributes are since it's not possible to fire these events in common ways, only using JavaScript/Selenium. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13770) Output panel: onkeydown, onkeyup and onkeypress don't work

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-13770: ---------------------------------- Summary: Output panel: onkeydown, onkeyup and onkeypress don't work Key: RF-13770 URL: https://issues.jboss.org/browse/RF-13770 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output, regression Affects Versions: 4.5.0.Alpha3 Reporter: Pavol Pitonak Priority: Critical Attributes onkeypress, onkeydown and onkeyup of a:outputPanel stopped working. Affects all browsers - it's not rendered in html. It's a *regression* since it worked fine in 4.5.0.Alpha3. It's questionable how useful these attributes are since it's not possible to fire these events in common ways, only using JavaScript/Selenium. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13758) RF 4.5 with MyFaces, CSS not loaded

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13758?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13758: --------------------------------- I believe the correct fix here is make our implementation comply to MyFaces implementation if that's technically feasible. ---- [~michpetrov] do you remember what are additional checks that make MyFaces pass our criteria? Have you verified that Resource Optimization works as expected for aggregated RichFaces JS/CSS? > RF 4.5 with MyFaces, CSS not loaded > ----------------------------------- > > Key: RF-13758 > URL: https://issues.jboss.org/browse/RF-13758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Matej Novotny > Assignee: Michal Petrov > Priority: Critical > Labels: myfaces, needs-qe > Fix For: 4.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When you use MyFaces as JSF implementation, RF fail to get CSS files hence the components are displayed as plain text. > I tried this (among others) with simpleapp which I modified by adding a simple rich:panel. With Mojarra the css for panel was received and panel was displayed correctly. Then I modified pom.xml to use MyFaces. The app can be deployed but the panel is just a plain text and page contains no css for styling. > This can be reproduced with Metamer/simpleapp/showcase. > Please see steps to reproduce for reproducers with Metamer and simpleapp. > Showcase reproducer is more complicated due to RF-13757. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13758) RF 4.5 with MyFaces, CSS not loaded

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13758?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13758: --------------------------------- {{ResourceMapping}} is an generalization of {{static-resource-mapping.properties}} configuration file from RichFaces 4.3. If we remove {{org.richfaces}} from the list, it means most of RichFaces resource requests won't be directed to {{ResourceServlet}} but served by default JSF servlet, it means resource links may stop to work. The only RichFaces 4.3 component I'm aware of that would be affected is {{rich:editor}}, but that has resources placed in {{org.richfaces.ckeditor}} resource library. > RF 4.5 with MyFaces, CSS not loaded > ----------------------------------- > > Key: RF-13758 > URL: https://issues.jboss.org/browse/RF-13758 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Matej Novotny > Assignee: Michal Petrov > Priority: Critical > Labels: myfaces, needs-qe > Fix For: 4.5.0.Beta1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > When you use MyFaces as JSF implementation, RF fail to get CSS files hence the components are displayed as plain text. > I tried this (among others) with simpleapp which I modified by adding a simple rich:panel. With Mojarra the css for panel was received and panel was displayed correctly. Then I modified pom.xml to use MyFaces. The app can be deployed but the panel is just a plain text and page contains no css for styling. > This can be reproduced with Metamer/simpleapp/showcase. > Please see steps to reproduce for reproducers with Metamer and simpleapp. > Showcase reproducer is more complicated due to RF-13757. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13761) Upgrade jQuery to 1.11.1+

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13761?page=com.atlassian.jira.plugin.s... ] Michal Petrov reassigned RF-13761: ---------------------------------- Assignee: Michal Petrov > Upgrade jQuery to 1.11.1+ > ------------------------- > > Key: RF-13761 > URL: https://issues.jboss.org/browse/RF-13761 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha3 > Reporter: Cody Lerum > Assignee: Michal Petrov > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > RF should include a more recent version of jQuery for compatibility reasons. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11174) [rich:extendedDataTable] attribute "width" of columns should support percent values instead of only accepting px values

by Dmitry Olyenyov (JIRA)

[ https://issues.jboss.org/browse/RF-11174?page=com.atlassian.jira.plugin.s... ] Dmitry Olyenyov updated RF-11174: --------------------------------- Attachment: width-fix-updated.diff Sorry, updated version. Forgot to alter getColumnWidth method > [rich:extendedDataTable] attribute "width" of columns should support percent values instead of only accepting px values > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-11174 > URL: https://issues.jboss.org/browse/RF-11174 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0.0.Final > Reporter: Rene O > Fix For: 5-Tracking > > Attachments: width-fix-updated.diff, width-fix.diff > > > Currently you can only define the width of a column inside the rich:extendedDataTable like this: > <rich:column width="120px" ... > But it should also be possible to define it like this: > <rich:column width="30%" ... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-11174) [rich:extendedDataTable] attribute "width" of columns should support percent values instead of only accepting px values

by Dmitry Olyenyov (JIRA)

[ https://issues.jboss.org/browse/RF-11174?page=com.atlassian.jira.plugin.s... ] Dmitry Olyenyov updated RF-11174: --------------------------------- Attachment: width-fix.diff I think I fixed this issue. Here is the patch. It adds class for all TDs in the all tables: header, body, footer. Works for me, at least. > [rich:extendedDataTable] attribute "width" of columns should support percent values instead of only accepting px values > ----------------------------------------------------------------------------------------------------------------------- > > Key: RF-11174 > URL: https://issues.jboss.org/browse/RF-11174 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0.0.Final > Reporter: Rene O > Fix For: 5-Tracking > > Attachments: width-fix.diff > > > Currently you can only define the width of a column inside the rich:extendedDataTable like this: > <rich:column width="120px" ... > But it should also be possible to define it like this: > <rich:column width="30%" ... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13759: ------------------------------- Labels: needs-qe (was: ) > Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0 > ----------------------------------------------------------------------------- > > Key: RF-13759 > URL: https://issues.jboss.org/browse/RF-13759 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk, component, core > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavel Slegr > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > both cdk and richfaces projects use different jboss-parent versions (9,12) > EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11. > Please unify into jboss-parent 11 > NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo > These classes use deprecated api such as > {code} > @parameter expression="${executedProject}"" > {code} > which doesn't work with maven-plugin-plugin 3.1 and leads into > {code} > [WARNING] The syntax > [WARNING] @parameter expression="${property}" > [WARNING] is deprecated, please use > [WARNING] @parameter property="property" > [WARNING] instead. > {code} > Some other additional changes may be also needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RF-13759) Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13759?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13759. -------------------------------- Resolution: Done I ended up changing the _maven-plugin-plugin_ javadoc doclet tags in the maven cdk plugin to annotations in order to get the update to work. After making the changes both the cdk and richfaces compile and tests pass. RichFaces smoke tests also pass. > Unify jboss-parent between richfaces and cdk projects & allign with EAP-6.3.0 > ----------------------------------------------------------------------------- > > Key: RF-13759 > URL: https://issues.jboss.org/browse/RF-13759 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk, component, core > Affects Versions: 4.5.0.Alpha3 > Reporter: Pavel Slegr > Assignee: Brian Leathem > Fix For: 4.5.0.Beta1 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > both cdk and richfaces projects use different jboss-parent versions (9,12) > EAP-6.3.0 which will be underlying base for RF\-4.5.0 uses as latest supported jboss-parent version 11. > Please unify into jboss-parent 11 > NOTE: updating cdk version into jboss-parent 11, will need a maintenance (update for deprecated code) in cdk/maven-plugin/src/main/java/org/richfaces/builder/mojo > These classes use deprecated api such as > {code} > @parameter expression="${executedProject}"" > {code} > which doesn't work with maven-plugin-plugin 3.1 and leads into > {code} > [WARNING] The syntax > [WARNING] @parameter expression="${property}" > [WARNING] is deprecated, please use > [WARNING] @parameter property="property" > [WARNING] instead. > {code} > Some other additional changes may be also needed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 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 August 2014