I'd like to @import some fonts, but Checkvist's custom CSS is loaded inside @media screen.

I'd like to @import some fonts, but Checkvist's custom CSS is loaded inside @media screen. @import rules must precede all other types of rules (with a few exceptions), hence cannot be used.

Would be great if there was a way to use @import with Checkvist's custom CSS option.

Comments

  1. Hello Ralf Hauber, it is a bit tricky, as we separate custom CSS by screen and print ones using @media. So far no good idea how to implement this without breaking styles used by other people.

    By the way, what kind of font you'd like to import?

    ReplyDelete
  2. Kirill Maximov The @import rules would have to be pulled out and emitted at the top of the CSS when you generate it. Alternatively, there could be a third input field for @import rules.

    On the client side, I'm using Tampermonkey, Stylus, etc., but it would be much better if Checkvist had what is needed to use fonts.

    Which font? No particular. Recently it was mr-eaves-xl-modern, but just by accident. For my fun, I like to try out fonts. Usually from Typekit (now Adobe Fonts), typography.com, and a few other foundries. Professionally, we have a corporate font (that is licensed per page view and must follow specific rules when included on web pages), and a different font for our newspaper.

    ReplyDelete
  3. Ralf Hauber Thanks a lot for the detailed explanation, impressive. I'm not so eager for new fonts :)

    I like the idea for extracting @import rules, will try to implement it so you could use it directly, without browser extensions.

    Best,

    ReplyDelete

Post a Comment

Popular posts from this blog

Hello friends

I'm really enjoy using checkvist, you are adding great features very quickly.

I seem to have found a serious issue.