We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
When each cell of a row is merged with the same cell on the next row, a table row like this will be produced:
.2+| ten .2+| eleven
As this seems to be correct, it will break the rendering of the table in Asciidoctor with an error
dropping cell because it exceeds specified number of columns
To Reproduce
Here is an AsciiDoc snippet which reproduces the Asciidoctor bug:
|=== | one | two | three | four .2+| five | six | seven | eight | nine .2+| ten .2+| eleven | next | next | next | next |===
An excel file which reproduces the behaviour has to be created.
Expected behavior
The whole table is rendered. I guess it would be enough to remove the rowspans
The text was updated successfully, but these errors were encountered:
fix #1192 exportExcel rowspans
517cac9
Merge pull request #1223 from docToolchain/1192-exportexcel-unnecessa…
d87e07c
…ry-rowspans-break-rendering-of-table fix #1192 exportExcel rowspans
rdmueller
Successfully merging a pull request may close this issue.
Describe the bug
When each cell of a row is merged with the same cell on the next row, a table row like this will be produced:
As this seems to be correct, it will break the rendering of the table in Asciidoctor with an error
To Reproduce
Here is an AsciiDoc snippet which reproduces the Asciidoctor bug:
An excel file which reproduces the behaviour has to be created.
Expected behavior
The whole table is rendered. I guess it would be enough to remove the rowspans
The text was updated successfully, but these errors were encountered: