CSS Working Group Wiki

Additional Pseudo-Elements

astearns — 2012-02-03T12:37:30-08:00

The ::outside pseudo-element was cut from css3-content and has not been tracked since. Other pseudo-elements concepts like wrapping a range of elements have been discussed from time to time. Additional pseudo-elements with more control over where they are positioned in the tree could help reduce markup clutter where elements are added to HTML for the sole purpose of CSS styling (Markup Clutter thread) (Thread discussing wrapping multiple elements). See also: cross-post from whatwg about anonymou…

CSS Vendor Prefixes - [cursor zoom-in zoom-out]

crissov — 2012-02-03T05:04:31-08:00

In CSS we use vendor prefixes for properties, values, @-rules that are: * vendor specific extensions (per CSS 2.1), or * experimental implementations (per CSS Snapshot 2010) (e.g. in Working Drafts) This is a collection of the latest thoughts towards policy/guidance for when to use vendor prefixes in an implementation and when it is safe/right/required to drop vendor prefixes from implementations.

Paris F2F February 2012 - [Participants]

gadams — 2012-02-02T06:24:16-08:00

Topics for the February 2012 CSS Working Group Face-to-Face meeting in Paris, France. When: Monday 6 February – Wednesday 8 Feburary Where: 23 avenue d'Italie, paris Room: TBD Registration: TBD - |survey

Region Styling

vhardy — 2012-02-02T05:00:30-08:00

Region Styling With regions, element (or pseudo-element) boxes are often broken into multiple pieces that are laid out in different regions. For example, it is possible to move an element and its generated box with width:100% to a flow and layout the flow between two regions, one of width 500px and one of width 200px. In that situation, the specified width for the element is 100% and its used value for the portion laid out in the first region is 500px and 200px for the second region.

CSS Region Templates - [4. Page view with generated pages]

alexmog — 2012-02-01T20:31:48-08:00

This is a collection of ideas spawned from discussions at TPAC2011. Not very organized yet. This may evolve into zero or more new spec modules. May overlap with existing modules too. Related: Paged View Related: Fragments, Columns, Regions, Pages Goals * Define a declarative way to generate regions or pages based on (a) amount of content in paged presentation and (b) some description of page design * Make it easy to produce a simple paginated view without script * Provide a way to gene…

Introduction - [Flowing content between arbitrary areas]

alexmog — 2012-02-01T19:46:19-08:00

Introduction This page captures use cases for CSS Regions (and exclusions). CSS Regions can be coupled with CSS Exclusions and Shapes use cases for rich layouts with non-rectangular and intruding boxes. Flowing content between arbitrary areas The following image illustrates flowing the same content across regions of different widths. As the content is resized, so are the various regions and the content simply flows between the different regions.

Specification Issues and Planning - [brainstorming]

alexmog — 2012-02-01T11:07:43-08:00

This section documents problems found in the CSS specs and working drafts. Problems documented here will be addressed by the editors, possibly after discussion in a CSS Working Group meeting, and will result in changes, corrections, clarifications, or no change.

Specs for paged view and paged layout - [Fragmentation enablers]

alexmog — 2012-02-01T01:12:36-08:00

See also: Paged View List of specifications that need to progress or be created to cover the range of known page view and page layout Note: some of the specs in this list may merge or split, in most cases it is not noted as such; main goal of this list is completeness.

Paged View - [Paged View]

alexmog — 2012-01-31T23:30:24-08:00

See also Fragments, Columns, Regions, Pages, CSS Region Templates “Paged view” or “page view” as a term relates broadly to the kind of presentation where content is laid out in discrete pages and shown to user one page at a time (or several pages at a time).

CSS Regions Page - [Issue 24: Creating a named flow from external resource]

alexmog — 2012-01-30T20:58:17-08:00

CSS Regions Page This page is used to track: * new issues that are not yet flagged in the specification * resolutions about issues that were in the specification This page started from the initial CSS Regions working draft. References: * CSS Regions working draft * CSS Regions editor draft

Test Suite Build System - [Build Requirements]

plinss — 2012-01-27T18:27:14-08:00

The CSS2.1 Test Suite's final format is generated from the XHTML 1.1 source files with a set of Python scripts. These can be found in the tools/ directory of the test suite repository. Build Requirements * Python 2.6 or 2.7 (2.6 preferred for OS X 10.6, 2.7 preferred for OS X 10.7) (note ucs4 support is required, on OSX, use 'port install python26 +ucs4' or 'port install python27 +ucs4' to install) * The Template-Python module * The lxml Python module * A patched copy of the Python htm…

Use Strings, not Numeric Constants

tabatkins — 2012-01-26T16:06:20-08:00

Use Strings, not Numeric Constants When an API needs to take or return an enumerated value, many older APIs follow the C convention and use numeric constants, stored on some interface object. Modern API practice is instead to use strings directly. See, for example, the responseType property used in XHR.

CSS Flexible Box Layout - [Issue 17]

alexmog — 2012-01-25T00:17:04-08:00

Specification Latest Working Draft: Latest Editor Draft: July 23, 2009 Working Draft: Use Cases CSS Flexible Box Layout - Use Cases

CSS3-Regions Scope - [Overset Text]

astearns — 2012-01-24T18:45:13-08:00

Generating Regions The issue of using region divs in HTML markup has been around since the initial presentation to the CSS WG (early feedback). Everyone seems to agree that there should be additional mechanisms to create stylable boxes in the render tree from CSS itself (pseudo-elements). Regions is not the only specification that could benefit from this addition to CSS.

CSS2.1 - [CSS2.1]

aprowse — 2012-01-24T14:08:39-08:00

The CSS2.1 specification is a revision of of CSS2 that corrects many errors and omissions in the CSS2 Recommendation. It has also dropped unimplemented features and introduced a handful of minor new ones. TODO: Audit issues list and make sure each issue has tests in the test suite. Then institute policy that issues cannot be marked as closed until there is a test checked in for that issue.

W3C Mercurial (hg) for Dummies - [Using Mercurial to edit a W3C spec]

plinss — 2012-01-23T14:06:21-08:00

What you need beforehand * A W3C member access username and password Installing Mercurial Windows Mac OS X You need to first install Mercurial on your system. * install XCode. It helps if you're using a fairly new OS X version (e.g. 10.6 Snow Leopard or 10.7 Lion) and XCode. XCode is available in the App Store. * install MacPorts (OSX 10.6) (OSX 10.7) (see Installing MacPorts for other installs). You do not need to install X11. If you already have MacPorts installed, be sure to upda…

Specifying Percentages that Play Nicely with calc() - Emphasized the key paragraph in the page

TabAtkins — 2012-01-23T13:28:32-08:00

The calc() function accepts any unit-ed value (a DIMENSION token), and also s. Percentages are converted into an appropriate dimension based on the context in which calc() is used, and then combined with the other values to eventually produce a single value in an appropriate unit.

Fragments, Columns, Regions, Pages - [Containers] “available now” and “proposed” were not used consistently, linked EDs and WDs instead

crissov — 2012-01-21T02:58:42-08:00

Background/overview Notes and examples in support of discussion on Regions and paged view See Paged View for use cases and proposals Layout Engine with Fragmentation Support Implementations of regions, columns and paginations will vary but in most general situation it is reasonable to assume that there is a layout engine that takes formatted content in DOM as input and fills one or more container with that content: