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 216K
  • Win 140K
  • OS X 45K
  • Linux 31K
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 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12
Windows 60 200 217 248 121 163 203 202 223 234 210 138 154 200 213 233 219 215 138 152 211 222 205 244 270 138 138 194 181 200 188 211 127 155 198 233 216 210 228 116 134 193 269 212 233 210
OS X 5 40 53 56 26 29 50 54 52 45 37 28 36 50 49 41 48 54 24 32 39 48 59 42 46 26 31 37 47 58 49 51 30 37 56 50 64 61 44 24 35 46 42 61 64 34
Linux 11 39 43 43 30 26 50 28 44 36 35 26 29 20 28 43 40 28 28 19 35 37 40 37 40 30 24 34 28 26 37 41 23 33 40 38 47 40 19 35 26 35 22 41 36 40

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
    • 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

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) 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

  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!