152016 - URL bar autocomplete should be case-insensitive

Status: RESOLVED WORKSFORME

(SeaMonkey :: Location Bar, enhancement)

Description

[Mudi Obada]

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

Comment 1

[Adam Hauner]

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

Comment 2

[WD]

I'm going out on a limb here and marking WONTFIX myself.
This would clearly break many many sites.

Comment 3

[Jonas Jørgensen]

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?

Comment 4

[alanjstr]

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

Comment 5

[Adam Hauner]

Mudi: Could you agree with change of summary to 'Autocomplete should be case
insensitive'?

Comment 6

[Mudi Obada]

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

[Jonas Jørgensen]

Confirming.

Comment 8

[Daniel Wang]

*** This bug has been marked as a duplicate of 38998 ***

Comment 9

[Daniel Wang]

what was I thinking?

Comment 10

[Andrew Schultz]

bug 233229 needs to be fixed first so that best-match-as-you-type still works

Comment 11

[Andrew Schultz]

Attachment: 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.

Comment 12

[Philip Chee]

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

[Philip Chee]

Really close as WORKSFORME

Comment 14

[Philip Chee]

Comment on attachment 205934 [details] [diff] [review]
patch

Cancelling review request for obsolete bug.