[JBoss JIRA] (RF-13099) Disabled input text is not visible
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13099?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13099:
-------------------------------
Workaround Description:
Style the disabled form elements using the following CSS:
{code}
input[type="text"]:disabled {
color:black;
}
select:disabled {
color:black;
}
{code}
Workaround: Workaround Exists
> Disabled input text is not visible
> ----------------------------------
>
> Key: RF-13099
> URL: https://issues.jboss.org/browse/RF-13099
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Kush Kumar
> Priority: Minor
> Labels: waiting_on_user
>
> Disabled input text is not visible -can you please help me out how can we make it visible or can we change the color of disabled text?
--
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, 9 months
[JBoss JIRA] (RF-13112) ScrollableDataTable: throws SCRIPT16389: Unspecified error after re-rendering and updating layout (e.g. when placed in TogglePanel)
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13112?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13112:
----------------------------
Summary: ScrollableDataTable: throws SCRIPT16389: Unspecified error after re-rendering and updating layout (e.g. when placed in TogglePanel) (was: ScrollableDataTable in TogglePanel: throws SCRIPT16389: Unspecified error)
> ScrollableDataTable: throws SCRIPT16389: Unspecified error after re-rendering and updating layout (e.g. when placed in TogglePanel)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13112
> URL: https://issues.jboss.org/browse/RF-13112
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 3.3.1.SP3, 3.3.3.Final
> Environment: Internet Explorer 8
> Reporter: Lukáš Fryč
>
> Use following example in richfaces-demo:
> {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>
> </style>
> <rich:simpleTogglePanel switchType="client" label="Add AJAX capability to existing JSF applications">
> <h:form>
> <rich:spacer height="30" />
> <rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px" width="700px" id="carList" rows="40" columnClasses="col"
> value="#{dataTableScrollerBean.allCars}" var="category" sortMode="multi">
> <rich:column id="make" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Make" />
> </f:facet>
> <h:outputText value="#{category.make}" />
> </rich:column>
> <rich:column id="model" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Model" />
> </f:facet>
> <h:outputText value="#{category.model}" />
> </rich:column>
> <rich:column id="price" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Price" />
> </f:facet>
> <h:outputText value="#{category.price}" />
> </rich:column>
> <rich:column id="mileage" sortable="true">
> <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" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="VIN" />
> </f:facet>
> <h:outputText value="#{category.vin}" />
> </rich:column>
> <rich:column id="stock" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Stock" />
> </f:facet>
> <h:outputText value="#{category.stock}" />
> </rich:column>
> </rich:scrollableDataTable>
> <rich:datascroller align="left" for="carList" maxPages="20"
> page="#{dataTableScrollerBean.scrollerPage}" id="sc2" />
> </h:form>
> </rich:simpleTogglePanel>
> <button onclick="var table=#{rich:component('carList')};console.log(table);)">Click me</button>
> </ui:composition>
> {code}
> Steps to reproduce:
> 1. open http://localhost:8080/patchtest/richfaces/dataTableScroller/examples/scro... in IE8
> 2. Click "»" or page 2 of the dataTableScroller
> 3. Shade the simpleTogglePanel.
--
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, 9 months
[JBoss JIRA] (RF-13112) ScrollableDataTable in TogglePanel: throws SCRIPT16389: Unspecified error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13112?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13112:
---------------------------------
The cause is that the method {{destroy}} is not never called.
As a workaround (and hopefully proper fix), we need to call this method before AJAX update.
To do that properly, we can leverage DOM cleanup mechanism, and register the "LayoutManager" as component to associated DOM element:
{code}
initialize: function($super, element, parentElement) {
$super(element, parentElement);
element.component = this;
element.component["rich:destructor"] = 'destroy';
...
{code}
The clean up will be called by [{{memory.js}}|https://source.jboss.org/browse/RichFaces/branches/enterprise/3.3.X/framework/impl/src/main/javascript/memory.js?r=14737#to80].
As part of cleanup, the {{destroy}} method will be called.
> ScrollableDataTable in TogglePanel: throws SCRIPT16389: Unspecified error
> -------------------------------------------------------------------------
>
> Key: RF-13112
> URL: https://issues.jboss.org/browse/RF-13112
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-ScrollableDataTable
> Affects Versions: 3.3.1.SP3, 3.3.3.Final
> Environment: Internet Explorer 8
> Reporter: Lukáš Fryč
>
> Use following example in richfaces-demo:
> {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>
> </style>
> <rich:simpleTogglePanel switchType="client" label="Add AJAX capability to existing JSF applications">
> <h:form>
> <rich:spacer height="30" />
> <rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px" width="700px" id="carList" rows="40" columnClasses="col"
> value="#{dataTableScrollerBean.allCars}" var="category" sortMode="multi">
> <rich:column id="make" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Make" />
> </f:facet>
> <h:outputText value="#{category.make}" />
> </rich:column>
> <rich:column id="model" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Model" />
> </f:facet>
> <h:outputText value="#{category.model}" />
> </rich:column>
> <rich:column id="price" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Price" />
> </f:facet>
> <h:outputText value="#{category.price}" />
> </rich:column>
> <rich:column id="mileage" sortable="true">
> <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" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="VIN" />
> </f:facet>
> <h:outputText value="#{category.vin}" />
> </rich:column>
> <rich:column id="stock" sortable="true">
> <f:facet name="header">
> <h:outputText styleClass="headerText" value="Stock" />
> </f:facet>
> <h:outputText value="#{category.stock}" />
> </rich:column>
> </rich:scrollableDataTable>
> <rich:datascroller align="left" for="carList" maxPages="20"
> page="#{dataTableScrollerBean.scrollerPage}" id="sc2" />
> </h:form>
> </rich:simpleTogglePanel>
> <button onclick="var table=#{rich:component('carList')};console.log(table);)">Click me</button>
> </ui:composition>
> {code}
> Steps to reproduce:
> 1. open http://localhost:8080/patchtest/richfaces/dataTableScroller/examples/scro... in IE8
> 2. Click "»" or page 2 of the dataTableScroller
> 3. Shade the simpleTogglePanel.
--
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, 9 months
[JBoss JIRA] (RF-13112) ScrollableDataTable in TogglePanel: throws SCRIPT16389: Unspecified error
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13112:
-------------------------------
Summary: ScrollableDataTable in TogglePanel: throws SCRIPT16389: Unspecified error
Key: RF-13112
URL: https://issues.jboss.org/browse/RF-13112
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-ScrollableDataTable
Affects Versions: 3.3.3.Final, 3.3.1.SP3
Environment: Internet Explorer 8
Reporter: Lukáš Fryč
Use following example in richfaces-demo:
{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>
</style>
<rich:simpleTogglePanel switchType="client" label="Add AJAX capability to existing JSF applications">
<h:form>
<rich:spacer height="30" />
<rich:scrollableDataTable rowKeyVar="rkv" frozenColCount="1" height="400px" width="700px" id="carList" rows="40" columnClasses="col"
value="#{dataTableScrollerBean.allCars}" var="category" sortMode="multi">
<rich:column id="make" sortable="true">
<f:facet name="header">
<h:outputText styleClass="headerText" value="Make" />
</f:facet>
<h:outputText value="#{category.make}" />
</rich:column>
<rich:column id="model" sortable="true">
<f:facet name="header">
<h:outputText styleClass="headerText" value="Model" />
</f:facet>
<h:outputText value="#{category.model}" />
</rich:column>
<rich:column id="price" sortable="true">
<f:facet name="header">
<h:outputText styleClass="headerText" value="Price" />
</f:facet>
<h:outputText value="#{category.price}" />
</rich:column>
<rich:column id="mileage" sortable="true">
<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" sortable="true">
<f:facet name="header">
<h:outputText styleClass="headerText" value="VIN" />
</f:facet>
<h:outputText value="#{category.vin}" />
</rich:column>
<rich:column id="stock" sortable="true">
<f:facet name="header">
<h:outputText styleClass="headerText" value="Stock" />
</f:facet>
<h:outputText value="#{category.stock}" />
</rich:column>
</rich:scrollableDataTable>
<rich:datascroller align="left" for="carList" maxPages="20"
page="#{dataTableScrollerBean.scrollerPage}" id="sc2" />
</h:form>
</rich:simpleTogglePanel>
<button onclick="var table=#{rich:component('carList')};console.log(table);)">Click me</button>
</ui:composition>
{code}
Steps to reproduce:
1. open http://localhost:8080/patchtest/richfaces/dataTableScroller/examples/scro... in IE8
2. Click "»" or page 2 of the dataTableScroller
3. Shade the simpleTogglePanel.
--
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, 9 months
[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13111:
-------------------------------
Labels: lazy-loaded partial_state_saving (was: partial_state_saving)
> Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-13111
> URL: https://issues.jboss.org/browse/RF-13111
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Reporter: Andrey Zhemoytuk
> Assignee: Brian Leathem
> Labels: lazy-loaded, partial_state_saving
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
> To reproduce try this snippet:
> {code:xml}
> <h:form>
> <rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
> </rich:dataTable>
> <a4j:commandButton value="Postback" execute="@this" render="result"/>
> </h:form>
>
> <h:panelGroup id="result">
> #{invoked}
> </h:panelGroup>
> {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, 9 months
[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13111:
-------------------------------
Fix Version/s: 5-Tracking
> Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-13111
> URL: https://issues.jboss.org/browse/RF-13111
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Reporter: Andrey Zhemoytuk
> Assignee: Brian Leathem
> Labels: lazy-loaded, partial_state_saving
> Fix For: 5-Tracking
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
> To reproduce try this snippet:
> {code:xml}
> <h:form>
> <rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
> </rich:dataTable>
> <a4j:commandButton value="Postback" execute="@this" render="result"/>
> </h:form>
>
> <h:panelGroup id="result">
> #{invoked}
> </h:panelGroup>
> {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, 9 months
[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
by Andrey Zhemoytuk (JIRA)
[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ]
Andrey Zhemoytuk updated RF-13111:
----------------------------------
Description:
Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
To reproduce simply try this snipplet:
{code:xml}
<h:form>
<rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
</rich:dataTable>
<a4j:commandButton value="Postback" execute="@this" render="result"/>
</h:form>
<h:panelGroup id="result">
#{invoked}
</h:panelGroup>
{code}
was:
In Richfaces 4 both datatable and extendedDatatable evaluate the value attribute even when rendered is set to false, even though it is not necessary. This makes it hard to achieve performance by trimming parts of the view tree. The built-in h:dataTable behaves correctly in that case.
To reproduce simply try this snipplet:
{code:xml}
<h:form>
<rich:dataTable value="#{myBean.property}" rendered="false">
</rich:dataTable>
</h:form>
{code}
Side note: The reason I'm posting this is, that i want to embed a rich:dataTable in a ajax loaded rich:togglePanelItem which is loaded on demand. Probably fixing the "render" problem will also make the dataTable lazy-loadable when switching to the corresponding togglePanelItem.
I hope this is no duplicate, I only found RichFaces 3 issues mentioning this problem.
> Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-13111
> URL: https://issues.jboss.org/browse/RF-13111
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Reporter: Andrey Zhemoytuk
> Assignee: Brian Leathem
> Labels: partial_state_saving
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
> To reproduce simply try this snipplet:
> {code:xml}
> <h:form>
> <rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
> </rich:dataTable>
> <a4j:commandButton value="Postback" execute="@this" render="result"/>
> </h:form>
>
> <h:panelGroup id="result">
> #{invoked}
> </h:panelGroup>
> {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, 9 months
[JBoss JIRA] (RF-13111) Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
by Andrey Zhemoytuk (JIRA)
[ https://issues.jboss.org/browse/RF-13111?page=com.atlassian.jira.plugin.s... ]
Andrey Zhemoytuk updated RF-13111:
----------------------------------
Description:
Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
To reproduce try this snippet:
{code:xml}
<h:form>
<rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
</rich:dataTable>
<a4j:commandButton value="Postback" execute="@this" render="result"/>
</h:form>
<h:panelGroup id="result">
#{invoked}
</h:panelGroup>
{code}
was:
Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
To reproduce simply try this snipplet:
{code:xml}
<h:form>
<rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
</rich:dataTable>
<a4j:commandButton value="Postback" execute="@this" render="result"/>
</h:form>
<h:panelGroup id="result">
#{invoked}
</h:panelGroup>
{code}
> Data Iteration components evaluate value on postback even if not rendered when partial state saving is turned off
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-13111
> URL: https://issues.jboss.org/browse/RF-13111
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.3
> Reporter: Andrey Zhemoytuk
> Assignee: Brian Leathem
> Labels: partial_state_saving
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Iteration components (datatable and extendedDatatable) evaluate the value attribute even when rendered is set to false, even though it is not necessary.
> To reproduce try this snippet:
> {code:xml}
> <h:form>
> <rich:dataTable rendered="false" value="#{viewScope.put('invoked', true)}">
> </rich:dataTable>
> <a4j:commandButton value="Postback" execute="@this" render="result"/>
> </h:form>
>
> <h:panelGroup id="result">
> #{invoked}
> </h:panelGroup>
> {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, 9 months