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

break-inside for columns. #1317

Open
Fyrd opened this Issue May 12, 2015 · 5 comments

Comments

Projects
None yet
5 participants
@Fyrd
Owner

Fyrd commented May 12, 2015

break-inside for columns.


This issue was imported from Google Moderator

Moderator votes: +5
Issue added by rdoyle on 2014-10-29
To vote this issue up or down, simply include +1 or -1 in your comment.

@m-artin

This comment has been minimized.

Show comment
Hide comment

m-artin commented Jan 21, 2016

+1

@ndorfin

This comment has been minimized.

Show comment
Hide comment
@ndorfin

ndorfin Aug 18, 2017

Not sure, but it looks like this is covered by http://caniuse.com/#feat=css-page-break ?

ndorfin commented Aug 18, 2017

Not sure, but it looks like this is covered by http://caniuse.com/#feat=css-page-break ?

@shrpne

This comment has been minimized.

Show comment
Hide comment

shrpne commented Jan 19, 2018

+1

@shrpne

This comment has been minimized.

Show comment
Hide comment
@shrpne

shrpne Feb 18, 2018

@Fyrd break-inside, break-after and break-before are generic properties to control break rules for columns, pages, and regions.
So I think http://caniuse.com/#feat=css-page-break should be reworked and became a part of break- properties

shrpne commented Feb 18, 2018

@Fyrd break-inside, break-after and break-before are generic properties to control break rules for columns, pages, and regions.
So I think http://caniuse.com/#feat=css-page-break should be reworked and became a part of break- properties

@rachelandrew

This comment has been minimized.

Show comment
Hide comment
@rachelandrew

rachelandrew Apr 1, 2018

I think the break-* data is also incorrect. Chrome appears to support break-before and break-after. It's pretty confusing lumping the old page-break-* with the new ones. It would be useful for people to be able to see exactly what combination of these things will work for them.

I think the break-* data is also incorrect. Chrome appears to support break-before and break-after. It's pretty confusing lumping the old page-break-* with the new ones. It would be useful for people to be able to see exactly what combination of these things will work for them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment