October 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-11449) richfaces.js - doesn't clean dom when render=@all

by Lukáš Fryč (JIRA)

richfaces.js - doesn't clean dom when render=@all ------------------------------------------------- Key: RF-11449 URL: https://issues.jboss.org/browse/RF-11449 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 4.0.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Priority: Critical Fix For: 4.1.0.Milestone3 Because source of partial-response update is set to "javax.faces.ViewRoot", richfaces.cleanDom do no clean up of DOM and no components with all the consequences (no components are destroyed). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (RF-11148) rich:editor - problems with handling render=@all DOM update

by Lukáš Fryč (JIRA)

rich:editor - problems with handling render=@all DOM update ----------------------------------------------------------- Key: RF-11148 URL: https://issues.jboss.org/browse/RF-11148 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Fix For: 4.1.0.Milestone2 Internal issue of CKEditor implementation of destroy() method, which can't find associated iframe. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (RF-11431) TabPanel: RF-9402 caused backward compability breakage of style naming

by Lukáš Fryč (JIRA)

TabPanel: RF-9402 caused backward compability breakage of style naming ---------------------------------------------------------------------- Key: RF-11431 URL: https://issues.jboss.org/browse/RF-11431 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-panels-layout-themes Affects Versions: 4.1.0.Milestone3 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone3 Following styles has been renamed: rf-tab-hdr-tabline-top-vis rf-tab-hdr-top-act rf-tab-hdr-top-inact ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[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, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (RF-11398) rich:message span renders with a height of 18ex

by Cody Lerum (JIRA)

rich:message span renders with a height of 18ex ----------------------------------------------- Key: RF-11398 URL: https://issues.jboss.org/browse/RF-11398 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone1 Reporter: Cody Lerum Default height of a rich:message is 18ex This creates div's 18x larger then necessary https://github.com/richfaces/components/blob/develop/validator/ui/src/mai... Shouldn't this be 1ex or not defined at all -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
8
0 / 0

[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, 1 month

6
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues October 2011