Suppress confusable theme import when tweaking #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR suppresses the confusable theme import when tweaking by
<style>
element andstyle
global directive.v0.0.6 could import another theme in tweaking style. However, the imported rule by
@import
would give confusion about the order of CSS rules because it is rolled-up to the beginning of packed style.The user would expect to see "Hello" by
font-size: 2em
. But actually, styles would apply1em
. This is because styles are ordered by "Imported theme in inline style
➡️Slide theme
➡️Inline style
" under the influence of a roll-up plugin.To prevent a confusable behavior, we have decided to suppress importing another theme in inline styles at this moment.
@import
and@import-theme
feature are overlapped in effect withtheme
directive.Of course you can still use
@import
without importing another theme.