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
When opening https://clerk.vision/ in Chrome (didn't try it in other browsers), we have some FOUT happening as the font loading takes some time.
One way of trying to solve this (which I've tested locally and it worked for Chrome at least) would be to add fonts to the head of the page at nextjournal.clerk.view/->html (and also for the static app). We could pass options through the call to main or some other function that keeps an atom with the options we want to be used, let me know what you think o/
The text was updated successfully, but these errors were encountered:
This would indeed be handy. Sketched a PoC in 7219298.
I think we'd want to support both a global and a per-notebook setting. What's a bit annoying is that the head isn't rendered by react so folks would need to reload the page to make this work but maybe that's fine as a start?
This would indeed be handy. Sketched a PoC in 7219298.
I think we'd want to support both a global and a per-notebook setting. What's a bit annoying is that the head isn't rendered by react so folks would need to reload the page to make this work but maybe that's fine as a start?
I've tried the above here which works perfectly with the caveat that the styles are injected twice (the ID is only there so I could quickly verify this issue)
When opening https://clerk.vision/ in Chrome (didn't try it in other browsers), we have some FOUT happening as the font loading takes some time.
One way of trying to solve this (which I've tested locally and it worked for Chrome at least) would be to add fonts to the head of the page at
nextjournal.clerk.view/->html
(and also for the static app). We could pass options through the call tomain
or some other function that keeps an atom with the options we want to be used, let me know what you think o/The text was updated successfully, but these errors were encountered: