- From: Håkon Wium Lie <howcome@opera.com>
- Date: Wed, 26 Feb 2014 23:17:08 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
Tab Atkins Jr. wrote: > >> The line-snap property would start out just snapping the dominant baseline > >> to whatever grid has been established for the element - the closest parent > >> with 'line-grid: new' or a default grid from the root element. When and if > >> named grids were added, then we could also add a keyword to the line-snap > >> property to pick a named grid instead (perhaps 'from <ident>'?) > > > > > > I was actually pondering the same thing, with the keywords > > line-grid: match-parent | create > > :) So it seems there's agreement that we do not need named grids. That's an important simplification, one that motivated me to write up this proposal: http://books.spec.whatwg.org/#baseline-grids > > I'm happy to update the spec as such, but thoughts on naming? > > (Also, comments from other people?) > > I like "match-parent", but is it useful to allow something to opt out > of the line-grid without establishing a new one? (That is, an > explicit "none" value?) Indeed, the "none" value is part of the proposal above. It think it makes sense to try using one property for most of the baseline needs. Also, I think the "root" and "page" values are useful. "root" is a grid defined by the font/position of the root element, while "page" is a grid defined by the page area + the font of the root element. To avoid show-through in printed matter, it is important to have a baseline grid that doesn't change when page margins are change. For example, the page area on the first page of a chapter may be different from those on other pages, but we still want baselines to match. Cheers, -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcome
Received on Wednesday, 26 February 2014 22:17:44 UTC