[JBoss JIRA] Created: (RF-3355) IE6 can't focus fields were covered by suggestionbox
by B VO (JIRA)
IE6 can't focus fields were covered by suggestionbox
----------------------------------------------------
Key: RF-3355
URL: http://jira.jboss.com/jira/browse/RF-3355
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.0.1
Environment: IE6, Seam 1.2.1
Reporter: B VO
Priority: Critical
After use a suggestionbox, fields (exactly part of fields) that were covered by the pop-up can't be use directly.
User can click in these fields but the focus stay in the suggestionbox's input field. for example, a select field open and close in second.
The user has to click in the page but out of the zone covered to these fields to retrieve a good comportment.
After that, if the user just focus the input field linked to the suggestionbox, the bug reappear.
--
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
17 years, 7 months
[JBoss JIRA] Created: (RF-3154) Nested ajax rendered components not submitting
by Adam Jenkins (JIRA)
Nested ajax rendered components not submitting
----------------------------------------------
Key: RF-3154
URL: http://jira.jboss.com/jira/browse/RF-3154
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4, 3.1.3, 3.1.2, 3.1.1, 3.1.5, 3.1.x
Environment: Jboss + Richfaces + Myfaces
Reporter: Adam Jenkins
Priority: Blocker
Attachments: ValueChangeBugReproduce.jsp
When an ajax output panel is rerendered on a selects 'onchange', and it contains a panel and another select (with similar behaviour), the values of the second select aren't being bound to the model...this is more easily explained in code:
See the attached jsf page and managed bean. When the first select with id="toggle" is changed, the output panel main-panel reRendered fine, and the child components (which have a 'rendered' attribute) are now visible...perfect
However the child component that is a select (id="some-select") that has a4j support isn't being bound to the backing bean when the onchange event is fired.
--
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
17 years, 7 months
[JBoss JIRA] Created: (RF-2218) dataTable binding causes restore view problem with back button and navigation
by Matt Fischer (JIRA)
dataTable binding causes restore view problem with back button and navigation
-----------------------------------------------------------------------------
Key: RF-2218
URL: http://jira.jboss.com/jira/browse/RF-2218
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.4
Environment: Tomcat v5.5, RichFaces 3.1.4.GA, tomahawk 1.1.5, myFaces 1.1.5, Windows XP Pro SP2 v2002
Reporter: Matt Fischer
Attachments: navtest.war
To summarize the problem: Two pages, one request scoped bean, navigation rule from page1 to page2, redirect: no, both dataTables bound to same UIData property in the request scoped bean.
Open page one, click the link, navigate to page 2 OK -> Click browser back button, click link on Page 1, navigate to Page 2 OK BUT displays Page 1 PLUS Page 2 results (side by side).
Details:
I have created a Request Scoped Bean, and two pages; page1.jsp and page2.jsp. I have a navigation rule to go from page1 to page2, redirect: no. There is a dataTable on both pages, page1 outputs one column that has a commandLink with action="success", forcing navigation to page 2. Both dataTables bind to a UIData property in the Request Scoped Bean. I have included .war files so it can be tested.
1. The first issue I get when I click the link on page1 is duplicate id error.
2. If I add an id tag to the t:outputText on page2.jsp then there is no duplicate id error, but I get the problem described above.
If the binding is removed, there is no problem.
I also have no problem with ajax4jsf - my production code is using the pre-combined version. I am putting out a new production release and wanted to use the latest richfaces 3.1.4.GA (the combined version).
See .war file
--
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
17 years, 7 months