W3C home > Mailing lists > Public > www-style@w3.org > April 2012

Re: [css3-fonts] Addition of font-size: xxx-large

From: Ryosuke Niwa <rniwa@webkit.org>
Date: Wed, 18 Apr 2012 01:18:03 -0700
Message-ID: <CABNRm621-5N-NqTFwvGGz9eP4hrWF=7qtJmkuRAJPZ2nD5UBbA@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: Aryeh Gregor <ayg@aryeh.name>, WWW Style <www-style@w3.org>, Ehsan Akhgari <ehsan@mozilla.com>, "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>
On Wed, Apr 18, 2012 at 1:07 AM, John Daggett <jdaggett@mozilla.com> wrote:

> Aryeh Gregor wrote:
> > Background: the idea is that document.execCommand("fontsize", false,
> > "foo") is what authors call when the user selects some text and picks
> > a size of "foo" from a drop-down.  Currently, the API supports only
> > values of 1 to 7.
>
> Right, and that's precisely where the problem lies, *not* in CSS!
>
> > Most real-world WYSIWYG editors use execCommand() sparingly if at all
> > because of lack of interop, but there are enough existing users of
> > execCommand() that we can't break them.
>
> I don't think more sensible values for fontSize will break anything here.
> Let the old, not very interoperable behavior remain, and define a new
> behavior that's a better match for CSS and more likely to be interoperable.
>

That won't work well with queryCommandValue('fontSize') which returns
values between 1 and 7.

- Ryosuke
Received on Wednesday, 18 April 2012 08:18:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:52 GMT