ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

CSS3

by y0ssar1an ST3 Top 100

The most complete CSS support for Sublime Text 3

Details

Installs

  • Total 188K
  • Win 120K
  • OS X 40K
  • Linux 28K
Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8
Windows 157 247 228 248 250 310 174 194 208 271 277 257 273 171 201 202 251 211 278 261 143 196 202 239 243 252 225 156 150 188 256 209 254 254 137 167 205 191 241 245 228 125 125 177 227 243
OS X 24 64 63 56 48 61 34 38 51 65 47 49 60 29 37 40 58 75 49 61 37 41 46 62 57 51 44 52 35 41 46 54 54 52 29 30 45 54 58 57 52 28 35 42 64 53
Linux 21 45 50 49 39 46 32 29 41 47 40 46 32 30 42 35 38 33 31 35 33 21 33 53 36 40 40 38 36 42 48 46 39 49 35 33 34 40 43 44 46 32 31 33 40 32

Readme

Source
raw.​githubusercontent.​com

CSS3

Join the chat at https://gitter.im/y0ssar1an/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
    • @apply
    • 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

before and after

Installation

  1. Install Package Control
  2. Install CSS3

    Platform Install Command
    Mac cmd+shift+p   → Package Control: Install Package → CSS3
    Linux/Windows ctrl+shift+p → Package Control: Install Package → CSS3
  3. (Required) Disable the default CSS package

    Platform Disable Command
    Mac cmd+shift+p   → Package Control: Disable Package → CSS
    Linux/Windows ctrl+shift+p → Package Control: Disable Package → CSS

    disabling the default CSS package

    Make sure you don't have any open files set to the default CSS syntax (bottom-right) or you may get an error message.

  4. (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,
    
  5. (Recommended) Disable CSS completions in Emmet

    If you have Emmet installed, its completions will drown out the carefully researched, standards-based completions offered by this package. You can disable Emmet completions by adding these two lines to your Emmet Package settings.

    "show_css_completions": false,
    "disable_tab_abbreviations_for_scopes": "source.css"
    
  6. (Recommended) Set CSS3 as the default language for .css files

    • Open a .css file.
    • View → Syntax → Open all with current extension as… → CSS3

    setting CSS3 as default

Best Practices

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!