November 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Created: (RF-3451) scrollableDataTable: text-selection cursor is always displayed in IE 7

by Tsikhon Kuprevich (JIRA)

scrollableDataTable: text-selection cursor is always displayed in IE 7 ---------------------------------------------------------------------- Key: RF-3451 URL: http://jira.jboss.com/jira/browse/RF-3451 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.1 Environment: 3.2.1.CR5 IE 7 Reporter: Tsikhon Kuprevich Assigned To: Nick Belaevski scrollableDataTable: text-selection cursor is always displayed in IE 7 -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-5172) ExtendedDataTable: after column removing, space that column occupied became empty, not allocated by remaining columns.

by Mikhail Vitenkov (JIRA)

ExtendedDataTable: after column removing, space that column occupied became empty, not allocated by remaining columns. ---------------------------------------------------------------------------------------------------------------------- Key: RF-5172 URL: https://jira.jboss.org/jira/browse/RF-5172 Project: RichFaces Issue Type: Bug Affects Versions: 3.3.0 Environment: IE6, IE7, FF 3.1.3, Safari 3.1, Opera 9.62(3.3.0.BETA1) seam 2.1.0.SP1 Reporter: Mikhail Vitenkov Assignee: Nick Belaevski Priority: Minor Remove any column from "Columns" popup submenu. Actual behavior: Remaining columns regrouped & empty space instead appear. See screenshot. -- 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, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-5086) extendedTable: Allow to turn of built-in menu

by Ilya Shaikovsky (JIRA)

extendedTable: Allow to turn of built-in menu --------------------------------------------- Key: RF-5086 URL: https://jira.jboss.org/jira/browse/RF-5086 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.3.0 Reporter: Ilya Shaikovsky Assignee: Nick Belaevski http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4192406#4192406 -- 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, 10 months

12
15
0 / 0

[JBoss JIRA] Created: (RF-3911) Speed up documentation building process

by Svetlana mukhina (JIRA)

Speed up documentation building process ---------------------------------------- Key: RF-3911 URL: http://jira.jboss.com/jira/browse/RF-3911 Project: RichFaces Issue Type: Feature Request Components: doc Affects Versions: 3.2.1 Reporter: Svetlana mukhina Assigned To: Nick Belaevski Priority: Optional Fix For: 3.2.2 It's necessary to speed up documentation building process -- 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

13 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (RF-1164) Font and hyphenation pattern in PDF

by Svetlana mukhina (JIRA)

Font and hyphenation pattern in PDF ----------------------------------- Key: RF-1164 URL: http://jira.jboss.com/jira/browse/RF-1164 Project: RichFaces Issue Type: Task Components: doc Affects Versions: Future Versions Reporter: Svetlana mukhina Assigned To: Nick Belaevski Fix For: 3.1.0 It's necessary to add more readable font and hyphenation possibility in PDF -- 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

13 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (RF-1205) GWT4JSF UIPage tage does not implement GwtSource

by Curt (JIRA)

GWT4JSF UIPage tage does not implement GwtSource ------------------------------------------------ Key: RF-1205 URL: http://jira.jboss.com/jira/browse/RF-1205 Project: RichFaces Issue Type: Bug Environment: WinXP JBoss 4.1CR1, GWT4JSF-1.1.2-SNAPSHOT Reporter: Curt Attachments: UIPage.java.patch Using the page tag from the https://ajax4jsf.dev.java.net/gwt namespace generates an error when it contains a listener child tag. The error is in GwtListenerHandler: com.sun.facelets.tag.TagException: /pages/Login.jsp @14,57 <gwt:gwtListener> Parent is not of type GwtSource, type is: org.ajax4jsf.gwt.jsf.UIPage@99c4cc at org.ajax4jsf.gwt.jsf.GwtListenerHandler.apply(GwtListenerHandler.java:163 The JSF page was structured: <f:view xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:gwt="https://ajax4jsf.dev.java.net/gwt" xmlns:dri="https://ajax4jsf.dev.java.net/gwt/DRI" contentType="text/html"> <gwt:page title="DRI"> <f:facet name="head"> <h:panelGroup> </h:panelGroup> </f:facet>  <dri:component id="main"> <gwt:gwtListener serviceBean="#{userAuth}"/> </dri:component> </gwt:page> </f:view> -- 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

