Open Bug 1470643 Opened 7 years ago Updated 2 years ago

Address bar not immediately cleared in Windows tablet mode

Categories

(Firefox :: Address Bar, defect, P5)

Product:
Firefox
Component:
Address Bar
Version:
60 Branch
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: xracoonx, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180605171542 Firefox for Android Steps to reproduce: 1 Enter Windows (10) tablet mode 2 Open a website 3 Open a new tab Actual results: The address bar is cleared only after a short delay. Expected results: It is cleared immediately.
Component: Untriaged → Address Bar
Do you mean the address bar input field, or the results popup?
Flags: needinfo?(xracoonx)
(In reply to Marco Bonardo [::mak] from comment #1) > Do you mean the address bar input field, or the results popup? It is the address bar input field.
Flags: needinfo?(xracoonx)
Priority: -- → P5
See Also: → 1498973

I think this has just gotten much worse on Nightly in the last week or perhaps two (not sure which as I don’t update every day): I never noticed any problem before (but I don’t often use Firefox when in tablet mode), but now when I return to desktop mode I am observing the address bar results dropdown staying open persistently (!) on all windows and never closing again until I kill the browser (though just now when trying it out, opening a result in a new tab with Alt+Enter did proceed to close it, but I’m pretty sure I tried that yesterday and the day before when I encountered this situation, unsuccessfully).

I would say this is now an important bug which substantially harms users that may easily encounter it. Most of the time I’m in a fairly bandwidth-constrained environment, so I can’t currently help with finding a regression window.

Welcome to the club. Though it is a slightly different bug than the one reported here. What you see is probably the one Marco referred to above. That other bug is at P2 but maybe it should get more attention...

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.