Firefox/Features/Locationbar Domain Highlight: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Once you have created your Feature page, please remove this paragraph and link to your page from the Features Inbox, where a team will triage it and move it in...")
 
No edit summary
Line 9: Line 9:
|-
|-
<section begin="status" />
<section begin="status" />
| [[Highlight the domain name in the location bar]]
| Highlight the domain name in the location bar
| {{StatusHealthy|status=Landed}}
| {{StatusHealthy|status=Landed}}
| 2011-05-05
| 2011-05-05
Line 26: Line 26:


== Release Requirements ==
== Release Requirements ==
Complete checklist of items that need to be satisfied before we can call this feature "done". 


== Next Steps & Open Issues ==
== Next Steps & Open Issues ==
Either the next set of tasks that need to happen to move this project along, or (ideally) the full list of project tasks/action items with things crossed off as they're finished. Including the name of who's responsible for each item, and a rough ETA can be useful.
Highlight the full domain (like Chrome) or only the base domain (like IE, Opera)? We're currently doing the latter. Do we want a pref for this?
 
Open issues include unanswered questions, things that need to be explored, decisions that still need to be made, etc.  Again, including the name of who's responsible for each item can be useful.


== Related Bugs & Dependencies ==
== Related Bugs & Dependencies ==
Links to the feature tracking bug & other relevant bugs; links to related plans (test plan, product marketing plan, etc.); notes about things that depend on this, etc.
{{bug|451833}}


== Risks ==
== Risks ==
Identify, prioritize, track and communicate any risks associated with this feature/project.


== Use Cases ==
== Use Cases ==
Everyone loves use cases, so you should provide them if you can (and where it makes sense).  The [[ChannelSwitching/ChannelSwitchingFeature#Use_Cases|Channel Switcher]] Feature Page has some good examples.


== Test Plans ==
== Test Plans ==
Any and all test plans and strategies.  Either inline or linked to.


== Goals ==
== Goals ==
The high level goals for the feature (which the release requirements checklist should fulfill).  These are the guiding light and overall vision for the feature.  Refer to this if there is confusion or are disputes about direction, designs, planning, etc.


== Non-Goals ==
== Non-Goals ==
Things we are specifically not doing or building as part of this feature.




[[Category:Firefox]]
[[Category:Firefox]]

Revision as of 11:58, 4 May 2011

Once you have created your Feature page, please remove this paragraph and link to your page from the Features Inbox, where a team will triage it and move it into the appropriate Feature list. If you have any questions, please contact Deb.

Feature Status ETA Owner
Highlight the domain name in the location bar Landed 2011-05-05 Dao Gottwald

Summary

Succinct summary of what this feature is all about.

Team

  • Feature Manager: Dao Gottwald
  • Lead Developer: Dao Gottwald

Release Requirements

Next Steps & Open Issues

Highlight the full domain (like Chrome) or only the base domain (like IE, Opera)? We're currently doing the latter. Do we want a pref for this?

Related Bugs & Dependencies

bug 451833

Risks

Use Cases

Test Plans

Goals

Non-Goals