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
If a user wants to submit their brew to a physical printer, they'll typically run into a requirement for some sort of page margin/bleed (generally .125") or risk having white borders around their pages. It'd be neat to allow adding bleed to a brew. I think this gets tricky with pdf generation though, so maybe not worth tackling?
Here is a Share link for some CSS that would do the trick of allowing a variable margin size, adds a red border where the bleed begins, and automatically adjusts the footer graphic for PHB 5e and the page padding.
To print the PDF, I believe you have to use the system print dialog rather than Chrome's. And use a Custom Size Document, and set the size equal to your page height and width size + 2*margins.
Perhaps a better way to do this exists with JS or something, but this is what I've got.
This should probably be solved at a document level with CSS variables rather than fixed values. IME, bleed changes from printer to printer and print format to print format.
If a user wants to submit their brew to a physical printer, they'll typically run into a requirement for some sort of page margin/bleed (generally .125") or risk having white borders around their pages. It'd be neat to allow adding bleed to a brew. I think this gets tricky with pdf generation though, so maybe not worth tackling?
Here is a Share link for some CSS that would do the trick of allowing a variable margin size, adds a red border where the bleed begins, and automatically adjusts the footer graphic for PHB 5e and the page padding.
To print the PDF, I believe you have to use the system print dialog rather than Chrome's. And use a Custom Size Document, and set the size equal to your page height and width size + 2*margins.
Perhaps a better way to do this exists with JS or something, but this is what I've got.
The text was updated successfully, but these errors were encountered: