September 2013 - richfaces-issues

[JBoss JIRA] (RF-13150) Remove JMS functionality from the RichFaces showcase

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13150?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13150: ------------------------------------ Thanks for the verification [~ppitonak]. Those artifacts were left in place as the JMS push in the RichFaces 4.3.x showcase was only disabled-by-default and not removed. The functionality is still present if people revert the configuration change and re-enable Push JMS in their local builds of the showcase. The RichFaces 5 showcase will likely not have JMS Push present at all, leaving the functionality to a dedicated demo. > Remove JMS functionality from the RichFaces showcase > ---------------------------------------------------- > > Key: RF-13150 > URL: https://issues.jboss.org/browse/RF-13150 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.4 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > The RichFaces showcase currently includes a demo of RichFaces push backed by JMS. The JMS security configuration however is not portable, and leads to difficulties in running the RichFaces showcase in other containers. > We target the showcase at demonstrating component capabilities, and leave the JMS integration to be demonstrated as a developer example. The caveat here is that we do a better job promoting the availability of our developer examples. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11673) Warning messages have color unreadable on white background - (warningColor)

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11673?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11673: ------------------------------- Labels: text_visibility (was: needs-qe text_visibility) > Warning messages have color unreadable on white background - (warningColor) > --------------------------------------------------------------------------- > > Key: RF-11673 > URL: https://issues.jboss.org/browse/RF-11673 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: skinning > Affects Versions: 4.0.0.Final > Reporter: Lukáš Fryč > Assignee: Wesley Hales > Labels: text_visibility > Fix For: 4.1.0.CR2 > > Attachments: Screenshot-5.png, Screenshot-6.png > > > {{warningColor}} is based on {{#FFE6E6}} in {{blueSky}} and other skins. > This color is unreadable on white background. > Change this color to be readable on white background by default. > *Breaks backward compatibility (affects {{4.0.0.Final}})* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11851) rich:hotKey - add support for onkeypress, onkeydown and onkeyup

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11851?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11851: ------------------------------- Labels: (was: needs-qe) > rich:hotKey - add support for onkeypress, onkeydown and onkeyup > --------------------------------------------------------------- > > Key: RF-11851 > URL: https://issues.jboss.org/browse/RF-11851 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.CR1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 4.2.0.CR1 > > > The binding will be done only for such types which have defined some handler. > This will mean removing {{@type}} attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11851) rich:hotKey - add support for onkeypress, onkeydown and onkeyup

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11851?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-11851. ------------------------------ > rich:hotKey - add support for onkeypress, onkeydown and onkeyup > --------------------------------------------------------------- > > Key: RF-11851 > URL: https://issues.jboss.org/browse/RF-11851 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.2.0.CR1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 4.2.0.CR1 > > > The binding will be done only for such types which have defined some handler. > This will mean removing {{@type}} attribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11977) Multiple fileUpload controls on the same page do not work

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11977?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-11977: ------------------------------- Labels: (was: needs-qe) > Multiple fileUpload controls on the same page do not work > --------------------------------------------------------- > > Key: RF-11977 > URL: https://issues.jboss.org/browse/RF-11977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: IE7,8,9, FireFox, Google Chrome > Reporter: Roxana Balaci > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: rf-11977-chromium-afterClickOn2ndUploadBtn.png, rf-11977-Chromium.png, rf-11977-ff11.png > > > Situation: > Two rich:fileUpload controls, in the same form. > When: > # choose first file for upload > # choose second file for upload > # click upload button for the first file > The first control disappears from the page and you cannot upload the second file (the upload event is never caught). > Could you please indicate a solution for this problem? > Thank you very much! > Part of the code used for testing is the following: > {code} > <h:form id="uploadForm"> > <rich:panel> > <rich:panel> > <rich:fileUpload id="uploadFile1" > fileUploadListener="#{bean.method1}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px"</rich:fileUpload> > </rich:panel> > <rich:panel> > <rich:fileUpload id="uploadFile2" > fileUploadListener="#{bean.method2}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px"</rich:fileUpload> > </rich:panel> > <rich:panel> > <a4j:commandButton id="addB" value="value" action="#{bean.method3}" > render="stg" /> > </rich:panel> > </rich:panel> > </h:form> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11977) Multiple fileUpload controls on the same page do not work

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-11977?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-11977. ------------------------------ > Multiple fileUpload controls on the same page do not work > --------------------------------------------------------- > > Key: RF-11977 > URL: https://issues.jboss.org/browse/RF-11977 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.1.0.Final > Environment: IE7,8,9, FireFox, Google Chrome > Reporter: Roxana Balaci > Assignee: Brian Leathem > Fix For: 4.2.1.CR1 > > Attachments: rf-11977-chromium-afterClickOn2ndUploadBtn.png, rf-11977-Chromium.png, rf-11977-ff11.png > > > Situation: > Two rich:fileUpload controls, in the same form. > When: > # choose first file for upload > # choose second file for upload > # click upload button for the first file > The first control disappears from the page and you cannot upload the second file (the upload event is never caught). > Could you please indicate a solution for this problem? > Thank you very much! > Part of the code used for testing is the following: > {code} > <h:form id="uploadForm"> > <rich:panel> > <rich:panel> > <rich:fileUpload id="uploadFile1" > fileUploadListener="#{bean.method1}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px"</rich:fileUpload> > </rich:panel> > <rich:panel> > <rich:fileUpload id="uploadFile2" > fileUploadListener="#{bean.method2}" maxFilesQuantity="1" > immediateUpload="true" listHeight="65px"</rich:fileUpload> > </rich:panel> > <rich:panel> > <a4j:commandButton id="addB" value="value" action="#{bean.method3}" > render="stg" /> > </rich:panel> > </rich:panel> > </h:form> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12052?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak closed RF-12052. ------------------------------ > rich:TabPanel - HTML comments should be supported inside the tabPanel > --------------------------------------------------------------------- > > Key: RF-12052 > URL: https://issues.jboss.org/browse/RF-12052 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Jean ANDRE > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: > E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase <Null Message> > java.lang.IllegalArgumentException > at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) > {code} > <rich:tabPanel id="itemView-tabs" > switchType="ajax" > headerPosition="top" > itemChangeListener="#{viewItemController.doItemChangeListener}" > activeItem="#{viewItemController.activeTab}" > immediate="true"> >  >  >  > <rich:tab id="nested-tabs-1" header="#{msg['nested.tab.static.header.1']}"> > </rich:tab> > {code} > Or at least, give us a clear error message as we did for tabPanel and the form tag. > Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12052) rich:TabPanel - HTML comments should be supported inside the tabPanel

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12052?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-12052: ------------------------------- Labels: (was: needs-qe) > rich:TabPanel - HTML comments should be supported inside the tabPanel > --------------------------------------------------------------------- > > Key: RF-12052 > URL: https://issues.jboss.org/browse/RF-12052 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Jean ANDRE > Assignee: Brian Leathem > Priority: Trivial > Fix For: 4.2.1.CR1 > > > Is it possible to support HTML comment inside a tabPanel. Because it causes this error if we but comments as shown below. The error is: > E org.richfaces.context.ExtendedPartialViewContextImpl processPartialExecutePhase <Null Message> > java.lang.IllegalArgumentException > at org.richfaces.component.AbstractTogglePanel.getChildName(AbstractTogglePanel.java:490) > {code} > <rich:tabPanel id="itemView-tabs" > switchType="ajax" > headerPosition="top" > itemChangeListener="#{viewItemController.doItemChangeListener}" > activeItem="#{viewItemController.activeTab}" > immediate="true"> >  >  >  > <rich:tab id="nested-tabs-1" header="#{msg['nested.tab.static.header.1']}"> > </rich:tab> > {code} > Or at least, give us a clear error message as we did for tabPanel and the form tag. > Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12853) rich:inplaceSelect: JS API bugs

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12853?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-12853: ------------------------------------ Verified in 4.3.4.Final respin. Issue is ready to be closed. > rich:inplaceSelect: JS API bugs > ------------------------------- > > Key: RF-12853 > URL: https://issues.jboss.org/browse/RF-12853 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Environment: JBoss AS 7.1, > FF 18, Chrome 24 > RichFaces 4.3.2-SNAPSHOT > Reporter: Jiří Štefek > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.3.4 > > > The function hidePopup() does not exist. > Error in console: > {code} > RichFaces.$(...).hidePopup is not a function > {code} > The function setValue() is not working. > Error in console: > {code} > TypeError: item is null > InplaceSelect.js line 217 > var clientSelectItem = item.data('clientSelectItem'); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12853) rich:inplaceSelect: JS API bugs

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12853?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-12853: ------------------------------- Labels: (was: needs-qe) > rich:inplaceSelect: JS API bugs > ------------------------------- > > Key: RF-12853 > URL: https://issues.jboss.org/browse/RF-12853 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Environment: JBoss AS 7.1, > FF 18, Chrome 24 > RichFaces 4.3.2-SNAPSHOT > Reporter: Jiří Štefek > Assignee: Brian Leathem > Fix For: 4.3.4 > > > The function hidePopup() does not exist. > Error in console: > {code} > RichFaces.$(...).hidePopup is not a function > {code} > The function setValue() is not working. > Error in console: > {code} > TypeError: item is null > InplaceSelect.js line 217 > var clientSelectItem = item.data('clientSelectItem'); > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues September 2013