[JBoss JIRA] (RF-13180) Autocomplete: ajax doesn't work with change event
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13180:
------------------------------------
Every "editable value holder" component should have a change event. The only point up for debate is whether it's fired after a user selects a value, or after the component is blurred (and the value has changed since it received focus).
IMO we should stick to the HTML input semantics that the change event is fired after blur, but we should provide an event whenever the user changes the value. The analogous event for the input component might be the "keypress" event.
> 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-13177) rich:extendedDataTable scrolling broken on OS-X
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13177:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
(was: 5-Tracking)
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
> Assignee: Matej Novotny
> Labels: osx
> Fix For: 5.0.0.Alpha3
>
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
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-13177) rich:extendedDataTable scrolling broken on OS-X
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13177?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13177:
-------------------------------
Component/s: component-tables
> rich:extendedDataTable scrolling broken on OS-X
> -----------------------------------------------
>
> Key: RF-13177
> URL: https://issues.jboss.org/browse/RF-13177
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality, component-tables
> Affects Versions: 4.3.3
> Environment: OS-X 10.8.3, Chrome 29.0.1547.62 or Safari or Firefox
> Reporter: Immo Benjes
> Assignee: Matej Novotny
> Labels: osx
> Fix For: 5.0.0.Alpha3
>
>
> In OS-X scrolling can be done by using two fingers on the touchpad. However this does not work for horizontal scrolling on the rich:extendedDataTable.
> You can scroll vertically but not horizontally.
> The horizontal scrolling with two fingers only works when the mouse is over the actual scrollbar!
> I had a look at the actual html code and it looks like the header, table content and scroller are generated as independent tables. The div that contains the table content (class rf-edt-cnt) has overflow:hidden; set. If you change that to overflow: auto you get the two finger scrolling over the content of the table, however the header and original scrollbar isn't scrolling. Would it be possible to hide the original scroller and synchronize the header (and footer?) when scrolling the content?
> In OS-X you have the option to only show the scrollbar when you scroll. This is quite nice as it gives you a bit more space. However in this case you cannot scroll with the extendedDataTable at all! The scrollbar of the extendedDataTable is hidden in this case and the height/width of the div containing the scrollbar is 0, so you can't navigate over it to enable the scrolling. That basically gives you no way of scrolling!
> See https://community.jboss.org/thread/231502
--
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-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13266:
-------------------------------
Fix Version/s: 4.3.5
> mediaOutput not working anymore on Glassfish3 and EAP6.1
> --------------------------------------------------------
>
> Key: RF-13266
> URL: https://issues.jboss.org/browse/RF-13266
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45
> Reporter: Fab Mars
> Assignee: Matej Novotny
> Labels: glassfish_v3, mediaOutput
> Fix For: 4.3.5
>
>
> This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3.
> I have 2 mediaOutput in my code, none works.
> The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression
> The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B
> I'm preparing a reproducer on github and will share the url in the next comment.
--
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-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13266:
-------------------------------
Labels: glassfish_v3 mediaOutput regression (was: glassfish_v3 mediaOutput)
> mediaOutput not working anymore on Glassfish3 and EAP6.1
> --------------------------------------------------------
>
> Key: RF-13266
> URL: https://issues.jboss.org/browse/RF-13266
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45
> Reporter: Fab Mars
> Assignee: Matej Novotny
> Labels: glassfish_v3, mediaOutput, regression
> Fix For: 4.3.5
>
>
> This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3.
> I have 2 mediaOutput in my code, none works.
> The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression
> The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B
> I'm preparing a reproducer on github and will share the url in the next comment.
--
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-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13266:
-------------------------------
Labels: regression (was: glassfish_v3 mediaOutput regression)
> mediaOutput not working anymore on Glassfish3 and EAP6.1
> --------------------------------------------------------
>
> Key: RF-13266
> URL: https://issues.jboss.org/browse/RF-13266
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.4
> Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45
> Reporter: Fab Mars
> Assignee: Matej Novotny
> Labels: regression
> Fix For: 4.3.5
>
>
> This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3.
> I have 2 mediaOutput in my code, none works.
> The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression
> The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B
> I'm preparing a reproducer on github and will share the url in the next comment.
--
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-13266) mediaOutput not working anymore on Glassfish3 and EAP6.1
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13266?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13266:
-------------------------------
Component/s: component-output
> mediaOutput not working anymore on Glassfish3 and EAP6.1
> --------------------------------------------------------
>
> Key: RF-13266
> URL: https://issues.jboss.org/browse/RF-13266
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.4
> Environment: Glassfish 3.1.2.2 patched with Weld 1.1.14 (the problem appears also on earlier Weld builds) and JSF 2.1.26 and JDK 1.7.0_45
> Reporter: Fab Mars
> Assignee: Matej Novotny
> Labels: regression
> Fix For: 4.3.5
>
>
> This is a followup to https://issues.jboss.org/browse/RF-13098 focusing on Glassfish3.
> I have 2 mediaOutput in my code, none works.
> The first one passes a Long as the value to the createContent method and the expected output is a PDF. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.util.el.ForwardingMethodExpression
> The second one passes an array of 3 bytes (a color code) and the expected result is an image. I get
> SEVERE: Input error for deserialize data java.io.InvalidClassException: Unauthorized deserialization attempt; [B
> I'm preparing a reproducer on github and will share the url in the next comment.
--
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-12593) RenderKitUtils.toScriptArgs() returns empty string when no not-null parameter provided
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12593?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12593:
-------------------------------
Comment: was deleted
(was: wefw)
> RenderKitUtils.toScriptArgs() returns empty string when no not-null parameter provided
> --------------------------------------------------------------------------------------
>
> Key: RF-12593
> URL: https://issues.jboss.org/browse/RF-12593
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.3.0.M2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Priority: Minor
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> The {{toScriptArgs(Object object)}} should always return JavaScript object:
> {code:javascript}
> { ... }
> {code}
> In case null object or no not-null parameter provided, empty object should be returned:
> {code:javascript}
> {}
> {code}
> Currently, it returns empty string {{""}} which is not handy if we expect JavaScript object as a return value.
--
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