After finding this thread: https://bootstrapstudio.io/forums/topic/warning-or-toggle-for-inline-css/
I can see a response from the developer, about specificity and stylesheets being an issue. The issue goes both ways - that's why I think it's best the user has an option to set default behaviour.
STYLESHEET ISSUE
I propose the CSS could be made in its own stylesheet called 'panel' or something similar, and if it doesn't exist, BSS creates the stylesheet. Remember, if the user would prefer in-line, they can choose to default to in-line and not have an extra stylesheet.
SPECIFICITY ISSUE
Personally, specificity when using the panel options is not a big deal for me, as I know if the changes I make in the panel don't work, I can just add a line of specific CSS, no in-line styles and still probably won't need to use !important.
Surely BSS could write the CSS with high specificity by looking at the parent classes / IDs. BSS could probably even detect when a rule just added was overridden and could prompt the user - to add classes / IDs, to add as inline or to use !important. These are just ideas.
In addition, if the option doesn't do anything due to not enough specificity, there could be a tick box next to each option or (ctrl+click) to add it as in-line instead. For me, that would be a last resort - probably after using !important, however it would be super handy when temporarily testing out provisional changes.
So, to recap:
- No digging through hundreds of lines of codes to edit in-line styles later. (I hate in-line styles, can you tell?)
- Less likely to have to use !important to override styles - it's easier to override stylesheets than in-line.
- If edits made in the panel don't work, there are still options to work with.
- If people prefer in-line, there could still be the option (in project settings, or in a preferences pane) for users to have it stay in-line by default, exactly how it is now.
I hope it's considered!
Thanks for such a great tool
Tom