19:14:29 <InstNEON001> If seamonkey is based off a relatively recent version of mozilla firefox, why doesn't CSS "break-after: page" work with print preview for PDF?
20:13:21 <njsg> InstNEON001: pondering if it's "based off a relatively recent version of mozilla firefox" is not the best way to look at it, it's more like: the "based off" firefox version is at an earlier point, and a lot of changes from firefox have been added on top of that, for features and also the security fixes from Firefox and Thunderbird
20:14:35 <njsg> InstNEON001: short answer is probably "it wasn't added (backported) yet", this reminds me of a help documentation style change that lacked something to fully apply, I wonder if it's the same thing
20:19:16 <InstNEON001> Can I have CSS automatically applied when I type a certain character?
20:19:22 <InstNEON001> In compositor.
20:21:53 <InstNEON001> Because changing settings to use css styles instead of html attributes doesn't work. Or at least doesn't seem to work.
20:28:03 <njsg> re: the break: It's possibly related to what I was thinking about, which is https://bugzilla.mozilla.org/show_bug.cgi?id=171549
20:28:27 <njsg> InstNEON001: so a quick test here shows "page-break-after:always" works, but "break-after: page" doesn't, is this what's happening there?
20:28:38 <njsg> then I'd guess bug 775618
20:32:07 <njsg> InstNEON001: "when [you] type a certain character?", as a sort of macro? something else?
20:32:18 <njsg> (sorry, I'm not sure I understand what you meant by that)