We're looking for a user researcher to understand the needs of developers and designers. Is this you or someone you know? Check out the post: https://mzl.la/2IGzdXS

CSS Reference

Notes and Updates

  • Fixed up CSS Template and existing examples at Nickolay's suggestion. -- dria 15:33, 17 October 2005 (PDT)
    • The link tags are not closed. --Nickolay 04:57, 21 October 2005 (PDT)


  • Should there be example pages (such as this one) for everything (for instance, this)? --Rappo 15:20, 18 March 2006 (PST)
    • I think that we can use a single page to demonstrate several related properties at once. --Nickolay 15:56, 18 March 2006 (PST)
      • Agreed. -- dria 17:01, 18 March 2006 (PST)


I suggest that we start using categories for articles that need to be worked on. The template has 8 sections, and we should have categories indicating that a particular section needs to be filled in. E.g. Category:CSS Reference:Needs Summary, Needs Syntax, Needs Compatibility, etc. We could reuse the Category:NeedsExample for missing examples and not create categories for the sections that can be trivially filled in, such as Specification, or not necessary, such as See also.

If we did it, I could for example create a CSS:cursor page to list the known standard and non-standard values without also having to write the whole page. The categories system would ensure that the page would not be forgotten. --Nickolay 04:57, 21 October 2005 (PDT)

  • Wow, I totally missed this comment when it was made, sorry. This seems like a perfectly reasonable idea. -- dria 17:03, 18 March 2006 (PST)

Browser Compatibility

Having looked at the CSS pages already created I believe that the Table looks much better and is probably more useful. A standardised list of browsers could then be created in the template. Any extra browsers could be added to specific entries if desired (e.g. screen readers included for aural specific styles). -- Qazzian 04:47, 11 September 2006 (PDT)

CSS level information

I think the info in this reference would be more useful if another metadata field were provided in the template, perhaps called "Specified in: ". Possible values would include "CSS 1", "CSS 2.1" and "CSS 3". Also, it would be good to indicate where a property has differed between specifications. --Mozcerize 10:20, 30 November 2006 (PST)

Broken Columns

I can't seem to edit this page without breaking columns. :not is a pseudo-class, not a selector and I've created a page called "general sibling selectors" to match the rest of the selectors; the page currently links to "general sibling combinator". Miken32 09 September 2008

Removed properties dropped from CSS 2.1

I removed aural properties for now: unimplemented und no normative part of CSS 2.1. There is a CSS3 Draft with different property names. Jürgen Jeka 2009-04-06

Removed page, unimplemented an dropped from CSS 2.1. User:Jürgen Jeka 2009-04-10

CSS documentation? 

This is probably not the right place to ask this question, so please excuse me in advance. but there used to be a set of selectors

#__firefox-findbar-search-id, .__mozilla-findbar-search

that allowed you to customize search results. This is no longer working in FF 3.5. Is there a reference I could use to get this working again?

Missing pages

There seem to be no reference pages for

User:jmabel 2010-10-27

Document Tags and Contributors

Last updated by: jmabel,