Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.1-Beta
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Tomcat 7.0.12
Description
In the Williams application, there is a component at the top affecting the state of the ace:datatable:
<f:ajax render="@form :WgpMainMessageNotificationBarStatus" execute="@this"
listener="#{confirmationPdaBean.confirmingLevelChange}">
<h:selectOneMenu id="confirmingLevelFilter" label="Confirming Level" rendered="#{!confirmationPdaBean.downloadPages}"
value="#{confirmationPdaBean.confirmingLevelFilterObject}" required="true"
onchange="showProcessingMessage('Processing Filter Change')">
<f:selectItem itemValue="#{null}" itemLabel="NONE SELECTED"
noSelectionOption="true" />
<f:selectItems value="#{confirmationPdaBean.confirmingLevelItems}" />
</h:selectOneMenu>
</f:ajax>
The listener is changing the value of the ace:dataTable to a datatable with more columns. When the update is applied, only the previous number of columns are displayed and the final column spans the width of the other headers (see attached screenshot).
The empty space in the datatable should be populated with content.
<f:ajax render="@form :WgpMainMessageNotificationBarStatus" execute="@this"
listener="#{confirmationPdaBean.confirmingLevelChange}">
<h:selectOneMenu id="confirmingLevelFilter" label="Confirming Level" rendered="#{!confirmationPdaBean.downloadPages}"
value="#{confirmationPdaBean.confirmingLevelFilterObject}" required="true"
onchange="showProcessingMessage('Processing Filter Change')">
<f:selectItem itemValue="#{null}" itemLabel="NONE SELECTED"
noSelectionOption="true" />
<f:selectItems value="#{confirmationPdaBean.confirmingLevelItems}" />
</h:selectOneMenu>
</f:ajax>
The listener is changing the value of the ace:dataTable to a datatable with more columns. When the update is applied, only the previous number of columns are displayed and the final column spans the width of the other headers (see attached screenshot).
The empty space in the datatable should be populated with content.
Activity
Brad Kroeger
created issue -
Brad Kroeger
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | datatablecolumnissue.png [ 13596 ] |
Brad Kroeger
made changes -
Assignee | Ken Fyten [ ken.fyten ] |
Brad Kroeger
made changes -
Assignee | Ken Fyten [ ken.fyten ] | Nils Lundquist [ nils.lundquist ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 2.1 [ 10241 ] | |
Fix Version/s | 2.1-Beta [ 10291 ] | |
Assignee Priority | P1 |
Nils Lundquist
made changes -
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Assignee Priority | P1 | |
Assignee | Nils Lundquist [ nils.lundquist ] |
Ken Fyten
made changes -
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Fix Version/s | 2.1-Beta2 [ 10294 ] | |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Security | Private [ 10001 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
How are these columns being made dynamic? Just being toggled on by the application at that point using the rendered attribute?
We are currently experiencing some odd behavior elsewhere regarding the state of Column rendered.