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 360K
  • Win 248K
  • OS X 65K
  • Linux 47K
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 Jul 6 Jul 5 Jul 4
Windows 121 139 136 111 146 143 143 102 124 134 143 137 152 158 96 111 152 159 142 136 142 94 95 118 154 93 153 169 92 130 144 186 152 161 133 108 115 131 148 153 164 156 106 118 166 161
OS X 17 14 14 25 21 20 23 11 9 18 16 21 19 21 13 7 26 19 19 27 20 11 14 14 13 11 18 17 10 16 18 17 22 21 31 9 16 13 22 17 26 30 12 14 23 19
Linux 19 15 17 16 15 16 27 14 13 22 15 17 19 18 15 15 20 20 16 13 19 7 10 24 21 14 20 25 5 18 17 15 18 11 25 17 15 16 22 24 14 23 10 26 12 13

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!