[JBoss JIRA] (RF-13157) rich:dropDownMenu under rich:accordion cannot work
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13157?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13157 at 9/26/13 11:43 AM:
--------------------------------------------------------------
Sorry for reply late --
Been working on other project.
After I tried to modfiy the z-index still not working...
Seems because the css class:
{code}
.rf-ac-itm-cnt {
border-color: #BED6F8;
border-style: solid;
border-width: 1px;
color: #000000;
font-family: Arial,Verdana,sans-serif;
font-size: 11px;
overflow-x: hidden;
overflow-y: auto;
padding: 10px;
position: relative;
}
{code}
If I take off:
{code}
{
overflow-x: hidden;
overflow-y: auto;
}
{code}
Then it can works fine.
was (Author: dlee606):
Sorry for reply late --
Been working on other project.
After I tried to modfiy the z-index still not working...
Seems because the css class:
.rf-ac-itm-cnt {
border-color: #BED6F8;
border-style: solid;
border-width: 1px;
color: #000000;
font-family: Arial,Verdana,sans-serif;
font-size: 11px;
overflow-x: hidden;
overflow-y: auto;
padding: 10px;
position: relative;
}
If I take off {
overflow-x: hidden;
overflow-y: auto;
}
Then it can works fine.
> rich:dropDownMenu under rich:accordion cannot work
> --------------------------------------------------
>
> Key: RF-13157
> URL: https://issues.jboss.org/browse/RF-13157
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-menu
> Affects Versions: 4.3.3
> Environment: Richfaces4.3.3 / CentOS6 / FireFox
> Reporter: David Lee
> Assignee: Pavol Pitonak
> Labels: waiting_on_user
>
> When I tried to put rich:dropDownMenu under rich:accordion,
> the side menu item cannot display on the right hand side.
> Please see the image of trouble screen.
--
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
10 years, 7 months
[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-13216:
----------------------------------
Assignee: Pavol Pitonak
QA please reproduce this issue (metamer should be fine).
cc: [~jhuska]
> PoupPanel doesn't disappear when rendered="false" and rerender it.
> ------------------------------------------------------------------
>
> Key: RF-13216
> URL: https://issues.jboss.org/browse/RF-13216
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.3
> Reporter: Takayuki Konishi
> Assignee: Pavol Pitonak
> Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip
>
>
> If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions.
> {code:xml}
> <h:body title="page 1">
> <a4j:outputPanel id="myPanel">
> <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}">
> <h:form>
> <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/>
> </h:form>
> </rich:popupPanel>
> <h:form>
> <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/>
> </h:form>
> </a4j:outputPanel>
> </h:body>
> {code}
> In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view.
> Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final.
> Note:
> In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function.
--
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
10 years, 7 months
[JBoss JIRA] (RF-13216) PoupPanel doesn't disappear when rendered="false" and rerender it.
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13216?page=com.atlassian.jira.plugin.s... ]
Brian Leathem edited comment on RF-13216 at 9/26/13 11:40 AM:
--------------------------------------------------------------
additional problem:
domElementAttachment="body" will break the ajax actions of the "outer" form.
consider the following example:
{code}
<h:form>
...
<rich:popupPanel>
<h:form>
<!-- local form needed for actions if we use default behaviour and move the panel in DOM -->
...
</h:form>
</rich:popupPanel
...
<a4j:commandbutton action="test.action()"/>
</h:form>
{code}
submit the commandButton will not work, because the DOM of the outer form now contains two hidden fields of "javax.faces.encodedURL" and the javascript code to fetch the submit-url (jsf.js) will fail in this scenario.
was (Author: nias):
additional problem:
domElementAttachment="body" will break the ajax actions of the "outer" form.
consider the following example:
<h:form>
...
<rich:popupPanel>
<h:form>
<!-- local form needed for actions if we use default behaviour and move the panel in DOM -->
...
</h:form>
</rich:popupPanel
...
<a4j:commandbutton action="test.action()"/>
</h:form>
submit the commandButton will not work, because the DOM of the outer form now contains two hidden fields of "javax.faces.encodedURL" and the javascript code to fetch the submit-url (jsf.js) will fail in this scenario.
> PoupPanel doesn't disappear when rendered="false" and rerender it.
> ------------------------------------------------------------------
>
> Key: RF-13216
> URL: https://issues.jboss.org/browse/RF-13216
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.3
> Reporter: Takayuki Konishi
> Attachments: rf3_3_4-modalpanel.zip, rf4_3_3-popuppanel.zip
>
>
> If you use the richfaces popupPanel in the default domElementAttachment="body" mode it will not disappear under specific conditions.
> {code:xml}
> <h:body title="page 1">
> <a4j:outputPanel id="myPanel">
> <rich:popupPanel domElementAttachment="body" show="true" rendered="#{test.showPopup}">
> <h:form>
> <a4j:commandButton action="#{test.switchPopup()}" value="switch off" render="myPanel"/>
> </h:form>
> </rich:popupPanel>
> <h:form>
> <a4j:commandButton action="#{test.switchPopup()}" value="switch on" render="myPanel"/>
> </h:form>
> </a4j:outputPanel>
> </h:body>
> {code}
> In Richfaces 3.3.x, on the other hand, there was a component cleanup system ({{memory.js _cleanComponentNodes}}) which was responsible to remove components after ajax calls if the component was removed from the current view.
> Therefore the above example (revert {{popupPanel}} to {{modalPanel}}) works in RF3.3.4.Final.
> Note:
> In case {{domElementAttachment="parent"}}, it will show [the other JSF2 bug|https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-790] where the view state was lost, therefore you must click the action button twice to really call the function.
--
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
10 years, 7 months
[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13225:
------------------------------------
The image mapping would need to be renamed. {{org.richfaces.images.ui}}?
As far as the CSS is concerned, debugging shows the resource path is obtained from [DynamicResourceWrapper|https://github.com/richfaces/richfaces/blob/master...], which will always return a path beginning with {{%skin%}} needed for the mapping files. I'm assuming those files are then supposed to be scanned and the path resolved from them (via a different handler) but that doesn't seem to be happening.
> RF5 build fails to render optimized resources
> ---------------------------------------------
>
> Key: RF-13225
> URL: https://issues.jboss.org/browse/RF-13225
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
>
> The improvements for 4.5.x along with resource handling improvements introduced several issues:
> * framework/pom.xml resource optimization
> {code}
> <execution>
> <id>static-resources</id>
> <phase>process-classes</phase>
> <goals>
> <goal>java</goal>
> </goals>
> <configuration>
> <arguments>
> <argument>--classpathDir</argument>
> <argument>${project.build.outputDirectory}</argument>
> <argument>--output</argument>
> <argument>${optimized.resources.directory}/Static/</argument>
> <argument>--prefix</argument>
> <argument>${optimized.resources.prefix}/Static/</argument>
> <argument>--mapping</argument
> <argument>${optimized.resources.mapping}/Static.properties</argument>
> <argument>--skins</argument>
> <argument>${optimized.resources.skins}</argument>
> <argument>--excludeFile</argument>
> <argument>^javax.faces</argument>
> <argument>excludeFile</argument>
> <argument>^org.richfaces.ui.images.*</argument>
> {code}
> {panel}
> the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail
> {panel}
> * CSS rendering from *.ecss
> {code}
> #{richSkin.imageUrl('inputBackgroundImage.png')}
> {code}
> {panel}
> the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{../org.richfaces.ui.images/gradientA.png}} (current)
> {panel}
--
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
10 years, 7 months
[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ]
Michal Petrov updated RF-13225:
-------------------------------
Description:
The improvements for 4.5.x along with resource handling improvements introduced several issues:
* framework/pom.xml resource optimization
{code}
<execution>
<id>static-resources</id>
<phase>process-classes</phase>
<goals>
<goal>java</goal>
</goals>
<configuration>
<arguments>
<argument>--classpathDir</argument>
<argument>${project.build.outputDirectory}</argument>
<argument>--output</argument>
<argument>${optimized.resources.directory}/Static/</argument>
<argument>--prefix</argument>
<argument>${optimized.resources.prefix}/Static/</argument>
<argument>--mapping</argument
<argument>${optimized.resources.mapping}/Static.properties</argument>
<argument>--skins</argument>
<argument>${optimized.resources.skins}</argument>
<argument>--excludeFile</argument>
<argument>^javax.faces</argument>
<argument>excludeFile</argument>
<argument>^org.richfaces.ui.images.*</argument>
{code}
{panel}
the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail
{panel}
* CSS rendering from *.ecss
{code}
#{richSkin.imageUrl('inputBackgroundImage.png')}
{code}
{panel}
the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{../org.richfaces.ui.images/gradientA.png}} (current)
{panel}
was:
The improvements for 4.5.x along with resource handling improvements introduced several issues:
* framework/pom.xml
{code}
<execution>
<id>static-resources</id>
<phase>process-classes</phase>
<goals>
<goal>java</goal>
</goals>
<configuration>
<arguments>
<argument>--classpathDir</argument>
<argument>${project.build.outputDirectory}</argument>
<argument>--output</argument>
<argument>${optimized.resources.directory}/Static/</argument>
<argument>--prefix</argument>
<argument>${optimized.resources.prefix}/Static/</argument>
<argument>--mapping</argument
<argument>${optimized.resources.mapping}/Static.properties</argument>
<argument>--skins</argument>
<argument>${optimized.resources.skins}</argument>
<argument>--excludeFile</argument>
<argument>^javax.faces</argument>
<argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument>
{code}
> RF5 build fails to render optimized resources
> ---------------------------------------------
>
> Key: RF-13225
> URL: https://issues.jboss.org/browse/RF-13225
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
>
> The improvements for 4.5.x along with resource handling improvements introduced several issues:
> * framework/pom.xml resource optimization
> {code}
> <execution>
> <id>static-resources</id>
> <phase>process-classes</phase>
> <goals>
> <goal>java</goal>
> </goals>
> <configuration>
> <arguments>
> <argument>--classpathDir</argument>
> <argument>${project.build.outputDirectory}</argument>
> <argument>--output</argument>
> <argument>${optimized.resources.directory}/Static/</argument>
> <argument>--prefix</argument>
> <argument>${optimized.resources.prefix}/Static/</argument>
> <argument>--mapping</argument
> <argument>${optimized.resources.mapping}/Static.properties</argument>
> <argument>--skins</argument>
> <argument>${optimized.resources.skins}</argument>
> <argument>--excludeFile</argument>
> <argument>^javax.faces</argument>
> <argument>excludeFile</argument>
> <argument>^org.richfaces.ui.images.*</argument>
> {code}
> {panel}
> the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail
> {panel}
> * CSS rendering from *.ecss
> {code}
> #{richSkin.imageUrl('inputBackgroundImage.png')}
> {code}
> {panel}
> the imageUrl method doesn't return the proper path, e.g. {{../org.richfaces.ui.images/gradientA.png}} (proper) instead of {{../org.richfaces.ui.images/gradientA.png}} (current)
> {panel}
--
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
10 years, 7 months
[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ]
Michal Petrov updated RF-13225:
-------------------------------
Fix Version/s: 5.0.0.Alpha2
> RF5 build fails to render optimized resources
> ---------------------------------------------
>
> Key: RF-13225
> URL: https://issues.jboss.org/browse/RF-13225
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
>
> The improvements for 4.5.x along with resource handling improvements introduced several issues:
> * framework/pom.xml
> {code}
> <execution>
> <id>static-resources</id>
> <phase>process-classes</phase>
> <goals>
> <goal>java</goal>
> </goals>
> <configuration>
> <arguments>
> <argument>--classpathDir</argument>
> <argument>${project.build.outputDirectory}</argument>
> <argument>--output</argument>
> <argument>${optimized.resources.directory}/Static/</argument>
> <argument>--prefix</argument>
> <argument>${optimized.resources.prefix}/Static/</argument>
> <argument>--mapping</argument
> <argument>${optimized.resources.mapping}/Static.properties</argument>
> <argument>--skins</argument>
> <argument>${optimized.resources.skins}</argument>
> <argument>--excludeFile</argument>
> <argument>^javax.faces</argument>
> <argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument>
> {code}
--
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
10 years, 7 months
[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources
by Michal Petrov (JIRA)
Michal Petrov created RF-13225:
----------------------------------
Summary: RF5 build fails to render optimized resources
Key: RF-13225
URL: https://issues.jboss.org/browse/RF-13225
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: resource handling
Affects Versions: 5.0.0.Alpha2
Reporter: Michal Petrov
The improvements for 4.5.x along with resource handling improvements introduced several issues:
* framework/pom.xml
{code}
<execution>
<id>static-resources</id>
<phase>process-classes</phase>
<goals>
<goal>java</goal>
</goals>
<configuration>
<arguments>
<argument>--classpathDir</argument>
<argument>${project.build.outputDirectory}</argument>
<argument>--output</argument>
<argument>${optimized.resources.directory}/Static/</argument>
<argument>--prefix</argument>
<argument>${optimized.resources.prefix}/Static/</argument>
<argument>--mapping</argument
<argument>${optimized.resources.mapping}/Static.properties</argument>
<argument>--skins</argument>
<argument>${optimized.resources.skins}</argument>
<argument>--excludeFile</argument>
<argument>^javax.faces</argument>
<argument>excludeFile</argument> <argument>^org.richfaces.ui.images.*</argument>
{code}
--
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
10 years, 7 months