[JBoss JIRA] (RF-13582) Revert the core package re-factoring
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13582:
----------------------------------
[~michpetrov] or [~bleathem] could you check my last comment?
> Revert the core package re-factoring
> ------------------------------------
>
> Key: RF-13582
> URL: https://issues.jboss.org/browse/RF-13582
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Brian Leathem
> Assignee: Michal Petrov
> Labels: needs-qe
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to):
> * .servlet (PushServlet, ResourceServlet)
> * .push.cdi (@PUsh)
> * .push. (TopicContext)
> * FileUploadException
> A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (RF-13582) Revert the core package re-factoring
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek edited comment on RF-13582 at 6/19/14 6:48 AM:
-----------------------------------------------------------
I have created a branch in qa repo for this. [This commit|https://github.com/richfaces/richfaces-qa/commit/5eab3f39145cf1bd6...] adds the RF 4.5 jars to Metamer and make it compilable, could you, please, check if I didn't something wrong? As you can see in the commit, there are just changes in rich components (not in core components).
I've also run all tests for a4j components from this branch ([verified with this job|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-x.y-me...], ignore the status JS API tests (different call of JS API function in RF 4.3 and 4.5 {{RichFaces.$}} X {{RichFaces.component}})) + manually verified {{queue}} and {{attachedQueue}} components (there are no WebDriver tests for them). From these results I can confirm that all a4j components works correctly in 4.3 Metamer with 4.5 components.
was (Author: jstefek):
I have created a branch in qa repo for this. [This commit|https://github.com/richfaces/richfaces-qa/commit/5eab3f39145cf1bd6...] adds the RF 4.5 jars to Metamer and make it compilable, could you, please, check if I didn't something wrong? As you can see in the commit, there are just changes in rich components.
I've also run all tests for a4j components from this branch ([verified with this job|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-x.y-me...], ignore the status JS API tests (different call of JS API function in RF 4.3 and 4.5 {{RichFaces.$}} X {{RichFaces.component}})) + manually verified {{queue}} and {{attachedQueue}} components (there are no WebDriver tests for them). From these results I can confirm that all a4j components works correctly.
> Revert the core package re-factoring
> ------------------------------------
>
> Key: RF-13582
> URL: https://issues.jboss.org/browse/RF-13582
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Brian Leathem
> Assignee: Michal Petrov
> Labels: needs-qe
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 3 hours
> Remaining Estimate: 3 hours
>
> To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to):
> * .servlet (PushServlet, ResourceServlet)
> * .push.cdi (@PUsh)
> * .push. (TopicContext)
> * FileUploadException
> A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek updated RF-13640:
-----------------------------
Labels: needs-backport regression (was: needs-backport needs-qe regression)
> Autocomplete with custom layout: cant select item by mouse
> ----------------------------------------------------------
>
> Key: RF-13640
> URL: https://issues.jboss.org/browse/RF-13640
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.6, 4.5.0.Alpha3
> Environment: Firefox 29.0.1
> Chrome 35.0.1916.114
> Reporter: liumin hu
> Assignee: Brian Leathem
> Labels: needs-backport, regression
> Fix For: 4.3.8, 4.5.0.Alpha3
>
>
> When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected.
> This bug was not observable before 4.3.6.Final.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek edited comment on RF-13640 at 6/19/14 6:32 AM:
-----------------------------------------------------------
Verified
* on EAP 6.3.ER7
* in Showcase: manually verified all autocomplete, select, inplaceSelect, orderingList and pickList samples on FF 30, Chrome 35, Safari 5.1.7, IE 10, IE 11
* in Metamer: ran all tests in FF for autocomplete, select, inplaceSelect, orderingList and pickList
[~bleathem], the issue is resolved in RF 4.5, I can also confirm that the issue RF-13531 remains resolved, you can continue with porting this fix to RF 4.3.
was (Author: jstefek):
Verified
* on EAP 6.3.ER7
* in Showcase: manually verified all autocomplete, select, inplaceSelect, orderingList and pickList samples on FF 30, Chrome 36, Safari 5.1.7, IE 10, IE 11
* in Metamer: ran all tests in FF for autocomplete, select, inplaceSelect, orderingList and pickList
[~bleathem], the issue is resolved in RF 4.5, I can also confirm that the issue RF-13531 remains resolved, you can continue with porting this fix to RF 4.3.
> Autocomplete with custom layout: cant select item by mouse
> ----------------------------------------------------------
>
> Key: RF-13640
> URL: https://issues.jboss.org/browse/RF-13640
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.6, 4.5.0.Alpha3
> Environment: Firefox 29.0.1
> Chrome 35.0.1916.114
> Reporter: liumin hu
> Assignee: Brian Leathem
> Labels: needs-backport, needs-qe, regression
> Fix For: 4.3.8, 4.5.0.Alpha3
>
>
> When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected.
> This bug was not observable before 4.3.6.Final.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (RF-13640) Autocomplete with custom layout: cant select item by mouse
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13640?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-13640:
----------------------------------
Verified
* on EAP 6.3.ER7
* in Showcase: manually verified all autocomplete, select, inplaceSelect, orderingList and pickList samples on FF 30, Chrome 36, Safari 5.1.7, IE 10, IE 11
* in Metamer: ran all tests in FF for autocomplete, select, inplaceSelect, orderingList and pickList
[~bleathem], the issue is resolved in RF 4.5, I can also confirm that the issue RF-13531 remains resolved, you can continue with porting this fix to RF 4.3.
> Autocomplete with custom layout: cant select item by mouse
> ----------------------------------------------------------
>
> Key: RF-13640
> URL: https://issues.jboss.org/browse/RF-13640
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-input
> Affects Versions: 4.3.6, 4.5.0.Alpha3
> Environment: Firefox 29.0.1
> Chrome 35.0.1916.114
> Reporter: liumin hu
> Assignee: Brian Leathem
> Labels: needs-backport, needs-qe, regression
> Fix For: 4.3.8, 4.5.0.Alpha3
>
>
> When the autocomplete component is used with a custom layout, n item in the suggestion list can not be selected by mouse, always the first one selected.
> This bug was not observable before 4.3.6.Final.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months