Closed
Bug 424251
Opened 17 years ago
Closed 17 years ago
pageproxystate set to valid when selecting an autocomplete result
Categories
(Firefox :: Address Bar, defect, P2)
Firefox
Address Bar
Tracking
()
VERIFIED
FIXED
Firefox 3
People
(Reporter: zeniko, Assigned: dao)
References
Details
(Keywords: regression)
Attachments
(1 file, 2 obsolete files)
(deleted),
patch
|
Gavin
:
review+
|
Details | Diff | Splinter Review |
Steps to Reproduce:
1. Enable browser.urlbar.autoFill
2. Start entering h t t ...
Actual result:
As soon as a URL is auto-filled, the current page's favicon is displayed again (opposed to the faded out page indicating non-validated user input).
Expected result:
Don't display any favicon until you hit Go/Enter or Esc (and if a favicon was to be displayed, it should be the one which is also displayed for the auto-filled suggestion, not the currently visible page's).
Updated•17 years ago
|
Flags: in-litmus?
Reporter | ||
Comment 1•17 years ago
|
||
This regressed between the 2008031204 and the 2008031303 builds -> bug 419656.
Blocks: 419656
Keywords: regression
Reporter | ||
Comment 2•17 years ago
|
||
This minimal change would fix it...
Comment 3•17 years ago
|
||
Yup, bug 419656 was the one that added aMustUseURI and uses it.
OS: Windows XP → All
Hardware: PC → All
Reporter | ||
Comment 4•17 years ago
|
||
Comment on attachment 310883 [details] [diff] [review]
minimal fix
Is this the right fix, then?
Attachment #310883 -
Flags: review?(edilee)
Comment 5•17 years ago
|
||
Comment on attachment 310883 [details] [diff] [review]
minimal fix
>+++ browser/base/content/browser.js
>@@ -1991,17 +1991,18 @@ function URLBarSetURI(aURI, aMustUseURI)
>- state = "valid";
>+ if (!aMustUseURI)
>+ state = "valid";
That would fix the issue. Perhaps comment why it shouldn't be valid when forced but is okay when not forced. Potentially someone would want the forced uri to be valid? gavin?
Should we check instead..
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/base/content/browser.js&rev=1.1008&mark=1953,1957,1999#1953
- if (!value || aMustUseURI) {
+ if (!value || aMustUseURI != null)
treating aMustUseURI as a tri-state null(undefined), true, false?
Attachment #310883 -
Flags: review?(gavin.sharp)
Attachment #310883 -
Flags: review?(edilee)
Attachment #310883 -
Flags: review+
Comment 6•17 years ago
|
||
Here's a version if we want to allow the forced uri to cause a valid proxy state.
Attachment #311002 -
Flags: review?(gavin.sharp)
Comment 7•17 years ago
|
||
Hrm, I'm kind of regretting using URLBarSetURI for bug 419656. I was worried about inconsistencies between the various ways we unescape URIs, but maybe misusing URLBarSetURI for setting the value for non-loads is worse.
Assignee | ||
Comment 8•17 years ago
|
||
(In reply to comment #0)
You don't need autofill for this. Just arrow through the list.
(In reply to comment #7)
> I was worried about inconsistencies between the various ways we unescape URIs
That could be solved by letting a helper function do the unescaping.
Assignee | ||
Updated•17 years ago
|
Flags: blocking-firefox3?
Summary: current page's favicon displayed when letting an address starting with a protocol auto-fill → pageproxystate set to valid when selecting an autocomplete result
Assignee | ||
Comment 9•17 years ago
|
||
Updated•17 years ago
|
Attachment #311002 -
Attachment is obsolete: true
Attachment #311002 -
Flags: review?(gavin.sharp)
Updated•17 years ago
|
Attachment #310883 -
Attachment is obsolete: true
Attachment #310883 -
Flags: review?(gavin.sharp)
Comment 10•17 years ago
|
||
Comment on attachment 311121 [details] [diff] [review]
use a helper function
Yeah this is better, thanks!
Attachment #311121 -
Flags: review?(gavin.sharp) → review+
Assignee | ||
Updated•17 years ago
|
Attachment #311121 -
Flags: approval1.9?
Comment 11•17 years ago
|
||
Not a blocker, autofill is a hidden pref that is unsupported.
Flags: blocking-firefox3? → blocking-firefox3-
Assignee | ||
Comment 12•17 years ago
|
||
(In reply to comment #11)
> Not a blocker, autofill is a hidden pref that is unsupported.
see comment 8:
> You don't need autofill for this. Just arrow through the list.
Flags: blocking-firefox3- → blocking-firefox3?
Updated•17 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P2
Target Milestone: --- → Firefox 3
Assignee | ||
Updated•17 years ago
|
Attachment #311121 -
Flags: approval1.9?
Updated•17 years ago
|
Keywords: checkin-needed
Comment 13•17 years ago
|
||
Checking in browser/base/content/browser.js;
/cvsroot/mozilla/browser/base/content/browser.js,v <-- browser.js
new revision: 1.1013; previous revision: 1.1012
done
Checking in browser/base/content/urlbarBindings.xml;
/cvsroot/mozilla/browser/base/content/urlbarBindings.xml,v <-- urlbarBindings.xml
new revision: 1.58; previous revision: 1.57
done
Comment 14•15 years ago
|
||
edited test cases https://litmus.mozilla.org/manage_testcases.cgi?testcase_id=8858 to include this expected behavior.
Status: RESOLVED → VERIFIED
Flags: in-litmus? → in-litmus+
You need to log in
before you can comment on or make changes to this bug.
Description
•