February 2011 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-7932) photoalbum: tree with albums collapses after drag&drop

by Pavol Pitonak (JIRA)

photoalbum: tree with albums collapses after drag&drop ------------------------------------------------------ Key: RF-7932 URL: https://jira.jboss.org/jira/browse/RF-7932 Project: RichFaces Issue Type: Bug Components: examples Affects Versions: 3.3.2.GA Environment: JBoss AS 5.1, IE 7, FF 3.5 Reporter: Pavol Pitonak Fix For: 3.3.3.CR1 When the user expands all albums and then d&d a picture from one album to another one, picture is moved and the tree is collapsed -- usability problem. -- 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

12 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-10383) Showcase: add samples for listeners

by Pavol Pitonak (JIRA)

Showcase: add samples for listeners ----------------------------------- Key: RF-10383 URL: https://issues.jboss.org/browse/RF-10383 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.0.0.Milestone5 Reporter: Pavol Pitonak Add samples for following tags so that community knows they exist and how to use them: * rich:itemChangeListener * rich:panelToggleListener * rich:treeSelectionChangeListener * rich:treeToggleListener -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (RF-8608) rich:effect name does not properly create the JS function to be called

by Tomas Cerny (JIRA)

rich:effect name does not properly create the JS function to be called ---------------------------------------------------------------------- Key: RF-8608 URL: https://jira.jboss.org/jira/browse/RF-8608 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.3.3.Final Reporter: Tomas Cerny Priority: Blocker rich:effect name does not properly create the JS function.. Consider your documentation example:  <div id="contentDiv">...</div> <input type="button" onclick="hideDiv({duration:0.7})" value="Hide" /> <input type="button" onclick="showDiv()" value="Show" /> <rich:effect name="hideDiv" for="contentDiv" type="Fade" /> <rich:effect name="showDiv" for="contentDiv" type="Appear" /> it worked on the older version but in 3.3.3 so I must downgrade :| This is my browser complaint: Error: Effect[A.type] is not a constructor Source File: http://localhost/a4j/g/3_3_3.Final/org/richfaces/ui.pack.js Line: 15201 -- 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

12 years, 8 months

7
19
0 / 0

[JBoss JIRA] Created: (RF-7921) DropDownMenu: wrong vertical positioning of popup list on scrolling in Firefox

by rofl rofl (JIRA)

DropDownMenu: wrong vertical positioning of popup list on scrolling in Firefox ------------------------------------------------------------------------------ Key: RF-7921 URL: https://jira.jboss.org/jira/browse/RF-7921 Project: RichFaces Issue Type: Bug Components: component-menu Affects Versions: 3.3.2.CR1, 3.3.1 Environment: winXP, hibernate 3.2.4.sp1, seam 2.1.0.SP1, firefox 3.5.3 Reporter: rofl rofl Priority: Minor The popup list of the drop down menu is wrongly positioned when one scrolls the page. It is shown too far below it's anchor point (i.e. it is not directly connected to it's anchor point) - the offset changes on scrolling (i.e. the more one scrools down, the farer below it is shown) -- 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

12 years, 9 months

5
8
0 / 0

[JBoss JIRA] Created: (RF-9580) select: implement filterNewValue analog as for 3.3.x combobox

by Ilya Shaikovsky (JIRA)

select: implement filterNewValue analog as for 3.3.x combobox ------------------------------------------------------------- Key: RF-9580 URL: https://jira.jboss.org/browse/RF-9580 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.0.0.Milestone4 Reporter: Ilya Shaikovsky Assignee: Anton Belevich will not fit M4 but need to implement later. you could check the filterNewValues attribute at 3.3.x combo and we could discuss naming for 4.x mode in select. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
5
0 / 0

[JBoss JIRA] Created: (RF-10456) CLONE - rich:messages displays messages multiple times

by Ilya Shaikovsky (JIRA)

