+rlanday who is working on autocapitalize for Android

Do you have any idea autocapitalize will be supported on non-Android
Chrome?

I think basically all that needs to be done to support autocapitalize on Chrome OS though is to update the browser-side code that gets the autocapitalize flags from InputMethodController in the renderer (e.g. perhaps in RenderWidgetHostViewAura::OnUpdateTextInputStateCalled()) to pass the flag along to the IME.

I don't normally work on Chrome OS input, but maybe I can figure out how to do it (assuming Chrome OS IMEs actually support the functionality?).

I don’t want to get your hopes up; I’m thinking that if the Chrome OS on-screen keyboards did support configurable autocapitalization, we would’ve already exposed this functionality to the web, so it might actually require actually building this feature from scratch in the keyboards.

Passing to shuchen@, who works on Chrome OS input.

The on-screen keyboard does support autocapitalize.
We may just need to hook up the web input field attribute with the on-screen keyboard configuration.

Yingbing, can you please take a look? Thanks.

We should already support the feature in R64. Previous may has bug.
Will verify it when I back office on Tuesday.

Since Tuesday the 2nd 2018 a few days have passed... Any updates on this?

FYI. wuyingbing@ will come back in early next week from the Chinese New Year holidays/vacation.

It looks like, even it's not supported yet, but it's working in it's own way
and not respecting autocapitalize=  hints. 

1. Create a page with <div contenteditable autocapitalize="off">div_editable</div>

https://jsfiddle.net/6osbsyxa/11/

Actual:
2a. Try to type "68. " see that it's auto-capitalizing.
2a. Try to type "steve" see that it's auto-capitalizing.

Expected:
2a. Try to type "68. " see that it's not auto-capitalizing.
2a. Try to type "steve" see that it's not auto-capitalizing.

Video:
https://drive.google.com/open?id=1VDSHD_AUPTrTvHjtBxOpsRdzLS-6oQtC

Deleted: VID_20180523_191314.mp4 24.7 MB

VID_20180523_191314.mp4 24.7 MB Download

We already advised our customer that this will turn out to be a Feature Request, and not a bug.
Will there be any estimated timeframe or we can't tell that right now?

Currently Chrome Input Tool API can't get "autocapitalize" properties.

Darren, could you help to add "autoCapitalize" properties on InputContext?
When you done, then reassign the bug to me.

The "autocapitalize" definition of w3c is here:
https://html.spec.whatwg.org/multipage/interaction.html#autocapitalization

I think the blink has supported the autocapitalize attribute:
https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/editing/ime/input_method_controller.cc?gsn=TextInputInfo&g=0&l=1357
And it is already bumped to the IMF.

The remaining effort will be bridge the info to the extension via the extension API, as in here:
https://cs.chromium.org/chromium/src/chrome/browser/extensions/api/input_ime/input_ime_api.cc?sq=package:chromium&dr=CSs&g=0&l=58-61

I can take over this.

Re #11, the extension API fix can be landed in M69. The IME extension fix (which uses the API) will be landed in M70.

This feature has never worked on Chrome OS/ Not with the on-screen or physical keyboard.

Settings > advanced > language and input > input method > US keyboard

chrome-extension://jkghodnilhceideoidjikpgommlajknk/hmm_options.html?code=xkb:us::eng

To classify, disable "Auto-capitalization", however, keyboard still enable the feature. it's a bug.

Keyboard detect previous character is the end of sentence, It make "shift" key pressed. It means "auto capitalization". If the prediction is not correct, user can simply press "shift" key to cancel the prediction.

However, the feature is trigger by chrome.input.ime.onSurroundingTextChanged.  
When your focus is already in inputbox, then you switch to other tab and back. However, in this case. System doesn't fire "onSurroundingTextChanged", so can't trigger auto capitalization.

And in url box, we also don't trigger the feature.

Re #17, besides the points mentioned in #18, it is a known issue[1] that the auto-cap feature doesn't work in an empty text field.
To verify whether the feature can work on your device, please use the on-screen keyboard on http://textarea.org, and just input "a" followed by the period ".". Observe whether the on-screen keyboard UI switches to upper-case mode.

[1]: We disable the auto-cap feature in an empty text field on purpose because Google Docs uses an empty hidden text field (iframe) as the input target. The auto-cap feature would make the on-screen keyboard always in upper-case mode on Google Docs.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f134fb094b6badc3726f8ccf60e0e9a5f0f19af7

commit f134fb094b6badc3726f8ccf60e0e9a5f0f19af7
Author: Shu Chen <shuchen@google.com>
Date: Fri Jun 15 03:12:04 2018

Expose the "autocapitalize" attribute of the text input field to the IME extension.

Bug:  786434 
Change-Id: I7f18cf55c99c61ad398015430818626aedd4da1e
Reviewed-on: https://chromium-review.googlesource.com/1098739
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Shu Chen <shuchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#567531}
[modify] https://crrev.com/f134fb094b6badc3726f8ccf60e0e9a5f0f19af7/chrome/browser/extensions/api/input_ime/input_ime_api.cc
[modify] https://crrev.com/f134fb094b6badc3726f8ccf60e0e9a5f0f19af7/chrome/browser/extensions/api/input_ime/input_ime_api.h
[modify] https://crrev.com/f134fb094b6badc3726f8ccf60e0e9a5f0f19af7/chrome/browser/extensions/api/input_ime/input_ime_api_chromeos.cc
[modify] https://crrev.com/f134fb094b6badc3726f8ccf60e0e9a5f0f19af7/chrome/common/extensions/api/input_ime.json
[modify] https://crrev.com/f134fb094b6badc3726f8ccf60e0e9a5f0f19af7/ui/keyboard/keyboard_util.h

Over to Yingbing to fix in the extension side.

Yingbing, can you update the status here?