[
https://issues.apache.org/jira/browse/DOXIA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678926#comment-17678926
]
Fred Eckertson commented on DOXIA-590:
--------------------------------------
[~michael-o]
Basing zebra striping based on tr:nth-child(odd) does not work with hidden
rows... period.
The a/b approach does work, but some a/b class names *might* need to be
reversed as rows are [un]hidden and care must be taken when assigning the
initial a/b values if the tables is born with hidden rows. Unfortunately,
doxia does support starting out with rows already hidden because it insists on
applying odd/even <-> a/b.
[My use
case|https://github.com/cerner/ccl-testing/blob/main/cerreal-maven-plugin] is a
page for showing unit test statuses. It has tables listing information for
*every* suite/test/assert, but normally one only wants to focus on *failed
stuff* so there are
[checkboxes|https://github.com/cerner/ccl-testing/blob/main/cerreal-maven-plugin/src/main/java/com/cerner/ccl/testing/maven/ccl/reports/CerrealReportGenerator.java#L91]
to toggle the visibility of failed suites/tests/asserts. I would like to
start off with the not failed things already hidden, but that is not really an
option and changing the a/b classes immediately after rendering the page causes
spastic flickering so I settled for starting off with everything displayed
which is less than ideal.
> Either provided element class or default class gets ignored
> -----------------------------------------------------------
>
> Key: DOXIA-590
> URL: https://issues.apache.org/jira/browse/DOXIA-590
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.8
> Reporter: Fred Eckertson
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M3
>
> Attachments: image-2022-05-18-21-57-40-619.png
>
>
> The following construct is somewhat common in doxia-core
> att.addAttribute( Attribute.CLASS, "a" );
> The documentation says that basic attributes (including CLASS) are supported.
> However in cases like this either that "a" or the CLASS that was provided in
> the attributes parameter will be ignored. The correct way to do this is to
> append the provided CLASS to "a " if a CLASS attribute was provided.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
