W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2012

Re: [whatwg] input type=barcode?

From: Tobie Langel <tobie.langel@gmail.com>
Date: Fri, 7 Sep 2012 15:15:19 +0200
Message-ID: <CAMK=o4fc8MigExgyVDMUvNAwqF4f5EBzY1Td=SkYCM9U19=H2g@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: WHATWG <whatwg@whatwg.org>
On Fri, Sep 7, 2012 at 6:35 AM, Ian Hickson <ian@hixie.ch> wrote:
> On Thu, 30 Aug 2012, Jonas Sicking wrote:
>>
>> I think while in theory we could rely on UAs to enable barcode entry
>> anywhere, which definitely would provide the maximum capabilities for
>> the user. In practice it seems hard to create UI which enables that
>> while at the same time isn't annoyingly shoving a barcode button in your
>> face which you generally is not interested in using.
>
> Agreed. I think a UA that wanted to support this would want to know which
> attributes to provide the feature for.
>
> In this respect it's similar to the WebKit-proprietary x-webkit-speech
> attribute on <input>. In fact, this suggests that if other browsers are
> interested in supporting speech input, maybe we should standardise it as
> an inputmode value, e.g. inputmode="speech". Possible the inputmode=""
> attribute in that case could be switched to a list of tokens, so you could
> in fact do inputmode="latin-prose speech" or inputmode="numeric barcode"
> in order to provide the user agent with more flexibility in the UI.

There seems to be some overlap, at least in semantics, with the
capture attribute described in HTML Media Capture[1] and recently
filed for inclusion in the Living Standard HTML spec[2].

Anyway these two concepts can be reconciled or their distinction clarified?

--tobie

---
[1]: http://dev.w3.org/2009/dap/camera/
[2]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17879
Received on Friday, 7 September 2012 13:15:50 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:45 UTC