[css3-regions] Avoid Markup Clutter from Christoph Pï¿½per on 2011-12-20 (www-style@w3.org from December 2011)

From: Christoph Pï¿½per <christoph.paeper@crissov.de>
Date: Tue, 20 Dec 2011 16:53:13 +0100
To: W3C Style <www-style@w3.org>
Message-Id: <B9565AAD-4E3E-4C80-AA22-BBEC12FF9F2A@crissov.de>

| The CSS regions module is independent of the layout of regions
| and the mechanism used to create them.

This module absolutetly should specify a means to generate stylable regions without additional markup. Whether it is an at-rule or a pseudo-element is debatable. I prefer ï¿½@regionï¿½, though.

Then, ï¿½@regionï¿½ like other at-rules, should be followed by an (optional) identifier / name, not an selector. Instead of an approach like ï¿½@mediaï¿½ with nested rulesets, the region name should be part of the selector inside a pseudo-class:

  @region foo {position: absolute; ï¿½}
  p                {color: red; ï¿½}
  p:in-region      {color: orange; ï¿½}
  p:in-region(foo) {color: green; ï¿½}

| However, for simplicity, our example uses elements as regions ï¿½

That would be setting a bad example. Regions should come from the box tree, not from the node tree.

Received on Tuesday, 20 December 2011 15:53:46 UTC