Chromium doesn't open OSK under GNOME Shell

Bug #1697641 reported by Will Cooke
20
This bug affects 5 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
High
Unassigned

Bug Description

Other Gtk apps signal the OSK to appear when using touch as the primary navigation method. e.g. Touch in to gedit, and the osk pops up, touch in to eog and it goes away.

Chromium doesn't do this (and nor does Firefox). This will be required for good 2-in-1 support.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 58.0.3029.110-0ubuntu0.16.04.1281
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DRM.card0-DP-1:
 edid-base64:
 dpms: Off
 modes:
 enabled: disabled
 status: disconnected
DRM.card0-DP-2:
 edid-base64: AP///////wAQrHNATDUxRxAWAQSlMx14O26lo1RPnyYRUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUA/h8RAAAeAAAA/wA1OURKUDI0SkcxNUwKAAAA/ABERUxMIFUyMzEySE0KAAAA/QA4TB5TEQAKICAgICAgAOk=
 dpms: On
 modes: 1920x1080 1680x1050 1680x945 1400x1050 1400x1050 1600x900 1280x1024 1280x1024 1440x900 1440x900 1280x960 1366x768 1360x768 1280x800 1280x800 1152x864 1280x768 1280x768 1280x720 1024x768 1024x768 1024x768 1024x576 800x600 800x600 800x600 800x600 848x480 640x480 640x480 640x480 720x400
 enabled: enabled
 status: connected
DRM.card0-DP-3:
 edid-base64:
 dpms: Off
 modes:
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-1:
 edid-base64:
 dpms: Off
 modes:
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-2:
 edid-base64:
 dpms: Off
 modes:
 enabled: disabled
 status: disconnected
DRM.card0-HDMI-A-3:
 edid-base64:
 dpms: Off
 modes:
 enabled: disabled
 status: disconnected
DRM.card0-LVDS-1:
 edid-base64: AP///////wAw5NgCAAAAAAAUAQOAHBB46tTllVlXiyggUFQAAAABAQEBAQEBAQEBAQEBAQEBYB1W2FAAGDAwQEcAFZwQAAAbAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBMRyBEaXNwbGF5CiAgAAAA/gBMUDEyNVdIMi1TTEIxAIQ=
 dpms: On
 modes: 1366x768
 enabled: enabled
 status: connected
DRM.card0-VGA-1:
 edid-base64:
 dpms: Off
 modes:
 enabled: disabled
 status: disconnected
Date: Tue Jun 13 09:54:41 2017
Desktop-Session:
 'None'
 'None'
 'None'
DetectedPlugins:

EcryptfsInUse: Yes
Env:
 'None'
 'None'
InstallationDate: Installed on 2016-04-22 (416 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Load-Avg-1min: 0.27
Load-Processes-Running-Percent: 0.1%
MachineType: LENOVO 4287CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=3016f766-1b5d-4550-ba62-3373b530cf42 ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET50WW (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4287CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4287CTO
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b''
modified.conffile..etc.default.chromium-browser: [deleted]

Related branches

Revision history for this message
Will Cooke (willcooke) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

Does that affect the omnibox (address bar), text fields in web content, or both?
I unfortunately don't have touch hardware to test that on.

Revision history for this message
Will Cooke (willcooke) wrote :

It's both.

Interestingly, double-pressing on text in the omnibox or a text input field does open a "Cut, Copy, Paste" dialogue.

Revision history for this message
Will Cooke (willcooke) wrote :

Olivier - could you take a look at this one again when you're back from hols?

Changed in chromium-browser (Ubuntu):
assignee: nobody → Olivier Tilloy (osomon)
Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Olivier Tilloy (osomon) wrote :

From http://www.chromium.org/developers/accessibility/linux-accessibility:

 « Currently, accessibility of Chromium on desktop Linux is not really supported. However, there is a medium-term plan to solve this - please contact <email address hidden> if you'd like more information. Our goal is for all users to have an excellent experience, and we have a plan that will make everything work great while minimizing the extra effort required by Chromium developers. »

Revision history for this message
Olivier Tilloy (osomon) wrote :

Some data points:

 Version 58.0.3029.110 on trusty, the a11y tree shows up in accerciser, but if I enable the OSK in the accessibility settings, the next launch only the root node shows up for chromium (and focusing text fields in chromium doesn't bring up the OSK).

 Version 58.0.3029.110 on xenial, only the root node shows up in accerciser, regardless of whether the OSK is enabled.

 Version 59.0.3071.109 on trusty, only the root node shows up in accerciser, regardless of whether the OSK is enabled.

Revision history for this message
Olivier Tilloy (osomon) wrote :

A long overdue update: accessibility seems to work again in chromium, it has to be force-enabled to actually function:

    ACCESSIBILITY_ENABLED=1 chromium-browser --force-renderer-accessibility

(useful documentation: https://www.chromium.org/developers/design-documents/accessibility)

Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

Oliver, is it still works for you with current Chromium builds?

Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
status: In Progress → New
assignee: Olivier Tilloy (osomon) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.