Comment 1 for bug 1317931

Confirming, same behavior here. On first glance, I'm not very hopeful we can fix this from Onboard, though.

For some background, Onboard has two ways of getting what you type to applications:

1) By directly inserting text into text entries via AT-SPI. This is preferred, it's the short path, it basically never fails. However it requires solid support for AT-SPI. We basically have this only in gtk-3 applications like gedit, epiphany, nautilus, etc.

2) By simulating key-strokes via XTest. There are various known problems with this path, for example firefox losing fast key-strokes and certain special characters unintentionally triggering hotkeys.

Chromium falls into category 2), because support for AT-SPI is basically non-existent there. However it gets the same treatment as firefox, and there special characters type well enough.

I see two ways forward: chromium provides AT-SPI text interfaces, or more realistically we try to figure out where the key-strokes get lost in chromium.