[JBoss JIRA] (RF-13176) tree: JS error after selecting an item in tree
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13176?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13176:
----------------------------------
[~lfryc] yes, it works now, thanks.
> tree: JS error after selecting an item in tree
> ----------------------------------------------
>
> Key: RF-13176
> URL: https://issues.jboss.org/browse/RF-13176
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tree
> Environment: richfaces-5.0.0-SNAPSHOT
> FF 18
> Tomcat 7.0.32, JBoss AS 7.1
> Reporter: Jiří Štefek
> Assignee: Lukáš Fryč
> Priority: Critical
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> The selecting of items does not work properly.
> After selecting an item (toggling of nodes works fine) from tree a JavaScript error occurs:
> {code}
> TypeError: RichFaces.$ is not a function
>
> ...EventHandler=function(handlerCode){if(handlerCode){return new Function("event",h...
> packed.js (line 178)
> {code}
> This also prevents any further manipulation with tree.
--
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-13180) Autocomplete: ajax doesn't work with change event
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13180?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13180:
------------------------------------
1. your test (link 1) isn't very useful because it doesn't simulate what a user does
2. autocomplete doesn't fire change event in Metamer even after blur is done, it *is a regression*
3. r.taglib.xml doesn't contain attribute onselect, however, there is onselectitem attribute, I *don't* agree with removing onchange attribute, there is a difference in behavior between onblur and onchange, see link 2
(link 1) https://github.com/richfaces/richfaces/blob/master/framework/src/test/int...
(link 2) http://docs.jboss.org/richfaces/latest_5_X/vdldoc/r/autocomplete.html
> 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: Pavol Pitonak
> 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, 7 months
[JBoss JIRA] (RF-13093) extendedDataTable column resizing and reordering not working on transient (stateless) views
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13093?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13093:
-------------------------------
Sprint: (was: 5.0.0.Alpha2 - Sprint 3)
> extendedDataTable column resizing and reordering not working on transient (stateless) views
> -------------------------------------------------------------------------------------------
>
> Key: RF-13093
> URL: https://issues.jboss.org/browse/RF-13093
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23
> Reporter: Salvo Isaja
> Labels: jsf22
> Fix For: 4.3.5, 5.0.0.Alpha3
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When turning on transient (stateless) views in recent Mojarra versions (as per JSF 2.2 specification, to my best understanding), using request scoped backing beans, javax.faces.ViewState becomes the constant "stateless". Column resizing and reordering in extendedDataTable causes an Ajax request to the server, but in this case an invalid response is sent, containing only:
> {code:xml}
> <?xml version='1.0' encoding='UTF-8'?>
> <partial-response></partial-response>
> {code}
> This causes an exception in {{jsf.js}} because the partial-response element has no children and no further JavaScript processing happens in the view until the page is reloaded. In the non-transient view case, I see a {{change}} element updating only the ViewState is returned, instead.
> Other features seem to work pretty well in stateless mode, by the way.
> Thanks
--
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-13168) 3rd party JSF component disappears on RichFaces ajax refresh
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13168?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13168:
-------------------------------
Sprint: (was: 5.0.0.Alpha2 - Sprint 3)
> 3rd party JSF component disappears on RichFaces ajax refresh
> ------------------------------------------------------------
>
> Key: RF-13168
> URL: https://issues.jboss.org/browse/RF-13168
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility, component-a4j-core
> Reporter: Frank Langelage
> Assignee: Brian Leathem
> Labels: interop, jsf22
> Fix For: 4.3.5, 5.0.0.Alpha3
>
> Attachments: install-mojarra-2.1.19.cli, Jira-WFLY-UT.tar, xaa, xab, xac
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> On some of my pages I'm using richfaces a4j:poll to refresh components regularly. The components refreshed is an openfaces datatable.
> This does not work with WildFly build from current sources.
> Same code works with JBoss AS 7.20. So problem is not related to richfaces or openfaces for me. Probably related to replacement of jboss-web with undertow.
> I'll attach a small project showing the problem.
> The mojarra datatable works fine, is refreshed every 10 seconds.
> The openfaces datatable below disappears on first refresh.
--
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-12214) Pack plain skin with UI components distribution (the resource plugin needs to be fixed)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12214?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12214:
-------------------------------
Sprint: 5.0.0.Alpha2 - Sprint 2, 5.0.0.Alpha2 - Sprint 3 (was: 5.0.0.Alpha2 - Sprint 2)
> Pack plain skin with UI components distribution (the resource plugin needs to be fixed)
> ---------------------------------------------------------------------------------------
>
> Key: RF-12214
> URL: https://issues.jboss.org/browse/RF-12214
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 4.2.1.Final
> Reporter: Nicolas Daniels
> Assignee: Lukáš Fryč
> Priority: Minor
> Labels: needs-qe
> Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> The plain skin is not packed/compresses as other styles, mainly because images generation is failing due to null property values.
> It could be good to have it as well. Beside it, probably that image generation with null value should be handled.
> Of course, any failed image generation should not be referenced in resulting css.
> (Fyi, currently, generating plain skin is working despite the warnings but missing images are still referenced in resulting css. This is not really good for resources optimization ;-))
--
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-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 updated RF-13180:
-------------------------------
Sprint: 5.0.0.Alpha2 - Sprint 2, 5.0.0.Alpha2 - Sprint 3 (was: 5.0.0.Alpha2 - Sprint 2)
> 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: Pavol Pitonak
> 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, 7 months
[JBoss JIRA] (RF-13164) Skinning of standard inputs not consistent
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13164?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13164:
-------------------------------
Sprint: 5.0.0.Alpha2 - Sprint 2, 5.0.0.Alpha2 - Sprint 3 (was: 5.0.0.Alpha2 - Sprint 2)
> Skinning of standard inputs not consistent
> ------------------------------------------
>
> Key: RF-13164
> URL: https://issues.jboss.org/browse/RF-13164
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: skinning
> Affects Versions: 5.0.0.Alpha2
> Reporter: Pavol Pitonak
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In 5.0.0-SNAPSHOT standard JSF inputs (such as h:inputText) are skinned by RichFaces or by Bootstrap depending on which components are used on page.
> When a new component (e.g. autocomplete) is used, it includes Bootstrap CSS file which overrides RichFaces skinning.
> Bootstrap CSS file should be probably included for each component.
--
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-13193) Rename the resource library to account for RF 4/5 resource overlap
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13193?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13193:
-------------------------------
Sprint: 5.0.0.Alpha2 - Sprint 2, 5.0.0.Alpha2 - Sprint 3 (was: 5.0.0.Alpha2 - Sprint 2)
> Rename the resource library to account for RF 4/5 resource overlap
> ------------------------------------------------------------------
>
> Key: RF-13193
> URL: https://issues.jboss.org/browse/RF-13193
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: resource handling
> Reporter: Brian Leathem
> Assignee: Michal Petrov
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Rename the RichFaces resource library name to something like: _org.richfaces.ui_, or _org.richfaces.widgets_. This will allow RF 4 and RF 5 components to co-exist when resource names overlap.
--
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