- From: Ian Hickson <ian@hixie.ch>
- Date: Sat, 1 Aug 2009 08:16:07 +0000 (UTC)
- To: Simon Pieters <simonp@opera.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-html@w3.org" <public-html@w3.org>
On Sat, 1 Aug 2009, Simon Pieters wrote: > On Sat, 01 Aug 2009 03:13:09 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote: > > Ian Hickson wrote: > > > > So basically the behavior should be as Firefox now except: > > > > 1) Treat inherit and initial as CSS syntax errors. > > 2) Always use "font: 10px sans serif" as the parent's font, not > > just when the <canvase> is outside of a DOM tree. > > > > Right? > > ...except when using a relative unit (em, ex, %) or using a relative > keyword (smaller, larger, bolder, lighter), in which case you inherit > from the canvas element. > > I think it's weird to sometimes inherit from the canvas element and > sometimes use 10px sans-serif. If we're going to use 10px sans-serif, > could we make the relative units relative to 10px sans-serif instead of > the canvas element? The spec never uses 10px sans-serif except as the default, unless I'm mistaken. > <canvas dir> (or rather the canvas element's 'direction') affects canvas > text rendering. Maybe direction should be an attribute on the 2d context > instead for consistency with .font? I considered that, but what would you make the default? The only logical answer seems to be "use the direction property on the <canvas>", at which point all you've really done is introduced a new attribute that adds yet another layer to something that already has far too many. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 1 August 2009 08:16:43 UTC