Improve find-in-page
From MozillaWiki
Please use "Edit with form" above to edit this page.
Status
Improve find-in-page | |
Stage | Development |
Status | In progress |
Release target | Firefox 25 |
Health | OK |
Status note | ` |
Team
Product manager | Asa Dotzler |
Directly Responsible Individual | Jennifer Boriss |
Lead engineer | Mike de Boer |
Security lead | Dan Veditz |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | Mihaela Velimiroviciu |
UX lead | Jennifer Boriss |
Product marketing lead | ` |
Operations lead | ` |
Additional members | Markus Stange, Adam [:hobophobe] |
Open issues/risks
Q & A on shifting content (from firefox-dev)
Stage 1: Definition
1. Feature overview
Firefox's find-in-page bar has several usability problems that need to be addressed in a redesign:
Problem with Find-in-page | Solution |
Located at the bottom of the Firefox window, away from all other main functionality. Yet, it's both main functionality and relates to the content on the page. | Should move to the top of the Firefox window, allowing users to easily scan down the page to see results (as they read) rather than having to scan backwards |
Displays globally, on all new tabs, which means that unwanted past searches constantly stick around | Should become tab-specific |
"/" shortcut is too easy to trigger in error in an app where slashes are important | "/" shortcut should be removed |
Only shows one result at a time | Find-in-page should highlight *all* matching results |
Currently difficult to see where find-in-page has located a result | A subtle animation/color change should indicate where results are found |
Doesn't say how many results were found | Should say how many results were found |
Not dismissable with Esc or clicking outside to close | Should be dismissable with Esc or clicking outside to close |
Doesn't have match whole word option | Should have match whole word option |
This feature falls primarily in the Experience category (from the "Discover, Experience, and Connect" vision statement.)
2. Users & use cases
`
3. Dependencies
`
4. Requirements
A working, tested implementation that satisfies the design specification in bug 565552.
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
Related
- Navigation and tab switching should always hide the find bar bug 628179
Stage 5: Release
10. Landing criteria
`
Feature details
Priority | Unprioritized |
Rank | 999 |
Theme / Goal | ` |
Roadmap | User Experience |
Secondary roadmap | ` |
Feature list | Desktop |
Project | ` |
Engineering team | Desktop front-end |
Team status notes
status | notes | |
Products | ` | ` |
Engineering | ` | ` |
Security | ` | ` |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | ` | ` |
User experience | ` | ` |
Product marketing | ` | ` |
Operations | ` | ` |