Closed Bug 1632013 Opened 6 years ago Closed 6 years ago

Text input does not trigger responses (e.g. autocomplete suggestions) immediately

Categories

(Core :: Widget: Gtk, defect, P3)

75 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: austin.glaser, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Steps to reproduce:

Unfortunately, I don't have any concrete reproduction steps. This appears to be a state the browser gets into (and exits) periodically after running for some time. It will reset if I restart the browser.

On different websites (or in different parts of the browser) this bug manifests in different ways. I am, however, pretty certain that the root cause is the same at this point. My reasoning is:

  • All appear to be associated with some missing action that occurs while I'm providing text input
  • Either all these issues are simultaneously present, or none are

I do not have deep knowledge of Firefox's internals, and I'm also not a web dev. But my instincts are telling me there is some kind of event on text input which is not being propagated -- the keystrokes are captured, but consumers are not notified, and so do not receive the entered text until some other event (a mouse click, for instance) occurs.

I know it's unhelpful to report a bug with no concrete reproduction steps -- but if someone can give me instructions on capturing debug logs from Firefox, I will try to do so both while the browser is in this state and while it's behaving correctly, or perform whatever kind of testing would be helpful in one state or the other.

Actual results:

When entering text in the address bar:

  • The text appears, but no auto completion or suggested dropdown appears
  • When I enter punctuation (e.g. '.' or '/'), press an arrow key, or click the mouse in the address bar, the autocompletions and dropdown appear

When composing a message in gmail, with suggestions enabled:

  • When I type a character that triggers a suggestion, the character and suggestion appear, and then the character I just entered disappears

When creating a time entry on https://harvestapp.com:

  • With the project dropdown highlighted, when I begin typing, no dropdown with filtered results appears
  • When I click the dropdown, I see the search text I've entered and the filtered results

Expected results:

When entering text in the address bar:

  • The autocomplete dropdown and text suggestions should appear as I type input

When composing a message in gmail, with suggestions enabled:

  • When I type a character that triggers a suggestion, the character and suggestion should appear, and persist while I keep typing

When creating a time entry on https://harvestapp.com:

  • With the project dropdown highlighted, when I begin typing, a dropdown with filtered project results should appear, and be updated as I type

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Address Bar

Pervasive text input problem, on Linux (according to the user agent string in comment 0), so over to Core::Widget: Gtk.

Component: Address Bar → Widget: Gtk
Product: Firefox → Core
Priority: -- → P3

(In reply to Austin Glaser from comment #0)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0

Do you see the same problem with https://nightly.mozilla.org?

I'll get back to you once I've installed it and run it for a bit

I have not seen this so far on nightly after ~2 hours of use. On 75.0, it usually shows up pretty quickly.

Okay, closing. Please let us know if you see it in nightly again.
Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME

I did just see this happen again on nightly briefly.

And it seems to be back on nightly consistently.

I tried capturing console logs, but when I type in the address bar none seem to be generated until I actually hit enter and start loading a page. Is there some other way I can capture more information to help debug this?

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