May 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8261) Add support to automatically scroll to the first field containing an error after user submits a form and validation fails?

by Frank (JIRA)

Add support to automatically scroll to the first field containing an error after user submits a form and validation fails? -------------------------------------------------------------------------------------------------------------------------- Key: RF-8261 URL: https://jira.jboss.org/jira/browse/RF-8261 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component Affects Versions: 3.3.2.SR1 Environment: Richfaces (3.3.2.SR1), Spring webflow (2.0.8), Hibernate Validator (4.0.2), ........... Reporter: Frank Hello, here's the context, I have a form which has enough fields to produce vertical scrolling. I'm using Hibernate Validator (4.0.x) to validate my form fields through rich:ajaxValidator. So, has the title says, I would like the page to scroll up 'automatically' to the first validation error of the form, after the user tries to submit the form with the save button (a4j:commandButton), and the form contains one or more errors (coming from JSF Validation phase...). So, big picture of feature request: On form-submit, if errors, automatic scroll to first form error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (RF-10837) VDL-DOC: update dependency version in the ui/dist pom

by Anton Belevich (JIRA)

VDL-DOC: update dependency version in the ui/dist pom ----------------------------------------------------- Key: RF-10837 URL: https://issues.jboss.org/browse/RF-10837 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Reporter: Anton Belevich Assignee: Jay Balunas update http://anonsvn.jboss.org/repos/richfaces/branches/4.0.X/ui/dist/richfaces... with faces-shade-transformers.version and faces-vdl-documentation version of released plugins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (RF-10549) CDK: attributes are not read from super class

by Nick Belaevski (JIRA)

CDK: attributes are not read from super class --------------------------------------------- Key: RF-10549 URL: https://issues.jboss.org/browse/RF-10549 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: cdk Reporter: Nick Belaevski I've added @Attribute annotation to UIDataAdaptor#getRowKeyConverter() method and expect this attribute to be available in taglib.xml for all iteration components, however that did not happen. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (RF-10973) Skinning: it's not possible to redefine some classes

by Pavol Pitonak (JIRA)

Skinning: it's not possible to redefine some classes ---------------------------------------------------- Key: RF-10973 URL: https://issues.jboss.org/browse/RF-10973 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: skinning Affects Versions: 4.0.0.Final Environment: Chrome 11.0.696.57 @ Linux i686 Reporter: Pavol Pitonak There are some differences among browsers in handling rewritten CSS classes, e.g. define following class for rich:panel: {code} .rf-p-b { padding: 0px; background-color: green; } {code} result: in Firefox 3.6.x, panel's body has padding 0 and green background, in Chrome 11 background is green but panel has default padding (10px) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (RF-10979) richfaces-showcase: tree demo uses application scoped bean

by Ilya Shaikovsky (JIRA)

richfaces-showcase: tree demo uses application scoped bean ---------------------------------------------------------- Key: RF-10979 URL: https://issues.jboss.org/browse/RF-10979 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky So if you will play with selection at richfaces-showcase for some time you will see that different result came as there are other users which uses the same demo page in the same time :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (RF-10988) richfaces-showcase: bad description at standard skinning page.

by Ilya Shaikovsky (JIRA)

richfaces-showcase: bad description at standard skinning page. -------------------------------------------------------------- Key: RF-10988 URL: https://issues.jboss.org/browse/RF-10988 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: examples Affects Versions: 4.0.0.Final Reporter: Ilya Shaikovsky 1) there are no levels anymore 2) parameters not specified so need to browse documentation additionally. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-10923) rich:hotKey it is not applicable for mobile devices

by Juraj Huska (JIRA)

rich:hotKey it is not applicable for mobile devices --------------------------------------------------- Key: RF-10923 URL: https://issues.jboss.org/browse/RF-10923 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Environment: Demo-application - richfaces-demo-3.3.1.SP3-jee5 container - EAP 5.1 with Jboss AS 5 mobile devices - iPhone 4 - OS version iOS 4.2.1 - browser Safari iPad1 - OS version iOS 4.2.1 - browser Safari Nexus S - OS Android 2.3.2 Reporter: Juraj Huska It is not applicable on devices with touch screen. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-10887) rich:select setValue(value) javascript api does not allow setting an empty value.

by Justin Wyer (JIRA)

rich:select setValue(value) javascript api does not allow setting an empty value. --------------------------------------------------------------------------------- Key: RF-10887 URL: https://issues.jboss.org/browse/RF-10887 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Final Reporter: Justin Wyer You can only set the value of the list to a valid entry in the list, been able to clear the value of the list would be useful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-9127) rich:messages produce content outside <html> tags on AJAX refresh

by StÃ©phane Daviet (JIRA)

rich:messages produce content outside <html> tags on AJAX refresh ----------------------------------------------------------------- Key: RF-9127 URL: https://jira.jboss.org/browse/RF-9127 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component Affects Versions: 3.3.3.Final, 3.3.2.SR1 Environment: Firefox 3.6.6 and IE7 on Windows Vista and XP Suspected not being platform specific Reporter: StÃ©phane Daviet Priority: Minor When refreshing after the response of an AJAX request, the rich:messages component produce unexpected content before the opening <html> tag. The combination of rich:messages with another component on the page triggering AJAX request (rich:ajaxValidator for instance) could produce this behavior. Each new request response add a new line before the first opening <html> tag. This behavior is reproductible on rich:messages page of the Live Demo and has also been reproduced on a simple custom page. Unexpected content spotted with Firebug: <dl id="j_id355:j_id356" class="rich-messages" style="display: none;"></dl> <dl id="j_id355:j_id356" class="rich-messages"></dl> <dl id="j_id355:j_id356" class="rich-messages"></dl> <dl id="j_id355:j_id356" class="rich-messages"></dl> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-10206) Add WAI-ARIA support to components

by Brent Yarger (JIRA)

Add WAI-ARIA support to components ---------------------------------- Key: RF-10206 URL: https://issues.jboss.org/browse/RF-10206 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: accessibility Affects Versions: 3.3.3.Final Reporter: Brent Yarger WAI-ARIA support would be a nice feature to have to improve accessibility of Richfaces. Both keyboard accessibility and screen reader accessibility could be significantly improved by adding WAI-ARIA support -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2011