-
-
Notifications
You must be signed in to change notification settings - Fork 706
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
Balance columns before "column-span: all" #1914
Comments
Hi! Is your problem related to #980? |
Sorry, I did a search in the issues already open, but I did not find it. However I am not sure it is related, since my image is a direct child of the only multi-column element (body). However I will make some test to be sure it is not related to that issue. I will try to write a minimal example that reassembles my scenario. |
Then maybe you forgot to set |
There was a Why the white-space in the top-right section? If I open the same file with firefox I got that area filled by text, as I would expect. The relevant tags are:
It contains just a long lorem ipsum text, then:
|
Could you please share a full HTML/CSS sample, so that we can easily reproduce your problem? |
Why do you use |
I used the However I do not know if the CSS specification mandates a behavior or not. The only things I can say against the weasyprint output are:
[1] In other words, I like this: and I dislike this: [2] Screenshot from firefox: |
We don’t write WeasyPrint following "logic", or what other browsers do. We try to follow the specification. I don’t say that Firefox and Chrome are right or wrong, I want to know what the specification tells in this case. So, we’ll be happy to implement what’s in the specification! The next step is thus to find in it what we exactly have to do. |
Me neither. I spoke about the two browsers just as a hint that MAYBE a specification exists, and it demands something like that output. But I agree with you that it is not enough to start changing stuff inside WeasyPrint.
100% agree also on this but I was not able to find the answer on the W3C specification, so for now I will just switch to the |
The answer is in the
|
Is the column-span attribute correctly handled? In my experimentation it seems just ignored, but maybe I am missing something. I used it as a property of an img tag.
The text was updated successfully, but these errors were encountered: