The most complete CSS support for Sublime Text 3
- Total 302K
- Win 203K
- OS X 58K
- Linux 41K
|Aug 21||Aug 20||Aug 19||Aug 18||Aug 17||Aug 16||Aug 15||Aug 14||Aug 13||Aug 12||Aug 11||Aug 10||Aug 9||Aug 8||Aug 7||Aug 6||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|
The most complete CSS and PostCSS-cssnext support for Sublime Text.
- 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…
- 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
- Install Package Control
Platform Install Command Mac
cmd+shift+p→ Package Control: Install Package → CSS3
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 → CSS
ctrl+shift+p→ Package Control: Disable Package → CSS
Make 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 without disabling them by adding this line to your Emmet package settings. “json "show_css_completions”: false
(Recommended) Set CSS3 as the default language for
- Open a
- View → Syntax → Open all with current extension as… → CSS3
- Open a
- 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!