CLONE - rich:messages displays messages multiple times ------------------------------------------------------ Key: RF-10456 URL: https://issues.jboss.org/browse/RF-10456 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 3.3.0, 3.3.1, 3.3.2.CR1, 3.3.2.GA, 3.3.2.SR1, 3.3.3.BETA1, 3.3.3.CR1, 3.3.3.Final Environment: Richfaces 3.3.0 upwards with integrated Spring Webflow (version 2.0.5) and Hibernate Validator 4.0.2. Reporter: Ilya Shaikovsky Assignee: Alexander Smirnov Fix For: 3.Future Using a graphValidator, I set up a bean with Hibernate Validator annotations. When multiple fields fail validation; the <rich:messages /> tag outputs the error messages multiple times. It seems as though the message is displayed based on the number of failed fields. For example; when 2 fields fail, it will display both error messages twice. If 3 fields fail, it'll display all 3 messages 3 times, and so on. I have managed to replicate the same error in versions 3.3.0 to 3.3.3. I have not tried >4 as we need a stable release. This may mean it could already be fixed in version 4; but I am submitting this issue regardless. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

5
30
0 / 0

[JBoss JIRA] Created: (RF-7344) Add controls for where in the header loaded scripts are placed

by Jay Balunas (JIRA)

Add controls for where in the header loaded scripts are placed -------------------------------------------------------------- Key: RF-7344 URL: https://jira.jboss.org/jira/browse/RF-7344 Project: RichFaces Issue Type: Task Components: browser compatibility, core Affects Versions: 3.3.1 Environment: IE8 Reporter: Jay Balunas Fix For: 3.3.2.CR1 IE8 requires some header content be located at the very top of the header. Because RichFaces places some of the loaded scripts first this can break. For example "<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />" will be ignored if not the first element after the header. Although the work around can be to just place the value in the header directly "<header name="X-UA-Compatible">IE=EmulateIE7</header>", RichFaces should have a way to control the location of the scripts in the header. This could take the form of a new context param or perhaps a tag that RF can trigger off of for default script placement. If not there behavior is defaulted to current. -- 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

12 years, 9 months

7
8
0 / 0

[JBoss JIRA] Created: (RF-10197) Right click menu - rich:contextMenu - should be supported for 4.0.0

by Devinder Singh (JIRA)

Right click menu - rich:contextMenu - should be supported for 4.0.0 ------------------------------------------------------------------- Key: RF-10197 URL: https://issues.jboss.org/browse/RF-10197 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-menu Affects Versions: 4.0.0.Milestone5 Environment: Windows Reporter: Devinder Singh rich:contextMenu is available in 3.x release but not yet supported in 4.0. As it enables right click menus on JSF components, it's a very useful feature that can be used in wide variety of applications -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

18
24
0 / 0

[JBoss JIRA] Created: (RF-3566) Can't use messages with fileUpload

by Ilya Shaikovsky (JIRA)

Can't use messages with fileUpload ---------------------------------- Key: RF-3566 URL: http://jira.jboss.com/jira/browse/RF-3566 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1 Reporter: Ilya Shaikovsky Assigned To: Nick Belaevski http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153840#4153840 Using his code in demosite listener I'm getting next behaviour. "Transfer error occuried" error in file upload status. But rich:messages which added to the page doesn't show anything. -- 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

12 years, 10 months

8
15
0 / 0

[JBoss JIRA] Created: (RF-8201) Print RichFaces module information at start up

by Jay Balunas (JIRA)

Print RichFaces module information at start up ---------------------------------------------- Key: RF-8201 URL: https://jira.jboss.org/jira/browse/RF-8201 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: build, core Reporter: Jay Balunas Fix For: 4.0.0.ALPHA2 During start up all RichFaces modules should printout meta data into the log. This would be for each module api, ui, impl, themes, etc.... This will be more important as we allow for module releases that may not always be 100% in sync. It will also help with debugging issues. -- 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

12 years, 10 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues February 2011