This is what we need to do for this bug
1) figure out what is done when word engine/predictive text is on, as auto caps works in this case. You can see it work by typing a sentence and then a period. The next word gets capatialize automatically.
2) decouple the auto-caps from the word engine/predictive text such that it can be enabled/disabled on it's own via setting (autocaps)
3) honor the input hints Qt.ImhNoAutoUppercase, Qt.ImhPreferUppercase and Qt.ImhPreferLowercase to control whether a field wants to change the behavior of auto-caps. (see http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-textinput.html#inputMethodHints-prop)
4) set the appropriate hints for our applications. webbrowser for example should use Qt.ImhNoAutoUppercase
This is what we need to do for this bug ercase, Qt.ImhPreferUpp ercase and Qt.ImhPreferLow ercase to control whether a field wants to change the behavior of auto-caps. (see http:// qt-project. org/doc/ qt-5.0/ qtquick/ qml-qtquick2- textinput. html#inputMetho dHints- prop) ercase
1) figure out what is done when word engine/predictive text is on, as auto caps works in this case. You can see it work by typing a sentence and then a period. The next word gets capatialize automatically.
2) decouple the auto-caps from the word engine/predictive text such that it can be enabled/disabled on it's own via setting (autocaps)
3) honor the input hints Qt.ImhNoAutoUpp
4) set the appropriate hints for our applications. webbrowser for example should use Qt.ImhNoAutoUpp