January 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12813) rich:panelMenuItem executes action even if disabled attribute evaluates to true

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12813?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12813: ---------------------------------- Assignee: Brian Leathem (was: Pavel Slegr) > rich:panelMenuItem executes action even if disabled attribute evaluates to true > ------------------------------------------------------------------------------- > > Key: RF-12813 > URL: https://issues.jboss.org/browse/RF-12813 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.0.Final > Reporter: Andrey Zhemoytuk > Assignee: Brian Leathem > Fix For: 4.3.5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > org.richfaces.renderkit.html.PanelMenuItemRenderer#doDecode does not check 'disabled' attribute (how usually do other components before executing action) which may cause security issues. > Initially reported on: > http://stackoverflow.com/questions/15130807/richfaces-panelmenuitem-reeva... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13239) Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13239?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13239: ------------------------------- Sprint: 4.3.5.Sprint 2 > Popup panel: CSS class rf-pp-hdr contains invalid property repeat-x > ------------------------------------------------------------------- > > Key: RF-13239 > URL: https://issues.jboss.org/browse/RF-13239 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Priority: Minor > Fix For: 4.3.5 > > > # deploy Metamer and open http://localhost:8080/metamer/faces/components/richPopupPanel/simple.xhtml > # check browser console > result: > * Invalid CSS property name: repeat-x (in popupPanel.ecss, line 40) > possible solution: > * replace > {code} > .rf-pp-hdr { > background: url(...); > repeat-x: top left #BED6F8; > ... > } > {code} > * with > {code} > .rf-pp-hdr { > background: url(...) repeat-x top left #BED6F8; > ... > } > {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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13292) Autocomplete: up and down arrow keys not working in Opera

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13292?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13292: ------------------------------- Sprint: 4.3.5.Sprint 2 > Autocomplete: up and down arrow keys not working in Opera > --------------------------------------------------------- > > Key: RF-13292 > URL: https://issues.jboss.org/browse/RF-13292 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input > Affects Versions: 4.3.4, 5.0.0.Alpha2 > Reporter: alexey plotnikov > Fix For: 4.3.5 > > > Hello, i use Richfaces 4.3.4.Final. Up and down arrow keys not working(ignoring) for Autocomplete component in Opera. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13203) a4j:queue should have status attribute

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13203?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13203: ------------------------------- Sprint: 4.3.5.Sprint 2 > a4j:queue should have status attribute > -------------------------------------- > > Key: RF-13203 > URL: https://issues.jboss.org/browse/RF-13203 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Labels: gss, queue > Fix For: 4.3.5 > > > a4j:queue should have status attribute, so it can connect to a4j:status. Consider the following example: > {noformat} > <a4j:queue name="quick" requestDelay="200" /> > <a4j:queue name="slow" requestDelay="1000" /> > <a4j:status name="quickStatus" startText="Started!" stopText="Stopped"/> > <br/> > <a4j:statusname="slowStatus" startText="Started!" stopText="Stopped" /> > > <h:form> > <a4j:commandButton action="#{test.dummy}" value="Quick"> > <a4j:attachQueue name="quick"/> > </a4j:commandButton> > </h:form> > <br/> > <h:form> > <a4j:commandButton action="#{test.dummy}" value="Slow"> > <a4j:attachQueue name="slow"/> > </a4j:commandButton> > </h:form> > {noformat} > By using the status attr. of a4j:queue, it would be possible to connect "slow" queue to "slowStatus" and thus every component that would be connected to the queue, would also be connected to the status. > Note in this example it would be simpler to set status attr. on the components themselves, but imagine there are more components connected to the queue. > I was also informed, that this functionality was present in RF 3.3. > Workarounds: > - set status attr on every component instead of on the queue- in larger applications this is not doable. > - use a4j:status JS API and a4j:queues' onsubmit and oncomplete methods- onsubmit and oncomplete a4j:queue are not implemented, so not working now -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13397) a4j:push not working with Internet Explorer >= 10

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13397?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13397: ------------------------------- Sprint: 4.3.5.Sprint 2 > a4j:push not working with Internet Explorer >= 10 > ------------------------------------------------- > > Key: RF-13397 > URL: https://issues.jboss.org/browse/RF-13397 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.4 > Environment: Any where Internet Explorer 10 or above is available > Reporter: Tobias Seppenhauser > Labels: richfaces > Fix For: 4.3.5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The <a4j:push> mechanism seems to be broken when using the Internet Explorer 10 or above. This can easily be verified by visiting the corresponding showcase component [1]. The UUID never gets updated. > Unfortunately I can't see any error in the Javascript console. > [1] http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&sk... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13208) Push: error "not well-formed" appears in browser console in Firefox

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13208?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13208: ------------------------------- Sprint: 4.3.5.Sprint 2 > Push: error "not well-formed" appears in browser console in Firefox > ------------------------------------------------------------------- > > Key: RF-13208 > URL: https://issues.jboss.org/browse/RF-13208 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 4.3.4 > Environment: RichFaces 4.3.4.Final > Metamer 4.3.4.20130919-Final > Mojarra 2.1.19 > EAP 6.1.1 > OpenJDK Runtime Environment 1.7.0_40-mockbuild_2013_09_19_20_10-b00 @ Linux > Firefox 24.0 @ Linux x86_64 > Reporter: Pavol Pitonak > Fix For: 4.3.5, 5.0.0.Alpha3 > > Attachments: firefox_console.png > > > # deploy Metamer and open http://127.0.0.1:8080/metamer/faces/components/a4jPush/twoPush.xhtml > # open browser console > # click "Push 2!" button > result: > * browser console contains "not well-formed" JavaScript error (see screenshot) > * when you click on the error, you can see something like this: > {quote} > <"topic":"jmsSampleAddress2","data":"day: 23, month: 9, time: 11:01:12.829","number":0> > {quote} > * component seems to work fine despite this error > * I couldn't see this error in Chrome 29 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13455) The rich:tabPanel no longer visits tab header facets while rendering a response.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13455?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13455: ------------------------------------ This change will need to be applied to the 4.3.5 and 4.5.0 branches. > The rich:tabPanel no longer visits tab header facets while rendering a response. > -------------------------------------------------------------------------------- > > Key: RF-13455 > URL: https://issues.jboss.org/browse/RF-13455 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > <h:head> > </h:head> > <h:body> > > <a4j:log hotkey="M" mode="popup" /> > <h:form id="form" prependId="false"> > <rich:tabPanel id="tabPanel"> > <rich:tab header="tab 1"> > <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" /> > </rich:tab> > <rich:tab> > <f:facet name="header"> > <h:outputText id="label" value="#{testBean.clicks} clicks" /> > </f:facet> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {code} > testBean is a simple session-scoped HashMap. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13455) The rich:tabPanel no longer visits tab header facets while rendering a response.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13455?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13455: ------------------------------- Fix Version/s: 4.5.0.Alpha2 > The rich:tabPanel no longer visits tab header facets while rendering a response. > -------------------------------------------------------------------------------- > > Key: RF-13455 > URL: https://issues.jboss.org/browse/RF-13455 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Labels: regression > Fix For: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > <h:head> > </h:head> > <h:body> > > <a4j:log hotkey="M" mode="popup" /> > <h:form id="form" prependId="false"> > <rich:tabPanel id="tabPanel"> > <rich:tab header="tab 1"> > <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" /> > </rich:tab> > <rich:tab> > <f:facet name="header"> > <h:outputText id="label" value="#{testBean.clicks} clicks" /> > </f:facet> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {code} > testBean is a simple session-scoped HashMap. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13456) The toggle panel components should allow the user to prevent rendering the active tab when the tab header is clicked.

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13456?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13456: ------------------------------- Fix Version/s: 5.0.0.Alpha4 (was: 5.0.0.Alpha3) > The toggle panel components should allow the user to prevent rendering the active tab when the tab header is clicked. > --------------------------------------------------------------------------------------------------------------------- > > Key: RF-13456 > URL: https://issues.jboss.org/browse/RF-13456 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Reporter: Brian Leathem > Fix For: 5.0.0.Alpha4 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The TogglePanelRenderer currently implicitly adds the tabPanel@active metacomponent to the list of rendered ids when a tab panel is clicked. > See: > https://github.com/richfaces/richfaces/blob/master/framework/src/main/jav... > {code} > PartialViewContext pvc = context.getPartialViewContext(); > pvc.getRenderIds().add(component.getClientId(context) + MetaComponentResolver.META_COMPONENT_SEPARATOR_CHAR + AbstractTogglePanel.ACTIVE_ITEM_META_COMPONENT); > {code} > Rather than adding the meta component id like this, the meta component id should be treated as the default value of the toggle panel's render attribute. specifying a value for the render attribute would override this default value, and require the user to explicitly call for a render of the active item by adding the meta component id to the render 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, 11 months

