August 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-4464) inputNumberSlider: component incorrect behavior inside rich:tabPanel during swith between tabs.

by Mikhail Vitenkov (JIRA)

inputNumberSlider: component incorrect behavior inside rich:tabPanel during swith between tabs. ----------------------------------------------------------------------------------------------- Key: RF-4464 URL: https://jira.jboss.org/jira/browse/RF-4464 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.1, Safari 3.1, Opera 9.52(3.3.0) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski #1. Add following code on the page(rich:tabPanel with two tabs, which contained inputNumberSlider component): <h:form> <rich:tabPanel switchType="client"> <rich:tab label="First"> Here is tab #1 <rich:inputNumberSlider value="10" /> </rich:tab> <rich:tab label="Second"> Here is tab #2 <rich:inputNumberSlider value="20" /> </rich:tab> </rich:tabPanel> <h:commandButton action="submit" value="Submit" /> </h:form> #2. Navigate to the page. #3. Go to "Second" tab. #4. Set pointer to max(100) value. #5. Return to the "First" tab & click "Submit" button(see #1) #6. Navigate to "Second" tab again & verify position of slider's pointer. #8. Enter '80' in component's input & press 'Enter'. #9. Turn back to "First" tab & press "Submit". Actual behavior: #6: Pointer is at the right border of component's input. See attachment. #9: Pointer moves to left. Screenshot described #6 issue is attached. -- 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

13 years, 11 months

6
15
0 / 0

[JBoss JIRA] Created: (RF-5379) Calendar: 'getData' JS API method is not implemented ot does not work

by Andrei Markavtsov (JIRA)

Calendar: 'getData' JS API method is not implemented ot does not work --------------------------------------------------------------------- Key: RF-5379 URL: https://jira.jboss.org/jira/browse/RF-5379 Project: RichFaces Issue Type: Bug Affects Versions: 3.0.0 Environment: RF 3.0.0.SNAPSHOT Reporter: Andrei Markavtsov Assignee: Nick Belaevski The method was described in developer guide : p. 6.27.6. JavaScript API. Currently, $('calendarId').component.getData(date) method causes JS 'is not a function' 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

13 years, 11 months

5
9
0 / 0

[JBoss JIRA] Created: (RF-2968) Deprecate MethodBinding in favor to MethodExpression

by Nick Belaevski (JIRA)

Deprecate MethodBinding in favor to MethodExpression ---------------------------------------------------- Key: RF-2968 URL: http://jira.jboss.com/jira/browse/RF-2968 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Nick Belaevski Assigned To: Maksim Kaszynski Fix For: 3.2.1 Deprecate MethodBinding/ValueBinding properties in favor to MethodExpression/ValueExpression -- 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

13 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (RF-7339) Cell grouping on RF Grid component

by Svetlana mukhina (JIRA)

Cell grouping on RF Grid component ------------------------------------ Key: RF-7339 URL: https://jira.jboss.org/jira/browse/RF-7339 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.3.1 Reporter: Svetlana mukhina Assignee: Alexander Tsebro Fix For: 3.3.2.CR1 Describe a new feature in the dev guide -- 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

13 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (RF-4275) Java docs language

by Svetlana mukhina (JIRA)

Java docs language ------------------- Key: RF-4275 URL: https://jira.jboss.org/jira/browse/RF-4275 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.1 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 3.2.2 Check English in Java Docs -- 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

13 years, 11 months

5
13
0 / 0

[JBoss JIRA] Created: (RF-7611) fix default column width assigned to extendedDataTable

by Prabhat Jha (JIRA)

fix default column width assigned to extendedDataTable ------------------------------------------------------ Key: RF-7611 URL: https://jira.jboss.org/jira/browse/RF-7611 Project: RichFaces Issue Type: Bug Components: component-tables Affects Versions: 3.3.1 Reporter: Prabhat Jha Fix For: 3.3.2.CR1 See the referenced forum entry. -- 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

13 years, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (RF-7718) statuses grouping in 4.0

by Ilya Shaikovsky (JIRA)

statuses grouping in 4.0 ------------------------ Key: RF-7718 URL: https://jira.jboss.org/jira/browse/RF-7718 Project: RichFaces Issue Type: Feature Request Components: component-a4j-core Affects Versions: 4.0.0.ALPHA1 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski Fix For: 4.0.0.BETA1 check Nick's sample on grouping statuses. -- 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

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-7538) enable submit button when all the required fields within the form/region are set propertly

by Gary Hu (JIRA)

enable submit button when all the required fields within the form/region are set propertly ------------------------------------------------------------------------------------------ Key: RF-7538 URL: https://jira.jboss.org/jira/browse/RF-7538 Project: RichFaces Issue Type: Feature Request Reporter: Gary Hu The submit button is not enabled until all the required fields within the form/region are set properly. I can think of two ways to implement it. 1) add a new attribute to a4j:form/a4j:rigion to indicate that if this feature is turned on/off. In addition, new attributes could be added to indicate the ids of the submit button, and/or ids of the required fields. For example: <a4j:form id="myForm" enableSubmitButtonForRequriedFields="true" submitButtonId="btnId" requiredFieldIds="id1,id2..." /> 2) add a new attribute to a a4j:commandButton to indicate if this feature is turned on/off. In addtion, new attributes could be added to indicate the ids of the form/region and/or the ids of the required fields. For example: <a4j:commandButton id="btnId" enableSubmitButtonForRequriedFields="true" parentidforrequiredfields="myForm" /> The example showed above means after all the required fields are set properly with the form "myForm" the button is enable. <a4j:commandButton id="btnId" enableSubmitButtonForRequriedFields="true" requiredFieldIds="id1, id2..." /> The example showed above means after all the required fields specified by the attribute "requiredFieldIds" are set properly the button is enabled. Of course, the attribute "enableSubmitButtonForRequriedFields" could be optional. So only the "parentidforrequiredfields" or "requiredFieldIds" is checked to determine if the button needs to be enabled/disable. -- 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

13 years, 11 months

5
11
0 / 0

[JBoss JIRA] Created: (RF-7492) a4j:queue support for standard form submits as well as AJAX request

by Jay Balunas (JIRA)

a4j:queue support for standard form submits as well as AJAX request ------------------------------------------------------------------- Key: RF-7492 URL: https://jira.jboss.org/jira/browse/RF-7492 Project: RichFaces Issue Type: Feature Request Components: component-misc Affects Versions: 3.3.1 Reporter: Jay Balunas Fix For: 4.0.0.BETA1 a4j:queue does not currently support forwarding standard form requests through an a4j:queue. This means that input items that are ajax enabled may be processed through a queue, but if the user clicks submit on the form that request that fire before items in the queue. A user reported a work around. Use a4j:commandButton and then rerender the most of the page - not optimal. We need to create an FAQ for the work around and investigate the standard form support. Brainstorming: This behavior may not be possible on a global or page coped queue. A form scoped a4j:queue could behave like a4j:support and inject the needed behavior into the form tag. -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-6524) maxRequestSize for richfile upload should be made configurable per component and not globally.

by sathay sayee (JIRA)

maxRequestSize for richfile upload should be made configurable per component and not globally. ---------------------------------------------------------------------------------------------- Key: RF-6524 URL: https://jira.jboss.org/jira/browse/RF-6524 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Environment: ALL Reporter: sathay sayee The Richfaces fileupload control currently has maxRequestSize attribute which can be passed as a init-param in the web.xml It would be better if it can be configured on a percontrol basis and not global. -- 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

13 years, 11 months

6
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2009