October 2010 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-8943) SyntaxHighlighter JavaScript-based component

by Nick Belaevski (JIRA)

SyntaxHighlighter JavaScript-based component -------------------------------------------- Key: RF-8943 URL: https://jira.jboss.org/browse/RF-8943 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: Future_4.X See related forum thread -- 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, 9 months

2
2
0 / 0

[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, 9 months

3
2
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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (RF-7787) Process JSF client-behavior information and generate Behavior and Behavior-renderer classes.

by Alexander Smirnov (JIRA)

Process JSF client-behavior information and generate Behavior and Behavior-renderer classes. -------------------------------------------------------------------------------------------- Key: RF-7787 URL: https://jira.jboss.org/jira/browse/RF-7787 Project: RichFaces Issue Type: Sub-task Reporter: Alexander Smirnov Assignee: Alexander Smirnov Fix For: 4.0.0.ALPHA2 1. Develop behavior-related annotations. 2. Create annotation processor for behavior classes. 3. Parse behavior section of the faces-config.xml 4. Write behavior classes. -- 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
5
0 / 0

[JBoss JIRA] Created: (RF-8760) All <url> elements of <scm> should be updated correctly for fisheye links

by Jay Balunas (JIRA)

All <url> elements of <scm> should be updated correctly for fisheye links ------------------------------------------------------------------------- Key: RF-8760 URL: https://jira.jboss.org/browse/RF-8760 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build Reporter: Jay Balunas Fix For: 4.0.0.Milestone1 most point to richfaces/ only -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-9068) Component archetypes must be updated based on the new build refactor for M2

by Jay Balunas (JIRA)

Component archetypes must be updated based on the new build refactor for M2 --------------------------------------------------------------------------- Key: RF-9068 URL: https://jira.jboss.org/browse/RF-9068 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build, CDK Reporter: Jay Balunas Assignee: Alex Kolonitsky Priority: Critical Fix For: 4.0.0.Milestone2 Please look into this as you are also updating the other archetype issue for M2. Components should not have boms, and other changes. Please compare with other areas. -- 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, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-9153) CSV export component of rich:dataTable/rich:extendedDataTable

by Michael Schmidt (JIRA)

CSV export component of rich:dataTable/rich:extendedDataTable ------------------------------------------------------------- Key: RF-9153 URL: https://jira.jboss.org/browse/RF-9153 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-tables Affects Versions: 4.0.0.Final, Future_4.X Reporter: Michael Schmidt Fix For: 4.0.0.Final, Future_4.X A component which allows the CSV export/download of any given rich:dataTable/rich:extendedDataTable. Especially in business applications there often is the requirement to export any data into excel. A generic way to do it would eliminate a lot of required work for Richfaces users. -- 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, 10 months

5
6
0 / 0

[JBoss JIRA] Created: (RF-7807) a4j:keepAlive: incompatibility with bound components

by Nick Belaevski (JIRA)

a4j:keepAlive: incompatibility with bound components ---------------------------------------------------- Key: RF-7807 URL: https://jira.jboss.org/jira/browse/RF-7807 Project: RichFaces Issue Type: Bug Reporter: Nick Belaevski Please take a look at linked forum thread -- 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

2
6
0 / 0

[JBoss JIRA] Created: (RF-6658) panelMenu components: provide selectedItemClass and selectedGroupClass attributes

by Ilya Shaikovsky (JIRA)

panelMenu components: provide selectedItemClass and selectedGroupClass attributes --------------------------------------------------------------------------------- Key: RF-6658 URL: https://jira.jboss.org/jira/browse/RF-6658 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski the same as for disable and hover states. -- 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

4
7
0 / 0

[JBoss JIRA] Created: (RF-2023) set Locale/DatePattern for Calendar globally (eg. in a web.xml context-param or something)

by Richard Kennard (JIRA)

set Locale/DatePattern for Calendar globally (eg. in a web.xml context-param or something) ------------------------------------------------------------------------------------------ Key: RF-2023 URL: http://jira.jboss.com/jira/browse/RF-2023 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.1.3 Environment: All Reporter: Richard Kennard Priority: Optional It would be great if you could set the Locale/DatePattern for the Calendar control globally (eg. in a web.xml context-param or something), rather than having to put... <rich:calendar locale="..." datePattern="..."/> ...every time you use the tag? I know you can currently use an EL expression, like... <rich:calendar locale="#{globals.locale}" datePattern="#{globals.pattern}"/> ...but that requires extra plumbing on the part of the developer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues October 2010