March 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12057) IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request

by Gurinder Randhawa (JIRA)

Gurinder Randhawa created RF-12057: -------------------------------------- Summary: IE 8 rich:toolTip client side toolTip has problems rendering upon ajax request Key: RF-12057 URL: https://issues.jboss.org/browse/RF-12057 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output Affects Versions: 4.1.0.Final Environment: Windows 7, IE 8 Reporter: Gurinder Randhawa Rich:Tooltip in client mode does not refresh upon an ajax event specifically in IE 8. A large part of external clients utilize IE 8 unfortunately. The tool tip is working correctly in IE 9, chrome and FF 7+. The tool tip is refreshed on next ajax request with "previous" ajax response. TOOL TIP CODE: =============== <rich:tooltip id="ttPriceBreakDown" styleClass="toolTip" for="totalPrice" mode="client"> <table class="toolTipTable1" border="0" cellpadding="2" cellspacing="0"> <tr> <td><h:outputText id="lblBase1" value="Base" styleClass="fieldLabel" /></td> <td></td> <td><h:outputText id="basePrice1" value="#{pp_.baseRate.price.total}"> <f:convertNumber type="currency" currencySymbol="$" maxFractionDigits="2" /> </h:outputText></td> </tr> <a4j:repeat id="rptFactors1" value="#{pp_.factorInputs}" var="factor"> <tr> <td><h:outputText id="factorDisplayName1" value="#{factor.displayName}" /></td> <td><h:outputText id="factorValue1" value="#{factor.value}" /></td> <td></td> </tr> </a4j:repeat> <a4j:repeat id="rptModifiers1" value="#{pp_.modifierPrices}" var="modifier"> <tr> <ui:fragment rendered="#{modifier.isDiscount()}"> <td><h:outputText id="priceDisc" rendered="#{modifier.calculated}" value="#{modifier.displayName}" styleClass="fieldLabel" /></td> </ui:fragment> <ui:fragment rendered="#{modifier.isRider()}"> <td><h:outputText id="priceRider" rendered="#{modifier.calculated}" value="#{modifier.displayName}" styleClass="fieldLabel" /></td> </ui:fragment> <ui:fragment rendered="#{not modifier.isRiderOrDiscount()}"> <td><h:outputText id="priceOther" rendered="#{modifier.calculated}" value="#{modifier.modifierType.name}" styleClass="fieldLabel" /></td> </ui:fragment> <td><h:outputText id="minFlag1" value="#{m_.min}" rendered="#{modifier.calculated}, #{modifier.applied.minimum}" /> <h:outputText id="maxFlag1" value="#{m_.max}" rendered="#{modifier.calculated}, #{modifier.applied.maximum}" /></td> <td><h:outputText id="modifierPriceTotal1" rendered="#{modifier.calculated}" value="#{modifier.price.total}"> <f:convertNumber type="currency" currencySymbol="$" /> </h:outputText></td> </tr> </a4j:repeat> <a4j:outputPanel> <tr> <td><h:outputText id="lblTotal" value="Total" styleClass="fieldLabel" /></td> <td></td> <td><h:outputText id="ttTotalPrice" value="#{pp_.price.total}"> <f:convertNumber type="currency" currencySymbol="$" /> </h:outputText></td> </tr> </a4j:outputPanel> <a4j:outputPanel> <tr> <td><h:outputText id="lblRated1" value="Rated" styleClass="fieldLabel" /></td> <td></td> <td><h:outputText id="ratedPrice1" value="#{pp_.lockable.target.ratedPrice.total}"> <f:convertNumber type="currency" currencySymbol="$" /> </h:outputText></td> </tr> <tr> <td><h:outputText id="lblCharged1" value="Charged" styleClass="fieldLabel" /></td> <td></td> <td><h:outputText id="chargedPrice1" value="#{pp_.price.total}"> <f:convertNumber type="currency" currencySymbol="$" /> </h:outputText></td> </tr> </a4j:outputPanel> </table> </rich:tooltip> AJAX REQUEST CODE, SELECTABLE CHECKBOX WHICH RE-RENDERS TOOLTIP =============================================================== <h:selectBooleanCheckbox value="#{pp_.selected}" rendered="#{pp_.hasCoverageAssigned()}" disabled="#{pp_.selectDisabled}" id="cbInsured"> <a4j:ajax listener="#{pp_.selectionChanged}" execute="@this" render="#{renderIds},#{selectionChangeRenderIds}" /> </h:selectBooleanCheckbox> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (RF-12055) horizontal scrollbar is not working properly by using ScrollableDataTable, with one column