1
0
0 / 0

[JBoss JIRA] (RF-13278) Add support for a 'header' meta-component to the rich:tabPanel

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-13278 at 1/2/14 9:30 PM: ------------------------------------------------------------ Thanks for the review Lukas. Your commit is sensible. Having thought about this issue over the break, and speaking about it with @lfryc today I've come to the following conclusions: # The tabPanel headers should be visited in the walk of the component tree, because they are visible on the page (RF-13455) # Having a tabPanel@header\{s} meta-component would still be useful (despite 1) # The @active item should be the default value of the tabPanel, but should be overridden when a user sets the render attribute of the tabPanel (RF-13456) We will address 1) in 4.3, however 2) and 3) will be included in 4.5/5.0. was (Author: bleathem): Thanks for the review Lukas. Your commit is sensible. Having thought about this issue over the break, and speaking about it with @lfryc today I've come to the following conclusions: # The tabPanel headers should be visited in the walk of the component tree, because they are visible on the page (RF-13455) # Having a tabPanel@header\{s} meta-component would still be useful (despite 1) # The @active item should be the default value of the tabPanel, but should be overridden when a user sets the render attribute of the tabPanel We will address 1) in 4.3, however 2) and 3) will be included in 4.5/5.0. > Add support for a 'header' meta-component to the rich:tabPanel > -------------------------------------------------------------- > > Key: RF-13278 > URL: https://issues.jboss.org/browse/RF-13278 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is placed in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:h="http://java.sun.com/jsf/html" > xmlns:c="http://java.sun.com/jsp/jstl/core" xmlns:rich="http://richfaces.org/rich" xmlns:a4j="http://richfaces.org/a4j" > xmlns:f="http://java.sun.com/jsf/core" xml:lang="en" lang="en"> > <h:head> > </h:head> > <h:body> > > <a4j:log hotkey="M" mode="popup" /> > <h:form id="form" prependId="false"> > <rich:tabPanel id="tabPanel"> > <rich:tab header="tab 1"> > <a4j:commandLink value="click me" action="#{testBean.put('clicks',testBean.clicks + 1)}" render="label" execute="@this" /> > </rich:tab> > <rich:tab> > <f:facet name="header"> > <h:outputText id="label" value="#{testBean.clicks} clicks" /> > </f:facet> > </rich:tab> > </rich:tabPanel> > </h:form> > </h:body> > </html> > {code} > testBean is a simple session-scoped HashMap. -- 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, 11 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 January 2014