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
Incorrect support data (example: BrowserX says "86" but support was added in "40")
Chrome does support break-after:always, But Firefox only supports this in print media, so FF has partial support, and Chrome full support of always.
break-after:always
always
Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox
Chrome should have mark of full support
Tested at https://homebrewery.naturalcrit.com/. Homepage appears different in chrome vs Firefox, with incorrect layout in Firefox.
No response
https://developer.mozilla.org/en-US/docs/Web/CSS/break-after
css.properties.break-after
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
Chrome does support
break-after:always
, But Firefox only supports this in print media, so FF has partial support, and Chrome full support ofalways
.What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox
What did you expect to see?
Chrome should have mark of full support
Did you test this? If so, how?
Tested at https://homebrewery.naturalcrit.com/. Homepage appears different in chrome vs Firefox, with incorrect layout in Firefox.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/CSS/break-after
MDN metadata
MDN page report details
css.properties.break-after
The text was updated successfully, but these errors were encountered: