MozillaWiki - User contributions [en]

Modules/Desktop Firefox

2021-11-22T20:04:17Z

Sfoster: Added Form Autofill new owner tgiles, and peers sgalich and dlee

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lina@mozilla.com Lina Cambridge], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert],
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:mhowell@mozilla.com Molly Howell], [mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:htwyford@mozilla.com Harry Twyford], [mailto:itiel_yn8@walla.com Itiel]
|peersemeritus=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:mtigley@mozilla.com Micah Tigley]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=[mailto:tgiles@mozilla.com Tim Giles]
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=[mailto:sgalich@mozilla.com Sergey Galich], [mailto:dlee@mozilla.com Dimi Lee]
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:aoprea@mozilla.com Andrei Oprea]
|peers=[mailto:najiang@mozilla.com Nan Jiang], [mailto:pdahiya@mozilla.com Punam Dahiya], [mailto:edilee@mozilla.com Ed Lee], [mailto:khudson@mozilla.com Kate Hudson],
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:tkikuchi@mozilla.com Toshihito Kikuchi]
|ownersemeritus=Aaron Klotz
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:aoprea@mozilla.com Andrei Oprea], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/uitour/
|url=
|components=Firefox::Tours
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:sgalich@mozilla.com Sergey Galich]
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=[mailto:sfoster@mozilla.com Sam Foster], [mailto:jwein@mozilla.com Jared Wein], [mailto:tgiles@mozilla.com Tim Giles], [mailto:dlee@mozilla.com Dimi Lee]
|peersemeritus=[mailto:bdanforth@mozilla.com Bianca Danforth], [mailto:srudie@mozilla.com Severin Rudie]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peersemeritus=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Screenshots
|description=Code relating to Screenshots functionality
|owner=[mailto:sfoster@mozilla.com Sam Foster]
|peers=[mailto:jhirsch@mozilla.com Jared Hirsch], [mailto:nbaumgardner@mozilla.com Niklas Baumgardner],
|peersemeritus=[mailto:bchen@mozilla.com Barry Chen]
|ownersemeritus=[mailto:emmamalysz@gmail.com Emma Malysz], [mailto:ian@ianbicking.org Ian Bicking]
|source_dirs=browser/extensions/screenshots, browser/components/screenshots/
|components=Firefox::Screenshots
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:htwyford@mozilla.com Harry Twyford]
|peersemeritus=[mailto:info@mikedeboer.nl Michael de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:pbz@mozilla.com Paul Zühlcke]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:prathiksha@mozilla.com Prathiksha]
|peersemeritus=[mailto:ewright@mozilla.com Erica Wright]
|ownersemeritus=[mailto:jhofmann@mozilla.com Johann Hofmann]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:dao@mozilla.com Dão Gottwald], [mailto:dharvey@mozilla.com Dale Harvey]
|peers=[mailto:afarre@mozilla.com Andreas Farre], [mailto:anny@mozilla.com Anny Gakhokidze]
|ownersemeritus=[mailto:info@mikedeboer.nl Michael de Boer], Kashav Madan
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=Firefox::Session Restore
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Modules/Desktop Firefox

2021-11-22T20:00:21Z

Sfoster: Moved Password Manager owner from sfoster to peer, new owner is sgalich

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lina@mozilla.com Lina Cambridge], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert],
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:mhowell@mozilla.com Molly Howell], [mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:htwyford@mozilla.com Harry Twyford], [mailto:itiel_yn8@walla.com Itiel]
|peersemeritus=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:mtigley@mozilla.com Micah Tigley]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:aoprea@mozilla.com Andrei Oprea]
|peers=[mailto:najiang@mozilla.com Nan Jiang], [mailto:pdahiya@mozilla.com Punam Dahiya], [mailto:edilee@mozilla.com Ed Lee], [mailto:khudson@mozilla.com Kate Hudson],
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:tkikuchi@mozilla.com Toshihito Kikuchi]
|ownersemeritus=Aaron Klotz
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:aoprea@mozilla.com Andrei Oprea], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/uitour/
|url=
|components=Firefox::Tours
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:sgalich@mozilla.com Sergey Galich]
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=[mailto:sfoster@mozilla.com Sam Foster], [mailto:jwein@mozilla.com Jared Wein], [mailto:tgiles@mozilla.com Tim Giles], [mailto:dlee@mozilla.com Dimi Lee]
|peersemeritus=[mailto:bdanforth@mozilla.com Bianca Danforth], [mailto:srudie@mozilla.com Severin Rudie]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peersemeritus=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Screenshots
|description=Code relating to Screenshots functionality
|owner=[mailto:sfoster@mozilla.com Sam Foster]
|peers=[mailto:jhirsch@mozilla.com Jared Hirsch], [mailto:nbaumgardner@mozilla.com Niklas Baumgardner],
|peersemeritus=[mailto:bchen@mozilla.com Barry Chen]
|ownersemeritus=[mailto:emmamalysz@gmail.com Emma Malysz], [mailto:ian@ianbicking.org Ian Bicking]
|source_dirs=browser/extensions/screenshots, browser/components/screenshots/
|components=Firefox::Screenshots
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:htwyford@mozilla.com Harry Twyford]
|peersemeritus=[mailto:info@mikedeboer.nl Michael de Boer]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:pbz@mozilla.com Paul Zühlcke]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:prathiksha@mozilla.com Prathiksha]
|peersemeritus=[mailto:ewright@mozilla.com Erica Wright]
|ownersemeritus=[mailto:jhofmann@mozilla.com Johann Hofmann]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:dao@mozilla.com Dão Gottwald], [mailto:dharvey@mozilla.com Dale Harvey]
|peers=[mailto:afarre@mozilla.com Andreas Farre], [mailto:anny@mozilla.com Anny Gakhokidze]
|ownersemeritus=[mailto:info@mikedeboer.nl Michael de Boer], Kashav Madan
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=Firefox::Session Restore
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Modules/Desktop Firefox

2021-02-12T18:41:07Z

Sfoster: Updating Password Manager peers

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
Owners and peers of the Desktop Firefox module may review code anywhere in the browser and toolkit directories. Reviews should be sent to the more specific submodules below where possible.

{{Module
|name=Desktop Firefox
|description=Standalone Web Browser.
|owner=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|fallbackpeers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:jwein@mozilla.com Jared Wein], [mailto:jhofmann@mozilla.com Johann Hofmann], [mailto:lina@mozilla.com Lina Cambridge], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|ownersemeritus=
|peersemeritus=[mailto:netzen@gmail.com Brian Bondy], [mailto:lchang@mozilla.com Luke Chang], [mailto:rchien@mozilla.com Ricky Chien], [mailto:dolske@mozilla.com Justin Dolske], [mailto:georg.fritzsche@googlemail.com Georg Fritzsche], [mailto:felipc@gmail.com Felipe Gomes], [mailto:tchien@mozilla.com Tim Guan-tin Chien], [mailto:rexboy@mozilla.com KM Lee Rex], [mailto:gasolin@mozilla.com Fred Lin], [mailto:ralin@mozilla.com Ray Lin], [mailto:fliu@mozilla.com Fischer Liu], [mailto:wmccloskey@mozilla.com Bill McCloskey], [mailto:mark@moxienet.com Mark Mentovai], [mailto:ted.mielczarek@gmail.com Ted Mielczarek], [mailto:bnicholson@mozilla.com Brian Nicholson], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:mano@mozilla.com Asaf Romano], [mailto:msamuel@mozilla.com Marina Samuel], [mailto:jryans@gmail.com J Ryan Stinnett], [mailto:gps@mozilla.com Gregory Szorc], [mailto:ttaubert@mozilla.com Tim Taubert]
|group=firefox-dev
|source_dirs=browser/, toolkit/
|url=[[Firefox/Code_Review|Code Review Guidelines]]
|components=Firefox, Toolkit
}}

== Submodules ==

{{Module
|name=Add-ons Manager
|description=Extension management back-end.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan], [mailto:kmaglione@mozilla.com Kris Maglione]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:jmathies@mozilla.com Jim Mathies], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/
|url=
|components=
}}

{{Module
|name=Add-ons Manager UI
|description=about:addons.
|owner=[mailto:scaraveo@mozilla.com Shane Caraveo], [mailto:mstriemer@mozilla.com Mark Striemer]
|ownersemeritus=[mailto:rstrong@mozilla.com Robert Strong], [mailto:aswan@mozilla.com Andrew Swan]
|peers=[mailto:lgreco@mozilla.com Luca Greco], [mailto:tjovanovic@mozilla.com Tomislav Jovanovic], [mailto:rwu@mozilla.com Rob Wu]
|source_dirs=toolkit/mozapps/extensions/content/
|url=
|components=
}}

{{Module
|name=Application Update
|description=The application update services.
|owner=[mailto:ksteuber@mozilla.com Kirk Steuber]
|peers=[mailto:mhowell@mozilla.com Molly Howell], [mailto:agashlin@mozilla.com Adam Gashlin]
|source_dirs=toolkit/mozapps/update/
|url=
|components=
}}

{{Module
|name=Bookmarks & History
|description=The bookmarks and history services (Places).
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:lina@mozilla.com Lina Cambridge], [mailto:standard8@mozilla.com Mark Banner], [mailto:adw@mozilla.com Drew Willcoxon]
|source_dirs=browser/components/places/, toolkit/components/places/
|url=
|components=
}}

{{Module
|name=Desktop Theme
|description=The style rules used in the desktop UI.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=[mailto:ntim.bugs@gmail.com Tim Nguyen]
|source_dirs=browser/themes/, toolkit/themes/
|url=
|components=Firefox::Theme, Toolkit::Themes
}}

{{Module
|name=Desktop UI
|description=The main browser UI except where covered by more specific submodules.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mconley@mozilla.com Mike Conley], [mailto:florian@queze.net Florian Quèze]
|source_dirs=browser/base/content/
|url=
|components=
}}

{{Module
|name=Download Manager
|description=The downloads UI and service.
|owner=[mailto:mbonardo@mozilla.com Marco Bonardo]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch]
|source_dirs=browser/components/downloads/, toolkit/mozapps/downloads/
|url=
|components=
}}

{{Module
|name=Enterprise Policies
|description=System policies for controlling Firefox.
|owner=[mailto:mkaply@mozilla.com Michael Kaply]
|peers=
|source_dirs=browser/components/enterprisepolicies/
|url=
|components=
}}

{{Module
|name=Form Autofill
|description=Form detection and autocomplete.
|owner=
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=
|source_dirs=browser/extensions/formautofill/, toolkit/components/satchel/
|url=
|components=
}}

{{Module
|name=In-product Messaging
|description=The system for delivering in-product messaging.
|owner=[mailto:aoprea@mozilla.com Andrei Oprea]
|peers=[mailto:najiang@mozilla.com Nan Jiang], [mailto:pdahiya@mozilla.com Punam Dahiya], [mailto:edilee@mozilla.com Ed Lee], [mailto:khudson@mozilla.com Kate Hudson],
|source_dirs=toolkit/components/messaging-system/
|url=
|components=Firefox::Messaging System
}}

{{Module
|name=Launcher Process
|description=Windows process for bootstrapping the browser process.
|owner=[mailto:aklotz@mozilla.com Aaron Klotz]
|peers=[mailto:mhowell@mozilla.com Molly Howell]
|source_dirs=browser/app/winlauncher
|url=
|components=Firefox::Launcher Process
}}

{{Module
|name=New Tab Page
|description=The new tab/home page.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:khudson@mozilla.com Kate Hudson], [mailto:aoprea@mozilla.com Andrei Oprea], [mailto:sdowne@getpocket.com Scott Downe]
|source_dirs=browser/components/newtab/
|url=
|components=Firefox::New Tab Page
}}

{{Module
|name=Normandy
|description=The experiments and off-train deployments system.
|owner=[mailto:mcooper@mozilla.com Michael Cooper]
|peers=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=toolkit/components/normandy/
|url=
|components=Firefox::Normandy
}}

{{Module
|name=Onboarding
|description=The onboarding experience including UI tours.
|owner=[mailto:elee@mozilla.com Ed Lee]
|peers=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/uitour/
|url=
|components=Firefox::Tours
}}

