-
Notifications
You must be signed in to change notification settings - Fork 72
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
Support Paged Media #137
Comments
Would a PR with How about adding the function implementing the |
That sounds like a reasonable approach. |
@dbaynard do you want to create a PR? |
Stale issue message |
Any progress on this? This would be really nice to have. |
@JonathanReeve If someone creates a PR I'll review and merge. @dbaynard are you still interested? |
This issue has not seen any activity in a long time. If no further activity occurs, it will be closed after ten weeks. |
Hello, please forgive my delay. I was keen in 2017; I'm now not sure I'll be using clay, in future. It looks like I should respond on #173, first; if that is a positive experience all round, I'll put together a plan, at least, for this feature. |
Hello,
Clay is already nearly there when it comes to supporting paged media, for use with
@media print
in browsers or dedicated typesetters such as Prince.Many of the changes are simply adding combinators; a suitable
Clay.Paged
module might be suitable.One change is more substantial.
@page
queries can take nested css, like@media
queries. For example, the following displays the line "This page is intentionally left blank" at the top of any page which has the associated pseudo-selectorblank
.It looks like extending, replacing or complementing the
query
functions to handle more than justmedia
queries would be the best way to go about implementing this. As it stands my workaround involves wrapping the@top-center { … }
using a monster regular expression in vim.It would be good to fully support the CSS paged media spec. How would this best be done?
See https://www.smashingmagazine.com/2015/01/designing-for-print-with-css/ for a good description of the capabilities.
The text was updated successfully, but these errors were encountered: