Below is a proposal to remove the "experimental" IME API implementation from Blink.

Is there sufficient interest from other implementers to keep this spec on the TR track or should we formally stop work on it and publish a WG Note?

Travis, All, WDYT?

-Thanks, ArtB

-------- Forwarded Message --------
Subject:        [blink-dev] Removing IME API code from Blink
Date:   Wed, 27 May 2015 14:15:15 +0900
From:   Takayoshi Kochi <ko...@chromium.org>
To:     blink-dev <blink-...@chromium.org>



IME API, experimentally implemented a while ago, has been under experimental flag
but we haven't got enough signal from users to get it out of experimental.
Therefore I'm thinking of removing the code from Blink (and Chromium) for code health. This is not an intent to deprecate, and if we get enough interest we may readd/reimplement
the spec.

We don't have real-world usage number of IME API. Even though IE11 implements IME API, theirs are ms- prefixed (while Blink's is unprefixed) and some of their API are available under Metro mode only due to their implementation details, so we guess the number of
people who depend on the existence of the API is quite small.

Any objections?

spec: http://www.w3.org/TR/ime-api/
bug: crbug.com/226938 <http://crbug.com/226938>
chromestatus: https://www.chromestatus.com/features/6366722080636928
Intent to implement: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/sxuEbPN6pPY/QpNxXgJyoScJ <https://groups.google.com/a/chromium.org/forum/#%21msg/blink-dev/sxuEbPN6pPY/QpNxXgJyoScJ>
caniuse: http://caniuse.com/#cats=JS%20API
--
Takayoshi Kochi
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org <mailto:blink-dev+unsubscr...@chromium.org>.



Reply via email to