[JBoss JIRA] (RF-13184) Autocomplete: hide attribute layout since it is auto-detected
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13184?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13184:
----------------------------
Summary: Autocomplete: hide attribute layout since it is auto-detected (was: Autocomplete: remove option layout since it's not needed anymore)
> Autocomplete: hide attribute layout since it is auto-detected
> -------------------------------------------------------------
>
> Key: RF-13184
> URL: https://issues.jboss.org/browse/RF-13184
> 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: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved)
> # set layout=div in autocomplete.xhtml
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> result:
> * ajax request is fired
> * status in page's header shows "ERROR"
--
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-13184) Autocomplete: remove option layout since it's not needed anymore
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13184?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13184:
----------------------------
Summary: Autocomplete: remove option layout since it's not needed anymore (was: Autocomplete: ajax completely broken when attribute layout is set)
> Autocomplete: remove option layout since it's not needed anymore
> ----------------------------------------------------------------
>
> Key: RF-13184
> URL: https://issues.jboss.org/browse/RF-13184
> 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: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved)
> # set layout=div in autocomplete.xhtml
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> result:
> * ajax request is fired
> * status in page's header shows "ERROR"
--
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-13184) Autocomplete: ajax completely broken when attribute layout is set
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13184?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13184:
---------------------------------
We don't need the 'layout' attribute as the widget itself auto-detects layout.
> Autocomplete: ajax completely broken when attribute layout is set
> -----------------------------------------------------------------
>
> Key: RF-13184
> URL: https://issues.jboss.org/browse/RF-13184
> 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: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> # (change event from "change" to "blur" in autocomplete.xhtml when RF-13180 is not resolved)
> # set layout=div in autocomplete.xhtml
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/autocompl...
> # type "a" into input
> result:
> * ajax request is fired
> * status in page's header shows "ERROR"
--
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-10227) autocomplete: implement "nothingLabel"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-10227?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-10227 at 10/11/13 1:03 PM:
-----------------------------------------------------------
Guys, even though I find it understand your requirements,
I'm not sure the 'nothingLabel' is actually good approach:
autocomplete doesn't serve the purpose of selection from choices, but rather suggesting when match is found.
If you want nothingLabel, I would suggest to use rich:select, which I believe should have this functionality.
rich:select provides your with a set of options your input is limited to. That's why it make sense to report user no valid option was found
/wrt the input he provided.
----
Without philosophical questions,
It seems jQuery UI Autocomnplete (which Rich Autocomplete is based on) also doesn't has this functionality built-in,
and people suggest to use such workarounds: http://stackoverflow.com/questions/4141945/jquery-ui-autocomplete-show-so...
If you want to help to proceed with this issue, please create an issue in [RichWidgets issue tracker|https://github.com/richwidgets/richwidgets/issues?state=open] first and we can discuss impl details there.
was (Author: lfryc):
Guys, even though I find it understand your requirements,
I'm not sure the 'nothingLabel' is actually good approach:
autocomplete doesn't serve the purpose of selection from choices, but rather suggesting when match is found.
If you want nothingLabel, I would suggest to use rich:select, which I believe should have this functionality.
rich:select provides your with a set of options your input is limited to. That's why it make sense to report user no valid option was found
/wrt the input he provided.
----
Without philosophical questions,
It seems jQuery UI Autocomnplete (which Rich Autocomplete is based on) also doesn't has this functionality built-in,
and people suggest to use such workarounds: http://stackoverflow.com/questions/4141945/jquery-ui-autocomplete-show-so...
If you want to help to proceed with this issue, please create an issue in RichWidgets issue tracker first and we can discuss impl details there.
> autocomplete: implement "nothingLabel"
> --------------------------------------
>
> Key: RF-10227
> URL: https://issues.jboss.org/browse/RF-10227
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: base functionality, component-input
> Affects Versions: 4.0.0.Milestone5
> Reporter: Juergen Zimmermann
> Fix For: 5-Future
>
>
> rich:autocomplete doesn't have an attribute for a "nothingLabel" to indicate that there are no matches
--
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-10227) autocomplete: implement "nothingLabel"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-10227?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-10227 at 10/11/13 1:03 PM:
-----------------------------------------------------------
Guys, even though I understand your requirements,
I'm not sure the 'nothingLabel' is actually good approach:
autocomplete doesn't serve the purpose of selection from choices, but rather suggesting when match is found.
If you want nothingLabel, I would suggest to use rich:select, which I believe should have this functionality.
rich:select provides your with a set of options your input is limited to. That's why it make sense to report user no valid option was found
/wrt the input he provided.
----
Without philosophical questions,
It seems jQuery UI Autocomnplete (which Rich Autocomplete is based on) also doesn't has this functionality built-in,
and people suggest to use such workarounds: http://stackoverflow.com/questions/4141945/jquery-ui-autocomplete-show-so...
If you want to help to proceed with this issue, please create an issue in [RichWidgets issue tracker|https://github.com/richwidgets/richwidgets/issues?state=open] first and we can discuss impl details there.
was (Author: lfryc):
Guys, even though I find it understand your requirements,
I'm not sure the 'nothingLabel' is actually good approach:
autocomplete doesn't serve the purpose of selection from choices, but rather suggesting when match is found.
If you want nothingLabel, I would suggest to use rich:select, which I believe should have this functionality.
rich:select provides your with a set of options your input is limited to. That's why it make sense to report user no valid option was found
/wrt the input he provided.
----
Without philosophical questions,
It seems jQuery UI Autocomnplete (which Rich Autocomplete is based on) also doesn't has this functionality built-in,
and people suggest to use such workarounds: http://stackoverflow.com/questions/4141945/jquery-ui-autocomplete-show-so...
If you want to help to proceed with this issue, please create an issue in [RichWidgets issue tracker|https://github.com/richwidgets/richwidgets/issues?state=open] first and we can discuss impl details there.
> autocomplete: implement "nothingLabel"
> --------------------------------------
>
> Key: RF-10227
> URL: https://issues.jboss.org/browse/RF-10227
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: base functionality, component-input
> Affects Versions: 4.0.0.Milestone5
> Reporter: Juergen Zimmermann
> Fix For: 5-Future
>
>
> rich:autocomplete doesn't have an attribute for a "nothingLabel" to indicate that there are no matches
--
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-10227) autocomplete: implement "nothingLabel"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-10227?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-10227:
---------------------------------
Guys, even though I find it understand your requirements,
I'm not sure the 'nothingLabel' is actually good approach:
autocomplete doesn't serve the purpose of selection from choices, but rather suggesting when match is found.
If you want nothingLabel, I would suggest to use rich:select, which I believe should have this functionality.
rich:select provides your with a set of options your input is limited to. That's why it make sense to report user no valid option was found
/wrt the input he provided.
----
Without philosophical questions,
It seems jQuery UI Autocomnplete (which Rich Autocomplete is based on) also doesn't has this functionality built-in,
and people suggest to use such workarounds: http://stackoverflow.com/questions/4141945/jquery-ui-autocomplete-show-so...
If you want to help to proceed with this issue, please create an issue in RichWidgets issue tracker first and we can discuss impl details there.
> autocomplete: implement "nothingLabel"
> --------------------------------------
>
> Key: RF-10227
> URL: https://issues.jboss.org/browse/RF-10227
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: base functionality, component-input
> Affects Versions: 4.0.0.Milestone5
> Reporter: Juergen Zimmermann
> Fix For: 5-Future
>
>
> rich:autocomplete doesn't have an attribute for a "nothingLabel" to indicate that there are no matches
--
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-10227) autocomplete: implement "nothingLabel"
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-10227?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-10227:
------------------------------------
[~ibenjes] this is a low-vote and hence low-priority issue. Either more votes or a Pull Request will be required to move this feature forward.
Checking with [~lfryc] to see if this is possibly a feature implemented in the RichFaces 5 autocomplete client-side rewrite.
> autocomplete: implement "nothingLabel"
> --------------------------------------
>
> Key: RF-10227
> URL: https://issues.jboss.org/browse/RF-10227
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: base functionality, component-input
> Affects Versions: 4.0.0.Milestone5
> Reporter: Juergen Zimmermann
> Fix For: 5-Future
>
>
> rich:autocomplete doesn't have an attribute for a "nothingLabel" to indicate that there are no matches
--
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-13256) CDI Push does not work in Firefox 17
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13256?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13256:
-------------------------------
Fix Version/s: 4.3.5
> CDI Push does not work in Firefox 17
> ------------------------------------
>
> Key: RF-13256
> URL: https://issues.jboss.org/browse/RF-13256
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-push/poll
> Affects Versions: 4.3.4
> Reporter: Oliver Kišš
> Fix For: 4.3.5
>
>
> CDI Push does not work in Firefox 17.
> To reproduce, see [CDI Push sample |http://showcase.richfaces.org/richfaces/component-sample.jsf?demo=push&sample=pushCdi&skin=blueSky] in Richfaces Showcase. Added messages are not visible in the Messages Consumer window.
> I could not see any errors in the developer 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, 5 months