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
In case the user add the custom stylesheet into the extension, and this stylesheet has the same name as one of built-in stylesheets, the styles will be ignored.
Step-by-step:
Create asciidoctor.css file with single line: p {color: red;}.
Add it to the extension.
Note, that it is now visible in the Custom section, and you can select it.
However, your documents will use the stylesheet of the same name from the Default section.
So, simply saying you cannot use asciidoctor.css as a file for your custom stylesheet. Something like asciidoctor_custom.css will work,
Tested with Chrome.
The text was updated successfully, but these errors were encountered:
I don't know if it's a good idea to use the same name as one of the built-in stylesheets.
The reason is that I'm using the stylesheet attribute to resolve the stylesheet.
So, if you want to use the built-in stylesheet "riak" in one of your document, you can use:
= Document:stylesheet: riak.css
But now the browser extension will use the overridden riak stylesheet instead of the default riak stylesheet.
Should we add an error message when you want to add a custom stylesheet with the same name? Should we automatically prefix the stylesheet with "custom_" (if the name conflicts with a built-in stylesheets)? Should we allow to override a built-in stylesheet?
In case the user add the custom stylesheet into the extension, and this stylesheet has the same name as one of built-in stylesheets, the styles will be ignored.
Step-by-step:
p {color: red;}
.However, your documents will use the stylesheet of the same name from the Default section.
So, simply saying you cannot use asciidoctor.css as a file for your custom stylesheet. Something like asciidoctor_custom.css will work,
Tested with Chrome.
The text was updated successfully, but these errors were encountered: