DataTable issue regarding reflow, expandableRowGroups and headerRow

[kewlman]

Primefaces 6.2
Server: Payara-4.1.174
JSF: Mojarra 2.2.14


Hello,

I have an issue with the dataTable component when used with reflow=true, expandableRowGroups=true and with a headerRow defined.
In desktop mode the table is rendered as expected, but if it's displayed on small devices the columns are not rendered as expected.
The columns have a width of table-width/#columns instead of the whole width of the table.

When I use the dataTable with reflow=true, expandableRowGroups=false and without headerRow defined the table is rendered as expected.

Is this a bug or does the dataTable not support this combination of settings ?

The primefaces showcase for row groups does not have any example with reflow, so I could not check whether there is something wrong on my part.

Code: Select all

<p:dataTable var="event" 
                         value="#{alarmOverviewBean.events}"
                         rows="#{alarmOverviewBean.rows}"
                         first="#{alarmOverviewBean.start}"                         
                         paginatorPosition="top"
                         rowsPerPageTemplate="15,30,45"
                         reflow="true"
                         paginator="true"
                         pageLinks="5"                         
                         scrollable="true"
                         scrollHeight="100%"
                         sortBy="#{event.date}"
                         expandableRowGroups="true"
                         style="font-size: .75rem;">
               <p:headerRow>
                    <p:column colspan="8">
                        <h:outputText value="#{alarmOverviewBean.extractDate(event.setTime)}"/>
                    </p:column>
                </p:headerRow>
                <p:column styleClass="severity-column #{alarmOverviewBean.getStyleClass(event.severity)}">
                </p:column>

                <p:column headerText="#{msg.node}"
                          styleClass="node-column">                    
                    <h:outputText value="#{event.label}"/>
                </p:column>

                <p:column headerText="#{msg.name}"
                          styleClass="name-column">
                    <h:outputText value="#{translationBean.translate(alarmOverviewBean.getDescriptor(event.descriptorId).name)}" />
                </p:column>

                <p:column headerText="#{msg.set_time}"
                          styleClass="set-column">
                    <h:outputText value="#{alarmOverviewBean.getTimestamp(event)}" />
                </p:column>

                <p:column headerText="#{msg.reset_time}"
                          styleClass="reset-column">
                    <h:outputText value="#{alarmOverviewBean.getResetTime(event)}"/>
                </p:column>

                <p:column headerText="#{msg.event_code}"                        
                          styleClass="event-code-column">
                    <h:outputText value="#{event.errorCode}"/>
                </p:column>

                <p:column headerText="#{msg.trigger_value}"
                          styleClass="context-column">
                    <h:outputText value="#{event.triggerValue}"/>
                </p:column>              
</p:dataTable> 
 

[kukeltje]

Is this a bug or does the dataTable not support this combination of settings ?

I think the latter. Please file an enhancement in GitHub