Bug 2050337 - Focused Form elements do not receive input
Summary: Focused Form elements do not receive input
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: qutebrowser
Version: 36
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Timothée Floure
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-03 18:02 UTC by Onyeibo Oku
Modified: 2022-09-05 07:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-05 07:27:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Onyeibo Oku 2022-02-03 18:02:17 UTC
Description of problem:
Text input boxes in forms (e.g. Log in, sign-in) receive focus but not text input from keyboard. Pressing [TAB] moves to the next indexed form element.  Buttons work but not text fields.

Version-Release number of selected component (if applicable):
2.4.0-2.fc36

How reproducible:
Its been consistent between reboots for some days

Steps to Reproduce:
1.  Update Fedora Rawhide to recent repo packages
2.  Fire up qutebrowser and try to log into an online account (e.g. bugzilla)
3.  *done*

Actual results:
Text input fields on the forms will only get focus but not receive text input

Expected results:
User should see text on screen as they are being typed into the textboxes

Additional info:

Comment 1 Ben Cotton 2022-02-08 20:17:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 2 Timothée Floure 2022-06-02 18:53:49 UTC
My gut feeling says it's a qt issue, not directly a qutebrowser issue. Does the issue persist? If so, please paste the content your qutebrowser `:version` page here (so that we have more infos on your environment).

Comment 3 Onyeibo Oku 2022-06-17 11:11:13 UTC
rgr(In reply to Timothée Floure from comment #2)
> My gut feeling says it's a qt issue, not directly a qutebrowser issue. Does
> the issue persist? If so, please paste the content your qutebrowser
> `:version` page here (so that we have more infos on your environment).

nah, it's gone.
Latest is happening in Firefox.  You can close this ticket.


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