To support autocorrect attribute for input element

[Rudy Lu]

Hi all,

We have a bug, Bug 943690 - Autocorrection doesn't honor <input autocorrect="off"> [1], talking about the support of autocorrect attribute.
Is there any discussion or proposal about supporting this and autocapitalize, and other attributes for input element?

I only found an old thread [2], that Mounir mentioned that we may not want to support that.
Is that idea ever changed after that discussion?

Thanks.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=943690
[2] https://groups.google.com/d/msg/mozilla.dev.webapi/Vs3-HGv9NNw/V8_NKwxGoaQJ

--
Best regards,
Rudy, Mozilla Taiwan

[Ehsan Akhgari]

I commented on the bug. I'm not aware of any plans to implement either
of the two attributes. Note that the autocorrect attribute is probably
insufficient for all but the simplest use cases, since the UA might
provide multiple autocorrection options.

Cheers,
Ehsan

> _______________________________________________
> dev-webapi mailing list
> dev-w...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-webapi
>

[Jan Jongboom]

I think we should support it one way or another, whether it's through the
autocorrect="off" attribute or with something better that we also propose
to W3C but I was pretty surprised that this wouldn't work. There are plenty
of use cases (typing over codes, typing names, etc.) where autocorrect is
really annoying (see f.e. the contacts app in FFOS).

[Ehsan Akhgari]

On 11/28/2013, 3:44 PM, Jan Jongboom wrote:
> I think we should support it one way or another, whether it's through
> the autocorrect="off" attribute or with something better that we also
> propose to W3C but I was pretty surprised that this wouldn't work. There
> are plenty of use cases (typing over codes, typing names, etc.) where
> autocorrect is really annoying (see f.e. the contacts app in FFOS).

Do you have a proposal for what you would like to see here? A simple
autocorrect attribute is probably insufficient as it doesn't specify
what type of autocorrection we're talking about.

Cheers,
Ehsan

[Jan Jongboom]

Can you give a scenario where a simple autocorrect attribute is not
sufficient? As far as I know we only have one type of autocorrect (at least
in FFOS)?

[Dale Harvey]

As far as I remember the email used inputmode=verbatim to prevent
autocomplete, always annoyed me because it was impossible to have it auto
capitalise for names and turn off autocomplete at the same time, would be
nice if we could autocomplete=off and support auto capitalisation as well

[Kevin Grandon]

It seems like we should probably leverage the autocorrect and autocapitalize attributes for this?

Best,
Kevin

[Ehsan Akhgari]

On 11/28/2013, 4:08 PM, Jan Jongboom wrote:
> Can you give a scenario where a simple autocorrect attribute is not
> sufficient? As far as I know we only have one type of autocorrect (at
> least in FFOS)?

Autocapitalization is one example, auto-grammar-correction is another.
In the future we might do other types of corrections as well (such as
iOS style phrase abbreviation.)

Note that I'm more interested in what we may have in Firefox OS and
elsewhere on the web in the future, what we have today should not be the
only requirement for designing this feature.

Cheers,
Ehsan

[Rudy Lu]

Hi all,

Just want add a note to clarify the current status in Firefox OS,

We have x-inputmode support implemented, and now it supports the following values:
'verbatim': don't alter the user's input at all
'latin': offer word suggestions/corrections, but no capitalization
'latin-prose': offer word suggestions and capitalization

As Dale mentioned, it seems we don't have a value for "auto capitalization only".

--
Best regards,
Rudy, Mozilla Taiwan

[Kevin Grandon]

Autocorrect and autocapitalize are two well understand HTML attributes. We should leverage these and do more work to standardize if we deem necessary.

I have filed this bug to implement in gaia: https://bugzilla.mozilla.org/show_bug.cgi?id=944607

If you oppose this, please comment here or in the bug.

Thanks,
Kevin

[Jan Jongboom]

And apparently it works for FF for Android, so...

[Ehsan Akhgari]

On 11/29/2013, 8:54 AM, Jan Jongboom wrote:
> And apparently it works for FF for Android, so...

Do you have a test case which shows this? I find that very surprising
since I can't find any mention of these attributes in mozilla-central
except in the imported CoreMirror source.

Cheers,
Ehsan

