[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 edited comment on RF-13348 at 11/25/13 8:56 AM:
------------------------------------------------------------
I am reopening the issue, because it is not behaving as the doc describes.
IMHO it is a bug and that the doc is correct.
It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns
* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column
Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout....
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.
My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be applied to the columns greater than the number of classes. If however the final class in the list is the `*` character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order the class in this list.
It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
Also if you can confirm it I can reopen [the upstream change|https://github.com/richwidgets/richwidgets/commit/1fc6d73b1a78669d...] which is behind it.
was (Author: jhuska):
I am reopening the issue, because it is not behaving as the doc describes.
IMHO it is a bug and that the doc is correct.
It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns
* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column
Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout....
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.
My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be applied to the columns greater than the number of classes. If however the final class in the list is the `*` character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order the class in this list.
It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
> 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 Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Juraj Húska edited comment on RF-13348 at 11/25/13 8:53 AM:
------------------------------------------------------------
I am reopening the issue, because it is not behaving as the doc describes.
IMHO it is a bug and that the doc is correct.
It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns
* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column
Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout....
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.
My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be applied to the columns greater than the number of classes. If however the final class in the list is the `*` character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order the class in this list.
It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
was (Author: jhuska):
I am reopening the issue, because it is not behaving as the doc describes.
IMHO it is a bug and that the doc is correct.
It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns
* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column
Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout....
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.
My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be
applied to the columns greater than the number of classes. If however the final class in the list is the `*`
character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order
the class in this list.
It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
> 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 Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13348?page=com.atlassian.jira.plugin.s... ]
Juraj Húska reopened RF-13348:
------------------------------
I am reopening the issue, because it is not behaving as the doc describes.
IMHO it is a bug and that the doc is correct.
It is behaving like this:
* *comma separated classes* -->
** _expected:_ provided classes applied to each column
** _actual:_ provided classes applied to individual columns
* *space separated classes* -->
** _expected:_ classes for individual columns
** _actual:_ all provided classes applied only for first column
Steps to reproduce:
# load Metamer at:
http://localhost:8080/metamer/faces/components/richPickList/columnLayout....
# set {{columnClasses}} to: _foo,bar,blah_
# inspect the first item, see that the first column has class _blah_, second the _bar_ and the third one class _blah_.
My another concern is abut this part:
bq. If the number of classes in this list is less than the number of column children, then no class will be
applied to the columns greater than the number of classes. If however the final class in the list is the `*`
character, the classes will instead be applied in a repeating manner every n-fold column, where n is the order
the class in this list.
It works only with classes comma separated, so if that is correct the doc should state it. I can create a doc issue if you can confirm my objections ?
> 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-13380) Error 404 not found for fonts
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved RF-13380.
-----------------------------
Resolution: Done
> Error 404 not found for fonts
> -----------------------------
>
> Key: RF-13380
> URL: https://issues.jboss.org/browse/RF-13380
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf. To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf. To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}
--
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-13380) Error 404 not found for fonts
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13380?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13380:
---------------------------------
Upstream issue: https://github.com/richwidgets/richwidgets/issues/143
> Error 404 not found for fonts
> -----------------------------
>
> Key: RF-13380
> URL: https://issues.jboss.org/browse/RF-13380
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: base functionality
> Affects Versions: 5.0.0.Alpha2
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> Reporter: Pavol Pitonak
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: 5.0.0.Alpha2
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/a4jAjax/hCommandButton.xhtml
> # see browser console
> result:
> * several resources are missing
> * Chrome console contains these errors:
> {quote}
> GET http://localhost:8080/metamer/faces/components/a4jAjax/RES_NOT_FOUND 404 (Not Found) hCommandButton.xhtml:27
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) hCommandButton.xhtml:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.ttf:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Regular-webfont.svg#OpenSansRegular:1
> GET http://localhost:8080/metamer/org.richfaces.resources/javax.faces.resourc... 404 (Not Found) :8080/metamer/org.richfaces.resources/javax.faces.resource/fonts/OpenSans-Semibold-webfont.svg#OpenSansSemibold:1
> {quote}
> * when deployed to JBoss AS 7.1.1.Final, you can see these warnings in server log
> {quote}
> 12:12:53,342 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,341 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.woff. To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,392 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-6) JSF1091: No mime type could be found for file fonts/OpenSans-Regular-webfont.ttf. To resolve this, add a mime-type mapping to the applications web.xml.
> 12:12:53,393 WARNING [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-3) JSF1091: No mime type could be found for file fonts/OpenSans-Semibold-webfont.ttf. To resolve this, add a mime-type mapping to the applications web.xml.
> {quote}
--
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-13381) Hotkey doesn't work with picklist
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13381:
----------------------------------
Summary: Hotkey doesn't work with picklist
Key: RF-13381
URL: https://issues.jboss.org/browse/RF-13381
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-misc, component-selects, regression
Affects Versions: 5.0.0.Alpha2
Environment: Showcase 5.0.0-SNAPSHOT
Reporter: Pavol Pitonak
# open http://showcaselatest-richfaces.rhcloud.com/richfaces/component-sample.js...
# click on first item in "Available cities" list
# press right arrow key on keyboard
# press End button on keyboard
result:
* nothing happens
expected:
* selected item moves to to righ list after pressing right arrow
* all items from left list should move to the right after pressing End button
--
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
