Windows8: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 10: Line 10:
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=;Links with info:
|Feature overview=Windows 8 contains to application environments, "Classic" and "Metro".  Classic is very similar to the Windows 7 environment at this time, it requires a simple evolution of the current Firefox Windows product.  Metro is an entirely new environment and requires a new Firefox front end and system integration points.
 
The feature goal here is a new Gecko based browser built for and integrated with the Metro environment.
 
Firefox on Metro, like all other Metro apps will be full screen, focused on touch interactions, and connected to the rest of the Metro environment through Windows 8 contracts.
 
Firefox on Metro will bring all of the Gecko capabilities to this new environment and the assumption is that we'll be able to run as a Medium integrity app so we can access all of the win32 Firefox Gecko libraries avoiding a port to the new WinRT API for the bulk of our code. We will need to have a pan and zoom capability for content.
 
We will need to determine if the Firefox front end on Metro will be built in XUL, C/C++, or HTML/CSS/JS (I'm assuming for now that .Net and XAML are off the table.)
 
Firefox on Metro is a full-screen App with an Appbar that contains common navigation controls (back, reload, etc.,) the Awesomebar, and some form of tabs.
 
Firefox will have three "view" modes -- full screen, 1/6th screen and 5/6th screen depending on how the user "docks" two full screen apps. Our UI will need to adjust
 
We'll also need integration with the share contract, the search contract, the settings contract, the picker contract, the print contract, the play to contract, and possibly a couple more.
 
We may want to offer a live tile with user-centric data like friends presence or other Firefox Home information updates
 
Ideally we'd be able to create secondary tiles for Web-based apps hosted in Firefox's runtime.
 
 
 
;Links with info:


* https://wiki.mozilla.org/Windows_8_Integration
* https://wiki.mozilla.org/Windows_8_Integration

Revision as of 01:54, 15 December 2011

Please use "Edit with form" above to edit this page.

Status

Windows 8 Metro Firefox
Stage Definition
Status In progress
Release target `
Health OK
Status note Placeholder feature page for all requirements to build a Windows 8 Metro-specific Firefox browser.

{{#set:Feature name=Windows 8 Metro Firefox

|Feature stage=Definition |Feature status=In progress |Feature version=` |Feature health=OK |Feature status note=Placeholder feature page for all requirements to build a Windows 8 Metro-specific Firefox browser. }}

Team

Product manager Asa Dotzler
Directly Responsible Individual `
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=Asa Dotzler

|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Windows 8 contains to application environments, "Classic" and "Metro". Classic is very similar to the Windows 7 environment at this time, it requires a simple evolution of the current Firefox Windows product. Metro is an entirely new environment and requires a new Firefox front end and system integration points.

The feature goal here is a new Gecko based browser built for and integrated with the Metro environment.

Firefox on Metro, like all other Metro apps will be full screen, focused on touch interactions, and connected to the rest of the Metro environment through Windows 8 contracts.

Firefox on Metro will bring all of the Gecko capabilities to this new environment and the assumption is that we'll be able to run as a Medium integrity app so we can access all of the win32 Firefox Gecko libraries avoiding a port to the new WinRT API for the bulk of our code. We will need to have a pan and zoom capability for content.

We will need to determine if the Firefox front end on Metro will be built in XUL, C/C++, or HTML/CSS/JS (I'm assuming for now that .Net and XAML are off the table.)

Firefox on Metro is a full-screen App with an Appbar that contains common navigation controls (back, reload, etc.,) the Awesomebar, and some form of tabs.

Firefox will have three "view" modes -- full screen, 1/6th screen and 5/6th screen depending on how the user "docks" two full screen apps. Our UI will need to adjust

We'll also need integration with the share contract, the search contract, the settings contract, the picker contract, the print contract, the play to contract, and possibly a couple more.

We may want to offer a live tile with user-centric data like friends presence or other Firefox Home information updates

Ideally we'd be able to create secondary tiles for Web-based apps hosted in Firefox's runtime.


Links with info

Specific requirements to come shortly.

2. Users & use cases

`

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

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=Windows 8 contains to application environments, "Classic" and "Metro". Classic is very similar to the Windows 7 environment at this time, it requires a simple evolution of the current Firefox Windows product. Metro is an entirely new environment and requires a new Firefox front end and system integration points.

The feature goal here is a new Gecko based browser built for and integrated with the Metro environment.

Firefox on Metro, like all other Metro apps will be full screen, focused on touch interactions, and connected to the rest of the Metro environment through Windows 8 contracts.

Firefox on Metro will bring all of the Gecko capabilities to this new environment and the assumption is that we'll be able to run as a Medium integrity app so we can access all of the win32 Firefox Gecko libraries avoiding a port to the new WinRT API for the bulk of our code. We will need to have a pan and zoom capability for content.

We will need to determine if the Firefox front end on Metro will be built in XUL, C/C++, or HTML/CSS/JS (I'm assuming for now that .Net and XAML are off the table.)

Firefox on Metro is a full-screen App with an Appbar that contains common navigation controls (back, reload, etc.,) the Awesomebar, and some form of tabs.

Firefox will have three "view" modes -- full screen, 1/6th screen and 5/6th screen depending on how the user "docks" two full screen apps. Our UI will need to adjust

We'll also need integration with the share contract, the search contract, the settings contract, the picker contract, the print contract, the play to contract, and possibly a couple more.

We may want to offer a live tile with user-centric data like friends presence or other Firefox Home information updates

Ideally we'd be able to create secondary tiles for Web-based apps hosted in Firefox's runtime.


Links with info

Specific requirements to come shortly. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority P1
Rank 12
Theme / Goal `
Roadmap Firefox Desktop
Secondary roadmap `
Feature list Desktop
Project `
Engineering team `

{{#set:Feature priority=P1

|Feature rank=12 |Feature theme=` |Feature roadmap=Firefox Desktop |Feature secondary roadmap=` |Feature list=Desktop |Feature project=` |Feature engineering team=` }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}