944607 - [meta] Leverage autocorrect and autocapitalize attributes for gaia keyboard hinting

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Description

[Kevin Grandon :kgrandon]

Autocorrect and autocapitalize are two fairly well understood HTML attributes. We should use these in gaia instead of using x-inputmode.

Comment 1

[Jason Smith [:jsmith]]

Relevant google group discussion for this:

https://groups.google.com/forum/#!topic/mozilla.dev.webapi/se0h7PUrQOY

Comment 2

[Ben Bucksch (:BenB)]

Looks like a dup of bug 943690 to me.

Comment 3

[Jason Smith [:jsmith]]

(In reply to Ben Bucksch (:BenB) from comment #2)
> Looks like a dup of bug 943690 to me.

Not really. That bug has a specific use case in mind with auto-correct off, while this bug targets the other use cases with auto-correct & auto-capitalize.

Comment 4

[(no longer active)]

(In reply to Kevin Grandon :kgrandon from comment #0)
> Autocorrect and autocapitalize are two fairly well understood HTML
> attributes.

Are they?  I've never seen a spec for either one of them, the only information I can find about them is on Apple's developer website <https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariHTMLRef/Articles/Attributes.html#//apple_ref/doc/uid/TP40008058-autocorrect>.

> We should use these in gaia instead of using x-inputmode.

I'm not sure why you think we should do that.  Gecko will happily ignore these attributes if you use them, so what's the point of using them?

Comment 5

[Kevin Grandon :kgrandon]

(In reply to :Ehsan Akhgari (needinfo? me!) from comment #4)
> (In reply to Kevin Grandon :kgrandon from comment #0)
> > Autocorrect and autocapitalize are two fairly well understood HTML
> > attributes.
> 
> Are they?  I've never seen a spec for either one of them, the only
> information I can find about them is on Apple's developer website
> <https://developer.apple.com/library/safari/documentation/AppleApplications/
> Reference/SafariHTMLRef/Articles/Attributes.html#//apple_ref/doc/uid/
> TP40008058-autocorrect>.
> 
> > We should use these in gaia instead of using x-inputmode.
> 
> I'm not sure why you think we should do that.  Gecko will happily ignore
> these attributes if you use them, so what's the point of using them?


Yes, developers who are building mobile apps today use these elements already when building mobile apps/websites. It makes sense to leverage only a single way of doing this to make the web truly ubiquitous.

Comment 6

[Kevin Grandon :kgrandon]

There is already a lot of good discussion in bug 943690. I think we should turn this into a meta bug and depend on that one.

Comment 7

[Ben Bucksch (:BenB)]

(In reply to Jason Smith [:jsmith] from comment #3)
> > Looks like a dup of bug 943690 to me.
> 
> Not really. That bug has a specific use case in mind with auto-correct off

No, actually, it doesn't. I filed bug 943690, and while I had *my* usecase in my Firefox OS app (not Marketplace search) in mind, I meant it to cover all usecases.

In bug 943690 comment 11, I specifically included a number of usecases on webpages, Firefox OS apps, and Firefox Marketplace search.

As such, I think this is a DUP.

Comment 8

[Kevin Grandon :kgrandon]

(In reply to Ben Bucksch (:BenB) from comment #7)
> As such, I think this is a DUP.

This is a meta bug, so it's just for tracking. We'll solve autocorrection in bug 943690.

Comment 9

[(no longer active)]

Please see bug 943690 comment 20.  This bug should probably be wontfixed because of the exact same reasons.

Comment 10

[Jason Smith [:jsmith]]

(In reply to :Ehsan Akhgari (needinfo? me!) from comment #9)
> Please see bug 943690 comment 20.  This bug should probably be wontfixed
> because of the exact same reasons.

The main objection I have here falls in alignment with the discussion that happened on https://bugzilla.mozilla.org/show_bug.cgi?id=921014#c11 - we have to make an accurate assessment of whether there exists a compatibility concern to warrant implementation of this. I think we need data similar to what happened on that bug to determine what to do here.

Comment 11

[(no longer active)]

(In reply to comment #10)
> (In reply to :Ehsan Akhgari (needinfo? me!) from comment #9)
> > Please see bug 943690 comment 20.  This bug should probably be wontfixed
> > because of the exact same reasons.
> 
> The main objection I have here falls in alignment with the discussion that
> happened on https://bugzilla.mozilla.org/show_bug.cgi?id=921014#c11 - we have
> to make an accurate assessment of whether there exists a compatibility concern
> to warrant implementation of this. I think we need data similar to what
> happened on that bug to determine what to do here.

Please let's have this discussion in one place.  :-)

Comment 12

[Jason Smith [:jsmith]]

See https://bugzilla.mozilla.org/show_bug.cgi?id=943690#c29.