W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2011

[Bug 14419] when canvas isn't supported, or for blind users, the canvas element's content should be displayed, so excluding input types like text and select is discriminatory

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Oct 2011 00:50:48 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RDQYS-0008AN-HT@jessica.w3.org>

--- Comment #3 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-10-11 00:50:47 UTC ---
No, it doesn't disadvantage anyone, because those types of inputs should just
be handled as normal HTML.

It's practically impossible for web devs to actually implement the equivalent
to <input type=text> in canvas.  That little element has massively complicated
interactions with lots of things, and is still sometimes buggy in the details
in modern browsers which have had tens or hundreds of browser-dev-hours devoted
to working on it.

If a drawing application is implementable in text, it's almost certainly going
to be a bad experience if the text-based editor is running at the same time as
the canvas-based editor.  If it *can* be run at the same time (say, perhaps
it's just a REPL-like interface to the canvas), then it's not fallback, it's an
alternative input method that can be useful to sighted users as well.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 11 October 2011 00:50:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:05 UTC