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 passing a .theme file during creation of an HTML document, the JSON styles for "Normal" are outputed in the final CSS as definitions for code span. (with a dot class-selector after span, but no class specified):
This is a bit confusing, and this use of the class selector seems dubious (I haven't managed to find any references to similar uses).
From pandoc/skylighting source, it is clear that pandoc ignores the "Normal" token — from skylighting's HTML.hs (line 50):
-- A 'NormalTok' is not marked up at all.
So, I'd expect all reference to "Normal" in the JSON theme file to be ignored in the final CSS output.
The point I'm trying to make here is that if you edit the actual CSS, and remove the "." after "code span", then the "Normal" styles become the base style for all <span> tags in the code block — and, for example, if you give to "Normal" a background color, then all tokens which don't explicitly define a background color will inherit it from "Normal", and the same goes for other styles of "Normal".
This isn't happening because of the "classless dot" in the CSS, it seems that the browser isn't able to resolve the class-less dot to a generic class for <span> tag. But my fear is that some browsers might handle differently the dotless class.
If the original intent was to ignore the "Normal" token and styling (as this seems the case, as normal text is simply otuside spans), and use the base style definitions instead (ie: those defined outside the "text-styles" JSON container), then the "Normal" text-styles should be ignored completely (IMO).
On the other hand, if the intention was that the styles of "Normal" were to define the base styles of the <span> tag (to be inherited by all code spans) then the dot is preventing it.
The text was updated successfully, but these errors were encountered:
When passing a
.theme
file during creation of an HTML document, the JSON styles for"Normal"
are outputed in the final CSS as definitions forcode span.
(with a dot class-selector afterspan
, but no class specified):This is a bit confusing, and this use of the class selector seems dubious (I haven't managed to find any references to similar uses).
From pandoc/skylighting source, it is clear that pandoc ignores the "
Normal
" token — from skylighting'sHTML.hs
(line 50):-- A 'NormalTok' is not marked up at all.
So, I'd expect all reference to
"Normal"
in the JSON theme file to be ignored in the final CSS output.The point I'm trying to make here is that if you edit the actual CSS, and remove the "
.
" after "code span
", then the"Normal"
styles become the base style for all<span>
tags in the code block — and, for example, if you give to"Normal"
a background color, then all tokens which don't explicitly define a background color will inherit it from"Normal"
, and the same goes for other styles of"Normal"
.This isn't happening because of the "classless dot" in the CSS, it seems that the browser isn't able to resolve the class-less dot to a generic class for
<span>
tag. But my fear is that some browsers might handle differently the dotless class.If the original intent was to ignore the
"Normal"
token and styling (as this seems the case, as normal text is simply otuside spans), and use the base style definitions instead (ie: those defined outside the"text-styles"
JSON container), then the"Normal"
text-styles should be ignored completely (IMO).On the other hand, if the intention was that the styles of
"Normal"
were to define the base styles of the<span>
tag (to be inherited by all code spans) then the dot is preventing it.The text was updated successfully, but these errors were encountered: