1887533 - Address bar contents shift leftwards (moving characters that I entered out of view), when a long domain name gets autocompleted

Status: NEW

(Fenix :: Toolbar, defect, P3)

Description

[Daniel Holbert [:dholbert]]

Steps to reproduce

1. Start with a fresh browser profile (optional but encouraged)

2. Visit these sites (to get them into your history and hence autocompletion):
   http://stripe-upload-api.s3.us-west-1.amazonaws.com
   https://support.mozilla.org/en-US/
   https://support.google.com

3. Open a new tab, and slowly type "s t r" into the address bar using the software keyboard. Watch the address bar contents carefully.

Expected behavior

Address bar contents should be stable (no horizontal scrolling) as you type.

Actual behavior

The address bar contents jump leftwards unexpectedly, so that "s" (the first character that I typed) is suddenly not visible.

Device information

• Firefox version: 125.0a1 (also reproducible in release 123.1.0, probably other/older builds as well)
• Android device model: Pixel 6a, Pixel 8
• Android OS version: 14

Any additional information?

I'll post a screencast shortly.

Comment 1

[Daniel Holbert [:dholbert]]

Attachment: screencast of bug manifesting a little bit (`s` gets shifted partially out of view)

Here's a screencast of the bug manifesting a little bit -- the "s" that I typed gets unexpectedly shifted leftwards slightly, making it partially cropped (partially pushed off the left edge of the address bar).

Comment 2

[Daniel Holbert [:dholbert]]

Attachment: screencast of bug manifesting a lot (`s` gets shifted **entirely** out of view)

Here's another screencast showing the bug manifesting a lot more. In this case, the "s" is fine when the long stripe-... domain name first autocompletes (when I type the t). But when I type the next letter (r), the address bar contents unexpectedly shift left, pushing the s entirely out of view.

Comment 3

[Daniel Holbert [:dholbert]]

Note: this doesn't happen every time, but I can pretty reliably reproduce one or both behaviors captured in comment 1 & comment 2 within a minute or so. If you're testing this bug and not seeing the issue right away, try restarting Firefox, or try again in a freshly-opened new tab.

Comment 4

[Daniel Holbert [:dholbert]]

note, both of those screencasts are from a fresh browser profile where I've just performed the STR in comment 0 (and restarted Firefox once or twice).

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:boek, could you have a look please?

For more information, please visit BugBot documentation.

Comment 6

[Jeff Boek [:boek]]

Roger: One more for you

Comment 7

[Roger Yang [:royang]]

Hi Daniel, can you still reproduce it in Nightly? I couldn't reproduce this issue. Thanks

Comment 8

[Daniel Holbert [:dholbert]]

I just repro'd with very-slightly-out-of-date Nightly 2024-04-27 on my Pixel 6a.

Updating now, I'll let you know if up-to-date Nightly still repro's it.

Comment 9

[Daniel Holbert [:dholbert]]

Yes, I can still reproduce in latest Nightly with the STR in comment 0 (on my Pixel 6a).

Notes to aid in reproducing:

• per comment 3 it might take a few attempts to reproduce it, so it's worth retesting a few times if you haven't already (starting with a fresh new-tab each time)
• it might also help to test in a fresh browser profile (e.g. clear Nightly data), to be sure that you're not getting other autocompletion suggestions from your own history, which might save you from triggering the bug.

Does that help with repro'ing? I can post a fresh screencast to demo it again, if that's useful.

Comment 10

[Daniel Holbert [:dholbert]]

Attachment: screencast of bug manifesting a few times in a fresh profile with latest Nightly on 4/30

Comment 11

[Daniel Holbert [:dholbert]]

See attached screencast from pixel 6a, captured today with latest Nightly, freshly cleared profile data (version info shown at 2:12 in video).

I perform the STR and just repeat step 3 over and over.

The bug only manifested twice for me, I think:
(1) at 0:51 (this was my second repetition of STR step 3). The first character "s" gets scrolled entirely out of view, as in comment 2.
(2) at 1:01 (this was my third repetition of STR step 3). The first character "s" gets scrolled partially out of view as in comment 1.

Comment 12

[Roger Yang [:royang]]

Understood. I'll try step 3 more until I can see it. Thanks

Comment 13

[Chris Peterson [:cpeterson]]

Let's retest after the new toolbar redesign lands in bug 1889863.