- From: Håkon Wium Lie <howcome@opera.com>
- Date: Wed, 1 Oct 2014 23:05:08 +0200
- To: Liam R E Quin <liam@w3.org>
- Cc: Alan Stearns <stearns@adobe.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "www-style\@w3.org" <www-style@w3.org>
Also sprach Liam R E Quin: > > I think that once we establish a good use case for reaching out to an > > ancestor’s grid, then we can introduce root/page and/or named grids. Until > > then, I’d rather keep things simple. I expect the vast majority of > > documents will establish only one grid. If actual usage shows something > > different, we can solve the use case when it comes up. > > How about a publication with two columns of text, e.g. main body > and sidebar on the outer edge of each page, where the sidebar has > smaller type...? Yes, this is a common case. So, your markup would be something like: <article> ... <aside>...</aside> ... <aside>...</aside> ... </article> Setting a baseline grid on the 'article' element is a solution for the main column, but setting it on 'aside' would lead to each <aside> element having its own baseline grid. This is another situation where the 'root' keyword would be handy, one could simply do: article { baseline-grid: new } aside { baseline-grid: root } Cheers, -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcome
Received on Wednesday, 1 October 2014 21:05:33 UTC