Closed Bug 442423 Opened 16 years ago Closed 6 years ago

Location Bar suggestions match comma tag separators

Categories

(Firefox :: Address Bar, defect)

3.0 Branch
defect
Not set
minor

Tracking

()

RESOLVED INACTIVE

People

(Reporter: sublime22091, Unassigned)

Details

(Keywords: polish, Whiteboard: [polish-hard][polish-interactive][polish-p4])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

Entering a comma into the location bar should not match the commas in a tag list.
In other words, the separators should neither be considered tag values nor searched as such.

Reproducible: Always

Steps to Reproduce:
1. Create any bookmark with multiple tags.
2. In location bar, type appropriate keywords to bring aforementioned bookmark into suggestion results.
3. Insert a comma as another search token.
Actual Results:  
Commas in CSV tag lists are matched in results.

Expected Results:  
Commas should only match against page titles or URLs.
It's as simple as typing just ',' by itself into the address bar.  It shows results with the comma separating tag names underlined.  Confirmed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → 3.0 Branch
Whiteboard: [polish-hard][polish-interactive]
This bug's priority relative to the set of other polish bugs is:
P4 - Polish issue that is rarely encountered, and is easily identifiable.

Clearly broken, but I wouldn't imagine that commas are an incredibly common in search terms across all users.
Whiteboard: [polish-hard][polish-interactive] → [polish-hard][polish-interactive][polish-p4]
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.