You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, when a user wants to change CSS parameters of a Page classed div, it has to be done via page :has() mechanisms. While this works pretty well, it's not the most intuitive thing for folks new to CSS.
Its primary failing is it only permits setting CSS Properties to predefined values.
This issue proposes that we extend the single-branch mustache syntax to be appendable to a \page and inserted into the page classed div's style, class, and arbitrary add-on attributes as desired.
Additionally, to support setting values on the first page, we need to consider dropping a completely empty Page 1, treating the \page definition as the start of the page, not the end. By only dropping the empty page body, we maintain backward compatibility.
example syntax:
\page{--TOC:"'exclude'",wide,XCUSTOMATTR="'Foo'"}
I may have the quoting syntax inverted in the example.
The text was updated successfully, but these errors were encountered:
Your idea:
Presently, when a user wants to change CSS parameters of a Page classed div, it has to be done via
page :has()
mechanisms. While this works pretty well, it's not the most intuitive thing for folks new to CSS.Its primary failing is it only permits setting CSS Properties to predefined values.
This issue proposes that we extend the single-branch mustache syntax to be appendable to a
\page
and inserted into the page classed div's style, class, and arbitrary add-on attributes as desired.Additionally, to support setting values on the first page, we need to consider dropping a completely empty Page 1, treating the
\page
definition as the start of the page, not the end. By only dropping the empty page body, we maintain backward compatibility.example syntax:
The text was updated successfully, but these errors were encountered: