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

CSS3

by ryboe ST3 Top 100

The most complete CSS support for Sublime Text

Labels language syntax, completions, auto-complete, reset, linting

Details

Installs

  • Total 502K
  • Win 364K
  • Mac 78K
  • Linux 60K
Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23 Oct 22 Oct 21 Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7
Windows 4 5 6 13 3 8 14 0 0 11 10 10 13 10 14 16 18 20 11 14 8 8 10 8 11 7 19 14 15 15 18 18 8 12 12 16 22 11 14 12 8 15 12 22 11 16
Mac 0 2 0 3 2 3 2 0 0 5 2 4 0 4 8 2 5 4 0 0 3 2 2 2 1 1 2 4 4 0 2 1 2 1 1 5 2 1 1 2 2 3 0 1 1 3
Linux 0 0 4 0 2 4 0 0 0 1 4 2 1 6 4 1 1 2 4 1 1 7 4 1 3 4 0 2 6 3 2 5 1 2 4 3 6 2 1 2 1 4 4 6 2 2

Readme

Source
raw.​githubusercontent.​com

CSS3

GitHub Actions Status Badge

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

  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

    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 for CSS only by adding this line to your Emmet package settings. “json "abbreviation_preview”: “markup”

    6. 

  6. (Recommended) Set CSS3 as the default language for .css files
    


      

    • Open a .css file.
      • 

    • View → Syntax → Open all with current extension as… → CSS3
      • 

    


    7. 




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!