13 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (RF-3517) Entered values in rich:subTable are lost upon validation errors

by Jonck van der Kogel (JIRA)

Entered values in rich:subTable are lost upon validation errors --------------------------------------------------------------- Key: RF-3517 URL: http://jira.jboss.com/jira/browse/RF-3517 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.4 Environment: Windows Vista, JBoss 4.0.5, JSF 1.2 Reporter: Jonck van der Kogel Given the following sample code: <rich:dataTable value="#{backingBean.holders}" var="holder"> <f:facet name="header"> <rich:columnGroup> <rich:column> <h:outputText value="Test"> </rich:column> </rich:columnGroup> </f:facet> <rich:column> <h:inputText value="#{holder.requiredTest}" required="true" /> </rich:column> <rich:subTable value="#{holder}" var="holderSubTable"> <rich:column colspan="1"> <h:inputText value="#{holderSubTable.test}" /> </rich:column> </rich:subTable> </rich:dataTable> When the surrounding form is submitted, the "test" field in the rich:subTable is cleared when a validation error occurs. This is not the expected behavior, normally in JSF when a validation error occurs the entered values remain. To illustrate this, I rebuilt the above scenario but now placed all fields within the same rich:dataTable like so: <rich:dataTable value="#{backingBean.holders}" var="holder"> <f:facet name="header"> <rich:columnGroup> <rich:column> <h:outputText value="Test"> </rich:column> <rich:column> <h:outputText value="Test2"> </rich:column> </rich:columnGroup> </f:facet> <rich:column> <h:inputText value="#{holder.requiredTest}" required="true" /> </rich:column> <rich:column> <h:inputText value="#{holder.test}" /> </rich:column> </rich:dataTable> In this case when the form is submitted and a validation error occurs the "test" field is not cleared, as expected. -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (RF-4398) Form: ajax form doesn't handle ajaxSingle in the right way

by Nick Belaevski (JIRA)

Form: ajax form doesn't handle ajaxSingle in the right way ---------------------------------------------------------- Key: RF-4398 URL: https://jira.jboss.org/jira/browse/RF-4398 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Reporter: Nick Belaevski Assignee: Alexander Smirnov Fix For: Future <a4j:form ajaxSubmit="true" ajaxSingle="true" id="a4jform"> Ajax single <h:inputText /> <h:commandButton actionListener="#{capitalsBean.action}" value="Button" id="button" /> </a4j:form> Pressing button submits the following parameters: AJAXREQUEST _viewRoot a4jform a4jform a4jform a4jform a4jform:button Button a4jform:j_id236 22 ajaxSingle a4jform autoScroll javax.faces.ViewState j_id2 ajaxSingle should be a4jform:button, duplicate parameters should not be submitted -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-4084) Auto tests development: portlets

by Nick Belaevski (JIRA)

Auto tests development: portlets -------------------------------- Key: RF-4084 URL: https://jira.jboss.org/jira/browse/RF-4084 Project: RichFaces Issue Type: Task Components: planning Reporter: Nick Belaevski Assignee: Alexander Smirnov -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (RF-4165) Support Plug n Skin feature in the portlets

by Alexander Smirnov (JIRA)

Support Plug n Skin feature in the portlets ------------------------------------------- Key: RF-4165 URL: https://jira.jboss.org/jira/browse/RF-4165 Project: RichFaces Issue Type: Feature Request Affects Versions: 3.2.1 Environment: Jboss Portal, portletbridge. Reporter: Alexander Smirnov Assignee: Alexander Smirnov Fix For: 3.2.2 When attempting to use a skin in JBoss Portal created using the Plug n Skin Tool for Richfaces components, the <skin-name>.skin.properties file is not referencing the <skin-name>.xcss file located at META-INFskins. Instead, the base skin properties are being used to render the Richfaces components. -- 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, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2008