No special characters in Facebook with spell checking activated

[cribari]

I run Qupzila version 2.2.3-2 in Arch Linux + KDE Plasma, qt5 version 5.10.0. My computer has a US International with dead keys keyboard layout. I have the hunspell, hunspell-en and hunspell-pt-br Arch packages installed. I installed the US English and the Brazilian Portuguese dictionaries for spell checking as follows:

cd /usr/share/hunspell 
sudo qwebengine_convert_dict en_US.dic en_US.bdic
sudo qwebengine_convert_dict pt_BR.dic pt_BR.bdic
sudo mkdir /usr/bin/qtwebengine_dictionaries
sudo cp *.bdic /usr/bin/qtwebengine_dictionaries/.

When spell checking is activated in the preferences I am unable to type special characters in Facebook. For instance, when I type é, ã, ô etc. the character shows up and is immediately erased. The only special chacater that is displayed upon typing is ç. Example: If I type "não" what I get is "no". The probem, which only happens with Facebook, vanishes when I disable spell checking.

[cribari]

The problem remains in Qupzilla version 2.2.4.

[ghost]

@cribari I tried to do it. How do you type these characters? Because I have only one way to do this - a virtual keyboard, and with vkbd it works

[cribari]

@Diablopc At the outset, assuming that your computer has a regular US keyboard, chose the following keyboard layout: US international with dead key. In KDE's system settings, it is listed as: English (US, intl., with dead keys). To type, for instance, não (which means no in Portuguese), enter n~ao (n tilde a o, no spaces between letters). The tilde will then the place above the a. Similarly, ^e yields ê, 'o yields ó and so on. Do that in konsole (the KDE terminal) and also on Facebook. It should work when you type in konsole but not in Facebook. The only special character that shows up correctly in Facebook is ç which is obtained by simultaneously pressing ALT and comma (ALT ,). P.S. Don't forget to first activate spell checking (US English and Brazilian Portuguese).

[ghost]

@cribari hah, yep. tomorrow I'll also try with qt5.9

Btw, retried with pure qtwebengine browser (it implements just qtwebengine and no more) The same behaviour appears. Seems this issue depends exactly on webengine, not on qupzilla...

[cribari]

The problem remains in version 2.2.5:

Application version 2.2.5 QtWebEngine version 5.10.0

[nowrep]

That's a bug in QtWebEngine, please report it to http://bugreports.qt.io/

[cribari]

Done: https://bugreports.qt.io/browse/QTBUG-66046