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

[Bug 13169] WF2: Allow placeholder on date/time fields for legacy browsers

From: <bugzilla@jessica.w3.org>
Date: Thu, 07 Jul 2011 17:20:22 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QesFS-0006rt-0A@jessica.w3.org>

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |Simetrical+w3cbug@gmail.com
           Platform|Other                       |All
            Summary|Why aren't placeholders     |WF2: Allow placeholder on
                   |available on Date/Time      |date/time fields for legacy
                   |fields? It seems to me they |browsers
                   |should.                     |
         OS/Version|other                       |All
           Severity|normal                      |enhancement

--- Comment #2 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-07 17:20:21 UTC ---
Related to bug 12868.  Bug 12781 comment 1 is relevant.  The question is, are
there going to be a significant number of browsers around that support
placeholder but not date/time inputs?  If we expect that all such browsers will
be gone within a year or two, it doesn't seem worth allowing this.  On the
other hand, it's harmless in browsers that do support the type.

I think it makes sense to allow attributes like maxlength and placeholder on
all the new input types for now, and say that browsers must ignore them if they
actually support the type.  It would be fallback content for legacy browsers,
like the contents of <video> or whatever.  In a few years we can revisit and
make them obsolete, once there's no reason to use them anymore.

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 Thursday, 7 July 2011 17:20:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:55 UTC