auto caps don't work on web page text fields

[Bill Filler]

auto caps don't work at all on webpages with text input (try gmail, twitter, etc)

[Bill Filler (bfiller)]

The current behavior is when first entering the input field the shift key is not enabled. But after typing a . ! or ? then auto caps works for the next word. I assume text fields from the web should work the same as in qml, as long as we are honoring the hints
http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-textinput.html#inputMethodHints-prop

[Michael Sheldon (michael-sheldon)]

It would seem the behaviour of this bug has changed a bit since being first reported, as now autocaps don't work even when following a punctuation mark. This seems to be because Oxide isn't updating the QInputMethod as frequently as it should. According to the docs (http://qt-project.org/doc/qt-5/qinputmethod.html#update) this needs to be called whenever the cursor position changes (e.g. because a new character has just been added, or the user has manually moved the cursor), as this triggers the update of the surrounding text within the keyboard that it uses for evaluating autocaps.

I'll continue to look in to the cause of it not switching to autocaps when first entering a field on the keyboard side, as we do get update() events from Oxide when entering/leaving fields, so this should be unrelated to the above.

[Michael Sheldon (michael-sheldon)]

My mistake; I was testing against the Google search field, and it seems Oxide explicitly requests no caps for search input, so autocaps do work following punctuation. Correct update behaviour will still be needed from Oxide to correctly handle autocaps when deleting the contents of a field though.

[Michael Sheldon (michael-sheldon)]

With the changes in this branch: https://code.launchpad.net/~michael-sheldon/ubuntu-keyboard/fix-1312329 capitals work correctly, except when changing between fields. It would appear that Oxide doesn't call reset() on the input method when changing fields (whereas normal fields do), once that matches standard input fields and the above branch is merged I think this should be largely fixed.