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