[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13629 at 5/22/14 4:56 AM:
-----------------------------------------------------------
The performance issue no more occur which is great, but unfortunately there are other issues introduced with this patch, reproducible on all browsers:
# _After resize, {{popupPanel}} visual state is broken. Its bottom border does not exist, rendered shadow is too big_
## please see the attachments: !popupPanelResizedAndBroken_2.png|thumbnail! and !popupResizedAndBroken_1.png|thumbnail!
## Steps to reproduce:
### Build and deploy project from https://github.com/jhuska/richfaces-sanbox/tree/RF-13629
### Load: http://localhost:8080/richfaces-sanbox/simpleResizablePopup.jsf
### Try to resize the {{popupPanel}}, either make it bigger or smaller and see that it is broken
# _PopupPanel can not be resized by its top border, because when D&Dropping its top border it is moved instead_
## Steps to reproduce:
### Build and deploy project from https://github.com/jhuska/richfaces-sanbox/tree/RF-13629
### Load: http://localhost:8080/richfaces-sanbox/simpleResizablePopup.jsf
### Try to resize the {{popupPanel}} by its top border, and see that it is not enlarged, but moved.
was (Author: jhuska):
The performance issue no more occur which is great, but unfortunately there are other issues introduced with this patch, reproducible on all browsers:
# _After resize, {{popupPanel}} visual state is broken. Its bottom border does not exist, rendered shadow is too big_
## please see the attachments: popupPanelResizedAndBroken_2 and popupResizedAndBroken_1
## Steps to reproduce:
### Build and deploy project from https://github.com/jhuska/richfaces-sanbox/tree/RF-13629
### Load: http://localhost:8080/richfaces-sanbox/simpleResizablePopup.jsf
### Try to resize the {{popupPanel}}, either make it bigger or smaller and see that it is broken
# _PopupPanel can not be resized by its top border, because when D&Dropping its top border it is moved instead_
## Steps to reproduce:
### Build and deploy project from https://github.com/jhuska/richfaces-sanbox/tree/RF-13629
### Load: http://localhost:8080/richfaces-sanbox/simpleResizablePopup.jsf
### Try to resize the {{popupPanel}} by its top border, and see that it is not enlarged, but moved.
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: needs-qe, regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
> When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska commented on RF-13629:
----------------------------------
The performance issue no more occur which is great, but unfortunately there are other issues introduced with this patch, reproducible on all browsers:
# _After resize, {{popupPanel}} visual state is broken. Its bottom border does not exist, rendered shadow is too big_
## please see the attachments: popupPanelResizedAndBroken_2 and popupResizedAndBroken_1
## Steps to reproduce:
### Build and deploy project from https://github.com/jhuska/richfaces-sanbox/tree/RF-13629
### Load: http://localhost:8080/richfaces-sanbox/simpleResizablePopup.jsf
### Try to resize the {{popupPanel}}, either make it bigger or smaller and see that it is broken
# _PopupPanel can not be resized by its top border, because when D&Dropping its top border it is moved instead_
## Steps to reproduce:
### Build and deploy project from https://github.com/jhuska/richfaces-sanbox/tree/RF-13629
### Load: http://localhost:8080/richfaces-sanbox/simpleResizablePopup.jsf
### Try to resize the {{popupPanel}} by its top border, and see that it is not enlarged, but moved.
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: needs-qe, regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
> When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13629:
-----------------------------
Attachment: popupPanelResizedAndBroken_2.png
popupResizedAndBroken_1.png
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: needs-qe, regression
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelResizedAndBroken_2.png, popupPanelWrong.png, popupResizedAndBroken_1.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
> When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13604) rich:editor is flickering on mouse hover
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/RF-13604?page=com.atlassian.jira.plugin.s... ]
Matej Novotny commented on RF-13604:
------------------------------------
I was tempering with this a little in order to find out where it can be reproduced. In the end I found it is generally observable.
Using the attached ZIP project...
You can use whichever browser you like (chrome, ff ie,..), and as for AS you can surely use Wildfly, JBoss AS 7.1, Glassfish (those I tested).
I tried recreating the project with JSF 2.1 instead of 2.2 as I was suspicious that could cause the problem. But with no luck - editor was still flickering.
However I was unable to reproduce this with Metamer which is Maven project compared to this, but otherwise using same libs (and similar versions). Not sure how, but could that make a difference?
> rich:editor is flickering on mouse hover
> ----------------------------------------
>
> Key: RF-13604
> URL: https://issues.jboss.org/browse/RF-13604
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.5
> Environment: Windows 7, Glassfish 4, Java 1.7, JSF2.2, Chrome (version 34.0.1847.116 m) or Internet Explorer (version 11.0.9600.16659)
> Reporter: Serge Rogatch
> Assignee: Matej Novotny
> Labels: editor, glassfish, jsf22
> Attachments: TutRichf1.zip
>
>
> Initially the rich:editor component didn't render, throwing some errors in JavaScript ( https://community.jboss.org/message/867978 ), however afterwards I was not able to reproduce that in a newly created project.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13637) Refresh the dist zip for RF 4.5
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13637?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13637:
------------------------------------
I propose the generated documentation be generated for each of the 3 richfaces maven jars (rich, a4j, and core). These generated docs will be stored as jars in the maven repo with the classifiers: source, javadoc, vdldoc, and jsdoc. These classifier jar will be generated when the component and core module are built with the {{release}} profile.
However three separate jars is not useful to be provided in the distribution zip. I propose a maven step to unpack the source jars of the 3 richfaces jars and regenerate the javadoc, vdldoc, and jsdoc documentation. These merged generated docs should not be stored in the maven repo directly, but rather as part of the richfaces-dist zip that will be in the maven repo.
> Refresh the dist zip for RF 4.5
> -------------------------------
>
> Key: RF-13637
> URL: https://issues.jboss.org/browse/RF-13637
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The distribution zip for RichFaces 4.5 needs to be refreshed to account for the module and repository changes.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13637) Refresh the dist zip for RF 4.5
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13637?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13637:
------------------------------------
The maven artifacts consist of:
* richfaces.jar (rich components)
* richafces-a4j.jar (a4j components)
* richfaces-core.jar (framework classes)
In the distributions zip I propose renaming these to:
* richfaces-components-rich.jar
* richfaces-components-core.jar
* richfaces-core.jar
I have implemented this using a {{dependencySet}} in the maven-assembly-plugin.
> Refresh the dist zip for RF 4.5
> -------------------------------
>
> Key: RF-13637
> URL: https://issues.jboss.org/browse/RF-13637
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: build/distribution
> Reporter: Brian Leathem
> Assignee: Brian Leathem
> Fix For: 4.5.0.Alpha3
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> The distribution zip for RichFaces 4.5 needs to be refreshed to account for the module and repository changes.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13637) Refresh the dist zip for RF 4.5
by Brian Leathem (JIRA)
Brian Leathem created RF-13637:
----------------------------------
Summary: Refresh the dist zip for RF 4.5
Key: RF-13637
URL: https://issues.jboss.org/browse/RF-13637
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build/distribution
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 4.5.0.Alpha3
The distribution zip for RichFaces 4.5 needs to be refreshed to account for the module and repository changes.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (RF-13629) popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13629?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13629.
--------------------------------
Labels: needs-qe regression (was: regression)
Resolution: Done
QE: please test the height/width settings of the popupPanel, and also test that RF-13616 remains fixed with this patch.
> popupPanel - minWidth, minHeight, maxWidth, maxHeight are not ignored when autosize == true
> -------------------------------------------------------------------------------------------
>
> Key: RF-13629
> URL: https://issues.jboss.org/browse/RF-13629
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.7
> Environment: Firefox
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Priority: Critical
> Labels: regression, needs-qe
> Fix For: 4.3.7
>
> Attachments: popupPanelGood.png, popupPanelWrong.png, sample.zip
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> In previous releases when attribute {{autosize == true}} attributes from $SUBJECT were ignored. In {{4.3.7.}}, they are not.
> When used together (does not really make sense IMHO, but maybe I am neglecting some use case), the popup width is not adjusted automatically.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months