by lakshmee n (JIRA)

lakshmee n created RF-12055: ------------------------------- Summary: horizontal scrollbar is not working properly by using ScrollableDataTable, with one column Key: RF-12055 URL: https://issues.jboss.org/browse/RF-12055 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: lakshmee n -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (RF-12054) TabPanel onitemchange of outer tab fired by inner tab

by Przemysław Dębski (JIRA)

Przemysław Dębski created RF-12054: -------------------------------------- Summary: TabPanel onitemchange of outer tab fired by inner tab Key: RF-12054 URL: https://issues.jboss.org/browse/RF-12054 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Reporter: Przemysław Dębski When changing outer tab, "onitemchange" event of outer tab is fired and alert with text 'onitemchange' is shown. But when changing inner tab both "onitemchange" event of outer tab and inner tab are fired and two alerts are show, one with text 'onitemchange' and second with 'onitemchange inner'. It's wrong behaviour, because outer tab is not switched and its "onitemchange" event shouldn't be fired. Same situation with "onbeforeitemchange". Page code to reproduce: {code:xml} <html contentType="text/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:f="http://java.sun.com/jsf/core" xmlns:rich="http://richfaces.org/rich"> <h:head></h:head> <h:body> <h:form> <rich:tabPanel onitemchange="alert('onitemchange')"> <rich:tab name="tab1" header="tab1">tab1</rich:tab> <rich:tab name="tab2" header="tab2"> <rich:tabPanel onitemchange="alert('onitemchange inner')"> <rich:tab name="tabinner1" header="tab inner 1">tab inner 1</rich:tab> <rich:tab name="tabinner2" header="tab inner 2">tab inner 2</rich:tab> </rich:tabPanel> </rich:tab> </rich:tabPanel> </h:form> </h:body> </html> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (RF-12047) Add "global" attribute to graphValidator

by Gerald Turner (JIRA)

Gerald Turner created RF-12047: ---------------------------------- Summary: Add "global" attribute to graphValidator Key: RF-12047 URL: https://issues.jboss.org/browse/RF-12047 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.2.0.Final Reporter: Gerald Turner Priority: Trivial graphValidator appends FacesMessages to the FacesContext with clientId set to the clientId of the graphValidator component, naturally, however I have a use-case for not assigning a clientId to those FacesMessages at all (null, global messages). The following example exhibits how graphValidator currently works: <rich:messages for="gv"/> <rich:graphValidator id="gv" .../> What I'm asking for is the following: <p:messages globalOnly="true"/> <rich:graphValidator id="gv" global="true" .../> (Conversely I could wishlist PrimeFaces to add a 'for' attribute to their 'messages' component, something like 'for="@global gv"', so no harm in closing this report ;-) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (RF-12046) JSR303 ConstraintViolation propertyPath support for graphValidator

by Gerald Turner (JIRA)

Gerald Turner created RF-12046: ---------------------------------- Summary: JSR303 ConstraintViolation propertyPath support for graphValidator Key: RF-12046 URL: https://issues.jboss.org/browse/RF-12046 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-validators Affects Versions: 4.2.0.Final Reporter: Gerald Turner Priority: Optional In JSR303 § 4.2 ConstraintViolation, there is the following note: "From rootBean and propertyPath, it is possible to rebuild the context of the failure" Perhaps it would be possible for graphValidator to map ConstraintViolation propertyPath to ValueExpressions, then iterate child EditableValueHolder components and assign FacesMessages to clientIds of these components where it finds a match, otherwise fallback on the current behavior of using the clientId of the graphValidator itself (perhaps even adding an the option to use a null clientId for global messages instead). A more thorough example of this use-case is here: http://stackoverflow.com/questions/5639088/cross-field-validation-with-in... Comments at stackoverflow suggest MyFaces ExtVal Bean Validation can do the trick, however I went down that road, their framework ignores ConstraintViolation propertyPath as well (see: http://old.nabble.com/Re%3A-ExtVal-BV-question-to33455513.html) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (RF-12045) Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers

