-
-
Notifications
You must be signed in to change notification settings - Fork 686
New issue
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
'column-span: all' triggers all kinds of errors #984
Comments
Hello @Tontyna Please, take a look at: #981 (comment) This may give some more clarifications about the IndexError Exceptions. |
The special treatment of boxes with Tried to defang and repair the wrecked skip_stack and to skip the already rendered In desparation I finally brute-forced the initial original root-tree to separate the original tree
defused tree
Of course, though the crashes disappear and the snippets are balanced and rendered as expected, this is an insane solution. Hoping for somebody else finding the fix, someone more familiar with skip-stacks than I am. |
As for flexboxes, where the order of rendered boxes can be changed, columns layout changes the tree in a complex way, totally breaking the There's no need to find a workaround for that. It's broken. To close #36 (yes, yes, I know, it's nearly 7 years old…) we'll have change the way skip stacks are stored. We don't have the same needs depending on the layout of the box, so we can have different structures at different levels. And, of course, as we can have parallel flows, we'll have more than one for each level. That's the fix we need. |
Therefore I propose to remove the |
It's time for this redesign. Let's say version 52 is the moment when we implement parallel flows. |
I'm not sure if this is the same issue, but it may be close enough to warrant placing it here rather than in its own issue. The bottom of the box carries over for all pages (at minimum padding and margin) when there is a colum-span:all. Here's a bare bones example that demonstrates the issue as presented in this image:
|
Confirmed to still have the same issue in release 52. (Also: thank you for release 52!!!) |
This issue is also the reason for the broken rendering |
Related to (duplicate of?) #1604. |
If other people are interested in reproducing the bugs, the original samples give the right errors using: body {
font-family: Liberation Serif;
font-size: 13pt;
} |
Snippet to produce duplicates:
Snippet to produce infinite loop:
Snippet to crash with AssertionError:
The text was updated successfully, but these errors were encountered: