[JBoss JIRA] Created: (RF-11399) rich:editor doesn't work with Mojarra 2.1.3 / JBossAS 7.1
by Juergen Zimmermann (JIRA)
rich:editor doesn't work with Mojarra 2.1.3 / JBossAS 7.1
---------------------------------------------------------
Key: RF-11399
URL: https://issues.jboss.org/browse/RF-11399
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.1.0.Milestone1
Environment: JBossAS 7 Jenkins build 1605
Reporter: Juergen Zimmermann
JBossAS 7 upgraded to Mojarra 2.1.3-b02. As long as Mojarra 2.0.4 was used, there was no problem with rich:editor. After the upgrade of Mojarra, rich:editor doesn't work any more: nothing is visible. I'll attach a screenshot of the generated HTML code as shown by Firebug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
by Tom Giberius (JIRA)
onselectionchange working incorrect with two extendedDataTable on same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the onselectionchange trigger does not fire. The master tables "thinks" that record three is the selected record while actually it should be record one which was the selected record in the master table.
The correct behaviour should be that each table should "rember" it selected record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the onselectionchange of the master should fire so that details of master record 3 can be shown. If you would have go back to record one of the master then not firing the onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months