Add support for SASS

[ikbenben]

from @asenseofdesign: This is an exciting extension. However, it would be even greater if it was compatible with SASS. Is it in your plans? :-)

[ikbenben]

we will need to investigate this.

the way the extension gets the css rules is different with how the default css inline editor gets the rules. this extension queries the html dom using the getMatchedCSSRules() method while the default css inline editor simply scans the CSS/SASS/LESS files in the project filesystem. The latter approach will result in matches that may not be actual matches. I'm guessing the brackets used this approach in order to support SASS and LESS.

in order to implement this, we will need to change the way the extension gets the CSS rules for a particular dom element

[unknownterritory]

Thank you, ikbenben, for referencing this issue here. In a project that uses SASS or LESS, the rules in those preprocessors files are the ones that actually reflect the the intention of the developer at that point in time, so not matching the actual css rules is not a problem as these are just a later sub-product. Also, when someone makes the choice of using a preprocessor, that choice is usually something that doesn't change throughout the duration of the whole project... So, what about inserting this in some sort of settings or preferences for the extension? That way the parsing could be redirected accordingly... if this makes sense at all to you.