Closed Bug 1346428 Opened 7 years ago Closed 4 years ago

[unifiedcomplete] First suggestions shows originally typed word instead of selected suggestion and brings confusion (sometimes)

Categories

(Firefox :: Address Bar, defect, P3)

34 Branch
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: 684sigma, Unassigned)

References

Details

(Keywords: ux-consistency, Whiteboard: [fxsearch])

I'm not sure if this bug is true, because even after you Delete that, press the Enter key will still open the autofilled domain.


I removes the "Regression" from summary, because it is a issue due to new introduction, though maybe this is regarded as regression. I added the "blocks" to make sure it is not ignored as much as possible.
Has STR: --- → yes
Summary: Regression First suggestions shows originally typed word instead of selected suggestion and brings confusion (sometimes) → [unifiedcomplete] First suggestions shows originally typed word instead of selected suggestion and brings confusion (sometimes)
Version: 52 Branch → 34 Branch
Sorry, I remember I uploaded 3 location bar bugs in a row, but in this one, I simply copy-pasted irrelevant description instead of correct one (the summary is correct!). Can I ask you to replace it / hide the 1st comment?
The right description of the issue is below


I have a problem with Firefox Beta 52. It doesn't happen in Firefox 28.
Sometimes when I select location bar suggestions, first suggestion shows a confusing hint - originally typed word.
It happens unpredictably, however, I noticed one specific scenario when it happens

1. Open https://en.wikipedia.org/wiki/Main_Page
2. Open new tab, type in location bar "wiki main page", press Down several times to select suggestion https://en.wikipedia.org/wiki/Main_Page , then press Right key to select the suggestion
3. Press Down to show suggestions

Result: "wiki main page - Search in Google"
Expected: "https://en.wikipedia.org/wiki/Main_Page - Visit"

As I understand "the first suggestion" concept, it's "shows you what happens when you press Enter in location bar". It's not some additional url I can click. Therefore seeing irrelevant suggestions is confusing. If it, in fact, is some additional url that shouldn't necessarily be related to pressing Enter in location bar, then this bug is probably invalid, but if it is, please clarify that the first suggestion doesn't have to be related to the text in location bar.
I added "Regression" in summary, because browsing became slower compared to Firefox 28, as browser tries to draw my attention to irrelevant hints and notifications. Possibly, don't remove it. As a user, I can't set tags, and can only track bugs/regressions that affect my browsing experience by adding something in the summary.



(In reply to YF (Yang) from comment #1)
> I removes the "Regression" from summary, because it is a issue due to new
> introduction, though maybe this is regarded as regression. I added the
> "blocks" to make sure it is not ignored as much as possible.

What you call a "new introduction" is notification that draws my attention to irrelevant things.
The summary is my only way to track bugs, including regressions and "duplicates" that were resolved and never tested. Earlier I assumed that noone is against minor changes in summary made at my discretion. Please suggest another way to track real regressions I reported, separately from non-regressions.
Flags: needinfo?(yfdyh000)
(In reply to 684sigma from comment #2)
> Sorry, I remember I uploaded 3 location bar bugs in a row, but in this one,
> I simply copy-pasted irrelevant description instead of correct one (the
> summary is correct!). Can I ask you to replace it / hide the 1st comment?
> The right description of the issue is below

Tagged.

> (In reply to YF (Yang) from comment #1)
> > I removes the "Regression" from summary, because it is a issue due to new
> > introduction, though maybe this is regarded as regression. I added the
> > "blocks" to make sure it is not ignored as much as possible.
> 
> What you call a "new introduction" is notification that draws my attention
> to irrelevant things.
> The summary is my only way to track bugs, including regressions and
> "duplicates" that were resolved and never tested. Earlier I assumed that
> noone is against minor changes in summary made at my discretion. Please
> suggest another way to track real regressions I reported, separately from
> non-regressions.

Maybe use the "Change Columns" in search results page, add the Keyworks, Has Regression Range, etc.

https://blogs.gnome.org/aklapper/2013/06/21/bugzillatips-changecolumns/
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(yfdyh000)
Keywords: ux-consistency
Priority: -- → P3
Whiteboard: [fxsearch]

Unfortunately the bug doesn't contain enough actionable information, I'm not sure about the RIGHT key handling suggested, probably the behavior changed quite a while in years so it doesn't apply to the current version.

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