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 04:18:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RDTnW-0000Zy-8U@jessica.w3.org>

--- Comment #6 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-10-11 04:18:33 UTC ---
(In reply to comment #5)
> Why do people think this has anything to do with reimplementing forms with
> canvas?
> The issue here is that sometimes a canvas will be unavailable or unusable, and
> in that case, why would you want to forbid a form asking for an email address
> or selecting from a list?

A canvas can't be "unavailable".  When a canvas is unusable, the fallback
content is meant to represent the same thing as the canvas.  How is a text
input in the fallback supposed to represent anything on the canvas other than a
canvas-implemented text input?

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 04:18:37 UTC

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