Closed Bug 1402291 Opened 8 years ago Closed 5 years ago

Selected suggestion was disappeared in location bar when go to a new tab then back to the previous tab

Categories

(Firefox :: Address Bar, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 --- wontfix

People

(Reporter: mAlmas, Unassigned)

Details

Attachments

(1 file)

Attached video new_tab.mp4
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce: 1. Open Firefox 2. Write any address(e.g. google.com) 3. While writing 1 or 2 letter location bar suggest some address link which is similar to it 4. Select www.google.com 5. Now open a new tab 6. Go to new tab 7. Then back to previous tab where "google" was selected Actual results: It does not show the selected address from the suggestion which i picked. It just show that 1 or 2 letter which was typed. Expected results: Location bar should contain or remember the selected Address link.
Component: Untriaged → Address Bar
This is related to the changes to the undo behavior in the Location Bar. In particular, what you typed (and is stored in undo history) is "go", you didn't type the rest. What's the expected outcome is debatable.
(In reply to Marco Bonardo [::mak] from comment #1) > This is related to the changes to the undo behavior in the Location Bar. In > particular, what you typed (and is stored in undo history) is "go", you > didn't type the rest. > What's the expected outcome is debatable. But in this case, when I try this in Chrome it was perfect as I wanted. They didn't do this.They store the selected one, not what I typed. And I need that thing not the typed letter.
But Firefox is not Chrome :) As I said, we need to define an expected behavior, and then based on that this is either a bug or a wontfix.
(In reply to Marco Bonardo [::mak] from comment #3) > But Firefox is not Chrome :) As I said, we need to define an expected > behavior, and then based on that this is either a bug or a wontfix. Okay, I understand.
I can understand that autocompletions which haven't been chosen by the user might be undone, but removing completions explicitly chosen by the user is surprising and unhelpful.
I agree with Almas and Karl, marking this a P3.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3

This should be working correctly now

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: