- From: Håkon Wium Lie <howcome@opera.com>
- Date: Mon, 9 Jan 2012 20:49:19 +0100
- To: Vincent Hardy <vhardy@adobe.com>
- Cc: Alan Stearns <stearns@adobe.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, fantasai <fantasai.lists@inkedblade.net>, www-style@w3.org
Also sprach Vincent Hardy:
> The issue of making something a region is the only part the specification
> addresses. The regions specification *does not* require the use of markup.
> It is agnostic. For example, Alan has done examples where regions are
> created on ::before and ::after pseudo-elements. Not necessarily what we'd
> like people to do either, but my point is that regions *do not* require
> elements and they do not inherently cause markup clutter. Regions only
> require a selector for the box it will turn into a region.
I believe that all specifications should include simple code examples.
These code examples should illustrate how the described functionality
is expected to be used. This is also important when evaluating the
proposal. So, while I think it's ok to say that a property may apply to
other things that elements (like, e.g., 'size' does), the draft must
give examples of how you expect it to be used.
If you don't foresee the properties described in css3-regions to be
used with elements, say so. And if you do expect them to, give
examples of good use.
> >>Officially, I'm fine with leaving Regions alone for now, with the
> >>understanding that we'll solve the problem in the near future with
> >>some mechanism for generating arbitrary pseudo-elements.
>
> For the specification example, I think it is ok to propose simple
> examples, and note that the expected best practice is to use generated
> pseudo-elements when that becomes available.
I don't think it's a good idea to progress css3-regions without
knowing how to use them.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Monday, 9 January 2012 19:51:31 UTC