> <mailto:ehsan....@gmail.com>> wrote:
>
> > On 11/28/2013, 4:08 PM, Jan Jongboom wrote:
> >> Can you give a scenario where a simple autocorrect attribute is not
> >> sufficient? As far as I know we only have one type of
> autocorrect (at
> >> least in FFOS)?
> >
> > Autocapitalization is one example, auto-grammar-correction is
> another. In the future we might do other types of corrections as
> well (such as iOS style phrase abbreviation.)
> >
> > Note that I'm more interested in what we may have in Firefox OS
> and elsewhere on the web in the future, what we have today should
> not be the only requirement for designing this feature.
> >
> > Cheers,
> > Ehsan
> >
>
> _______________________________________________
> dev-webapi mailing list

> dev-w...@lists.mozilla.org <mailto:dev-w...@lists.mozilla.org>
> https://lists.mozilla.org/listinfo/dev-webapi
>
>

[Jonas Sicking]

I'd really like to create a thought through proposal for this stuff.
As I understand it, there are at least the following things that as a
developer you'd like to control:

* Should spellcheck be enabled.
* Should autocorrect for virtual keyboards be forced-off.
* Should autocapitalize be entirely off, should it autocapitalize for
"normal" text, or for names.
* Numeric entry (for example zipcodes, where <input type=number> is in
appropriate)
* For Japanese entry, should it use Hirakana or Katakana.

I don't know if other scripts or languages need other metadata. Does
chinese or arabic?

There's a lot of correlation between several of these. For example for
things like code entry you want all "aids" like autocaptialize,
autocorrect and spellcheck. And if spellcheck is turned off then
autocorrect seesm like it should at least default to being off.

Another thing to keep in mind is that a single <input> might need to
handle both latin text, and japanese text. This is something that
happens in particular to bilingual people who have names that uses one
script, but visits websites that uses a different script.

There is a proposal in the HTML spec right now. But it conflates a lot
of the above concepts, and also is pretty hard to understand. And it
doesn't allow specifying handling both for japanese and latin text.

I'd love to find a proposal that is reasonably easy to use, with
sensible defaults, but also allows a high degree of control if the
author so desires.

Mounir (formerly at Mozilla, now at Google) has been looking into
this. So if anyone can help out with the above, please do let him
know.

It'd be good for the mobile web, and make it more competitive with
other mobile platforms, if we can find a good solution to the above.

/ Jonas

On Thu, Nov 28, 2013 at 11:22 PM, Kevin Grandon <kgra...@mozilla.com> wrote:
> Autocorrect and autocapitalize are two well understand HTML attributes. We should leverage these and do more work to standardize if we deem necessary.
>
> I have filed this bug to implement in gaia: https://bugzilla.mozilla.org/show_bug.cgi?id=944607
>
> If you oppose this, please comment here or in the bug.
>
> Thanks,
> Kevin
>
> ----- Original Message -----
> From: "Rudy Lu" <r...@mozilla.com>

> To: "Ehsan Akhgari" <ehsan....@gmail.com>
> Cc: mozilla-d...@lists.mozilla.org, "Jan Jongboom" <janjo...@gmail.com>
> Sent: Friday, November 29, 2013 1:29:15 AM
> Subject: Re: To support autocorrect attribute for input element
>
> Hi all,
>
> Just want add a note to clarify the current status in Firefox OS,
>
> We have x-inputmode support implemented, and now it supports the following values:
> 'verbatim': don't alter the user's input at all
> 'latin': offer word suggestions/corrections, but no capitalization
> 'latin-prose': offer word suggestions and capitalization
>
> As Dale mentioned, it seems we don't have a value for "auto capitalization only".
>
> --
> Best regards,
> Rudy, Mozilla Taiwan
>

> On 2013/11/29, at 上午6:55, Ehsan Akhgari <ehsan....@gmail.com> wrote:
>
>> On 11/28/2013, 4:08 PM, Jan Jongboom wrote:
>>> Can you give a scenario where a simple autocorrect attribute is not
>>> sufficient? As far as I know we only have one type of autocorrect (at
>>> least in FFOS)?
>>
>> Autocapitalization is one example, auto-grammar-correction is another. In the future we might do other types of corrections as well (such as iOS style phrase abbreviation.)
>>
>> Note that I'm more interested in what we may have in Firefox OS and elsewhere on the web in the future, what we have today should not be the only requirement for designing this feature.
>>
>> Cheers,
>> Ehsan
>>
>
> _______________________________________________
> dev-webapi mailing list
> dev-w...@lists.mozilla.org

> https://lists.mozilla.org/listinfo/dev-webapi

> _______________________________________________
> dev-webapi mailing list
> dev-w...@lists.mozilla.org

> https://lists.mozilla.org/listinfo/dev-webapi