Intent to Deprecate: x-webkit-speech input element attribute

Tommy Widenflycht

unread,

Feb 12, 2014, 10:08:53 AM2/12/14

to blink-dev

Primary eng (and PM) emails

tom...@chromium.org, PM ser...@chromium.org

Summary

We would like to remove support for the x-webkit-speech input element attribute.

Motivation

This was a Chromium experiment with speech recognition and as such never implemented by any other browser; nor will it ever be standardized. Developers should use the new JavaScript API instead.

Usage information from UseCounter

0.1% (PrefixedSpeechAttribute)

Compatibility Risk

The worst case scenario is that input fields will be "just" input fields without any speech recognition features.

Row on feature dashboard?

No (the entry on the dashboard is for the proper JS API)

Requesting approval to remove too?

No, but we would like to remove it next quarter.

Kenneth Rohde Christiansen

unread,

Feb 12, 2014, 10:15:46 AM2/12/14

to Tommy Widenflycht, blink-dev

lgtm. The usage is pretty high, but as you said in the compatibility
risk section, the worst case scenario is that input fields will be
"just" input fields without any speech recognition features, so LGTM!

> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+...@chromium.org.

--
Kenneth Rohde Christiansen
Web Platform Architect, Intel Corporation.
Phone +45 4294 9458 ﹆﹆﹆

Jochen Eisinger

unread,

Feb 12, 2014, 11:57:17 AM2/12/14

to Tommy Widenflycht, blink-dev

I understand that the implementation has several bugs which aren't present in the new api, so lgtm to remove it

Best
Jochen

Darin Fisher

unread,

Feb 12, 2014, 12:11:31 PM2/12/14

to Jochen Eisinger, Tommy Widenflycht, blink-dev

LGTM

Alex Russell

unread,

Feb 12, 2014, 4:05:17 PM2/12/14

to Darin Fisher, Jochen Eisinger, Tommy Widenflycht, blink-dev

LGTM. Removing prefixed properties is something I feel we should take a stronger position on than standardized names. The longer they fester, the worse they get.

LGTM

Ian Hickson

unread,

Feb 14, 2014, 12:53:26 PM2/14/14

to Tommy Widenflycht, blink-dev

On Wed, 12 Feb 2014, Tommy Widenflycht wrote:
>
> We would like to remove support for the x-webkit-speech input element
> attribute.

Is there any reason we shouldn't just make all form fields support this?

--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'

PhistucK

unread,

Feb 14, 2014, 4:03:33 PM2/14/14

to Ian Hickson, Tommy Widenflycht, blink-dev

I guess the details should be discussed. There are websites that use <input> in unusual ways, monitoring keypress and such and copying the pressed key to another field and such, for example.

On Android this is probably already possible, but on the desktop it is not.

☆PhistucK

Tommy Widenflycht

unread,

Feb 18, 2014, 9:25:39 AM2/18/14

to Ian Hickson, blink-dev

As far as I understood it the standardization working group much preferred the JS API.

Ian Hickson

unread,

Feb 18, 2014, 12:37:23 PM2/18/14

to Tommy Widenflycht, blink-dev

On Tue, 18 Feb 2014, Tommy Widenflycht wrote:
> On Fri, Feb 14, 2014 at 6:53 PM, Ian Hickson <i...@hixie.ch> wrote:
> > On Wed, 12 Feb 2014, Tommy Widenflycht wrote:
> > >
> > > We would like to remove support for the x-webkit-speech input
> > > element attribute.
> >
> > Is there any reason we shouldn't just make all form fields support
> > this?
>
> As far as I understood it the standardization working group much
> preferred the JS API.

Say I (as a user) go to:

http://brailmodellerenglish.runboard.com/,pleasedo=simplesearch

Why, on desktop, can I not dictate to my browser what to put in that
search box? On mobile I can.

I don't understand what needs standardising to do this.

(This is separate from whether we want to provide a dedicated API for
this, which I agree would be useful in some cases.)

Reply all

Reply to author

Forward