CSS3
The most complete CSS support for Sublime Text
Details
Installs
- Total 505K
- Win 366K
- Mac 79K
- Linux 60K
| Jun 6 | Jun 5 | Jun 4 | Jun 3 | Jun 2 | Jun 1 | May 31 | May 30 | May 29 | May 28 | May 27 | May 26 | May 25 | May 24 | May 23 | May 22 | May 21 | May 20 | May 19 | May 18 | May 17 | May 16 | May 15 | May 14 | May 13 | May 12 | May 11 | May 10 | May 9 | May 8 | May 7 | May 6 | May 5 | May 4 | May 3 | May 2 | May 1 | Apr 30 | Apr 29 | Apr 28 | Apr 27 | Apr 26 | Apr 25 | Apr 24 | Apr 23 | Apr 22 | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Windows | 5 | 18 | 7 | 11 | 5 | 6 | 7 | 11 | 5 | 13 | 7 | 12 | 6 | 7 | 11 | 9 | 11 | 6 | 18 | 6 | 11 | 14 | 21 | 33 | 10 | 9 | 4 | 12 | 4 | 8 | 4 | 13 | 10 | 7 | 12 | 11 | 9 | 9 | 8 | 5 | 9 | 23 | 16 | 5 | 11 | 9 |
| Mac | 0 | 1 | 3 | 0 | 4 | 1 | 1 | 1 | 4 | 1 | 5 | 4 | 0 | 0 | 1 | 4 | 2 | 2 | 4 | 2 | 5 | 2 | 7 | 5 | 6 | 2 | 3 | 1 | 0 | 3 | 4 | 0 | 3 | 1 | 1 | 3 | 4 | 1 | 3 | 3 | 2 | 1 | 1 | 7 | 3 | 2 |
| Linux | 1 | 2 | 3 | 0 | 1 | 1 | 1 | 2 | 2 | 1 | 0 | 1 | 0 | 1 | 2 | 0 | 1 | 2 | 2 | 3 | 1 | 4 | 2 | 1 | 2 | 5 | 0 | 4 | 1 | 3 | 1 | 3 | 3 | 1 | 4 | 2 | 0 | 3 | 3 | 3 | 0 | 3 | 1 | 1 | 1 | 1 |
Readme
- Source
- raw.githubusercontent.com
CSS3
The most complete CSS and PostCSS-cssnext support for Sublime Text.
Features
- Absurdly Complete: I mined the entire set of draft specs and supported everything. Some of this stuff won't be implemented in browsers for years. If it's in the spec, it's supported.
- Future Proof: PostCSS-cssnext is fully supported. If
you use cssnext, you can use futuristic CSS like…
- nesting
- custom selectors
- custom properties
- custom media queries
- CSS Modules
- lots more
- Productive: Offers a full set of completions for properties, descriptors, @-rules, functions, and selectors. The completions are highly specific to what you're writing.
- Modern: Bad, old CSS is flagged. Unnecessarily prefixed properties aren't highlighted. Catches lots of mistakes. Encourages best practices.
- Faithful: Follows the W3C specs extremely closely.
- Fast: CSS3 has been designed for Sublime's new custom regex engine, which is crazy fast. The syntax highlighting typically takes less than 100ms, even for very large CSS files.
Before & After
Installation
- Install Package Control
Install CSS3
Platform Install Command Mac cmd+shift+p→ Package Control: Install Package → CSS3Linux/Windows ctrl+shift+p→ Package Control: Install Package → CSS3(Required) Disable the default CSS package
Platform Disable Command Mac cmd+shift+p→ Package Control: Disable Package → CSSLinux/Windows ctrl+shift+p→ Package Control: Disable Package → CSSMake sure you don't have any open files set to the default CSS syntax (bottom-right) or you may get an error message.
(Strongly Recommended) Enable completions inside completions
By default, Sublime will not offer completions inside completions. In other words, the completions menu is suppressed when you're tabbing through a snippet. This prevents a lot of CSS3 completions from appearing. Add these keys to your User Settings to fix this:
"auto_complete_commit_on_tab": true, "auto_complete_with_fields": true,
(Recommended) Hide CSS completions from Emmet
If you have Emmet installed, its completions will drown out the carefully researched, standards-based completions offered by this package. You can hide Emmet completions for CSS only by adding this line to your Emmet package settings. “json "abbreviation_preview”: “markup”
(Recommended) Set CSS3 as the default language for
.cssfiles- Open a
.cssfile. - View → Syntax → Open all with current extension as… → CSS3
- Open a
Best Practices
- Always use quotes inside
url(). Unquoted URLs are intentionally not highlighted.
Help Me Out!
If you think something's missing, make sure you're not asking for something on this list of bad CSS properties. If it's not on that list, open an issue and I'll investigate. Definitely check out the CONTRIBUTING guidelines before submitting your PR. It could save you a lot of time. I'll be monitoring the specs as they're updated on this W3C feed, but I still need your help. Let's keep bad code out of the Web!