Closed Bug 326063 Opened 18 years ago Closed 9 days ago

cmd+return doesn't work with about:config in autocomplete window

Categories

(Camino Graveyard :: Location Bar & Autocomplete, defect)

All
macOS
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mozillabugs.3.maxchee, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060203 Camino/1.0rc1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.1) Gecko/20060203 Camino/1.0rc1

under certain conditions.

Reproducible: Always

Steps to Reproduce:
1. go to about.com
2. go to about:config
3. go to google.com
4. type about in the location bar
5. select about:config in the pulldown menu
6. cmd+return

Actual Results:  
about.com is opened in a new tab!

Expected Results:  
about:config should be opened in a new tab

if about:config is typed into the location bar, then cmd+return displays the expected behaviour.
See also bug 316620; this might be the same problem.  

We don't actually autocomplete about:config in the location bar when you select it in the child window, whereas for all other urls we do autocomplete the entire url.
Summary: cmd+return doesn't work with about:config → cmd+return doesn't work with about:config in autocomplete window
We deliberately do not autocomplete about: URLs. (Probably a choice related to the fact that we don't save them in history outside the current session.)

We probably ought not to display them in the autocomplete array, which would solve this problem. Alternatively, we should properly autocomplete but continue not saving them in history.

cl
I agree with t(In reply to comment #2)
> We deliberately do not autocomplete about: URLs. (Probably a choice related to
> the fact that we don't save them in history outside the current session.)
> 
> We probably ought not to display them in the autocomplete array, which would
> solve this problem. Alternatively, we should properly autocomplete but continue
> not saving them in history.
> 
> cl
> 

I agree with the alternative approach.
(In reply to comment #2)
> We probably ought not to display them in the autocomplete array, which would
> solve this problem. Alternatively, we should properly autocomplete but continue
> not saving them in history.

Firefox does the latter, but if the former is simpler (and it seems to me it will be), then we should just do the simplest thing.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Camino1.2
Assignee: mikepinkerton → nobody
QA Contact: location.bar
Target Milestone: Camino1.6 → ---
Due to bug 504688, we're now doing the latter.  Depending on the outcome of that bug, we may just close this one.
Depends on: 504688
Hardware: PowerPC → All
Status: NEW → RESOLVED
Closed: 9 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.