[JBoss JIRA] (RF-13157) rich:dropDownMenu under rich:accordion cannot work
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-13157?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-13157:
------------------------------------
Did you try setting z-index on drop down menu? Unfortunately, there is no z-index attribute on JSF component so you need to use CSS directly.
> 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
11 years, 2 months
[JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13077?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13077 at 9/2/13 3:05 AM:
---------------------------------------------------------
After brain-storming, we have decided to use one RichFaces internal service which will delegate to multiple user-defined services loaded by ServiceLoader.
was (Author: lfryc):
After brain-storming, we have decided to use one RichFaces internal service which will delegate to multiple services loaded by ServiceLoader.
> Allow programatically configure Resource Mapping by exposing a service interface
> --------------------------------------------------------------------------------
>
> Key: RF-13077
> URL: https://issues.jboss.org/browse/RF-13077
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.).
> {code:java}
> public interface ResourceMapper {
> /**
> * @return null when no mapping should be involved
> public ResourceMapping mapResource(ResourceKey key);
> }
> public interface ResourceMapping {
> URL getURL(FacesContext context);
> }
> public interface StaticURLResourceMapping implements ResourceMapping {
> URL getURL();
> }
> public class FacesResourceMapping implements ResourceMapping {
> public ResourceKey getResourceKey() {
> ...
> }
> }
> {code}
> This way people may decide e.g. move all resources from given resource library to another library.
> This is related to RF-11543.
--
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
11 years, 2 months
[JBoss JIRA] (RF-13077) Allow programatically configure Resource Mapping by exposing a service interface
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13077?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13077:
---------------------------------
After brain-storming, we have decided to use one RichFaces internal service which will delegate to multiple services loaded by ServiceLoader.
> Allow programatically configure Resource Mapping by exposing a service interface
> --------------------------------------------------------------------------------
>
> Key: RF-13077
> URL: https://issues.jboss.org/browse/RF-13077
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: resource handling
> Affects Versions: 5.0.0.Alpha2
> Reporter: Lukáš Fryč
> Assignee: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> A concept of a service should allow to programatically provide a mapped URL for a resource, either local one (JSF resource) or remote (on static server, CDN, etc.).
> {code:java}
> public interface ResourceMapper {
> /**
> * @return null when no mapping should be involved
> public ResourceMapping mapResource(ResourceKey key);
> }
> public interface ResourceMapping {
> URL getURL(FacesContext context);
> }
> public interface StaticURLResourceMapping implements ResourceMapping {
> URL getURL();
> }
> public class FacesResourceMapping implements ResourceMapping {
> public ResourceKey getResourceKey() {
> ...
> }
> }
> {code}
> This way people may decide e.g. move all resources from given resource library to another library.
> This is related to RF-11543.
--
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
11 years, 2 months
[JBoss JIRA] (RF-13126) ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
by Steven W. (JIRA)
[ https://issues.jboss.org/browse/RF-13126?page=com.atlassian.jira.plugin.s... ]
Steven W. commented on RF-13126:
--------------------------------
Thanks for your follow-up - I am not seeing the new table state format that you referred to; please point me to it exactly ala expected json in full (that test class also seemed to conform) - following is what I record as being set under 5.0 Alpha 1 (I was not able to get overnight snapshot going because of a complaint about action methods for rich:commandLink) -
{"
columnsVisibility":{"col0":"1","col1":"1","col2":"1","col3":"1","col4":"1","col5":"1","col6":"1","col7":"1","col8":"1","col9":"1"},"columnGroupingState":{},"columnsSizeState":{"col0":"0","col1":"250","col2":"110","col3":"100","col4":"94","col5":"250","col6":"200","col7":"120","col8":"228","col9":"100"},"columnsOrder":["col0","col1","col2","col3","col4","col5","col6","col7","col8","col9"]}
> ExtendedDataTable Header Column Widths does not conform to Row Data Column Widths specified in TableState
> ----------------------------------------------------------------------------------------------------------
>
> Key: RF-13126
> URL: https://issues.jboss.org/browse/RF-13126
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 5.0.0.Alpha1
> Environment: Windows / Tomcat 7 / JDK 1.7 (Firefox & IE)
> Reporter: Steven W.
>
> In prior 3.x release the ExtendedDataTable control supported TableState data for sizing of columns - this worked relatively well *however* there is/was a bug such that the columns headers above the table did *not* align properly with the data rows of the table below; this could be partially accommodated by specifying a size for the column (in the TableState data) that was wider than the longest string in the column data as he initial / minimum size.
> In subsequent release (in 4.x time frame I believe) the control was refactored and the TableState capability as a whole was lost - I saw this in another report on the forum or Jira though not the same but other related issues may be RF-4855 + RF-13094 and RF-13095 ; the report I remember reading, however, is that this TableState functionality was lost during the refactoring and was then said to be restored in a subsequent release.
> I am now using Version 5 of RichFaces to include the first milestone and latest (overnight) snapshot and am confirming this column header sizing AND/OR TableState table header sizing issue(s) still remain, regardless of prior attempts to include TableState data recognition and, if/as so, the widths of the column headers does not respect the TableState data nor do they conform to the column widths of the data in the rows below.
--
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
11 years, 2 months