Intent to Implement and Ship: spellcheck attribute in webview

83 views
Skip to first unread message

Miguel Garcia

unread,
Feb 3, 2016, 6:59:28 AM2/3/16
to blink-dev

Contact emails
mig...@chromium.org to...@chromium.org


Spec
https://html.spec.whatwg.org/multipage/interaction.html#spelling-and-grammar-checking


Summary
Spell checking in content editable elements is a very useful feature that most browsers (including Chrome) support. We want to bring that ability to WebView as well.

Motivation
Android WebView is the only platform that does not support spell checking.

Interoperability and Compatibility Risk
Unlike the existing implementation in Chrome we would like to treat the default behaviour as “false-by-default”. The spec is very flexible in this respect. Quoting from it.


"For each element, user agents must establish a default behaviour"


The reason for having a different default than Chrome is that we don’t want to break existing apps out there that rely on the existing behaviour. Apps that want to use the new functionality will need to specify the attribute (something like <textarea spellcheck> </textarea>)

Ongoing technical constraints
None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes! With this intent to ship we make this statement true.

OWP launch tracking bug
https://code.google.com/p/chromium/issues/detail?id=583616

Link to entry on the feature dashboard
https://www.chromestatus.com/features/5653714173952000


Domenic Denicola

unread,
Feb 3, 2016, 11:23:12 AM2/3/16
to Miguel Garcia, blink-dev
Good stuff! Just some minor things I noticed...

From: mig...@google.com [mailto:mig...@google.com] On Behalf Of Miguel Garcia

> Unlike the existing implementation in Chrome we would like to treat the default behaviour as “false-by-default”. The spec is very flexible in this respect. Quoting from it.
>
> "For each element, user agents must establish a default behaviour"

Upon re-reading this area of the spec I realized it was confusing. Your interpretation is correct but the sentences immediately after the one you quote are misleading. Filed https://github.com/whatwg/html/issues/615 to get that clarified :)

> The reason for having a different default than Chrome is that we don’t want to break existing apps out there that rely on the existing behaviour. Apps that want to use the new functionality will need to specify the attribute (something like <textarea spellcheck> </textarea>)

FYI: It'd be <textarea spellcheck="true">

Philip Jägenstedt

unread,
Feb 4, 2016, 4:31:47 AM2/4/16
to Miguel Garcia, blink-dev
LGTM1, spellcheck for all!
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+...@chromium.org.

Chris Harrelson

unread,
Feb 4, 2016, 2:06:15 PM2/4/16
to Philip Jägenstedt, Miguel Garcia, blink-dev
LGTM2

Dimitri Glazkov

unread,
Feb 4, 2016, 2:06:53 PM2/4/16
to Chris Harrelson, Philip Jägenstedt, Miguel Garcia, blink-dev
LGTM3

Joe Medley

unread,
Feb 17, 2016, 10:52:26 AM2/17/16
to Dimitri Glazkov, Chris Harrelson, Philip Jägenstedt, Miguel Garcia, blink-dev
Which version to you plan to ship in? Please update the dashboard.

Joe Medley | Technical Writer, DevPlat | jme...@google.com | 816-678-7195

Joe Medley

unread,
Feb 22, 2016, 1:06:18 PM2/22/16
to Miguel Garcia, Chris Harrelson, Philip Jägenstedt, blink-dev, Dimitri Glazkov
Miguel,

Which version do you plan to ship in?

Joe

Joe Medley | Technical Writer, DevPlat | jme...@google.com | 816-678-7195

Reply all
Reply to author
Forward
0 new messages