W3C home > Mailing lists > Public > public-canvas-api@w3.org > October to December 2011

Re: Request to re-open issue 131 -USE CASES, USE CASES, USE CASES

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 20 Dec 2011 02:10:02 -0800
Message-ID: <CA+c2ei9-0XsrSCxW8MfFCnR6eFS4pMhZK2UOJ-99rK_xHT4-PA@mail.gmail.com>
To: Charles Pritchard <chuck@jumis.com>
Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Frank Olivier <Frank.Olivier@microsoft.com>, Cynthia Shelly <cyns@microsoft.com>, david bolter <david.bolter@gmail.com>, "dbolter@mozilla.com" <dbolter@mozilla.com>, Steve Faulkner <faulkner.steve@gmail.com>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-html@w3.org" <public-html@w3.org>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, Sam Ruby <rubys@intertwingly.net>
On Mon, Dec 19, 2011 at 11:53 AM, Charles Pritchard <chuck@jumis.com> wrote:

> **
> Silly enough, one of the most frustrating technical problems with
> launching an <input> is alignment.
> Even with a full CSS reset and strict font detection, we still had issues
> with margin/padding of the native control.
> Text decoration is another issue, though it's substantially improved over
> the last two years.
> The pdf.js demonstrates small alignment quirks. They'd have better
> selection support if they coded it into Canvas; but it works well enough
> without, and the oncopy/onpaste patches in FF are still under review.

Sounds like this should be a priority for accessibility to track then?

I'd much rather spend time on fixing this than spend time on creating APIs
specifically for enabling text editors in canvas.

/ Jonas
Received on Tuesday, 20 December 2011 10:14:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:54 UTC