Firefox/Features/URL Autocomplete
Status
Inline URL autocomplete | |
Stage | Landed |
Status | Complete |
Release target | Firefox 14 |
Health | OK |
Status note | Landed in m-c (https://hg.mozilla.org/mozilla-central/rev/953bde82b7a7) backed out for 12, and again for 13 (bug 746572). |
{{#set:Feature name=Inline URL autocomplete
|Feature stage=Landed |Feature status=Complete |Feature version=Firefox 14 |Feature health=OK |Feature status note=Landed in m-c (https://hg.mozilla.org/mozilla-central/rev/953bde82b7a7) backed out for 12, and again for 13 (bug 746572). }}
Team
Product manager | Asa Dotzler |
Directly Responsible Individual | Alex Limi |
Lead engineer | Marco Bonardo |
Security lead | ` |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | Vlad Ghetiu (irc: vladg) |
UX lead | Alex Limi |
Product marketing lead | ` |
Operations lead | ` |
Additional members | ` |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Alex Limi |Feature lead engineer=Marco Bonardo |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Vlad Ghetiu (irc: vladg) |Feature ux lead=Alex Limi |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Enabling autocomplete inline in the URL entry field makes it easier to enter often-typed URLs, and make our browser feel a lot faster, since the user gets immediate feedback on where we think they will go.
We stopped “speaking URL” when AwesomeBar came along, and it makes us seem slower when typing a URL. A large portion of people still "speak URLs" when navigating the internet, and we currently do a bad job at accommodating these people.
We propose to turn on inline autocomplete, with some additional changes that make it stop completion at URL boundaries (e.g. "/").
2. Users & use cases
`
3. Dependencies
`
4. Requirements
A working, tested implementation that satisfies the design specification in bug 566489.
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
Interaction is described in bug 566489.
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
Stage 5: Release
10. Landing criteria
` {{#set:Feature open issues and risks=` |Feature overview=Enabling autocomplete inline in the URL entry field makes it easier to enter often-typed URLs, and make our browser feel a lot faster, since the user gets immediate feedback on where we think they will go.
We stopped “speaking URL” when AwesomeBar came along, and it makes us seem slower when typing a URL. A large portion of people still "speak URLs" when navigating the internet, and we currently do a bad job at accommodating these people.
We propose to turn on inline autocomplete, with some additional changes that make it stop completion at URL boundaries (e.g. "/"). |Feature users and use cases=` |Feature dependencies=` |Feature requirements=A working, tested implementation that satisfies the design specification in bug 566489. |Feature non-goals=` |Feature functional spec=` |Feature ux design=Interaction is described in bug 566489. |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=* bug 566489
|Feature landing criteria=` }}
Feature details
Priority | P2 |
Rank | 999 |
Theme / Goal | Experience |
Roadmap | User Experience |
Secondary roadmap | Firefox Desktop |
Feature list | Desktop |
Project | Responsiveness |
Engineering team | Desktop front-end |
{{#set:Feature priority=P2
|Feature rank=999 |Feature theme=Experience |Feature roadmap=User Experience |Feature secondary roadmap=Firefox Desktop |Feature list=Desktop |Feature project=Responsiveness |Feature engineering team=Desktop front-end }}
Team status notes
status | notes | |
Products | ` | ` |
Engineering | ` | ` |
Security | sec-review-unnecessary | ` |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | Testing in progress | Test Plan |
User experience | OK | Seems to work well, some slight performance issues with the URL bar that may or may not be related to this particular change. |
Product marketing | ` | ` |
Operations | ` | ` |
{{#set:Feature products status=`
|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-unnecessary |Feature security health=OK |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=Testing in progress |Feature qa notes=Test Plan |Feature ux status=OK |Feature ux notes=Seems to work well, some slight performance issues with the URL bar that may or may not be related to this particular change. |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}