RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1067395 - Screen Keyboard in firefox needs restart to work
Summary: Screen Keyboard in firefox needs restart to work
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firefox
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Stransky
QA Contact: Desktop QE
URL:
Whiteboard:
: 1221521 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-20 11:37 UTC by Martin Simon
Modified: 2021-09-03 09:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-17 09:10:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Simon 2014-02-20 11:37:04 UTC
Description of problem:
When I have firefox running and enable Screen Keyboard accessibility, it simply doesn't work in firefox, but it does in other gnome components (like gnome-terminal or xchat). I need to restart firefox with Screen Keyboard accessibility option enabled to get it work.

Version-Release number of selected component (if applicable):
firefox-24.3.0-2.el7.x86_64
gnome-shell-3.8.4-22.el7.x86_64
xulrunner-24.3.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Make sure you have Screen Keyboard disabled
2. Start firefox and gnome-terminal
3. Enable Screen Keyboard accessibility
4. Focus on any input field in firefox
5. Focus on gnome-terminal

Actual results:
Firefox does not invoke on-screen keyboard although the gnome-terminal does

Expected results:
in both cases the on-screen keyboard should be shown

Additional info:

Comment 1 Martin Stransky 2014-11-19 12:10:53 UTC
Well, and how to enable the "Screen Keyboard accessibility"?

Comment 2 Martin Simon 2014-11-19 13:26:38 UTC
It's called "On Screen Keyboard" now and you can enable it with Settings (system user menu) -> Universal Access -> tab Typing -> On Screen Keyboard.

However, not it seems to be working on firefox-31.2.0-3.el7_0.x86_64 (although it's not stable, e.g. some time the keyboard appears even when no input field nor text box is focused and it doesn't want to disappear or e.g. when i started firefox and firefox's default home page appears, i got no on screen keyboard)

Comment 4 Martin Stransky 2015-05-21 10:06:59 UTC
*** Bug 1221521 has been marked as a duplicate of this bug. ***

Comment 6 Tomas Pelka 2017-02-17 09:10:31 UTC
With 3.22 gnome-shell and firefox 52

Comment 7 Andy 2021-09-03 09:26:16 UTC
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1601840


Note You need to log in before you can comment on or make changes to this bug.