May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12934) ajax request for rich:tooltip should respect the showDelay parameter

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12934?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12934: ------------------------------- Fix Version/s: 5-Tracking > ajax request for rich:tooltip should respect the showDelay parameter > -------------------------------------------------------------------- > > Key: RF-12934 > URL: https://issues.jboss.org/browse/RF-12934 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.2.1.Final > Reporter: Guillaume Morin-Brassard > Fix For: 5-Tracking > > > A rich:tooltip with mode="ajax" should not trigger the ajax request until the delay specified by the showDelay attribute is expired. > Otherwise, when we quickly move the mouse over multiple components to which ajax tooltips are attached, multiple ajax request are triggered and they flood the ajax request buffer. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12932) <rich:tab> render-attribute does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12932?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-12932. -------------------------------- Resolution: Duplicate Issue This issue has been resolved in RichFaces 4.3.2.CR1. > <rich:tab> render-attribute does not work > ----------------------------------------- > > Key: RF-12932 > URL: https://issues.jboss.org/browse/RF-12932 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Reporter: Alexey Shakov > > render attribute of rich:tab-Component is ignored. > In the following example, clicks on tab1 and tab2 do not re-render panelGroup with id="x", but clicks on link1 and link2 do the job. > {code:xml} > <h:form> > <rich:tabPanel> > <rich:tab header="tab1" render="x"> > <a4j:commandLink value="link1" render="x" /> > </rich:tab> > <rich:tab header="tab2" render="x"> > <a4j:commandLink value="link2" render="x" /> > </rich:tab> > </rich:tabPanel> > <h:panelGroup id="x"> > <h:outputText value="#{baseBean.currentDate}"> > <f:convertDateTime pattern="dd-MM-yyyy HH:mm:ss" /> > </h:outputText> > </h:panelGroup> > </h:form> > {code} > (This snippet works with RF 4.2.1.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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12931) rich:fileupload broken with recent versions of mojarra

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12931?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12931: ---------------------------------- Assignee: Pavol Pitonak [~ppitonak] please verify. > rich:fileupload broken with recent versions of mojarra > ------------------------------------------------------ > > Key: RF-12931 > URL: https://issues.jboss.org/browse/RF-12931 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1 > Environment: Glassfish 3.2.1.1, Mojarra 2.1.21 > Reporter: Frederick Kämpfer > Assignee: Pavol Pitonak > Priority: Critical > Labels: javascript > > On recent versions of Mojarra the following simple fileupload facelet page produces an javascript error: > {code:xml} > <!DOCTYPE html> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:rich="http://richfaces.org/rich" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:a4j="http://richfaces.org/a4j" > xmlns:c="http://java.sun.com/jsp/jstl/core"> > <f:view> > <h:head> > </h:head> > <h:body> > <script type="text/javascript"> > jsf.ajax.addOnError(function(e) { > console.log(e); > alert("An error occured:\n" + e.errorName + '\n' + e.description); > }); > </script> > <h:form> > <rich:fileUpload/> > </h:form> > </h:body> > </f:view> > </html> > {code} > The problem seems to be that the context.element parameter is undefined in jsf.ajax.response. Probably due to RichFaces' Javascript extensions. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12923) rich:notifyMessage, notifyMessages: some attributes are not applied to created message component

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12923?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12923: ------------------------------- Fix Version/s: 5-Tracking > rich:notifyMessage, notifyMessages: some attributes are not applied to created message component > ------------------------------------------------------------------------------------------------ > > Key: RF-12923 > URL: https://issues.jboss.org/browse/RF-12923 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Fix For: 5-Tracking > > > Attributes: style (styleClass is applied), title, dir* and lang* are only applied to created empty span element of the component, but not for the created message. > *rich:notify doesn't contain these attributes -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12924) rich:notifyMessage(s): add information about for which id they were created

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12924?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12924: ------------------------------- Fix Version/s: 5-Tracking > rich:notifyMessage(s): add information about for which id they were created > --------------------------------------------------------------------------- > > Key: RF-12924 > URL: https://issues.jboss.org/browse/RF-12924 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators > Reporter: Jiří Štefek > Priority: Minor > Fix For: 5-Tracking > > > The created rich:notifyMessage(s) don't include an id of which input it was created for, but the rich:message(s) do (in theirs @id). Wouldn't it be possible to include such information somewhere? -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12925) rich:notify, notifyMessage, notifyMessages: no detail and no summary

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12925?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12925: ------------------------------- Fix Version/s: 5-Tracking > rich:notify, notifyMessage, notifyMessages: no detail and no summary > -------------------------------------------------------------------- > > Key: RF-12925 > URL: https://issues.jboss.org/browse/RF-12925 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Fix For: 5-Tracking > > > Consider, when: > * rich:notify: @summary and @detail are empty, > * rich:notifyMessage(s): @showSummary=false and @showDetail=false, > should these empty messages be created/rendered? > The rich:message(s) components aren't displayed if these conditions apply. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12929) PickList change event not firing correctly when ordering objects in target area

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12929?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12929: ------------------------------- Fix Version/s: 5-Tracking > PickList change event not firing correctly when ordering objects in target area > ------------------------------------------------------------------------------- > > Key: RF-12929 > URL: https://issues.jboss.org/browse/RF-12929 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 4.3.0.Final > Environment: JBoss AS 7 > Reporter: Simon Plangger > Labels: event, onchange, pickList > Fix For: 5-Tracking > > > The *change* event is not firing, when moving an element from the target area (selected side) to the top or to the bottom of the list. There is no problem with moving items and the change event as long as you don't make it the first or last entry. > To reproduce: > {code} > <rich:pickList > onchange="alert('changed')" > orderable="true" > > > <f:selectItem itemLabel="test 1" itemValue="test 1" /> > <f:selectItem itemLabel="test 2" itemValue="test 2" /> > <f:selectItem itemLabel="test 3" itemValue="test 3" /> > <f:selectItem itemLabel="test 4" itemValue="test 4" /> > <f:selectItem itemLabel="test 5" itemValue="test 5" /> > </rich:pickList> > {code} > Just *select all* items and move them around. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12926) rich:notify: ecss contains old (and unused) styleClasses for history

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12926?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12926: ------------------------------- Fix Version/s: 5-Tracking > rich:notify: ecss contains old (and unused) styleClasses for history > -------------------------------------------------------------------- > > Key: RF-12926 > URL: https://issues.jboss.org/browse/RF-12926 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > Reporter: Jiří Štefek > Priority: Minor > Fix For: 5-Tracking > > > Remove redundant (from old version of rich:notify*, from RF 4.3.X) all styles and resources for rich:notify* history. > Styles in notify.ecss: > * rf-ntf-hstr > * rf-ntf-hstr-hdr > * rf-ntf-hstr button > * rf-ntf-hstr-hndl -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12920) rich:validator: and message(s) component with invalid or empty @for

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12920?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12920: ------------------------------- Fix Version/s: 5-Tracking > rich:validator: and message(s) component with invalid or empty @for > ------------------------------------------------------------------- > > Key: RF-12920 > URL: https://issues.jboss.org/browse/RF-12920 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Fix For: 5-Tracking > > > Validation on client side. > When a message(s) component is using invalid or empty @for, then the component will show validation messages for all validated inputs. > But when you submit the form (ajax/http) there will be no messages in this component. > Message components: rich:message, rich:messages, rich:notifyMessage, rich:notifyMessages. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12922) rich:validator: only first message from multiple validation will appear

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12922?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12922: ---------------------------------- Assignee: Jiří Štefek Can you compare the rich:messages behaviour in this regard to the h:messages behaviour? > rich:validator: only first message from multiple validation will appear > ----------------------------------------------------------------------- > > Key: RF-12922 > URL: https://issues.jboss.org/browse/RF-12922 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Environment: RichFaces 4.3.2-SNAPSHOT > Metamer 5.0.0-SNAPSHOT > JBoss AS 7.1.1.Final > Java(TM) SE Runtime Environment 1.7.0_09-b05 @ Linux > Firefox 18.0 @ Linux x86_64 > Reporter: Jiří Štefek > Assignee: Jiří Štefek > > When an input is validated by e.g. 2 rules and the value put in it does not pass both validations, only one message is displayed to the client. > Is it intention? > Message components: rich:messages and rich:notifyMessages -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2013