[JBoss JIRA] (RF-13382) rich:select realign options list on window resize
by Gabriele Gervasi (JIRA)
[ https://issues.jboss.org/browse/RF-13382?page=com.atlassian.jira.plugin.s... ]
Gabriele Gervasi updated RF-13382:
----------------------------------
Attachment: Schermata 2013-11-25 alle 18.51.03.png
Schermata 2013-11-25 alle 18.51.30.png
> rich:select realign options list on window resize
> -------------------------------------------------
>
> Key: RF-13382
> URL: https://issues.jboss.org/browse/RF-13382
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.4
> Reporter: Gabriele Gervasi
> Priority: Optional
> Attachments: Schermata 2013-11-25 alle 18.51.03.png, Schermata 2013-11-25 alle 18.51.30.png
>
>
> I'm currently developing a web application and i notice that rich:select options doesn't follow rich:select input on window resize. If it's possible to change this behaviour it will be really apprentice. I temporarily simply solved hiding on window resize.
> <script>
> window.onresize = function(event) {
> document.activeElement.blur();
> }
> </script>
--
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-13382) rich:select realign options list on window resize
by Gabriele Gervasi (JIRA)
Gabriele Gervasi created RF-13382:
-------------------------------------
Summary: rich:select realign options list on window resize
Key: RF-13382
URL: https://issues.jboss.org/browse/RF-13382
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-selects
Affects Versions: 4.3.4
Reporter: Gabriele Gervasi
Priority: Optional
I'm currently developing a web application and i notice that rich:select options doesn't follow rich:select input on window resize. If it's possible to change this behaviour it will be really apprentice. I temporarily simply solved hiding on window resize.
<script>
window.onresize = function(event) {
document.activeElement.blur();
}
</script>
--
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-13348) pickList - columnClass attribute behaves differently than in RF4
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Juraj Húska closed RF-13348.
----------------------------
Thank you for explaining. It was rather my misunderstanding, docs seems to be clear now.
Verified. Closing.
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
> Key: RF-13348
> URL: https://issues.jboss.org/browse/RF-13348
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?
--
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-13379) Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization)
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13379?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13379:
-------------------------------
Fix Version/s: 5.0.0.Alpha3
> Build on Travis fails due to NoClassDefFoundEx.: javax/servlet/Servlet (during framework resource optimization)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: RF-13379
> URL: https://issues.jboss.org/browse/RF-13379
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: resource handling
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha3
>
>
> https://travis-ci.org/richfaces/richfaces/builds/14381706
> {code}
> [INFO] <<< exec-maven-plugin:1.2.1:java (static-resources) @ richfaces <<<
> [INFO]
> [INFO] --- exec-maven-plugin:1.2.1:java (static-resources) @ richfaces ---
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Nov 24, 2013 8:04:06 AM org.richfaces.resource.optimizer.ResourceGenerator execute
> SEVERE: null
> java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at org.richfaces.resource.optimizer.ResourceGenerator.execute(ResourceGenerator.java:437)
> at org.richfaces.resource.optimizer.GenerateResourcesMain.main(GenerateResourcesMain.java:39)
> at sun.reflect.NativethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativethodAccessorImpl.invoke(NativethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.NoClassDefFoundError: javax/servlet/Servlet
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at org.richfaces.resource.ResourceFactoryImpl.creatappedResource(ResourceFactoryImpl.java:356)
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:343)
> {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-13348) pickList - columnClass attribute behaves differently than in RF4
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13348:
------------------------------------
[~jhuska] I think you are not interpreting the docs as intended:
{quote}
When table layout is used, _columnClasses_ specifies a comma-delimited list of CSS style classes to apply to each column. A space separated list of classes may be specified for an individual column.
{quote}
What is meant by this is that the comma character is the column delimeter, and the space character spearates multiple classes to be applied to a single column in the iteration over the columns.
Let me demonstrate with an example:
{code}
columnClasses = class1, class2a class2b, class3, *
{code}
Then I expect a table with 5 columns to have the following classes:
|| column || CSS class ||
| column 1 | class1 |
| column 2 | class2a class2b |
| column 3 | class3 |
| column 4 | class1 |
| column 5 | class2a class2b |
This behavior is confirmed with the richwidget tests:
https://github.com/richwidgets/richwidgets/blob/master/test/widgets/selec...
https://github.com/richwidgets/richwidgets/blob/master/test/widgets/selec...
If you feel the docs are still unclear, please open a new issue addressing the documentation of the _columnClasses_ attribute.
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
> Key: RF-13348
> URL: https://issues.jboss.org/browse/RF-13348
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?
--
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-13348) pickList - columnClass attribute behaves differently than in RF4
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13348.
--------------------------------
Resolution: Done
> pickList - columnClass attribute behaves differently than in RF4
> ----------------------------------------------------------------
>
> Key: RF-13348
> URL: https://issues.jboss.org/browse/RF-13348
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 5.0.0.Alpha2
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 5.0.0.Alpha2
>
>
> {{collumnClass}} attribute of {{r:pickList}} behaves in this way in *RF5*:
> Suppose a {{pickList}}, which items consist from _three_ columns.
> * if you set {{collumnClass}} to: {{foo bar}}, then first column has class {{foo}}, the second one {{bar}}
> * if you set it to {{foo, bar}}, then the first column has class {{foo,bar}} - expected
> In *RF4*, it was different though:
> * it worked as {{collumnClass}} for {{dataTable}}. Literally as it is described in VDL doc:
> bq. Assigns one or more space-separated CSS class names to the columns of the table. If the CSS class names are comma-separated, each class will be assigned to a particular column in the order they follow in the attribute. If you have less class names than columns, the class will be applied to every n-fold column where n is the order in which the class is listed in the attribute. If there are more class names than columns, the overflow ones are ignored.
> The way how it worked in RF4 seems more reasonable for me. What is your opinion on this ?
--
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