Closed Bug 1327685 Opened 6 years ago Closed 6 years ago

Autocomplete suggestions of numeric selectors are confusing

Categories

(DevTools :: Inspector, defect)

Product:
DevTools
Component:
Inspector
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox54 affected)

Status:
RESOLVED DUPLICATE of bug 1327037
Tracking Flags:
Tracking Status
firefox54 --- affected

People

(Reporter: arni2033, Unassigned)

Details

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open url   data:text/html,<body id="100"><div id="10">
2. Open inspector
3. In search field in inspector type "#", then type "1", then "0", then "0"

AR:
 In Step 3 autocomplete suggestions change like shown below:
   ["#\31 00", "#\31 0"]  ->  ["#131 00", "#131 0"]  ->  ["#101 00", "#101 0"]  -> ["#100 00"].
     ¯          ¯               ¯¯         ¯¯              ¯¯¯        ¯¯¯            ¯¯¯¯
 Underscores represent what part of suggestion is highlighted as "typed". Suggestions do this actually
 Value "#100 00" is neither what I typed, nor what I get if I press Tab key (I get "#\31 00")
 
ER:  Either X or Y
 X) Autocomplete suggestions should only show human values, just like normal words. They should be:
   ["#100", "#10"]        ->  ["#100", "#10"]        ->  ["#100", "#10"]        ->  ["#100"]
     ¯       ¯                  ¯¯      ¯¯                 ¯¯¯     ¯¯¯                ¯¯¯¯
 Y) Autocomplete suggestions should display real values. They should be:
   ["#\31 00", "#\31 0"]  ->  ["#\31 00", "#\31 0"]  ->  ["#\31 00", "#\31 0"]  ->  ["#\31 00"]
     ¯          ¯               ¯¯¯¯       ¯¯¯¯            ¯¯¯¯ ¯     ¯¯¯¯ ¯          ¯¯¯¯ ¯¯
No longer blocks: 1277113
Tested on Mac OS X 10.10 with FF Nighlty 54.0a1 (2017-01-25) and I can reproduce the behaviour described in the bug.
status-firefox54: --- → affected
Component: Untriaged → Developer Tools: Inspector
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.