by Jan Papousek (JIRA)

Jan Papousek created RF-12045: --------------------------------- Summary: Metamer: focusing of rich:inplaceInput behaves in Google Chrome differently than in other browsers Key: RF-12045 URL: https://issues.jboss.org/browse/RF-12045 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final Java(TM) SE Runtime Environment 1.6.0_31-b04 @ Linux Chrome 17.0.963.78 @ Linux i686 Reporter: Jan Papousek Priority: Optional After clicking on rich:inplaceInput in Firefox, the cursor is placed in the beginning of the input and nothing is selected. Doing the same in Google Chrome - the text in the input is selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (RF-12039) fileupload: attribute data does not work

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12039: -------------------------------- Summary: fileupload: attribute data does not work Key: RF-12039 URL: https://issues.jboss.org/browse/RF-12039 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss Web 7.0.10.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 10.0.1 @ Linux x86_64 Chrome 17.0.963.56 @ Linux i686 Reporter: Jiří Štefek # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Set attribute data = 'RichFaces 4' # Set attribute onuploadcomplete = alert(event.data) # Upload file # Alert with "RichFaces 4" should show -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (RF-12037) Fileupload:onbegin, oncomplete and onbeforedomupdate does not work

by Jiří Štefek (JIRA)

Jiří Štefek created RF-12037: -------------------------------- Summary: Fileupload:onbegin, oncomplete and onbeforedomupdate does not work Key: RF-12037 URL: https://issues.jboss.org/browse/RF-12037 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input Affects Versions: 4.2.0.Final Environment: RichFaces 4.2.1-SNAPSHOT Metamer 4.2.1-SNAPSHOT Mojarra 2.1.5-SNAPSHOT JBoss AS 7.1.0.Final OpenJDK Runtime Environment 1.6.0_24-b24 @ Linux Firefox 10.0.1 @ Linux x86_64 Chrome 17.0.963.56 @ Linux i686 Reporter: Jiří Štefek # Deploy metamer # open http://localhost:8080/metamer/faces/components/richFileUpload/simple.xhtml # Attribute onbegin=alert('1') # Attribute onbeforedomupdate=alert('2') # Attribute oncomplete=alert('3') # Upload file # 3 alerts should show -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[JBoss JIRA] (RF-12036) showcase - rich:progressBar - client side mode of progressBar halts another progress bar in AJAX mode

by Juraj Huska (JIRA)

Juraj Huska created RF-12036: -------------------------------- Summary: showcase - rich:progressBar - client side mode of progressBar halts another progress bar in AJAX mode Key: RF-12036 URL: https://issues.jboss.org/browse/RF-12036 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-output, showcase Affects Versions: 4.2.0.Final Environment: browsers: Firefox 10, Chrome 17 Reporter: Juraj Huska When you have open both samples for the rich:progressBar at the same browser(in separated cards), and run Ajax mode one and during of execution of this one also the client mode one, then the Ajax one is halted. The server updates are still coming for that Ajax one, however the visual state is not updated. It is not restored even when the second one is completed. This is noticeable on showcase since RF 4.0.0.Final, and reproducible on GAE or OpenShift accounts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] (RF-12034) Accepting multiple date format in rich calendar

by Sunil Chauraha (JIRA)

Sunil Chauraha created RF-12034: ----------------------------------- Summary: Accepting multiple date format in rich calendar Key: RF-12034 URL: https://issues.jboss.org/browse/RF-12034 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sunil Chauraha -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues March 2012