[JBoss JIRA] (RF-13261) Autocomplete: introduce onfocus, onselect, onopen, onclose, onsearch, onresponse event handlers
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13261:
-------------------------------
Summary: Autocomplete: introduce onfocus, onselect, onopen, onclose, onsearch, onresponse event handlers
Key: RF-13261
URL: https://issues.jboss.org/browse/RF-13261
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Lukáš Fryč
Those event handlers are exposed by jQuery UI Autocomplete:
http://api.jqueryui.com/autocomplete/
--
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, 5 months
[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13180:
---------------------------------
As previously discussed, we could incorporate an event which will mean 'the user input changed' or 'the input was changed by the widget' (this is case of calendar, autocomplete, select, inplace select and others). Would you mind to create a issue request for this case?
> Autocomplete: ajax doesn't work with change event
> -------------------------------------------------
>
> Key: RF-13180
> URL: https://issues.jboss.org/browse/RF-13180
> 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
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Blocker
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # select Alabama
> result:
> * ajax request is not fired
> * output is not updated
> * when "change" event in r:ajax is changed to "blur", the use-case works
--
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, 5 months
[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13180:
---------------------------------
[~ppitonak], I believe that with introduction of {{onselect}} event handler we no longer need {{onchange}} event, do you agree?
> Autocomplete: ajax doesn't work with change event
> -------------------------------------------------
>
> Key: RF-13180
> URL: https://issues.jboss.org/browse/RF-13180
> 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
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Blocker
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # select Alabama
> result:
> * ajax request is not fired
> * output is not updated
> * when "change" event in r:ajax is changed to "blur", the use-case works
--
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, 5 months
[JBoss JIRA] (RF-13260) Autocomplete - remove onlist* event handlers
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13260?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13260:
----------------------------
Description:
I believe those onlist* mouse and keyboard handlers are not necessary with exposing rich jQuery UI Autocomplete event API:
http://api.jqueryui.com/autocomplete/
In 4.3, those events could be used for intercepting process of menu manipulation, but the new events are so rich that the list handlers are not necessary.
One can potentially use such a code to register event handler:
{code}
#{r:jquery('autocomplete')}.autocomplete('menu').on('click', );
{code}
was:
I believe those onlist* mouse and keyboard handlers are not necessary with exposing rich jQuery UI Autocomplete event API:
http://api.jqueryui.com/autocomplete/
In 4.3, those events could be used for intercepting process of menu manipulation, but the new events are so rich that the list handlers are not necessary.
> Autocomplete - remove onlist* event handlers
> --------------------------------------------
>
> Key: RF-13260
> URL: https://issues.jboss.org/browse/RF-13260
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: component-input
> Reporter: Lukáš Fryč
> Priority: Minor
>
> I believe those onlist* mouse and keyboard handlers are not necessary with exposing rich jQuery UI Autocomplete event API:
> http://api.jqueryui.com/autocomplete/
> In 4.3, those events could be used for intercepting process of menu manipulation, but the new events are so rich that the list handlers are not necessary.
> One can potentially use such a code to register event handler:
> {code}
> #{r:jquery('autocomplete')}.autocomplete('menu').on('click', );
> {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
12 years, 5 months
[JBoss JIRA] (RF-13260) Autocomplete - remove onlist* event handlers
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13260:
-------------------------------
Summary: Autocomplete - remove onlist* event handlers
Key: RF-13260
URL: https://issues.jboss.org/browse/RF-13260
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: component-input
Reporter: Lukáš Fryč
Priority: Minor
I believe those onlist* mouse and keyboard handlers are not necessary with exposing rich jQuery UI Autocomplete event API:
http://api.jqueryui.com/autocomplete/
In 4.3, those events could be used for intercepting process of menu manipulation, but the new events are so rich that the list handlers are not necessary.
--
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, 5 months
[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13180:
---------------------------------
I can confirm that RF4.3 autocomplete behaves the same way - fire {{change}} event is fired only when input is blurred.
There is {{select}} event which is fired when user selects a value.
> Autocomplete: ajax doesn't work with change event
> -------------------------------------------------
>
> Key: RF-13180
> URL: https://issues.jboss.org/browse/RF-13180
> 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
> JBoss AS 7.2.0.Final-redhat-8
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 29.0.1547.65 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Blocker
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> # select Alabama
> result:
> * ajax request is not fired
> * output is not updated
> * when "change" event in r:ajax is changed to "blur", the use-case works
--
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, 5 months
[JBoss JIRA] (RF-13141) rich:select item Selction not working with huge lists
by J W (JIRA)
[ https://issues.jboss.org/browse/RF-13141?page=com.atlassian.jira.plugin.s... ]
J W commented on RF-13141:
--------------------------
New Knowledge on this issue: it is cause by the calculation of the offset in the __scrollToSelectedItem function. However this does not affect Google Chrome!
> rich:select item Selction not working with huge lists
> -----------------------------------------------------
>
> Key: RF-13141
> URL: https://issues.jboss.org/browse/RF-13141
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component, component-selects
> Affects Versions: 4.3.2
> Reporter: J W
> Labels: select
> Fix For: 5-Tracking
>
>
> 1) Expand the select box with a huge list
> 2) Press and Hold Down Arrow-Key
> 3) after a couple of seconds you can see how the marked item (the last one in the current scroll) is moving out of the visible scroll list.
> 4) at this point the marked item is not visible anymore and you can not mark items anymore by hovering/using ArrowKeys. The Scroll List keeps moving whenever you move your mouse, making it actually impossible to select any item
> Also:
> If you scroll down in a list (20 items) move your mouse to the first partially visible item in the scroll. the scroll box will scroll up and do the same thing again since the mouse is still at the same place indicating the user wants to mark the next partially visible item. the result is,that the scroll scrolls allways 2-3 items heavily irritating the user.
> I guess the __scrollToSelectedItem function in list.js is the reason for this bad behavior.
--
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, 5 months