[JBoss JIRA] (RF-7169) scrollableDataTable: first column disappears after crolling
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-7169?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem updated RF-7169:
------------------------------
Description:
see richfaces demo
Code to reproduce:
{code}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:a4j="http://richfaces.org/a4j"
xmlns:rich="http://richfaces.org/rich">
<style>
.scrolls{
width:300px;
height:200px;
overflow:auto;
}
</style>
<h:form>
<rich:spacer height="30" />
<rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px"
width="400px" id="carList" rows="40" columnClasses="col"
value="#{dataTableScrollerBean.allCars}" var="category" sortMode="single"
binding="#{dataTableScrollerBean.table}"
sortOrder="#{dataTableScrollerBean.order}"
selection="#{dataTableScrollerBean.selection}">
<rich:column id="make">
<f:facet name="header"><h:outputText styleClass="headerText" value="Make" /></f:facet>
<h:outputText value="#{category.make}" />
</rich:column>
<rich:column id="model">
<f:facet name="header"><h:outputText styleClass="headerText" value="Model" /></f:facet>
<h:outputText value="#{category.model}" />
<h:inputText value=""/>
</rich:column>
<rich:column id="price">
<f:facet name="header"><h:outputText styleClass="headerText" value="Price" /></f:facet>
<h:outputText value="#{category.price}" />
</rich:column>
<rich:column id="mileage">
<f:facet name="header"><h:outputText styleClass="headerText" value="Mileage" /></f:facet>
<h:outputText value="#{category.mileage}" />
</rich:column>
<rich:column width="200px" id="vin">
<f:facet name="header"><h:outputText styleClass="headerText" value="VIN" /></f:facet>
<h:outputText value="#{category.vin}" />
</rich:column>
<rich:column id="stock">
<f:facet name="header"><h:outputText styleClass="headerText" value="Stock" /></f:facet>
<h:outputText value="#{category.stock}" />
<h:inputText value=""/>
</rich:column>
</rich:scrollableDataTable>
<rich:spacer height="20px"/>
<a4j:commandButton value="Show Current Selection" reRender="table"
action="#{dataTableScrollerBean.takeSelection}"
oncomplete="javascript:Richfaces.showModalPanel('panel');"/>
</h:form>
<rich:modalPanel id="panel" autosized="false" keepVisualState="false" width="315" height="230">
<f:facet name="header">
<h:outputText value="Selected Rows"/>
</f:facet>
<f:facet name="controls">
<span style="cursor:pointer" onclick="javascript:Richfaces.hideModalPanel('panel')">X</span>
</f:facet>
<h:panelGroup layout="block" styleClass="scrolls">
<rich:dataTable value="#{dataTableScrollerBean.selectedCars}" var="sel" id="table">
<rich:column>
<f:facet name="header"><h:outputText value="Make" /></f:facet>
<h:outputText value="#{sel.make}" />
</rich:column>
<rich:column id="model">
<f:facet name="header"><h:outputText value="Model" /></f:facet>
<h:inputText value=""/>
</rich:column>
<rich:column id="price">
<f:facet name="header"><h:outputText value="Price" /></f:facet>
<h:outputText value="#{sel.price}" />
</rich:column>
<rich:column id="mileage">
<f:facet name="header"><h:outputText value="Mileage" /></f:facet>
<h:outputText value="#{sel.mileage}" />
</rich:column>
<rich:column id="stock">
<f:facet name="header"><h:outputText value="Stock" /></f:facet>
<h:inputText value=""/>
</rich:column>
</rich:dataTable>
</h:panelGroup>
</rich:modalPanel>
</ui:composition>
{code}
was:see richfaces demo
> scrollableDataTable: first column disappears after crolling
> -----------------------------------------------------------
>
> Key: RF-7169
> URL: https://issues.jboss.org/browse/RF-7169
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility, component-ScrollableDataTable
> Affects Versions: 3.3.1
> Environment: richfaces-demo
> IE 8
> Reporter: Tsikhon Kuprevich
> Priority: Minor
> Fix For: 3.Future
>
>
> see richfaces demo
> Code to reproduce:
> {code}
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich">
> <style>
> .scrolls{
> width:300px;
> height:200px;
> overflow:auto;
> }
> </style>
> <h:form>
> <rich:spacer height="30" />
> <rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px"
> width="400px" id="carList" rows="40" columnClasses="col"
> value="#{dataTableScrollerBean.allCars}" var="category" sortMode="single"
> binding="#{dataTableScrollerBean.table}"
> sortOrder="#{dataTableScrollerBean.order}"
> selection="#{dataTableScrollerBean.selection}">
> <rich:column id="make">
> <f:facet name="header"><h:outputText styleClass="headerText" value="Make" /></f:facet>
> <h:outputText value="#{category.make}" />
> </rich:column>
> <rich:column id="model">
> <f:facet name="header"><h:outputText styleClass="headerText" value="Model" /></f:facet>
> <h:outputText value="#{category.model}" />
> <h:inputText value=""/>
> </rich:column>
> <rich:column id="price">
> <f:facet name="header"><h:outputText styleClass="headerText" value="Price" /></f:facet>
> <h:outputText value="#{category.price}" />
> </rich:column>
> <rich:column id="mileage">
> <f:facet name="header"><h:outputText styleClass="headerText" value="Mileage" /></f:facet>
> <h:outputText value="#{category.mileage}" />
> </rich:column>
> <rich:column width="200px" id="vin">
> <f:facet name="header"><h:outputText styleClass="headerText" value="VIN" /></f:facet>
> <h:outputText value="#{category.vin}" />
> </rich:column>
> <rich:column id="stock">
> <f:facet name="header"><h:outputText styleClass="headerText" value="Stock" /></f:facet>
> <h:outputText value="#{category.stock}" />
> <h:inputText value=""/>
> </rich:column>
> </rich:scrollableDataTable>
> <rich:spacer height="20px"/>
> <a4j:commandButton value="Show Current Selection" reRender="table"
> action="#{dataTableScrollerBean.takeSelection}"
> oncomplete="javascript:Richfaces.showModalPanel('panel');"/>
> </h:form>
> <rich:modalPanel id="panel" autosized="false" keepVisualState="false" width="315" height="230">
> <f:facet name="header">
> <h:outputText value="Selected Rows"/>
> </f:facet>
> <f:facet name="controls">
> <span style="cursor:pointer" onclick="javascript:Richfaces.hideModalPanel('panel')">X</span>
> </f:facet>
> <h:panelGroup layout="block" styleClass="scrolls">
> <rich:dataTable value="#{dataTableScrollerBean.selectedCars}" var="sel" id="table">
> <rich:column>
> <f:facet name="header"><h:outputText value="Make" /></f:facet>
> <h:outputText value="#{sel.make}" />
> </rich:column>
> <rich:column id="model">
> <f:facet name="header"><h:outputText value="Model" /></f:facet>
> <h:inputText value=""/>
> </rich:column>
> <rich:column id="price">
> <f:facet name="header"><h:outputText value="Price" /></f:facet>
> <h:outputText value="#{sel.price}" />
> </rich:column>
> <rich:column id="mileage">
> <f:facet name="header"><h:outputText value="Mileage" /></f:facet>
> <h:outputText value="#{sel.mileage}" />
> </rich:column>
> <rich:column id="stock">
> <f:facet name="header"><h:outputText value="Stock" /></f:facet>
> <h:inputText value=""/>
> </rich:column>
> </rich:dataTable>
> </h:panelGroup>
> </rich:modalPanel>
> </ui:composition>
> {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
11 years, 6 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by santhosh siravuri (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
santhosh siravuri commented on RF-12675:
----------------------------------------
Removing dragIndicator get's rid of JSE but then it fails with NPE because of https://issues.jboss.org/browse/RF-10967
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: Drag, drop, myfaces
> Fix For: 4.3.3, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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, 6 months
[JBoss JIRA] (RF-8701) dataScroller: add facets support for customizations
by Dennis Detoya (JIRA)
[ https://issues.jboss.org/browse/RF-8701?page=com.atlassian.jira.plugin.sy... ]
Dennis Detoya commented on RF-8701:
-----------------------------------
Ok. tnx. ill try..:-)
> dataScroller: add facets support for customizations
> ---------------------------------------------------
>
> Key: RF-8701
> URL: https://issues.jboss.org/browse/RF-8701
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.ALPHA1
> Reporter: Ilya Shaikovsky
> Fix For: 5-Tracking
>
>
> Important Note: I do not see how some block components could be inserted into datascroller currently. That could potentially add lot of confusion and usage problems in future - so we have to discuss markup again. Many guys using "pages" facet redefinition and place some block controls/div based markup there.
> And, I prefer to sacrifice the "semantic" principles there again in order to avoid problems.
--
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, 6 months
[JBoss JIRA] (RF-8701) dataScroller: add facets support for customizations
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-8701?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem commented on RF-8701:
-----------------------------------
You could try something with some custom html/javascript and rich:componentControl.
> dataScroller: add facets support for customizations
> ---------------------------------------------------
>
> Key: RF-8701
> URL: https://issues.jboss.org/browse/RF-8701
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.ALPHA1
> Reporter: Ilya Shaikovsky
> Fix For: 5-Tracking
>
>
> Important Note: I do not see how some block components could be inserted into datascroller currently. That could potentially add lot of confusion and usage problems in future - so we have to discuss markup again. Many guys using "pages" facet redefinition and place some block controls/div based markup there.
> And, I prefer to sacrifice the "semantic" principles there again in order to avoid problems.
--
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, 6 months
[JBoss JIRA] (RF-8701) dataScroller: add facets support for customizations
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-8701?page=com.atlassian.jira.plugin.sy... ]
Brian Leathem updated RF-8701:
------------------------------
Fix Version/s: 5-Tracking
(was: 5-Future)
> dataScroller: add facets support for customizations
> ---------------------------------------------------
>
> Key: RF-8701
> URL: https://issues.jboss.org/browse/RF-8701
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.0.0.ALPHA1
> Reporter: Ilya Shaikovsky
> Fix For: 5-Tracking
>
>
> Important Note: I do not see how some block components could be inserted into datascroller currently. That could potentially add lot of confusion and usage problems in future - so we have to discuss markup again. Many guys using "pages" facet redefinition and place some block controls/div based markup there.
> And, I prefer to sacrifice the "semantic" principles there again in order to avoid problems.
--
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, 6 months
[JBoss JIRA] (RF-13056) Showcase - delete unused configuration for GAE
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13056?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13056:
-------------------------------
Fix Version/s: 5-Tracking
> Showcase - delete unused configuration for GAE
> ----------------------------------------------
>
> Key: RF-13056
> URL: https://issues.jboss.org/browse/RF-13056
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
> Fix For: 5-Tracking
>
>
> There are some files and configuration for Google App Engine in the showcase.
> IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
> Here is the list of files/configs which are redundant IMHO:
> * {{src/main/java-gae}}
> * {{src/main/webapp-gae}}
> * {{src/main/resources/logging.properties}}
> * {{pom.xml}} - profile for gae
> There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
> {code}
> 13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
> {code}
> According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}} to avoid worse consequences in the future.
--
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, 6 months
[JBoss JIRA] (RF-13056) Showcase - delete unused configuration for GAE
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13056?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13056:
-------------------------------
Fix Version/s: 5.0.0.Alpha2
(was: 5-Tracking)
> Showcase - delete unused configuration for GAE
> ----------------------------------------------
>
> Key: RF-13056
> URL: https://issues.jboss.org/browse/RF-13056
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
> Fix For: 5.0.0.Alpha2
>
>
> There are some files and configuration for Google App Engine in the showcase.
> IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
> Here is the list of files/configs which are redundant IMHO:
> * {{src/main/java-gae}}
> * {{src/main/webapp-gae}}
> * {{src/main/resources/logging.properties}}
> * {{pom.xml}} - profile for gae
> There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
> {code}
> 13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
> {code}
> According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}} to avoid worse consequences in the future.
--
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, 6 months
[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13046:
-------------------------------
Fix Version/s: 4.3.3
5-Tracking
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Fix For: 4.3.3, 5-Tracking
>
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
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, 6 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12675:
-------------------------------
Fix Version/s: 4.3.3
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Priority: Critical
> Labels: Drag, drop, myfaces
> Fix For: 4.3.3, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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, 6 months