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
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Currently you can only show the CSS styles inline in the HTML files if there are styles associated with it. You should be able to click any tag and if there are no relevant styles it should allow you to add some right then and there instead of doing nothing.
The text was updated successfully, but these errors were encountered:
A good idea, but one of the grey areas is "what file do you add the styles in?" - it would be easy if everyone used a stylesheet for every corresponding html file, but of course that's not the case, and adding style elements in your markup doesn't really make for the most maintainable of code.
You can do stuff like this in Blend, right clicking a tag, id or class and adding a CSS Rule, but Blend is a visually cluttered tool, and it dictates where the code goes - usually in your html, because guessing a stylesheet is too unpredictable.
The only ideal option is to link stylesheets and HTML files together, but brackets is a code editor, not an IDE, and it wouldn't really be right to dictate someone's project layout/ coding style.
Buuut... If perhaps you right-clicked the tag/id/class/etc and maybe had to select an appropriate file in your working set, maybe then you could add styles to your elements without interruption. The next grey area to think about is whether you fill in that style like you would in typical inline editing, or get taken to the .css file in question in the main view...
Currently you can only show the CSS styles inline in the HTML files if there are styles associated with it. You should be able to click any tag and if there are no relevant styles it should allow you to add some right then and there instead of doing nothing.
The text was updated successfully, but these errors were encountered: