CSS specificity calculator for Sublime Text 2
- Total 4K
- Win 2K
- Mac 1K
- Linux 476
|Aug 5||Aug 4||Aug 3||Aug 2||Aug 1||Jul 31||Jul 30||Jul 29||Jul 28||Jul 27||Jul 26||Jul 25||Jul 24||Jul 23||Jul 22||Jul 21||Jul 20||Jul 19||Jul 18||Jul 17||Jul 16||Jul 15||Jul 14||Jul 13||Jul 12||Jul 11||Jul 10||Jul 9||Jul 8||Jul 7||Jul 6||Jul 5||Jul 4||Jul 3||Jul 2||Jul 1||Jun 30||Jun 29||Jun 28||Jun 27||Jun 26||Jun 25||Jun 24||Jun 23||Jun 22|
Use Package Control to install “sublime-csspecific”.
Alternate instructions (not recommended): Clone the repository into your Sublime Text packages folder:
git clone https://github.com/spadgos/sublime-csspecific CSSpecific
Don't forget to watch for updates!
Open a file containing CSS (this can include HTML files!), and then activate CSSpecific by hitting the hotkey (default:
Alt+Ctrl+Shift+C), or using the Command Palette.
If you have nothing selected, then all CSS selectors in the file will be evaluated. If you have one or more non-empty selections, then only the selectors which intersect with your selections will be shown.
Actual CSS specificity is not calculated as a single number. For simplicity, the real values are converted to a single number (basically, id = 100, class = 10, tag = 1), which is fine in most circumstances, but will break if you have more than 10 classes or tags referenced in a single selector. If this is the case for you, you have bigger problems to deal with first.
If you find a bug in the calculations, send me a pull request or report an issue in the tracker. Feature requests welcome, too.