URL bar autocomplete should be case-insensitive

RESOLVED WORKSFORME

Status

--
enhancement
RESOLVED WORKSFORME
17 years ago
7 years ago

People

(Reporter: mudi, Assigned: ajschult784)

Tracking

(Blocks: 1 bug)

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
This might be by design but I think case insensitivity would be a conviniece...
(not only for for the domain part)

Comment 1

17 years ago
As some URL parts could be case sensitive (path, parameter values etc.), this
bug report should be resolved as WONTFIX. 
Whiteboard: WONTFIX

Comment 2

17 years ago
I'm going out on a limb here and marking WONTFIX myself.
This would clearly break many many sites.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX

Comment 3

17 years ago
Reopening. By the HTTP 1.1 specification, 3.2.3 "URI Comparison",
<http://ietf.org/rfc/rfc2616.txt>:

| When comparing two URIs to decide if they match or not, a client
| SHOULD use a case-sensitive octet-by-octet comparison of the entire
| URIs, with these exceptions:
[then is listed four exceptions none of which are relevant here]

That clearly states that URIs are case sensitive; thus they should be treated
case sensitively when determining whether a link is visited or not. However, I
fail to see why the autocomplete dropdown in the URL bar should also be case
sensitive; listing matches which are identical except for case would not break
any sites.

wd, aha, do you disagree?
Severity: minor → enhancement
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---

Comment 4

17 years ago
While that doesn't sound like what the author asked for, I think that's a good idea.

Comment 5

17 years ago
Mudi: Could you agree with change of summary to 'Autocomplete should be case
insensitive'?
OS: Windows 2000 → All
Hardware: PC → All
(Reporter)

Comment 6

17 years ago
Sorry for causing confusion. I actually meant the url autocompletion matching
(and not matching against memory or disk cache). This autocompletion is a UI
convinience, I think the HTTP RFC shouldn't apply.

Comment 7

17 years ago
Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: url bar is case sensitive → URL bar autocomplete should be case-insensitive
Whiteboard: WONTFIX

Comment 8

17 years ago

*** This bug has been marked as a duplicate of 38998 ***
Status: NEW → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → DUPLICATE

Comment 9

17 years ago
what was I thinking?
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---

Updated

15 years ago
Blocks: 221040
Component: Location Bar → XP Apps: GUI Features
Product: Core → Mozilla Application Suite
(Assignee)

Comment 10

13 years ago
bug 233229 needs to be fixed first so that best-match-as-you-type still works
Assignee: hewitt → ajschult
Status: REOPENED → NEW
Component: XP Apps: GUI Features → Location Bar
Depends on: 233229
Product: Mozilla Application Suite → Core
(Assignee)

Comment 11

13 years ago
Created attachment 205934 [details] [diff] [review]
patch

I had to make autocomplete autofill fully case insensitive too so that it would notice the match.  I'm not sure why it wasn't case insensitive before.
Attachment #205934 - Flags: review?(jag)
Product: Core → SeaMonkey
QA Contact: claudius → location-bar

Comment 12

7 years ago
WORKSFORME Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111215 SeaMonkey/2.8a1
Probably due to using the smart location bar code nowadays.

Comment 13

7 years ago
Really close as WORKSFORME
Status: NEW → RESOLVED
Last Resolved: 17 years ago7 years ago
Resolution: --- → WORKSFORME

Comment 14

7 years ago
Comment on attachment 205934 [details] [diff] [review]
patch

Cancelling review request for obsolete bug.
Attachment #205934 - Flags: review?(jag-mozilla)
You need to log in before you can comment on or make changes to this bug.