[JBoss JIRA] (RF-13152) <a4j:support> does not override "literal" inline event handlers (i.e. event handlers which does not contain any EL-expressions)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13152?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13152:
-------------------------------
Fix Version/s: 3.Future
> <a4j:support> does not override "literal" inline event handlers (i.e. event handlers which does not contain any EL-expressions)
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13152
> URL: https://issues.jboss.org/browse/RF-13152
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 3.3.3.Final
> Environment: JSF 1.2
> Reporter: Nicholas Oxhøj
> Priority: Minor
> Fix For: 3.Future
>
> Attachments: test.xhtml
>
>
> If I nest an <a4j:support> inside a component which also has an inline event listener whose text doesn't contain any EL-expressions, the <a4j:support> _won't_ be executed. For example
> {code}
> <h:inputText onchange="alert('Inline listener')">
> <a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
> </h:inputText>
> {code}
> will show an alert with "Inline listener" and *not* perform the <a4j:support>.
> If you add _any_ EL-expression to the inline event listener, the <a4j:support> _will_ be executed instead. For example
> {code}
> <h:inputText onchange="alert('Inline listener')#{''}">
> <a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
> </h:inputText>
> {code}
> *will* show an alert with "a4j:support listener".
> I am not exactly sure how a UIComponents "attributes" and "value expression bindings" are supposed to work together according to the JSF spec, but the problem here seems to be that when the inline listener doesn't contain any EL-expressions, it is stored as an "attribute", but the <a4j:support> is stored as a "value binding expression". Later, during page rendering, HtmlInputText#getOnchange() will first look for an attribute called "onchange" and return that if found. Only if an attribute is not found, it looks for a "value expression binding" and returns that.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi edited comment on RF-13127 at 8/26/13 9:21 AM:
------------------------------------------------------------
New minimal project richfaces.zip to demonstrate issue. Run with mvn jetty:run. Edit multiple fields and see what element is returned by rich:element nested in the onvalid and oninvalid event.
was (Author: parisila):
New minimal project to demonstrate issue
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Labels: waiting_on_user
> Attachments: JSFTemplate.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13127) onvalid and oninvalide pass wrong element when using rich:element with String field
by Louis Parisi (JIRA)
[ https://issues.jboss.org/browse/RF-13127?page=com.atlassian.jira.plugin.s... ]
Louis Parisi updated RF-13127:
------------------------------
Attachment: richfaces.zip
New minimal project to demonstrate issue
> onvalid and oninvalide pass wrong element when using rich:element with String field
> -----------------------------------------------------------------------------------
>
> Key: RF-13127
> URL: https://issues.jboss.org/browse/RF-13127
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.3
> Reporter: Louis Parisi
> Labels: waiting_on_user
> Attachments: JSFTemplate.zip, richfaces.zip
>
>
> I have a bean iterated in a datatable. Using the rich:validator on fields in the bean I am executing javascript when a field is validated and apply styling based on valid or invalid state. The code below returns the correct element when the underlying field is a BigDecimal but intermittently returns the element from row zero and sometimes another rown when the field is a String. If I just reference a String vs. BigDecimal and display the element passed to the javascript I get form:myTable:4:myField for a BigDecimal field and always form:myTable:0:myField no matter the row for a String field.
> {code}
> <h:inputText id="vendor" value="#{car.vendor}" valueChangeListener="#{car.valueChanged}">
> <rich:validator oninvalid="valueModified(#{rich:element('vendor')}, false)"
> onvalid="valueModified(#{rich:element('vendor')}, true)"/>
> </h:inputText>
> {code}
> {code}
> <script>
> function valueModified(element, valid) {
> // use element.style rather than jQuery as it
> // does not set entire background
> alert("valueModified: " + element.id + " | valid: " + valid);
> element.style.background='yellow';
> if (valid) {
> jQuery(element).css("border-color", "lightgray");
> } else {
> jQuery(element).css("border-color", "red");
> }
> }
> </script>
> {code}
> Some other tests I did while trying to debug are:
> * I passed the rowKeyVar to a javascript method in the onvalid event and it passed the correct row for a BigDecimal and always zero for a String field.
> * The oncomplete event of the validator does not seem to fire for a String field but does for a BigDecimal field.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13151) Number of Data Fields in PopUpPanel appear to stop events for DataScroller and sorting of extendedDataTable
by Deb Owsley (JIRA)
[ https://issues.jboss.org/browse/RF-13151?page=com.atlassian.jira.plugin.s... ]
Deb Owsley commented on RF-13151:
---------------------------------
Unfortunately, no.
The page that contains the extendedDataTable, data scroller, and the popup panel (call this pageB.xhtml) is called from PageA.xhtml as an "include". Page A is a tabPanel and has a form tag. Page B used to have a form element, but it was removed because we were told form inside of form is not good. The PopUpPanel also had a form around it, which was removed. When I added the form tag around the popUpPanel it allowed for the 11th and 12th field to be added and still do the sort and paging but was unable to submit the form. ( wasn't able to submit the form without the form element either)
> Number of Data Fields in PopUpPanel appear to stop events for DataScroller and sorting of extendedDataTable
> -----------------------------------------------------------------------------------------------------------
>
> Key: RF-13151
> URL: https://issues.jboss.org/browse/RF-13151
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Deb Owsley
> Labels: waiting_on_user
>
> In my rich:popupPanel, I have 10 elements, as follows:
> {code}
> <a4j:region id="addEquipmentRegion" status="equipmentWaitStatus">
> <rich:popupPanel id="addEquipmentModPanel" autosized="true" width="600" height="400">
> <f:facet name="header"><h:outputText value="Add Equipment"/></f:facet>
> <f:facet name="controls">
> <h:panelGrid>
> <h:graphicImage value="img/close_modal.png" styleClass="hidelink" id="hideAddEquipmentModPanel">
> <rich:componentControl target="addEquipmentModPanel" operation="hide" event="onclick"/>
> </h:graphicImage>
> </h:panelGrid>
> </f:facet>
> <rich:panel id="addEquipmentPanel">
>
> <s:decorate id="equipmentBaseIDDecoration" template="layout/edit.xhtml">
> <ui:define name="label">Base ID</ui:define>
> <rich:select id="addBaseID" enableManualInput="true" required="true"
> value="#{equipmentHome.instance.baseID}">
> <f:selectItems value="#{entityAttribute.baseIDs}"/>
> </rich:select>
> </s:decorate>
> .....
> {code}
> This popup panel is called from a button on one of my pages that contains a data scroller and an extendedDataTable.
> If I add an 11th element inside of my PopUpPanel, then all data scrolling and sorting in the extendedDataTable stops working.
> I have removed different elements from the popup and it doesn't matter. As long as I only have 10 all events fire. As soon as there are 11, everything stops.
> I get absolutely no errors in my jboss console.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13152) <a4j:support> does not override "literal" inline event handlers (i.e. event handlers which does not contain any EL-expressions)
by Nicholas Oxhøj (JIRA)
[ https://issues.jboss.org/browse/RF-13152?page=com.atlassian.jira.plugin.s... ]
Nicholas Oxhøj updated RF-13152:
--------------------------------
Summary: <a4j:support> does not override "literal" inline event handlers (i.e. event handlers which does not contain any EL-expressions) (was: <a4j:support> does not override literal event handlers without EL-espressions)
> <a4j:support> does not override "literal" inline event handlers (i.e. event handlers which does not contain any EL-expressions)
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13152
> URL: https://issues.jboss.org/browse/RF-13152
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 3.3.3.Final
> Environment: JSF 1.2
> Reporter: Nicholas Oxhøj
> Priority: Minor
> Attachments: test.xhtml
>
>
> If I nest an <a4j:support> inside a component which also has an inline event listener whose text doesn't contain any EL-expressions, the <a4j:support> _won't_ be executed. For example
> {code}
> <h:inputText onchange="alert('Inline listener')">
> <a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
> </h:inputText>
> {code}
> will show an alert with "Inline listener" and *not* perform the <a4j:support>.
> If you add _any_ EL-expression to the inline event listener, the <a4j:support> _will_ be executed instead. For example
> {code}
> <h:inputText onchange="alert('Inline listener')#{''}">
> <a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
> </h:inputText>
> {code}
> *will* show an alert with "a4j:support listener".
> I am not exactly sure how a UIComponents "attributes" and "value expression bindings" are supposed to work together according to the JSF spec, but the problem here seems to be that when the inline listener doesn't contain any EL-expressions, it is stored as an "attribute", but the <a4j:support> is stored as a "value binding expression". Later, during page rendering, HtmlInputText#getOnchange() will first look for an attribute called "onchange" and return that if found. Only if an attribute is not found, it looks for a "value expression binding" and returns that.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13152) <a4j:support> does not override literal event handlers without EL-espressions
by Nicholas Oxhøj (JIRA)
[ https://issues.jboss.org/browse/RF-13152?page=com.atlassian.jira.plugin.s... ]
Nicholas Oxhøj updated RF-13152:
--------------------------------
Attachment: test.xhtml
Example showing the erroneous behavior.
> <a4j:support> does not override literal event handlers without EL-espressions
> -----------------------------------------------------------------------------
>
> Key: RF-13152
> URL: https://issues.jboss.org/browse/RF-13152
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 3.3.3.Final
> Environment: JSF 1.2
> Reporter: Nicholas Oxhøj
> Priority: Minor
> Attachments: test.xhtml
>
>
> If I nest an <a4j:support> inside a component which also has an inline event listener whose text doesn't contain any EL-expressions, the <a4j:support> _won't_ be executed. For example
> {code}
> <h:inputText onchange="alert('Inline listener')">
> <a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
> </h:inputText>
> {code}
> will show an alert with "Inline listener" and *not* perform the <a4j:support>.
> If you add _any_ EL-expression to the inline event listener, the <a4j:support> _will_ be executed instead. For example
> {code}
> <h:inputText onchange="alert('Inline listener')#{''}">
> <a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
> </h:inputText>
> {code}
> *will* show an alert with "a4j:support listener".
> I am not exactly sure how a UIComponents "attributes" and "value expression bindings" are supposed to work together according to the JSF spec, but the problem here seems to be that when the inline listener doesn't contain any EL-expressions, it is stored as an "attribute", but the <a4j:support> is stored as a "value binding expression". Later, during page rendering, HtmlInputText#getOnchange() will first look for an attribute called "onchange" and return that if found. Only if an attribute is not found, it looks for a "value expression binding" and returns that.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13152) <a4j:support> does not override literal event handlers without EL-espressions
by Nicholas Oxhøj (JIRA)
Nicholas Oxhøj created RF-13152:
-----------------------------------
Summary: <a4j:support> does not override literal event handlers without EL-espressions
Key: RF-13152
URL: https://issues.jboss.org/browse/RF-13152
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-a4j-core
Affects Versions: 3.3.3.Final
Environment: JSF 1.2
Reporter: Nicholas Oxhøj
Priority: Minor
If I nest an <a4j:support> inside a component which also has an inline event listener whose text doesn't contain any EL-expressions, the <a4j:support> _won't_ be executed. For example
{code}
<h:inputText onchange="alert('Inline listener')">
<a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
</h:inputText>
{code}
will show an alert with "Inline listener" and *not* perform the <a4j:support>.
If you add _any_ EL-expression to the inline event listener, the <a4j:support> _will_ be executed instead. For example
{code}
<h:inputText onchange="alert('Inline listener')#{''}">
<a4j:support event="onchange" onsubmit="alert('a4j:support listener')" />
</h:inputText>
{code}
*will* show an alert with "a4j:support listener".
I am not exactly sure how a UIComponents "attributes" and "value expression bindings" are supposed to work together according to the JSF spec, but the problem here seems to be that when the inline listener doesn't contain any EL-expressions, it is stored as an "attribute", but the <a4j:support> is stored as a "value binding expression". Later, during page rendering, HtmlInputText#getOnchange() will first look for an attribute called "onchange" and return that if found. Only if an attribute is not found, it looks for a "value expression binding" and returns that.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reopened RF-13046:
--------------------------------
Scrollers are rendered and visible in 4.3.4.Final. However, horizontal scroller doesn't work, after ajax it starts working fine.
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richExtendedDataTable/froz...
# scroll with horizontal scroller (result: nothing happens)
# switch to second page using data scroller
# scroll with horizontal scroller (result: scroller works)
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
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
12 years, 7 months
[JBoss JIRA] (RF-13125) a4j:log does swallow the message from jsf.js's sendError method
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13125?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13125:
------------------------------------
Lukas, could you please provide some information about how to reproduce this issue?
> a4j:log does swallow the message from jsf.js's sendError method
> ---------------------------------------------------------------
>
> Key: RF-13125
> URL: https://issues.jboss.org/browse/RF-13125
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3, 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> {code:title=jsf.js:2220}
> } catch (ex) {
> sendError(request, context, "malformedXML", ex.message);
> return;
> }
> {code}
> The ex.message is not shown in output of a4j:log.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13035) Simpleapp Archetype: mobile version shows modal dialog
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13035?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reopened RF-13035:
--------------------------------
Stille reproducible in 4.3.4.Final in all browsers.
> Simpleapp Archetype: mobile version shows modal dialog
> -------------------------------------------------------
>
> Key: RF-13035
> URL: https://issues.jboss.org/browse/RF-13035
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 4.1.0.Final, 5.0.0.Alpha1
> Reporter: Jan Papousek
> Assignee: Brian Leathem
> Fix For: 4.3.4, 5.0.0.Alpha2
>
> Attachments: modal-iphone.png, richfaces-simpleapp-jee6.war, simpleapp-modal.png
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> When the simpleapp archetype is built with "-Dmobile-optimized=true", the welcome page shows modal dialog (see screenshot).
--
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
12 years, 7 months