Bug 746112

Summary:	firefox won't automatically open the new gnome on-screen keyboard
Product:	[Fedora] Fedora	Reporter:	Tobias Domhan <tdomhan>
Component:	firefox	Assignee:	Jan Horak <jhorak>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gecko-bugs-nobody, jhorak, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-06 13:16:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tobias Domhan 2011-10-13 22:25:43 UTC

Description of problem:
the new on-screen keyboard is a really cool feature. once enabled in the accessibility settings it will open up as soon as a text input field gets focus.
this is true for the shell and all other applications I tested, e.g. google chrome.
however there is one app, namely firefox, that just won't open the keyboard, when the url or search field will get focus.

Version-Release number of selected component (if applicable):
I downloaded, installed and updated fedora to the latest software available.

How reproducible:


Steps to Reproduce:
1. enable on screen keyboard in accessibility settings
2. go to firefox and click in the url bar
  
Actual results:
no on-screen keyboar showing up

Expected results:
an on-screen keyboard appearing as soon as the url bar gets focus

Additional info:

Comment 1 Jan Horak 2012-03-29 15:10:07 UTC

Yep, that's true. Taking...

Comment 2 Ray Strode [halfline] 2012-08-10 15:32:14 UTC

relevant irc discussion:

<jhorak> I'm a litte bit puzzled about on-screen keyboard. It used to autohide and show when clicking on input field, now it doesn't.
<halfline> i think it "detects" text entries using a gtk plugin from caribou
<halfline> so it could be you don't have the right plugin installed anymore
<halfline> or maybe you have it for gtk3 apps and not gtk2 apps
<halfline> (or vice versa)
<jhorak> hm, caribou, I didn't have caribou-gtk2/3-module installed.
<aday> jhorak, yep, it worked in F16
<aday> must have regressed for F17
<aday> it doesn't seem to work in firefox in F16; it's fine with gtk2 and gtk3 apps though
<jhorak> it might be missing caribou modules...
<halfline> i think firefox filters its gtk module list
<halfline> iirc
<halfline> so that might be related

Comment 3 Jan Horak 2012-09-06 13:16:25 UTC

We've escalated this bug to upstream:
https://bugzilla.mozilla.org/show_bug.cgi?id=789038