{{Module
|name=Password Manager
|description=Managing, saving and filling logins.
|owner=[mailto:sfoster@mozilla.com Sam Foster]
|ownersemeritus=[mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|peers=[mailto:jwein@mozilla.com Jared Wein], [mailto:tgiles@mozilla.com Tim Giles], [mailto:dlee@mozilla.com Dimi Lee]
|peersemeritus=[mailto:bdanforth@mozilla.com Bianca Danforth], [mailto:srudie@mozilla.com Severin Rudie]
|source_dirs=toolkit/components/passwordmgr/, browser/components/aboutlogins
|url=https://wiki.mozilla.org/Toolkit:Password_Manager
|components=Toolkit::Password Manager, Toolkit::Password Manager: Site Compatibility, Firefox::about:logins
}}

{{Module
|name=Preferences
|description=The front-end preferences system.
|owner=[mailto:jwein@mozilla.com Jared Wein]
|peers=[mailto:mstriemer@mozilla.com Mark Striemer], [mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|source_dirs=browser/components/preferences/, browser/themes/*/preferences, toolkit/mozapps/preferences
|url=
|components=
}}

{{Module
|name=Profile Migration
|description=Migrating data from other browsers.
|owner=[mailto:gkruitbosch@mozilla.com Gijs Kruitbosch]
|peers=[mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:mozilla@noorenberghe.ca Matthew Noorenberghe]
|source_dirs=browser/components/migration/
|url=
|components=
}}

{{Module
|name=Search and Address Bar
|description=The search service, address bar and address bar autocomplete.
|owner=[mailto:standard8@mozilla.com Mark Banner], [mailto:dwillcoxon@mozilla.com Drew Willcoxon]
|peers=[mailto:dharvey@mozilla.com Dale Harvey], [mailto:mbonardo@mozilla.com Marco Bonardo], [mailto:dao@mozilla.com Dão Gottwald], [mailto:mdeboer@mozilla.com Mike de Boer], [mailto:htwyford@mozilla.com Harry Twyford]
|source_dirs=browser/components/search/, browser/components/urlbar/, toolkit/components/search/
|url=
|components=Firefox::Address Bar, Firefox::Search
}}

{{Module
|name=Security and Privacy UI
|description=The front-end to our security and privacy features, including Protections UI, Site Identity, Site Permissions and Certificate Errors
|owner=[mailto:jhofmann@mozilla.com Johann Hofmann]
|peers=[mailto:nhnt11@mozilla.com Nihanth Subramanya], [mailto:ewright@mozilla.com Erica Wright], [mailto:pbz@mozilla.com Paul Zühlcke], [mailto:prathiksha@mozilla.com Prathiksha]
|source_dirs=browser/components/protections/, browser/components/controlcenter/
|url=
|components=Firefox::Security, Firefox::Protections UI, Firefox::Site Identity, Firefox::Site Permissions
}}

{{Module
|name=Session Restore
|description=Restoring a user's session after starting Firefox.
|owner=[mailto:mdeboer@mozilla.com Michael de Boer]
|peers=[mailto:dao@mozilla.com Dão Gottwald], [mailto:alchen@mozilla.com Alphan Chen]
|source_dirs=browser/components/sessionstore/, toolkit/components/sessionstore/
|url=
|components=
}}

{{Module
|name=Tabbed Browser
|description=The UI component controlling browser tabs.
|owner=[mailto:dgottwald@mozilla.com Dão Gottwald]
|peers=
|source_dirs=browser/base/content/tabbrowser*, browser/modules/AsyncTabSwitcher.jsm
|url=
|components=Firefox::Tabbed Browser
}}

{{Module
|name=Windows Installer
|description=The installer for Windows.
|owner=[mailto:mhowell@mozilla.com Molly Howell]
|peers=[mailto:agashlin@mozilla.com Adam Gashlin], [mailto:nalexander@mozilla.com Nick Alexander]
|source_dirs=browser/installer/, toolkit/mozapps/installer/
|url=
|components=Firefox::Installer
}}

Firefox/SVG Asset Optimization

2019-07-16T18:56:40Z

Sfoster: Initial notes on svg optimization of the film-strip style svg animations

This page is about the production and optimization of SVG assets for use in Firefox UI.

== Background ==

The SVG output from most drawing applications requires optimization before it can be committed to mozilla-central. As SVG is a text format, SVG files are subject to code review, and need to be readable and file-size kept to a reasonable minimum.

== Film-strip Animations ==

Many of the new UI animations added in Firefox 57 ("Quantum") used a "film strip" technique to get pre-rendered, 60fps animation that could run entirely on the compositor and off the main thread. These SVG files were typically a horizontal strip of frames, each frame offset on the x-axis by frame index * frame width. To play the animation, the CSS transform property is updated to translateX to a value that places the current frame at 0,0 in a cropped element. This technique is [http://msuja.ws/svg.html explained and illustrated here].

There are many ways to create and optimize the output assets for these animations. The toolchain we used was a mix of existing tools and custom scripts and processes:

== Asset preparation process ==

The framing and motion design was done in After Effects, and exported using the BodyMovin plugin to a SVG-as-json format.

This [https://sfoster.github.io/svgspritesheet/ JSON-SVG] tool imports the data exported by BodyMovin, creates a SVG document and plays the animation in order to generate the static frames. The output can be saved from the browser.

[https://github.com/svg/svgo SVGO] was used to optimize these rather bloaty documents down to a more appropriate size. SVGO uses a plugin architecture to string together a series of optimization steps, based on a config file. The goal is to:

* Eliminate any proprietary markup, vendor metadata, comments
* Simplify DOM - eliminating unnecessary and hidden elements and flattening out nested structures
* Convert shapes and pre-apply and consolidate transforms to paths

[https://github.com/svg/svgo SVGO] is a generic optimization tool. Which plugins to use and the order to apply them depends on the specific input given and desired output. What works for one image may not for another - this is not a push-button-get-result kind of operation. Each image or animation will likely need config tweaks, possible manual post-processing and careful preview to ensure detail isn't lost in the optimization. For the filmstrip images and this workflow there are specific considerations:

* Remove moz-select attributes that are added when saving from the browser
* Replace specific color values with context-fill and context-stroke. See [https://sfoster.github.io/svgspritesheet/preview-context-colors.html this tool] for help picking colors to substitute and previewing the result
* Add the mozilla license
* De-duplicate repeated paths. These animations frequently involve many frames which move a entire shape, or transform the color of a shape and we can use a path and use href to define and reference these paths once rather than inlining these long paths in every frame.

Some of these steps are trivial to perform manually (like adding the license), or search/replace to swap out designated colors for context-fill/context-stroke. The path de-duplication is amenable to scripting if the need arises. There are a couple of possibly-useful plugins in a [https://github.com/sfoster/svgo/ fork of the SVGO repo]. The repo includes a[https://github.com/sfoster/svgo/blob/master/photon.default.config sample config file]. Usage like so:

./bin/svgo --config=your.config --input=/path/to/file.svg --output=/path/to/optimizes/file.svg

Community:SummerOfCode19:Brainstorming

2019-01-28T17:08:08Z

Sfoster: /* Add Firefox Tab Manager proposal */

Once again, Mozilla intends to apply to participate in Google's Summer Of Code.

Mozilla community members, please submit proposals here for 2019 Google Summer of Code projects with Mozilla. This page is for brainstorming - as we approach the deadline, those ideas that are accepted will be transferred to the [[Community:SummerOfCode19|official list]].)

Our application for summer of 2019 goes into Google on '''February 4th''', so get those project ideas in well ahead of time.

Are you a student looking to apply to GSoC with Mozilla? Your first stop should be the [[Community:SummerOfCode19|official list of ideas]]. This page is full of weird ideas, only some of which will make the cut. It could be that they are not properly defined, the wrong size, or don't have a mentor. That makes them less likely to get accepted. You can, of course, also submit your own ideas - you don't have to put an idea on this page and get it 'made official' in order to send in a proposal for it.

==How To Write A Good Project Proposal==

Before adding an proposal to this list, please consider the following:

* '''Be specific'''. It's hard to understand the impact of, or the size of, vague proposals.
* '''Consider size'''. The student has eight weeks to design, code, test and document the proposal. It needs to fill, but not overfill, that time.
* '''Do your research'''. Support the idea with well-researched links.
* '''Don't morph other people's ideas'''. If you have a related idea, place it next to the existing one, or add a comment.
* '''Insert only your own name into the Mentor column''', and then only if you are willing to take on the responsibility. If you think the SoC admins won't know who you are, leave contact details.
* '''Check back regularly'''. The administrators may have questions about your idea that you will need to answer.
* '''Know when to give up'''. If you've added the same idea for the last three years and it hasn't made it to the official page, perhaps you can predict what will happen this time.

==Suggestion List==

[[SummerOfCode|Here are the ideas lists from previous years]].

Proposals can be in almost any part of the Mozilla project, though they do need to be mostly focused on code. If there is no category below for your corner of Mozilla, add one!

Here is the template for adding project proposals. Feel free to add new proposal to existing general categories, or add new categories as appropriate.

== 2019 Proposed Project List ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Additional Comments
|-
| Improve Python in the browser
| The [https://github.com/iodide-project/pyodide pyodide] project allows the Python scientific stack to run in the browser by compiling it to WebAssembly. Help make stuff run better and faster there.
| Python and JavaScript. Can learn the WebAssembly parts as you go.
| [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]
| [https://mozillians.org/en-US/u/mdboom/ Michael Droettboom]
| There are a number of specific projects we have in mind, but are open to other proposals that are within scope and seem practical within the timeframe. (1) Implement matplotlib's display on top of Web APIs (HTML5 Canvas, etc.) This would allow us to avoid shipping a whole separate rendering engine to the browser. (2) Build WebAssembly support into the conda packaging system to make it easier to distribute new compiled packages for Pyodide. (3) Make multi-dimensional arrays sharable between Python and Javascript. See Pyodide's [https://github.com/iodide-project/pyodide/issues list of issues] for additional ideas. About the mentor: Michael Droettboom is a Staff Data Engineer at Mozilla, and a former lead developer of matplotlib with years of experience building the Python scientific ecosystem.
|-
| ReSpec
| [https://github.com/w3c/respec/ ReSpec] is a JS-based tool used to write W3C Specifications (Web Standards) that is widely used by the Web Standards Community. With 6+ years of development, it's heavily depended upon by the W3C community at large (of which Mozilla is an active participant). ReSpec's code is in need of some modernization, optimizations, and bug fixes - and we could use your help! In this project, you would have the opportunity to make ReSpec's UI more accessible, making it leaner and faster using distributed processing with Web Workers, and/or adding new features to make the lives of W3C spec Editor's better.
| JavaScript, HTML, CSS.
| [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]
| [https://mozillians.org/en-US/u/mcaceres/ Marcos Caceres]
| ReSpec offers students the opportunity to work on a large code base that has extensive real world use and impact. The project offers students an extensive range of problems to tackle, from UI design, to concurrent processing (using Web Workers to do distributed text processing), dealing with accessibility and internationalization, writing and learning about unit and integration tests, security, code review, etc. - as well as exposure to the W3C and the web standards community, this project also aims at teaching students about how web standards are put together. To determine if this is a project you would like to be part of, see the [https://github.com/w3c/respec/issues/ list of issues] you could work on. It's a great opportunity to learn about all aspects of open source software development, but with the freedom to take on small to large challenges over the Summer (depending on your skill level and level of confidence). About the mentor: Marcos Caceres is a Staff Engineer at Mozilla who has been working on Web Standards for over a decade. Marcos is the lead maintainer of ReSpec. Marcos has extensive experience mentoring developers and has previously successfully mentor a GSO student.
|-
| Ship Public Suffix List (PSL) over Remote Settings
| The list of public domain suffixes (DNS) is shipped with every release, with no way to update it on long term releases for example.
Now that Remote Settings has become a solid solution to ship data, we could use it to publish updates of the PSL.
The task consist in migrating the current client code to read from Remote Settings instead of a file, and implement a scheduled job (like Python) to push updates automatically (most likely compiled as a DAFSA file)
| JavaScript and some Python basics
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]
| [https://mozillians.org/en-US/u/leplatrem/ Mathieu Leplatre]
| https://bugzilla.mozilla.org/show_bug.cgi?id=1083971
|-
| Support AdBlock Plus-style ad blocklists
| As of today, Gecko and GeckoView support ad blocking using a custom JSON format for blocklists and entitylists. The current blocklist format lacks regex pattern matching and the ability to block only images, scripts, or other specific resources from a page. The Fenix project would like first party support for the industry-standard blocklists used by other ad blockers, so we can benefit from the work of community-updated blocklists with our own custom ad blocking solution.
| C++?
| [https://mozillians.org/en-US/u/colee/ Colin Lee]
| Seeking a mentor
| https://bugzilla.mozilla.org/show_bug.cgi?id=1519197
|-
| [https://github.com/marco-c/bugbug bugbug]
| A platform for machine learning projects applied on Bugzilla, VCS and other software development data.
| Python
| [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)
| [https://github.com/marco-c Marco Castelluccio] (FIRST_NAME@mozilla.com)
| The project will involve one or more of:
i) building additional classifiers (e.g., to detect bugs with no steps to reproduce, or to suggest a developer to assign to a bug, and so on);

ii) improving accuracy/precision/recall of the existing classifiers by implementing other machine learning techniques (e.g., by using convolutional neural networks or recurrent neural networks);

iii) improving accuracy/precision/recall by implementing additional feature extraction steps or making the already existing ones better.
|-
| Make the Firefox WebAuthn Soft Token a Real Thing
| The Web Authentication Soft Token provides second-factor login support without needing a Security Key dongle. It would be very usable if the Soft Token were a) synchronized across an account using Sync, b) could be controlled via a Web Extension, and perhaps c) had some UI. If these things were true, most people could get quality authentication support without buying another device.
| C++, Javascript, Basic cryptography
| [https://mozillians.org/en-US/u/jcjones/ J.C. Jones]
| [https://mozillians.org/en-US/u/jcjones/ J.C. Jones]
| https://wiki.mozilla.org/Security/CryptoEngineering#Web_Authentication
|-
| WebSocket Monitor
| Support for WebSocket monitoring and inspection in Firefox DevTools.
| JavaScript/React
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]
| [https://mozillians.org/en-US/u/odvarko/ Jan Odvarko]
| This project aims at providing support for WebSocket monitoring and inspection in Firefox DevTools. The feature should be built on top of the existing Network panel UI and responsible for visualizing data sent through WebSocket connection (i.e. WS frames). The user should be able to use the UI to see as well as analyse the data (search, filter, etc.).
* [https://docs.google.com/document/d/1ruHk-BA3cqzU7VHoVltnAwWt_2OXKOOAI4nTHwYllzk/edit# Detailed Project Description]
|-
| Helpful crash reporter
| The crash reporter only allows users to send crash reports but in some cases it might help the user diagnose the crash and solve it on his/her own
| C++, Javascript
| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto]
| [https://mozillians.org/en-US/u/gsvelto/ Gabriele Svelto]
| There's a few things that could be implemented:
* A quick test of the memory owned by the crashed process (such as those in [http://www.memtest.org/ memtest86+]) might catch faulty memory, a common cause for crashes
* The crash reporter client might try and validate Firefox files which can sometimes become corrupted (usually because of hardware issues). If they are it can prompt the user to re-install Firefox
* Many crashes are caused by buggy graphics drivers, while we blacklist the most egregious offenders we can't cover them all. The crash reporter might identify a faulty driver (if a bug for it has already been filed) and point the user to up-to-date drivers
* For crashes caused by known bugs it should be possible to point the user to the bug filed on bugzilla
|-
| Debugger Inline Variable Preview
| When the Firefox DevTools debugger is paused, users can hover over variables to get a useful tooltip that details the variable's value at that time. While this popup is very informative, one valuable enhancement would be displaying relevant contextual variables values alongside the variable inline, alleviating the need for tooltips and allowing the user to more quickly get the information they need. The applicant will work alongside the Debugger's team to implement this feature based on UX mockups and be given space to share and implement ideas of their own.
| Javascript
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh]
| [https://mozillians.org/en-US/u/davidwalsh/ David Walsh]
|
|-
| GitHub Checks Support Improvements
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports reporting results to the [https://github.com/taskcluster/taskcluster/pull/129/checks?check_run_id=54327344 GitHub Checks API], but only reports success or failure. Let's add support for showing [https://developer.github.com/v3/checks/runs/ annotations] - snippets of log output, more detailed results, images, and so on. We can even add support for additional "actions" on the task, such as re-running with debugging enabled.
| Server-side JS
| [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell]
| [https://mozillians.org/en-US/u/ireneOwl/ Irene Storozhko], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell]
|
|-
| Support GitHub Logins in Taskcluster
| [https://github.com/taskcluster/taskcluster Taskcluster] currently supports logging in with Auth0, the Mozilla login system. We would like to make it useful outside of Mozilla, and most other users do their development on GitHub, making GitHub logins a good solution. This project would involve adding support for signing in with GitHub, as well as the more challenging task of assigning appropriate permissions to users based on the setup of their GitHub account.
| Server-side JS
| [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell]
| [https://mozillians.org/en-US/u/ireneOwl/ Irene Storozhko], [https://mozillians.org/en-US/u/djmitche/ Dustin Mitchell]
|
|-
| Improve Webdriver support in Servo
| [https://github.com/servo/servo/ Servo] currently supports a minimal subset of the [https://w3c.github.io/webdriver/ Webdriver standard]. We would like to improve Servo's support, and verify its correctness by passing a [https://github.com/web-platform-tests/wpt/tree/master/webdriver set of automated tests]. This project would involve writing Rust code to extend the webdriver server inside of Servo, as well as JavaScript and Python to support the [https://web-platform-tests.org/writing-tests/testdriver.html testdriver.js] testharness.
| Familiarity with Python & JavaScript; interest in learning Rust
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews]
| [https://mozillians.org/en-US/u/jdm/ Josh Bowman-Matthews]
| [https://github.com/servo/servo/wiki/Support-Webdriver-based-tests-project Project description]
|-
| Support importing Instruments profiles in perf.html
| [https://github.com/devtools-html/perf.html/ perf.html] visualizes performance data recorded from various performance analysis tools. It is a tool designed to consume performance profiles from Gecko Profiler but can visualize any profiler able to output JSON. It currently supports Gecko, Chrome and perf profile formats. Instruments is a performance analyzer that comes with Xcode. This project would involve adding support for Instruments profile import in perf.html.
| Familiarity with JavaScript & React
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]
| [https://mozillians.org/en-US/u/canaltinova/ Nazım Can Altınova]
| https://github.com/devtools-html/perf.html/issues/1138
|-
| Common Voice - WebAssembly MP3 Encoding
| Currently Common Voice doesn’t support Safari, which is also why we have an iOS app. The only reason being the missing MediaRecorder API. It could be polyfilled (rebuilt in “userspace”) by compiling an MP3 encoder to WebAssembly. I’ve tried that a couple of times, but never had enough time to fix the opaque bugs happening in Safari. This could also be turned into its own library and would be a nice story overall of how WASM can help with WebCompat and missing APIs.
| JavaScript
| [https://mozillians.org/u/gweber/ Gregor Weber]
| [https://mozillians.org/u/gweber/ Gregor Weber]
| [https://github.com/mozilla/voice-web/issues/469 This GitHub issue] lines out some thoughts around how to implement it and you can find references to closed PRs which tried implementing it in various ways.
|-
| Common Voice - Voice Wave Avatar
| We’d like our users to have unique(ish) avatars based either on the characteristics of their voice or a visualization of how their name (or an utterance of their choosing) is pronounced. It could also be a combination of the two ideas. We’re very open to explore this space together, though the a candidate should have some knowledge in sound theory.
| JavaScript, Some knowledge of sound theory
| [https://mozillians.org/u/gweber/ Gregor Weber]
| [https://mozillians.org/u/gweber/ Gregor Weber]
|-
| Tab Manager menu in Firefox
| This project will extend the tab overflow menu - which shows tabs not visible in the browser's tab strip - to allow management of all open tabs across all browser windows. The selected student will be working directly in the Firefox codebase to add functionality and new menu structures to make this easily accessible for end users.
| JavaScript, CSS, and web experience
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster], [https://mozillians.org/en-US/u/bbell/ Bryan Bell]
| [https://mozillians.org/en-US/u/sfoster/ Sam Foster]
| We have [https://mozilla.invisionapp.com/share/4SNCEPDUEZ6#/screens UX mockups] for this feature, which could be broken into two phases. We also have a [https://bugzilla.mozilla.org/show_bug.cgi?id=1480542 bug on file], where discussion has begun. While working on this you will become very familiar with the Browser Toolbox, our own "Inspector" tool for the browser user-interface, as well as writing automated tests for the new feature you're adding. The existing tab overflow code lives in our [https://searchfox.org/mozilla-central/source/browser/base/content/browser-allTabsMenu.js browser-allTabsMenu.js] file, which will be the starting point for the new tab manager. You can look at this and the existing tab code to get an idea of how this currently works.

-
|-
| ..your next idea here!
|
|
|
|
|
|}

Connected Devices/Projects/Project Haiku

2017-01-27T02:04:42Z

Sfoster: Added backlogged project status block up top

{{Sidebar 
| navbar = off
| headingstyle = background-color:#eee;
| heading1 = Project Haiku 
| content1 = [[image:Connected-devices.jpg|300px]] 
| heading2 = Below, Haiku Post-pivot Prototype 
| content2 = [[image:Haiku_pivot_proto.jpg|300px]]
| heading3 = Author(s) 
| content3 = Mozilla 
| heading4 = Released 
| content4 = 2016.02.11 (Initial Pitch) 
| content5 =  
| heading6 = Innovation Status 
| content6 = [[Connected_Devices/Product_Innovation_Process#Process Gates|Stage 1 (Validation)]] 
| heading7 = Website 
| content7 = https://mzl.la/haiku 
}}

<div style="background-color: #ffc; padding: 0.5em">

Project Status: Backlogged

This project is not currently under active development by Mozilla.
</div>

'''Project Haiku''' (formerly Project Smart Home) began as a project to offer a middle ground between "in a box" smart-home solutions like Apple Homekit and DIY solutions like Raspberry Pi. We envisioned modular, affordable hardware with easy-to-use rules that would empower people to solve unique everyday problems in new and creative ways.

But we realized quickly that home automation and the industry's notion of a "smart home" are not the set of problems we are passionate about, or where we feel we can get most traction. So we moved in a different direction and chose to focus on a wearable device that would connect girls aged 12-15 with the people they loved.

At the same time, the [https://wiki.mozilla.org/Connected_Devices/Projects/Smart_Displays Smart Displays project] was also exploring the space of human connection. They arrived at a product opportunity for a stationary object that connects family members who live apart from one another.

Because these 2 projects are working in a similar space, we've decided to merge them under the Project Haiku name. '''So Project Haiku is pivoting away from a wearable to a stationary object that resides inside the home.''' We're using the Smart Display work as the jumping point for our pivot.

== Current Work ==
We presented [https://docs.google.com/presentation/d/1RkOlF1B59kBiiiP7NVdjg6c_81yqd8RolmMMgIGa7vY our pivot plan] to the PIB on Sep 20, 2016. Our product concept focuses on connecting grandparents and grandchildren. We're currently running an experiment to test our major assumptions.
* [https://drive.google.com/open?id=0ByeF_fkExK_BcmJpaExSU2NCck0 UX design for learning prototype]
* [https://drive.google.com/open?id=0By2sNBDNKma0UFN2Z2dTN096WVk Pictures from our recent workweek] in Mountain View where the team built the learning prototypes for 20 people

== Program Status ==
{| class="wikitable"
! style="text-align: center;" | Milestone
! style="text-align: center;" | Date
! style="text-align: center;" | Status
! style="text-align: center;" | Status Notes
|-
| Kick off meeting
| 3/03/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/presentation/d/1cIBckLrt9uZuVbtYObkTC0C-O7kU5Zqos6iuH2K1M04/edit#slide=id.p Kick off presentation]
|-
| First Research plan drafted
| 3/14/2016
! style="background:#00B2FF;" | Done
|
|-
| Research plan #1 drafted
| 3/29/2016
! style="background:#00B2FF;" | Done
|
|-
| Portland working week to analyze the Research findings and set the following goals/milestones
| 4/08/2016
! style="background:#00B2FF;" | Done
|
|-
| User Research #2 [from May 25th to 29th]
| 5/08/2016
! style="background:#00B2FF;" | Done
|
|-
| London All Hands Presentations (different sessions)
| 6/13/2016
! style="background:#00B2FF;" | Done
|
|-
| MVP review
| 6/15/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/presentation/d/1ATZDq0sntmA0Y5cc2mmqB1z4B9WlqguJNWUtOvctCK4/edit?usp=sharing MVP Review presentation]
|-
| User Research #2 findings
| 7/07/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/a/mozilla.com/presentation/d/1-tIWwk2JJbQpfM_j2fi5MVUfsfXHQGfN0z7nCqfAUdU/edit?usp=sharing Project Haiku: User Research #2 findings]
|-
| Kick off meeting: Team reset
| 7/11/2016
! style="background:#00B2FF;" | Done
|
|-
| User Research #3
| 8/03/2016
! style="background:#00B2FF;" | Done
| Survey to validate the hypotheses about the "priority people" and the "auto-replies"
|-
| User Research #4
| 8/26/2016
! style="background:#00B2FF;" | Done
| HTML prototype set up on Heroku to test the interactions and make refinements to the User Experience. It will help us to validate the assumptions "We believe that people want to provide their status to others (and will set/unset it)" and "We believe that when a person's status is off, they are not interested in the status of others"
|-
| User Research #5
| 8/19/2016
! style="background:#00B2FF;" | Done
| Sponsored Post on Instagram to set a baseline for future tests of our value propositions. We ran the post without a CTA over the weekend but this will be our baseline going forward.
|-
| User Research #6
|
! style="background:#00B2FF;" | Done
| Provide off-the-shelf smartwatch to girls age 12-15 to see if a wearable fits into their lives.
|-
| User Research #7
|
! style="background:#C1C6CA;" | On hold
| Make a physical prototype so girls can provide feedback on it. Our goal is to give them to a small group of girls and focus is on the wearable experience.
|-
| User Research #8
|
! style="background:#00B2FF;" | Done
| Survey 100 grandparents about how they currently communicate with their grandchildren. Purpose: set a baseline for measuring success of UR #9.
|-
| User Research #9
|
! style="background:#00B2FF;" | Done
| Share lofi prototype with 10 pairs of grandparents and grandchildren. Purpose: test major assumptions around product concept: voice calls + send/receive emojis. ([https://docs.google.com/a/mozilla.com/presentation/d/1RkOlF1B59kBiiiP7NVdjg6c_81yqd8RolmMMgIGa7vY see slide 13 here].
|
|-
| User Research #10
|
! style="background:#00EC00;" | On Target
| Share lofi prototype with 5 pairs of grandparents and grandchildren. Purpose: test participant interest in revised product concept: send/receive voicemail + send/receive emojis.
|}

'''Status Key'''
{| class="wikitable"
! style="text-align: center;" | Color
! style="text-align: center;" | Status
! style="text-align: center;" | Key
|-
! style="background:#00EC00;" |
| On Target
| The project or deliverable is expected to meet its due date.
|-
! style="background:#FFFF00;" |
| Challenged
| The project or deliverable is facing an issue that might cause it to miss its due date, but a “get well” plan has been developed to get it back on track.
|-
! style="background:#FF2800;" |
| At Risk or Late
| The project or deliverable is blocked or facing an issue that might cause it to miss its due date, and there’s no “get well” plan to get it back on track, or it is already late.
|-
! style="background:#00B2FF;" |
| Done
| The project or deliverable has been completed.
|-
! style="background:#C1C6CA;" |
| On Hold or Not Started
| The project or deliverable has either not been started or has been placed on hold.
|}

== Archived Completed Deliverables ==
{| class="wikitable"
! style="text-align: center;" | Milestone
! style="text-align: center;" | Date
! style="text-align: center;" | Status
! style="text-align: center;" | Status Notes
|-
| First Research plan drafted
| 3/14/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/document/d/1PJ9nvk7ahBIl_SLf-kMD67ENEEp6hxrQFSgbgc53Tu8/edit Initial Research Plan] is already out of date as it was revisited.
|-
| Revised Research plan #1 and Interviews guides
| 3/29/2016
! style="background:#00B2FF;" | Done
| New Research plan created to learn about the '''needs of the new targeted audiences: Babysitting age (12 to 15 years old) and independent elderly (aging in place). Both have caregivers who question the independence of the 2 audiences'''. To run this new research plan we'll be using these [https://drive.google.com/a/mozilla.com/folderview?id=0ByeF_fkExK_BQXhqUUtXdFExQWM&usp=drive_web two Interview Guides] together with these [https://drive.google.com/a/mozilla.com/folderview?id=0ByeF_fkExK_BNkxJOHZ0S3hkdmM&usp=sharing&tid=0By5ZvBZQRgjRS2RYbVM2X0owSk0# Consent & Compensation Forms].
|-
| Research findings from the Interviews
| 4/27/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/presentation/d/1i0ocmaQBrk4G4VfcGoYP7hJDql8QVrfSd7_l6-hqvd8/edit#slide=id.p Project Haiku: User Research #1 findings]
|-
| Research plan #2: Interviews guides, Research prototype, Diaries and all the documentation and logistics necessary for the User Study.
| 5/24/2016
! style="background:#00B2FF;" | Done
| [https://drive.google.com/drive/u/1/folders/0By5ZvBZQRgjReG9sN2ktTFhWdzg Project Haiku - User Study #2]. This User Research wants to validate this hypothesis: '''Creating an ambient method of communicating for 12 to 15 year old girls will create fewer interruptions that distract them from being in the moment at home and at school and improve their personal connections'''.
|-
| Research #2 findings
| 7/07/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/a/mozilla.com/presentation/d/1-tIWwk2JJbQpfM_j2fi5MVUfsfXHQGfN0z7nCqfAUdU/edit?usp=sharing Project Haiku: User Research #2 findings]
|-
| Decisions coming out of UR #2
| 7/12/2016
! style="background:#00B2FF;" | Done
| [https://docs.google.com/document/d/10mtbBIhJ_553V6kNuGlbL9YDzsmNekvB7YkVhHPMbHQ/edit?usp=sharing Project Haiku: Decisions coming out of UR #2]
|-
| Vision, Ideas, Assumptions, Hypotheses and Experiments
|
! style="background:#00B2FF;" | Done
| [https://docs.google.com/spreadsheets/d/1_C8njNIUu5DohL0ZywxyDEvK88Da_I7oFGmXKSIw_Vo/edit?usp=sharing Project Haiku: Experiments]
|-
| User Research #3 findings
| 8/05/2016
! style="background:#00B2FF;" | Done
| [https://drive.google.com/open?id=1JOU9r3alOYP1tsXEw6w931O-3gs2Zp3LUqoaPwwYp8Q Project Haiku: UR #3 findings] User Research to validate the assumptions related to the '''number of priority people that girls care about at a time and the number and type of auto-replies'''
|-
| User Research #5 findings 
| 8/19/2016
! style="background:#00B2FF;" | Done
| [https://drive.google.com/open?id=1cbtIBkbmAXb0h6pBMUUFCHUb1lezyNLVuCAb76PdI_0 Project Haiku: UR #5 findings]
|-
| User Research #4 findings (UR #4 was an internal technology experiment)
| 9/8/2016
! style="background:#00B2FF;" | Done
| [https://drive.google.com/open?id=1Y58aWEH95Ld62dC0XsViZO3buL6tnq-b8TrEdlS2q68 Project Haiku: UR #4 findings]
|-
| User Research #6 findings
| 9/26/2016
! style="background:#00B2FF;" | Done
| [https://drive.google.com/open?id=1XIq9ohtlCsk67m0VIVhZ-xOTLkBeaViByM1Tmqvod98 Project Haiku: UR #6 findings]
|-
| User Research #8 findings
| 10/12/2016
! style="background:#00B2FF;" | Done
| [https://drive.google.com/open?id=1xLgxSgp79z0Pcuin7_e60bFU185o6HdNsU9HfWSm4zE Project Haiku: UR #8 findings]
|-
| User Research #9 findings
| [fill in date]
! style="background:#00EC00;" | On target
| [https://drive.google.com/open?id=1tdJHZ60m_uFXAGi71Ex8XUg4bWuQ11TJtqMX7IPS2XQ Survey 01 - Pre-survey Findings]

[https://drive.google.com/open?id=1y9TKtL-eA6weG3MFR14TbRcO0FC37L8UsCPPHHamH2g Survey 02 - Mid-survey Findings]

[https://drive.google.com/open?id=19RmA9XO7rq_7N5_rP-1Zx62xskqIaSObSFgu0xFb354 Survey 03 - Post-survey Findings]

[https://drive.google.com/open?id=11LSKb1K7rWXfxMH3qdm9m_RGG78YsNbHH-uObAdzoyU Prototype Use - Data Analysis]

|}

== Development process ==
=== Repositories ===
* [https://github.com/mozilla/project_haiku.iot/wiki Github wiki]: This page is a chronological history of our progress. We'll create more pages as we need them.
* [https://github.com/mozilla/project_haiku.iot Project Haiku on Github]: main Github repository for Project Haiku
* [https://github.com/mozilla/project_haiku_status_api.iot Project Haiku status api on Github]: Github repository for status API supporting the Bluetooth wearable
* [https://drive.google.com/a/mozilla.com/folderview?id=0By5ZvBZQRgjRS2RYbVM2X0owSk0&usp=sharing Google Drive folder containing all project docs]

=== IRC ===
You can find us on irc.mozilla.org, channel #haiku.
=== Methodology ===
The project is in early state but we are planning to use some agile practices:
* Weekly meetings in Smart_Home Vidyo room on Mondays at 13:00 PM (Pacific Time). [https://docs.google.com/document/d/15VycPAmiSK3FLQ8QOprGtKo6h1CuQk9F0vGiY4BmTTY/edit?usp=sharing Weekly meeting doc]

=== Sprint Demos/Progress Report meetings ===

{| class="wikitable"
! style="text-align: center;" | Date
! style="text-align: center;" | Presentation
! style="text-align: center;" | Vidyo Recording
! style="text-align: center;" | Notes
|-
| 4/15/2016
| [https://docs.google.com/presentation/d/1HlcRGTyI6YxsWgql94GhZqE242Bwbfj1e8EzLMM6Bgg/edit?usp=sharing checkin #1 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=bAemFuBjNdFZL35 checkin #1 Video Recording]
| Feedback already added in the [https://docs.google.com/presentation/d/1HlcRGTyI6YxsWgql94GhZqE242Bwbfj1e8EzLMM6Bgg/edit?usp=sharing Slides]
|-
| 4/29/2016
| [https://docs.google.com/presentation/d/14WFC-ziHbdrlpDgrRAbB-1uibCdzuZaKjh2q9EBlc7I/edit?usp=sharing checkin #2 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=PuXPOfHGIATREKZ checkin #2 Video Recording]
| Feedback already added in the [https://docs.google.com/presentation/d/14WFC-ziHbdrlpDgrRAbB-1uibCdzuZaKjh2q9EBlc7I/edit?usp=sharing Slides]
|-
| 5/13/2016
| [https://docs.google.com/presentation/d/14jUhfshNRFxJRTEIZ7mfGk4ngZ7zE06Pv98s4z9gnQs/edit?usp=sharing checkin #3 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=PuXPOfHGIATREKZ checkin #3 Video Recording]
| Feedback already added in the [https://docs.google.com/presentation/d/14jUhfshNRFxJRTEIZ7mfGk4ngZ7zE06Pv98s4z9gnQs/edit?usp=sharing Slides]
|-
| 5/27/2016
| [https://docs.google.com/presentation/d/1SbLKGwnLUouIN0Ad7fm1kw7StgijmMqalODLBSZTT6k/edit?usp=sharing checkin #4 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=KUIGa81YoGGXgoH checkin #4 Video Recording]
| Feedback already added in the [https://docs.google.com/presentation/d/1SbLKGwnLUouIN0Ad7fm1kw7StgijmMqalODLBSZTT6k/edit?usp=sharing Slides]
|-
| 7/15/2016
| [https://docs.google.com/presentation/d/1a5rA-VPaTBmLCbTUFHSP9mTMqoWasEeSe_EDqlsphJg/edit?usp=sharing checkin #5 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=mosnNP20AtsNKsN checkin #5 Video Recording]
| Feedback already added in the [https://docs.google.com/presentation/d/1a5rA-VPaTBmLCbTUFHSP9mTMqoWasEeSe_EDqlsphJg/edit?usp=sharing Slides]
|-
| 8/05/2016
| [https://docs.google.com/presentation/d/1-tTvdmGdqkWR0dZI7gteKf5mLE-QBkjSlgX7J11O5ys checkin #6 Slides]
| This was a text-only update, so there is no vidyo recording or feedback.
|
|-
| 8/19/2016
| [https://drive.google.com/open?id=1Qbl9RGRwxz4O-hPzXFzV6ytOdMa5wWkztjf0i4RdvHM checkin #7 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=0ZL1FytQ0gdvTGP checkin #7 Video Recording]
|
|-
| 8/31/2016
| Haiku vision and strategy
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=xzd1D1hT9aQ0odN Haiku vision and strategy Video Recording]
|
|-
| 9/20/2016
| [https://docs.google.com/presentation/d/1RkOlF1B59kBiiiP7NVdjg6c_81yqd8RolmMMgIGa7vY Haiku Pivot Plan presentation]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=Jr9yijw9LxjVtFB Haiku Pivot : Video Recording]
|
|-
| 11/03/2016
| [https://drive.google.com/open?id=1RfH-NyLuvRZrKNCDvtnmIptl0t2lGsKq6ov2RzFrK_E Checkin #8 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=ySkH0o8252QelS9 Checkin #8 : Video Recording]
| Feedback already added in the [https://drive.google.com/open?id=1RfH-NyLuvRZrKNCDvtnmIptl0t2lGsKq6ov2RzFrK_E Slides]
|
|-
| 11/15/2016
| [https://drive.google.com/open?id=1mbH6LvZAYThRd6b3PivMpSt9Shr_q4aezB9xOAgjttA Checkin #9 Slides]
| [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=OOKazR5ALZpiGDc Checkin #9 : Video Recording]
| Feedback already added in the [https://drive.google.com/open?id=1mbH6LvZAYThRd6b3PivMpSt9Shr_q4aezB9xOAgjttA Slides]
|}

== Participation ==
We are currently in a validation phase of o[[Connected_Devices/Product_Innovation_Process|ur product innovation process]]. If you would like to get involved as a tester, developer or adviser, you can get in touch with our [[Connected_Devices/Participation|connected devices participation team]].

=== Getting in touch ===
* The best way to get in touch with us is to come and chat in our irc channel [http://chat.mibbit.com/?channel=%23foxlink&server=irc.mozilla.org channel #haiku of irc.mozilla.org] and through Discourse where we have a specific discussion forum for [https://discourse.mozilla-community.org/c/connected-devices/project-haiku Project Haiku] together with the rest of Connected Devices Projects.

== References ==
* [https://docs.google.com/presentation/d/13iXSC1PgZSYMa_oNUOqXFBJqnQOlSIZ_b1P8HIeywug/edit#slide=id.gf81a417fb_2_45 Innovation Board pitch deck]

== Team ==
* [mailto:ehunt@mozilla.com Elizabeth Hunt]- Product Lead / UX Designer
* [mailto:kcaldwell@mozilla.com Katie Caldwell] - User Experience Designer
* [mailto:sfoster@mozilla.com Sam Foster] - SW Engineer
* [mailto:pdahiya@mozilla.com Punam Dahiya]- SW Engineer
* [mailto:mpotharaju@mozilla.com Mahendranadh Potharaju]- EPM
* [mailto:ksolomon@mozilla.com Kian Solomon] - SW Engineer
* [mailto:bdong@mozilla.com Braden Dong] - Product Legal

Connected Devices/Projects/Project Haiku

2016-06-08T00:32:16Z

Sfoster: point people at #haiku channel

B2G/RTL/2.5

2015-10-28T20:40:22Z

Sfoster: Adding spec link

== Overview ==
=== User story ===
As Mozilla we want to offer the best RTL experience on our new release of Firefox OS so that all languages can be correctly supported for our user base.
=== Acceptance Criteria ===
RTL support to be improved to the updated final spec.

== UX Spec ==
* https://mozilla.app.box.com/s/y60s1ngyza9jcltmpaqwfoye4f311n5r

== Project Initial Implementation Phases ==
=== Phases ===
Details soon.

=== Modules to cover ===
'''Old modules'''
* Browser
* Calendar
* Camera
* Clock
* Contacts
* Dialer
* Email
* Find My Device
* First Time Use (FTU)
* FM Radio
* Gallery
* Homescreen
* Keyboard
* Messages/SMS
* Music
* Network Alerts
* Ringtones
* Search
* Shared
* Settings
* System
* Usage/Cost Control
* Video
* Wallpaper
* WAP Push

'''New modules'''
* Hackerplace
* Customizer
* Studio
* Sharing
* Webmaker (Should we?)
* Bugzilla Lite

The list goes on, but we have to see if we will have to implement RTL for apps living in https://github.com/fxos/ that are related to the spark project (wiki: https://wiki.mozilla.org/Firefox_OS/Spark)

== Nice-to-have Features ==
Those are features we tried to work on in previous versions or nice-to-haves
* '''Hijri/Islamic Calendar Support''': One of they features we said we would support in 3.0 (as for now 2.5) is the Islamic aka Hijri Calendar for Firefox OS.

* '''Eastern Arabic Numerals''': We should try to implement Eastern Arabic Numerals into the System since they are core elements of the Arabic language.

* '''Multi-Arabic Locales''': Those are used because of the differences between Arabic variations across The Arab countries, one of the variations is the use of Eastern or Western Arabic Numerals where ar-EG (Arabic Egypt) uses ١٢٣٤٥٦٫٧٨٩ while ar-TN (Arabic Tunisia) uses 123456.789. Android does a good job supporting those locales.

* '''Arabic Dictionary & Text prediction''': We should have text prediction support for Arabic as well as a dict/wordlist.

== Tracking bugs ==
Tracking bug: {{Bugzilla|1179459}}

<bugzilla>
{ "blocks": ["1179459"], "status": ["UNCONFIRMED", "ASSIGNED", "NEW", "REOPENED"] }
</bugzilla>

== Meetings ==
N/A

Gaia/CSS Guidelines

2015-09-16T16:45:14Z

Sfoster: Added short note about inline/flexbox to RTL/Bidi intro.

==Indentation==
* No tabs.
* Indent by two spaces.
* No (trailing spaces) spaces that appears at the end of a string.

==Style==
* Use lowercased-and-hyphen delimited classes and ids.

==Units==
* em, rem, %
* You don't have to add any units, if the value is 0
<pre>
body {
font-size: 10px;
}

1rem = 10px
1px = 0.1rem
</pre>

==Selectors==

* end in an opening brace
* be closed with a closing brace on a separate line without indentation
* Multiple selectors should each be on a single line

<pre>
/*single selector*/
.gaia {
...
}

/*multiple selectors*/
.b2g,
.gaia,
.firefox-os {
...
}
</pre>

==Comments==

Describe a section of code

<pre>
/**
* Your Comment Here.
*/
</pre>

Shorter inline comments may be added after a property, preceded with a space

<pre>
... {
padding-left: 2em; /* dir="ltr" */
}
</pre>

==Properties==

* All properties should be on the following line after the opening brace.
* have a single space before the property value
* allways add a semi-colon at the end
* multiple values - each value should be separated with a space.

<pre>
.b2g {
color: #efefef;
font-size: 0.9rem;
font-family: Open Sans, sans-serif;
}
</pre>

==Background==

* color is first
* image path without any quotes
* background repeat
* background position with % or rem
* Don't use shorthand property when you change only a single value(except when you need to override a rules)
<pre>
... {
background: #fff url(images/default.png) no-repeat 3rem 100%;
padding: 0 0 0 5rem;
}
</pre>

===Multiple Backgrounds===
<pre>
... {
background: url(images/image-3.png),
url(images/image-2.png),
url(images/image-1.png),
#fff;
}
</pre>

===Gradients===
<pre>
... {
background: linear-gradient(to bottom, #fff, #000);
}
</pre>

==Borders==
<pre>
... {
border: 0.1rem solid #fff;
}
</pre>

==Colors==
<pre>
... {
color: #0f0; /* HEX color - defined using the 3-character dash notation */
color: #00ff00 /* HEX color - defined using the 6-character dash notation */
color: rgba( 34, 12, 64, 0.3); /* rgba(R,G,B,a) - using only for transparent colors */
}
</pre>

==Direction (RTL/LTR and BiDi)==

Many UI elements are have to be mirrored for languages written Right-To-Left. This comes for free with flex-box and other inline element layouts. However, if you need to use positioning or other explicit styling and layout, here’s how you can make it easier.

===Use the same specificity for LTR and RTL===
Rules that are direction-specific (e.g LTR) should have the same specificity as their RTL counterparts. Rules with an implicit direction should be made explicit using either the dir attribute selector (html[dir="ltr|rtl"]), or the :-moz-dir(rtl) pseudo-class. RTL and LTR -specific rules should always be grouped together in the same stylesheet to simplify maintenance.
<pre>
html[dir="ltr"] .foo {
left: 0;
}
html[dir="rtl"] .foo {
right: 0;
}
</pre>

===Use direction-sensitive rules===
Many CSS rules that include a `left` or `right` keyword can be written with `start` or `end` instead:

{| class="wikitable" style="width: 100%"
|-
! left/right !! begin/end !! browser compatibility
|-
|style="text-align: center" colspan="3"| text alignment
|-
| <code>text-align: left text-align: right</code> || <code>text-align: start text-align: end</code> || Chrome 1.0+, Safari 3.1+, Firefox 3.6+, Android, iOS Not supported by Internet Explorer
|-
|style="text-align: center" colspan="3"| padding, margin, border
|-
| <code>padding-left padding-right</code> || <code>[https://developer.mozilla.org/docs/Web/CSS/padding-inline-start padding-inline-start] [https://developer.mozilla.org/docs/Web/CSS/padding-inline-end padding-inline-end]</code> || Firefox 41+
|-
| <code>border-left border-right</code> || <code>[https://developer.mozilla.org/docs/Web/CSS/border-inline-start border-inline-start] [https://developer.mozilla.org/docs/Web/CSS/border-inline-end border-inline-end]</code> || Firefox 41+
|-
| <code>margin-left margin-right</code> || <code>[https://developer.mozilla.org/docs/Web/CSS/margin-inline-start margin-inline-start] [https://developer.mozilla.org/docs/Web/CSS/margin-inline-end margin-inline-end]</code> || Firefox 41+
|-
|style="text-align: center" colspan="3"| absolute positioning
|-
| <code>left right</code> || <code>[https://developer.mozilla.org/docs/Web/CSS/offset-inline-start offset-inline-start] [https://developer.mozilla.org/docs/Web/CSS/offset-inline-end offset-inline-end]</code> || Firefox 41+
|-
|style="text-align: center" colspan="3"| float positioning
|-
| <code>float: left float: right</code> || <code>float: inline-start float: inline-end</code> || (not yet supported)
|}

'''Warning:''' in most cases, you don’t want to apply these direction-sensitive rules to HTML elements carrying a <code>dir="auto"</code> attribute because the layout would be modified by the content direction.

===margin, padding, border: do not use 4-value shorthands===
Beware of the shorthands on margin/padding/border rules:
<pre>
margin: 1rem; /* OK: start and end margins are set to 1rem */
margin: 1rem 2rem; /* OK: start and end margins are set to 2rem */
margin: 1rem 2rem 3rem; /* OK: start and end margins are set to 2rem */
margin: 1rem 2rem 3rem 4rem; /* direction-specific! */
</pre>
Shorthands with 1, 2 or 3 values are BiDi-proof; shorthands with 4 values are not.

As an example, rather than using:
<pre>
.myClass {
padding: 1rem 2rem 3rem 4rem;
}
</pre>

you should use:
<pre>
.myClass {
padding: 1rem 2rem 3rem;
padding-inline-start: 4rem;
}
</pre>

or, if the target element has a <code>dir="auto"</code> attribute (or if your browser doesn’t support -inline-start):

<pre>
.myClass {
padding: 1rem 2rem 3rem;
}
html[dir="ltr"] .myClass {
padding-left: 4rem;
}
html[dir="rtl"] .myClass {
padding-right: 4rem;
}
</pre>

Gaia/CSS Guidelines

2015-08-03T22:23:14Z

Sfoster: Adding guidelines for RTL/LTR/bidi

Firefox OS/systemsfe/status/2.2S3

2015-01-08T05:26:15Z

Sfoster: Created page with "== Demos == === {{Bug|1061324}}: Rework cards view into cards strip with app chrome === This work was completed back in 2014-09-12 but didn't get approved for uplift to 2.1 s..."

== Demos ==

=== {{Bug|1061324}}: Rework cards view into cards strip with app chrome ===
This work was completed back in 2014-09-12 but didn't get approved for uplift to 2.1 so is new to some. I'll use it to get the ball rolling on this demo thing.

https://vimeo.com/116215276

https://bugzilla.mozilla.org/show_bug.cgi?id=1061324

Summit2013/Experiences/signups

2013-10-01T18:29:32Z

Sfoster: /* Nuit Blanche Stroll */

Please sign up below.

'''UPDATE:''' There are many folks who are also asking if they can add sessions to this. The answer is yes! And, there will also be white boards and post its in the main area of each venue for you to propose/add organic social sessions there as well.

 Note: Please ONLY add/remove your name. Please do not move lists around or change times as it is causing lots of confusion. If you have questions or need help please use #mozsummit. Thank you.
=Santa Clara=
==Friday ==
=== Photo Walk ===

If you are interested in an early morning [6:30am] tour in the beautiful Silicon Valley, you are in luck! [https://mozillians.org/en-US/u/Ludovic Ludovic Hirlimann] and [https://mozillians.org/en-US/u/rolandtanglao Roland Tanglao]

More information here: http://sietch-tabr.tumblr.com/post/60429342277/extra-summit-activity-part-1-santa-clara-photowalks

* Time:
* Meeting Location:
* Need to Knows:

Sign Up Here:
<table border=1><tr><th colspan=2>Name</th></tr>
<tr><td>Oarabile Mudongo</td><td>Jaydev Ajit Kumar</td></tr>
<tr><td>Bill Walker</td><td>Viking KARWUR</td></tr>
<tr><td>Muhammad Mehmood Ali</td><td>Asad Sajjad</td></tr>
<tr><td>Shazia Rizwan</td><td>Nagasahas DS </td></tr>
<tr><td>Abdul Rauf</td><td>Jemmy RORONG</td></tr>
<tr><td>Finan AKBAR</td><td>Dimas ANDHANA</td></tr>
<tr><td>Fauzan ALFI</td><td>Artanto ISHAAM</td></tr>
<tr><td>Kalpa Welivitigoda</td><td>Ashkary Rahman</td></tr>
<tr><td>Irayani Queencyputri</td><td>Eriska Triana Primayasari</td></tr>
<tr><td>Deryan Everestha Maured</td><td>Nuri Abidin</td></tr>
<tr><td>Rahmat Dwi Jatmiko</td><td>Andi Darmawan</td></tr>
<tr><td>I Gede Bagus Kosha</td><td>Sayak Sarkar</td></tr>
<tr><td>Shahrin Hossain</td><td>Soumya Deb</td></tr>
<tr><td>Sankha Narayan Guria</td><td>Swarnava Sengupta</td></tr>
<tr><td>Avik Pal</td><td>Gaurab Patra</td></tr>
<tr><td>Diwanshi Pandey</td><td>Subhashish Kundu</td></tr>
<tr><td>Shafiul Azam Chowdhury</td><td>Rahid Hasan</td></tr>
<tr><td>Hilary Ho Jia Hao</td><td>Gauthamraj Elango</td></tr>
<tr><td>Jayakumar Sadhasivam</td><td>Md Aminul Islam Sajib</td></tr>
<tr><td>Md Golam Mostafa</td><td>[[user:maktrix|Mahay Alam Khan]]</td></tr>
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td><td>Zobayer Ahmed Khan</td></tr>
<tr><td>Benny Chandra</td><td>Yoe One Ariestya Niovitta</td></tr>
<tr><td>Rizqinofa Putra M</td><td>Gasper Derzanic</td></tr>
<tr><td>Atul Jangra</td><td>Akshay Aurora</td></tr>
<tr><td>Aji Kisworo Mukti</td><td>[[user:ahsan.net|Mashkawat Ahsan]]</td></tr>
<tr><td>Matjaž Horvat</td><td>[[user:rok.samsa|Rok Samsa]]</td></tr>
<tr><td>[[user:mythrobin|Robin Mehdee]]</td><td>Rohan Dasanayaka</td></tr>
<tr><td>Anup Kumar Mishra</td><td>Ankit Gadgil</td></tr>
<tr><td>Ajay Kumar</td><td>Ankit Kumar Mishra</td></tr>
<tr><td>Parmpreet Singh</td><td>Gary Chen</td></tr>
<tr><td>Clarice Wang</td><td>[[user:RodrigoPadula|Rodrigo Padula]]</td></tr>
<tr><td>Dominic Kuo</td><td>Steve Chung</td></tr>
<tr><td>Kate Huang</td><td>Linear Li</td></tr>
<tr><td>Yuren Ju</td><td>Kan-Ru Chen (:kanru)</td></tr>
<tr><td>Szu-Yu Chen (:aknow)</td><td>Goran Kohek</td></tr>
<tr><td>Soumya Kanti Chakraborty</td><td>Jon Buckley</td></tr>
<tr><td>Rizky Ariestiyansyah</td><td>Ani Peter</td></tr>
<tr><td>Alex Lakatos</td><td>Marcela Oniga</td></tr>
<tr><td>Sammy Fung</td><td>Kengatharaiyer Sarveswaran (Sarves)</td></tr>
<tr><td>Jim Chen (:jchen)</td><td>Muhammad Syafiq Mazli (:syafiqmazli)</td></tr>
<tr><td>Mohamed Aidid Jaafar (:aidid)</td><td>Haryati Salehin (:yadyadun)</td></tr>
<tr><td>Lai Chen Haw (:chenhaw)</td><td>Rishabh Narayan</td></tr>
<tr><td>Manoj Kumar Giri</td><td>Shankar Prasad (:shanky)</td></tr>
<tr><td>Sandeep Shedmake</td><td>Krishnababu K (:Krishna)</td></tr>
<tr><td>Grigorios Petsos</td><td>Benjamin Pokharel</td></tr>
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td><td>Luigi Tedone</td></tr>
<tr><td>Michael Comella (:mcomella)</td><td>[[user:Bobreyes|Robert 'Bob' Reyes]]</td></tr>
<tr><td>Kevin John Ventura (:kjventura)</td><td>Kathrine Faye Tandog</td></tr>
<tr><td>Kathleen Joyce Domanog</td><td>Erika Aurea Gatmaitan</td></tr>
<tr><td>Michelle Anne Santos</td><td>Arun Balachandran Ganesan (:abc)</td></tr>
<tr><td>Kevin Ngo (:ngoke/:kngo)</td><td>Cherlowe Reinard Ramirez</td></tr>
<tr><td>Mark Giffin (markg)</td><td>Marcus Ang</td></tr>
<tr><td>Cervantes Yu</td><td>Aditya Fitri Hananta Putra</td></tr>
<tr><td>John Daggett</td><td>PATIL Kailas Ravsaheb</td></tr>
<tr><td>Vaibhav Bajaj</td><td>Komal Gandhi</td></tr>
<tr><td>Ajay Jogawath</td><td>Jafar Muhammed</td></tr>
<tr><td>Srikar Ananthula</td><td>Sai Kiran Alagundula</td></tr>
<tr><td> Raghuram K</td><td> Srikanth Namu</td></tr>
<tr><td> Sandraghassen Subbaraya Pillai</td><td> André Reinald</td></tr>
<tr><td>Remco Kaptein</td><td>Shahmir Khan</td></tr>
<tr><td>Meraj Imran</td><td>Hema Bhanu</td></tr>
<tr><td> Maniraj</td><td>Saurabh Anand</td></tr>
<tr><td> Abhishek Potnis</td><td>Amod Narvekar</td></tr>
<tr><td> [https://mozillians.org/zh-CN/u/steekid/ Hao Shen]</td><td>Chihiro Akiba</td></tr>
<tr><td>Atsushi Shimono (:himorin)</td><td>Hideki Akiba</td></tr>
<tr><td>Masashi Honma</td><td>[[user:kinshuksunil|Kinshuk Sunil]]</td></tr>
<tr><td>Fang, Chiung-Hui (GDH)</td><td>Xin Mu </td></tr>
<tr><td>Hiro Imamura</td><td>Midhun Manojkumar </td></tr>
<tr><td>Hector Zhao (:hectorz)</td><td>Miyake Shuuji</td></tr>
<tr><td>Changyu Hu</td><td>Yi Chen</td></tr>
<tr><td>Kao, Wei-Ko (:othree)</td><td>Kevin, Liu</td></tr>
<tr><td>Sudheesh Singanamalla (:ShellHacker)</td><td>Prof. D.V.L.N.Somayajulu</td></tr>
<tr><td>[[user:ivikash|Vikash Agrawal]]</td><td>[[user:espressive|Schalk Neethling]]</td></tr>
<tr><td>Evil Machines (:m1)</td><td>Martian Ho</td></tr>
<tr><td>Wichai Termwuttipreecha</td><td></td></tr>
</table>

==Saturday==
=== Movie Night ===

On Saturday in '''all three''' locations, we will be holding a movie night complete with big screens and old fashioned pop corn. We will be starting with Code Rush the documentary about the early days of Mozilla.

We may be showing another movie after this, if there is enough interest.

We have plenty of room, but would like to get a count of how many people will be joining us. Please add your name to the sign up below if you are interested.

<table border=1><tr><th>Name</th></tr>
<tr><td>Heather Arthur</td><td>Oarabile Mudongo</td></tr>
<tr><td>Pascal Finette</td><td>Jon Hylands</td></tr>
<tr><td>Rob Hudson</td><td>Viking KARWUR</td></tr>
<tr><td>Shahmir Khan</td><td>Muhammad Mehmood Ali</td></tr>
<tr><td>Asad Sajjad</td><td>Shazia Rizwan</td></tr>
<tr><td>Alex Vincent</td><td>Gautam A</td></tr>
<tr><td>Nagasahas DS</td><td>Jemmy RORONG</td></tr>
<tr><td>Finan AKBAR</td><td>Dimas ANDHANA</td></tr>
<tr><td>Artanto ISHAAM</td><td>Fauzan ALFI</td></tr>
<tr><td>Kalpa Welivitigoda</td><td>Ashkary Rahman</td></tr>
<tr><td>Irayani Queencyputri</td><td>Eriska Triana Primayasari</td></tr>
<tr><td>Deryan Everestha Maured</td><td>Nuri Abidin</td></tr>
<tr><td>Rahmat Dwi Jatmiko</td><td>Andi Darmawan</td></tr>
<tr><td>I Gede Bagus Kosha</td><td>Sayak Sarkar</td></tr>
<tr><td>Priyanka Nag</td><td>Soumya Deb</td></tr>
<tr><td>Sankha Narayan Guria</td><td>Swarnava Sengupta</td></tr>
<tr><td>Ankit Gadgil</td><td>Jaydev Ajit Kumar</td></tr>
<tr><td>Diwanshi Pandey</td><td>Avik Pal</td></tr>
<tr><td>Gaurab Patra</td><td>Subhashish Kundu</td></tr>
<tr><td>Hilary Ho Jia Hao</td><td>Gauthamraj Elango</td></tr>
<tr><td>[[user:maktrix|Mahay Alam Khan]]</td><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr>
<tr><td>Zobayer Ahmed Khan</td><td>Benny Chandra</td></tr>
<tr><td>Yoe One Ariestya Niovitta</td><td>Rizqinofa Putra M</td></tr>
<tr><td>Jayakumar Sadhasivam</td><td>Atul Jangra</td></tr>
<tr><td>Akshay Aurora</td><td>Aji Kisworo Mukti</td></tr>
<tr><td>Matjaž Horvat</td><td>[[user:mythrobin|Robin Mehdee]]</td></tr>
<tr><td>Rohan Dasanayaka</td><td>Ajay Kumar</td></tr>
<tr><td>Ankit Mishra</td><td>Parmpreet Singh</td></tr>
<tr><td>Anup Kumar Mishra</td><td>Goran Kohek</td></tr>
<tr><td>Soumya Kanti Chakraborty</td><td>Jon Buckley</td></tr>
<tr><td>Tim Taubert</td><td>Rizky Ariestiyansyah</td></tr>
<tr><td>Ani Peter</td><td>Sammy Fung</td></tr>
<tr><td>Jim Chen (:jchen)</td><td>Muhammad Syafiq Mazli (:syafiqmazli)</td></tr>
<tr><td>Mohamed Aidid Jaafar (:aidid)</td><td>Haryati Salehin (:yadyadun)</td></tr>
<tr><td>Lai Chen Haw (:chenhaw)</td><td>Rishabh Narayan </td></tr>
<tr><td>Manoj Kumar Giri </td><td>Shankar Prasad (:shanky)</td></tr>
<tr><td>Sandeep Shedmake</td><td>Krishnababu K (:Krishna)</td></tr>
<tr><td>Grigorios Petsos</td><td>Benjamin Pokharel</td></tr>
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td><td>Luigi Tedone</td></tr>
<tr><td>Nick Fitzgerald</td><td>Anton Kovalyov</td></tr>
<tr><td>Arun Balachandran Ganesan</td><td>Kevin Ngo</td></tr>
<tr><td>Brendan Dahl</td><td>Johnny Stenback</td></tr>
<tr><td>Christopher De Cairos</td><td>Sean Bolton</td></tr>
<tr><td>Joanna Mazgaj</td><td>[[user:Netoarmando|Armando Neto]]</td></tr>
<tr><td>[[user:RodrigoPadula|Rodrigo Padula]]</td><td>Aditya Fitri Hananta Putra</td></tr>
<tr><td>John Daggett</td><td>Dwi Hardyanto</td></tr>
<tr><td>PATIL Kailas Ravsaheb</td><td>Blair McBride</td></tr>
<tr><td>Ajay Jogawath</td><td>[[user:Komal gandhi|Komal Gandhi]]</td></tr>
<tr><td>Vaibhav Bajaj</td><td>Jafar Muhammed</td></tr>
<tr><td>Srikar Ananthula</td><td>Sai Kiran Alagundula</td></tr>
<tr><td>Raghuram K</td><td>Srikanth Namu</td></tr>
<tr><td>Alexis M</td><td>Sandraghassen Subbaraya Pillai</td></tr>
<tr><td>byron jones</td><td>André Reinald</td></tr>
<tr><td>Aaron Druck</td><td>Ville Pohjanheimo</td></tr>
<tr><td>Jay Sullivan</td><td>Meraj Imran</td></tr>
<tr><td>Hema Bhanu</td><td>Maniraj</td></tr>
<tr><td>Philipp Wagner</td><td>Saurabh Anand</td></tr>
<tr><td>Abhishek Potnis</td><td>Amod Narvekar</td></tr>
<tr><td>Behnam Esfahbod</td><td>Felipe Gomes</td></tr>
<tr><td>Amy Hu</td><td>[[User:kinshuksunil|Kinshuk Sunil]]</td>
<tr><td>David Chen</td><td>Midhun Manojkumar </td></tr>
<tr><td>Michael Maslaney</td><td>[[user:Tim.babych|Tim Babych]]</td></tr>
<tr><td>[[user:ivikash|Vikash Agrawal]]</td><td>Nicholas Hurley</td></tr>
<tr><td>Sudheesh Singanamalla</td><td>Prof. D.V.L.N.Somayajulu</td></tr>
<tr><td>Evil Machines (:m1)</td><td>Marco Bonardo (:mak)</td></tr>
<tr><td>Nigel Babu (:nigelb)</td><td></td></tr>
</table>

=== Mozillians Pilates ===

Not just any Pilates - Pilates instructed by [https://mozillians.org/en-US/u/pfinette/ Pascal Finette] who is a certified Pilates trainer!(little known fact he also trains two Olympic B-Cadre Team USA marathoners)

He's offered to lead a wake you up Pilates session for 15-20 people on Friday. If more would like to join, he will host it again on Saturday.

If you are local, please bring a yoga mat or bath towel with you. We will provide a limited number of mats for those who need them.

<table border=1><tr><th>Name</th></tr>
<tr><td>Jennifer Bertsch </td></tr>
<tr><td>Iacopo Benesperi</td></tr>
<tr><td>Gautam A</td></tr>
<tr><td>Nagasahas DS</td></tr>
<tr><td>Lindsay Kenzig</td></tr>
<tr><td>[[user:maktrix|Mahay Alam Khan]]</td></tr>
<tr><td>Aashish Jagini</td></tr>
<tr><td>Kathryn Meisner</td></tr>
<tr><td>Ani Peter</td></tr>
<tr><td>Jayakumar Sadhasivam</td></tr>
<tr><td>Mardi Douglass</td></tr>
<tr><td>Kate Naszradi</td></tr>
<tr><td>Manoj Kumar Giri</td></tr>
<tr><td>Shankar Prasad (:shanky)</td></tr>
<tr><td>Krishnababu K (:Krishna)</td></tr>
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td></tr>
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr>
<tr><td>Luigi Tedone</td></tr>
<tr><td>Sean Bolton</td></tr>
<tr><td>Joanna Mazgaj</td></tr>
<tr><td>Zobayer Ahmed Khan</td></tr>
<tr><td>Sandraghassen Subbaraya Pillai</td></tr>
<tr><td>Vaibhav Bajaj</td></tr>
<tr><td>Chihiro Akiba</td></tr>
<tr><td>Alina Mierlus</td><tr>
</table>

=== Great America ===

Are you up for a night of shows, fast rides, daring drops and good old fashioned American fair food? Did I mention they have a Halloween themed side of the park as well? If you'd like to join in the experience, come join your fellow Mozillians at Great America!

There are plenty (200+) tickets available, but you must sign up by 10/1 to receive an admission ticket.

<table border=1><tr><th colspan=2>Name</th></tr>
<tr><td>1 Pascal Finette</td> <td>2 Jennifer Bertsch</td></tr>
<tr><td>3 Rob Hudson</td> <td>4 Viking KARWUR</td></tr>
<tr><td>5 Iacopo Benesperi</td> <td>6 Michelle Cristobal</td></tr>
<tr><td>7 Shahmir Khan</td> <td>8 Asad Sajjad</td></tr>
<tr><td>9 Muhammad Mehmood Ali</td> <td>10 Gautam A</td></tr>
<tr><td>11 Nagasahas DS</td> <td>12 Abdul Rauf</td></tr>
<tr><td>13 Jemmy RORONG</td> <td>14 Finan AKBAR</td></tr>
<tr><td>15 Dimas ANDHANA</td> <td>16 Artanto ISHAAM</td></tr>
<tr><td>17 Fauzan ALFI</td> <td>18 Ashkary Rahman</td></tr>
<tr><td>19 Irayani Queencyputri</td> <td>20 Eriska Triana Primayasari</td></tr>
<tr><td>21 Deryan Everestha Maured</td> <td>22 Nuri Abidin</td></tr>
<tr><td>23 Rahmat Dwi Jatmiko</td> <td>24 Andi Darmawan</td></tr>
<tr><td>25 I Gede Bagus Kosha</td> <td>26 Shazia Rizwan</td></tr>
<tr><td>27 Shafiul Azam Chowdhury</td> <td>28 Rahid Hasan</td></tr>
<tr><td>29 Sayak Sarkar</td> <td>30 Shahrin Hossain</td>
<tr><td>31 Soumya Deb</td> <td>32 Swarnava Sengupta</td></tr>
<tr><td>33 Avik Pal</td> <td>34 Gaurab Patra</td></tr>
<tr><td>35 Subhashish Kundu</td> <td>36 Kaustav Das Modak </td></tr>
<tr><td>37 Galaxy Kadiyala</td> <td>38 Vineel Reddy Pindi</td></tr>
<tr><td>39 Gauthamraj Elango</td> <td>40 Faizal Aziz</td></tr>
<tr><td>41 Sara Khan</td> <td>42 Hilary Ho Jia Hao</td></tr>
<tr><td>43 Md Aminul Islam Sajib</td> <td>44 [[user:maktrix|Mahay Alam Khan]]</td></tr>
<tr><td>45 Zobayer Ahmed Khan</td> <td>46 Abdur Rahman </td></tr>
<tr><td>47 Benny Chandra</td> <td>48 Yoe One Ariestya Niovitta</td></tr>
<tr><td>49 [[user:ahsan.net|Mashkawat Ahsan]]</td> <td>50 Jayakumar Sadhasivam</td></tr>
<tr><td>51 Rizqinofa Putra M</td> <td>52 Gasper Derzanic</td></tr>
<tr><td>53 Atul Jangra</td> <td>54 Aji Kisworo Mukti</td></tr>
<tr><td>55 Matjaž Horvat</td> <td>56 [[user:rok.samsa|Rok Samsa]]</td></tr>
<tr><td>57 [[user:mythrobin|Robin Mehdee]]</td> <td>58 Rohan Dasanayaka </td></tr>
<tr><td>59 Anup Kumar Mishra </td> <td>60 Ankit Mishra </td></tr>
<tr><td>61 Parmpreet Singh </td> <td>62 Ajay Kumar </td></tr>
<tr><td>63 Clarice Wang </td> <td>64 Goran Kohek </td></tr>
<tr><td>65 Soumya Kanti Chakraborty</td> <td>66 Jon Buckley</td></tr>
<tr><td>67 [[user:alefteris|Thanos Lefteris]]</td> <td>68 Akshay Aurora</td></tr>
<tr><td>69 Rizky Ariestiyansyah</td> <td>70 Ani Peter</td></tr>
<tr><td>71 Angela Leung</td> <td>72 Alex Lakatos</td></tr>
<tr><td>73 Marcela Oniga</td> <td>74 Nikki Tran</td></tr>
<tr><td>75 Kengatharaiyer Sarveswaran (Sarves) </td> <td>76 Ankit Gadgil</td></tr>
<tr><td>77 Diwanshi Pandey</td> <td>78 Jake Watkins</td></tr>
<tr><td>79 Jim Chen (:jchen)</td> <td>80 Md Golam Mostafa</td></tr>
<tr><td>81 Muhammad Syafiq Mazli (:syafiqmazli)</td> <td>82 Mohamed Aidid Jaafar (:aidid)</td></tr>
<tr><td>83 Haryati Salehin (:yadyadun)</td> <td>84 Lai Chen Haw (:chenhaw)</td></tr>
<tr><td>85 Rishabh Narayan</td> <td>86 Louis-Rémi Babé</td></tr>
<tr><td>87 James Kitchener</td> <td>88 Manoj Kumar Giri</td></tr>
<tr><td>89 Shankar Prasad (:shanky)</td> <td>90 Krishnababu K (:Krishna)</td></tr>
<tr><td>91 Grigorios Petsos</td> <td>92 Benjamin Pokharel</td></tr>
<tr><td>93 [[user:Rifaz|Rifaz Nahiyan]]</td> <td>94 [[user:Ashickurnoor|Ashickur Rahman]]</td></tr>
<tr><td>95 Sofanit Belay (Sofi)</td> <td>96 Luigi Tedone</td></tr>
<tr><td>97 Jennifer Fong</td> <td>98 Soledad Penades</td></tr>
<tr><td>99 [[user:Ckolos|Chris Kolosiwsky]]</td> <td>100 [[user:bobm|Bob Micheletto]]</td></tr>
<tr><td>101 [[user:bnicholson|Brian Nicholson]]</td> <td>102 [[user:hoosteeno|Justin Crawford]]</td></tr>
<tr><td>103 [[user:AxelHecht|Axel Hecht]]</td> <td>104 Michael Comella (:mcomella)</td></tr>
<tr><td>105 Arun Balachandran Ganesan (:abc)</td> <td>106 Kevin Ngo (:kngo/:ngoke)</td></tr>
<tr><td>107 Brendan Dahl</td> <td>107 Nick Fitzgerald</td></tr>
<tr><td>107 Anton Kovalyov</td> <td>108 Matt Woodrow</td></tr>
<tr><td>109 Cherlowe Reinard Ramirez</td> <td>110 Bas Schouten</td></tr>
<tr><td>111 [[user:Netoarmando|Armando Neto]]</td> <td>112 Gary Chen</td></tr>
<tr><td>113 Linear Li</td> <td>114 Kate Huang</td></tr>
<tr><td>115 Steve Chung</td> <td>116 Dominic Kuo</td></tr>
<tr><td>117 Ian Liu</td> <td>118 Sankha Narayan Guria</td></tr>
<tr><td>119 Szu-Yu Chen (:aknow)</td> <td>120 [[user:Bobreyes|Robert 'Bob' Reyes]]</td></tr>
<tr><td>121 Cervantes Yu</td> <td>122 Anne Michelle Santos</td></tr>
<tr><td>123 Kevin John Ventura</td> <td>124 Kathrine Faye Tandog</td></tr>
<tr><td>125 Kathleen Joyce Domanog</td> <td>126 Erika Aurea Gatmaitan</td></tr>
<tr><td>127 Marcus Ang</td> <td>128 Aditya Fitri Hananta Putra</td></tr>
<tr><td>129 Dwi Hardyanto</td> <td>130 PATIL Kailas Ravsaheb</td></tr>
<tr><td>131 Vaibhav Bajaj</td> <td>132[[user:Komal gandhi| Komal Gandhi]]</td></tr>
<tr><td>133 Ajay Jogawath</td> <td>134 Jafar Muhammed</td></tr>
<tr><td>135 Sandeep Shedmake</td> <td>136 Srikar Ananthula</td></tr>
<tr><td>137 Sai Kiran Alagundula</td> <td>138 Raghuram K </td></tr>
<tr><td>139 Ginn Chen </td> <td>140 Leon Sha </td></tr>
<tr><td>[[user:RodrigoPadula|141 Rodrigo Padula]]</td> <td>142 Sandraghassen Subbaraya Pillai </td></tr>
<tr><td>143 byron jones</td> <td>144 Srikanth Namu</td></tr>
<tr><td>145 [[User:KaiRo|Robert Kaiser (KaiRo)]]</td> <td>146 André Reinald</td></tr>
<tr><td>147 Aaron Druck</td> <td>148 Remco Kaptein</td></tr>
<tr><td>149 Harvey Anderson</td> <td>150 Alexis Stowers</td></tr>
<tr><td>151 Mary Biondi</td><td>152 Kim Murphy</td></tr>
<tr><td>153 Ashlee Chavez</td><td>154 Meraj Imran</td></tr>
<tr><td>155 Hema Bhanu</td><td>156 Maniraj</td></tr>
<tr><td>157 [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]</td><td>158 Philipp Wagner</td></tr>
<tr><td>159 Saurabh Anand</td><td>160 Oarabile Mudongo</td></tr>
<tr><td>161 Jaydev Ajit Kumar</td><td>162 Marina Samuel</td></tr>
<tr><td>163 Axilleas Pipinellis</td><td>164 [https://mozillians.org/en-US/u/relud/ Daniel Thornton]</td></tr>
<tr><td>165 [https://mozillians.org/en-US/u/taratatach/ Erwan Guyader]</td><td>166 Antoine D. (Flaburgan)</td></tr>
<tr><td>167 [https://mozillians.org/zh-CN/u/steekid/ Hao Shen]</td><td>168 Makoto Kato</td></tr>
<tr><td>169 Yumi Ochiai</td><td>170 Eri Inoue</td></tr>
<tr><td>171 Atsushi Shimono (:himorin)</td><td>172 Tetsuharu OHZEKI</td></tr>
<tr><td>173 ABE Hiroki (hATrayflood)</td><td>174 Masashi Honma</td></tr>
<tr><td>175 Tetsuya Kosaka</td><td>176 Peter Chen [:petercpg]</td></tr>
<tr><td>177 Irvin [:irvinfly]</td><td>178 [https://mozillians.org/en-US/u/benbangert/ Ben Bangert]</td></tr>
<tr><td>179 Toby Elliott</td><td>180 [https://mozillians.org/en-US/u/jrconlin/ jr conlin]</td></tr>
<tr><td>181 Dayo Choul</td><td>182 Behnam Esfahbod</td></tr>
<tr><td>183 Daisuke MORI</td><td>184 Edward Hu</td></tr>
<tr><td>185 Felipe Gomes</td><td>186 [[User:kinshuksunil|Kinshuk Sunil]]</td></tr>
<tr><td>187 Hideki Akiba</td><td>188 Chihiro Akiba</td></tr>
<tr><td>189 Rachel Zhang</td><td>190 Fang, Chiung-Hui(GDH)</td></tr>
<tr><td>191 Xin Mu</td><td>192 [https://mozillians.org/en-US/u/Med0paW/ Rui You] (:ryou)</td></tr>
<tr><td>193 Hiro Imamura</td><td>194 Midhun Manojkumar</td></tr>
<tr><td>195 Miyake Shuuji</td><td>196 [https://mozillians.org/en-US/u/yuanxulei/ Yuan Xulei] (:yxl)</td></tr>
<tr><td>197 Wayne Chang</td><td>198 Ivan Tsay</td></tr>
<tr><td>199 Bruce Huang</td><td>200 Dapeng Wei</td></tr>
<tr><td>201 Changyu Hu</td><td>202 Yi Chen</td></tr>
<tr><td>203 Masayuki Nakano</td><td>204 Kevin, Liu</td></tr>
<tr><td>205 Ernest Chiang</td><td>206 James Teh</td></tr>
<tr><td>207 Kao Wei-Ko(:othree)</td><td>208 [[user:ivikash|Vikash Agrawal]]</td></tr>
<tr><td>209 Pierros Papadeas (:pierros)</td><td>210 Athanasia Thalia Papoutsaki</td></tr>
<tr><td>211 Christos Bacharakis</td><td>212 Schalk Neethling</td></tr>
<tr><td>213 Heather Arthur</td><td>214 Nicholas Hurley</td></tr>
<tr><td>215 Katherine Nelson</td><td>216 Michael Maslaney</td></tr>
<tr><td>217 Alina Mierlus</td><td>218 [[user:Tim.babych|Tim Babych]]</td></tr>
<tr><td>219 Sudheesh Singamalla</td><td>220 Prof. D.V.L.N. Somayajulu</td></tr>
<tr><td>221 John Karahalis</td><td>222 Stefan Mirea</td></tr>
<tr><td>223 Kyle Lahnakoski</td><td>224 [https://mozillians.org/en-US/u/Fiag/ Qing Lei]</td></tr>
<tr><td>225 Martian Ho</td><td></td></tr>
</table>

=== Bill Walker w/the Roger Steen Band @ San Pedro Square Market ===

Come see Bill Walker perform original rock and roll with the [http://rogersteenband.com Roger Steen Band] at 8pm in [http://www.sanpedrosquaremarket.com/ San Pedro Square], San Jose. Roger Steen is the founding guitarist of The Tubes, and has recently released his [https://itunes.apple.com/us/album/roger-steen/id635651246 first solo album]. We'll be performing songs from that album as well as some cool covers. If you put your names here, we can work out some way to carpool and/or take public transit together.

<table border=1><tr><th>Name</th></tr>
<tr><td>Bill Walker</td></tr>
<tr><td>Rifaz Nahiyan</td></tr>
</table>

==Sunday==
=== Mozillians Pilates ===

Not just any Pilates - Pilates instructed by [https://mozillians.org/en-US/u/pfinette/ Pascal Finette] who is a certified Pilates trainer!(little known fact he also trains two Olympic B-Cadre Team USA marathoners)

He's offered to lead a wake you up Pilates session for 15-20 people. He is also offering a class on Saturday, if you haven't yet signed up there. :-)

If you are local, please bring a yoga mat or bath towel with you. We will provide a limited number of mats for those who need them.

<table border=1><tr><th>Name</th></tr>
<tr><td>Kalpa Welivitigoda</td></tr>
<tr><td>Ani Peter</td></tr>
<tr><td>Mardi Douglass</td></tr>
<tr><td>Kate Naszradi</td></tr>
<tr><td>Krishnababu K</td></tr>
<tr><td>[[user:Rifaz|Rifaz Nahiyan]]</td></tr>
<tr><td>[[user:Ashickurnoor|Ashickur Rahman]]</td></tr>
<tr><td>Nick Fitzgerald</td></tr>
<tr><td>Anton Kovalyov</td></tr>
<tr><td>Benjamin Pokharel</td></tr>
<tr><td>Michael Comella (:mcomella)</td></tr>
<tr><td>Joanna Mazgaj</td></tr>
<tr><td>Szu-Yu Chen (:aknow)</td></tr>
<tr><td>Vaibhav Bajaj</tr></td>
<tr><td>[https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]</td></tr>
<tr><td>Chihiro Akiba</td></tr>
<tr><td>Kathleen Joyce Domanog</td></tr>
<tr><td>Erika Aurea Gatmaitan</td></tr>
<tr><td>[[user:Tim.babych|Tim Babych]]</td></tr>
<tr><td>Fang, Chiung-Hui (GDH)</td></tr>
</table>

===MozSpace Tour Mountain View===

Want to view the Mozilla Mountain View Space? We have set up a small tour for those people that want to take visit the Mountain View space before the closing dinner and party.

We will be taking a shuttle over to the office (15 minute drive), will stay for enough time to capture some pictures and then walk back. (We will be at the Space for about 25-30 minutes) Then we will board the shuttle and head back to the venue for some dinner.

The tour will be hosted by Sylvie Brossard and a few other Mozillians.

'''Time:''' 5:15-6:15 
''*we will begin boarding the shuttle right after closing session. Departing at 5:15 
'''Meeting Location:''' Main Lobby by the "Ask Me" desk 
'''Need to know:''' We will be back to the venue by 6:30, so we can join the closing dinner and dance party festivities. ''There is limited space available as we have a 55 person shuttle.''

Sign Up Here: (MAX 55 people)
*
*
*

=Toronto=
==Friday ==
=== Real Canadian Superhero Pub Crawl (MOVED TO SATURDAY)===
 
WE HAVE HAD TO MOVE THE PUB CRAWL TO SATURDAY. PLEASE SIGN UP AGAIN IF YOU ARE STILL INTERESTED.
 [[File:WeWantYou2.jpg|200px]] 

=== People in town Friday but not into drinking ===
<table border=1><tr><th>Name</th></tr>
<tr><td>[https://mozillians.org/en-US/u/terrameijar/ Vuyisile Ndlovu] </td></tr>
<tr><td>Jose Junior Villagomez Melgar </td></tr>
<tr><td>[https://mozillians.org/en-US/u/gueroJeff/ Jeff Beatty]</td></tr>
<tr><td>[https://mozillians.org/pt-BR/u/jaymeayres/ Jayme Ayres]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/pmac/ Paul McLanahan]</td></tr>
<tr><td>[https://mozillians.org/es-Mx/u/leonshion/ Miriam León]</td></tr>
<tr><td>[https://mozillians.org/es-Mx/u/Ednah/ Ednah Kiome]</td></tr>
<tr><td>[https://mozillians.org/es-Mx/u/alexfuser/ Alex Fuser]</td></tr>
<tr><td>[https://mozillians.org/es/u/Nex/ Hugo Acosta]</td></tr>
<tr><td>[https://mozillians.org/es/u/lourcastillo/ Lourdes Castillo]</td></tr>
<tr><td>[https://mozillians.org/es/u/psep/ Pablo Sepúlveda]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/ZiggyMaes/ Ziggy Maes]</td></tr>
<tr><td>Lianne Lee</td></tr>
<tr><td>[https://mozillians.org/en-US/u/andreags/ Andrea Guzmán Siu]</td></tr>
<tr><td>Huda Sarfraz</td></tr>
<tr><td>[https://mozillians.org/en-US/u/ajones/ Anthony Jones]</td></tr>
<tr><td>[https://mozillians.org/es/u/aldopy/ Aldo Medina]</td></tr>
<tr><td>[https://mozillians.org/es/u/Rocio/ Rocio Meza]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/orin/ Orin Chen]</td></tr>
</table>

==Saturday==
=== Movie Night ===
On Saturday in '''all three''' locations, we will be holding a movie night complete with big screens and old fashioned pop corn. We will be starting with Code Rush the documentary about the early days of Mozilla.

We may be showing another movie after this, if there is enough interest.

We have plenty of room, but would like to get a count of how many people will be joining us. Please add your name to the sign up below if you are interested.

<table border=1><tr><th>Name</th></tr>
<tr><td>Gloria Meneses</td></tr>
<tr><td>Lianne Lee</td></tr>
<tr><td>Huda Sarfraz</td></tr>
<tr><td>Etienne Segonzac</td></tr>
<tr><td>[https://mozillians.org/en-US/u/terrameijar/ Vuyisile Ndlovu] </td></tr>
<tr><td>Peter Radcliffe</td></tr>
<tr><td>Amira Dhalla</td></tr>
<tr><td>Elsa Rodriguez</td></tr>
<tr><td>Ednah Kiome</td></tr>
<tr><td>Sam Foster</td></tr>
<tr><td>Jay Sullivan</td><tr>
<tr><td>Diane Bisgeier</td></tr>
<tr><td>Marcelo Poli</td></tr>
<tr><td>Carlos Valim "Coragem"</td></tr>
<tr><td>[https://mozillians.org/en-US/u/Joshua-S/ Joshua Smith]</td></tr>
<tr><td>[https://mozillians.org/pt-BR/u/jayme.ayres/ Jayme Ayres]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/pmac/ Paul McLanahan]</td></tr>
<tr><td>[https://mozillians.org/es-Mx/u/leonshion/ Miriam León]</td></tr>
<tr><td>[https://mozillians.org/es-Mx/u/alexfuser/ Alex Fuser]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/bsilverberg/ Bob Silverberg]</td></tr>
<tr><td>Nikhil Marathe</td></tr>
<tr><td>Nicholas Nethercote</td></tr>
<tr><td>[https://mozillians.org/en-US/u/mchris/ Chris Riley]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/ZiggyMaes/ Ziggy Maes]</td></tr>
<tr><td>[https://mozillians.org/en-US/u/Faten/ Faten Ben Thabet]</td></tr>
<tr><td>Zhou Huiling</td></tr>
<tr><td>Hannes Verschore</td></tr>
<tr><td>Bhavana Bajaj</td></tr>
<tr><td>Ben Francis</td></tr>
<tr><td>J. Ryan Stinnett</td></tr>
</table>

{{:Summit2013/Experiences/signups/Toronto}}

=== Mozillians Hockey ===
Hockey is Canada's national winter sport. Sign-up to participate in or watch a shinny hockey game* at the old Maple Leaf Gardens on Saturday, October 5, 9:00pm.

Note: Skating is difficult. This game is open to anyone but it is suggested that only people who have previous skating experience participate in the game itself.

*Shinny hockey, a Canadian tradition, is played with only skates, a helmet, gloves, and a stick. There are no goalies, no body contact, and no raising the puck or slap-shots.

What you need to know:

We will be meeting in the lobby of the hotel at 8:00pm. We'll walk to the rink and the game will start at 9:00pm.

[https://mozillians.org/lmandel Lawrence Mandel] and [https://mozillians.org/lsblakk Lukas Blakk] have stepped up to help drive this. Please ping them with additional questions.

'''Sign up here!'''
https://docs.google.com/forms/d/1fhE8oVSAkk5gN9-pfoQ-lCJjQEO2My3kup2NcuAagW0/viewform

=== Nuit Blanche Stroll ===

From 6:51pm to sunrise on Sunday, Toronto will be a large exhibit hall of contemporary art. [http://www.scotiabanknuitblanche.ca/ Nuit Blanche] is an annual art exhibit with hundreds of art projects and installations in the streets of the city.

# Jay Sullivan
# Vuyisile Ndlovu
# Nicholas Nethercote
# Faten Ben Thabet
# Lianne Lee
# Huda Sarfraz
# Ben Francis
# Aldo Medina
# Rocio Meza
# J. Ryan Stinnett
# Ricardo Pontes
# Bhavana Bajaj
# Ricardo Sato
# Carlos Valim "Coragem"
# Joanne Nguyen
# Winnie Aoieong
# Michael Coates
# Jesebel Kim
# Jim Cook
# Sam Foster

=== Real Canadian Superhero Pub Crawl (NEW DATE) ===
[[File:WeWantYou2.jpg|right]] Sure, Canada is a fun clean country filled with really nice people. And, as some know, Toronto is the "New York" of Canada, crammed with exciting architecture, extremely diverse culture, and Smarties.
 
'''BUT.... '''

When the sun sets on this northern community, there arises a seedy side to Canada's Gotham city. Mozilla is recruiting a brave set of individuals to help us clean up the streets, one bar at a time. This isn't a job for the weak or vertically impaired. You must have a strong constitution and some comfortable walking shoes to participate.

'''Sign up NOW''' for the one and only Real Canadian Superhero Pub Crawl. We will be walking from the Sheraton Center around the downtown area and back to the hotel, pub hopping the entire way. We will provide masks and other paraphernalia, you bring your favorite super hero t-shirt (or any brightly colored t-shirt you have), as well as your super power, and of course, the super strength to finish the crawl. BAM!

Gifts and prizes for anyone who brings their own costume, and/or for anyone who is willing to wear tights. '''KAPOW!'''

Here's some juju to help think of great alter egos: [http://en.wikipedia.org/wiki/List_of_The_Incredibles_characters#Other_superheroes GET ALTER EGO IDEAS NOW!]

; '''Feedback or questions?''' : Email this mild mannered guy: [https://mozillians.org/en-US/u/phundal/ phundal@mozilla.com]

; '''Note:''': The drinking age is 19 in Ontario. Please plan on bringing photo ID, as they will definitely check at every bar!
<table class="wikitable" border=0 valign="top">
<tr><td>
; ''' Super Sign up sheet ''': Current maximum is 35, but if there is strong interest, we can look to extend.
<table class="wikitable" border=1><tr><th>#</th><th>Name</th><th>Alter Ego</th></tr>
<tr><td>1</td><td>[https://mozillians.org/en-US/u/phundal/ Patrick Hundal]</td><td>Ale-inhaler</td></tr>
<tr><td>2</td><td>Maya Barrow</td><td>Margareeta</td></tr>
<tr><td>3</td><td>[https://mozillians.org/en-US/u/rseiji/ Ricardo Sato]</td><td>Satozilla</td></tr>
<tr><td>4</td><td>[https://mozillians.org/en-US/u/jaydson/ Jaydson Gomes]</td><td>Quail Man</td></tr>
<tr><td>5</td><td>Patrick Cloke</td><td></td></tr>
<tr><td>6</td><td>[https://mozillians.org/en-US/u/Urcu/ Eduardo Urcullú Madrid]</td><td>Urcumeitor</td></tr>
<tr><td>7</td><td>[https://mozillians.org/en-US/u/felipenmoura/ Felipe N. Moura]</td><td>Mulder</td></tr>
<tr><td>8</td><td>Ricardo Panasggio</td><td>Super Sober</td></tr>
<tr><td>9</td><td>Evelyn Urcullú</td><td></td></tr>
<tr><td>10</td><td>Carlos Valim "Coragem"</td><td>Fox from tha ghetto</td></tr>
<tr><td>11</td><td>[https://mozillians.org/en-US/u/lasr21/ LASR21 a.k.a Luis Sanchez]</td><td>Mexican Panda</td></tr>
<tr><td>12</td><td>[https://mozillians.org/en-US/u/rdaub/ Ralph Daub]</td><td>Snow-Dance</td></tr>
<tr><td>13</td><td>[https://mozillians.org/en-US/u/prixon/ Matej Priteržnik]</td><td>Black Ma-jek</td></tr>
<tr><td>14</td><td>[https://mozillians.org/en-US/u/ricardopontes/ Ricardo Pontes]</td><td>Chuckzilla</td></tr>
<tr><td>15</td><td>Julien Wajsberg</td><td>Flashberg</td></tr>
<tr><td>16</td><td>Arzhel Younsi</td><td>Super Celtic</td></tr>
<tr><td>17</td><td>Paul Adenot</td><td>Bierman</td></tr>
<tr><td>18</td><td>Manuel Camacho</td><td>GREEN</td></tr>
<tr><td>19</td><td>Romina Guerra</td><td>Super PINK</td></tr>
<tr><td>20</td><td>[https://mozillians.org/en-US/u/keppelen/ Giovanni Keppelen dos Santos]</td><td></td></tr>
<tr><td>21</td><td>[https://mozillians.org/en-US/u/deluna/ Bernard de Luna]</td><td></td></tr>
<tr><td>22</td><td>[https://mozillians.org/en-US/u/andregarzia/ Andre Alves Garzia]</td><td>Drunken Fennec</td></tr>
<tr><td>23</td><td>[https://mozillians.org/en-US/u/leobalter/ Leo Balter]</td><td>The Mozillator</td></tr>
<tr><td>24</td><td>[https://mozillians.org/en-US/u/gabriela.oliv/ Gabriela Oliveira]</td><td>Chuchu Girl</td></tr>
<tr><td>25</td><td>[https://mozillians.org/en-US/u/dricupello/ Adriano Cupello]</td><td></td></tr>
<tr><td>26</td><td>Andrea Balle</td><td></td></tr>
<tr><td>27</td><td>[https://mozillians.org/en-US/u/enzomatrix/ Marcelo Poli]</td><td></td></tr>
<tr><td>28</td><td>[https://mozillians.org/en-US/u/alex_mayorga/ alex_mayorga]</td><td>The orange Zorro</td></tr>
<tr><td>29</td><td>[https://mozillians.org/en-US/u/orin/ Orin Chen]</td><td></td></tr>
<tr><td>30</td><td>Maicon Ferreira</td><td></td></tr>
<tr><td>31</td><td>Jay Sullivan</td><td></td></tr>
<tr><td>32</td><td>[https://mozillians.org/en-US/u/winniea/ Winnie Aoieong]</td><td></td></tr>
<tr><td>33</td><td>Michael Coates</td><td></td></tr>
<tr><td>34</td><td>[https://mozillians.org/en-US/u/jnguyen/ Joanne Nguyen]</td><td></td></tr>
<tr><td>35</td><td>Jim Cook</td><td></td></tr>
<tr><td>36</td><td>Jesebel Kim</td><td></td></tr>
<tr><td></td><td>Below is waiting list</td><td></td></tr>
<tr><td>37</td><td></td><td></td></tr>
<tr><td>38</td><td></td><td></td></tr>
</table>
</td>
<td valign="top">
;Start time: We will begin at 7:30pm in the Sheraton lobby, and we will spend about 30min at each pub. If you are playing catch-up from the CN Tower, estimate about 45min (total) for each pub.
 
;'''List of pubs on tour (not finalized...)''':[http://goo.gl/maps/Nd1R2 Google map of pubs]
 
;Fionn MacCool's: 181 University Avenue, Toronto, ON +1 416-363-1944, http://primepubs.com‎
;Earls Kitchen & Bar: 150 King St W #100, Toronto, ON, +1 416-916-0227, http://earls.ca
;Irish Embassy Pub and Grill: 49 Yonge Street, Toronto, ON +1 416-866-8282, http://irishembassypub.com‎
;P.J. O'Brien Irish Pub & Restaurant: 39 Colborne Street, Toronto, ON +1 416-815-7562, http://pjobrien.com‎
;C'est What : 67 Front Street East, Toronto, ON +1 416-867-9499, http://cestwhat.com‎
; The Jason George : 104 Front Street East, Toronto, ON +1 416-363-7100, http://thejasongeorge.ca‎
;The Richmond Rogue: 284 Richmond Street East, Toronto, ON +1 416-868-9595, http://therichmondrogue.com‎
;New Windsor Tavern: 124 Church Street, Toronto, ON +1 416-364-9698, http://mcveighspub.com‎
</td></table>

==Sunday==

===MozSpace Tour===

Want to view the Mozilla Toronto Space? We have set up a small tour for those people that want to take visit the Toronto space before the closing dinner and party.

We will be walking over to the office (15 minute walk), will stay for enough time to capture some pictures and then walk back. (We will be at the Space for about 25-30 minutes)

The tour will be hosted by a few Mozillians from the Space.

'''Time:''' 5:15-6:15 (we start walking back at 6:00) 
'''Meeting Location:''' Main Lobby by the "Ask Me" desk 
'''Need to know:''' We will be back to the venue by 6:30, so we can join the closing dinner and dance party festivities.

Sign Up Here:
*[https://mozillians.org/es/u/Urcu/ Eduardo Urcullú Madrid]
*
*

=Brussels=
==Friday ==
=== Jellyfishing ===
OMG Jellys! Yes, you read that right! Our very own [https://mozillians.org/en-US/u/rlord/ Rob Lord] is going to instruct and lead a group of Mozillians to Jelly Fish through the cobble streets of Brussels.
:Want to see more, check out this '''[https://vimeo.com/35285151 video]'''

Sign up here, limit is '''20''' people, which means we are '''full'''.
# Mohamed El Sharnoby
# Janet Swisher
# Jeff Griffiths
# Aashish Jagini
# Onur Avsar
# Piniel Romulia Hasibuan
# Mubiru Jonathan
# André Fiedler
# Ilana Segall
# William Reynolds
# Laura Forrest
# Fabio Magnoni
# Wei Li
# Yanfang Liu
# Sharon Xiaoyun Yang
# Curtis Koenig
# Gervase Markham
# Antoine Turmel
# Avinash Kundaliya
# Justin O'Kelly

=== Dancing! Fun! ===
Hi, [https://mozillians.org/en-US/u/kumar/ Kumar McMillan] here. While I'm not working on Firefox OS payments I'm most likely DJing in my living room, at some dance party or bar, etc. My good friend and Bruxelles local [http://lowdjo.com/ Lowdjo] invited me to play records with him at [https://www.facebook.com/pages/Caf%C3%A9-Central/143434702389318 Le Cafe Central] while I'm out there. No need to sign-up, just stop by if you're interested in dancing to disco, boogie, 80s funk, or whatever else we feel like playing.

* Time: 11pm to 4am (we'll be DJing the entire time)
* Location: [https://www.facebook.com/pages/Caf%C3%A9-Central/143434702389318 Le Cafe Central] (includes full bar)
* Address: [http://www.bing.com/maps/default.aspx?v=2&pc=FACEBK&mid=8100&rtp=adr.~pos.50.847777198698_4.3477700156474_Caf%C3%A9+Central_14+rue+borgwal%2C+1000+Brussels%2C+Belgium&cp=50.847777198698~4.3477700156474&lvl=16&sty=r&rtop=0~0~0~&mode=D&FORM=FBKPL2&mkt=en-US 14 rue borgwal, 1000 Brussels, Belgium]

Sign-ups: N/A

==Saturday==
=== Bikram yoga ===

We'll attend a [http://en.wikipedia.org/wiki/Bikram_Yoga Bikram yoga] (hot yoga) class at [http://www.fbyci.com/brussels/index.htm the Brussels school]. Please sign up if you'd like to attend.

It looks like we have enough people to make this happen. Woot!

'''Time:''' 8:00pm Local Time 
'''Meeting Location:''' Meet by "Ask Me" desk at 19:15 and we will travel to the school from there. 
'''Need To Know:''' Try not to eat too much just before going to class (eat lightly for 2h before the class starts). Bring light clothing (men can do just shorts or add a T-shirt, women can wear shorts and a top), it gets very sweaty.

#Dirkjan Ochtman
#John Baptist Ochieng
#Nicholas Grammater
#Jonathan Watt
#Shane Tomlinson
#Jovan Ssebaggala
#Giorgio Maone
#Reed Loden
#MA Darche
#Rodrigo Waters
#Denish Okidi

=== Movie Night ===

On Saturday in '''all three''' locations, we will be holding a movie night complete with big screens and old fashioned pop corn. We will be starting with Code Rush the documentary about the early days of Mozilla.

We may be showing another movie after this, if there is enough interest.

We have plenty of room, but would like to get a count of how many people will be joining us. Please add your name to the sign up below if you are interested.

*Gene Wood
*Mihnea Dobrescu-Balaur
*Aashish Jagini
*Netha Hussain
*Liz Compton
*Piniel Romulia Hasibuan
*Mubiru Jonathan
*André Fiedler
*Antoine Turmel
*Avinash Kundaliya
*Justin O'Kelly
*David Rajchenbach-Teller
*Robyn Chau
*Dirkjan Ochtman
*John Baptist Ochieng
*Joyce Nalwadda
*Dave Hunt
*Felix Klock
*William Dorffer
*Sheeri Cabral
*Luca Greco
*Alex Fuser
*Zach Carter
*Laura Thomson
*Jonathan Watt
*Shane Tomlinson
*Dejan Strbad
*Jordan Lund
*Reed Loden
*Aki Laaksovirta
*Flore Allemandou
*Monique Brunel
*Majda Nafissa Rahal
*Rubén Martín
*William Duyck
*RJ Hsiao
*Achraf Fouwad
*Denish Okidi

=== La Bier Circus ===
Saturday Beer geek trip - http://www.bier-circus.be/beer-catalog/. This place is small, so let's not pile on! Meet there at 7:30 - it's a ten-minute walk from SQUARE. The Mozilla swag will, doubtless, make us obvious.

* Dustin J. Mitchell (organizer)
* Rail Aliiev
* Adrian Fernandez
* Monique Brunel
* Kris Maglione
* Andreas Wagner
* Zach Beauvais
* Jorge Villalobos
* Daniel Holbert
* Rodrigo Waters
* Achraf Fouwad
* Johannes Vogel

=== Bar Delirium ===

We have secured 2 drink vouchers for beer and soft drinks for all those who have signed up below. Get ready to enjoy a real pub experience!

'''Time:''' 7:45-10:00pm 
'''Meeting Location''': Please pick up your drink tickets from the "Ask Me" desk anytime between 7:30-7:45pm. We will walk to Delirium at 7:45pm. 
'''Need To Know:''' Drink vouchers can be used for beer and soft drinks only. You must pick up your drink vouchers before you head to Delirium. 

''(List sorted to remove duplicates)''
*Aashish Jagini
*Adam Newman
*Adrian Fernandez
*Alba González
*Aleksandra Uzelac
*Alex Fuser
*Alex Gibson
*Alexis Metaireau
*Alison Wheeler
*Altin Ukshini
*Amy Tsay
*Andreas Kleinert
*Andreas Wagner
*André Fiedler
*Andy McKay
*Antoine Turmel
*Ardian Haxha
*Arpad Borsos
*Austin King
*Balazs Koren
*Bella Su
*Ben Kero
*Berni Melero
*Bree Tipper
*Chris AtLee
*Chris More
*Chris Turra
*Corey Shields
*Curtis Koenig
*Dan Maher
*Dave Hunt
*David Rajchenbach-Teller
*Dejan Binder
*Derek Moore
*Dietrich Ayala
*Dustin J. Mitchell
*Ed Lim
*Elio Qoshi
*Estela Liu
*Fabio Magnoni
*Fabricio Zuardi
*Frank Wein
*Frederik Braun
*Gemma Petrie
*Gene Wood (+1 for Friday)
*Gent Thaci
*Georg Fritzsche
*Gina Yeh
*Giorgio Maone
*Greg Cox
*Gregory Szorc
*Hagen Halbach
*Hernán Rodríguez Colmeiro
*Ilana Segall
*Irina Parievsky
*JB Ochieng
*Jeff Griffiths
*Jennifer Hayashi
*Jennifer Morrow
*Jessica Jong
*Jessilyn Davis
*Joe Cheng
*John Hesling
*Jon Coppeard
*Jorge Villalobos
*Jovan Ssebaggala
*Julen Ruiz Aizpuru
*Julien Vehent
*Justin Dow
*Jürgen Berg
*Kannan Vijayan
*Karsten Düsterloh
*Kris Maglione
*Konstantina Papadea
*Laura Forrest
*Laura Thomson
*Lizz Noonan
*Luca Greco
*Lucas Rocha
*Malini Das
*Marc Schifer
*Mark Côté
*Martin Creutziger
*Mathieu Laurent
*Michelle Marovich
*Michael Bebenita
*Mihnea Dobrescu-Balaur
*Mubiru Jonathan
*Naveed Ihsanullah
*Nicholas Grammater
*Niko Visnjic
*Nino Vranešič
*Onur Avsar
*Oskar Ivanić
*Phoebe Chang
*Pierre-Louis Augey
*Raivis Dejus
*Redon Skikuli
*Reed Loden
*Robert Wood
*Robyn Chau
*Rodrigo Waters
*Rubén Martín
*Sal Espinosa
*Saša Jakovljević
*Shane Caraveo
*Shane Tomlinson
*Shelly Lin
*Shyam Mani
*Simon Bennetts
*Simon Sapin
*Sokol Dollani
*Sébastien Barbieri
*Tauni Oxborrow (+1 for Friday)
*Thierry Régagnon
*Théo Chevalier
*Till Schneidereit
*Tom Schuster
*Toni Hermoso
*Ty Flanagan
*Van Le
*Vien Doan
*Vit lai
*William Duyck
*William Reynolds
*Wilson Guaraca
*Zac Campbell
*Zach Carter
*Dejan Strbad
*Ana-Maria Antolovic
*RJ Hsiao
*Achraf Fouwad
*Denish Okidi

=== Chocolate Making (7:30pm) ===
Mozillians in Brussels, you are in for a real treat! If you like making chocolate, or just like chocolate tasting we've got two options for you!
On Saturday, one of Brussels top chocolatiers, Laurent Gerbaud will be conducting a chocolate making class (tasting also included) for the first 25 Mozillians to sign up.
If you'd like to read more about them, check out them out [http://www.chocolatsgerbaud.be here]
For those that are interested in tasting the many types of chocolate Brussels has to offer, please sign up for the Sunday session.

Space is limited, '''25''' spots available and is now '''FULL'''

# Marcia Knous
# Doris Coleman
# Mary Trombley
# Tanner Young
# Krupa Raj
# Larissa Co
# Gemma Petrie
# Fernando García Gómez
# Elio Qoshi
# Redon Skikuli
# Sokol Dollani
# Altin Ukshini
# Gent Thaci
# Ardian Haxha
# Berni Melero
# Mavis Ou
# Vien Doan
# Jennifer Hayashi
# Fabricio Zuardi
# Benjamin Sternthal
# Mohamed El Sharnoby
# Maureen Hanratty
# Sébastien Desvignes
# Wilson Guaraca
# James Graham

=== Chocolate Tasting ONLY (8:30pm) ===
Space is limited, '''25''' spots available:
# Marco Zehe
# Sébastien Barbieri
# Mathieu Laurent
# Ioana Chiorean
# Kris Maglione
# Jorge Villalobos
# Florin Bogdan Strugariu
# Bartosz Piec
# Leo McArdle
# Yousef Alam
# Jan Bambach
# William Reynolds
# Laura Forrest
# Peipei Cheng
# Yanfang Liu
# Wei Li
# Phoebe Chang
# Jessica Jong
# Sharon Xiaoyun Yang
# Aleksandra Uzelac
# Oskar Ivanic
# Dejan Binder
# Saša Jakovljevic
# Nino Vranešic
# Aashish Jagini

===Chocolate Waiting List===
#Avinash Kundaliya
#Pauline Proffett
#Robyn Chau
#Lizz Noonan
#Alexis Metaireau
#Thierry Régagnon
#Jovan Ssebaggala
#JB Ochieng
#Laura Thomson
#Niko Visnjic
#Julen Ruiz Aizpuru
#Pierre-Louis Augey
#Hiroyuki Ikezoe
#Daisuke Akatsuka
#Tomoya Asai
#Giorgio Maone
#Jordan Lund
#Adrian Fernandez
#Joe Cheng
#Majda Nafissa Rahal
#Rubén Martín
#Konstantina Papadea
#Daniel Holbert
#Denish Okidi

==Sunday==
=== Chocolate Tasting (5pm) ===
''details above''. Space is limited, '''25''' spots available and is now '''FULL'''.

# Krupa Raj
# Marcia Knous
# Gene Wood
# Fabricio Zuardi
# Wilson Guaraca
# Mavis Ou
# Mohamed El Sharnoby
# Jean Collings
# Jessilyn Davis
# Richard Marti
# Doris Coleman
# Janet Swisher
# Kim Ludvigsen
# Ana-Maria Antolovic
# aleth
# John Bevan
# Mihnea Dobrescu-Balaur
# Alexandros Mioglou
# Aashish Jagini
# Tauni Oxborrow
# Netha Hussain
# Ziga Milek
# Dustin J. Mitchell
# Fabio Magnoni
# Alison Wheeler

=== Chocolate Tasting (6:15pm) ===
Also full.
# Tom Schuster
# Onur Avsar
# Piniel Romulia Hasibuan
# Zhenshuo Fang
# Mubiru Jonathan
# Gina Yeh
# Bella Su
# Shelly Lin
# Vit lai
# Balazs Koren
# Marco Zehe
# Ty Flanagan
# Emily Goligoski
# Chloe Varelidi
# Bree Tipper
# Irina Parievsky
# Karen Rudnitski
# Hernán Rodríguez Colmeiro
# Kristin Baird
# Tobias Markus
# Brian Birtles
# Kevin Brosnan
# Allison Naaktgboren
# Simon Sapin
# Curtis Koenig

Summit2013/Experiences/signups

2013-09-23T19:30:48Z

Sfoster: /* Movie Night */

Firefox/Windows 8 Integration

2013-08-22T22:42:33Z

Sfoster: /* Crash Testing */

== Wiki ==

* [https://wiki.mozilla.org/Firefox/Metro Metro Project] - meeting times, bug lists, project goals, team info, etc.
* [[Firefox/Features|General Firefox Product Feature Tracking]] - Firefox feature tracking.
* [https://wiki.mozilla.org/Firefox_Metro_UI Firefox Metro UI wiki] - including comp work and UX bug tracking.
* [[Windows8|Metro Project Status]] - not really in use.
* [[Windows_8_Integration]] - General 3rd party browser collaboration page dedicated to overview, architecture, and challenges for vendors. Early research with Google.
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208;query_format=advanced;list_id=2566504 Windows 8 (desktop)]
* [[Firefox/Windows 8 Metro Style Guides]] - coding standards and UI guidelines

== Useful Bugzilla Queries ==
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;list_id=5745479 Win8 Metro]

* Metro Firefox complete list

[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notsubstring;list_id=5756053;field0-1-0=status_whiteboard;field0-0-0=status_whiteboard;resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;value0-2-0=MetroV1;value0-1-0=feature%3Dstory;field0-2-0=short_desc;type0-0-0=notsubstring;value0-0-0=feature%3Depic;type0-2-0=notsubstring Win8 Metro]

* Metro Firefox complete list
* Minus feature=story, epic, and MetroV1

[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notsubstring;value0-7-0=feature%3Ddefect;field0-3-0=status_whiteboard;type0-1-0=notequals;type0-5-0=notsubstring;value0-5-0=feature%3Dwork;value0-4-0=feature%3Dstory;list_id=5745413;field0-1-0=blocked;field0-0-0=blocked;type0-4-0=notsubstring;resolution=---;field0-6-0=status_whiteboard;value0-3-0=feature%3Depic;field0-7-0=status_whiteboard;query_format=advanced;value0-2-0=MetroV1;value0-6-0=feature%3Dchange;value0-1-0=842686;type0-3-0=notsubstring;field0-2-0=short_desc;field0-5-0=status_whiteboard;field0-4-0=status_whiteboard;type0-6-0=notsubstring;type0-0-0=notequals;value0-0-0=841214;type0-2-0=notsubstring;product=Firefox%20for%20Metro Untagged Bugs]
* Not blocked by various pm triage tracking bugs
* Whiteboard does not contain feature=epic, work, change, defect, story
* Summary does not contain 'MetroV1'

[https://bugzilla.mozilla.org/buglist.cgi?chfield=%5BBug%20creation%5D;chfieldfrom=-72h;known_name=Last%20Three%20Days;columnlist=opendate%2Cbug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc;resolution=---;op_sys=Windows%20XP;op_sys=Windows%20Vista;op_sys=Windows%207;op_sys=Windows%208;op_sys=Windows%208%20Metro;query_based_on=Last%20Three%20Days;chfieldto=Now;query_format=advanced;product=Firefox%20for%20Metro;list_id=5745420 Last three days]

* Bugs filed against product Metro Firefox in the last three days

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4351876;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;product=Core;product=Toolkit;product=www.mozilla.org Platform]

* Core, Toolkit, mozilla.org

== Getting Involved ==
Contact Brian Bondy with questions (bbondy on [http://irc.mozilla.org IRC]). The Windows 8 integration team can be found in in #windev.

=== Bugzilla ===

Please file front end bugs under the product [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20for%20Metro Firefox for Metro]. Back end bugs should be filed in the appropriate Platform component.

=== Front End Windows 8 Development ===

* To contribute to front end bugs, you will use: JS, CSS, XUL, XBL
* You do not actually need Windows 8 to work on the front end code
* Follow the steps in the Metro Builds section below to get setup
* The front end code is located in browser/metro
* Style guidelines of all types can be found on https://wiki.mozilla.org/Firefox/Windows_8_Metro_Style_Guides
* the front end code is to be literally a user friendly. it helps developers to get understood easily.

=== Platform Integration Windows 8 Development ===

* To contribute to platform integration bugs, you will use: C++
* You do need Windows 8 to work on the platform integration code
* You can obtain a 90 day free Windows 8 evaluation for developers from Microsoft
* Follow the steps in the Metro Builds section below to get setup
* The platform integration code is located in widget/windows/winrt
* You can find Windows 8 platform integration bugs here http://goo.gl/B0Xjo or by doing an advanced bugzilla search for: OS = Windows 8 Metro, Product = Core, Component = Widget: Win32

== Metro Builds ==

=== Nightly Builds ===

Update: 6/24/2013

Nightly builds are now being generated on mozilla-central.

Nightly builds off the mozilla-central repository are currently available in the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/ Firefox build archives].

To set these builds up:

* Install the browser using the latest installer
* Open the desktop browser - when the default browser check occurs, select yes to set Firefox as the default. You should also receive a Windows prompt, select Nightly. This will associate Firefox with various protocol handlers and create the Firefox tile.
* To set file handler associations use Window's Control Panel for default program associations. (Options -> Advanced -> General and click the default browser button at the bottom to open this panel.)

For more detailed help on installing / setting the browser as the default, visit the [https://support.mozilla.org/en-US/kb/how-do-i-install-windows-8-metro-style-firefox Metro Firefox support page].

=== Nightly Crash Reports ===

[https://crash-stats.mozilla.com/topcrasher/byversion/MetroFirefox/22.0a1/7 Firefox for Metro]

=== Switching Default Browsers ===

This can be a little tedious when working with multiple builds / installs on a single device. Steps:

* Close Firefox both in Metro and on Desktop
* Open Control Panel's default programs and set IE as the default
* With debug builds: run the resulting firefox.exe on the desktop and set as the default through Options menu -> Advanced -> General tab -> Make default button.
* For release builds: run the resulting firefox.exe on the desktop and click yes to the default settings dialog, then select 'Nightly' in the Windows 8 prompt.
* In Control Panel's default programs, set firefox as the default browser.

To confirm the right browser is set, launch the browser in Metro, switch to desktop, open task manager, right-click the Firefox process, and select open file location.

Note pinned taskbar shortcuts can't be trusted to open the right browser.

=== Zip Builds ===

Zip installs from daily checkins are currently available on the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/ Firefox build archives].

To install:

* Download the newest firefox-(rev).0a1.en-US.win32.zip to your Win8 device
* Unpack the main firefox folder to a suitable location
* Run firefox.exe on the desktop
* If prompted by Windows, select Nightly/Aurora/Firefox as the default.
* Open Options -> Advanced -> General and click the "Make Firefox the default browser" button. This will open Windows Control Panel where you will need to select the channel build you are testing and set the defaults.

=== Building Locally ===

Updated 5/21/2013

* Install Visual Studio 2010 or 2012.
* Install [https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Windows_Prerequisites MozillaBuild] (version 1.7 required)
* Install the [http://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx Windows 8.0 SDK]
* Install [http://www.microsoft.com/en-us/download/confirmation.aspx?id=6812 DirectX SDK (June 2010)]

* For VC 2010 builds:
** Modify the the following header in the sdk:
<pre>
C:\Program Files (x86)\Windows Kits\8.0\Include\winrt\asyncinfo.h

line 67:

enum class AsyncStatus {

to

enum /*class*/ AsyncStatus {
</pre>

If you use both VC 2010 and VC 2012 (or plan to install VC 2012 in the near future) you might want to instead use the following patch, which reverts to the original code under VC 2012 and later:
<pre>
--- asyncinfo.h.orig 2013-05-21 08:47:49 -0400
+++ asyncinfo.h 2013-05-21 08:48:55 -0400
@@ -58,17 +58,21 @@
/* interface __MIDL_itf_asyncinfo_0000_0000 */
/* [local] */

// Microsoft Windows
// Copyright (c) Microsoft Corporation. All rights reserved.
#pragma once
#ifdef __cplusplus
namespace ABI { namespace Windows { namespace Foundation {
+#if defined (_MSC_VER) && _MSC_VER >= 1700
enum class AsyncStatus {
+#else
+enum AsyncStatus {
+#endif
Started = 0,
Completed,
Canceled,
Error,
};
} } } // ABI::Windows:::Foundation
using ABI::Windows::Foundation::AsyncStatus;
#ifndef _HIDE_GLOBAL_ASYNC_STATUS
</pre>

* For Express versions of VS:
** Install [http://www.microsoft.com/en-us/download/details.aspx?id=11800 the Windows Driver Toolkit, version 7.1] - Version 7.1 is needed because it contains the necessary ATL headers that express VS lacks.
** Add the following to start-msvc*.bat file near the end just before the line that reads cd "%USERPROFILE%" (assumes WinDDK was installed in "C:\WinDDK\7600.16385.1"):
<pre>
set "INCLUDE=C:\WinDDK\7600.16385.1\inc\atl71;%INCLUDE%"
set "LIB=C:\WinDDK\7600.16385.1\lib\ATL\i386;%LIB%"
</pre>

* [https://developer.mozilla.org/en-US/docs/Simple_Firefox_build#Get_the_source Check out mozilla-central]. Make sure the obj directory has "Modify" permissions given to the current user.
* Create a standard browser .mozconfig file with the options you prefer and add

<pre>
ac_add_options --enable-metro
</pre>

* [https://developer.mozilla.org/en-US/docs/Simple_Firefox_build#Building Build Firefox].

At this point, you should be able to launch the metro browser on the desktop using a command line switch:

<pre>
(obj)/dist/bin/firefox.exe -metrodesktop
</pre>

To register local builds as the default browser:

* For debug builds: run the resulting firefox.exe on the desktop and set as the default through Options menu -> Advanced -> General tab -> Make default button.
* For release builds: run the resulting firefox.exe on the desktop and click yes to the default settings dialog, then select 'Nightly' in the Windows 8 prompt.
* Open up Control Panel -> Default Programs. You should see 'Metro Firefox' in the list of applications.
* Set all Metro Firefox defaults in Default Programs.

At which point you should have a Firefox tile in Win8 that launches the browser.

Note, for debug builds, see [[Firefox/Windows_8_Integration#Logging_Assertions]].

=== Desktop Launch ===

To launch within the metro experience follow the registration steps above. To launch the metro front end UI using the win32 widget backend on the desktop (including non-Windows-8 devices) use the -metrodesktop command line option:

<pre>(path to firefox build)/firefox.exe -metrodesktop</pre>

To set things up such that you can test touch input on the desktop - flip the 'metro.debug.treatmouseastouch' to true in /browser/metro/profile/metro.js.

Note on the desktop we use the desktop's Win32/Widget backend. This can behave differently from the Win8 WinRT backend. The translational layer for Win32 events is location in /browser/metro/content/base/input.js.

=== Testing ===

[https://developer.mozilla.org/en-US/docs/Browser_chrome_tests Browser-chrome tests] for Metro Firefox are located in [http://hg.mozilla.org/projects/elm/file/default/browser/metro/base/tests/ browser/metro/base/tests]. The tests run in the Metro environment; Windows 8 is required.

Currently, some of the selection tests may fail (specifically, browser_selection_frame_textarea.js) if the device and CSS pixels are out of sync. To solve this, you may need to change the following pref in about:config to the following value.

layout.css.devPixelsPerPx = 1.0 (default is -1.0, which makes Firefox autoscale CSS pixels)

To start the tests, run the following command in the mozilla-build shell, at the top level of your obj-dir:

pymake mochitest-metro-chrome

The Metro browser will launch, run the tests and exit. Any failures will be printed to the console. The complete test log will be written to the file <code>mochitest-metro-chrome.log</code> in the objdir.

=== Building on Linux or Mac OS X ===

You can use the ''--enable-metro'' configure option and the ''-metrodesktop'' command-line flag to build and run the Metro UI on other platforms too. For details, see [http://limpet.net/mbrubeck/2012/09/19/metro-firefox-without-windows.html Metro Firefox without Windows 8].

On Mac, you might need to run "./mach build browser" after your build completes. For details, see {{bug|847807}}.

* there is a problem with html5 EMBED tag. '''an EMBED tag is basically to play media files.''' but we can't use this on mac.

=== Logging Assertions ===

When you're running Metro Firefox with --enable-debug, there will be assertion failure messages that show up in the console. The following environment variable is assumed for the Metro environment:

<pre>
XPCOM_DEBUG_BREAK=warn
</pre>

=== Remote Debug Output ===

NSPR logging can be dumped to OutputDebugString using the NSPR_LOG_FILE environment variable:

<pre>
NSPR_LOG_FILE=WinDebug
</pre>

To log NS assertions and warnings in debug builds add the nsDebug log module:

<pre>
NSPR_LOG_MODULES=nsDebug:4
</pre>

<strike>{{bug|762519}}</strike> was filed on getting javascript's dump output going to OutputDebugString as well.

=== DOM Inspector ===

Getting DOM Inspector attached to builds running on the desktop takes a few tweaks.
* Install the dom inspector addon (if you do not have it already) on your desktop firefox
* Copy the 'inspector@mozilla.org' folder under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory. (Example: C:\Users\Brian\AppData\Roaming\Mozilla\MetroFirefox\Profiles\amrcb8eg.default\extensions)
* add an entry in inspector's install.rdf file for metrofx and make sure the maxVersion is set correctly.

<pre>
<em:targetApplication>
<Description>
<em:id>{99bceaaa-e3c6-48c1-b981-ef9b46b67d60}</em:id>
<em:minVersion>1.0a1</em:minVersion>
<em:maxVersion>19.0a1</em:maxVersion>
</Description>
</em:targetApplication>
</pre>

* Add the [https://developer.mozilla.org/en/XULRunner_tips startDOMi function] to /browser/metro/base/content/browser.js.
* Add a call to startDOMi() below the BrowserUI.init() call.
** If you start the browser and see a blank screen with your patch containing startDOMi() applied, it probably means the extension hasn't been enabled/installed properly. Often its the last step of flipping values.
* Tweak the following extension prefs in metro.js:
<pre>
pref("extensions.autoDisableScopes", 15);
pref("extensions.minCompatibleAppVersion", "4.0");
pref("extensions.strictCompatibility", false);
</pre>

* The extensions.json file will be created the first time MetroFirefox is run and discovers the inspector@mozilla.org extension content in the profile, but you have to flip a couple of values to make it actually work. Set the 'active' property to boolean true and the userDisabled property to boolean false.

=== Venkman Debugger ===

(10/5/12 - Note, since we've changed the app id, this probably doesn't work.)

* Copy the '{f13b157f-b174-47e7-a34d-4815ddfdfeb8}' xpi under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory.

* Launch the browser with the '-venkman' command line option.

=== JS Shell ===

For debugging the ede js shell and javascript console are available on the app bar in desktop builds.

=== Crash Testing ===

To test the Crash Reporter UI and other crash-related behavior, you can make use of install the [http://people.mozilla.com/~tmielczarek/crashme/ Crash Me addon] (sources are on [http://code.google.com/p/crashme/ Google Code].) This extension is already Metro Firefox ready, so you just need to follow similar steps as for the DOM Inspector to enable it.
* Install the Crash Me addon (if you do not have it already) on your desktop firefox
* Copy the 'crashme@ted.mielczarek.org' folder under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory. (Example: C:\Users\Brian\AppData\Roaming\Mozilla\MetroFirefox\Profiles\amrcb8eg.default\extensions)
* - OR - you can just download and unzip the .xpi file into a crashme@ted.mielczarek.org folder in your profile extensions directory
* To allow discovery and install of add-ons, set extensions.autoDisableScopes to 15, either via your local metro.js or in about:config
* If you are using a local build, you may need to edit the metroapp.ini (generated from the metroapp.ini.in template) to ensure the Crash Reporter Enabled=1 flag is set.

To use, you'll find a new "Crash Now!" entry in the Settings charm. Tap it to crash.

=== WinRT Compiler Generated Code ===

Compiler switches:
* /d1ZWtokens - dump C++ code generated code for C++/CX.
* /d1reportAllClassLayout - dump class layouts
* /d1reportSingleClassLayoutXXX - where XXX performs substring matches against the class name.

=== Remote Debugging with a VM ===

(This was last tested with the Win8 RP)

Setup steps -

* create a new drive for vm, clone src there, build. obj dir should also be on this drive.
* Enable sharing on the drive, set permissions to full access
* On workstation, map vm share to a local drive. Use the same drive letter for both the vm drive and the mapped workstation drive!
* config vm’s metro firefox as the default Metro browser
* on vm, start – ‘debug’ should bring up remote debug tools folder – run the x64 version if on 64 bit os, x86 otherwise
* start remote debugger on vm
* create empty remote debugging project on workstation
* in project set debug settings:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: vm network name w/ port
** Attach: Yes
* Launch browser in vm
* F5 in project on workstation

That should be it. OutputDebugString output will land in the workstation debugger console. Breaking in the debugger doesn't kill the browser as long as metro is active and the browser is running in the foreground.

Note – AFAICT, you can’t reverse the relationship here. Metro will not launch a default browser located on a mapped drive that points to an obj dir on workstation. If we could fine a way around this it would be great.

=== Remote Debugging with a Tablet ===

Setup steps -

* In Explorer on the tablet purge any unused space on C, including old Windows installation files, using the system file cleanup option under the drive's properties panel.
* From Control Panel, bring up the disk manager and split the main disk partition into two. A 20GB partition for mozilla related bits is suitable.
* Format the second partition and designate a drive letter for it. Use a drive letter your debugging workstation does not use.
* Right-click the new mozilla drive in Explorer and select Share. Share the volume using your login credentials or you can also openly share to "Everyone" if your local network is secure. Set permissions on the share to full access.
* On your main workstation browse to the tablet share and map it to a local drive using the same drive letter you used for the tablet drive. This insures object source has the same path info on both machines.
* Install Visual Studio and mozilla-build on the tablet.
* Checkout mozilla-central on the mozilla partition of the tablet, then build and register the browser.
* On the tablet, Start + ‘debug’ should bring up a remote debug tools folder via search, open this and launch the remote debug monitor. Run the x64 version if on 64 bit os, x86 otherwise. (Pin this to your start menu for easy access.)
* Under the monitor's tools menu, add permission for your login credentials or "Everyone" for remote debugging.
* On the workstation, create a blank C++ debugging project for the tablet, set debug settings as follows:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: Tablet network name w/ port. The remote debugging tools window on the tablet can provide this.
** Attach: Yes

After this you should be able to launch the browser on the tablet and attach to it from Visual Studio on your workstation. You should also be able to browse source on the networked drive, set break points, etc., just like a local debug session. Most debug output the browser spits out should be transferred over to the remote debugger.

Note you might have to fiddle with access permissions a bit. Opening everything up to Everyone saves a lot of time, but might not be the most secure environment, depending on your situation.

=== Diagnosing Startup Problems ===

Due to the embedded nature of metro browsers, diagnosing startup problems can be a bit of a pain. There are a few things you can do to help devs figure out what's going wrong.


1) Launch the metro browser interface on desktop to confirm the install is working.


* Navigate to firefox's install location in explorer
* Hold shift, right-click the folder with firefox.exe and select open command prompt.
* in the prompt type 'firefox.exe -metrodesktop'

The metro front end should launch in a window on the desktop. If not, try uninstalling and re-installing. If that doesn't help, please file a bug.


2) Check Direct3D start up check results


Using regedit.exe, check under the following key for a value named 'MetroD3DAvailable':

HKEY_CURRENT_USER\SOFTWARE\Mozilla\Firefox

If the value is 0, Direct3D startup checks failed. Please file a bug, and post the Graphics section of your desktop browser's about:support section to the bug. If there is no value, please file a bug. If the value is 1, startup checks succeeded.


3) Check for submitted crashes reports


To check if metro fx is generating and submitting crash reports open explorer to the following path:

C:\Users\(youraccount)\AppData\Roaming\Mozilla\MetroFirefox\Crash Reports\submitted\

If the folder exists and contains text files please file a bug and copy the contents of a few of the most recent files into the bug.


4) Check for unsubmitted crashes reports


Metro firefox can not submit crashes for analysis unless the browser fully starts ({{bug|797023}}).

To check if metro fx is crashing on startup, open explorer to the following path:

C:\Users\(youraccount)\AppData\Roaming\Mozilla\MetroFirefox\Crash Reports\

In this folder look for two files:

LastCrash lastCrashFilename

If both files are present, delete them, and try restarting Metro Firefox again. After doing this, check the folder again. If the files return, a startup crash is likely.

There are two things you can do t this point to help diagnose the problem:

Option 1: Use Desktop Firefox to submit the crash report to Mozilla's crash server -

* open lastCrashFilename with notepad.exe
* copy the temp path and note the file name of the crash report
* open the temp path in explorer and locate the two files associated with the report.

There will be two files, both will have the same file name (a uuid string) and the extensions .dmp and .extra.

* shutdown desktop firefox if it is running
* In explorer, copy both files from their location into the follow folder:

C:\Users\(youraccount)\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending\

* start Desktop Firefox.
* Navigate to 'about:crashes'.
* find the uuid of the report you copied and click on its link

If the link does not resolve to a crash server crash report immediately, wait a few minutes and try again. Once the link resolves, file a bug and copy the report's link into the bug report.

Option 2:

File a bug and contact a dev. who you can share your crash report with. Note crash reports can contain user specific info, do not submit these files to bugzilla as attachments.


4) Logging startup


..


5) CEH logging


..

== Testing Harness ==

Builds generate a test harness (dist/bin/metrotestharness.exe) that can be used to launch the metro browser into the immersive environment. This harness is also packed up with the test zips used in automation testing.

Metro Firefox can't accept standard command line parameters since it must be launched by Windows. The harness acts as a pass through for mozilla command line parameters firefox.exe can accept. Incoming params are written out to an ini file @ dist/bin and read in via [http://mxr.mozilla.org/mozilla-central/source/browser/app/nsBrowserApp.cpp nsBrowserApp] when the browser starts up.

By default the test harness assumes the default browser (firefox.exe) is in the same folder metrotestharness.exe is located. If you want to launch the default browser at a different location from metrotestharness.exe, you must specify a firefox path using -firefoxpath (fullpath):

<pre>metrotestharness.exe -firefoxpath T:\Mozilla\objmcrel\dist\bin\ -url www.mozilla.org</pre>

The test harness will need *write* permission to this location to write out a command line arg ini file.

[http://mxr.mozilla.org/mozilla-central/source/browser/metro/shell/testing/metrotestharness.cpp harness source]

== Using Devtools ==
* Tracking bug https://bugzilla.mozilla.org/show_bug.cgi?id=850019
** There are known issues with the profiler. All other parts should be functional, modulo the refactoring work the devtools team is doing on them.
* This hooks into the tools developed & maintained by the devtools team.
* They have been refactoring & improving their tools, so it highly encouraged to use Nightly builds on both sides of the pairing if possible.

* Before you start
** You must have metro installed & working
** You must access to a classic/desktop fx. This need not be a local build
** If you are connecting remotely, you must make sure both machines can ping each other before starting. This will save you a lot of grief later
*** on windows ipconfig in the cmdline is helpful in getting your ip address
*** on windows 8 this usually means disabling the firewall (not encouraged) or adding inbound/outbound firewall rules to allow them to connect.
**** If you need it, Peter in IT now knows a fair bit about setting up those rules if you get lost or stuck.
** If you are on wifi, both devices must be on the same network to communicate. Mozilla != Mozilla-G.
*** It sounds silly but some of the windows devices only see Mozilla-G and the older company issued thinkpads do not have the hardware for it.

* Setup
** Go to about:config on classic/desktop fx
*** devtools.debugger.force-local -> false
*** devtools.debugger.remote-enabled -> true
*** Check that these values are what you want
**** devtools.debugger.remote-port -> 6000 (I'd leave this one alone unless you have a compelling reason to change it)
*** If you don't have these, you'll probably want these as well
**** devtools.debugger.log -> true
**** browser.dom.window.dump.enabled -> true
** Restart classic/desktop fx
*** You need to restart for the next step to work.
** Navigate Firefox button -> Web Developer -> "Connect.." entry between the Error Console" & "Get More Tools" Entry
*** https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Debugging/Setting_up is what this step is based on
** Go to about:config on metrofx
*** devtools.debugger.force-local -> false
*** devtools.debugger.remote-enabled -> true
*** and you may want
**** devtools.debugger.log -> true
**** devtools.errorconsole.enabled -> true
**** browser.dom.window.dump.enabled -> true
*** devtools.debugger.remote-port -> 6000 (again I'd leave this one alone)
*** It is unclear if a restart is required. I frequently do in the test-build-dev cycle anyway.
** Make sure metrofx is started (and not suspended)
** In classic fx, click the "Connect..." entry
*** Depending on your version, this will launch a new tab or a new panel on firefox
*** Enter the ip of metrofx if you are connecting remotely and the port number if you've changed them.
*** If you are connecting on a localhost, you shouldn't need to change the default settings.
** Click the connect button in classic fx
** On metrofx a strap(the metro version of the modal dialog) will appear about an incoming connection.
*** Click/tap "allow"
** On classic fx, the connect page will reload with a list of active tabs & processes. Usually 'main process' is the most interesting.
** The devtools console will appear & the aforementioned tab on classic fx will disappear
** Sally forth & debug!

* Notes
** I usually pair on localhost, using an external monitor so I can see metrofx & classicfx at the same time.
** If you are using localhost without an external monitor, beware of windows suspending the metrofx while its waiting for the incoming connection. This will cause the pairing to fail.
** While you can pair classic/metrofx running out of the same obj dir, I frequently experienced unexpected hangs and crashes as a result.
** if you close the devtools window, this usually results in the metro browser shutting down

== Samsung Series 7 ==

The Series seven is the first device we started developing with. Details below on getting the hardware set up with Windows 8.

* To order, file a bug under mozilla.org, Server Operations: Desktop Issues. See {{bug|738613}}, CC your PM or Asa.

* Once you have the tablet, dock, and keyboard, unpack. Charge up the device. It'll be running Win7, ignore all the default software.

* Download the 64-bit (3.6 gig) Win8 ISO from \\fs2\IT\Microsoft. Add your name to the list of people who will need product keys in {{bug|783811}}. Burn the ISO to a suitable memory stick. For burning on Windows you'll need to download and install the [http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool Windows 7 USB DVD Download Tool] from Microsoft. For burning on mac?

* Once you have the ISO burned, plug the USB stick into the tablet's dock. Browse to the USB drive and run "setup.exe". When prompted choose that you want to save nothing from the previous install.

* Samsung provides an instruction manual on hooking up the Bluetooth keyboard. You can do this after you've installed Win8 as the Win7 desktop instructions are applicable on Win8 desktop.

* After the tablet is set up, download Firefox nightly or build a local copy and start debugging!

=== Firmware Updates ===

For more precise touch input, especially with tap and hold, install the "Touch Screen Sensor Firmware Configuration Updater Tool". Updating the system bios from 7 to 10 doesn't hurt either. Make sure to reboot the system after the install.

[http://www.samsung.com/global/windowspreview/ Samsung Link]

=== Samsung Series 7 Tweaks ===

* To fix auto changing brightness problems for wipe Win8 installs:
** Open desktop
** click/tap on the battery icon in the taskbar, select "More power options"
** Select your current power plan or create a new plan via the link on the left.
** Under the power plan select "Change advanced power settings"
** scroll down to "Display" and expand
** Find the sub-option "Enable adaptive brightness" and expand
** disable both options under this sub-option

== Metro Planning ==

(Older content from the original planning stage)

This is summary of our work / planning for a Win8 Metro browser. For testing purposes we have been working with the /mobile/xul Fennec browser. Moving forward we would like to take the base Fennec XUL code and Metro specific code we've already developed (currently on Elm with some build related work already on mc) and integrate this in with the default Firefox build and install.

We are interested in getting as much feedback as possible from stake holders and from people who have worked with these newer platforms. If you have Win8 up and running in a vm or on a test system, there are details here on how to get builds going, how to register the browser, and test builds for installing.

* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;list_id=2566518 Metro specific bug list]
* [http://piercedotzler.com/asa/Developing_a_Metro-Style_Enabled_Desktop_Browser.html#_Toc318127097 Developing Metro Style Enabled Desktop Browsers]

=== What’s different and what’s the same ===

By in large platform was a nice fit for Metro. We ran into surprisingly few problems. It took us about a week to get a basic version of Fennec running in the environment and most of that time was spent combing through the registration/integration doc Microsoft sent us. Below are some specific details on the areas of the repo we are currently leveraging.

nsBrowserApp

<strike>Currently using fennec’s nsBrowserApp.</strike>

chrome interface markup and css (different)

Metro apps are single window applications. The current desktop UI does not fit this new environment. There are no secondary windows we create. Secondary UI (file pickers, warnings, message boxes, toasts) are all displayed and managed by the os. The interfaces to these features are also async. We will provide interfaces for invoking these. Some have already been integrated on Elm (file picker for example).

browser comps (different)

dictionaries, hyphenation, res, searchplugins, extensions, plugins (shared)

Due to the differences in view model most of /browser components code can’t be leveraged. Fennec's script based components are currently in use. [http://mxr.mozilla.org/mozilla-central/source/mobile/xul/components/]

The current metro browser leverages the Fennec front end app code but we could switch to firefox’s code base and enable / augment what we need for metro.

toolkit/xre (modest differences)

The app model is slightly different for Metro. UI events and rendering do not occur on the main thread. We have a working model implemented on Elm that breaks up parts of XRE_main so that certain parts (startup & run) can be called on a different ‘main’ thread.

widget (mostly shared widget/windows code base with different nsIWidget classes)

There are significant differences in the view model so we needed a new nsWindow class. nsWindow latches into a new set of apis for events and view management. [http://mxr.mozilla.org/projects-central/source/elm/widget/windows/winrt/] Generally winrt and winapi code has integrated well together. We are currently leveraging [http://msdn.microsoft.com/en-us/library/windows/apps/hh755822(v=vs.110).aspx Component Extensions] and various winrt runtime classes. We will be able to share a great deal of win32 widget code.

default browser integration (new registration / launch characteristics for both desktop and metro for win8, older os remains unchanged)

installer/helper/uninstall (shared codebase w/new registration for win8)

On Windows8 the mechanics of launching the browser have changed. There is a new intermediary (a ‘command execute handler’) which is a small, light weight COM server Windows launches. This application chooses which browser to launch based on the environment requested. This change effects the launch of both browsers and the way we register as the default browser on Windows 8. [http://mxr.mozilla.org/projects-central/source/elm/mobile/xul/metro/] We currently have a basic Fennec install going for testing purposes, but it shouldn’t be too hard to move this over to the Firefox installer.

everything else in runtime (shared)

Generally we’re currently leveraging a majority of our common code base without issue. Threading, timers, networking, ssl, layout, gfx, etc. have all fit in really well. Misc. detail -

* gfx - not currently using accelerated layers but plan to in the near future. The surface rendered to in Metro is D2D and there is no GDI fallback. As such there are some issues with blacklisted hardware.
* e10s - currently using Fennec’s out of process tabs.
* Accessibility - not integrated yet.
* Netwerk - no issues.
* Layout - no issues.
* dom & dom/system & hal - DOM interfaces for device info / sensor input and events. Currently there isn't much here for Windows.
* media - no issues.
* storage - works, although there are some profile corruption problems from early termination which can occur in metro. We also have a 'shared profile' problem (see Big Issues).
* toolkit - very little of this is in use. Crash reporter UI will need work/integration.
* xpcom - no issues.

=== A tentative proposal ===

* Copy mobile/xul code down to browser level in /browser/metro.
* Integrate metro startup into firefox's nsBrowserApp {{bug|747347}}.
* Integrate building this new area into the current desktop firefox build. {{bug|747347}}
* Fixup the firefox installer so that we bring both browsers down in a single unified windows install. {{bug|737833}}
* Share the runtime between the two apps in the install. [completed]
* Have nsBrowserApp communicate to xul lib what environment we are running in. [completed]
* Dynamically switch out which code path we want in xul lib where necessary. [completed]
* Organize dist interface code and browser comps such that desktop firefox install layout remains unchanged. Layer metro specific resources down in such a way that the two sets of resources do not conflict. {{bug|755724}}
* <strike>Share a single profile between both browsers</strike> or Sync two profiles on the same machine.

Elm to mozilla-central migration tracking bug: {{bug|747347}}

==== Pros and Cons ====

* Pro – single unified Windows installer / unified browser build.
* Pro – shared runtime without multiple copies of key files like xul.dll.

* Con – larger Windows install regardless of what version of the os we install on. metrobrowser would be present on all Windows installs.
* Con – builders / release eng. will have to upgrade to VC11 / Win8 SDK to do the build. For the time being however we have a build switch that enables win8 specific components, so we can start landing on mc without breaking existing desktop builds which leverage vc10 build tools. {{bug|737994}}

* Pro/Con – With this setup we currently assume we will leverage xul lib. On the positive side having xul makes putting together our UI fast and easy. On the negative side startup performance may be an issue. We are working on getting telemetry data going so we can better measure this in the test builds we are distributing. Thus far test builds we have going on Samsung tablets and a few other test machines show promise on startup performance. Windows is obviously optimized for loading our libraries and the browsers we compete against all have the same encumbrance.

=== Big Issues ===

* Windows XP - The current VC11 Beta redist runtime is not compatible with XP. ({{bug|744942}})
* Profiles – Certain areas of the user’s profile will need to be shared between two concurrently running browser apps. We’ve just begun exploring ways to do this. Potential solution might involve a mysql database connection shim that leverages a profile broker and IPC so both browsers can talk to the same profile. We also might consider using Sync. There are some hurdles here to overcome. [A decision was made to use Sync initially.]
* Accessibility - This area of the code base will be in heavy use in the Metro environment with touch interfaces. Our accessibility code will require performance work and may require a new UI Automation adapter since Win8 leverages UI Automation exclusively.
* e10s - (khuey) Certain things are pretty much broken in e10s (e.g. IndexedDB) and other features have not received any testing in several months. Relying on e10s will likely require some investment in the platform to clean this up for metro/desktop parity. Not relying on e10s may decrease the amount of existing XUL Fennec code that can be reused. [question: (jimm) what's the difference in the amount of work we have to do? We've disabled remote tabs on elm for now to see what's broken.] [A decision was made to use in-process content for the foreseeable future.]
* Extensions - currently extension support will be off until a suitable extension mechanism can be designed and implemented.

== Links ==

* [http://msdn.microsoft.com/en-us/library/windows/apps/br211369%28v=VS.85%29.aspx API for Metro style apps]
* [http://www.pcworld.com/article/240125/windows_8_on_arm_processors_three_working_tablet_demos.html ARM support]

Firefox/Windows 8 Integration

2013-08-22T19:19:37Z

Sfoster: Add steps for Crash Testing

== Wiki ==

* [https://wiki.mozilla.org/Firefox/Metro Metro Project] - meeting times, bug lists, project goals, team info, etc.
* [[Firefox/Features|General Firefox Product Feature Tracking]] - Firefox feature tracking.
* [https://wiki.mozilla.org/Firefox_Metro_UI Firefox Metro UI wiki] - including comp work and UX bug tracking.
* [[Windows8|Metro Project Status]] - not really in use.
* [[Windows_8_Integration]] - General 3rd party browser collaboration page dedicated to overview, architecture, and challenges for vendors. Early research with Google.
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208;query_format=advanced;list_id=2566504 Windows 8 (desktop)]
* [[Firefox/Windows 8 Metro Style Guides]] - coding standards and UI guidelines

== Useful Bugzilla Queries ==
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;list_id=5745479 Win8 Metro]

* Metro Firefox complete list

[https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=notsubstring;list_id=5756053;field0-1-0=status_whiteboard;field0-0-0=status_whiteboard;resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;value0-2-0=MetroV1;value0-1-0=feature%3Dstory;field0-2-0=short_desc;type0-0-0=notsubstring;value0-0-0=feature%3Depic;type0-2-0=notsubstring Win8 Metro]

* Metro Firefox complete list
* Minus feature=story, epic, and MetroV1

[https://bugzilla.mozilla.org/buglist.cgi?type0-7-0=notsubstring;value0-7-0=feature%3Ddefect;field0-3-0=status_whiteboard;type0-1-0=notequals;type0-5-0=notsubstring;value0-5-0=feature%3Dwork;value0-4-0=feature%3Dstory;list_id=5745413;field0-1-0=blocked;field0-0-0=blocked;type0-4-0=notsubstring;resolution=---;field0-6-0=status_whiteboard;value0-3-0=feature%3Depic;field0-7-0=status_whiteboard;query_format=advanced;value0-2-0=MetroV1;value0-6-0=feature%3Dchange;value0-1-0=842686;type0-3-0=notsubstring;field0-2-0=short_desc;field0-5-0=status_whiteboard;field0-4-0=status_whiteboard;type0-6-0=notsubstring;type0-0-0=notequals;value0-0-0=841214;type0-2-0=notsubstring;product=Firefox%20for%20Metro Untagged Bugs]
* Not blocked by various pm triage tracking bugs
* Whiteboard does not contain feature=epic, work, change, defect, story
* Summary does not contain 'MetroV1'

[https://bugzilla.mozilla.org/buglist.cgi?chfield=%5BBug%20creation%5D;chfieldfrom=-72h;known_name=Last%20Three%20Days;columnlist=opendate%2Cbug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc;resolution=---;op_sys=Windows%20XP;op_sys=Windows%20Vista;op_sys=Windows%207;op_sys=Windows%208;op_sys=Windows%208%20Metro;query_based_on=Last%20Three%20Days;chfieldto=Now;query_format=advanced;product=Firefox%20for%20Metro;list_id=5745420 Last three days]

* Bugs filed against product Metro Firefox in the last three days

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4351876;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;product=Core;product=Toolkit;product=www.mozilla.org Platform]

* Core, Toolkit, mozilla.org

== Getting Involved ==
Contact Brian Bondy with questions (bbondy on [http://irc.mozilla.org IRC]). The Windows 8 integration team can be found in in #windev.

=== Bugzilla ===

Please file front end bugs under the product [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20for%20Metro Firefox for Metro]. Back end bugs should be filed in the appropriate Platform component.

=== Front End Windows 8 Development ===

* To contribute to front end bugs, you will use: JS, CSS, XUL, XBL
* You do not actually need Windows 8 to work on the front end code
* Follow the steps in the Metro Builds section below to get setup
* The front end code is located in browser/metro
* Style guidelines of all types can be found on https://wiki.mozilla.org/Firefox/Windows_8_Metro_Style_Guides
* the front end code is to be literally a user friendly. it helps developers to get understood easily.

=== Platform Integration Windows 8 Development ===

* To contribute to platform integration bugs, you will use: C++
* You do need Windows 8 to work on the platform integration code
* You can obtain a 90 day free Windows 8 evaluation for developers from Microsoft
* Follow the steps in the Metro Builds section below to get setup
* The platform integration code is located in widget/windows/winrt
* You can find Windows 8 platform integration bugs here http://goo.gl/B0Xjo or by doing an advanced bugzilla search for: OS = Windows 8 Metro, Product = Core, Component = Widget: Win32

== Metro Builds ==

=== Nightly Builds ===

Update: 6/24/2013

Nightly builds are now being generated on mozilla-central.

Nightly builds off the mozilla-central repository are currently available in the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/ Firefox build archives].

To set these builds up:

* Install the browser using the latest installer
* Open the desktop browser - when the default browser check occurs, select yes to set Firefox as the default. You should also receive a Windows prompt, select Nightly. This will associate Firefox with various protocol handlers and create the Firefox tile.
* To set file handler associations use Window's Control Panel for default program associations. (Options -> Advanced -> General and click the default browser button at the bottom to open this panel.)

For more detailed help on installing / setting the browser as the default, visit the [https://support.mozilla.org/en-US/kb/how-do-i-install-windows-8-metro-style-firefox Metro Firefox support page].

=== Nightly Crash Reports ===

[https://crash-stats.mozilla.com/topcrasher/byversion/MetroFirefox/22.0a1/7 Firefox for Metro]

=== Switching Default Browsers ===

This can be a little tedious when working with multiple builds / installs on a single device. Steps:

* Close Firefox both in Metro and on Desktop
* Open Control Panel's default programs and set IE as the default
* With debug builds: run the resulting firefox.exe on the desktop and set as the default through Options menu -> Advanced -> General tab -> Make default button.
* For release builds: run the resulting firefox.exe on the desktop and click yes to the default settings dialog, then select 'Nightly' in the Windows 8 prompt.
* In Control Panel's default programs, set firefox as the default browser.

To confirm the right browser is set, launch the browser in Metro, switch to desktop, open task manager, right-click the Firefox process, and select open file location.

Note pinned taskbar shortcuts can't be trusted to open the right browser.

=== Zip Builds ===

Zip installs from daily checkins are currently available on the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/ Firefox build archives].

To install:

* Download the newest firefox-(rev).0a1.en-US.win32.zip to your Win8 device
* Unpack the main firefox folder to a suitable location
* Run firefox.exe on the desktop
* If prompted by Windows, select Nightly/Aurora/Firefox as the default.
* Open Options -> Advanced -> General and click the "Make Firefox the default browser" button. This will open Windows Control Panel where you will need to select the channel build you are testing and set the defaults.

=== Building Locally ===

Updated 5/21/2013

* Install Visual Studio 2010 or 2012.
* Install [https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Windows_Prerequisites MozillaBuild] (version 1.7 required)
* Install the [http://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx Windows 8.0 SDK]
* Install [http://www.microsoft.com/en-us/download/confirmation.aspx?id=6812 DirectX SDK (June 2010)]

* For VC 2010 builds:
** Modify the the following header in the sdk:
<pre>
C:\Program Files (x86)\Windows Kits\8.0\Include\winrt\asyncinfo.h

line 67:

enum class AsyncStatus {

to

enum /*class*/ AsyncStatus {
</pre>

If you use both VC 2010 and VC 2012 (or plan to install VC 2012 in the near future) you might want to instead use the following patch, which reverts to the original code under VC 2012 and later:
<pre>
--- asyncinfo.h.orig 2013-05-21 08:47:49 -0400
+++ asyncinfo.h 2013-05-21 08:48:55 -0400
@@ -58,17 +58,21 @@
/* interface __MIDL_itf_asyncinfo_0000_0000 */
/* [local] */

// Microsoft Windows
// Copyright (c) Microsoft Corporation. All rights reserved.
#pragma once
#ifdef __cplusplus
namespace ABI { namespace Windows { namespace Foundation {
+#if defined (_MSC_VER) && _MSC_VER >= 1700
enum class AsyncStatus {
+#else
+enum AsyncStatus {
+#endif
Started = 0,
Completed,
Canceled,
Error,
};
} } } // ABI::Windows:::Foundation
using ABI::Windows::Foundation::AsyncStatus;
#ifndef _HIDE_GLOBAL_ASYNC_STATUS
</pre>

* For Express versions of VS:
** Install [http://www.microsoft.com/en-us/download/details.aspx?id=11800 the Windows Driver Toolkit, version 7.1] - Version 7.1 is needed because it contains the necessary ATL headers that express VS lacks.
** Add the following to start-msvc*.bat file near the end just before the line that reads cd "%USERPROFILE%" (assumes WinDDK was installed in "C:\WinDDK\7600.16385.1"):
<pre>
set "INCLUDE=C:\WinDDK\7600.16385.1\inc\atl71;%INCLUDE%"
set "LIB=C:\WinDDK\7600.16385.1\lib\ATL\i386;%LIB%"
</pre>

* [https://developer.mozilla.org/en-US/docs/Simple_Firefox_build#Get_the_source Check out mozilla-central]. Make sure the obj directory has "Modify" permissions given to the current user.
* Create a standard browser .mozconfig file with the options you prefer and add

<pre>
ac_add_options --enable-metro
</pre>

* [https://developer.mozilla.org/en-US/docs/Simple_Firefox_build#Building Build Firefox].

At this point, you should be able to launch the metro browser on the desktop using a command line switch:

<pre>
(obj)/dist/bin/firefox.exe -metrodesktop
</pre>

To register local builds as the default browser:

* For debug builds: run the resulting firefox.exe on the desktop and set as the default through Options menu -> Advanced -> General tab -> Make default button.
* For release builds: run the resulting firefox.exe on the desktop and click yes to the default settings dialog, then select 'Nightly' in the Windows 8 prompt.
* Open up Control Panel -> Default Programs. You should see 'Metro Firefox' in the list of applications.
* Set all Metro Firefox defaults in Default Programs.

At which point you should have a Firefox tile in Win8 that launches the browser.

Note, for debug builds, see [[Firefox/Windows_8_Integration#Logging_Assertions]].

=== Desktop Launch ===

To launch within the metro experience follow the registration steps above. To launch the metro front end UI using the win32 widget backend on the desktop (including non-Windows-8 devices) use the -metrodesktop command line option:

<pre>(path to firefox build)/firefox.exe -metrodesktop</pre>

To set things up such that you can test touch input on the desktop - flip the 'metro.debug.treatmouseastouch' to true in /browser/metro/profile/metro.js.

Note on the desktop we use the desktop's Win32/Widget backend. This can behave differently from the Win8 WinRT backend. The translational layer for Win32 events is location in /browser/metro/content/base/input.js.

=== Testing ===

[https://developer.mozilla.org/en-US/docs/Browser_chrome_tests Browser-chrome tests] for Metro Firefox are located in [http://hg.mozilla.org/projects/elm/file/default/browser/metro/base/tests/ browser/metro/base/tests]. The tests run in the Metro environment; Windows 8 is required.

Currently, some of the selection tests may fail (specifically, browser_selection_frame_textarea.js) if the device and CSS pixels are out of sync. To solve this, you may need to change the following pref in about:config to the following value.

layout.css.devPixelsPerPx = 1.0 (default is -1.0, which makes Firefox autoscale CSS pixels)

To start the tests, run the following command in the mozilla-build shell, at the top level of your obj-dir:

pymake mochitest-metro-chrome

The Metro browser will launch, run the tests and exit. Any failures will be printed to the console. The complete test log will be written to the file <code>mochitest-metro-chrome.log</code> in the objdir.

=== Building on Linux or Mac OS X ===

You can use the ''--enable-metro'' configure option and the ''-metrodesktop'' command-line flag to build and run the Metro UI on other platforms too. For details, see [http://limpet.net/mbrubeck/2012/09/19/metro-firefox-without-windows.html Metro Firefox without Windows 8].

On Mac, you might need to run "./mach build browser" after your build completes. For details, see {{bug|847807}}.

* there is a problem with html5 EMBED tag. '''an EMBED tag is basically to play media files.''' but we can't use this on mac.

=== Logging Assertions ===

When you're running Metro Firefox with --enable-debug, there will be assertion failure messages that show up in the console. The following environment variable is assumed for the Metro environment:

<pre>
XPCOM_DEBUG_BREAK=warn
</pre>

=== Remote Debug Output ===

NSPR logging can be dumped to OutputDebugString using the NSPR_LOG_FILE environment variable:

<pre>
NSPR_LOG_FILE=WinDebug
</pre>

To log NS assertions and warnings in debug builds add the nsDebug log module:

<pre>
NSPR_LOG_MODULES=nsDebug:4
</pre>

<strike>{{bug|762519}}</strike> was filed on getting javascript's dump output going to OutputDebugString as well.

=== DOM Inspector ===

Getting DOM Inspector attached to builds running on the desktop takes a few tweaks.
* Install the dom inspector addon (if you do not have it already) on your desktop firefox
* Copy the 'inspector@mozilla.org' folder under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory. (Example: C:\Users\Brian\AppData\Roaming\Mozilla\MetroFirefox\Profiles\amrcb8eg.default\extensions)
* add an entry in inspector's install.rdf file for metrofx and make sure the maxVersion is set correctly.

<pre>
<em:targetApplication>
<Description>
<em:id>{99bceaaa-e3c6-48c1-b981-ef9b46b67d60}</em:id>
<em:minVersion>1.0a1</em:minVersion>
<em:maxVersion>19.0a1</em:maxVersion>
</Description>
</em:targetApplication>
</pre>

* Add the [https://developer.mozilla.org/en/XULRunner_tips startDOMi function] to /browser/metro/base/content/browser.js.
* Add a call to startDOMi() below the BrowserUI.init() call.
** If you start the browser and see a blank screen with your patch containing startDOMi() applied, it probably means the extension hasn't been enabled/installed properly. Often its the last step of flipping values.
* Tweak the following extension prefs in metro.js:
<pre>
pref("extensions.autoDisableScopes", 15);
pref("extensions.minCompatibleAppVersion", "4.0");
pref("extensions.strictCompatibility", false);
</pre>

* The extensions.json file will be created the first time MetroFirefox is run and discovers the inspector@mozilla.org extension content in the profile, but you have to flip a couple of values to make it actually work. Set the 'active' property to boolean true and the userDisabled property to boolean false.

=== Venkman Debugger ===

(10/5/12 - Note, since we've changed the app id, this probably doesn't work.)

* Copy the '{f13b157f-b174-47e7-a34d-4815ddfdfeb8}' xpi under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory.

* Launch the browser with the '-venkman' command line option.

=== JS Shell ===

For debugging the ede js shell and javascript console are available on the app bar in desktop builds.

=== Crash Testing ===

To test the Crash Reporter UI and other crash-related behavior, you can make use of install the Crash Me addon from [http://code.google.com/p/crashme/ Google Code]. This extension is already Metro Firefox ready, so you just need to follow similar steps as for the DOM Inspector to enable it.
* Install the Crash Me addon (if you do not have it already) on your desktop firefox
* Copy the 'crashme@ted.mielczarek.org' folder under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory. (Example: C:\Users\Brian\AppData\Roaming\Mozilla\MetroFirefox\Profiles\amrcb8eg.default\extensions)
* - OR - you can just download and unzip the .xpi file into a crashme@ted.mielczarek.org folder in your profile extensions directory
* To allow discovery and install of add-ons, set extensions.autoDisableScopes to 15, either via your local metro.js or in about:config
* If you are using a local build, you may need to edit the metroapp.ini (generated from the metroapp.ini.in template) to ensure the Crash Reporter Enabled=1 flag is set.

To use, you'll find a new "Crash Now!" entry in the Settings charm. Tap it to crash.

=== WinRT Compiler Generated Code ===

Compiler switches:
* /d1ZWtokens - dump C++ code generated code for C++/CX.
* /d1reportAllClassLayout - dump class layouts
* /d1reportSingleClassLayoutXXX - where XXX performs substring matches against the class name.

=== Remote Debugging with a VM ===

(This was last tested with the Win8 RP)

Setup steps -

* create a new drive for vm, clone src there, build. obj dir should also be on this drive.
* Enable sharing on the drive, set permissions to full access
* On workstation, map vm share to a local drive. Use the same drive letter for both the vm drive and the mapped workstation drive!
* config vm’s metro firefox as the default Metro browser
* on vm, start – ‘debug’ should bring up remote debug tools folder – run the x64 version if on 64 bit os, x86 otherwise
* start remote debugger on vm
* create empty remote debugging project on workstation
* in project set debug settings:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: vm network name w/ port
** Attach: Yes
* Launch browser in vm
* F5 in project on workstation

That should be it. OutputDebugString output will land in the workstation debugger console. Breaking in the debugger doesn't kill the browser as long as metro is active and the browser is running in the foreground.

Note – AFAICT, you can’t reverse the relationship here. Metro will not launch a default browser located on a mapped drive that points to an obj dir on workstation. If we could fine a way around this it would be great.

=== Remote Debugging with a Tablet ===

Setup steps -

* In Explorer on the tablet purge any unused space on C, including old Windows installation files, using the system file cleanup option under the drive's properties panel.
* From Control Panel, bring up the disk manager and split the main disk partition into two. A 20GB partition for mozilla related bits is suitable.
* Format the second partition and designate a drive letter for it. Use a drive letter your debugging workstation does not use.
* Right-click the new mozilla drive in Explorer and select Share. Share the volume using your login credentials or you can also openly share to "Everyone" if your local network is secure. Set permissions on the share to full access.
* On your main workstation browse to the tablet share and map it to a local drive using the same drive letter you used for the tablet drive. This insures object source has the same path info on both machines.
* Install Visual Studio and mozilla-build on the tablet.
* Checkout mozilla-central on the mozilla partition of the tablet, then build and register the browser.
* On the tablet, Start + ‘debug’ should bring up a remote debug tools folder via search, open this and launch the remote debug monitor. Run the x64 version if on 64 bit os, x86 otherwise. (Pin this to your start menu for easy access.)
* Under the monitor's tools menu, add permission for your login credentials or "Everyone" for remote debugging.
* On the workstation, create a blank C++ debugging project for the tablet, set debug settings as follows:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: Tablet network name w/ port. The remote debugging tools window on the tablet can provide this.
** Attach: Yes

After this you should be able to launch the browser on the tablet and attach to it from Visual Studio on your workstation. You should also be able to browse source on the networked drive, set break points, etc., just like a local debug session. Most debug output the browser spits out should be transferred over to the remote debugger.

Note you might have to fiddle with access permissions a bit. Opening everything up to Everyone saves a lot of time, but might not be the most secure environment, depending on your situation.

=== Diagnosing Startup Problems ===

Due to the embedded nature of metro browsers, diagnosing startup problems can be a bit of a pain. There are a few things you can do to help devs figure out what's going wrong.


1) Launch the metro browser interface on desktop to confirm the install is working.


* Navigate to firefox's install location in explorer
* Hold shift, right-click the folder with firefox.exe and select open command prompt.
* in the prompt type 'firefox.exe -metrodesktop'

The metro front end should launch in a window on the desktop. If not, try uninstalling and re-installing. If that doesn't help, please file a bug.


2) Check Direct3D start up check results


Using regedit.exe, check under the following key for a value named 'MetroD3DAvailable':

HKEY_CURRENT_USER\SOFTWARE\Mozilla\Firefox

If the value is 0, Direct3D startup checks failed. Please file a bug, and post the Graphics section of your desktop browser's about:support section to the bug. If there is no value, please file a bug. If the value is 1, startup checks succeeded.


3) Check for submitted crashes reports


To check if metro fx is generating and submitting crash reports open explorer to the following path:

C:\Users\(youraccount)\AppData\Roaming\Mozilla\MetroFirefox\Crash Reports\submitted\

If the folder exists and contains text files please file a bug and copy the contents of a few of the most recent files into the bug.


4) Check for unsubmitted crashes reports


Metro firefox can not submit crashes for analysis unless the browser fully starts ({{bug|797023}}).

To check if metro fx is crashing on startup, open explorer to the following path:

C:\Users\(youraccount)\AppData\Roaming\Mozilla\MetroFirefox\Crash Reports\

In this folder look for two files:

LastCrash lastCrashFilename

If both files are present, delete them, and try restarting Metro Firefox again. After doing this, check the folder again. If the files return, a startup crash is likely.

There are two things you can do t this point to help diagnose the problem:

Option 1: Use Desktop Firefox to submit the crash report to Mozilla's crash server -

* open lastCrashFilename with notepad.exe
* copy the temp path and note the file name of the crash report
* open the temp path in explorer and locate the two files associated with the report.

There will be two files, both will have the same file name (a uuid string) and the extensions .dmp and .extra.

* shutdown desktop firefox if it is running
* In explorer, copy both files from their location into the follow folder:

C:\Users\(youraccount)\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending\

* start Desktop Firefox.
* Navigate to 'about:crashes'.
* find the uuid of the report you copied and click on its link

If the link does not resolve to a crash server crash report immediately, wait a few minutes and try again. Once the link resolves, file a bug and copy the report's link into the bug report.

Option 2:

File a bug and contact a dev. who you can share your crash report with. Note crash reports can contain user specific info, do not submit these files to bugzilla as attachments.


4) Logging startup


..


5) CEH logging


..

== Testing Harness ==

Builds generate a test harness (dist/bin/metrotestharness.exe) that can be used to launch the metro browser into the immersive environment. This harness is also packed up with the test zips used in automation testing.

Metro Firefox can't accept standard command line parameters since it must be launched by Windows. The harness acts as a pass through for mozilla command line parameters firefox.exe can accept. Incoming params are written out to an ini file @ dist/bin and read in via [http://mxr.mozilla.org/mozilla-central/source/browser/app/nsBrowserApp.cpp nsBrowserApp] when the browser starts up.

By default the test harness assumes the default browser (firefox.exe) is in the same folder metrotestharness.exe is located. If you want to launch the default browser at a different location from metrotestharness.exe, you must specify a firefox path using -firefoxpath (fullpath):

<pre>metrotestharness.exe -firefoxpath T:\Mozilla\objmcrel\dist\bin\ -url www.mozilla.org</pre>

The test harness will need *write* permission to this location to write out a command line arg ini file.

[http://mxr.mozilla.org/mozilla-central/source/browser/metro/shell/testing/metrotestharness.cpp harness source]

== Using Devtools ==
* Tracking bug https://bugzilla.mozilla.org/show_bug.cgi?id=850019
** There are known issues with the profiler. All other parts should be functional, modulo the refactoring work the devtools team is doing on them.
* This hooks into the tools developed & maintained by the devtools team.
* They have been refactoring & improving their tools, so it highly encouraged to use Nightly builds on both sides of the pairing if possible.

* Before you start
** You must have metro installed & working
** You must access to a classic/desktop fx. This need not be a local build
** If you are connecting remotely, you must make sure both machines can ping each other before starting. This will save you a lot of grief later
*** on windows ipconfig in the cmdline is helpful in getting your ip address
*** on windows 8 this usually means disabling the firewall (not encouraged) or adding inbound/outbound firewall rules to allow them to connect.
**** If you need it, Peter in IT now knows a fair bit about setting up those rules if you get lost or stuck.
** If you are on wifi, both devices must be on the same network to communicate. Mozilla != Mozilla-G.
*** It sounds silly but some of the windows devices only see Mozilla-G and the older company issued thinkpads do not have the hardware for it.

* Setup
** Go to about:config on classic/desktop fx
*** devtools.debugger.force-local -> false
*** devtools.debugger.remote-enabled -> true
*** Check that these values are what you want
**** devtools.debugger.remote-port -> 6000 (I'd leave this one alone unless you have a compelling reason to change it)
*** If you don't have these, you'll probably want these as well
**** devtools.debugger.log -> true
**** browser.dom.window.dump.enabled -> true
** Restart classic/desktop fx
*** You need to restart for the next step to work.
** Navigate Firefox button -> Web Developer -> "Connect.." entry between the Error Console" & "Get More Tools" Entry
*** https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Debugging/Setting_up is what this step is based on
** Go to about:config on metrofx
*** devtools.debugger.force-local -> false
*** devtools.debugger.remote-enabled -> true
*** and you may want
**** devtools.debugger.log -> true
**** devtools.errorconsole.enabled -> true
**** browser.dom.window.dump.enabled -> true
*** devtools.debugger.remote-port -> 6000 (again I'd leave this one alone)
*** It is unclear if a restart is required. I frequently do in the test-build-dev cycle anyway.
** Make sure metrofx is started (and not suspended)
** In classic fx, click the "Connect..." entry
*** Depending on your version, this will launch a new tab or a new panel on firefox
*** Enter the ip of metrofx if you are connecting remotely and the port number if you've changed them.
*** If you are connecting on a localhost, you shouldn't need to change the default settings.
** Click the connect button in classic fx
** On metrofx a strap(the metro version of the modal dialog) will appear about an incoming connection.
*** Click/tap "allow"
** On classic fx, the connect page will reload with a list of active tabs & processes. Usually 'main process' is the most interesting.
** The devtools console will appear & the aforementioned tab on classic fx will disappear
** Sally forth & debug!

* Notes
** I usually pair on localhost, using an external monitor so I can see metrofx & classicfx at the same time.
** If you are using localhost without an external monitor, beware of windows suspending the metrofx while its waiting for the incoming connection. This will cause the pairing to fail.
** While you can pair classic/metrofx running out of the same obj dir, I frequently experienced unexpected hangs and crashes as a result.
** if you close the devtools window, this usually results in the metro browser shutting down

== Samsung Series 7 ==

The Series seven is the first device we started developing with. Details below on getting the hardware set up with Windows 8.

* To order, file a bug under mozilla.org, Server Operations: Desktop Issues. See {{bug|738613}}, CC your PM or Asa.

* Once you have the tablet, dock, and keyboard, unpack. Charge up the device. It'll be running Win7, ignore all the default software.

* Download the 64-bit (3.6 gig) Win8 ISO from \\fs2\IT\Microsoft. Add your name to the list of people who will need product keys in {{bug|783811}}. Burn the ISO to a suitable memory stick. For burning on Windows you'll need to download and install the [http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool Windows 7 USB DVD Download Tool] from Microsoft. For burning on mac?

* Once you have the ISO burned, plug the USB stick into the tablet's dock. Browse to the USB drive and run "setup.exe". When prompted choose that you want to save nothing from the previous install.

* Samsung provides an instruction manual on hooking up the Bluetooth keyboard. You can do this after you've installed Win8 as the Win7 desktop instructions are applicable on Win8 desktop.

* After the tablet is set up, download Firefox nightly or build a local copy and start debugging!

=== Firmware Updates ===

For more precise touch input, especially with tap and hold, install the "Touch Screen Sensor Firmware Configuration Updater Tool". Updating the system bios from 7 to 10 doesn't hurt either. Make sure to reboot the system after the install.

[http://www.samsung.com/global/windowspreview/ Samsung Link]

=== Samsung Series 7 Tweaks ===

* To fix auto changing brightness problems for wipe Win8 installs:
** Open desktop
** click/tap on the battery icon in the taskbar, select "More power options"
** Select your current power plan or create a new plan via the link on the left.
** Under the power plan select "Change advanced power settings"
** scroll down to "Display" and expand
** Find the sub-option "Enable adaptive brightness" and expand
** disable both options under this sub-option

== Metro Planning ==

(Older content from the original planning stage)

This is summary of our work / planning for a Win8 Metro browser. For testing purposes we have been working with the /mobile/xul Fennec browser. Moving forward we would like to take the base Fennec XUL code and Metro specific code we've already developed (currently on Elm with some build related work already on mc) and integrate this in with the default Firefox build and install.

We are interested in getting as much feedback as possible from stake holders and from people who have worked with these newer platforms. If you have Win8 up and running in a vm or on a test system, there are details here on how to get builds going, how to register the browser, and test builds for installing.

* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;list_id=2566518 Metro specific bug list]
* [http://piercedotzler.com/asa/Developing_a_Metro-Style_Enabled_Desktop_Browser.html#_Toc318127097 Developing Metro Style Enabled Desktop Browsers]

=== What’s different and what’s the same ===

By in large platform was a nice fit for Metro. We ran into surprisingly few problems. It took us about a week to get a basic version of Fennec running in the environment and most of that time was spent combing through the registration/integration doc Microsoft sent us. Below are some specific details on the areas of the repo we are currently leveraging.

nsBrowserApp

<strike>Currently using fennec’s nsBrowserApp.</strike>

chrome interface markup and css (different)

Metro apps are single window applications. The current desktop UI does not fit this new environment. There are no secondary windows we create. Secondary UI (file pickers, warnings, message boxes, toasts) are all displayed and managed by the os. The interfaces to these features are also async. We will provide interfaces for invoking these. Some have already been integrated on Elm (file picker for example).

browser comps (different)

dictionaries, hyphenation, res, searchplugins, extensions, plugins (shared)

Due to the differences in view model most of /browser components code can’t be leveraged. Fennec's script based components are currently in use. [http://mxr.mozilla.org/mozilla-central/source/mobile/xul/components/]

The current metro browser leverages the Fennec front end app code but we could switch to firefox’s code base and enable / augment what we need for metro.

toolkit/xre (modest differences)

The app model is slightly different for Metro. UI events and rendering do not occur on the main thread. We have a working model implemented on Elm that breaks up parts of XRE_main so that certain parts (startup & run) can be called on a different ‘main’ thread.

widget (mostly shared widget/windows code base with different nsIWidget classes)

There are significant differences in the view model so we needed a new nsWindow class. nsWindow latches into a new set of apis for events and view management. [http://mxr.mozilla.org/projects-central/source/elm/widget/windows/winrt/] Generally winrt and winapi code has integrated well together. We are currently leveraging [http://msdn.microsoft.com/en-us/library/windows/apps/hh755822(v=vs.110).aspx Component Extensions] and various winrt runtime classes. We will be able to share a great deal of win32 widget code.

default browser integration (new registration / launch characteristics for both desktop and metro for win8, older os remains unchanged)

installer/helper/uninstall (shared codebase w/new registration for win8)

On Windows8 the mechanics of launching the browser have changed. There is a new intermediary (a ‘command execute handler’) which is a small, light weight COM server Windows launches. This application chooses which browser to launch based on the environment requested. This change effects the launch of both browsers and the way we register as the default browser on Windows 8. [http://mxr.mozilla.org/projects-central/source/elm/mobile/xul/metro/] We currently have a basic Fennec install going for testing purposes, but it shouldn’t be too hard to move this over to the Firefox installer.

everything else in runtime (shared)

Generally we’re currently leveraging a majority of our common code base without issue. Threading, timers, networking, ssl, layout, gfx, etc. have all fit in really well. Misc. detail -

* gfx - not currently using accelerated layers but plan to in the near future. The surface rendered to in Metro is D2D and there is no GDI fallback. As such there are some issues with blacklisted hardware.
* e10s - currently using Fennec’s out of process tabs.
* Accessibility - not integrated yet.
* Netwerk - no issues.
* Layout - no issues.
* dom & dom/system & hal - DOM interfaces for device info / sensor input and events. Currently there isn't much here for Windows.
* media - no issues.
* storage - works, although there are some profile corruption problems from early termination which can occur in metro. We also have a 'shared profile' problem (see Big Issues).
* toolkit - very little of this is in use. Crash reporter UI will need work/integration.
* xpcom - no issues.

=== A tentative proposal ===

* Copy mobile/xul code down to browser level in /browser/metro.
* Integrate metro startup into firefox's nsBrowserApp {{bug|747347}}.
* Integrate building this new area into the current desktop firefox build. {{bug|747347}}
* Fixup the firefox installer so that we bring both browsers down in a single unified windows install. {{bug|737833}}
* Share the runtime between the two apps in the install. [completed]
* Have nsBrowserApp communicate to xul lib what environment we are running in. [completed]
* Dynamically switch out which code path we want in xul lib where necessary. [completed]
* Organize dist interface code and browser comps such that desktop firefox install layout remains unchanged. Layer metro specific resources down in such a way that the two sets of resources do not conflict. {{bug|755724}}
* <strike>Share a single profile between both browsers</strike> or Sync two profiles on the same machine.

Elm to mozilla-central migration tracking bug: {{bug|747347}}

==== Pros and Cons ====

* Pro – single unified Windows installer / unified browser build.
* Pro – shared runtime without multiple copies of key files like xul.dll.

* Con – larger Windows install regardless of what version of the os we install on. metrobrowser would be present on all Windows installs.
* Con – builders / release eng. will have to upgrade to VC11 / Win8 SDK to do the build. For the time being however we have a build switch that enables win8 specific components, so we can start landing on mc without breaking existing desktop builds which leverage vc10 build tools. {{bug|737994}}

* Pro/Con – With this setup we currently assume we will leverage xul lib. On the positive side having xul makes putting together our UI fast and easy. On the negative side startup performance may be an issue. We are working on getting telemetry data going so we can better measure this in the test builds we are distributing. Thus far test builds we have going on Samsung tablets and a few other test machines show promise on startup performance. Windows is obviously optimized for loading our libraries and the browsers we compete against all have the same encumbrance.

=== Big Issues ===

* Windows XP - The current VC11 Beta redist runtime is not compatible with XP. ({{bug|744942}})
* Profiles – Certain areas of the user’s profile will need to be shared between two concurrently running browser apps. We’ve just begun exploring ways to do this. Potential solution might involve a mysql database connection shim that leverages a profile broker and IPC so both browsers can talk to the same profile. We also might consider using Sync. There are some hurdles here to overcome. [A decision was made to use Sync initially.]
* Accessibility - This area of the code base will be in heavy use in the Metro environment with touch interfaces. Our accessibility code will require performance work and may require a new UI Automation adapter since Win8 leverages UI Automation exclusively.
* e10s - (khuey) Certain things are pretty much broken in e10s (e.g. IndexedDB) and other features have not received any testing in several months. Relying on e10s will likely require some investment in the platform to clean this up for metro/desktop parity. Not relying on e10s may decrease the amount of existing XUL Fennec code that can be reused. [question: (jimm) what's the difference in the amount of work we have to do? We've disabled remote tabs on elm for now to see what's broken.] [A decision was made to use in-process content for the foreseeable future.]
* Extensions - currently extension support will be off until a suitable extension mechanism can be designed and implemented.

== Links ==

* [http://msdn.microsoft.com/en-us/library/windows/apps/br211369%28v=VS.85%29.aspx API for Metro style apps]
* [http://www.pcworld.com/article/240125/windows_8_on_arm_processors_three_working_tablet_demos.html ARM support]

Firefox/Windows 8 Integration

2012-11-05T15:30:56Z

Sfoster: /* DOM Inspector */

== Wiki ==

[https://wiki.mozilla.org/Firefox/Metro Metro Team] - meeting times, bug lists, etc.

[[Firefox/Features|General Firefox Product Feature Tracking]] - Firefox feature tracking.

[[Windows8|Metro Project Status]] - not really in use.

[[Windows_8_Integration]] - General 3rd party browser collaboration page dedicated to overview, architecture, and challenges for vendors. Early research with Google.

== Desktop Development ==

[https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208;query_format=advanced;list_id=2566504 General Windows 8 bug list]

== Metro Development ==

[https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=notregexp;query_format=advancedresolution=---;op_sys=Windows%208%20Metro;list_id=3868779 Bug List] - all open "Windows 8 Metro" bugs

[https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;resolution=---;op_sys=Windows%208%20Metro;list_id=3868779 Bug List] - all open "Windows 8 Metro" bugs minus 'completed-elm' white board tag

=== General Platform Integration ===

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4351876;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;product=Core;product=Toolkit;product=www.mozilla.org Platform Bug List] - Core, Toolkit, mozilla.org

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4351876;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;product=Core;product=Toolkit;product=www.mozilla.org Platform Bug List] - Core, Toolkit, mozilla.org minus 'completed-elm'

=== General Front End ===

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4638979;resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;product=Firefox;product=Firefox%20for%20Metro Front End Buglist]

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4188841;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;product=Firefox;product=Firefox%20for%20Metro Front End Buglist] - minus 'completed-elm'

[https://wiki.mozilla.org/Firefox_Metro_UI Firefox Metro UI wiki] - including comp work and UX bug tracking.

[https://etherpad.mozilla.org/metro-mvp Front-end laundry list] - checklist of front end features.

=== Q3 Firefox Goals ===

[https://bugzilla.mozilla.org/buglist.cgi?quicksearch=sw%3Ametro-preview%20-sw%3Acompleted-elm;list_id=4454405 Tagged Bug List] - metro-preview tagged bugs minus completed-elm.

End of September: "Implement Firefox Metro UI preview: This preview will include primary browser UI for navigation and tabs and will be delivered as a combined classic+metro browser."

Important platform / build bugs:

* <strike>{{bug|755724}}</strike> - split dist/bin resources bug
* <strike>{{bug|737833}}</strike> - basic installer work on elm
* <strike>{{bug|779902}}</strike> - enable nightly metro builds on elm
* <strike>{{bug|782451}}</strike> - copy/paste fails for winrt backend
* <strike>{{bug|787786}}</strike> - UA string
* <strike>{{bug|771238}} / {{bug|785750}}</strike> - file picker freeze

=== Q4 Firefox Goals ===

* WinRT vc10 backport / Merge to mc
* TSF / Soft keyboard contexts
* OMTC / Pinch and Zoom
* Suspend / resume handling
* Local Sync
* Dual-mode scrollbars
* Immersive automated test support w/infrastructure

=== Q1 Firefox Goals ===

* Flash interop
* Accessibility / UIA interop
*

=== Sync specific ===

TBD - new plan based on recent Sync meetings. Need to update this.

Relying on the Sync service for syncing the metro profile with a default desktop profile presents various issues:

* simple sync setup - setting up a new sync account in both browsers is problematic. Device pairing will be troublesome between metro/desktop due to suspend issues. Potentially the installer could be used to do initial setup for both browsers. We could also use a local connection or the registry to populate sync account info in both browsers.
* interprocess communication - when flipping back and forth between metro and the desktop, running instances need to know when they need to sync. {{bug|769424}}
* interprocess identification - the metro browser should communicate it's sync account id when signaling the default desktop browser to sync. {{bug|769424}}
* browser startup - AFAICT from testing, Firefox is configured to sync any new data on delayed startup, then recheck every 90 seconds. Need to confirm metrofx does the same. Assuming this is the default, missed interprocess events shouldn't be an issue.
* smarter interprocess signaling - when signaling another browser the signalee should be aware of whether data was actually updated before triggering events. {{bug|770298}}
* Sync service load - syncing regularly between two browsers will add considerable load on the sync service. TBD how serious this is and whether or not sync 2.0 apis can alleviate the problem.
* network reliance - we would like to avoid this down the road in some TBD way. The current test implementation using the Sync 1.0 service relies on the computer being connected to a network. {{bug|768638}}
* local sync -
** one possible solution would be to add support for importing/exporting changesets over a specific time period. Two clients using the same account could then share changesets rather than hitting the network. Data would be transmitted as json between processes. For security purposes clients would only import data associated with the same account (w/a check before the eval), and data should be obfuscated.
** another solution would be to use a local sync server run by one browser. How would this integrate with the networked sync service?
* mirroring - is there data that doesn't get mirrored between two clients? (deleting a bookmark for example) Mirroring between metrofx and the desktop browser should to be strict both browser should feel as if they are sharing the same profile.
* Sync 1.0 or 2.0 - the sync team has expressed the need for the use of sync 2.0 apis for metro integration. ETA of development.

[https://etherpad.mozilla.org/metro-sync Sync Team etherpad]

=== Plugin specific ===

* Flash: [https://github.com/mozilla/shumway Shumway]
* PDF: {{bug|771250}}
* General plugin support bug: {{bug|738600}}

=== Tests specific ===

Rel-Eng related tracking bugs for Win8 Classic and Metro work:

<bugzilla>
{
"id": "754399,731280"
}
</bugzilla>

Metro testing:

<bugzilla>
{
"id": "771271,759905,773817"
}
</bugzilla>

Currently metro browser chrome tests can be run using 'make mochitest-metro-chrome' in the top level of the objdir.

=== Accessibility specific ===

<bugzilla>
{
"id": "778493,762769, 741750"
}
</bugzilla>

[https://wiki.mozilla.org/Accessibility Accessibility Team wiki] 
{{bug|648121}} - Accessibility telemetry tracking bug

== Getting Involved ==
Contact Brian Bondy with questions (bbondy on [http://irc.mozilla.org IRC]). The Windows 8 integration team can be found in in #windev.

=== Bugzilla ===

Please file front end bugs under the product [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20for%20Metro Firefox for Metro]. Back end bugs should be filed in the appropriate Platform component.

=== Front End Windows 8 Development ===

* To contribute to front end bugs, you will use: JS, CSS, XUL, XBL
* You do not actually need Windows 8 to work on the front end code
* Follow the steps in the Metro Builds section below to get setup
* The front end code is located in browser/metro
* You can find Windows 8 front end bugs here http://goo.gl/YQZiy or by doing an advanced bugzilla search for: OS = Windows 8 Metro, Product = Firefox, Component = General

=== Platform Integration Windows 8 Development ===

* To contribute to platform integration bugs, you will use: C++, C++/CX
* You do need Windows 8 to work on the platform integration code
* You can obtain a 90 day free Windows 8 evaluation for developers from Microsoft
* Follow the steps in the Metro Builds section below to get setup
* The platform integration code is located in widget/windows/winrt
* You can find Windows 8 platform integration bugs here http://goo.gl/B0Xjo or by doing an advanced bugzilla search for: OS = Windows 8 Metro, Product = Core, Component = Widget: Win32

== Metro Builds ==

=== Elm Nightly Builds ===

Nightly builds off the Elm repository where metro development is taking place are currently available in the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-elm/ Firefox build archives].

To set these builds up:

* Install the browser using the latest installer
* Open the desktop browser - when the default browser check occurs, select yes to set Firefox as the default. You should also receive a Windows prompt, select Nightly. This will associate Firefox with various protocol handlers and create the Firefox tile.
* To set file handler associations use Window's Control Panel for default program associations. (Options -> Advanced -> General and click the default browser button at the bottom to open this panel.)

For the time being, only the desktop browser can do browser updates to new builds ({{bug|794936}}, {{bug|794937}}). If prompted to update, make sure to shut the metro browser down first to allow the update to complete.

=== Switching Default Browsers ===

This can be a little tedious when working with multiple builds / installs on a single device. Steps:

* Close Firefox both in Metro and on Desktop
* Open Control Panel's default programs and set IE as the default
* Open the browser you want as the default directly by browsing to the firefox.exe location and double-clicking the exe.
* When prompted to set as default, click yes. In the Windows prompt, choose Nightly.
* In Control Panel's default programs, set firefox as the default browser.

To confirm the right browser is set, launch the browser in Metro, switch to desktop, open task manager, right-click the Firefox process, and select open file location.

Note pinned taskbar shortcuts can't be trusted to open the right browser.

=== Elm Zip Builds ===

Zip installs from daily checkins are currently available on the [http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/elm-win32-metro/ metro builder archives]. Note these are not nightlies, they do not self update. To install:

* Download the newest firefox-18.0a1.en-US.win32.zip to your Win8 device
* Unpack the main firefox folder to a suitable location
* Run firefox.exe
* Set Metro Firefox as the default browser through Firefox preferences, which launches Control Panel -> Default Programs

==== Elm Symbols ====

(Obsolete - dep build symbols no longer uploaded. Use Nightly builds for debugging w/symbols.)

Win8 Metro builders do not upload dep build symbols to the symbol server. However they do upload full symbol packages to the [http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/elm-win32-metro/ metro builder archives]. For debugging zip builds using pdbs, download the full symbols package, unzip to a suitable folder, and unpack the pdbs using the shell command below in the root of the folder. Then add this folder location to the debugging -> symbols paths in Visual Studio under the Tools menu.

<pre>find . -name "*.pd_" | while read FILENAME; do expand -r $FILENAME; done</pre>

=== Building Locally ===

Updated 10/31/2012

* Install Visual Studio 2010 or 2012.
* Install [https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Windows_Prerequisites MozillaBuild]

: For VS 2010/8.0 SDK builds, update to the latest start-msvc2010 batch script from [https://hg.mozilla.org/mozilla-build/summary mozilla-build repo].

* Install the [http://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx Windows 8.0 SDK]
* Modify the the following header in the sdk:

<pre>
C:\Program Files (x86)\Windows Kits\8.0\Include\winrt\asyncinfo.h

line 67:

enum class AsyncStatus {

to

enum /*class*/ AsyncStatus {
</pre>

* Check out Elm. Make sure the obj directory has "Modify" permissions given to the current user.
* Create a standard browser .mozconfig file with the options you prefer and add

<pre>
ac_add_options --enable-metro
ac_add_options --disable-webrtc
</pre>

* Config and build Elm

: Notes:
* WebRTC issues are being sorted out in {{bug|799121}}

At this point, you should be able to launch the metro browser on the desktop using a command line switch:

<pre>
(obj)/dist/bin/firefox.exe -metrodesktop
</pre>

For registering as the default Metro browser:

* Run firefox.exe on the desktop and set as the default
* Open up Control Panel -> Default Programs. You should see 'Metro Firefox' in the list of applications.
* Set all Metro Firefox defaults in Default Programs.

At which point you should have a Firefox tile in Win8 that launches the browser.

=== Desktop Launch ===

To launch within the metro experience follow the registration steps above. To launch the metro front end UI using the win32 widget backend on the desktop (including non-Windows-8 devices) use the -metrodesktop command line option:

<pre>(path to firefox build)/firefox.exe -metrodesktop</pre>

To set things up such that you can test touch input on the desktop - flip the 'metro.debug.treatmouseastouch' to true in /browser/metro/profile/metro.js.

Note on the desktop we use the desktop's Win32/Widget backend. This can behave differently from the Win8 WinRT backend. The translational layer for Win32 events is location in /browser/metro/content/base/input.js.

=== Testing ===

[https://developer.mozilla.org/en-US/docs/Browser_chrome_tests Browser-chrome tests] for Metro Firefox are located in [http://hg.mozilla.org/projects/elm/file/default/browser/metro/base/tests/ browser/metro/base/tests]. The tests run in the Metro environment; Windows 8 is required.

To start the tests, run the following command in the mozilla-build shell, at the top level of your obj-dir:

make mochitest-metro-chrome

The Metro browser will launch, run the tests and exit. Any failures will be printed to the console. The complete test log will be written to the file <code>mochitest-metro-chrome.log</code> in the objdir.

=== Building on Linux or Mac OS X ===

You can use the ''--enable-metro'' configure option and the ''-metrodesktop'' command-line flag to build and run the Metro UI on other platforms too. For details, see [http://limpet.net/mbrubeck/2012/09/19/metro-firefox-without-windows.html Metro Firefox without Windows 8].

=== Logging Assertions ===

When you're running Metro Firefox with --enable-debug, there will be assertion failure messages that pop up. Because they appear on the desktop and block the UI, they will make the Metro UI appear to hang until you dismiss them on the desktop. You can set the following environment variable to ensure that they're logged rather than displayed as popups:

<pre>
XPCOM_DEBUG_BREAK=warn
</pre>

=== Remote Debug Output ===

NSPR logging can be dumped to OutputDebugString using the NSPR_LOG_FILE environment variable:

<pre>
NSPR_LOG_FILE=WinDebug
</pre>

To log NS assertions and warnings in debug builds add the nsDebug log module:

<pre>
NSPR_LOG_MODULES=nsDebug:4
</pre>

<strike>{{bug|762519}}</strike> was filed on getting javascript's dump output going to OutputDebugString as well.

=== DOM Inspector ===

Getting DOM Inspector attached to builds running on the desktop takes a few tweaks.

* Copy the 'inspector@mozilla.org' folder under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory.
* add an entry in inspector's install.rdf file for metrofx and make sure the maxVersion is set correctly.

<pre>
<em:targetApplication>
<Description>
<em:id>{99bceaaa-e3c6-48c1-b981-ef9b46b67d60}</em:id>
<em:minVersion>1.0a1</em:minVersion>
<em:maxVersion>19.0a1</em:maxVersion>
</Description>
</em:targetApplication>
</pre>

* Add the [https://developer.mozilla.org/en/XULRunner_tips startDOMi function] to /browser/metro/base/content/browser.js.
* Add a call to startDOMi() below the BrowserUI.init() call.
* Tweak the following extension prefs in metro.js:
<pre>
pref("extensions.autoDisableScopes", 15);
pref("extensions.minCompatibleAppVersion", "4.0");
pref("extensions.strictCompatibility", false);
</pre>

* The extensions.sqlite database file will be created the first time MetroFirefox is run and discovers the inspector@mozilla.org extension content in the profile, but you have to flip a couple of values to make it actually work. Using your favorite sqlite tool (the [https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ SQLite Manager Add-on] works), find the inspector's entry in the 'addon' table and set the 'active' field to integer 1, and the userDisabled field to integer value 0.

=== Venkman Debugger ===

(10/5/12 - Note, since we've changed the app id, this probably doesn't work.)

* Copy the '{f13b157f-b174-47e7-a34d-4815ddfdfeb8}' xpi under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory.

* Launch the browser with the '-venkman' command line option.

=== JS Shell ===

For debugging the ede js shell and javascript console are available on the app bar in desktop builds.

=== WinRT Compiler Generated Code ===

Compiler switches:
* /d1ZWtokens - dump C++ code generated code for C++/CX.
* /d1reportAllClassLayout - dump class layouts
* /d1reportSingleClassLayoutXXX - where XXX performs substring matches against the class name.

=== Remote Debugging with a VM ===

(This was last tested with the Win8 RP)

Setup steps -

* create a new drive for vm, clone src there, build. obj dir should also be on this drive.
* Enable sharing on the drive, set permissions to full access
* On workstation, map vm share to a local drive. Use the same drive letter for both the vm drive and the mapped workstation drive!
* config vm’s metro firefox as the default Metro browser
* on vm, start – ‘debug’ should bring up remote debug tools folder – run the x64 version if on 64 bit os, x86 otherwise
* start remote debugger on vm
* create empty remote debugging project on workstation
* in project set debug settings:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: vm network name w/ port
** Attach: Yes
* Launch browser in vm
* F5 in project on workstation

That should be it. OutputDebugString output will land in the workstation debugger console. Breaking in the debugger doesn't kill the browser as long as metro is active and the browser is running in the foreground.

Note – AFAICT, you can’t reverse the relationship here. Metro will not launch a default browser located on a mapped drive that points to an obj dir on workstation. If we could fine a way around this it would be great.

=== Remote Debugging with a Tablet ===

Setup steps -

* Install Win8 on the tablet, use the same login/password you use on the workstation you'll be debugging from.
* From Explorer purge any unused space on C, including old Windows installation files using the system file cleanup option under the drive's properties panel.
* From Control Panel, bring up the disk manager and split the main partition into two. A 80GB/20GB split is suitable.
* Format the second partition and designate a drive letter for it. Use a drive letter your main workstation doesn't use.
* Right-click the new drive in Explorer and select Share. Share this volume for your login credentials, you can also openly share it to everyone if your local network is secure. Set permissions on the share to full access.
* On your main workstation, map the tablet share to a local drive. Use the same drive letter for both the tablet drive and the mapped workstation drive. This insures object source has the same path info.
* Checkout Elm on the second drive of the tablet, build and register the browser.
* On the tablet, Start + ‘debug’ should bring up remote debug tools folder – run the x64 version if on 64 bit os, x86 otherwise.
* On the workstation, create a debugging project for the tablet, set debug settings as follows:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: Tablet network name w/ port. The remote debugging tools window on the tablet can provide this.
** Attach: Yes

After this you should be able to launch the browser on the tablet and attach to it from Visual Studio on your workstation. You should also be able to browse source on the networked drive, set break points, etc., just like a local debug session.

== Hardware ==

[https://docs.google.com/spreadsheet/ccc?key=0AowtJTCuyojddHpMeDV5czhDMkU0bFBKTktQLUhkbnc Asa's Google Docs list of Win8 touch friendly hardware]

== Samsung Series 7 ==

The Series seven is the first device we started developing with. Details below on getting the hardware set up with Windows 8.

* To order, file a bug under mozilla.org, Server Operations: Desktop Issues. See {{bug|738613}}, CC your PM or Asa.

* Once you have the tablet, dock, and keyboard, unpack. Charge up the device. It'll be running Win7, ignore all the default software.

* Download the 64-bit (3.6 gig) Win8 ISO from \\fs2\IT\Microsoft. Add your name to the list of people who will need product keys in {{bug|783811}}. Burn the ISO to a suitable memory stick. For burning on Windows you'll need to download and install the [http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool Windows 7 USB DVD Download Tool] from Microsoft. For burning on mac?

* Once you have the ISO burned, plug the USB stick into the tablet's dock. Browse to the USB drive and run "setup.exe". When prompted choose that you want to save nothing from the previous install.

* Samsung provides an instruction manual on hooking up the Bluetooth keyboard. You can do this after you've installed Win8 as the Win7 desktop instructions are applicable on Win8 desktop.

* After the tablet is set up, download Firefox nightly or build a local copy and start debugging!

=== Firmware Updates ===

For more precise touch input, especially with tap and hold, install the "Touch Screen Sensor Firmware Configuration Updater Tool". Updating the system bios from 7 to 10 doesn't hurt either. Make sure to reboot the system after the install.

[http://www.samsung.com/global/windowspreview/ Samsung Link]

=== Samsung Series 7 Tweaks ===

* To fix auto changing brightness problems for wipe Win8 installs:
** Open desktop
** click/tap on the battery icon in the taskbar, select "More power options"
** Select your current power plan or create a new plan via the link on the left.
** Under the power plan select "Change advanced power settings"
** scroll down to "Display" and expand
** Find the sub-option "Enable adaptive brightness" and expand
** disable both options under this sub-option

== Metro Planning ==

(Older content from the original planning stage)

This is summary of our work / planning for a Win8 Metro browser. For testing purposes we have been working with the /mobile/xul Fennec browser. Moving forward we would like to take the base Fennec XUL code and Metro specific code we've already developed (currently on Elm with some build related work already on mc) and integrate this in with the default Firefox build and install.

We are interested in getting as much feedback as possible from stake holders and from people who have worked with these newer platforms. If you have Win8 up and running in a vm or on a test system, there are details here on how to get builds going, how to register the browser, and test builds for installing.

* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;list_id=2566518 Metro specific bug list]
* [http://piercedotzler.com/asa/Developing_a_Metro-Style_Enabled_Desktop_Browser.html#_Toc318127097 Developing Metro Style Enabled Desktop Browsers]

=== What’s different and what’s the same ===

By in large platform was a nice fit for Metro. We ran into surprisingly few problems. It took us about a week to get a basic version of Fennec running in the environment and most of that time was spent combing through the registration/integration doc Microsoft sent us. Below are some specific details on the areas of the repo we are currently leveraging.

nsBrowserApp

<strike>Currently using fennec’s nsBrowserApp.</strike>

chrome interface markup and css (different)

Metro apps are single window applications. The current desktop UI does not fit this new environment. There are no secondary windows we create. Secondary UI (file pickers, warnings, message boxes, toasts) are all displayed and managed by the os. The interfaces to these features are also async. We will provide interfaces for invoking these. Some have already been integrated on Elm (file picker for example).

browser comps (different)

dictionaries, hyphenation, res, searchplugins, extensions, plugins (shared)

Due to the differences in view model most of /browser components code can’t be leveraged. Fennec's script based components are currently in use. [http://mxr.mozilla.org/mozilla-central/source/mobile/xul/components/]

The current metro browser leverages the Fennec front end app code but we could switch to firefox’s code base and enable / augment what we need for metro.

toolkit/xre (modest differences)

The app model is slightly different for Metro. UI events and rendering do not occur on the main thread. We have a working model implemented on Elm that breaks up parts of XRE_main so that certain parts (startup & run) can be called on a different ‘main’ thread.

widget (mostly shared widget/windows code base with different nsIWidget classes)

There are significant differences in the view model so we needed a new nsWindow class. nsWindow latches into a new set of apis for events and view management. [http://mxr.mozilla.org/projects-central/source/elm/widget/windows/winrt/] Generally winrt and winapi code has integrated well together. We are currently leveraging [http://msdn.microsoft.com/en-us/library/windows/apps/hh755822(v=vs.110).aspx Component Extensions] and various winrt runtime classes. We will be able to share a great deal of win32 widget code.

default browser integration (new registration / launch characteristics for both desktop and metro for win8, older os remains unchanged)

installer/helper/uninstall (shared codebase w/new registration for win8)

On Windows8 the mechanics of launching the browser have changed. There is a new intermediary (a ‘command execute handler’) which is a small, light weight COM server Windows launches. This application chooses which browser to launch based on the environment requested. This change effects the launch of both browsers and the way we register as the default browser on Windows 8. [http://mxr.mozilla.org/projects-central/source/elm/mobile/xul/metro/] We currently have a basic Fennec install going for testing purposes, but it shouldn’t be too hard to move this over to the Firefox installer.

everything else in runtime (shared)

Generally we’re currently leveraging a majority of our common code base without issue. Threading, timers, networking, ssl, layout, gfx, etc. have all fit in really well. Misc. detail -

* gfx - not currently using accelerated layers but plan to in the near future. The surface rendered to in Metro is D2D and there is no GDI fallback. As such there are some issues with blacklisted hardware.
* e10s - currently using Fennec’s out of process tabs.
* Accessibility - not integrated yet.
* Netwerk - no issues.
* Layout - no issues.
* dom & dom/system & hal - DOM interfaces for device info / sensor input and events. Currently there isn't much here for Windows.
* media - no issues.
* storage - works, although there are some profile corruption problems from early termination which can occur in metro. We also have a 'shared profile' problem (see Big Issues).
* toolkit - very little of this is in use. Crash reporter UI will need work/integration.
* xpcom - no issues.

=== A tentative proposal ===

* Copy mobile/xul code down to browser level in /browser/metro.
* Integrate metro startup into firefox's nsBrowserApp {{bug|747347}}.
* Integrate building this new area into the current desktop firefox build. {{bug|747347}}
* Fixup the firefox installer so that we bring both browsers down in a single unified windows install. {{bug|737833}}
* Share the runtime between the two apps in the install. [completed]
* Have nsBrowserApp communicate to xul lib what environment we are running in. [completed]
* Dynamically switch out which code path we want in xul lib where necessary. [completed]
* Organize dist interface code and browser comps such that desktop firefox install layout remains unchanged. Layer metro specific resources down in such a way that the two sets of resources do not conflict. {{bug|755724}}
* <strike>Share a single profile between both browsers</strike> or Sync two profiles on the same machine.

Elm to mozilla-central migration tracking bug: {{bug|747347}}

==== Pros and Cons ====

* Pro – single unified Windows installer / unified browser build.
* Pro – shared runtime without multiple copies of key files like xul.dll.

* Con – larger Windows install regardless of what version of the os we install on. metrobrowser would be present on all Windows installs.
* Con – builders / release eng. will have to upgrade to VC11 / Win8 SDK to do the build. For the time being however we have a build switch that enables win8 specific components, so we can start landing on mc without breaking existing desktop builds which leverage vc10 build tools. {{bug|737994}}

* Pro/Con – With this setup we currently assume we will leverage xul lib. On the positive side having xul makes putting together our UI fast and easy. On the negative side startup performance may be an issue. We are working on getting telemetry data going so we can better measure this in the test builds we are distributing. Thus far test builds we have going on Samsung tablets and a few other test machines show promise on startup performance. Windows is obviously optimized for loading our libraries and the browsers we compete against all have the same encumbrance.

=== Big Issues ===

* Windows XP - The current VC11 Beta redist runtime is not compatible with XP. ({{bug|744942}})
* Profiles – Certain areas of the user’s profile will need to be shared between two concurrently running browser apps. We’ve just begun exploring ways to do this. Potential solution might involve a mysql database connection shim that leverages a profile broker and IPC so both browsers can talk to the same profile. We also might consider using Sync. There are some hurdles here to overcome. [A decision was made to use Sync initially.]
* Accessibility - This area of the code base will be in heavy use in the Metro environment with touch interfaces. Our accessibility code will require performance work and may require a new UI Automation adapter since Win8 leverages UI Automation exclusively.
* e10s - (khuey) Certain things are pretty much broken in e10s (e.g. IndexedDB) and other features have not received any testing in several months. Relying on e10s will likely require some investment in the platform to clean this up for metro/desktop parity. Not relying on e10s may decrease the amount of existing XUL Fennec code that can be reused. [question: (jimm) what's the difference in the amount of work we have to do? We've disabled remote tabs on elm for now to see what's broken.] [A decision was made to use in-process content for the foreseeable future.]
* Extensions - currently extension support will be off until a suitable extension mechanism can be designed and implemented.

== Links ==

* [http://msdn.microsoft.com/en-us/library/windows/apps/br211369%28v=VS.85%29.aspx API for Metro style apps]
* [http://www.pcworld.com/article/240125/windows_8_on_arm_processors_three_working_tablet_demos.html ARM support]

Firefox/Windows 8 Integration

2012-11-05T15:29:44Z

Sfoster: /* DOM Inspector */

== Wiki ==

[https://wiki.mozilla.org/Firefox/Metro Metro Team] - meeting times, bug lists, etc.

[[Firefox/Features|General Firefox Product Feature Tracking]] - Firefox feature tracking.

[[Windows8|Metro Project Status]] - not really in use.

[[Windows_8_Integration]] - General 3rd party browser collaboration page dedicated to overview, architecture, and challenges for vendors. Early research with Google.

== Desktop Development ==

[https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208;query_format=advanced;list_id=2566504 General Windows 8 bug list]

== Metro Development ==

[https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=notregexp;query_format=advancedresolution=---;op_sys=Windows%208%20Metro;list_id=3868779 Bug List] - all open "Windows 8 Metro" bugs

[https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;resolution=---;op_sys=Windows%208%20Metro;list_id=3868779 Bug List] - all open "Windows 8 Metro" bugs minus 'completed-elm' white board tag

=== General Platform Integration ===

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4351876;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;product=Core;product=Toolkit;product=www.mozilla.org Platform Bug List] - Core, Toolkit, mozilla.org

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4351876;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;product=Core;product=Toolkit;product=www.mozilla.org Platform Bug List] - Core, Toolkit, mozilla.org minus 'completed-elm'

=== General Front End ===

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4638979;resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;product=Firefox;product=Firefox%20for%20Metro Front End Buglist]

[https://bugzilla.mozilla.org/buglist.cgi?list_id=4188841;resolution=---;op_sys=Windows%208%20Metro;status_whiteboard_type=notregexp;query_format=advanced;status_whiteboard=completed-elm;product=Firefox;product=Firefox%20for%20Metro Front End Buglist] - minus 'completed-elm'

[https://wiki.mozilla.org/Firefox_Metro_UI Firefox Metro UI wiki] - including comp work and UX bug tracking.

[https://etherpad.mozilla.org/metro-mvp Front-end laundry list] - checklist of front end features.

=== Q3 Firefox Goals ===

[https://bugzilla.mozilla.org/buglist.cgi?quicksearch=sw%3Ametro-preview%20-sw%3Acompleted-elm;list_id=4454405 Tagged Bug List] - metro-preview tagged bugs minus completed-elm.

End of September: "Implement Firefox Metro UI preview: This preview will include primary browser UI for navigation and tabs and will be delivered as a combined classic+metro browser."

Important platform / build bugs:

* <strike>{{bug|755724}}</strike> - split dist/bin resources bug
* <strike>{{bug|737833}}</strike> - basic installer work on elm
* <strike>{{bug|779902}}</strike> - enable nightly metro builds on elm
* <strike>{{bug|782451}}</strike> - copy/paste fails for winrt backend
* <strike>{{bug|787786}}</strike> - UA string
* <strike>{{bug|771238}} / {{bug|785750}}</strike> - file picker freeze

=== Q4 Firefox Goals ===

* WinRT vc10 backport / Merge to mc
* TSF / Soft keyboard contexts
* OMTC / Pinch and Zoom
* Suspend / resume handling
* Local Sync
* Dual-mode scrollbars
* Immersive automated test support w/infrastructure

=== Q1 Firefox Goals ===

* Flash interop
* Accessibility / UIA interop
*

=== Sync specific ===

TBD - new plan based on recent Sync meetings. Need to update this.

Relying on the Sync service for syncing the metro profile with a default desktop profile presents various issues:

* simple sync setup - setting up a new sync account in both browsers is problematic. Device pairing will be troublesome between metro/desktop due to suspend issues. Potentially the installer could be used to do initial setup for both browsers. We could also use a local connection or the registry to populate sync account info in both browsers.
* interprocess communication - when flipping back and forth between metro and the desktop, running instances need to know when they need to sync. {{bug|769424}}
* interprocess identification - the metro browser should communicate it's sync account id when signaling the default desktop browser to sync. {{bug|769424}}
* browser startup - AFAICT from testing, Firefox is configured to sync any new data on delayed startup, then recheck every 90 seconds. Need to confirm metrofx does the same. Assuming this is the default, missed interprocess events shouldn't be an issue.
* smarter interprocess signaling - when signaling another browser the signalee should be aware of whether data was actually updated before triggering events. {{bug|770298}}
* Sync service load - syncing regularly between two browsers will add considerable load on the sync service. TBD how serious this is and whether or not sync 2.0 apis can alleviate the problem.
* network reliance - we would like to avoid this down the road in some TBD way. The current test implementation using the Sync 1.0 service relies on the computer being connected to a network. {{bug|768638}}
* local sync -
** one possible solution would be to add support for importing/exporting changesets over a specific time period. Two clients using the same account could then share changesets rather than hitting the network. Data would be transmitted as json between processes. For security purposes clients would only import data associated with the same account (w/a check before the eval), and data should be obfuscated.
** another solution would be to use a local sync server run by one browser. How would this integrate with the networked sync service?
* mirroring - is there data that doesn't get mirrored between two clients? (deleting a bookmark for example) Mirroring between metrofx and the desktop browser should to be strict both browser should feel as if they are sharing the same profile.
* Sync 1.0 or 2.0 - the sync team has expressed the need for the use of sync 2.0 apis for metro integration. ETA of development.

[https://etherpad.mozilla.org/metro-sync Sync Team etherpad]

=== Plugin specific ===

* Flash: [https://github.com/mozilla/shumway Shumway]
* PDF: {{bug|771250}}
* General plugin support bug: {{bug|738600}}

=== Tests specific ===

Rel-Eng related tracking bugs for Win8 Classic and Metro work:

<bugzilla>
{
"id": "754399,731280"
}
</bugzilla>

Metro testing:

<bugzilla>
{
"id": "771271,759905,773817"
}
</bugzilla>

Currently metro browser chrome tests can be run using 'make mochitest-metro-chrome' in the top level of the objdir.

=== Accessibility specific ===

<bugzilla>
{
"id": "778493,762769, 741750"
}
</bugzilla>

[https://wiki.mozilla.org/Accessibility Accessibility Team wiki] 
{{bug|648121}} - Accessibility telemetry tracking bug

== Getting Involved ==
Contact Brian Bondy with questions (bbondy on [http://irc.mozilla.org IRC]). The Windows 8 integration team can be found in in #windev.

=== Bugzilla ===

Please file front end bugs under the product [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20for%20Metro Firefox for Metro]. Back end bugs should be filed in the appropriate Platform component.

=== Front End Windows 8 Development ===

* To contribute to front end bugs, you will use: JS, CSS, XUL, XBL
* You do not actually need Windows 8 to work on the front end code
* Follow the steps in the Metro Builds section below to get setup
* The front end code is located in browser/metro
* You can find Windows 8 front end bugs here http://goo.gl/YQZiy or by doing an advanced bugzilla search for: OS = Windows 8 Metro, Product = Firefox, Component = General

=== Platform Integration Windows 8 Development ===

* To contribute to platform integration bugs, you will use: C++, C++/CX
* You do need Windows 8 to work on the platform integration code
* You can obtain a 90 day free Windows 8 evaluation for developers from Microsoft
* Follow the steps in the Metro Builds section below to get setup
* The platform integration code is located in widget/windows/winrt
* You can find Windows 8 platform integration bugs here http://goo.gl/B0Xjo or by doing an advanced bugzilla search for: OS = Windows 8 Metro, Product = Core, Component = Widget: Win32

== Metro Builds ==

=== Elm Nightly Builds ===

Nightly builds off the Elm repository where metro development is taking place are currently available in the [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-elm/ Firefox build archives].

To set these builds up:

* Install the browser using the latest installer
* Open the desktop browser - when the default browser check occurs, select yes to set Firefox as the default. You should also receive a Windows prompt, select Nightly. This will associate Firefox with various protocol handlers and create the Firefox tile.
* To set file handler associations use Window's Control Panel for default program associations. (Options -> Advanced -> General and click the default browser button at the bottom to open this panel.)

For the time being, only the desktop browser can do browser updates to new builds ({{bug|794936}}, {{bug|794937}}). If prompted to update, make sure to shut the metro browser down first to allow the update to complete.

=== Switching Default Browsers ===

This can be a little tedious when working with multiple builds / installs on a single device. Steps:

* Close Firefox both in Metro and on Desktop
* Open Control Panel's default programs and set IE as the default
* Open the browser you want as the default directly by browsing to the firefox.exe location and double-clicking the exe.
* When prompted to set as default, click yes. In the Windows prompt, choose Nightly.
* In Control Panel's default programs, set firefox as the default browser.

To confirm the right browser is set, launch the browser in Metro, switch to desktop, open task manager, right-click the Firefox process, and select open file location.

Note pinned taskbar shortcuts can't be trusted to open the right browser.

=== Elm Zip Builds ===

Zip installs from daily checkins are currently available on the [http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/elm-win32-metro/ metro builder archives]. Note these are not nightlies, they do not self update. To install:

* Download the newest firefox-18.0a1.en-US.win32.zip to your Win8 device
* Unpack the main firefox folder to a suitable location
* Run firefox.exe
* Set Metro Firefox as the default browser through Firefox preferences, which launches Control Panel -> Default Programs

==== Elm Symbols ====

(Obsolete - dep build symbols no longer uploaded. Use Nightly builds for debugging w/symbols.)

Win8 Metro builders do not upload dep build symbols to the symbol server. However they do upload full symbol packages to the [http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/elm-win32-metro/ metro builder archives]. For debugging zip builds using pdbs, download the full symbols package, unzip to a suitable folder, and unpack the pdbs using the shell command below in the root of the folder. Then add this folder location to the debugging -> symbols paths in Visual Studio under the Tools menu.

<pre>find . -name "*.pd_" | while read FILENAME; do expand -r $FILENAME; done</pre>

=== Building Locally ===

Updated 10/31/2012

* Install Visual Studio 2010 or 2012.
* Install [https://developer.mozilla.org/en-US/docs/Developer_Guide/Build_Instructions/Windows_Prerequisites MozillaBuild]

: For VS 2010/8.0 SDK builds, update to the latest start-msvc2010 batch script from [https://hg.mozilla.org/mozilla-build/summary mozilla-build repo].

* Install the [http://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx Windows 8.0 SDK]
* Modify the the following header in the sdk:

<pre>
C:\Program Files (x86)\Windows Kits\8.0\Include\winrt\asyncinfo.h

line 67:

enum class AsyncStatus {

to

enum /*class*/ AsyncStatus {
</pre>

* Check out Elm. Make sure the obj directory has "Modify" permissions given to the current user.
* Create a standard browser .mozconfig file with the options you prefer and add

<pre>
ac_add_options --enable-metro
ac_add_options --disable-webrtc
</pre>

* Config and build Elm

: Notes:
* WebRTC issues are being sorted out in {{bug|799121}}

At this point, you should be able to launch the metro browser on the desktop using a command line switch:

<pre>
(obj)/dist/bin/firefox.exe -metrodesktop
</pre>

For registering as the default Metro browser:

* Run firefox.exe on the desktop and set as the default
* Open up Control Panel -> Default Programs. You should see 'Metro Firefox' in the list of applications.
* Set all Metro Firefox defaults in Default Programs.

At which point you should have a Firefox tile in Win8 that launches the browser.

=== Desktop Launch ===

To launch within the metro experience follow the registration steps above. To launch the metro front end UI using the win32 widget backend on the desktop (including non-Windows-8 devices) use the -metrodesktop command line option:

<pre>(path to firefox build)/firefox.exe -metrodesktop</pre>

To set things up such that you can test touch input on the desktop - flip the 'metro.debug.treatmouseastouch' to true in /browser/metro/profile/metro.js.

Note on the desktop we use the desktop's Win32/Widget backend. This can behave differently from the Win8 WinRT backend. The translational layer for Win32 events is location in /browser/metro/content/base/input.js.

=== Testing ===

[https://developer.mozilla.org/en-US/docs/Browser_chrome_tests Browser-chrome tests] for Metro Firefox are located in [http://hg.mozilla.org/projects/elm/file/default/browser/metro/base/tests/ browser/metro/base/tests]. The tests run in the Metro environment; Windows 8 is required.

To start the tests, run the following command in the mozilla-build shell, at the top level of your obj-dir:

make mochitest-metro-chrome

The Metro browser will launch, run the tests and exit. Any failures will be printed to the console. The complete test log will be written to the file <code>mochitest-metro-chrome.log</code> in the objdir.

=== Building on Linux or Mac OS X ===

You can use the ''--enable-metro'' configure option and the ''-metrodesktop'' command-line flag to build and run the Metro UI on other platforms too. For details, see [http://limpet.net/mbrubeck/2012/09/19/metro-firefox-without-windows.html Metro Firefox without Windows 8].

=== Logging Assertions ===

When you're running Metro Firefox with --enable-debug, there will be assertion failure messages that pop up. Because they appear on the desktop and block the UI, they will make the Metro UI appear to hang until you dismiss them on the desktop. You can set the following environment variable to ensure that they're logged rather than displayed as popups:

<pre>
XPCOM_DEBUG_BREAK=warn
</pre>

=== Remote Debug Output ===

NSPR logging can be dumped to OutputDebugString using the NSPR_LOG_FILE environment variable:

<pre>
NSPR_LOG_FILE=WinDebug
</pre>

To log NS assertions and warnings in debug builds add the nsDebug log module:

<pre>
NSPR_LOG_MODULES=nsDebug:4
</pre>

<strike>{{bug|762519}}</strike> was filed on getting javascript's dump output going to OutputDebugString as well.

=== DOM Inspector ===

Getting DOM Inspector attached to builds running on the desktop takes a few tweaks.

* Copy the 'inspector@mozilla.org' folder under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory.
* add an entry in inspector's install.rdf file for metrofx and make sure the maxVersion is set correctly.

<pre>
<em:targetApplication>
<Description>
<em:id>{99bceaaa-e3c6-48c1-b981-ef9b46b67d60}</em:id>
<em:minVersion>1.0a1</em:minVersion>
<em:maxVersion>19.0a1</em:maxVersion>
</Description>
</em:targetApplication>
</pre>

* Add the [https://developer.mozilla.org/en/XULRunner_tips startDOMi function] to /browser/metro/base/content/browser.js.
* Add a call to startDOMi() below the BrowserUI.init() call.
* Tweak the following extension prefs in metro.js:
<pre>
pref("extensions.autoDisableScopes", 15);
pref("extensions.minCompatibleAppVersion", "4.0");
pref("extensions.strictCompatibility", false);
</pre>

* The extensions.sqlite database file will be created the first time Firefox is run and discovers the inspector@mozilla.org extension content in the profile, but you have to flip a couple of values to make it actually work. Using your favorite sqlite tool (the [https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ SQLite Manager Add-on] works), find the inspector's entry in the 'addon' table and set the 'active' field to integer 1, and the userDisabled field to integer value 0.

=== Venkman Debugger ===

(10/5/12 - Note, since we've changed the app id, this probably doesn't work.)

* Copy the '{f13b157f-b174-47e7-a34d-4815ddfdfeb8}' xpi under your Firefox profile's extension directory over to your MetroFirefox profile extensions directory.

* Launch the browser with the '-venkman' command line option.

=== JS Shell ===

For debugging the ede js shell and javascript console are available on the app bar in desktop builds.

=== WinRT Compiler Generated Code ===

Compiler switches:
* /d1ZWtokens - dump C++ code generated code for C++/CX.
* /d1reportAllClassLayout - dump class layouts
* /d1reportSingleClassLayoutXXX - where XXX performs substring matches against the class name.

=== Remote Debugging with a VM ===

(This was last tested with the Win8 RP)

Setup steps -

* create a new drive for vm, clone src there, build. obj dir should also be on this drive.
* Enable sharing on the drive, set permissions to full access
* On workstation, map vm share to a local drive. Use the same drive letter for both the vm drive and the mapped workstation drive!
* config vm’s metro firefox as the default Metro browser
* on vm, start – ‘debug’ should bring up remote debug tools folder – run the x64 version if on 64 bit os, x86 otherwise
* start remote debugger on vm
* create empty remote debugging project on workstation
* in project set debug settings:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: vm network name w/ port
** Attach: Yes
* Launch browser in vm
* F5 in project on workstation

That should be it. OutputDebugString output will land in the workstation debugger console. Breaking in the debugger doesn't kill the browser as long as metro is active and the browser is running in the foreground.

Note – AFAICT, you can’t reverse the relationship here. Metro will not launch a default browser located on a mapped drive that points to an obj dir on workstation. If we could fine a way around this it would be great.

=== Remote Debugging with a Tablet ===

Setup steps -

* Install Win8 on the tablet, use the same login/password you use on the workstation you'll be debugging from.
* From Explorer purge any unused space on C, including old Windows installation files using the system file cleanup option under the drive's properties panel.
* From Control Panel, bring up the disk manager and split the main partition into two. A 80GB/20GB split is suitable.
* Format the second partition and designate a drive letter for it. Use a drive letter your main workstation doesn't use.
* Right-click the new drive in Explorer and select Share. Share this volume for your login credentials, you can also openly share it to everyone if your local network is secure. Set permissions on the share to full access.
* On your main workstation, map the tablet share to a local drive. Use the same drive letter for both the tablet drive and the mapped workstation drive. This insures object source has the same path info.
* Checkout Elm on the second drive of the tablet, build and register the browser.
* On the tablet, Start + ‘debug’ should bring up remote debug tools folder – run the x64 version if on 64 bit os, x86 otherwise.
* On the workstation, create a debugging project for the tablet, set debug settings as follows:
** Remote command: (common letter drive):\(path to obj dir)\dist\bin\firefox.exe
** Working dir – same
** Remove Server Name: Tablet network name w/ port. The remote debugging tools window on the tablet can provide this.
** Attach: Yes

After this you should be able to launch the browser on the tablet and attach to it from Visual Studio on your workstation. You should also be able to browse source on the networked drive, set break points, etc., just like a local debug session.

== Hardware ==

[https://docs.google.com/spreadsheet/ccc?key=0AowtJTCuyojddHpMeDV5czhDMkU0bFBKTktQLUhkbnc Asa's Google Docs list of Win8 touch friendly hardware]

== Samsung Series 7 ==

The Series seven is the first device we started developing with. Details below on getting the hardware set up with Windows 8.

* To order, file a bug under mozilla.org, Server Operations: Desktop Issues. See {{bug|738613}}, CC your PM or Asa.

* Once you have the tablet, dock, and keyboard, unpack. Charge up the device. It'll be running Win7, ignore all the default software.

* Download the 64-bit (3.6 gig) Win8 ISO from \\fs2\IT\Microsoft. Add your name to the list of people who will need product keys in {{bug|783811}}. Burn the ISO to a suitable memory stick. For burning on Windows you'll need to download and install the [http://www.microsoftstore.com/store/msstore/html/pbPage.Help_Win7_usbdvd_dwnTool Windows 7 USB DVD Download Tool] from Microsoft. For burning on mac?

* Once you have the ISO burned, plug the USB stick into the tablet's dock. Browse to the USB drive and run "setup.exe". When prompted choose that you want to save nothing from the previous install.

* Samsung provides an instruction manual on hooking up the Bluetooth keyboard. You can do this after you've installed Win8 as the Win7 desktop instructions are applicable on Win8 desktop.

* After the tablet is set up, download Firefox nightly or build a local copy and start debugging!

=== Firmware Updates ===

For more precise touch input, especially with tap and hold, install the "Touch Screen Sensor Firmware Configuration Updater Tool". Updating the system bios from 7 to 10 doesn't hurt either. Make sure to reboot the system after the install.

[http://www.samsung.com/global/windowspreview/ Samsung Link]

=== Samsung Series 7 Tweaks ===

* To fix auto changing brightness problems for wipe Win8 installs:
** Open desktop
** click/tap on the battery icon in the taskbar, select "More power options"
** Select your current power plan or create a new plan via the link on the left.
** Under the power plan select "Change advanced power settings"
** scroll down to "Display" and expand
** Find the sub-option "Enable adaptive brightness" and expand
** disable both options under this sub-option

== Metro Planning ==

(Older content from the original planning stage)

This is summary of our work / planning for a Win8 Metro browser. For testing purposes we have been working with the /mobile/xul Fennec browser. Moving forward we would like to take the base Fennec XUL code and Metro specific code we've already developed (currently on Elm with some build related work already on mc) and integrate this in with the default Firefox build and install.

We are interested in getting as much feedback as possible from stake holders and from people who have worked with these newer platforms. If you have Win8 up and running in a vm or on a test system, there are details here on how to get builds going, how to register the browser, and test builds for installing.

* [https://bugzilla.mozilla.org/buglist.cgi?resolution=---;op_sys=Windows%208%20Metro;query_format=advanced;list_id=2566518 Metro specific bug list]
* [http://piercedotzler.com/asa/Developing_a_Metro-Style_Enabled_Desktop_Browser.html#_Toc318127097 Developing Metro Style Enabled Desktop Browsers]

=== What’s different and what’s the same ===

By in large platform was a nice fit for Metro. We ran into surprisingly few problems. It took us about a week to get a basic version of Fennec running in the environment and most of that time was spent combing through the registration/integration doc Microsoft sent us. Below are some specific details on the areas of the repo we are currently leveraging.

nsBrowserApp

<strike>Currently using fennec’s nsBrowserApp.</strike>

chrome interface markup and css (different)

Metro apps are single window applications. The current desktop UI does not fit this new environment. There are no secondary windows we create. Secondary UI (file pickers, warnings, message boxes, toasts) are all displayed and managed by the os. The interfaces to these features are also async. We will provide interfaces for invoking these. Some have already been integrated on Elm (file picker for example).

browser comps (different)

dictionaries, hyphenation, res, searchplugins, extensions, plugins (shared)

Due to the differences in view model most of /browser components code can’t be leveraged. Fennec's script based components are currently in use. [http://mxr.mozilla.org/mozilla-central/source/mobile/xul/components/]

The current metro browser leverages the Fennec front end app code but we could switch to firefox’s code base and enable / augment what we need for metro.

toolkit/xre (modest differences)

The app model is slightly different for Metro. UI events and rendering do not occur on the main thread. We have a working model implemented on Elm that breaks up parts of XRE_main so that certain parts (startup & run) can be called on a different ‘main’ thread.

widget (mostly shared widget/windows code base with different nsIWidget classes)

There are significant differences in the view model so we needed a new nsWindow class. nsWindow latches into a new set of apis for events and view management. [http://mxr.mozilla.org/projects-central/source/elm/widget/windows/winrt/] Generally winrt and winapi code has integrated well together. We are currently leveraging [http://msdn.microsoft.com/en-us/library/windows/apps/hh755822(v=vs.110).aspx Component Extensions] and various winrt runtime classes. We will be able to share a great deal of win32 widget code.

default browser integration (new registration / launch characteristics for both desktop and metro for win8, older os remains unchanged)

installer/helper/uninstall (shared codebase w/new registration for win8)

On Windows8 the mechanics of launching the browser have changed. There is a new intermediary (a ‘command execute handler’) which is a small, light weight COM server Windows launches. This application chooses which browser to launch based on the environment requested. This change effects the launch of both browsers and the way we register as the default browser on Windows 8. [http://mxr.mozilla.org/projects-central/source/elm/mobile/xul/metro/] We currently have a basic Fennec install going for testing purposes, but it shouldn’t be too hard to move this over to the Firefox installer.

everything else in runtime (shared)

Generally we’re currently leveraging a majority of our common code base without issue. Threading, timers, networking, ssl, layout, gfx, etc. have all fit in really well. Misc. detail -

* gfx - not currently using accelerated layers but plan to in the near future. The surface rendered to in Metro is D2D and there is no GDI fallback. As such there are some issues with blacklisted hardware.
* e10s - currently using Fennec’s out of process tabs.
* Accessibility - not integrated yet.
* Netwerk - no issues.
* Layout - no issues.
* dom & dom/system & hal - DOM interfaces for device info / sensor input and events. Currently there isn't much here for Windows.
* media - no issues.
* storage - works, although there are some profile corruption problems from early termination which can occur in metro. We also have a 'shared profile' problem (see Big Issues).
* toolkit - very little of this is in use. Crash reporter UI will need work/integration.
* xpcom - no issues.

=== A tentative proposal ===

* Copy mobile/xul code down to browser level in /browser/metro.
* Integrate metro startup into firefox's nsBrowserApp {{bug|747347}}.
* Integrate building this new area into the current desktop firefox build. {{bug|747347}}
* Fixup the firefox installer so that we bring both browsers down in a single unified windows install. {{bug|737833}}
* Share the runtime between the two apps in the install. [completed]
* Have nsBrowserApp communicate to xul lib what environment we are running in. [completed]
* Dynamically switch out which code path we want in xul lib where necessary. [completed]
* Organize dist interface code and browser comps such that desktop firefox install layout remains unchanged. Layer metro specific resources down in such a way that the two sets of resources do not conflict. {{bug|755724}}
* <strike>Share a single profile between both browsers</strike> or Sync two profiles on the same machine.

Elm to mozilla-central migration tracking bug: {{bug|747347}}

==== Pros and Cons ====

* Pro – single unified Windows installer / unified browser build.
* Pro – shared runtime without multiple copies of key files like xul.dll.

* Con – larger Windows install regardless of what version of the os we install on. metrobrowser would be present on all Windows installs.
* Con – builders / release eng. will have to upgrade to VC11 / Win8 SDK to do the build. For the time being however we have a build switch that enables win8 specific components, so we can start landing on mc without breaking existing desktop builds which leverage vc10 build tools. {{bug|737994}}

* Pro/Con – With this setup we currently assume we will leverage xul lib. On the positive side having xul makes putting together our UI fast and easy. On the negative side startup performance may be an issue. We are working on getting telemetry data going so we can better measure this in the test builds we are distributing. Thus far test builds we have going on Samsung tablets and a few other test machines show promise on startup performance. Windows is obviously optimized for loading our libraries and the browsers we compete against all have the same encumbrance.

=== Big Issues ===

* Windows XP - The current VC11 Beta redist runtime is not compatible with XP. ({{bug|744942}})
* Profiles – Certain areas of the user’s profile will need to be shared between two concurrently running browser apps. We’ve just begun exploring ways to do this. Potential solution might involve a mysql database connection shim that leverages a profile broker and IPC so both browsers can talk to the same profile. We also might consider using Sync. There are some hurdles here to overcome. [A decision was made to use Sync initially.]
* Accessibility - This area of the code base will be in heavy use in the Metro environment with touch interfaces. Our accessibility code will require performance work and may require a new UI Automation adapter since Win8 leverages UI Automation exclusively.
* e10s - (khuey) Certain things are pretty much broken in e10s (e.g. IndexedDB) and other features have not received any testing in several months. Relying on e10s will likely require some investment in the platform to clean this up for metro/desktop parity. Not relying on e10s may decrease the amount of existing XUL Fennec code that can be reused. [question: (jimm) what's the difference in the amount of work we have to do? We've disabled remote tabs on elm for now to see what's broken.] [A decision was made to use in-process content for the foreseeable future.]
* Extensions - currently extension support will be off until a suitable extension mechanism can be designed and implemented.

== Links ==

* [http://msdn.microsoft.com/en-us/library/windows/apps/br211369%28v=VS.85%29.aspx API for Metro style apps]
* [http://www.pcworld.com/article/240125/windows_8_on_arm_processors_three_working_tablet_demos.html ARM support]

Pancake/Team/Meetings/2012-09-17

2012-09-17T19:13:45Z

Sfoster: /* Sam Foster (sfoster) */

== Gordon Brander (gordonb) ==

Past week:

* Comp of app updates screen https://wiki.mozilla.org/File:French-toast-history-concept.e.05.png
* Update to recent searches comp https://wiki.mozilla.org/File:French-toast-type-ahead-concept.c.01.png
* Type-ahead search comp https://wiki.mozilla.org/File:French-toast-type-ahead-concept-2.c.01.png
* App Updates Feed comp https://wiki.mozilla.org/File:French-toast-feed-concept.c.01.png
* Keynote spec describing and showing French Toast's layer interactions.
* HTML/CSS Prototype:
** Updates feed
** Search results
** Website pin
** Website update

== Sam Foster (sfoster) ==

Past week:

Being a week of work in the prototype [https://github.com/mozillapancake/pancake-ft-client French Toast pancake client] (app-skeleton branch)

* Search and search results functional.
* Stubs in place for url opening (Pancake.* APIs)
* Login/logout behaviour driven by (observable) username and session settings
* Exploring localStorage + storage events. Can react to logout/login and other setting changes across open windows/tabs
* Hooked up POST to stack/search to create new sessions
* Hooked up active stacks query
* Prototyped router and route for search terms (gives us working search + search result urls)
* Node.js reverse-proxying server checked in under 'proxy' directory. npm install && npm start to install/run

Coming up:

* At a [http://ongamestart.com/ conference] Wed, Thurs, Friday of this week; spotty availability
* Break out "saved searches" (session/active) onto its own page
* Create browser-based viewer for testing/development
* Wire up content and applications links to explore layer behavior
* Further implementation/integration of the proposed Pancake.* APIs for full application lifecycle

Pancake/Team/Meetings/2012-09-17

2012-09-17T18:47:32Z

Sfoster: Notes for week of 09/17

== Gordon Brander (gordonb) ==

Past week:

* Comp of app updates screen https://wiki.mozilla.org/File:French-toast-history-concept.e.05.png
* Update to recent searches comp https://wiki.mozilla.org/File:French-toast-type-ahead-concept.c.01.png
* Type-ahead search comp https://wiki.mozilla.org/File:French-toast-type-ahead-concept-2.c.01.png
* App Updates Feed comp https://wiki.mozilla.org/File:French-toast-feed-concept.c.01.png
* Keynote spec describing and showing French Toast's layer interactions.
* HTML/CSS Prototype:
** Updates feed
** Search results
** Website pin
** Website update

== Sam Foster (sfoster) ==

Past week:

Being a week of work in the prototype [https://github.com/mozillapancake/pancake-ft-client French Toast pancake client] (app-skeleton branch)

* Search and search results functional.
* Stubs in place for url opening (Pancake.* APIs)
* Login/logout behaviour driven by (observable) username and session settings
* Exploring localStorage + storage events. Can react to logout/login and other setting changes across open windows/tabs
* Hooked up POST to stack/search to create new sessions
* Hooked up active stacks query
* Prototyped router and route for search terms (gives us working search + search result urls)
* Node.js reverse-proxying server checked in under 'proxy' directory. npm install && npm start to install/run

Coming up:

* Break out "saved searches" (session/active) onto its own page
* Create browser-based viewer for testing/development
* Wire up content and applications links to explore layer behavior
* Further implementation/integration of the proposed Pancake.* APIs for full application lifecycle

Pancake/French Toast/Message API

2012-09-12T10:42:28Z

Sfoster: /* Discussion */

=== User stories ===

==== As a front-end developer, I need a way to tell the native app to open a new layer containing a specific layer state. ====

FrenchToast.openApplicationView(url)

==== As a front-end developer, I need a way to tell the native app to open a URL in the viewer. ====

FrenchToast.openPublicView(url)

''I don't think we need the name parameter. I don't think we want layers to be able to talk directly to each other. Instead, I believe we can stick to a service-oriented architecture based on URLs.'' -[[Gbrander]]

==== As a front-end developer, I need the app to tell me when a layer has received focus so that I can check for updates and refresh data if necessary. ====

What about a DOM event?

window.addEventListener('layerFocus', fn)

'' Focus isn't quite the same as active/visible. On the desktop, focus doesn't happen until an element in the window receives focus. I'm not sure how that plays out on touch devices. I think we want visibility''

''There is an actual API for this: [http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility/Overview.html PageVisibility] but we would have to investigate browser support. As I understand it, our "layers" are going to be window object in UiWebViews or their equivalent, so this seems like the right place to start. I would rather polyfill this though than invent our own.''

* http://davidwalsh.name/page-visibility
* https://developer.mozilla.org/en-US/docs/DOM/Using_the_Page_Visibility_API
* https://github.com/ai/visibility.js

==== As a front-end developer, I need a way to securely ''verify that the user is authenticated'' so that I do not expose confidential information. ====

// find out if the current session is valid
FrenchToast.getSession()

// to start browserid
FrenchToast.startBrowserId(callback)

// to validate the browserid token
FrenchToast.validateBrowserIdReceipt(receipt, callback)

''Can somebody who worked on the session stuff in the past verify that these could satisfy the user story?'' - [[Gbrander]]

''What about the way it works today are we wanting to fix? This functionality currently resides in the misnamed/misplaced [https://github.com/mozillapancake/pancake-ft-client/blob/app-skeleton/js/lib/signin.js lib/signin]. ISTM that the modules under service/* could be FrenchToast.*. Lets talk.'' - [[Sfoster]]

==== As a front-end developer, I need access to a shared store that persists across sessions. All layers should have access to this store. ====

Use standard localStorage to serialize/deserialize persisted app data.

window.localStorage
JSON.stringify
JSON.parse

''Can we confirm that the same localStorage is available between UIWebViews'' - [[Gbrander]]

=== Discussion ===

''I don't think we need a general message mechanism to talk to the app. I also don't think we need to be able to send messages to specific layers from specific layers. In general, I would like to make the coupling between layers loose, and based on requesting URLs be opened. The layer itself can decide what to do with the URL.'' -[[Gbrander]]

''Agreed that urls should be the primary messaging mechanism. We also have storage events which (browser-support willing) should allow us to signal state changes like login/logout across windows/layers. I suspect there's still a need for the native/js messaging though.

Pancake/French Toast/Message API

2012-09-12T10:37:13Z

Sfoster: /* As a front-end developer, I need the app to tell me when a layer has received focus so that I can check for updates and refresh data if necessary. */

Pancake/French Toast/Store

2012-09-11T13:52:16Z

Sfoster: /* As a front-end developer, I need to transform data coming from the server for display on the client-side. I need this transformed data to be "live". It should be updated when the original data is updated. */

=== User Scenarios ===

==== As a front-end developer, I need my program to be "push" notified of updates from the server and other data sources, so that the client can efficiently react to the most up-to-date information. ====

''By making the store an intermediary between the "client" (the app and its viewModel) and the server (or wherever data needs to come from) we give the store the role of a central dispatcher. Using an EventEmitter (like node.js) we can make the store an event source and the viewModel's properties the event sink. Now, any change to the store (e.g. incoming data from the server, or some other part of the UI) is broadcast to the queries (live resultsets) which it impacts. '' [[Sfoster]]

==== As a front-end developer, I need to be able to specifiy sub-sets of information and be notified when these sub-sets change, so that parts of the interface can react to the data that interests them. ====

''There are a few ways to do this. Event channels is one. Filtering is another. If you think about it, event channels are really a domain specific language around querying change notifications. I prefer a filtering approach because predicate functions are more flexible than DSLs. If we still should want an event channel DSL, we could create one on top of predicate functions.'' -[[Gbrander]]

''We have a simple-enough implementation borrowed from dojo's object store. Its query method accepts a dictionary of properties as predicate for the matching, and returns a lazy array of results. Furthermore, put/add/remove operations on the store trigger a check on these queries to determine if their results are impacted, and the change is sent to these resultsets via its observe mechanism. The query engine is pluggable - we can use a more sophisticated engine if necessary. The observe method on resultsets does not itself speak EventEmitter, but is easily wired into. There's an assumption baked into the design that reads are more frequent than writes - as each write essentially re-applies all open queries against the data.'' [[Sfoster]]

''The client-side store is there to provide convenient access to data and abstracts away details of where the data originally comes from. To this end, we decorate records with a <code>meta_type_</code>name<code>: true</code>, making queries for types as easy as <code>store.query({ meta_type_foo: true })</code>. Similarly, the composite nature of some responses is flattenned out - each object in s a response is filed separately'' [[Sfoster]]

==== As a front-end developer, I need to transform data coming from the server for display on the client-side. I need this transformed data to be "live". It should be updated when the original data is updated. ====

''Knockout.js is a capable and flexible data-binding library. It provides for "extenders" - functions attached to an observable value which provide a hook to respond to value changes. A <code>composeWith</code> extender allows us to specify a list of functions which can progressively filter, decorate and reduce values down to a render-ready value. The function composition happens once as the observable is assigned, and is executed each time the underlying value changes. '' [[Sfoster]]

Pancake/French Toast/Store

2012-09-11T13:43:55Z

Sfoster: /* As a front-end developer, I need to be able to specifiy sub-sets of information and be notified when these sub-sets change, so that parts of the interface can react to the data that interests them. */

Pancake/French Toast/Store

2012-09-11T13:30:25Z

Sfoster: /* As a front-end developer, I need my program to be "push" notified of updates from the server and other data sources, so that the client can efficiently react to the most up-to-date information. */

Pancake/French Toast/Message API

2012-09-11T13:14:11Z

Sfoster: /* As a front-end developer, I need a way to securely verify that the user is authenticated so that I do not expose confidential information. */

Pancake/French Toast/Message API

2012-09-11T13:12:20Z

Sfoster: /* As a front-end developer, I need a way to securely verify that the user is authenticated so that I do not expose confidential information. */

Pancake/Team/Meetings/2012-09-10

2012-09-10T19:32:04Z

Sfoster:

== Gordon (gbrander) ==

* Design concepts for
** Type-ahead search
** Search results
** Updates screen
** Lv 0 tabs
* Started prototyping HTML/CSS for French Toast https://github.com/gordonbrander/french-toast-html
* Recorded design/engineering decisions and resources
** Created project page on Wiki for everything French Toast https://wiki.mozilla.org/Pancake/French_Toast
** Wrote up user scenarios and approaches for:
*** App messaging https://wiki.mozilla.org/Pancake/French_Toast/Message_API
*** Client-side store (via conversation with sfoster) https://wiki.mozilla.org/Pancake/French_Toast/Store
*** IO/AJAX (via conversation with sfoster) https://wiki.mozilla.org/Pancake/French_Toast/IO
*** Layer navigation behavior https://wiki.mozilla.org/Pancake/UX/Navigation
*** Search https://wiki.mozilla.org/Pancake/UX/Search
*** Type-ahead search https://wiki.mozilla.org/Pancake/UX/Type-ahead_Search

== Sam (sfoster) ==

* Front-end architecture prototype dev
** Ajax middleware implemented for request and response filtering/adapting
** LocalStorage store implementation; reactive, localStorage-backed app settings
** EventEmitter-based 'streams' join data APIs to viewModel properties
** Knockout.js 'wireTo' extension to hook an observable array to a stream
** Troubleshooting data flow and promises - now using promised-io's promise.js (unmodified)
* FE status: https://github.com/mozillapancake/pancake-ft-client
** 'install' using volo not working - vendor/js is populated in the git repo and should work as-is
** Load search/index.html as '/search/' to see current state of play (not much to see)

This week
---------
* Hook up persona and session tokens to id and authenticate user (populating settings.username())
* Build out dashboard, list and detail view templates to work on flow between "pages"
* On-going API/data implementation to populate viewModels

Pancake/Team/Meetings/2012-08-20

2012-08-20T18:19:49Z

Sfoster:

== Deb (dria) ==
'''Last week'''
* Put together a comprehensive initial (draft) list of user stories for French Toast & started matching those to proposed development phases
* Short email exchange with Cori about research projects, following up this week

'''This week'''
* Finish first draft of user stories & development plan for French toast (ping me if you want access)
* Look in to some tools for managing/tracking an agile dev plan like this (suggestions welcome -- currently only know of Pivotal Tracker)
* Meet with Cori re: Sharing user study & get that ball rolling
* Sort out (likely with Gordon) plan for doing our own lightweight usability testing on a biweekly basis (UR team doesn't do those, apparently)
* Make time to read a bunch of Pancake-related things that have been in my queue for a while (several books)

== Gordon (gordonb) ==

* Updated demo path
* Created Keynote UX Deck for IDEO
* Updated wireframes
** Switched to infinite stacking paradigm, instead of multiple layers of tabs
** Ideation for Discovery mode
** Revisited browsing controls
** Snap back to Lv1 behavior
** Updated search results
** Removed sidebar from Lv2 and 3.
* Wrapped up Keynote prototype
* Tested module conversion scripts (Node -> AMD) so we can use Node libraries on the front end
* Investigated amd forked pancake-ft-client
* Investigating amd-store, getting familiar

== Stefan ==

* Experimented with Linked In's Cleo typeahead engine
* Learned how to use Elastic MapReduce in both Streaming and Native (Java) modes
* Processed various data sets on Elastic MapReduce as input for Cleo
* Deployed a typeahead prototype

== Sam (sfoster) ==

* Exploration of using dojo/store as backing store with Knockout.js doing data-binding: https://github.com/sfoster/todomvc/tree/amdstore_ko
* Started skeleton app to prototype French Toast front-end architecture: https://github.com/mozillapancake/pancake-ft-client

Pancake/Team/Meetings/2012-08-13

2012-08-13T19:16:08Z

Sfoster:

== Deb (dria) ==
'''Last week'''
* Final review of current French Toast designs, all is well & very excited to get started
* Put together initial draft of French Toast development plan
* Sent User Research projects proposal (first two) to Cori - no word yet, but I think she's in Brazil
* Went through some user research projects again in detail, started brainstorming out potential Pancake details based on them
* Got my Nexus 7 and have started using it as my primary tablet in prep for Android client

'''This week'''
* Flesh out French Toast development plan
* Follow up with Cori about user research proposal
* Further brainstorming/thinking around user research findings
* Further thinking about a larger/longer-term user research project (4-6 month)
* Finalize what needs to move to the public wiki in order to do an initial release & move those things
* Start digging in to whatever research or information is available about search and sharing. Deep dive on these.

== Gordon (gbrander) ==

Last week:

* Created interactive prototype Keynote, with all screens and states interconnected by links. Everything screen except profile is represented.
* Updated wireframes
** Explored interaction paradigms for layer stacking, allowing users to easily hop between layers.
** Wireframe for app dashboard
** Updates to wireframes based on interactive prototype feedback
* Updated UX deck with changes to wireframes.
* Tested conversion scripts for Node JavaScript modules, making them AMD (client) compatible. This opens up a few potential libraries for use on the front-end.
* HTML prototyping a TODOs app with Reducers library. This library could potentially simplify and improve performance of the front-end. We're giving it a smoke test by building a simple TODOs app with it.

This week:

* Add profile to the interactive prototype
* Create a full animated demo path for the app
* A few tweaks to the layer interaction model for the Keynote prototype.
* [[Pancake/Prototyping | Lean user testing with the prototype]].
* A bit more experimentation with Reducers.

My goal is to make as much progress on design as possible right now so we don't end up with engineering outpacing design.

== Sam (sfoster) ==

Last Week:

* Exploring reactive programming approaches, reducers library
** Formed poor opinion of browserify
* Port of dojo store API and implementation with composable LocalStorage, Observable, JsonRest classes and mixins
** IndexDB-based API
** extensible architecture
** AMD with little/no dependencies
** "live" query results, opt-in item and item-property level change notification
* Exploring data-binding and reactive-style "views"
* Prototype TODO app using said store and handlebars for templating
* Review/prototype of entity/component based app architecture
** TODO proof-of-concept app underway

This week:

* Closure on above explorations
* Caching store proof of concept
* Initial lattice API prototype
* Integration plan as appropriate

== Stefan ==

=== Last week ===

* I've mostly been learning Android and hacking on a basic Pancake prototype.
* Pushed code to http://github.com/mozillapancake/pancake-android
* Configured a Jenkins instance to do automatic builds
* Builds can be grabbed from http://play.fxhome.mozillalabs.com/builds/Pancake-release-unsigned.apk
* Pushed a new build of Pancake to staging
* Dealt with a Persona issue that might affect us (deprecating older API Urls)

=== This week ===

* Trying to get more functionality in the Android app.
* Experimenting with Linkedin's Cleo for Typeahead search

== Olivier ==

'''Last week'''
* Looked into some app packaging issues
* Wrote bits of a url recommendation engine based on pancake data

'''This week'''
* Finish url recommendation engine
* Deployment to production
* Configuration of stats backends in staging & production

== Nhirata ==
* Nada for Pancake
* Most work has been b2g gaia work and crashkill for mobile.
* same thing for this week plus holiday.
* same thing for the next week plus holiday.
* on holiday from 15 ~ 20th (friends' wedding. Will be back on the 21st.)

Webdev:Conferences

2012-03-13T10:29:52Z

Sfoster: Added We-5 conf in Q2 April

= 2012 =
== Q1 ==
* Jan 11 [http://waza.heroku.com/ Heroku's Waza] San Francisco, USA
** tofumatt may attend
** mkelly
* Jan 16-20 [http://linux.conf.au linux.conf.au] Ballarat, Australia
** laura (speaking)
* Jan 18-20 [http://webvisionsevent.com Webvisions], NYC
** skinny (speaking)
* Feb 4-5 [http://fosdem.org/2012/ FOSDEM 2012], Brussels, Belgium
* Feb 29-Mar 2 [http://confoo.ca/en Confoo] Montréal
** andym (speaking) [http://confoo.ca/en/2012/session/real-time-web-apps-using-python gevent] and [http://confoo.ca/en/2012/session/unit-testing-with-python Unit testing]
* March 7-15 [http://us.pycon.org/2012 pycon] Santa Clara
** Erik (talks)
** james bennett (tutorials)
** kumar
** Rob Hudson
** ashort
** willkg
** mkelly
** ckoehler
** lars
** dd
** timw
** cmore (Django tutorial only [https://us.pycon.org/2012/schedule/presentation/327/ 1] [https://us.pycon.org/2012/schedule/presentation/458/ 2] -- no conf.)
* March 24-25 [http://libreplanet.org/wiki/LibrePlanet2012 LibrePlanet 2012] Cambridge, MA
** willkg

== Q2 ==
* April 2-3 [http://2012.jsconf.us/ JSConf] Scottsdale, Arizona
** potch
** jlongster (hoping to speak)
** espressive
* April 4-6 [http://web-5.org/ Web-5] Béziers(34), France
** sfoster (speaking)
** robert nyman (speaking)
* April 14-15 [http://rencontres.django-fr.org/2012/ Djangocong] Carnon-Montpellier, France [sponsoring]
** Rik
* May 23-24 [http://gluecon.com/2012/] GLUE Con
** lorchard (?)
* June 4-8 [http://2012.djangocon.eu/ DjangoCon EU] Zurich, Switzerland
** Rik
* June 26-29 [http://opensourcebridge.org Open Source Bridge] Portland, OR
** ckoehler
** wenzel?
** skinny

== Q3 ==

* July 5-7 [http://webvisionsevent.com Webvisions], Barcelona
** skinny (speaking)
* July 16-20 [http://www.oscon.com/oscon2012 OSCON], Portland
** andym (submitting talk)
** laura (submitted talk, on committee)
** ednapiranha?
* July 20-22, [http://throneofjs.com/ Throne of JS], Toronto, ON
* July 25-26, [https://www.blackhat.com/html/bh-us-12/bh-us-12-home.html BlackHat], Las Vegas, NV
* July 26-29, [http://lanyrd.com/2012/defcon/ Defcon 20], Las Vegas, NV
* Sept 3-8 DjangoCon, Washington DC
** andym (submitting talk)
** jsocol (I've had good luck recruiting/promoting for Moz here)
** groovecoder
** pmclanahan
** laura? local!

== Q4 ==
* Dec (last week) Chaos Computer Congress (29C3), Berlin

<div class="NavFrame collapsed">
<div class="NavHead">2011</div>
<div class="NavContent" style="text-align:left">

= 2011 =
== Q1 ==
* Feb 5-6 - [http://fosdem.org/2011/ fosdem]
* Feb 19 - [http://superhappydevhouse.org SuperHappyDevHouse] @ Tech Museum of Innovation in San Jose
** lorchard?
* March 9-11 - [http://confoo.ca/en ConFoo.ca]
** andym (speaking)
* March 11-13 - [http://us.pycon.org/2011/ PyCon US]
** wenzel
** kumar (speaking)
* March 11-15 - [http://sxsw.com/interactive/talks/sessions SXSWinteractive]
** laura (speaking)

== Q2 ==
* April 9-10 - [http://codeconf.com/ CodeConf]
** jbalogh
* May 10-11 - [http://www.google.com/events/io/2010/ Google I/O]
** lorchard?
* May 25-26, [http://www.gluecon.com/ GlueCon]
** paulc?
* May 27, [http://schoolofdev.com/Tulsa/2011/default.aspx Tulsa School of Dev]
** groovecoder
* June 6-9, [http://djangocon.eu DjangoCon EU]
** andym (speaking)
* June 21-24, [http://opensourcebridge.org Open Source Bridge], Portland OR
** All of us!
** ryansnyder (speaking)
** wenzel (speaking)
* June 27-29, [http://futureofwebapps.com/las-vegas-2011/ The Future of Web Apps], Las Vegas, NV

== Q3 ==

* July 25-29, [http://www.oscon.com/oscon2011 OSCON], Portland OR
** kumar?
** laura (speaking)
** (various IT people)
* July 30 - Aug 4, [http://www.blackhat.com/ Blackhat], Las Vegas, NV
** clouserw
* Sept 6-10 - DjangoCon
** davedash (speaking)
** brandonsavage
** tofumatt would like to be put in the raffle
* Sept 16-17 [http://pygotham.org/ PyGotham], New York, NY
** jsocol
* Sept 28-30 [http://omniti.com/surge/2011 Surge], Baltimore MD

== Q4 ==
* Oct 6-7 - [http://py.codeconf.com/ PyCodeConf 2011 (Miami, Florida, US)] -- "Future of Python" conf put on by the folks from GitHub
** ricky
** laura (speaking)
** wenzel
** erikrose
** jlongster
** timw
** peterbe
* Oct 13-15 - [http://www.paris-web.fr/ ParisWeb 2011] Paris
** Rik - How browsers work
* Oct 20 - [http://www.contactcon.com/ Contact Summit 2011]
** lorchard?
** Contact will explore how to realize the greater promise of social media to promote new forms of culture, commerce, collective action and creativity.
* Oct 22-27 - [http://splashcon.org/2011/ SPLASH (formerly OOPSLA)]. OOPSLA is a >1000-person conference on everything from Haskell to Java to Smalltalk to software engineering in general—always an amazing collection of people. It's in Portland this year.
** erikrose
* Nov 1-2 - [http://www.newgameconf.com/ New Game Conference]
** "The Conference for HTML5 Game Developers" Google and Bocoup are putting this on- we should have a Mozilla presence to keep the debate lively :)
** potch
* Nov 7-11 - [http://na11.apachecon.com/ ApacheCon] Vancouver, BC
* Nov 8-9 - [http://www.hadoopworld.com Hadoop World] NYC
* Nov 8-9 - [http://velocityconf.com/velocityeu/ Velocity Conference EU] Berlin
** Rik
* Nov 9-10 - [http://www.defragcon.com/ Defrag]
* Nov 9-12 - [http://gracehopper.org/2011/ Grace Hopper Celebration of Women in Computing]. PDX Has an Open Source day, Lukas and Stormy are on a panel
** laura?
* Nov 12-13 - [http://somethin-else.org/index.php?post/2011/08/16/Save-the-date%21-Mozilla-Camp-Europe-2011-Berlin-%28Nov-12-13%29 MozCamp Europe 2011] Berlin
** Rik
* Dec 5-7 - [http://www.pmi.org/en/Professional-Development/SeminarsWorld/CourseScheduleDetails.aspx?CourseScheduleID={9CAF9A7C-FFD1-4754-9213-3BF0292E35B5} Project Management Institute's - Learning Simulation]
** cmore
</div>
</div>

<div class="NavFrame collapsed">
<div class="NavHead">2010</div>
<div class="NavContent" style="text-align:left">

= 2010 =
== Q1 ==
* [http://fosdem.org/2010/ fosdem] Feb 6--7
** wenzel
* [http://sxsw.com/interactive SXSW] March 12-16
** ozten
** jsocol (bump for other folks)
* [http://www.larpcon.com/ LARPcon]
** wclouser
** mccammos
** lorchard (totally have my own boffers)

== Q2 ==
* [http://aneventapart.com/2010/seattle/ An Event Apart (Seattle)] April 5--7
** jsocol
** rdoherty
* [http://en.oreilly.com/mysql2010/ MySQLConf] April 12--15
** jsocol
* [http://events.jquery.org/2010/sf-bay-area JQuery SF Bay Area Conference] April 24--25
* [http://djangocon.eu/ djangocon.eu] Berlin, May 24--26/28
* [http://www.gluecon.com/2010/ GlueCon] and CloudCamp, Denver, CO May 25--28
** lorchard
* [http://opensourcebridge.org/ Open Source Bridge] Portland, June 1--4
** skeen
* [http://en.oreilly.com/velocity2010 Velocity] June 22--24
* [http://java.sun.com/javaone/ JavaOne] June 22--25
** jbalogh

== Q3 ==
* [http://en.oreilly.com/oscon2010 OSCON] July 19--23
** lorchard
** lars
** laura (committee, maybe speaking)
** skeen
* [http://www.blackhat.com/ Blackhat] July 24--29
** abuchanan
** paulc
* [http://www.uxweek.com/ UX Week] August 24--27
* [http://djangocon.us/ DjangoCon] September 7--9
** dd - went last year, but I felt it was helpful
** jbalogh - as long as it doesn't conflict with CakeFest, I'm gonna talk about zamboni. In front of people.
** clouserw
** jsocol
** paulc?
** wenzel
** ricky
* [http://ideaconference.org/ IDEA] Sept 14--16
** rdoherty
* [http://www.aneventapart.com/2010/dc/ An Event Apart (DC)] September 16-18
* [http://handcraftedcss.com/ Handcrafted CSS] Sept 14
* [http://cakefest.org/ CakeFest]
** jbalogh
* [http://www.twicon.org/ TwiCon]
** morgamic - I will be presenting on why Jake is better than Edward.
** fligtarsmom
* [http://omniti.com/surge/2010 Surge] Sept 30 - Oct 1

== Q4 ==
* [http://www.svgopen.org/2009/ SVG Open 2009], Oct 2-4
* [http://www.uist2010.org/ UIST (NYC)] Oct 3-6
* [http://futureofwebapps.com/london-2010/ Future of Web Apps (London)] Oct 4-6
* [http://fronteers.nl/congres Fronteers], Oct 4-8
* [http://www.cloudera.com/company/events/hadoop-world-2010 Hadoop World] Oct 12
* [http://ar.pycon.org/2010/about/ PyCon Argentina], Oct 15-16
** Ian: I'll be giving a keynote
* [http://www.pythonbrasil.org.br/2010 Python Brasil], Oct 21-23
** Ian: I'll be giving a keynote here too
* [http://www.aneventapart.com/2010/sandiego/ An Event Apart (San Diego)] Nov 1-2

</div>
</div>

<div class="NavFrame collapsed">
<div class="NavHead">2009</div>
<div class="NavContent" style="text-align:left">
= 2009 =
== Q2 ==
* [http://java.sun.com/javaone/ JavaOne]
* Velocity
** rdoherty
** jbalogh (if anyone else wants to bump me out and come down, that's cool)

== Q3 ==
* Blackhat
** clouserw
* OSCON
** ozten
** lars
** laura
* [http://djangocon09.eventbrite.com/ DjangoCon]
** ddash
** jbalogh

== Q4 ==
* [http://www.svgopen.org/2009/ SVG Open 2009], Oct 2-4
* [http://ideaconference.org/ IDEA] Sept 14-16
** Neil (?)
* [http://handcraftedcss.com/ Handcrafted CSS] Sept 14
** might be interesting?
</div>
</div>