W3C home > Mailing lists > Public > public-html@w3.org > November 2014

Re: A missing point in the HTML5 spec

From: Shane McCarron <shane@aptest.com>
Date: Tue, 4 Nov 2014 09:43:25 -0600
Message-ID: <CAOk_reFhB3L+u+-jKwYmKT6WhpMQmD2-HYM-E2pEKa9VcNjUJA@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: Andry Rendy <master.skywalker.88@gmail.com>, HTMLWG WG <public-html@w3.org>
FYI inputmode is from the mobile community back in the day.  It was first
introduced in XHTML 1.0 Basic I think.  And it was part of Modularization.
You can see it at
http://www.w3.org/TR/2008/REC-xhtml-basic-20080729/#s_inputmode for example.

On Tue, Nov 4, 2014 at 7:14 AM, Steve Faulkner <faulkner.steve@gmail.com>
wrote:

> Thanks Andry,
>
> bug filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=27229
>
> --
>
> Regards
>
> SteveF
> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
>
> On 4 November 2014 12:47, Andry Rendy <master.skywalker.88@gmail.com>
> wrote:
>
>> To the attention of the HTML5 specification authors and whoevere
>> interested.
>> While tracking a bug in another project (Validator.w3.org/nu) I noticed
>> that the attribute "inputmode" has been inserted in the official spec. It
>> is listed in the <input> element (a table specifies on which input states
>> it applies) and in the <textarea> element lists of allowed attributes.
>> However, differently from any other attribute in the spec, it has no prose
>> to explain what it is needed for, or what kind of attribute it is
>> (enumerated), or its possible values.
>> Now spec should state whether @inputmode is actually allowed and in what
>> states and functions, or remove it because it is quite a problem for
>> authors.
>> Thank you in advance.
>>
>
>


-- 
Shane McCarron
Managing Director, Applied Testing and Technology, Inc.
Received on Tuesday, 4 November 2014 15:43:54 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:46:11 UTC