| Summary: | nested groups are not rendered correctly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Matteo Di Liberto Gasparin <mdiliberto> | ||||
| Component: | BIRT | Assignee: | Birt-ReportEngine-inbox <Birt-ReportEngine-inbox> | ||||
| Status: | NEW --- | QA Contact: | Maggie Shen <lshen> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | a.j.winkworth, bianca.dietz, bluesoldier, h.vonbargen, jlebiannic | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
*** Bug 379479 has been marked as a duplicate of this bug. *** More information in my closed duplicate report below. It seems to be effecting all emitters that I have tried. This bug is a big issue for me. The functionality BIRT provides with grouping data sets is exactly what I need, but I can't really use it, as long as the tables are messed up. It would be amazing if someone could look into it because I don't think that I'm able to fix this myself. |
Created attachment 201969 [details] report design showing the bug Using multiple nested groups with the "drop" option I get an ugly "staircase effect". The attachment shows an example. Looking at the produced html you can see that after the <td> element containing the first cell (which, by the way, spans the wrong number of rows) there are numCols - 1 <td> empty elements, and so on for the following cells. Seems like the "drop" option is effectively ignored for the purpose of laying out the table