[JBoss JIRA] (RF-13308) Autocomplete: clientFilterFunction doesn't work in Firefox
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13308?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak closed RF-13308.
------------------------------
I cannot reproduce anymore.
> Autocomplete: clientFilterFunction doesn't work in Firefox
> ----------------------------------------------------------
>
> Key: RF-13308
> URL: https://issues.jboss.org/browse/RF-13308
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, regression
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Mojarra 2.1.19
> EAP 6.1.1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering...
> # set attribute mode to "client"
> # set attribute clientFilterFunction to "customClientFilterFunction"
> # type "no" to the autocomplete
> # select "Raleigh of North Carolina"
> # click outside of autocomplete in order to send selected value to the server
> # check that output contains "North Carolina"
> result:
> * works fine in Chrome 30
> * in Firefox 24, after you type "no", popup with suggestions is not displayed
> * works fine in RichFaces 4.3.4.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
12 years, 4 months
[JBoss JIRA] (RF-13304) Autocomplete: value change listener doesn't work
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13304:
------------------------------------
Verified
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
> Key: RF-13304
> URL: https://issues.jboss.org/browse/RF-13304
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, regression
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression
--
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, 4 months
[JBoss JIRA] (RF-13304) Autocomplete: value change listener doesn't work
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13304?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak closed RF-13304.
------------------------------
> Autocomplete: value change listener doesn't work
> ------------------------------------------------
>
> Key: RF-13304
> URL: https://issues.jboss.org/browse/RF-13304
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input, regression
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> EAP 6.1.1
> Mojarra 2.1.19-jbossorg-1
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Firefox 24 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl... in Firefox 24
> # type 'h' into autocomplete
> # select 'Hawaii'
> # click outside the autocomplete so that the value is sent to the server
> # check phases panel in header
> result:
> * you can see "* 1 value changed: null -> Hawaii" and "* 2 value changed" for a short while
> * after ca. 1s yet another ajax request is done and only "* 2 value changed" is visible
> * in Chrome 30, the second ajax request is not fired
> * in Chrome 30, when you select some nonexisting value in autocomplete, e.g. "xxx", it behaves the same as Firefox 24
> * in RichFaces 4.3.4.Final, output of both listeners is visible, it is a regression
--
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, 4 months
[JBoss JIRA] (RF-13325) pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13325:
----------------------------------
Just tell me if you feel like there should be two issues for these two events. IMHO it is the same issue, with the same root cause.
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-13325
> URL: https://issues.jboss.org/browse/RF-13325
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.
--
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, 4 months
[JBoss JIRA] (RF-13325) pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13325:
-----------------------------
Description:
{{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.
was:{{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-13325
> URL: https://issues.jboss.org/browse/RF-13325
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
> I believe issue for both event handlers is the same, as both occurs when moving the mouse pointer in one of the lists (source list or target list). They should not.
--
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, 4 months
[JBoss JIRA] (RF-13325) pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13325?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13325:
-----------------------------
Description: {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself. (was: {{r:pickList}} event callback for *onmouseout* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.)
> pickList: onmouseout/onmouseover is triggered even when pointer button is not moved out/over element
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-13325
> URL: https://issues.jboss.org/browse/RF-13325
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
>
> {{r:pickList}} event callback for *onmouseout* and *onmouseover* is called even when the mouse pointer does not leave the {{r:pickList}} element itself.
--
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, 4 months