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
Improve support for break-* properties #127
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Plugin authors can register functions to hooks provided by the core code with `vivliostyle.plugin.registerHook` method. They can be removed by `vivliostyle.pulgin.removeHook` method. - Types of implemented hooks are listed in `vivliostyle.plugin.HOOKS`. - There is currently one hook: "SIMPLE_PROPERTY". See comments in code for details.
- Spec: https://drafts.csswg.org/css-break/#break-within - Values: auto | avoid | avoid-page | avoid-column | avoid-region - Note that the current implementation treat all values other than `auto` as the same as `avoid`. The fine-grained control (distinguishing `avoid`, `avoid-page`, `avoid-column` and `avoid-region`) will be a future task and tracked with a separate issue.
…alues for `break-before`/`break-after` properties - Spec: CSS Fragmentation Module - Forced Breaks https://drafts.csswg.org/css-break/#forced-breaks - Unforced Breaks https://drafts.csswg.org/css-break/#unforced-breaks - Note that though the spec requires to honor multiple break values at a single break point, the current implementation choose one of them and discard the others. The fine-grained control of these break values will be a future task and tracked with a separate issue.
kwkbtr
added a commit
that referenced
this pull request
Jan 7, 2016
Improve support for break-* properties
This was referenced Jan 7, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
page-break-*
properties are now treated as aliases forbreak-*
properties with page break values.break-*
properties according to the latest CSS Fragmentation Module specauto
break-inside
other thanauto
as the same asavoid
. The fine-grained control (distinguishingavoid
,avoid-page
,avoid-column
andavoid-region
) will be a future task and tracked with a separate issue.break-before
/break-after
values at a single break point, the current implementation choose one of them and discard the others. The fine-grained control of these break values will be a future task and tracked with a separate issue.