MozillaWiki - User contributions [en]

Firefox/CSS Tips

2019-10-20T10:53:06Z

P.A.: Add link to up-to-date documentation on MDN

This page contains information about CSS used in the Firefox front end.

<div style="margin: 1em 0px; border: 2px solid orange; padding: 1em; background-color: #FFC; text-align: center;">'''More detailed and up-to-date documentation is available on MDN at:[https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/CSS_Guidelines The Firefox codebase: CSS Guidelines]'''</div>

== Basics ==

First, you can find the existing Firefox CSS at https://dxr.mozilla.org/mozilla-central/source/browser/themes. Here are some basic tips that can result in faster reviews if you are changing CSS.

* Split your CSS into theme and content files (see below)
* Avoid <tt>!important</tt> but if you have to use it, make sure it's obvious why you're using it (maybe with a comment)
* Avoid magic numbers, prefer automatic sizing
* Avoid setting styles in JavaScript. It's generally better to set a class and then specify the styles in CSS
* <tt>classList</tt> is generally better than <tt>className</tt>. There's less chance of over-writing an existing class

=== Boilerplate ===

Make sure each file starts with the standard copyright header (see [https://www.mozilla.org/MPL/headers/ License Boilerplate])

=== Testing ===

CSS changes to the frontend should generally be similar across platforms since they mostly use a shared implementation, but there can still be differences worth checking out. Ideally you should test major changes on all of Windows, OS X and Ubuntu in both light and dark themes.

== Formatting ==

In general the formatting looks like this:
selector,
alternate-selector {
property: value;
other-property: other-value;
}

Also:
* Omit units on 0 values
** Example: Use <tt>margin: 0;</tt>, not <tt>margin: 0px;</tt>
* Add a space after each comma, '''except''' within color functions
** Example: <tt>-moz-linear-gradient(top, black 1px, rgba(255,255,255,0.2) 1px)</tt>
* Always add a space before <tt> !important</tt>
* Assume <tt>="true"</tt> in attribute selectors
** Example: Use <tt>option[checked]</tt>, not <tt>option[checked="true"]</tt>
* Use longhand versions of properties so it's clear what you're changing.
** Example: Use <tt>border-color: red</tt>, not <tt>border: red;</tt>

Naming Standards for class names:
* lower-case-with-dashes is the most common
* But camelCase is also used sometimes. It makes sense to first try to fit in with code around, and if there is doubt or if isn't anything to fit in with to use lower-case-with-dashes.

== Performance ==

* Read [https://developer.mozilla.org/en/CSS/Writing_Efficient_CSS Writing Efficient CSS]
* Use an iframe where possible so your rules are scoped to the smallest possible set of nodes
* If your CSS is used in browser.xul, you need to take special care of performance:
** Descendant selectors should be avoided
** If possible find ways to '''only''' use id selectors, class selectors and selector groups

== Content or Theme CSS ==

We have 2 competing priorities - A desire to avoid repetition (aka [https://en.wikipedia.org/wiki/Don%27t_repeat_yourself DRY]), and the desire to allow Firefox to look different depending on your platform or your theme preferences. As a result we split our CSS into rules that are likely to change between themes (aka theme CSS) and those that are not (aka content CSS).

There are stored:
* content CSS files are stored along with your JS/HTML/etc.
* theme CSS files are stored in the <tt>themes/(windows|osx|linux)</tt> directories
* theme CSS that should look the same on all supported platforms are stored in the <tt>themes/shared</tt> directory

Typically certain CSS properties are going to lean one way or the other: color - 99% of the time it will be theme CSS, overflow - 99% content.

<table style="font-size: 90%; border: 1px solid #999;">
<tr>
<th> 99% theme
<th> 70% theme
<th> 70% content
<th> 99% content
<tr>
<td> <tt>font-*, color, *-color, border-*, -moz-appearance [1]</tt>
<td> <tt>line-height, padding, margin</tt>
<td> <tt>cursor, width, max-width, top, bottom [2], etc</tt>
<td> <tt>overflow, direction, display, *-align, align-*, *-box-*, flex-*, order</tt>
</table>

If you're not sure, then go for content CSS unless you can imagine the value changing on another platform.

When importing your stylesheets, it's best to import the content CSS before the theme CSS, that way the theme values get to override the content values (which is probably what you want), and you're going to want them both after the global values, so your imports will look like this:

<?xml-stylesheet href="chrome://global/skin/global.css" type="text/css"?>
<?xml-stylesheet href="chrome://browser/content/path/module.css" type="text/css"?>
<?xml-stylesheet href="chrome://browser/skin/path/module.css" type="text/css"?>

[1] <tt>-moz-appearance</tt> is tricky. Generally, when specifying <tt>-moz-appearance: foo;</tt> you're giving hints as to how something should act, however <tt>-moz-appearance: none;</tt> is probably saying 'ignore browser preconceptions - I want a blank sheet', so that's more visual. However <tt>-moz-appearance</tt> values aren't implemented and don't behave consistently across platforms, so idealism aside <tt>-moz-appearance</tt> should always be in theme CSS.

[2] However there is probably a better way than using absolute positioning.

== Localization ==

Text Direction:
* For margins, padding and borders, use start/end rather than left/right
** Example: Use <tt>margin-inline-start: 3px;</tt> not <tt>margin-left: 3px</tt>
** Tip: whenever you specify an <tt>unbalanced</tt> margin, padding or border style (i.e. the value for left is different from the value for right), think of using -end/ -start
* When there is no special RTL-aware property (eg. float: left|right) available, use the pseudo :-moz-locale-dir(ltr|rtl)
* Remember that while a tab content's scrollbar still shows on the right in RTL, an overflow scrollbar will show on the left
* Write "padding: 0 3px 4px;" instead of "padding: 0 3px 4px 3px;". This makes it more obvious that the padding is symmetrical (so RTL won't be an issue)

Testing:
* Use the [https://addons.mozilla.org/en-US/firefox/addon/force-rtl/ Force RTL extension]
* Or go to about:config and set <tt>intl.uidirection.en</tt> to rtl

== Toggles ==

Sometimes you have a style that you want to turn on and off. For example a tree twisty, a tab background, etc. The Mozilla way is to perform the toggle using an attribute rather than a class. So:
.tree-node[opened] {
background-image: url(down-arrow.png);
}
.tree-node:not([opened]) {
background-image: url(right-arrow.png);
}

== The Mozilla Environment ==

Pre-defined classes:
* Use <tt>plain</tt> in place of <tt>margin: 0</tt>

Theme values:
* Use them where possible
** Example: <tt>border-radius: @toolbarbuttonCornerRadius@</tt>, not <tt>border-radius: 3px</tt>
* Where a theme value doesn't fit, make sure you have buy-in from UX

Lists of theme values:
* [https://developer.mozilla.org/en/CSS/color_value#Mozilla_System_Color_Extensions System Colors]
* [https://developer.mozilla.org/en/CSS/font#Mozilla_Extensions System Fonts]
* [https://developer.mozilla.org/en/CSS_Reference/Mozilla_Extensions CSS Extensions]

== Tips ==

* Use <tt>:empty</tt> to match a node that doesn't have children
* Usually, if <tt>margin</tt> or <tt>padding</tt> has 4 values, something is wrong. If the left and right values are asymmetrical, you're supposed to use <tt>-start</tt> and <tt>-end</tt>. If the values are symmetrical, so use only 3 values (see localization section)

TestEngineering/Performance/Talos/Profiling

2018-05-25T12:34:59Z

P.A.: It seems that this page was copied without removing the original. Based on recent history, the original page is now the most up-to-date.

#REDIRECT [[Buildbot/Talos/Profiling]]

MOSS/Foundational Technology/Projects We Use

2017-02-09T14:02:13Z

P.A.: Add Eclipse

This is an incomplete list of the free software and open source projects Mozilla relies upon. As a starting point, it lists each project along with a short statement of how we depend on it. Where practical it would also be helpful to identify a Mozillian most closely associated with our use of each project.

Note that presence on this list isn't the same as, nor is it a prerequisite for, applying for the MOSS "Foundational Technology" track - projects have to make an application using the process on the [[MOSS/Foundational Technology|Foundational Technology]] page.

This is a work in progress - please contribute to this list.

{| class="wikitable"
|-
! Project !! Description !! Contact within Mozilla
|-
| [https://angularjs.org/ angular.js] || Used by A-Team for web apps (eg Treeherder) || Member of Jonathan Griffin's team
|-
| [https://httpd.apache.org Apache Server] || Used by A-Team for web apps || Member of Jonathan Griffin's team
|-
| [https://github.com/ansible/ansible Ansible] || Used by IT (netops) and A-Team to manage deployments || jbarnell , GPS?
|-
| [https://github.com/h4writer/arewefastyet AreWeFastYet] || Compare JS performance across JS engines and platforms || Hannes Verschore
|-
| [https://babeljs.io/ BabelJS] || JavaScript compiler, Used by Gaia, TaskCluster team || Selena Deckelmann
|-
| [https://pypi.python.org/pypi/blessings/ Blessings] || Terminal formatting lib used by mozilla-central build process || Erik Rose
|-
| [http://getbootstrap.com/ Bootstrap] || HTML/CSS/JS framework, used by many of Mozilla's sites. || Webdev
|-
| [http://brew.sh/ brew / Homebrew] || Mac OS X packaging system, used to install dev tools || Sam Penrose
|-
| [https://bro.org bro] || The Bro Network Security Monitor || Michal Purzynski
|-
| [http://browserify.org Browserify] || Build JS dependencies for the browser || mozilla-services (kinto.js)
|-
| [http://buildbot.net/ BuildBot] || The base system currently in use for release || Dustin J. Mitchell
|-
| [http://bugzilla.org/ Bugzilla] (upstream) || The base Bugzilla on that we customize for Mozilla's use || Mark Côté
|-
| [http://www.celeryproject.org/ Celery] || Distributed task queue. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| [http://ckeditor.com/ CKEditor] || WYSIWYG editor on MDN ||
|-
| [http://chaijs.com/ Chai] || JavaScript test and assertion library || Cloud Services, Tarek Ziade's team (kinto.js), Firefox Hello team
|-
| [http://www.llvm.org Clang/LLVM] || C/C++ compiler and infrastructure || Ehsan Akhgari & Sylvestre Ledru
|-
| [https://codemirror.net/ CodeMirror] || Used in DevTools, [https://thimble.mozilla.org Thimble], and other online code tools || David Humphrey/Simon Wex
|-
| [https://pypi.python.org/pypi/cookiecutter/ Cookiecutter] || Templating system used to clone our [https://github.com/mozilla/sugardough Sugardough] Django template || Giorgos Logiotatidis
|-
| [https://conemu.github.io/ ConEmu] || Console emulator for Windows. Used by devs running Windows. || Ed Morley
|-
| [http://curl.haxx.se/ curl] || internet transfer tool and library, used by crashreporter and FirefoxOS || Daniel Stenberg
|-
| [https://www.debian.org/ Debian] || Used on many developer boxes || Sylvestre Ledru or glandium
|-
| [http://deis.io Deis] || Open Source Heroku-like PaaS platform. Hosts www.mozilla.org, masterfirefoxos.mozilla.org, etc. || Member of Benjamin Sternthal's team
|-
| [https://disconnect.me/trackerprotection Disconnect.me ] || Open, transparent, neutral Tracking Protection blocklist used in Firefox Private Browsing Windows || Marshall Erwin, Javaun Moradi, Francois Marier
|-
| [https://discourse.org Discourse] || [https://discourse.mozilla-community.org Community], [https://discourse.webmaker.org/ Webmaker], [https://discourse.mozilla-advocacy.org/ Advocacy], et al || [[IT/Community/WG/Discourse|Community Ops]] (Yousef Alam or Tanner Filip)
|-
| [https://djangoproject.com Django] || Backend web framework used on many of our websites, including addons.mozilla.org, marketplace.mozilla.org, support.mozilla.org, Input, Snippets, MDN (Mozilla Developer Network), mozilla.org, Treeherder || Andy McKay and Jannis Leidel are (or have been) on the [https://www.djangoproject.com/foundation/ Django Software Foundation] board, Jannis is core team member
|-
| [http://www.django-rest-framework.org Django REST framework] || API framework. Used by various Mozilla sites including MDN, Firefox marketplace, mozilla.org, support.mozilla.com. || Andy McKay and Jannis Leidel
|-
| [https://github.com/docker/docker Docker] || Used by release engineering for Linux build and test containers and by ateam for managing test and production services. Used by many Mozilla websites as well such as addons.mozilla.org, marketplace.mozilla.org. (Plus docker-compose and docker machine) || Member of Selena Deckelmann's team
|-
| [https://eclipse.org/ Eclipse] || Integrated Development Environment used by many developers || —
|-
| [https://www.elastic.co/products/elasticsearch elasticsearch] || Search engine for various web sites and analytics || Erik Rose
|-
| [http://www.gnu.org/software/emacs/ emacs] || Programmable editor used by many developers || —
|-
| [http://eslint.org/ eslint] || Pluggable linting utiltity used by Firefox Hello, DevTools and Firefox Android || Mark Banner
|-
| [https://github.com/ether/etherpad-lite Etherpad] || Used for meeting notes, etc || JP Schneider
|-
| [https://flake8.readthedocs.org/ flake8] || Wrapper around Python linters. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| [http://flask.pocoo.org/ Flask] || Python web framework || Erik Rose
|-
| [https://fortawesome.github.io/Font-Awesome/ Font Awesome] || Font and CSS toolkit, used by many of Mozilla's sites. || Webdev
|-
| [http://gcc.gnu.org GCC] || C/C++ compiler and infrastructure || Nathan Froyd
|-
| [https://git-scm.com/ Git] || Version control system - https://git.mozilla.org || Unknown
|-
| [http://gunicorn.org/ gunicorn] || Python WSGI HTTP Server. Used by Treeherder, Socorro, Pontoon. || Webdev
|-
| [http://www.freedesktop.org/wiki/Software/HarfBuzz/ HarfBuzz] || International text shaping engine used in Firefox/Servo || Platform team
|-
| [http://hunspell.sourceforge.net/ Hunspell] || Spellchecking engine || Ehsan Akhgari
|-
| [https://github.com/hunspell/hyphen/ Hyphen] || Hyphenation library || Jonathan Kew
|-
| [https://github.com/jkbrzt/httpie HTTPie] || HTTP command-line client || Cloud Services (among many others), Tarek Ziade's team
|-
| [https://theintern.github.io/intern/ Intern] || Intern is a complete test system for JavaScript designed to help you write and run consistent, high-quality test cases for your JavaScript libraries and applications. || jrgm/vladikoff
|-
| [http://canonware.com/jemalloc/ jemalloc] || Memory allocation library || We can ask glandium
|-
| [http://jenkins-ci.org/ Jenkins CI] || Continuous integration system used by WebQA and EE || Unknown
|-
| [https://jquery.com/ jQuery] || JavaScript library, used by many of Mozilla's sites. || Webdev
|-
| [https://github.com/tmpvar/jsdom jsdom] || DOM implementation in full JS || Test suites in Cloud Services, Tarek Ziade's team (kinto.js)
|-
| [https://github.com/open-source-parsers/jsoncpp jsoncpp] || A C++ library for interacting with JSON, used by the crashreporter client and Socorro. || Gabriele Svelto
|-
| [http://kombu.readthedocs.org/ Kombu] || Messaging library for Python. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| libjpeg-turbo || JPEG decoding library || Jeff Muizelaar
|-
| [http://www.libpng.org/pub/png/libpng.html libpng] || PNG decoding library || Jeff Muizelaar
|-
| libvpx (Google) || Library for support of Google’s VP* family of codecs || Tim Terriberry
|-
| Linux || OS kernel used in Firefox OS || Unknown
|-
| [https://lodash.com/ lodash] || JavaScript utility library, used by many of Mozilla's sites. || Webdev & Firefox Hello
|-
| [https://www.list.org/ Mailman] || [https://mail.mozilla.org/listinfo Mailing lists] || Unknown
|-
| [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] || You are reading this on a wiki || Sheeri Cabral
|-
| [https://www.mercurial-scm.org/ Mercurial] || Version control system and source code management || GPS
|-
| [http://mochajs.org/ Mocha] || JavaScript test runner || Cloud Services, Tarek Ziade's team (kinto.js); Firefox Hello team
|-
| [https://github.com/kumar303/mohawk Mohawk] || Python library for Hawk HTTP authorization. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| [http://mozdef.com mozdef] || Security event monitoring and incident response || Jeff Bryner
|-
| [http://www.mingw.org/wiki/msys msys] || Used to build Firefox on Windows. Note: It's likely best we support the newer MSYS2 project instead: https://github.com/msys2 || Unknown
|-
| [https://www.mysql.com/ MySQL] || Open source relational DB used by many developers, including AMO, SUMO, Input, bugzilla, releng, adminstered by IT || Sheeri Cabral
|-
| [https://www.nagios.org/ Nagios] || IT management system. Used for notifications of system failures || Sheeri Cabral, Ashish V.
|-
| [http://netsniff-ng.org/ netsniff-ng] || Linux networking toolkit || Michal Purzynski
|-
| nICEr || Library for traversing firewalls || Unknown
|-
| [https://nixos.org NixOS] || Reproducible Linux distribution. Used by some developers || Nicolas B. Pierron
|-
| [https://nodejs.org Node.js] || JavaScript runtime for server side applications, command line utilities || Nick Desaulniers
|-
| nrappkit || Toolkit for building standalone applications || Unknown
|-
| OpenH264 (Cisco) || H.264 video library || Unknown
|-
| [http://openresty.org OpenResty] || a fast web app server by extending nginx, used by cloudops || Benson Wong (mostlygeek)
|-
| [http://www.openssh.com/ OpenSSH] || Remote server management, secure transport for Git and Mercurial || Unknown
|-
| [https://www.openstreetmap.org OpenStreetMap] || Online/offline maps, used by the location service and on mozilla.org || Unknown
|-
| [http://www.openLDAP.org/ OpenLDAP] || User management used by Infra || :jabba?
|-
| [https://openvpn.net/ Openvpn] || VPN used by Infra || :jabba?
|-
| [http://www.inspircd.org/ inspircd] || Irc server used by mozilla || Unknown
|-
| [http://openssl.org/ OpenSSL] || Cryptograpahy and TLS Toolkit || Nick Desaulniers
|-
| [https://github.com/khaledhosny/ots OTS] || OpenType sanitizer used by Firefox to protect against security bugs in underlying platforms related to malicious fonts || Jonathan Kew
|-
| [https://www.owasp.org/index.php/ZAP OWASP ZAP] || Web security testing tool used by security and QA teams || Simon Bennetts (psiinon)
|-
| [https://owncloud.org/ Owncloud] || Open platform to host your cloud under your control || Some communities have been using it to host files under their control (ask Nukeador)
|-
| [https://pypi.python.org/pypi/parsimonious/ Parsimonious] || Parsing lib used by DXR and a few other sites (I think) || Erik Rose
|-
| [https://github.com/mozilla/pdf.js PDF.js] || Used as the PDF Viewer in Firefox and Firefox OS || Brendan Dahl, Yury Delendik
|-
| [https://github.com/PyCQA/pep8 pep8] || Python linter. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| [https://www.perl.org/ Perl] || Used by Bugzilla || Member of Jonathan Griffin's team
|-
| [https://github.com/pypa/pip pip] || Python package tool. Used by all Python projects. || Erik Rose and Jannis Leidel, Jannis is core team member ([https://www.pypa.io/ PyPA])
|-
| [http://piwik.org/ Piwik] || Analytic software that gives you the control and respects privacy || Some communities have been using it to avoid GA analytics (Ask Nukeador)
|-
| [http://cmusphinx.sourceforge.net/ Pocketsphinx] || Speech recognition toolkit embedded into Firefox OS|| André Natal
|-
| [http://www.postgresql.org/ PostgreSQL] || Open source relational DB used by many developers, adminstered by IT || Selena Deckelmann
|-
| [https://github.com/PrismJS/prism Prism.js] || Syntax highlighting on code samples on MDN ||
|-
| [https://github.com/puppetlabs/puppet Puppet] || System administration tool || Member of Amy Rich's team
|-
| [https://github.com/pyflakes/pyflakes pyflakes] || Python linter. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| [http://pypy.org/ PyPy] || Python language runtime. Used by Web Push service. || Cloud Services, esp. Ben Bangert
|-
| [https://github.com/Pylons/pyramid/ Pyramid] || Python Web framework || Cloud Services team
|-
| [http://pytest.org/ pytest] || Python testing tool. Used by Treeherder and others. || Member of Jonathan Griffin's team
|-
| Python || Scripting language || [http://python.org/psf/ Python Software Foundation], Selena Deckelmann is a former board member
|-
| [https://pypi.python.org/pypi/pyelasticsearch/ pyelasticsearch] || Python client for elasticsearch || Erik Rose
|-
| [https://www.rabbitmq.com/ RabbitMQ] || Distributed Queue, used by Socorro, Pulse (all our publicly available build/test/commit information flows through this), Treeherder, addons.mozilla.org (with Celery), marketplace.mozilla.org (with Celery) || Selena Deckelmann
|-
| [http://facebook.github.io/react/index.html ReactJS] || Javascript library for building user interfaces. Used by Firefox Hello & DevTools || Mark Banner
|-
| [https://readthedocs.org/ Read the Docs] || Hosted automatically-built documentation, used by Cloud Services and a wide variety of mozilla Github projects || Ben Bangert, Jannis Leidel, Gervase Markham
|-
| [http://redis.io/ Redis] || Really fast data structure store, cache and message broker || Cloud Services Tarek Ziade's team, Loop Server (Hello) team
|-
| [http://python-requests.org/ Requests] || "Python HTTP Requests for Humans". Used by many many Mozilla Python projects. || Member of Jonathan Griffin's team
|-
| [https://www.reviewboard.org/ Review Board] || The base of MozReview, the new review tool being developed to replace Splinter || Steven MacLeod, Mike Conley
|-
| [http://wordlist.aspell.net/ SCOWL] || en-US word list used for spell checking. || ehsan
|-
| [http://www.seleniumhq.org/ Selenium] || Browser test driver || stephend/AutomatedTester or jrgm/vladikoff
|-
| [http://sinonjs.org/ Sinon] || JavaScript mock library || Cloud Services, Tarek Ziade's team (kinto.js); Firefox Hello team
|-
| [https://slimerjs.org/ SlimerJS] || Scriptable browser, based on Gecko, used for functional tests in some few Mozilla projects ( [[PluotSorbet]], some FxOS apps ? and others ?) || Myk Melez
|-
| [http://www.sqlalchemy.org/ SQLAlchemy]] || Database Toolkit and ORM for Python || bhearsum
|-
| [https://www.sqlite.org/ SQLite] || File-based database || khuey
|-
| [http://learnboost.github.io/stylus/ Stylus] || CSS Pre-processor on several sites || webdev
|-
| [https://subversion.apache.org/ Subversion] || https://svn.mozilla.org ''(Planning to decommission in near future)'' || Unknown
|-
| [http://http://suricata-ids.org/ suricata] || IDS / IPS / NSM engine || Michal Purzynski
|-
| [https://tox.readthedocs.org/en/latest/ Tox] || Test automation || Tarek Ziade's Team
|-
| [https://travis-ci.org/ Travis] || Continuous integration system used by several teams (eg Treeherder) || Jonathan Griffin's team
|-
| [https://github.com/mitchellh/vagrant Vagrant]|| Build and distribute dev envs, used by Treeherder and others || Member of Jonathan Griffin's team
|-
| [http://valgrind.org/ Valgrind] || Memory error detection and profiling of C and C++ code || jseward, njn
|-
| [http://vim.org/ vim] || editor used by many developers || —
|-
| [https://github.com/w3c/web-platform-tests web-platform-tests] || Testcases and tooling for cross-browser testing of web-platform APIs || jgraham
|-
| [http://www.webrtc.org WebRTC.org] || Components to support real-time communication in browsers and mobile applications || Randell Jesup
|-
| [http://www.wordpress.org WordPress] || Powers our blogs, blog.mozilla.org || Craig Cook
|-
| [https://xiph.org Xiph.Org] || Media codecs ship in Firefox, encoding tools || Ralph Giles
|-
| [http://zlib.net zlib] || Streaming compression and decompression for HTTP, PNG, etc. ||

|}

Electrolysis

2017-01-29T11:18:16Z

P.A.: Use the correct case for the multiprocessCompatible flag.

== Overview ==

Electrolysis functionality hosts, renders, or executes web related content in background [https://en.wikipedia.org/wiki/Child_process child processes] which communicate with the "parent" Firefox browser via various [https://developer.mozilla.org/en-US/docs/IPDL ipdl protocols]. The two major advantages of this model are security and performance. Security improvements are accomplished through security sandboxing, performance improvements are born out of the fact that multiple processes better leverage available client computing power.

Electrolysis child processes are currently in use for the following tasks within Firefox:

* Legacy NPAPI plugin hosting
* Media playback
* Web content ('content processes')

In the future Electrolysis child processes may be used to handle other browser tasks including graphical composition, and addon hosting for addons that leverage the new [[WebExtensions]] apis.

In Mozilla documentation "Electrolysis" is often shorted as "e10s".

== Testing ==

=== Nightly/Aurora ===

If you're on Nightly or Aurora, e10s is already enabled by default! A user-facing checkbox is available for controlling Electrolysis functionality. Open Preferences and check the "Enable multi-process" checkbox and then restart your browser:

[[File:E10s-toggle-in-preferences.png|324x150px|frameless|Nightly > Preferences > General > Enable multi-process]]

=== Firefox Beta ===

If you're currently using Firefox Beta you might be testing e10s already, check ''about:support'' and look for a number higher than 0 in the "Multiprocess Windows" entry. If you would like to opt-in to help us test open ''about:config'' and toggle '''browser.tabs.remote.autostart''' to true. On your next restart, e10s should be active.

=== Firefox Release ===

If you're using Firefox 48 or later, you might be using e10s already. Check about:support and look for a number higher than 0 in the "Multiprocess Windows" entry. If you would like to opt-in, open about:config and toggle browser.tabs.remote.autostart to true. On your next restart, e10s should be active.

=== Force Enable ===

If you've tried enabling e10s following the instruction above, but your ''about:support'' indicates that e10s is disabled (e.g., accessibility, add-ons can trigger this), you can force e10s on for testing purposes. Within ''about:config'' create a new boolean pref named '''browser.tabs.remote.force-enable''' and set it to true. This is not encouraged, use it at your own risk!

== Schedule and Status ==

A single content process model is currently being tested on Nightly, Aurora and Beta channels. See the schedule below for planned rollout to release. A multiple content process model (e10s-multi) will roll out in a follow up release. View the [https://wiki.mozilla.org/Electrolysis/Multiple_content_processes Multiple Content Process] wiki page for more information.

=== Schedule ===

The following schedule covers rollout of the single content process feature to release builds.

{| class="wikitable"
|-
! Date !! Trunk !! Aurora !! Beta !! Release !! Target % !! Actual %
|-
| 2015-04-30 || 40 default (working on m5) || 39 off || 38 off || 37 off || - || -
|-
| 2015-05-11 || 41 default (working on m6) || 40 prompt || 39 off || 38 off || - ||-
|-
| 2015-06-29 || 42 default (working on m7/m8) || 41 prompt|| 40 off || 39 off || - || -
|-
| 2015-08-10 || 43 default (working on m8) || 42 default || 41 off || 40 off || - || -
|-
| 2015-09-21 || 44 default || 43 default || 42 off || 41 off || - || -
|-
| 2015-11-02 || 45 default || 44 default || 43 off || 42 off || - || -
|-
| 2015-12-14 || 46 default || 45 default || 44 A/B [1] || 43 off || - || -
|-
| 2016-01-25 || 47 default || 46 default || 45 A/B [1] || 44 off|| - || -
|-
| 2016-03-07 || 48 default || 47 default || 46 A/B [1] || 45 off|| - || -
|-
| 2016-04-25 || 49 default || 48 default || 47 50% [1][2] || 46 off|| - || -
|-
| 2016-06-06 || 50 default || 49 default || 48 [1][2] || 47 off|| -||-
|-
| 2016-08-01 || 51 default[6] || 50 default || 49 [2][4]|| 48 ON [3] || 41% || 30-33%
|-
| 2016-09-19 || 52 default [7][8] || 51 default[6] || 50 default [4] || 49 ON [5] || + 3-4% || 35%
|-
|2016-11-07 || 53 default [8] || 52 default [7]|| 51 default [6] || 50 ON [5]|| + 6-12%||
|-
|2017-01-24 || 54 default || 53 default [8] || 52 default [7] || 51 ON [*]|| * ||
|-
|2017-03-07 || 55 default || 54 default || 53 default || 52 ON [*]|| *||
|-
|2017-04-18 || 56 default || 55 default || 54 default || 53 ON [*] || * ||
|}

[1] qualifying users: users that do not use addons and have not activated accessibility support over 30 days. 
[2] full run across the entire beta period 
[3] 1% of qualifying users with ramp up to 100% during the release cycle 
[4] White listed Add-Ons + Add-Ons created as a WebExtension testing on beta, full cycle 
[5] White listed Add-Ons + Add-Ons created as a WebExtension shipping on Release 
[6] A11y+ Windows 8 touch screen support enabled, not riding trains 
[7] A11y + Windows 8 riding trains 
[8] E10s Multi Enabled, Not riding trains 
[*] indicates the goal for the release has yet to be planned

=== Add-ons Schedule ===

The following schedule rollout of Electrolysis as it releases specifically to add-ons. Each release of Firefox will add more and more add-ons to the cohort of users who get multi process Firefox.

Users with add-ons not in yet the cohort to get multi-process, will continue to run Firefox (as before) without e10s enabled.

{| class="wikitable"
|-
! Version !! Cohort
|-
| 49 || limited experimental set of Extensions and all WebExtensions
|-
| 50 || all Extensions marked "multiprocessCompatible" and all WebExtensions [1]
|-
| 51 || all Extensions and all WebExtensions [1], [2], [3]
|-
| 52 || as in 51 [2], [3]
|-
| 53 || as in 52 [2], [3]
|}

[1] Before each stage moves from beta to release, there are release criteria (crashes, jank etc) that need to be met. We will delay moving to Release if issues are identified in Beta.

[2] Initially [https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Multiprocess_Firefox_and_the_SDK#Testing_your_add-on Shims] will be available that will help certain add-ons with compatibility. These are a temporary measure due to potential [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox/Cross_Process_Object_Wrappers#Limitations_of_CPOWs limitations] that could impact user experience.

[3] With the exception of Extensions marked explicitly as NOT multiprocessCompatible.

For information on add-on support rollout see the [https://wiki.mozilla.org/Add-ons Add-on Project Wiki].

===Staged Roll-Out Plan===
To read a summary of the Roll-Out plan, see [https://asadotzler.com/ Asa's blog].

=== Windows XP ===
Due to [https://wiki.mozilla.org/Electrolysis/XP stability issues] Windows XP is currently not leveraging e10s on release channel. XP and Vista will move out to Extended Support Release (ESR) 45 when 45 merges to release ({{bug|1303827}}). As such there are no plans to support e10s for XP/Vista in the future.

=== Weekly Status Reports ===
==2015==
* [https://wiki.mozilla.org/E10s/Status/Nov13 Nov 13] 
* [https://wiki.mozilla.org/E10s/Status/Nov20 Nov 20] 
* [https://wiki.mozilla.org/E10s/Status/Nov27 Nov 27] 
* [https://wiki.mozilla.org/E10s/Status/Dec4 Dec 4] 
* [https://wiki.mozilla.org/E10s/Status/Dec22 Dec 22] 
==2016==
* [https://wiki.mozilla.org/E10s/Status/Jan15 Jan 15] 
* [https://wiki.mozilla.org/E10s/Status/Jan29 Jan 29] 
* [https://wiki.mozilla.org/E10s/Status/Feb12 Feb 12] 
* [https://wiki.mozilla.org/E10s/Status/March29 March 29] 
* [https://wiki.mozilla.org/E10s/Status/April8 April 8] 
* [https://wiki.mozilla.org/E10s/Status/April22 April 22] 
* [https://wiki.mozilla.org/E10s/Status/May5 May 6] 
* [https://wiki.mozilla.org/E10s/Status/May20 May 20] 
* [https://wiki.mozilla.org/E10s/Status/July1 July 1] 
* [https://wiki.mozilla.org/E10s/Status/July8 July 8] 
* [https://wiki.mozilla.org/E10s/Status/July22 July 22] 
* [https://wiki.mozilla.org/E10s/Status/July22 July 29] 
* [https://wiki.mozilla.org/E10s/Status/Aug05 Aug 05] 
* [https://wiki.mozilla.org/E10s/Status/Aug12 Aug 12] 
* [https://wiki.mozilla.org/E10s/Status/Aug26 Aug 26] 
* [https://wiki.mozilla.org/E10s/Status/Sept2 Sept 2] 
* [https://wiki.mozilla.org/E10s/Status/Sept9 Sept 9] 
* [https://wiki.mozilla.org/E10s/Status/Sept23 Sept 23] 
* [https://wiki.mozilla.org/E10s/Status/Oct 3 Oct 3] 
* [https://wiki.mozilla.org/E10s/Status/Oct11 Oct 11] 
* [https://wiki.mozilla.org/E10s/Status/Oct24 Oct 24] 
* [https://wiki.mozilla.org/E10s/Status/Nov3 Nov 3] 
* [https://wiki.mozilla.org/E10s/Status/Dec1 Dec 1] 
* [https://wiki.mozilla.org/E10s/Status/Dec23 Dec 23] 

==2017==

== Experiments ==
There's a dedicated page for the experiments: [[Electrolysis/Experiments|E10s Experiments]]

== Contributing ==

The simplest way to help out is to test a release that has e10s enabled, and file bug when you find them. Please try to find duplicates prior to filing.

For developers interested in helping out, MDN has a [https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox good introduction to e10s], useful for both Firefox and add-on developers.

== Security Sandboxing ==

See the [https://wiki.mozilla.org/Security/Sandbox Security Sandbox] wiki page for more information and status.

== Accessibility Support ==
See the [https://wiki.mozilla.org/Electrolysis/Accessibility e10s Accessibility] wiki page for support implementation detail.

== Add-ons Compatibility ==

Add-on authors should refer to the MDN [https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox Firefox Add-on Migration Guide] for porting existing add-ons to e10s. For general design information see the [https://developer.mozilla.org/en-US/Firefox/Multiprocess_Firefox Multiprocess Firefox] MDN documentation. Add-on testing compatibility is currently available at http://arewee10syet.com.

For more information about Add-on issue mitigation and rollout of e10s to add-on users, see the [https://wiki.mozilla.org/Add-ons Add-on Project Wiki] page.

== Past Milestones ==

* 2014-09-11 - {{bug|1064885}} - Enable opt-in option for Nightly
* 2014-11-13 - {{bug|1093691}} - Enabled for Nightly builds
* 2015-05-08 - {{bug|1161260}} - Enable opt-in option for Aurora
* 2015-07-28 - {{bug|1182097}} - Disabled on Aurora for about 1 week due to a bug in a11y prompting
* 2015-07-31 - {{bug|1188605}} - Enabled for Aurora builds
* 2015-12-15 - {{bug|1229104}} - Beta testing
* 2016-08-01 - Enabled for non-add-on users in Release 48 / Beta testing of add-on users in 49

== Communication ==

{| class="wikitable fullwidth-table"
| Weekly Cross Functional Covering current e10s status, multi-e10s, add-ons rollout, and sandboxing.
|| Fridays @ 10am Pacific
* Vidyo: [https://v.mozilla.com/flex.html?roomdirect.html&key=njJM9NHQBt2a "e10s"]
* Invitation: Contact Erin Lancaster (:elan) for an invite.
* [https://docs.google.com/document/d/1MS8ol0vJPQ2eNnbZTr6lQABxRBt5KtvuTAfwlMihMls/edit Meeting Notes]
|-
| Weekly Team Meeting (No longer active)
|| [http://arewemeetingyet.com/Los_Angeles/2014-04-24/09:00/w/E10s Weekly Team Meeting Thursday at 9:00am PT]
* Vidyo: [https://v.mozilla.com/flex.html?roomdirect.html&key=njJM9NHQBt2a "e10s"]
* Invitation: Contact blassey, jimm, or larissa to get added to the meeting invite list.
* [https://wiki.mozilla.org/Electrolysis/Meetings Meeting Notes]
|-
| Weekly Addons Design Meeting (No longer active)
||
* Vidyo: [https://v.mozilla.com/flex.html?roomdirect.html&key=njJM9NHQBt2a "e10s"]
* Invitation: Contact billm to get added to the meeting invite list.
* [https://e10s.etherpad.mozilla.org/addons-notes Meeting Notes Etherpad]
|-
| IRC
||
* Server: irc.mozilla.org
* Channel: [irc://irc.mozilla.org/e10s #e10s]
|-
| Newsgroup/Mailing List
||
* https://lists.mozilla.org/listinfo/dev-tech-electrolysis
|-
|}

==People==
{| class="wikitable fullwidth-table"
| Engineering Management
||
* Brad Lassey
|-
|Product Management
||
*Jeff Griffiths
|-
| Project Management
||
* Erin Lancaster - e10s Go to Market
* Shell Escalante - Add-Ons
|-
| QA
||
* Tracy Walker (e10s Quality Assurance Lead)
|-
| Development Team
||
* Mike Conley
* Felipe Gomes
* Blake Kaplan
* Gabor Krizsanits
* William McCloskey
* Jim Mathies
* Tom Schuster
* Dave Townsend
* George Wright
|}

== Meeting Notes ==

[https://wiki.mozilla.org/Electrolysis/Meetings Link]

== Reference ==

* [https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox MDN: Working with multiprocess Firefox]
* [https://developer.mozilla.org/en-US/docs/The_message_manager The message manager]
* [https://developer.mozilla.org/en-US/docs/Cross_Process_Object_Wrappers Cross-process object wrappers]
* [[Electrolysis/Archive | Archive of past content on this page]]
* [https://etherpad.mozilla.org/uYS8ZplOMU Electrolysis platform notes]
* [https://etherpad.mozilla.org/rRk4aEHkwC Notes on the Chromium IPC library]
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AhFRRYurPzRndHQwUVNscThIbFBsYmNRaU44LVlDdlE#gid=0 Addon Compatibility Test Results]
* [http://mxr.mozilla.org/mozilla-central/source/dom/base/nsIMessageManager.idl#15 IDL comments about Message Manager]
* Tim Taubert's [http://timtaubert.de/blog/2011/08/firefox-electrolysis-101/ "Firefox Electrolysis 101"] blog post (2011)
* [[Electrolysis/e10s test tips|Tips for converting tests to be e10s compatible]]
* [[Electrolysis/Performance_Optimization|Performance optimization tips]]
* [https://www.mozilla.org/firefox/channel/ Download Beta, Developer, or Release]
* [https://nightly.mozilla.org/ Download Nightly]

== Bug Lists ==
=== Nightly enable blockers ===
* M2 bugs: http://tinyurl.com/mjywvmb (one leftover bug, assigned m5+, 1047603)
* M3 bugs: http://tinyurl.com/n7jekh6 (all resolved + dependencies resolved)
=== Aurora uplift blockers (plus dev. tools) ===
* M4 bugs: http://is.gd/fi3ByM
* M5 bugs: http://is.gd/hNTLWk
* M6 bugs: http://is.gd/1Dw8gN
* M4–M6 bugs: http://is.gd/drPSBc
=== Beta blockers ===
* M7 bugs: http://is.gd/HQGwVi
* M8 bugs: http://is.gd/Au5e7x
=== GA Blockers ===
* M9 Actionable Bugs: http://is.gd/qufPe0
* M9 plus RC Meta Bugs: http://is.gd/tv81Zf
* M9 RC Metas: http://is.gd/hTHo9U
* RC Meta Children: http://is.gd/eKcXxH
=== Summary Lists ===
* M7–M8 bugs: http://is.gd/YPXLZT
* M4–M8 bugs: http://is.gd/16YH4l
=== Devtools Lists ===
* e10s-m7 and e10s-m8 bugs: http://is.gd/zrzaRw
* e10s-m4 through e10s-m8 bugs: http://is.gd/Ra53os
=== Performance bugs (e10s-perf) ===
* Complete e10s-perf List: http://is.gd/izIbfl
* P1: http://is.gd/N4Kska
* P2: http://is.gd/tricyk
=== Future ===
* tracking-e10s:+ P1: http://is.gd/ztBxgX (no tests or sdk bugs)
* tracking-e10s:+ P1: http://is.gd/syKhQ8 (everything)
* tracking-e10s:+ P2: http://is.gd/NnCvUQ
* tracking-e10s:+ P3: http://is.gd/PD3PI8
* tracking-e10s:+ P4: http://is.gd/K6dCIq
* tracking-e10s:later: http://is.gd/B1cfnm
=== Triage Lists ===
* e10s Triage List: https://is.gd/S0iUXW
* e10s-perf Triage List: http://is.gd/5R5Leo
* e10s needinfo Triage List: http://is.gd/MoraEb
* tracking-e10s:? specific needinfo List: http://is.gd/vsPqdk
* Add-on triage List: http://is.gd/P2aqLC
* tracking-e10s:+ List: http://is.gd/ybrg68
** minus needinfos
** minus Summary containing 'intermittent', 'test', 'addon', 'add-on'
** minus Keywords containing 'meta', 'qawanted'
** minus bugs with a priority set
** not blocking {{bug|apz-desktop}}, {{bug|e10s-tests}}, {{bug|e10s-perf}}, {{bug|e10s-addons}}, {{bug|e10s-gfx}}, {{bug|e10s-sdk}}, {{bug|e10sa11y2}}, {{bug|e10s-ime}}, {{bug|dte10s}}, {{bug|e10s-social}}, {{bug|e10s-multi}}, {{bug|e10s-harness}}
* tracking-e10s:+ needinfos List: http://is.gd/YADITg
* RTL Blockers: http://is.gd/cKUiNa

=== Misc. Trackers ===
* Accessibility tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1029143
* Devtools bug tracking: https://etherpad.mozilla.org/devtools-e10s-statuses
=== '''Uplift candidates''': (M9 and P1 tracking+ bugs fixed in FF 48 but not 47) ===
* https://wiki.mozilla.org/E10s/Status/m9

Community:SummerOfCode15

2015-12-16T11:08:42Z

P.A.: /* Firefox */ Not mentoring the Download Integrity project right now

This page lists all the [[SummerOfCode|Google Summer of Code]] 2015 projects with confirmed mentors, and which have been approved by the SoC administrator. New suggestions can be made on [[Community:SummerOfCode15:Brainstorming|the Brainstorming page]]. Do not edit this page yourself; contact Florian for edits.

'''Potential students''': you may choose from the list below, '''but you do not have to'''. Feel free to submit a proposal for your own idea. However, before you do so, see the [[Community:SummerOfCode15:Brainstorming|guidelines for good ideas]]. You can also discuss your ideas or application in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction . Your idea will have a significantly greater chance of being chosen if you can find an existing member of the Mozilla community who is willing to evaluate or mentor it. (You should name that person in your application.)

In addition to the specifically-named projects below, we have also tagged a number of bugs in Bugzilla with the keyword [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=student-project&resolution=--- student-project]. However, as the idea of a "student project" is wider than just the Summer of Code, students looking through the list will need to decide whether any particular bug listed there is actually the right size and scope for Summer of Code.

==Application Advice==

You should do the following:

* Talk to the mentor. Contact details are on this page; if all you have is a nickname, get on [[IRC|IRC]] and try and contact them.
* Read the [https://flossmanuals.net/GSoCStudentGuide/ GSoC Student Guide] and follow its advice.
* Read [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not To Apply For Summer Of Code] and avoid doing the things listed there.
* Read our examples of good applications: [[SummerOfCode/SampleApplications/1|1]], [[SummerOfCode/SampleApplications/2|2]], [[SummerOfCode/SampleApplications/3|3]].
* Apply on [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 the GSoC site] (note that we have an [[SummerOfCode/ApplicationTemplate|application template]]).
* It is entirely acceptable to apply for 2 or 3 projects, if more than one catches your eye; if the applications are high quality, that can improve your chances. However, more than 3 seems like spam.

Note that if a project suggests it would be helpful to know XUL (Mozilla's user interface description language), you may be able to get away with learning on the job. Don't be put off from applying if the project otherwise looks right for you.

Questions about individual projects are best addressed to the potential mentor of that project. These should be listed in the table below. If you want to contact a mentor and contact details are not here, ask people in the #introduction channel on IRC: irc://irc.mozilla.org/#introduction. If you have questions of any other sort, send mail to [mailto:florian@queze.net,clokep@gmail.com Florian and Patrick]. We will try and respond as soon as possible and get your questions directed to the right person. Please allow at least 48 hours for a reply.

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Download Integrity
| Enhance detection of broken downloads in Firefox. Methods may include:<ul><li>[http://www.w3.org/TR/SRI/#the-a-element-1 Subresource Integrity for the <a> element]<li>[[Features/HTTP_Digest_header_verification#Stage_1:_Definition|HTTP Digest header verification]]<li>Network-level indications like bad HTTP framing</ul>The activities include:<ul><li>Implement the front-end in JavaScript to display failed integrity checks<li>Implement and/or use the required back-end features in C++<li>Work with the Mozilla community to discuss and refine the behavior of the feature, including which methods should be implemented first</ul>
| C++, JavaScript
| [https://mozillians.org/en-US/u/paolo/ Paolo]
|
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Source Map Library
| This project would implement missing library support for certain of the source map spec, specifically "indexed" source maps, and experimenting with extensions for encoding the original source code's lexical environment in the source map.
| JavaScript, Node.js
| [https://mozillians.org/en-US/u/fitzgen/ fitzgen]
| [https://mozillians.org/en-US/u/fitzgen/ fitzgen]
| Easy for a contributor to ramp up on, because it can be done completely in Node.js without needing to build Firefox.
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Mailbox-to-maildir converter
| Mailbox and Maildir are two alternative on-disk storage formats for email messages. Thunderbird currently uses Mailbox, but wants to use Maildir. Hence the need for a converter. This is one of the last critical pieces blocking moving away from mbox-style mailboxes. See {{bug|856087}}.
| JavaScript, C++
| jcranmer
| rkent
|
|-
| Alternate protocol for mailnews folders
| Thunderbird has long-term plans to implement a variety of mail and mail-like protocols to be managed as mailnews folders. An existing addon (SkinkGlue) exists to provide the glue for this. Implement one other protocol, which might be Fastmail's JMAP, or Calendar events & tasks
| JavaScript
| rkent
| rkent and, depending on protocol brong from Fastmail, or Fallen
| I doubt having 2 twitter implementations in Thunderbird is a valuable investment of time. JMAP seems the most promising protocol idea here; do we know if brong is on board to (co-)mentor this? Even though the code would be primarily written in JS, I suspect having some C++ skills to be able to understand some of mailnews' internals would be very helpful.
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Improve the JavaScript XMPP implementation and implement new features.
| Includes better error handling, implementing multi-user chats (MUCs), test coverage and adding new/missing features. Feature-parity with libpurple's XMPP implementation is one of the prerequisites for replacing it with the JavaScript implementation and is an end-goal of this project. Students are expected to compile a list of bugs or unimplemented features in the JavaScript XMPP code.
| JavaScript, XPCOM, an understanding of XMPP is desired
| Florian Quèze
| aleth, Patrick Cloke [:clokep]
|
|-
| Implement a new protocol plug-in in JavaScript
| Instantbird supports protocol plugins implemented in JavaScript. The student will add support for a new protocol in Instantbird. The student working on new protocols should take every opportunity to improve the code and APIs shared by all JavaScript protocol plugins (IRC, XMPP, Yahoo and Twitter). It is expected that the student research the feasibility of interoperability concerns of the protocol during the application period. Students are expected to implement a protocol they use on a day-to-day basis to dog-food the code.
| JavaScript, XPCOM, maybe js-ctypes, understanding of network protocols
| Patrick Cloke
| Patrick Cloke [:clokep]
| Possible protocols include: Google Hangouts, Facebook, WhatsApp, SIP, Bonjour, OSCAR, TextSecure or Telegram
|-
| File transfer support
| API design, backend implementation, frontend UI for supporting file transfers in Instantbird.
| XPCOM, JavaScript, webrtc, networking protocols
| nhnt11
| Patrick Cloke [:clokep]
|
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Introducing Calendar Accounts
| Traditionally our calendar extension is organized into a list of calendars, each calendar being implemented by a “provider”, for example local storage or using the CalDAV protocol. The service to manage these calendars maintains a simple list, the entries have no connection to each other.
Some calendar providers would greatly benefit from being able to group calendars into accounts, for example free-busy lookups are usually per-server operations and not per-calendar. It would also open the door for some great new features that have been postponed because they can be implemented cleaner with the notion of accounts.
| XUL, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
| [[Media:Calendar-gsoc2015-calmgr.pdf|Click here for a detailed project description]]
|-
| Resource Booking Improvements
| The Lightning extension has a dialog for inviting attendees to an event, which also shows availability information. Albeit not very obvious, it also allows booking resources and rooms. To improve this experience we would like users to be able to pick rooms and resources in a way that they don't need to remember the room address and quickly see which rooms and resources exist and are available around the proposed time of the event.
| XUL, CSS, JavaScript
| [mailto:mozilla@kewis.ch Fallen]
| [mailto:mozilla@kewis.ch Fallen]
| [[Media:Calendar-gsoc2015-resourcebooking.pdf|Click here for a detailed project description]]
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Bugzilla Extension Exchange Format
| Write an installer script for Bugzilla extensions
| Perl
| dylan (dylan@mozilla.com)
| dylan
| Spec: http://hardison.net/~dylan/BEEF.html
|}

== Accessibility ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance Alerts Release Management Toolchain
| This GSOC project will deliver functionality of detecting alerts as they merge between branches. This is mostly important for regressions, but should also include improvements. We generate thousands of performance alerts every year, and we need a way to look at the high level of what is concerning while having the ability to drill down and understand what small details make up the bigger problems. This depends on us seeing these regression when the code was originally introduced and action being taken to file a bug. In many cases we have preferences that turn features on and off which will have an affect on the alerts that we care about. The target here is a release manager can go to a dashboard, and see the state of the release (most important after uplifting code) and get a list of bugs that are of interest.

This will be integrating a system into TreeHerder to store alerts and allow graphs of the data to be annotated. There will be an API so alert can be generated from other sources and managed by other tools as well.

| Python, AngularJS, SQL, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/wlach/ Will Lachance]], [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| The impact here is the ability for developers and release managers to see the performance impact of their changes while helping us track this.
|-
| Retry failures in automation and provide annotations for intermittent failures vs real failures
| Of the thousands of unitests which are run for each platform and each push we find many intermittent failures. This is a pain point for developers when they test their code on try server. Now that we have TreeHerder, it isn't much work to automatically annotate jobs as intermittent or a regression/failure. In mochitest we have --bisect-chunk which will retry the given test and determine if it is an intermittent or a real regression. The goal here is to do this automatically for all jobs on try server. Jobs will still turn orange. With the outcome of this project failures would need to have a different view in the UI.
| Python, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| This will build off an existing set of tools while helping us bridge the gap towards a much better review and automated landing of patches system. In the short term, this will aid in developers who see failures and either do multiple pushes, many retriggers, or just ignore them- in summary we will not need to worry as much about wasting resources related to intermittents.
|-
| Unittest sanitizer
| With our thousands of test files, there are hundreds that have dangerous api calls which result in leftover preferences, permissions, and timing issues. A lot of work has been done here, we need to fix tests and expand our work on these resources to all our tests. In addition to cleaning up dangerous test code, we need to understand our tests and how reliable they are. We need to build tools that will allow us to determine how safe and reliable our tests are individually and as part of a suite. Upon completion of this project we should have the majority of tests cleaned up, and a toolchain that can be easily run and generate a report on how stable each test is.
| Python, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/mwargers/ Martijn Wargers]], [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| The impact this has is helping us cleanup our tests to reduce intermittents and give us tools to write better tests and understand our options for running tests in different configurations.
|-
|mozregression GUI
|Using Python, create a graphical user interface for mozregression (http://mozilla.github.io/mozregression) along with an installer and automatic update system to make it easier for less technical contributors to find and report regression ranges in Firefox and Thunderbird.
|Python
|[mailto:wlachance@mozilla.com William Lachance]
|[mailto:wlachance@mozilla.com William Lachance], [mailto:j.parkouss@gmail.com Julien Pagès]
|-
| Convert Mozmill test cases to Marionette
| he Mozmill framework is being replaced by Marionette to support multi-process Firefox. In the previous Mozmill toolchain we have dozens of libraries and hundreds of tests. This project will entail assessing those tests for uniqueness (compared to browser-chrome) and porting what tests and libraries make sense to Marionette. The goal here is to assess all the tests and have at least 75 converted.
| Python, Javascript
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]]
| [[https://mozillians.org/en-US/u/jmaher/ Joel Maher]], [[https://mozillians.org/en-US/u/whimboo/ Henrik Skupin]]
| Existing tests live here:
http://hg.mozilla.org/qa/mozmill-tests/file/default

new tests live here:
https://github.com/mozilla/firefox-ui-tests
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Define, test, and publish json hyperschemas for all release engineering APIs
| We have several APIs (e.g. buildapi, clobberer, (modern) mapper, mozpool, slavealloc, slaveapi, ...) but have no central standardised way of defining them, publishing them, documenting them, or sharing them. A cool project would be to use json hyperschema (see e.g. https://brandur.org/elegant-apis) to define all our apis, and have a framework for auto testing them, auto-documenting them, even potentially auto-generating client libraries for them e.g. in python, and auto-publishing the schemas to a central location for reference. Another interesting option might be using http://swagger.io/.

Example REST apis that we have are:

* Build API: https://wiki.mozilla.org/ReleaseEngineering/Applications/BuildAPI
* Clobberer: https://api.pub.build.mozilla.org/docs/usage/clobberer/#endpoints
* (Modern) Mapper: https://wiki.mozilla.org/ReleaseEngineering/Applications/Mapper
* Mozpool: http://hg.mozilla.org/build/mozpool/file/tip/API.txt
* Slave API: http://mozilla-slaveapi.readthedocs.org/en/latest/api/#slaves-slave-actions-disable

This GSoC project would involve creating hyperschemas for the above APIs (and potentially others too), finding a good place to publish these references, and look at setting up some tools to generate documentation for these APIs, together with code generation of client libraries, and their associated documentation (godoc, javadoc, …) and if time allows, even auto-generation and deployment of new documentation, libraries, as and when these json hyper schemas get updated (perhaps with travis ci deploying to e.g. github pages or heroku).
| json, json hyperschema, solid programming skills, enthusiasm, code generation, web interface design
| [mailto:pmoore@mozilla.com Pete Moore]
| [mailto:pmoore@mozilla.com Pete Moore]
| Some good starting points:
* http://spacetelescope.github.io/understanding-json-schema/ (for json schema)
* https://brandur.org/elegant-apis (for json hyper schema)
* http://json-schema.org/
|-
| Decouple Mozharness internals by breaking it into standalone modules
| What is Mozharness: It's a configuration-driven script harness that is used for automating > 90% of Mozilla's build and test jobs. It is also used by release engineering services outside of continuous integration.

What needs to decoupled: Mozharness has reached some scaling issues. Jobs that do builds and tests inherit and share exhaustive number of mixins. This leads to a complicated Method Resolution Order and objects with too many attrs that are not even needed.

How can this be done: replace the mixins with standalone classes that act as services. The classes can be instantiated many times and are aware of only their own responsibilities. Once stand alone, you then make them into packages within a mozharness library and installable by pip.

The benefit:

* better scalability
* more pythonic so the entry for contribution is less intimidating
* tools outside of mozharness can avail of subcomponents of mozharness

steps and goals for gsoc:

* part (1) take mixins like log.py, config.py, buildbot.py, python.py, signing.py, and tooltool.py and convert them from mixins to standalone classes
** example of how that's done: {{bug|1063532}}
* part (2) turn the now standalone classes into python packages

| python, solid programming skills, enthusiasm
| [mailto:jlund@mozilla.com Jordan Lund], Armen Zambrano
| [mailto:jlund@mozilla.com Jordan Lund]
| more details:

* https://docs.google.com/a/mozilla.com/document/d/1AQZT9opDkqb0tgZaVAtfAX2_dVWFHNWmz0ImgS5-hPM
* https://etherpad.mozilla.org/mozharness-mixins
* http://hg.mozilla.org/build/mozharness
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| rustfmt
| Create a code formatting tool that automatically reformats Rust code to meet conventions.
| Experience with Rust.
| [https://mozillians.org/en-US/u/brson brson]
| [https://mozillians.org/en-US/u/brson brson], [http://www.rustaceans.org/nick29581 nrc]
|
|-
| Rust Code Completion for SublimeText
| This project would develop a plugin for the Sublime Text editor that provides code completion for the Rust programming language, by integrating with the Rust [https://github.com/phildawes/racer Racer] project. This would require interfacing between Python (for the Plugin) and Rust (for Racer).
| Rust, Python
| [https://mozillians.org/en-US/u/pnkfelix pnkfelix]
| [https://mozillians.org/en-US/u/pnkfelix pnkfelix]
|
|-
| Refactoring Rust
| Create a tool for refactoring Rust code.
| Experience with Rust.
| [http://www.rustaceans.org/nick29581 nrc]
| [http://www.rustaceans.org/nick29581 nrc]
|
|-
| Tools and macros
| Develop tools and/or APIs for comprehension and manipulation of macros. For example, extend DXR to work with macros or demonstrate a proof of concept refactoring or formatting tool that works with macros.
| Experience with Rust, particularly macros.
| [http://www.rustaceans.org/nick29581 nrc]
| [http://www.rustaceans.org/nick29581 nrc]
|
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Speculative HTML parsing
| Servo's [https://github.com/servo/html5ever/ HTML parser] currently blocks whenever it needs to execute JS code (eg. when <script> tags are encountered in a page). We want to split the HTML parsing code into two threads, one of which can continue parsing the rest of the HTML source [http://www.dorothybrowser.com/portfolio/parallel-parser/ speculatively] while the other is busy executing JS; once the second is finished, the parser can use the result of the first thread's efforts to improve page load performance.
| Prior [http://www.rust-lang.org/ Rust] experience valuable. Familiarity with HTML.
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/kmcallister/ kmc]
|-
| HTTP/2 implementation in hyper
| [https://github.com/hyperium/hyper/ Hyper], the Rust HTTP library that Servo relies upon, is missing support for exciting new technologies like [https://http2.github.io/ HTTP/2]. This project would design and integrate an HTTP/2 implementation into the client and servo code for hyper.
| Experience writing code that interacts with network protocols. Prior [http://www.rust-lang.org/ Rust] experience valuable.
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/seanmonstar/ seanmonstar] and [https://github.com/reem/ reem]
|-
| Server-Sent Events
| Servo lacks an implementation of the [https://developer.mozilla.org/en-US/docs/Web/API/EventSource EventSource Web API]. The goal of this project is to implement that API, following the [https://html.spec.whatwg.org/multipage/comms.html#server-sent-events specification] as closely as possible and enabling the [https://github.com/w3c/web-platform-tests/tree/master/eventsource tests] for this feature that already exist.
| Prior experience with [http://www.rust-lang.org/ Rust] valuable. Comfortable reading and writing JavaScript for the web.
| [https://mozillians.org/en-US/u/jdm/ jdm]
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|-
| Improve form support
| Servo currently has rather basic form support, with simple widgets. We lack support for many form controls and functionality like file uploads and form validation. We'd like to add support for most form behavior, based on the [https://html.spec.whatwg.org/multipage/forms.html specification].
| Familiarity with web HTML/Javascript. Prior experience with [http://www.rust-lang.org/ Rust] and/or reading web specifications valuable.
| [https://mozillians.org/en-US/u/Manishearth Manishearth]
| [https://mozillians.org/en-US/u/Manishearth Manishearth] (or [https://mozillians.org/en-US/u/jdm/ jdm])
|
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [https://github.com/noflo/noflo-ui NoFlo-UI]
| Implement an UI widget on noflo-ui. It could be a timeline (see [https://github.com/noflo/noflo-ui/issues/151 this issue]), plugins for IIP editing or packet display for particular data types. Considering the timeline widget, an initial prototype could be a component library (see [https://github.com/noflo/noflo-tween/blob/master/components/Timeline.coffee noflo-tween]). Proposals should include sketches and an implemented prototype (pull requested to noflo-ui).
| javascript, coffeescript, ux
| [[User:Forresto|Forresto]]
| [[User:Forresto|Forresto]]
| [http://noflojs.org NoFlo] is a JS dataflow implementation and has runtimes for browser, image processing ([https://github.com/jonnor/imgflo imgflo]), microcontrollers ([https://github.com/jonnor/microflo microflo]), SuperCollider ([https://github.com/jonnor/sndflo sndflo]) and other targets. [https://app.flowhub.io Flowhub] is the browser-based IDE for the creation of NoFlo graphs.
|-
| [https://github.com/tweenjs/tween.js Tween.JS]
| Port Tween.js to ES6 and make it a modern citizen of the JS world
| javascript, web animations, graphics
| [[User:Sole|Sole]]
| [[User:Sole|Sole]]
| Tween.JS is a small engine for declaring and running interpolations between values. It's used in interactive experiences, games and all sorts of projects.
|-
| [https://github.com/sole/Animated_GIF Animated_GIF]
| Refactor and build a version 2, splitting the library into independent reusable modules. Also work on compatibility with Firefox OS.
| javascript, web animations, graphics, web workers, pixel handling, canvas
| [[User:Sole|Sole]]
| [[User:Sole|Sole]]
| Animated_GIF is a library for generating Animated GIFs on the browser. It's used in demo apps in mozilla, some properties at webmaker, the wildly successful chat at meatspac.es and who knows where else.
|-
| Create image filters using [http://noflojs.org NoFlo]
| It's possible to start prototyping image filters using [https://app.flowhub.io Flowhub] (use [https://www.filterforge.com/ Filter Forge]'s filters as inspiration and our porting of [https://github.com/jonnor/imgflo/wiki/Recreating-Instagram-filters some Instagram filters]) and components libraries like [http://github.com/noflo/noflo-image noflo-image] and [http://github.com/noflo/noflo-canvas noflo-canvas], then port the filters to imgflo. Another option is to create filters directly on imgflo using GEGL. Proposals should include a running NoFlo graph for a non-trivial image filter, together with sketches and original/processed images. Imgflo+GEGL filters are preferred. Pull requests to noflo-image and imgflo are a plus.
| javascript, coffeescript, noflo, cpp, computer vision basics
| [[User:Vilsonvieira|Vilson Vieira]]
| [[User:Vilsonvieira|Vilson Vieira]]
| [http://noflojs.org NoFlo] is a JS dataflow implementation and has runtimes for browser, image processing ([https://github.com/jonnor/imgflo imgflo]), microcontrollers ([https://github.com/jonnor/microflo microflo]), SuperCollider ([https://github.com/jonnor/sndflo sndflo]) and other targets. [https://app.flowhub.io Flowhub] is the browser-based IDE for the creation of NoFlo graphs. [http://gegl.org GEGL] is a graph-based image processing framework used by imgflo (it's also possible to use noflo-canvas instead of GEGL, but GEGL is preferred due to performance reasons).
|}

== Webmaker ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Automated front-end testing
| Help build automated front-end tests for our Cordova App and investigate different cross-platform continuous integration systems (e.g. sauce labs), with a specific emphasis on Android and Firefox OS.
| javascript, nodejs
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
|
|-
| Community moderation for webmaker.app
| Help build/improve admin interface, integrate with our services architecture to help choose featured content and support community moderation
| javascript, nodejs, css, html
| [[User:k88hudson|k88hudson]]
| [[User:k88hudson|k88hudson]]
|
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [http://www.mozillascience.org/projects/codemeta Code as a Research Object]
| Using the proposed [https://github.com/mbjones/codemeta crosswalk schema] between existing software metadata, create a service (can be a simple website) that will allow users to search and filter software across existing data archives and repositories (Zenodo, figshare, GitHub). Comparing the existing schemas for code storage to help create a metadata standard that allows for discoverability, reuse and citation.
| json, [http://zenodo.org/dev zenodo api], [http://api.figshare.com/docs/intro.html figshare api], [https://developer.github.com/ github api]
| [[User:Abby|Abby]]
| [[User:Abby|Abby]]
| "Code as a Research Object" is exploring integrating software into the scholarly workflow. Collaboration with GitHub, figshare and Zenodo.

Background reading: http://www.mozillascience.org/code-as-as-research-object-new-phase/

http://www.mozillascience.org/code-as-a-research-object-metadata-for-software-discovery/

http://www.mozillascience.org/code-as-a-research-object-updates-prototypes-next-steps/
|-
|}

Firefox/Meeting/21-Jul-2015

2015-07-21T12:26:11Z

P.A.: General Topics / Roundtable

== Details ==

* Third Tuesday of the month - 8:00am Pacific, 11:00am Eastern, 15:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/8:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics / Roundtable ==
(tips/tricks, productivity improvements, industry news)
* BrowserTestUtils
* Easily add live pref-controlled logging to your module which outputs to stdout and the Browser Console (with inspectable objects): <code>
XPCOMUtils.defineLazyGetter(this, "log", () => {
let ConsoleAPI = Cu.import("resource://gre/modules/devtools/Console.jsm", {}).ConsoleAPI;
let consoleOptions = {
maxLogLevelPref: PREF_LOG_LEVEL,
prefix: "My Log Prefix",
};
return new ConsoleAPI(consoleOptions);
});
</code>
* Frequency of this meeting
* What is the status of feature reviews?
* What is the status of product line reviews?
* Have we centrally documented our new sub-team structure?
** Helps to find whom to ask if you have a question about something
** Existing module system doesn't have answers for User Experience and Product

== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping report, fix and test bugs.''

Thanks to the following people for regular contributions to the desktop Firefox front-end in the last year!
* Alice White [:Alice0775]
* Aryx [:archaeopteryx][:aryx]
* Brian R. Bondy [:bbondy]
* Ekanan Ketunuti
* Ian Moody [:Kwan]
* Luís Miguel [:Quicksaver]
* Masatoshi Kimura [:emk]
* Richard Marti [:Paenglab]
* Sören Hentzschel
* Tim Nguyen [:ntim]
* Tooru Fujisawa [:arai]
* and probably others who were missed!

== Project Updates ==
=== e10s ===
=== Hello ===
=== Privacy/Security ===
* Planning to ship Tracking Protection in Private Browsing for 42
** Likely one tracking list with a tour ([https://www.dropbox.com/sh/nhh6z6nr9gx0mng/AAAPYeSlfVZADtNGeGqIh1pwa?dl=0&preview=Tp+Onboarding+Spec+v3.png spec]).
* Interns are continuing [https://docs.google.com/spreadsheets/d/1hty3GVRIc-BwPSr9y-FCvrPo40c3v_otGTcGuOmrtQY/edit#gid=1896114302 great work on the password manager] for 42.

=== Search ===
* Unified Autocomplete bugs still being resolved
* Search suggestions in the awesomebar
=== Windows 10 ===
* Ensure Firefox is not completely broken in Firefox 40 (fix critical bugs) and tweak UI to make it fit in better with Windows 10 look and feel overall.
** Windows 10 updates officially to start to go out on July 29th, 2015.
** Firefox 40 GA on Aug 11th, 2015.

Firefox/Meeting/21-Jul-2015

2015-07-21T12:18:21Z

P.A.: General Topics / Roundtable

== Details ==

* Third Tuesday of the month - 8:00am Pacific, 11:00am Eastern, 15:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/8:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics / Roundtable ==
(tips/tricks, productivity improvements, industry news)
* BrowserTestUtils
* Easily add live pref-controlled logging to your module which outputs to stdout and the Browser Console (with inspectable objects): <code>
XPCOMUtils.defineLazyGetter(this, "log", () => {
let ConsoleAPI = Cu.import("resource://gre/modules/devtools/Console.jsm", {}).ConsoleAPI;
let consoleOptions = {
maxLogLevelPref: PREF_LOG_LEVEL,
prefix: "My Log Prefix",
};
return new ConsoleAPI(consoleOptions);
});
</code>
* Frequency of this meeting
* What is the status of feature reviews?
* What is the status of product line reviews?

== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping report, fix and test bugs.''

Thanks to the following people for regular contributions to the desktop Firefox front-end in the last year!
* Alice White [:Alice0775]
* Aryx [:archaeopteryx][:aryx]
* Brian R. Bondy [:bbondy]
* Ekanan Ketunuti
* Ian Moody [:Kwan]
* Luís Miguel [:Quicksaver]
* Masatoshi Kimura [:emk]
* Richard Marti [:Paenglab]
* Sören Hentzschel
* Tim Nguyen [:ntim]
* Tooru Fujisawa [:arai]
* and probably others who were missed!

== Project Updates ==
=== e10s ===
=== Hello ===
=== Privacy/Security ===
* Planning to ship Tracking Protection in Private Browsing for 42
** Likely one tracking list with a tour ([https://www.dropbox.com/sh/nhh6z6nr9gx0mng/AAAPYeSlfVZADtNGeGqIh1pwa?dl=0&preview=Tp+Onboarding+Spec+v3.png spec]).
* Interns are continuing [https://docs.google.com/spreadsheets/d/1hty3GVRIc-BwPSr9y-FCvrPo40c3v_otGTcGuOmrtQY/edit#gid=1896114302 great work on the password manager] for 42.

=== Search ===
* Unified Autocomplete bugs still being resolved
* Search suggestions in the awesomebar
=== Windows 10 ===
* Ensure Firefox is not completely broken in Firefox 40 (fix critical bugs) and tweak UI to make it fit in better with Windows 10 look and feel overall.
** Windows 10 updates officially to start to go out on July 29th, 2015.
** Firefox 40 GA on Aug 11th, 2015.

WeeklyUpdates/2015-04-20

2015-04-20T10:08:32Z

P.A.: /* Friends of Mozilla Friends of Mozilla */ Thanks for a very good contribution!

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

* Thanks to Ganesh Sahukari for fixing a long-standing issue in Firefox with [https://bugzilla.mozilla.org/show_bug.cgi?id=1009465 opened documents not being set read-only on Windows], adding [https://bugzilla.mozilla.org/show_bug.cgi?id=1022816 a new OS.File API] in the process.

== Upcoming Events ==

=== This Week ===
* Check out a [http://dragonair.student.iastate.edu/mozilla/sourcecodeknowledge/project/gecko-dev/ website/tool developed for academic dissertation work to help Mozilla developers better understand the codebase and communication structure]. Help out by participating in a short 15 minute interview on IRC. Contact Patrick to setup an interview time (IRC: '''carlsonp''', email: '''carlsonp@iastate.edu'''). Cheers!

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
*[http://fluentconf.com/javascript-html-2015/public/schedule/speakers / O'Reilly FLUENT Conference: The Web Platform]
**April 20th-22nd in San Francisco
** Mozillians attending are Andreas Gal: Keynote Speaker, Dan Callahan + Mike Taylor: Tutorial, Potch: Tech Demo
** Fluent spotlights the emerging methods, tools, and technologies of the Web Platform. Developers, software engineers, UX/UI designers, and other web professionals come to Fluent to share their experiences and expertise—and to learn what they need to know to stay competitive
*[https://quality.mozilla.org/event/bug-triage-day-56/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
*[http://mobilewestafrica.com/2015/ MEF Nigeria: Mozilla at Mobile West Africa]
** April 21st to 23rd in Lagos, Nigeria
** Mozillians in attendance Nisha Malhan and Tayo Fagbohun
**MEF Nigeria is part of Mobile West Africa for 2015. It will be the 16th event in the Mobile Web Africa series of conferences across Sub-Saharan Africa and All Amber’s 20th conference since the company’s inception in 2009

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
*[https://quality.mozilla.org/event/bug-verification-day-61/ Weekly Bug Verification Day]

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
*[http://2015.phillytechweek.com/events/dev_day_big_talks/ Philly Tech Week: Dev Day Talks]
** April 23rd in Philadelphia, PA
**Mozillian attending Andrew Sutherland, Speaking on The Firefox OS email app: devious stratagems for offline HTML apps on limited-resource devices
** An afternoon of high-level dev talks focused around problem solving and innovative solutions. You'll hear from over 15 dev experts talking about real world scenarios and the tools they're using

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===
*[http://linuxfestnorthwest.org/2015 Linux Fest Northwest]
** April 25th-26th in Bellinghan, WA
** Mozillian attending Benjamin Kerensa
**LinuxFest Northwest is the longest running, largest open source conference in the Pacific Northwest

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Content Services ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table wikitable"
|-
! Who are you
! Area of Question
! Question
|-
| ''What is your Name?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''
|-

|-
|}

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! New Volunteers
! Introduced by
! Speaker location
! New Volunteers location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Rob Thijssen
| Q Fortier
| Portland
| Remote (UK)
| Senior DevOps Engineer
|-

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Automation & Tools ===
==== bugzilla.mozilla.org ====
Notable changes to [https://bugzilla.mozilla.org/ bugzilla.mozilla.org] during the last week:
* {{bug|1152818}} Changing an assignee to nobody@mozilla.org now automatically resets the status from ASSIGNED to NEW
[[BMO/Recent_Changes|All changes]].

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Community:SummerOfCode15:Brainstorming

2015-02-19T17:04:02Z

P.A.: /* Firefox */ Add Download Integrity project

Mozilla community members - submit proposals here for 2015 Google Summer of Code projects with Mozilla. (If this page looks empty, it's because accepted ideas have already been transferred to the [[Community:SummerOfCode15|official list]].) '''The''' absolute last '''deadline for submitting ideas''' in time to help us get accepted by Google '''is February 20th'''.

Are you a students looking to apply to SoC with Mozilla? Your first stop should be the [[Community:SummerOfCode15|official list of ideas]]. This page is full of weird and whacky ideas, some of which are still on here for a reason - 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 - don't be fooled by the "Code" in "Summer of Code". If there is no category below for your part of Mozilla, add one!

== Mozilla Platform (Gecko) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Firefox Performance Dashboard
| This project would implement the dashboard described in [https://bugzilla.mozilla.org/show_bug.cgi?id=1132498 bug 1132498]. Collecting the memory and CPU usage of addons and webpages and displaying it in a fashion that shows bad actors would be valuable for power users.
| HTML, CSS, JavaScript
| [https://mozillians.org/en-US/u/jdm/ jdm]
|
|
|-
| Download Integrity
| Enhance detection of broken downloads in Firefox. Methods may include:<ul><li>[http://www.w3.org/TR/SRI/#the-a-element-1 Subresource Integrity for the <a> element]<li>[[Features/HTTP_Digest_header_verification#Stage_1:_Definition|HTTP Digest header verification]]<li>Network-level indications like bad HTTP framing</ul>The activities include:<ul><li>Implement the front-end in JavaScript to display failed integrity checks<li>Implement and/or use the required back-end features in C++<li>Work with the Mozilla community to discuss and refine the behavior of the feature, including which methods should be implemented first</ul>
| C++, JavaScript
| Paolo
| Paolo
|
|}

== Firefox Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox for Android ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox OS / Boot2Gecko ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Thunderbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| Performance testing
| Add and deploy a performance testsuite for Thunderbird to catch regressions in areas such as startup, message search, folder display, message display, etc.
| JavaScript, Python, preferably some performance analysis experience
| jcranmer
| ?
| Needs a mentor -- florian
|-
| Secure email UI
| Develop good interfaces for key management and illustrating the security levels of messages succinctly, preferably applicable to both S/MIME and OpenPGP.
| Strong UX experience; JS, XUL or HTML; crypto background advantageous
| jcranmer
| ?
| Summer of Code is about coding, not about UX work; asking students to do UX work often leads to disappointing results -- florian. This may be too large a task; narrowing focus could be useful.
|-
| Alternate protocol for mailnews folders
| Thunderbird has long-term plans to implement a variety of mail and mail-like protocols to be managed as mailnews folders. An existing addon (SkinkGlue) exists to provide the glue for this. Implement one other protocol, which might be Twitter, Fastmail's JMAP, or Calendar events & tasks
| Javascript
| rkent
| rkent and, depending on protocol, a chat guy (clokep?), brong from Fastmail, or Fallen
| I doubt having 2 twitter implementations in Thunderbird is a valuable investment of time. JMAP seems the most promising protocol idea here; do we know if brong is on board to (co-)mentor this? Even though the code would be primarily written in JS, I suspect having some C++ skills to be able to understand some of mailnews' internals would be very helpful.
|-
|}

== Instantbird ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Calendar ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== SeaMonkey ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

==NSS (Network Security Services)==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Bugzilla ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Firefox Support (SUMO) ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== QA ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Automation & Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|-
|}

== Documentation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla Developer Network ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Mozilla IT and Infrastructure ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Sync / Services ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Developer Tools ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Add-on SDK ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Foundation ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== OpenArt ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
| [https://github.com/noflo/noflo-ui NoFlo-UI]
| Implement an UI widget on noflo-ui. It could be a timeline (see [https://github.com/noflo/noflo-ui/issues/151 this issue]), plugins for IIP editing or packet display for particular data types. Considering the timeline widget, an initial prototype could be a component library (see [https://github.com/noflo/noflo-tween/blob/master/components/Timeline.coffee noflo-tween]). Proposals should include sketches and an implemented prototype (pull requested to noflo-ui).
| javascript, coffeescript, ux
| [[User:Forresto|Forresto]]
| [[User:Forresto|Forresto]]
| [http://noflojs.org NoFlo] is a JS dataflow implementation and has runtimes for browser, image processing ([https://github.com/jonnor/imgflo imgflo]), microcontrollers ([https://github.com/jonnor/microflo microflo]), SuperCollider ([https://github.com/jonnor/sndflo sndflo]) and other targets. [https://app.flowhub.io Flowhub] is the browser-based IDE for the creation of NoFlo graphs.
|-
| [https://github.com/tweenjs/tween.js Tween.JS]
| Port Tween.js to ES6 and make it a modern citizen of the JS world
| javascript, web animations, graphics
| [[User:Sole|Sole]]
| [[User:Sole|Sole]]
| Tween.JS is a small engine for declaring and running interpolations between values. It's used in interactive experiences, games and all sorts of projects.
|-
| [https://github.com/sole/Animated_GIF Animated_GIF]
| Refactor and build a version 2, splitting the library into independent reusable modules. Also work on compatibility with Firefox OS.
| javascript, web animations, graphics, web workers, pixel handling, canvas
| [[User:Sole|Sole]]
| [[User:Sole|Sole]]
| Animated_GIF is a library for generating Animated GIFs on the browser. It's used in demo apps in mozilla, some properties at webmaker, the wildly successful chat at meatspac.es and who knows where else.
|-
| Create image filters using [http://noflojs.org NoFlo]
| It's possible to start prototyping image filters using [https://app.flowhub.io Flowhub] (use [https://www.filterforge.com/ Filter Forge]'s filters as inspiration and our porting of [https://github.com/jonnor/imgflo/wiki/Recreating-Instagram-filters some Instagram filters]) and components libraries like [http://github.com/noflo/noflo-image noflo-image] and [http://github.com/noflo/noflo-canvas noflo-canvas], then port the filters to imgflo. Another option is to create filters directly on imgflo using GEGL. Proposals should include a running NoFlo graph for a non-trivial image filter, together with sketches and original/processed images. Imgflo+GEGL filters are preferred. Pull requests to noflo-image and imgflo are a plus.
| javascript, coffeescript, noflo, cpp, computer vision basics
| [[User:Vilsonvieira|Vilson Vieira]]
| [[User:Vilsonvieira|Vilson Vieira]]
| [http://noflojs.org NoFlo] is a JS dataflow implementation and has runtimes for browser, image processing ([https://github.com/jonnor/imgflo imgflo]), microcontrollers ([https://github.com/jonnor/microflo microflo]), SuperCollider ([https://github.com/jonnor/sndflo sndflo]) and other targets. [https://app.flowhub.io Flowhub] is the browser-based IDE for the creation of NoFlo graphs. [http://gegl.org GEGL] is a graph-based image processing framework used by imgflo (it's also possible to use noflo-canvas instead of GEGL, but GEGL is preferred due to performance reasons).
|}

== Release Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Emscripten ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Rust ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Servo ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Engineering ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|}

== Localization ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Build system ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Security Assurance ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

== Mozilla Science Lab ==

{| class="standard-table" border="1" style="border-collapse: collapse"
|-
! Title
! Details
! Skills Needed
! Reporter
! Mentor(s)
! Comments
|-
|}

User:P.A./Address bar architecture improvements

2014-12-19T16:56:52Z

P.A.: Create page with description of technology prototype

== Overview ==

The address bar in Firefox currently relies on Form Autocomplete infrastructure for a number of tasks:
* Handle keyboard input in the text field
* Open and display the panel with the suggestions for locations to visit
* Read the list of suggestions to display, through an autocomplete provider for the Places database
* Handle keyboard navigation in the panel
* Accept and execute the navigation or action associated with selecting an item from the panel

While some of these may be similar to what is required by Form Autocomplete (for example, waiting some time after a key press before triggering a search), many others differ substantially in how they should be implemented. This led to the proliferation of special cases in the Form Autocomplete infrastructure to accommodate the needs of the address bar, and made the code difficult to maintain.

In fact, the address bar is a central part of the user experience, and as such has developed special use cases to which many users are accustomed, such as certain keyboard sequences leading to certain sites, based on the ordering of location suggestions. Since these developed spontaneously, they are not always captured by existing user interface tests. Trying to work with the current code, and keep correct handling of the common cases at the same time, makes progress slower when adding new features.

One of the ways to address these issues is incremental refactoring. Another approach, explored here, is prototyping a new codebase.

== Prototype ==

The prototype would be developed with the following characteristics in mind:
* Developed as a front-end Desktop-only browser component
* Only used by the address bar, which is then disconnected from Form Autocomplete
* Generates suggestions non-generically
** Makes queries to Places and gets results directly
** Does not try to reuse Unified Autocomplete, but copies part of its queries
* Uses JavaScript in all places where it is possible
* Uses new JavaScript language features
* Designed for asynchronous execution
* Has UI testing simulating mouse and keyboard input

In the process of doing this, we may understand where it makes sense to factor code in reusable modules and where it doesn't. For example, some of the work to handle keyboard navigation could be used to improve the search bar as well, but this will be clear only after the prototype is ready.

The initial cases the prototype would support are:
* Support direct navigation using the ENTER key or the GO button
* Type a full address (http://www.mozilla.org/) and navigate to it
* Type a shorter address (www.mozilla.org) and navigate to it
* With a page in history, for example https://www.mozilla.org/en-US/contribute/:
** Type a part of the address (www.mozilla.org) and navigate to the page
** Type a part of the title (at present "Volunteer") and navigate to the page
* Type part of the title of an open tab and switch to it
* Style a bookmarked page differently in the suggestions

Some explorations would be made possible:
* Richer styling of suggestions
* More complex keyboard interaction in the panel
** For example, search suggestions in the first row

Non-goals for the prototype:
* Match current address bar behavior
* Create a viable product ''(however, since this is a technology/implementation prototype, it will start with product-quality code)''

== Possible next steps ==

The purpose of the prototype is to understand whether there may be a way forward for this architecture. If so, the following steps would consist in:
* Identify clearer boundaries for reuse of existing components in the new architecture
* Bring existing components and tests into the new architecture, to match known use cases
* Honor a chosen subset of the currently supported address bar behavior preferences
* Switch to the new architecture on Nightly and discover more use cases
** The key difference with the current state would be that the changes to adapt to those use cases could be done much faster than now, and with fewer regressions
* Release the new architecture when it matches use cases satisfactorily
** Matching every single special case would be a non-goal

User:P.A./Form user experience improvements

2014-06-02T14:29:09Z

P.A.: /* References */ Add Toolkit Autocomplete bug list

== Overview ==

Submitting information to visited websites, using a '''web form''' or similar mechanism, is an increasingly common use case on the Internet.

Web forms are currently the preferred way for websites to ask the user for different classes of information:
* Common personal information, for example a '''name and address''' for shipping a product.
* Other identifying information that may be specific to one website, for example a '''username'''.
* Authentication of identity using a secret key, for example a '''password'''.
* Authentication and authorization of payments using secret '''credit card data'''.
* Recurring input that may be specific to one website, for example '''search terms'''.
* Information that may be reused on different websites, for example the '''e-mail address''' of a contact.
* Miscellaneous information that is entered only once, for example a '''message'''.

Each class of information has different characteristics, but most of them can generally benefit from a mechanism that is able to remember past input and help the user in entering the same data again, on either the same website or a different one.

=== Benefits ===

A good web form user experience, that takes into account previous input, is beneficial to both users and websites:
* Users will not need to spend time entering the same information again and again on different websites.
* Users returning to a website may authenticate more quickly using their stored username and password.
* Websites can have a lower barrier to entry when registering new users.
* Websites could accept payments with an easy user experience, but without the complex requirements created by storing credit card data on the server.

=== Themes ===

To offer a good user experience for all the different classes of information, the web browser needs to:
* '''Identify which class of information is being requested by the website.'''
** For complex data, this includes determining which input field corresponds to which part of the information.
* '''Collect and store data in the most reusable form.'''
** This includes building an accurate, reusable user profile from the available input.
* '''Adapt to different expected input in different websites.'''
** For example, deal with two separate name and surname fields or one single full name field.
** Different websites may have different field validation rules.
* '''Store and provide secret keys and data securely.'''
* '''Provide the simplest experience for completing the current task.'''
** For example, identify when a validation rule applies, and prevent the need of editing the data every time.
** The experience should be consistent across websites, so that if two websites look the same, the browser provides a similar experience with both of them.

There are current and proposed web APIs that websites my use to help the browser in solving these problems, but even for websites that don't use them, the browser should offer a solution that improves the overall experience.

Authors may be helped with upgrading their website to provide a better form experience with several actions:
* '''Provide meaningful console error messages and suggestions in the browser.'''
** These messages should be available by default to users of developer tools in Firefox.
** For example, indicate why the type of a field cannot be recognized.
* '''Define and evangelize best practices for websites.'''
** For example, a full name field is encouraged over separate name and surname fields.
* '''Encourage sites to adopt new web features.'''
** For example, the <code>autocomplete</code> attribute and the <code>requestAutocomplete</code> method.

== Approaches ==

The general problems stated above may be solved in several different ways, some of which have already been implemented in Firefox for a long time.

=== Login Manager ===

This existing feature stores usernames and passwords for future input.
* Populates username and password fields only.
** ''The username may be an e-mail address, but this is independent from the user profile.''
* The list of available usernames and associated passwords is specific to a particular website.
** ''This feature is often used with only a single username and associated password for each website.''
* May fill in the required information automatically once the user authorized the website.

=== Form History ===

This existing feature remembers past input in single-line text fields.
* Populates only one field at a time.
* Which list of past values is used depends only on an identifier provided by the website.
** ''The identifier is the HTML ''<code>name</code>'' or ''<code>id</code>'' attribute.''
* Past values are shared across all websites.
* Requires explicit user action on the individual field.
** ''This can be clicking to show the list of past values, or typing to search.''

Unrelated data can easily be mixed if different websites reuse the identifier with different meanings. Conversely, data cannot be reused if websites don't use the same identifier.

=== Form Autofill ===

This unimplemented feature remembers past input for common data sets, like personal information, that are generally shared across websites.
* Populates several related fields at a time.
* Past values are shared across all websites.
* May fill in the required information automatically once the user authorized the website.

=== requestAutocomplete ===

This unimplemented feature allows websites to explicitly request personal information from the browser.
* Replaces in-page form fields with a '''browser-provided interface'''.
* The browser may provide a different input experience depending on the device.
* Provides a similar input experience across all websites.
* Past values are shared across all websites.
* May fill in the required information automatically once the user authorized the website.

This feature works by transmitting the information to the server using '''hidden form fields''' after the website requested the browser to display the interface.

The website may display '''visible fields later in the process''' to correct any data validation errors.

== Comparison of strategies ==

One of the most difficult problems that '''form autofill''' has to deal with, for existing websites, is identifying which type of data is being requested by each form field. Authors can update the website to use the <code>autocomplete</code> attribute to help the browser, but the feature may not be available if the website doesn't do this. This can make it unclear to the user why one website supports autofill and another similarly-looking site doesn't.

On the other hand, '''requestAutocomplete''' only works with websites that have changed their input flow to explicitly request some personal information from the browser. This feature shows a browser-provided interface that provides data to the website. While the feature could be used in an "unclear" way to populate visible fields, similarly to form autofill, we can ensure that the difference is clear by '''requiring that target form fields are hidden''' at the time of the request to autocomplete them.

== Implementation ==

=== Existing features ===

Most of the main and support code for Login Manager and Form History can be found in these source folders and files:
* <code>toolkit/components/autocomplete/</code>
* <code>toolkit/components/passwordmgr/</code>
* <code>toolkit/components/satchel/</code>
* <code>toolkit/content/widgets/autocomplete.xml</code>

==== Suggesting past input ====

The autocompletion mechanism has the following typical control flow:
# The main entry point is the global '''<code>@mozilla.org/satchel/form-fill-controller;1</code>''' service implemented in <code>nsFormFillController.cpp</code>.
# All <code><browser></code> elements with an <code>autocompletepopup</code> attribute, at the time of the <code>pageshow</code> event, call <code>nsIFormFillController.attachToBrowser</code> on the global service.
# When an input field raises the <code>focus</code> event, <code>nsFormFillController::Focus</code> checks if autocompletion should be enabled, in which case it registers the input field with the global '''<code>@mozilla.org/autocomplete/controller;1</code>''' service, and starts forwarding input events to <code>nsIAutoCompleteController</code>.
#* The <code>nsFormFillController::GetSearchAt</code> method returns <code>form-history</code>, indicating that searches should be handled by the '''<code>@mozilla.org/autocomplete/search;1?name=form-history</code>''' global service, which is the same service implemented in <code>nsFormFillController.cpp</code>.
# At this point, typically while typing, <code>nsAutoCompleteController::HandleText</code> starts searches by calling the <code>nsFormFillController::StartSearch</code> method.
#* Note that the <code>nsIAutoCompleteInput.searchParam</code> getter of the same global service provides one of the parameters of the function.
# The <code>StartSearch</code> method dispatches the call through <code>autoCompleteSearch</code> or <code>autoCompleteSearchAsync</code> to either:
#* '''Login Manager''', through the global '''<code>@mozilla.org/login-manager;1</code>''' service.
#* '''Form History''', through the global '''<code>@mozilla.org/satchel/form-autocomplete;1</code>''' service.
# When the result is available, <code>nsFormFillController.cpp</code> invokes the <code>nsAutoCompleteController::OnSearchResult</code> method.
#* This stores the result in the global service implemented in <code>nsAutoCompleteController.cpp</code>.
#* This calls <code>nsIAutoCompletePopup.invalidate</code>, and also indirectly <code>nsIAutoCompletePopup.openAutocompletePopup</code>, on the entry returned by <code>nsFormFillController::GetPopup</code>, which is the <code>autocompletepopup</code> associated to the browser window.
#** The <code>openAutocompletePopup</code> method is called with a reference to the <code>nsIAutoCompleteInput</code> corresponding to the global service implemented in <code>nsFormFillController.cpp</code>.
# The <code>nsIAutoCompletePopup</code> interface will display the popup and handle its input.
#* This may cause the actual calls to be routed through IPC in case the interface is invoked in a child process.
# In response to popup events, the contents of the <code>input</code> field are updated.

==== Recording new input ====

When a form is submitted, saving the submitted data is handled by a different mechanism:
# The main entry point is the global '''<code>@mozilla.org/satchel/form-history-startup;1</code>''' service implemented in <code>FormHistoryStartup.js</code>.
# This registers the global <code>formSubmitListener.js</code> content script for all browsers.
# Form submissions monitored by the content script are translated into <code>FormHistory.jsm</code> calls to update the stored data.

=== Bug list ===

* {{bug|1009935}} - Implement the @autocomplete attribute for values other than off/on
* {{bug|939351}} - Implement requestAutocomplete backend
* {{bug|946022}} - Implement requestAutocomplete for Firefox for Android
* {{bug|990367}} - requestAutocomplete UI for Firefox desktop
* {{bug|998077}} - Sync support for autofill data
* {{bug|1007176}} - Implement requestAutocomplete on donate.mozilla.org
* {{bug|1007181}} - Project Review: requestAutoComplete on donate.mozilla.org

== References ==

* [https://etherpad.mozilla.org/requestautocomplete requestAutocomplete Etherpad]
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#autofill WHATWG Autofill specification work]
* [https://www.w3.org/Bugs/Public/buglist.cgi?component=HTML&list_id=34802&product=WHATWG&resolution=---&short_desc=autocomplete&short_desc_type=allwordssubstr WHATWG Autofill specification bug list]
* [https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DUI-Browser-Autofill-Interactive Chromium Autofill implementation bug list]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=10261611&classification=Components&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Form%20Manager&product=Toolkit Form Manager bug list]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=10374896&classification=Components&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Autocomplete&product=Toolkit Toolkit Autocomplete bug list]
* [https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion MDN documentation mentioning form autocompletion]

User:P.A./Form user experience improvements

2014-05-30T13:35:34Z

P.A.: /* Implementation */ Add implementation notes for existing features

== Overview ==

Submitting information to visited websites, using a '''web form''' or similar mechanism, is an increasingly common use case on the Internet.

Web forms are currently the preferred way for websites to ask the user for different classes of information:
* Common personal information, for example a '''name and address''' for shipping a product.
* Other identifying information that may be specific to one website, for example a '''username'''.
* Authentication of identity using a secret key, for example a '''password'''.
* Authentication and authorization of payments using secret '''credit card data'''.
* Recurring input that may be specific to one website, for example '''search terms'''.
* Information that may be reused on different websites, for example the '''e-mail address''' of a contact.
* Miscellaneous information that is entered only once, for example a '''message'''.

Each class of information has different characteristics, but most of them can generally benefit from a mechanism that is able to remember past input and help the user in entering the same data again, on either the same website or a different one.

=== Benefits ===

A good web form user experience, that takes into account previous input, is beneficial to both users and websites:
* Users will not need to spend time entering the same information again and again on different websites.
* Users returning to a website may authenticate more quickly using their stored username and password.
* Websites can have a lower barrier to entry when registering new users.
* Websites could accept payments with an easy user experience, but without the complex requirements created by storing credit card data on the server.

=== Themes ===

To offer a good user experience for all the different classes of information, the web browser needs to:
* '''Identify which class of information is being requested by the website.'''
** For complex data, this includes determining which input field corresponds to which part of the information.
* '''Collect and store data in the most reusable form.'''
** This includes building an accurate, reusable user profile from the available input.
* '''Adapt to different expected input in different websites.'''
** For example, deal with two separate name and surname fields or one single full name field.
** Different websites may have different field validation rules.
* '''Store and provide secret keys and data securely.'''
* '''Provide the simplest experience for completing the current task.'''
** For example, identify when a validation rule applies, and prevent the need of editing the data every time.
** The experience should be consistent across websites, so that if two websites look the same, the browser provides a similar experience with both of them.

There are current and proposed web APIs that websites my use to help the browser in solving these problems, but even for websites that don't use them, the browser should offer a solution that improves the overall experience.

Authors may be helped with upgrading their website to provide a better form experience with several actions:
* '''Provide meaningful console error messages and suggestions in the browser.'''
** These messages should be available by default to users of developer tools in Firefox.
** For example, indicate why the type of a field cannot be recognized.
* '''Define and evangelize best practices for websites.'''
** For example, a full name field is encouraged over separate name and surname fields.
* '''Encourage sites to adopt new web features.'''
** For example, the <code>autocomplete</code> attribute and the <code>requestAutocomplete</code> method.

== Approaches ==

The general problems stated above may be solved in several different ways, some of which have already been implemented in Firefox for a long time.

=== Login Manager ===

This existing feature stores usernames and passwords for future input.
* Populates username and password fields only.
** ''The username may be an e-mail address, but this is independent from the user profile.''
* The list of available usernames and associated passwords is specific to a particular website.
** ''This feature is often used with only a single username and associated password for each website.''
* May fill in the required information automatically once the user authorized the website.

=== Form History ===

This existing feature remembers past input in single-line text fields.
* Populates only one field at a time.
* Which list of past values is used depends only on an identifier provided by the website.
** ''The identifier is the HTML ''<code>name</code>'' or ''<code>id</code>'' attribute.''
* Past values are shared across all websites.
* Requires explicit user action on the individual field.
** ''This can be clicking to show the list of past values, or typing to search.''

Unrelated data can easily be mixed if different websites reuse the identifier with different meanings. Conversely, data cannot be reused if websites don't use the same identifier.

=== Form Autofill ===

This unimplemented feature remembers past input for common data sets, like personal information, that are generally shared across websites.
* Populates several related fields at a time.
* Past values are shared across all websites.
* May fill in the required information automatically once the user authorized the website.

=== requestAutocomplete ===

This unimplemented feature allows websites to explicitly request personal information from the browser.
* Replaces in-page form fields with a '''browser-provided interface'''.
* The browser may provide a different input experience depending on the device.
* Provides a similar input experience across all websites.
* Past values are shared across all websites.
* May fill in the required information automatically once the user authorized the website.

This feature works by transmitting the information to the server using '''hidden form fields''' after the website requested the browser to display the interface.

The website may display '''visible fields later in the process''' to correct any data validation errors.

== Comparison of strategies ==

One of the most difficult problems that '''form autofill''' has to deal with, for existing websites, is identifying which type of data is being requested by each form field. Authors can update the website to use the <code>autocomplete</code> attribute to help the browser, but the feature may not be available if the website doesn't do this. This can make it unclear to the user why one website supports autofill and another similarly-looking site doesn't.

On the other hand, '''requestAutocomplete''' only works with websites that have changed their input flow to explicitly request some personal information from the browser. This feature shows a browser-provided interface that provides data to the website. While the feature could be used in an "unclear" way to populate visible fields, similarly to form autofill, we can ensure that the difference is clear by '''requiring that target form fields are hidden''' at the time of the request to autocomplete them.

== Implementation ==

=== Existing features ===

Most of the main and support code for Login Manager and Form History can be found in these source folders and files:
* <code>toolkit/components/autocomplete/</code>
* <code>toolkit/components/passwordmgr/</code>
* <code>toolkit/components/satchel/</code>
* <code>toolkit/content/widgets/autocomplete.xml</code>

==== Suggesting past input ====

The autocompletion mechanism has the following typical control flow:
# The main entry point is the global '''<code>@mozilla.org/satchel/form-fill-controller;1</code>''' service implemented in <code>nsFormFillController.cpp</code>.
# All <code><browser></code> elements with an <code>autocompletepopup</code> attribute, at the time of the <code>pageshow</code> event, call <code>nsIFormFillController.attachToBrowser</code> on the global service.
# When an input field raises the <code>focus</code> event, <code>nsFormFillController::Focus</code> checks if autocompletion should be enabled, in which case it registers the input field with the global '''<code>@mozilla.org/autocomplete/controller;1</code>''' service, and starts forwarding input events to <code>nsIAutoCompleteController</code>.
#* The <code>nsFormFillController::GetSearchAt</code> method returns <code>form-history</code>, indicating that searches should be handled by the '''<code>@mozilla.org/autocomplete/search;1?name=form-history</code>''' global service, which is the same service implemented in <code>nsFormFillController.cpp</code>.
# At this point, typically while typing, <code>nsAutoCompleteController::HandleText</code> starts searches by calling the <code>nsFormFillController::StartSearch</code> method.
#* Note that the <code>nsIAutoCompleteInput.searchParam</code> getter of the same global service provides one of the parameters of the function.
# The <code>StartSearch</code> method dispatches the call through <code>autoCompleteSearch</code> or <code>autoCompleteSearchAsync</code> to either:
#* '''Login Manager''', through the global '''<code>@mozilla.org/login-manager;1</code>''' service.
#* '''Form History''', through the global '''<code>@mozilla.org/satchel/form-autocomplete;1</code>''' service.
# When the result is available, <code>nsFormFillController.cpp</code> invokes the <code>nsAutoCompleteController::OnSearchResult</code> method.
#* This stores the result in the global service implemented in <code>nsAutoCompleteController.cpp</code>.
#* This calls <code>nsIAutoCompletePopup.invalidate</code>, and also indirectly <code>nsIAutoCompletePopup.openAutocompletePopup</code>, on the entry returned by <code>nsFormFillController::GetPopup</code>, which is the <code>autocompletepopup</code> associated to the browser window.
#** The <code>openAutocompletePopup</code> method is called with a reference to the <code>nsIAutoCompleteInput</code> corresponding to the global service implemented in <code>nsFormFillController.cpp</code>.
# The <code>nsIAutoCompletePopup</code> interface will display the popup and handle its input.
#* This may cause the actual calls to be routed through IPC in case the interface is invoked in a child process.
# In response to popup events, the contents of the <code>input</code> field are updated.

==== Recording new input ====

When a form is submitted, saving the submitted data is handled by a different mechanism:
# The main entry point is the global '''<code>@mozilla.org/satchel/form-history-startup;1</code>''' service implemented in <code>FormHistoryStartup.js</code>.
# This registers the global <code>formSubmitListener.js</code> content script for all browsers.
# Form submissions monitored by the content script are translated into <code>FormHistory.jsm</code> calls to update the stored data.

=== Bug list ===

* {{bug|1009935}} - Implement the @autocomplete attribute for values other than off/on
* {{bug|939351}} - Implement requestAutocomplete backend
* {{bug|946022}} - Implement requestAutocomplete for Firefox for Android
* {{bug|990367}} - requestAutocomplete UI for Firefox desktop
* {{bug|998077}} - Sync support for autofill data
* {{bug|1007176}} - Implement requestAutocomplete on donate.mozilla.org
* {{bug|1007181}} - Project Review: requestAutoComplete on donate.mozilla.org

== References ==

* [https://etherpad.mozilla.org/requestautocomplete requestAutocomplete Etherpad]
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#autofill WHATWG Autofill specification work]
* [https://www.w3.org/Bugs/Public/buglist.cgi?component=HTML&list_id=34802&product=WHATWG&resolution=---&short_desc=autocomplete&short_desc_type=allwordssubstr WHATWG Autofill specification bug list]
* [https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DUI-Browser-Autofill-Interactive Chromium Autofill implementation bug list]
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=10261611&classification=Components&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=Form%20Manager&product=Toolkit Form Manager bug list]
* [https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion MDN documentation mentioning form autocompletion]

User:P.A./Form user experience improvements

2014-05-28T16:46:34Z

P.A.: Add bug references

User:P.A./Form user experience improvements

2014-05-28T15:42:22Z

P.A.: Add references

User:P.A./Form user experience improvements

2014-05-28T14:19:35Z

P.A.: Add comparison of strategies

User:P.A./Form user experience improvements

2014-05-28T14:00:17Z

P.A.: Add approaches

User:P.A./Form user experience improvements

2014-05-28T13:21:15Z

P.A.: Add benefits and edit themes

User:P.A./Form user experience improvements

2014-05-28T11:56:16Z

P.A.: Add general themes

User:P.A./Form user experience improvements

2014-05-28T10:40:58Z

P.A.: Create page with general overview

Buildbot/Talos/Tests

2014-04-15T19:45:18Z

P.A.: /* xperf */ Clarify that it currently tests startup I/O regressions only

= Talos Tests =

== Where to get this information ==

* Talos tests are defined in http://hg.mozilla.org/build/talos/file/tip/talos/test.py
* TBPL abbreviations are defined in http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/tip/js/Config.js#l302
* [http://graphs.mozilla.org/ Perf-o-matic] names are defined in http://hg.mozilla.org/graphs/file/tip/sql/data.sql
* Talos suites are configured for production in http://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla-tests/config.py; these names are mapped to TBPL via regexes: http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/file/e2e344885c80/js/Data.js#l512
* Inline help is available by running ''talos --print-tests'' to get a list of all tests and their descriptions. To get help on a subset of tests, including their run-time parameters, use e.g. ''talos --print-tests -a ts:tsvg [options]''

A table detailing information flow from buildbot to talos to TBPL and graphserver is available at http://k0s.org:8080/ . This is generated with the [http://k0s.org/mozilla/hg/talosnames talosnames] script, as detailed in http://k0s.org/mozilla/blog/20120724135349 . See also {{bug|770460}}.

== Talos Test Types ==

There are two different species of Talos tests:

* [[#Startup Tests]] : start up the browser and wait for either the load event or the paint event and exit, measuring the time
* [[#Page Load Tests]] : load a manifest of pages

=== Startup Tests ===

[http://hg.mozilla.org/build/talos/file/tip/talos/startup_test Startup tests] launch Firefox and measure the time to the onload or paint events. Firefox is invoked with a URL to:

* http://hg.mozilla.org/build/talos/file/tip/talos/startup_test/startup_test.html for the onload event
* http://hg.mozilla.org/build/talos/file/tip/talos/startup_test/tspaint_test.html for the paint event

=== Page Load Tests ===
Many of the talos tests use the page loader to load a manifest of pages.
These are tests that load a specific page and measure the time it takes to load the page, scroll the page, draw the page etc. In order to run a page load test, you need a manifest of pages to run. The manifest is simply a list of URLs of pages to load, separated by carriage returns, e.g.:
<pre>
http://www.mozilla.org
http://www.mozilla.com
</pre>
Example: http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/svg/svg.manifest

Manifests may also specify that a test computes its own data by prepending a <tt>%</tt> in front of the line:
<pre>
% http://www.mozilla.org
% http://www.mozilla.com
</pre>
Example: http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/v8_7/v8.manifest

The file you created should be referenced in your config file, for example, open sample.config, and look for the line referring to the test you want to run:
<pre>
- name: tp4
url: '-tp page_load_test/tp4.manifest -tpchrome -tpnoisy -tpformat tinderbox -tpcycles 10'
</pre>
* -tp controls the location of your manifest
* -tpchrome tells Talos to run the browser with the normal browser UI active
* -tpnoisy means "generate lots of output"
* -tpformat controls the format of the results, they default to the results we send to displays like [http://graphs.mozilla.org graphserver] and [http://tbpl.mozilla.org tbpl].
* -tpcycles controls the number of times we run the entire test.

=== Paint Tests ===
Paint tests are measuring the time to receive both the [https://developer.mozilla.org/en/Gecko-Specific_DOM_Events#MozAfterPaint MozAfterPaint] and OnLoad event instead of just the OnLoad event.

Currently we run _paint tests for these tests:
* ts_paint
* tpaint
* tp5n
* sunspider
* a11y
* tscroll/tscrollx

=== NoChrome Tests ===

All tests run through the pageloader extension can be run with or without browser chrome. The tests load the same pages as described above in either case. The majority or tests are run with browser chrome enabled. On mobile (native android builds) we have to run everything as nochrome since we don't support additional xul windows.

The ability to run tests without the browser chrome opens up the ability to further isolate performance regressions.

== Test Descriptions ==

=== CanvasMark ===
* contact: :jmaher
* source: https://github.com/kevinroast/CanvasMark
* type: [https://wiki.mozilla.org/Buildbot/Talos#Page_Load_Tests PageLoader]

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|tcanvasmark
|Canvasmark
|
|-
|tcanvasmark_nochrome
|Canvasmark, NoChrome
|see [[#NoChrome Tests]]
|}

These tests run the third-party [http://www.kevs3d.co.uk/dev/canvasmark/ CanvasMark] benchmark suite, which measures the browser's ability to render a variety of canvas animations at a smooth framerate as the scenes grow more complex.

Results are a score "based on the length of time the browser was able to maintain the test scene at greater than 30 FPS, multiplied by a weighting for the complexity of each test type" ('''higher is better''').

=== tp5 ===
* contact: :jmaher
* source: not available
* type: [https://wiki.mozilla.org/Buildbot/Talos#Page_Load_Tests PageLoader]

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|tp5r
|Tp5r MozAfterPaint
|tp5 with responsiveness
|-
|tp5row
|Tp5 Row Major MozAfterPaint
|tp5r running in [https://elvis314.wordpress.com/2012/03/12/reducing-the-noise-in-talos/ Row Major] with 25 cycles/page, ignoring the first 5
|-
|tp5n
|Tp5 No Network Row Major MozAfterPaint
|tp5row with a new tp5.zip that has no 404s and no external network access
|-
|tp5
|Tp5 MozAfterPaint
|Measures the time to load a webpage and receive [[Buildbot/Talos/Tests#Paint_Tests|both a MozAfterPaint and OnLoad event]].
|}

Tests the time it takes Firefox to load the tp5 web page test set. The web set was culled from the Alexa top 500 April 8th, 2011 and consists of 100 pages.

Unfortunately, we do not distribute a copy of the set of test web pages as these would not constitute fair use. Here are the broad steps we use to create the test set:
# Take the Alexa top 500 sites list
# Remove all sites with questionable or explicit content
# Remove duplicate site (for ex. many Google search front pages)
# Manually select to keep interesting pages (such as pages in different locales)
# Select a more representative page from any site presenting a simple search/login/etc. page
# Deal with Windows 255 char limit for cached pages
# Limit test set to top 100 pages

Note that the above steps did not eliminate all outside network access so we had to take further action to scrub all the pages so that there are 0 outside network accesses (this is done so that the tp test is as deterministic measurement of our rendering/layout/paint process as possible). If you are on the Mozilla intranet, you can obtain the [http://fs/public/Talos/ current page set] for local testing. DO NOT DISTRIBUTE IT.

==== Private Bytes ====

A memory metric tracked during tp4 test runs. This metric is sampled every 20 seconds.

For windows, a [http://technet.microsoft.com/en-us/library/cc780836%28WS.10%29.aspx description from Microsoft TechNet].

==== RSS (Resident Set Size)====

A memory metric tracked during tp5 test runs. This metric is sampled every 20 seconds. This metric is collected on linux/mac only.

[http://en.wikipedia.org/wiki/Resident_set_size Description from wikipedia].

==== Xres (X Resource Monitoring)====

A memory metric tracked during tp5 test runs. This metric is sampled every 20 seconds. This metric is collected on linux only.

[http://linux.die.net/man/3/xres xres man page].

==== Working Set (tp5_memset) ====

A memory metric tracked during tp5 test runs. This metric is sampled every 20 seconds. This metric is collected on windows only. [http://technet.microsoft.com/en-us/library/cc780836%28WS.10%29.aspx Description from Microsoft TechNet].

==== Modified Page List Bytes ====

A memory metric tracked during tp5 test runs. This metric is sampled every 20 seconds. This metric is collected on Windows7 only. [http://msdn.microsoft.com/en-us/library/aa965225%28VS.85%29.aspx Description from Microsoft MSDN].

==== % CPU ====

Cpu usage tracked during tp5 test runs. This metric is sampled every 20 seconds. This metric is collected on windows only.

==== Responsiveness ====

Reports the delay in milliseconds for the event loop to process a [[Performance/Snappy#Current Infrastructure|tracer event]]. For more details, see {{bug|631571}}.

=== ts_paint ===

* contact: :mak, :jimm, :jmaher
* source: [http://hg.mozilla.org/build/talos/file/tip/talos/startup_test/tspaint_test.html tspaint_test.html]
* Perfomatic: "Ts, Paint"
* type: Startup

Launches tspaint_test.html with the current timestamp in the url, waits for [[Buildbot/Talos/Tests#Paint_Tests|MozAfterPaint and onLoad]] to fire, then records the end time and calculates the time to startup.

The basic ts test uses a blank profile. Formerly known as ts before we looked for the MozAfterPaint event.

==== ts_places_generated_med ====
* contact: :mak, :mattn, :jmaher
* source: [http://hg.mozilla.org/build/talos/file/tip/talos/startup_test/tspaint_test.html tspaint_test.html]
* type: Startup
* dirty: this is also referred to as the dirty test

Runs the same test as ts_paint, but uses a generated profile to simulate what an average user would have. The profile consists of 4 files:
* [[http://hg.mozilla.org/build/talos/file/63e4fcd8784d/talos/places_generated_med/permissions.sqlite permissions.sqlite]] - allowXULXBL in moz_hosts
* [[http://hg.mozilla.org/build/talos/file/63e4fcd8784d/talos/places_generated_med/prefs.js prefs.js]] - these are just prefs to allow script access to chrome
* places.sqlite - updated daily via [[https://hg.mozilla.org/build/tools/file/tip/buildfarm/utils/updateGenerated.py buildbot script]] to have [[http://hg.mozilla.org/build/tools/file/tip/buildfarm/utils/generator/places/builddb/increment_dates.py recent dates]] for these tables:
moz_historyvisit, 111750 items
moz_bookmarks, 1354 items
moz_favicons, 22042 items
moz_annos, 0 items
moz_items_annos, 8 items

other tables which are not updated:
moz_places, 22088 items
moz_keywords, 7 items
moz_anno_attributes, 6 items
moz_bookmarks_roots, 5 items
moz_inputhistory, 342 items

* [[http://hg.mozilla.org/build/talos/file/63e4fcd8784d/talos/places_generated_med/localstore.rdf localstore.rdf]]
** todo: this is outdated

==== ts_places_generated_max ====
* contact: :mak, :mattn, :jmaher
* source: [http://hg.mozilla.org/build/talos/file/tip/talos/startup_test/tspaint_test.html tspaint_test.html]
* type: Startup
* dirty: this is also referred to as the dirty test

Runs the same test as ts_paint, but uses a generated profile to simulate what an average user would have. The profile consists of 4 files:
* [[http://hg.mozilla.org/build/talos/file/63e4fcd8784d/talos/places_generated_med/permissions.sqlite permissions.sqlite]] - allowXULXBL in moz_hosts
* [[http://hg.mozilla.org/build/talos/file/63e4fcd8784d/talos/places_generated_med/prefs.js prefs.js]] - these are just prefs to allow script access to chrome
* places.sqlite - updated daily via [[https://hg.mozilla.org/build/tools/file/tip/buildfarm/utils/updateGenerated.py buildbot script]] to have [[http://hg.mozilla.org/build/tools/file/tip/buildfarm/utils/generator/places/builddb/increment_dates.py recent dates]] for these tables:
moz_historyvisit, 725054 items
moz_bookmarks, 144757 items
moz_favicons, 144705 items
moz_annos, 0 items
moz_items_annos, 8 items

other tables which are not updated:
moz_places, 144751 items
moz_keywords, 601 items
moz_anno_attributes, 6 items
moz_bookmarks_roots, 5 items
moz_inputhistory, 342 items

* [[http://hg.mozilla.org/build/talos/file/63e4fcd8784d/talos/places_generated_med/localstore.rdf localstore.rdf]]
** todo: this is outdated

=== tdhtml ===
* '''turned off on all branches and platforms November 1st, 2012'''
* contact: :peterv, :jmaher
* source: [http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/dhtml dhtml.manifest]
* type: [https://wiki.mozilla.org/Buildbot/Talos#Page_Load_Tests PageLoader]

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|tdhtmlr
|DHTML Row Major
|Row based and 25 cycles/page.
|-
|tdhtml.2
|DHTML 2
|Ignoring the first value instead of the highest (usually the highest is the first)
|}

Tests which measure the time to cycle through a set of DHTML test pages. This test will be updated in the near future.

This test is also ran with the [https://wiki.mozilla.org/Buildbot/Talos#NoChrome_Tests nochrome] option.

=== tsvg, tsvgx ===
* contact: :jwatt, :jmaher, :avih
* source: [http://hg.mozilla.org/build/talos/file/default/talos/page_load_test/svg svg.manifest], [http://hg.mozilla.org/build/talos/file/default/talos/page_load_test/svgx svgx]
* type: PageLoader

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|tsvgx
|SVG-ASAP
|[https://groups.google.com/d/topic/mozilla.dev.platform/RICw5SJhNMo/discussion Replacing tscroll,tsvg with tscrollx,tsvgx]
|-
|svgr
|SVG Row Major
|[https://elvis314.wordpress.com/2012/03/12/reducing-the-noise-in-talos/ Row Major] and 25 cycles/page.
|-
|svg
|SVG
|Column based and 5 cycles.
|}

An svg-only number that measures SVG rendering performance. About half of the tests are animations or iterations of rendering. The ASAP test (tsvgx) iterates in unlimited frame-rate mode thus reflecting the maximum rendering throughput of each test. The reported value is the page load time, or, for animations/iterations - overall duration the sequence/animation took to complete. To turn on ASAP mode, we set these preferences:
preferences = {'layout.frame_rate': 0, 'docshell.event_starvation_delay_hint': 1}

=== tsvg-opacity ===
* contact: :jwatt, :jmaher
* source: [http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/svg svg.manifest]
* type: PageLoader

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|svgr_opacity
|SVG, Opacity Row Major
|[https://elvis314.wordpress.com/2012/03/12/reducing-the-noise-in-talos/ Row Major] and 25 cycles/page.
|-
|svg_opacity
|SVG, Opacity
|Column based and 5 cycles.
|}

An svg-only number that measures SVG rendering performance.

* Note: most of the page load tests measure from before the location is changed, until onload + mozafterpaint, therefore any changes in chrome performance from the location change, or network performance (the pages load from a local web server) would affect page load times. SVG opacity is rather quick by itself, so any such chrome/network/etc performance changes would affect this test more than other page load tests (relatively, in percentages).

=== tpaint ===
* contact: :jimm, :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/e2dd770e2d4c/talos/startup_test/tpaint.html tpaint-window.html]]
* type: Startup

{| cellspacing="1" cellpadding="1" border="1"
|-
|Talos test name
|Graphserver name
|Description
|-
|tpaint
|Paint
|twinopen but measuring the time after we receive the [[Buildbot/Talos/Tests#Paint_Tests|MozAfterPaint and OnLoad event]].
|-
|twinopen
|
|original test to measure the time to open window based on OnLoad event.
|-
|txul
|Txul
|another name for twinopen. Also we report txul in the regression emails.
|}

Tests the amount of time it takes the open a new window. This test does not include startup time. Multiple test windows are opened in succession, results reported are the average amount of time required to create and display a window in the running instance of the browser. (Measures ctrl-n performance.)

=== JSS/Domaeo Tests ===

Dromaeo suite of tests for JavaScript performance testing. See the [https://wiki.mozilla.org/Dromaeo Dromaeo wiki] for more information.

This suite is divided into several sub-suites.

==== Dromaeo CSS ====
contact: :dmandelin, :jmaher
source: [[http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/dromaeo css.manifest]]
type: PageLoader
reporting: speed in test runs per second (higher is better)

Each page in the manifest is part of the dromaemo css benchmark.

==== Dromaeo DOM ====
contact: :dmandelin, :jmaher
source: [[http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/dromaeo dom.manifest]]
type: PageLoader
reporting: speed in test runs per second (higher is better)

Each page in the manifest is part of the dromaemo css benchmark.

=== a11y ===
* contact: :davidb, :tbsaunde, :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/a11y a11y.manifest]]
* type: PageLoader
* measuring: ???
* reporting: test time in ms (lower is better)

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|a11yr
|a11y Row Major MozAfterPaint
|[https://elvis314.wordpress.com/2012/03/12/reducing-the-noise-in-talos/ Row Major] testing with 25 cycles per page
|-
|a11y.2
|a11y 2 MozAfterPaint
|same as a11y ignoring the first value collected instead of the largest
|-
|a11y
|a11y MozAfterPaint
|iterate through each page, 5 cycles through the list, ignore the highest value from each page
|}

This test ensures basic a11y tables and permutations do not cause performance regressions.

=== tscroll, tscrollx ===
* contact: :jrmuizel, :jmaher, :avih
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/scroll scroll.manifest]]
* type: PageLoader
* measuring: Scroll performance
* reporting: Average frame interval (1/FPS). Lower is better.

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|tscrollx
|tscroll-ASAP MozAfterPaint
|[https://groups.google.com/d/topic/mozilla.dev.platform/RICw5SJhNMo/discussion Replacing tscroll,tsvg with tscrollx,tsvgx]
|-
|tscrollr
|tscroll Row Major
|[https://elvis314.wordpress.com/2012/03/12/reducing-the-noise-in-talos/ Row Major] testing with 25 cycles
|-
|tscroll.2
|tscroll 2
|Ignore the first value for each page instead of the largest
|-
|tscroll
|tscroll
|run through each page in the manifest and cycle 5 times. For each page, ignore the largest value
|}

This test scrolls several pages where each represent a different known "hard" case to scroll (* needinfo), and measures the average frames interval (1/FPS) on each. The ASAP test (tscrollx) iterates in unlimited frame-rate mode thus reflecting the maximum scroll throughput per page. To turn on ASAP mode, we set these preferences:
preferences = {'layout.frame_rate': 0, 'docshell.event_starvation_delay_hint': 1}

=== tresize ===
* contact: :jimm, :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/6d1c5ee867e6/talos/startup_test/tresize-test.html tresize-test.html]]
* type: StartupTest
* measuring: Time to do XUL resize, in ms (lower is better).
* reporting: ???

{| cellspacing="1" cellpadding="1" border="1"
|-
| Talos test name
| Graphserver name
| Description
|-
|tresize
|tresize
|TODO
|}

A purer form of paint measurement than tpaint. This test opens a single window positioned at 10,10 and sized to 300,300, then resizes the window outward |max| times measuring the amount of time it takes to repaint each resize. Dumps the resulting dataset and average to stdout or logfile.

=== xperf ===
* contact: :taras, :aklotz, :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/xtalos xperf instrumentation]]
* type: Pageloader (tp5n) / Startup
* measuring: IO counters from windows (currently, only startup IO is in scope)
* reporting: Summary of read/write counters for disk, network (lower is better)

Talos will turn orange for 'x' jobs on windows 7 if your changeset accesses files which are not predefined in the [[http://hg.mozilla.org/build/talos/file/ae09eb897102/talos/xtalos/xperf_whitelist.json whitelist]]. If your job turns orange, you will see a list of files in tbpl (or in the log file) which have been accessed unexpectedly (similar to this):
* TEST-UNEXPECTED-FAIL : xperf: File '{profile}\secmod.db' was accessed and we were not expecting it. DiskReadCount: 6, DiskWriteCount: 0, DiskReadBytes: 16904, DiskWriteBytes: 0
* TEST-UNEXPECTED-FAIL : xperf: File '{profile}\cert8.db' was accessed and we were not expecting it. DiskReadCount: 4, DiskWriteCount: 0, DiskReadBytes: 33288, DiskWriteBytes: 0
* TEST-UNEXPECTED-FAIL : xperf: File 'c:\$logfile' was accessed and we were not expecting it. DiskReadCount: 0, DiskWriteCount: 2, DiskReadBytes: 0, DiskWriteBytes: 32768 TEST-UNEXPECTED-FAIL : xperf: File '{profile}\secmod.db' was accessed and we were not expecting it. DiskReadCount: 6, DiskWriteCount: 0, DiskReadBytes: 16904, DiskWriteBytes: 0
* TEST-UNEXPECTED-FAIL : xperf: File '{profile}\cert8.db' was accessed and we were not expecting it. DiskReadCount: 4, DiskWriteCount: 0, DiskReadBytes: 33288, DiskWriteBytes: 0
* TEST-UNEXPECTED-FAIL : xperf: File 'c:\$logfile' was accessed and we were not expecting it. DiskReadCount: 0, DiskWriteCount: 2, DiskReadBytes: 0, DiskWriteBytes: 32768

In the case that these files are expected to be accessed during startup by your changeset, then we can add them to the [[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos whitelist]].

Xperf runs tp5 while collecting xperf metrics for disk IO and network IO. The providers we listen for are:
* [http://hg.mozilla.org/build/talos/file/tip/talos/xperf.config#l10 ['PROC_THREAD', 'LOADER', 'HARD_FAULTS', 'FILENAME', 'FILE_IO', 'FILE_IO_INIT']]

The values we collect during stackwalk are:
* [http://hg.mozilla.org/build/talos/file/tip/talos/xperf.config#l11 ['FileRead', 'FileWrite', 'FileFlush']]

=== kraken ===
* contact: :dmandelin, :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/kraken kraken.manifest]]
* type: [https://wiki.mozilla.org/Buildbot/Talos#Page_Load_Tests PageLoader]
* measuring: JavaScript performance
* reporting: Total time for all tests, in ms (lower is better)
* Perfomatic name: Kraken Benchmark MozAfterPaint

This is the [[Kraken]] javascript benchmark taken verbatim and slightly modified to fit into our pageloader extension and talos harness.

=== V8, version 7===
* contact: :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/v8_7 v8.manifest]]
* type: PageLoader
* measuring: ???
* reporting: weighted score (higher is better)
* Perfomatic name: V8 version 7 MozAfterPaint

this is the V8 (version 7) javascript benchmark taken verbatim and slightly modified to fit into our pageloader extension and talos harness.

The previous version of this test is V8 version 5 which was run on selective branches and operating systems.

=== TART/CART ===
* contact: :avih, :jmaher, :MattN
* source: [http://hg.mozilla.org/build/talos/file/tip/talos/page_load_test/tart tart]
* type: PageLoader
* measuring: Desktop Firefox UI animation speed and smoothness
* reporting: intervals in ms (lower is better) - see below for details
* Perfomatic name: Tab Animation Test, Customization Animation Tests

TART is the '''Tab Animation Regression Test''' and CART is the '''Customize Animation Regression Test'''.

TART tests tab animation on these cases:
* Simple: single new tab of about:blank open/close without affecting (shrinking/expanding) other tabs.
* icon: same as above with favicons and long title instead of about:blank.
* Newtab: newtab open with thumbnails preview - without affecting other tabs, with and without preload.
* Fade: opens a tab, then measures fadeout/fadein (tab animation without the overhead of opening/closing a tab).
** Case 1 is tested with DPI scaling of 1.
** Case 2 is tested with DPI scaling of 1.0 and 2.0.
** Case 3 is tested with the default scaling of the test system.
** Case 4 is tested with DPI scaling of 2.0 with the "icon" tab (favicon and long title).
** Each animation produces 3 test results:
*** error: difference between the designated duration and the actual completion duration from the trigger.
*** half: average interval over the 2nd half of the animation.
*** all: average interval over all recorded intervals.

CART uses the same framework to measure performance of the Australize "customize" animation (for entering the toolbar/menu customization view). Subtests include:
* Customize-enter animation (full and css-animation-only part).
* Customize-exit animation

TART/CART can be used as a stand-alone addon:
* Set the browser to ASAP mode (preferences layout.framerate=0, docshell.event_starvation_delay_hint=1). This makes the browser refresh the screen as fast as possible instead of limiting it to 60hz, thus allows higher resolution measurements. Requires restart to take effect.
* Zip the addon dir of the source code and rename the extension to xpi.
* Install the addon xpi and restart the browser.
* Visit chrome://tart/content/tart.html
* Select subtests to run. By default the selected tests are all the TART tests. CART is the "Customize" test.

=== Robocop ===

[[Auto-tools/Projects/Robocop|Robocop]] is Mozilla's Android test framework based on [http://robotium.org Robotium]. In addition to functional/unit tests, there are several robocop performance tests run by Talos.

; Robocop Checkerboarding Real User Benchmark (tcheck2/trobocheck2/rck2)
: "Checkerboard" refers to cases where we can't render new portions of a page as fast as a user scrolls to them, and so they see a blank area, low-resolution rendering, or a checkerboard pattern as they scroll. This test is designed to stress the browser. It uses a real-world test page, scrolls in all directions, and also zooms the page in various ways. Reports the '''average percentage of the screen that is "checkerboarded"''' over time (lower is better). [http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/testCheck2.java.in (source)]
; Robocop Pan Benchmark (robopan/trobopan/rp)
: This test measures "jank" during scrolling. It scrolls down a page repeatedly, and records each "missed" frame (any frame drawn more than 1/40 sec after the previous frame). For each missed frame, it calculates how much it was delayed past 1/40 second. The test reports the '''sum of the squares of the delays for all missed frames''' (lower is better). [http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/testPan.java.in (source)]
; Robocop Database Benchmark (roboprovider/troboprovider/rpr)
: This test measures the performance of the history and bookmarks ContentProvider database in Firefox for Android. It performs several database operations and reports the '''time to complete the operations, in milliseconds''' (lower is better). [http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/testBrowserProviderPerf.java.in (source)]

See also:
* [[Mobile/Fennec/Android#Testing]]
* [http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/tests/ Source code for Robocop tests]

=== Other data ===

These are not part of the Talos code, but like Talos they are benchmarks that record data using the graphserver and are analyzed by the same scripts for regressions.

==== Number of Constructors (num_ctors) ====

This test runs at build time and measures the number of static initializers in the compiled code. Reducing this number is helpful for [https://blog.mozilla.org/tglek/2010/05/27/startup-backward-constructors/ startup optimizations].

* https://hg.mozilla.org/build/tools/file/348853aee492/buildfarm/utils/count_ctors.py

==== Codesighs ====

Codesighs measures the size of the compiled libraries and executables. Runs on Linux and Mac at build time, triggered by the --enable-codesighs configure flag.

For details see [[Codesighs]].

==== Trace Malloc ====

This test is run as part of the "make leaktest" step during debug build jobs. It uses the [[Performance:Leak_Tools#Trace-malloc|trace-malloc]] tool from [http://mxr.mozilla.org/mozilla-central/source/tools/trace-malloc/ tools/trace-malloc] to wrap calls to malloc and log information about every memory allocation. See also [http://mxr.mozilla.org/mozilla-central/source/build/leaktest.py.in leaktest.py].

* trace_malloc_leaks
* trace_malloc_maxheap
* trace_malloc_alloc

Snappy/Promises unification

2014-02-27T15:50:46Z

P.A.: Create page with description of Promises unification

== Current situation ==

As of March 2013, we have three libraries implementing the JavaScript Promise object, used in production code:
* Add-on SDK Promises
* Promise.jsm
* DOM Promises

Promises are becoming an important part of interfaces in production code, and interoperability between these different implementations is becoming a concern as those have subtle differences or relevant limitations.

It is therefore important to reach a point where we don't pay the maintenance cost of different implementations across all the products.

== Unification plan ==

With the stabilization of the DOM/ES6 Promises specification in late January 2013 for the subset of functionality that we need, we can now identify the DOM Promises implementation as the final migration target. This implementation, however, has a number of limitations over Promise.jsm, related to debuggability. In order of importance:

* {{bug|966452}} - DOM Promises should report all unhandled rejections to the Console on GC
* {{bug|966471}} - DOM Promise state, value and reason should be inspectable in the debugger
* {{bug|966472}} - DOM Promise handlers should be inspectable in the debugger

Since Promise.jsm currently implements a subset of the DOM Promises interface and behaves in the same way as far as code is concerned, then migration to Promise.jsm is an appropriate intermediate step. The major work is related to porting the Add-on SDK Promises, in particular these bugs are on file:
* {{bug|887923}} - Switch Task.jsm to use Promise.jsm
* {{bug|881050}} - Use the new "Promise.jsm" implementation in Developer Tools

The sooner we complete the migration, the less new code will be written that depends on behavior that is incorrect according to the specification.

== Immediate goals ==

Unification towards DOM Promises can proceed on two parallel tracks:
# Remove all uses of Add-on SDK Promises from mozilla-central
# Implement new DOM Promises features, then migrate Promise.jsm to use DOM Promises internally

The first goal is the most important, to be ideally completed in a short time. The last step after both have completed would be to deprecate Promise.jsm and migrate all callers to directly use DOM Promises.

The overall Promises work is tracked in [https://bugzilla.mozilla.org/showdependencytree.cgi?id=856878&hide_resolved=1 bug 856878].

Firefox/Meeting/Template

2013-10-15T17:24:23Z

P.A.: /* Project Updates */ Downloads API project is now completed

Firefox/Meeting/15-Oct-2013

2013-10-15T17:23:30Z

P.A.: /* Downloads API */ Add update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/10:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
== Project Updates ==
===Australis===
* More performance stuff!
** We've determined that switching to SVG curves and putting the linear-gradient into the active tab stroke image will put Windows XP in the black WRT TART. \o/ Patches en route (but partially blocked on shorlander for graphics assets for lw-themes)
** We've determined that the slowdown for OS X 10.6 is caused by the GPU taking longer to composite things when we have the tabs drawn in the titlebar. mconley is going to try to use Xcode's OpenGL Profiler to determine what we're waiting for.
* Improvements to Linux theming.
* Recent tabs/windows added to the history widgets
* Drag improvements in customize mode
* Improved handling of wide widgets in the menu panel
* Improved panel layouts
* Improved styling of combined buttons

===Downloads API===
* Reduce maintenance and support surface by locking the Downloads API activation preference in place

===Thumbnailing===
'''Foreground thumbnailing'''

* WIP patch awaiting Tim's feedback: {{Bug|809056}} - reduce thumbnailing impact when there are no thumbnail service consumers
* putting on hold for now, until graphics people are able to work on it: improving canvas.drawWindow() performance

'''Background thumbnailing'''

* resolving goal as complete: ensure minimal resource usage by background thumbnail service
* profiled I/O, network usage, results are good: {{Bug|899848}} - Ensure minimal disk io caused by background thumbnailing
* looking at remaining e10s-related crashes before finally enabling background thumbnail service on Beta and release channels
* landed: {{Bug|924651}} - BackgroundPageThumbs should log crashes as a telemetry completion reason
* landed: {{Bug|924665}} - BackgroundPageThumbs captures can finish twice
* trying to reproduce on try server: {{Bug|917517}} - Intermittent browser_thumbnails_background_crash.js | dumpID is present and not an empty string
* trying to find reduced test case for strange OS.File behavior: {{Bug|909933}} - Intermittent browser_thumbnails_update.js | thumbnail is still green - Got 255,0,0, expected 0,255,0

===SessionStore===
* A few code cleanups ({{bug|923034}}, {{bug|923854}}).
* Fix a rather rare regression for windows quickly opened at startup ({{bug|900910}}).
* Fixing lost windows due to ID collisions ({{bug|925771}}).
* Ensure write instructions after shutdown will be prevented ({{bug|922785}}, {{bug|922814}})
* Remove synchronous startup code ({{bug|918024}}).
* Still working to get rid of saving state right after startup ({{bug|887780}}, {{bug|921581}}).
* Marionette tests for startup path are coming along
* Work to collect more data in content scripts to be e10s friendly ({{bug|909048}}, {{bug|910668}}, {{bug|919835}}).

===Places API asyncification===
* dependencies blocking async transaction manager got reviewed, meeting tomorrow to discuss current status of the remaining patches.
* Raymond attached new patch to do async queries in bookmarks backups, reviewing it.
* Backups hash comparison blocked due to a test failure, investigation ongoing.
* Investigated url index replacement through the hashing functions in mfbt, still really early wip.

===Social API===
===e10s===

* Summit sessions | mini work week
* {{bug|897061}} Autocomplete
* {{bug|919835}} Session Restore
* {{bug|921935}} {{bug|925058}} Focus manager

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Firefox/Meeting/1-Oct-2013

2013-10-01T17:03:15Z

P.A.: No Downloads API update!

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/10:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==

* GSoC update: Google Summer of Code 2013 has now finished. [http://felipe.wordpress.com/2013/10/01/gsoc2013-completed/ Felipe's blog post] and [http://trystswithcode.quora.com/In-the-name-of-numbers phenom's post].

== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
== Project Updates ==
===Australis===
* Last week was a great week, performance-wise.
** The URL bar merge caused a regression because of a CSS rule that wasn't specific enough, which made the back button enable / disable when tab closing. This got fixed in {{bug|916946}}.
** We were transitioning the opacity of tabs being closed even though they're not supposed to be visible in the first place. This got fixed in {{bug|919541}}
** We're going to try moving the linear-gradient texture from CSS into the stroke image, which should save us some time as well. This is in bug {{bug|921038}}.
** We're going to try switching our curve background drawing from clip-paths to SVG curves. Coupled with SVG caching ({{bug|764299}}), this has the potential to wipe out our Windows TART regressions. This is being investigated in {{bug|921051}}.
** We've begun re-orienting our investigations to OS X, since we're still regressing TART there a bit (~7% on 10.6).
** More details are in [https://mail.mozilla.org/pipermail/firefox-dev/2013-September/000989.html the weekly Australis Performance Report] that mconley posted to firefox-dev.

===Thumbnailing===
'''Foreground thumbnailing'''

* WIP patch awaiting Tim's feedback: {{Bug|809056}} - reduce thumbnailing impact when there are no thumbnail service consumers
* reopened: {{Bug|880026}} - Intermittent browser_thumbnails_storage_migrate3.js | Test timed out | uncaught exception - ReferenceError: executeSoon is not defined

'''Background thumbnailing'''

* landed: {{Bug|920676}} - Firefox Beta (25) release notes should not include "Blank or missing page thumbnails when opening a new tab"
* patched but still investigating orange: {{Bug|909933}} - Intermittent browser_thumbnails_update.js | thumbnail is still green - Got 255,0,0, expected 0,255,0
* patch for review: Bug 917517 - Intermittent browser_thumbnails_background_crash.js | dumpID is present and not an empty string
* still awaiting Tim's review: {{Bug|910036}} - about:newtab shouldn't load thumbnails in background when hidden by preloader
* new, appears to be e10s problem: {{Bug|921173}} - Intermittent browser_thumbnails_background_crash.js | application timed out after 330 seconds with no output

===SessionStore===
* Remove synchronous startup code ({{bug|918024}}).
* Getting the crash monitor landed to get rid of saving state right after startup ({{bug|887780}}, {{bug|921581}}).
* Fix a rather rare regression for windows quickly opened at startup ({{bug|900910}}).
* Collecting data mostly in content scripts and make it work with e10s ({{bug|910646}}, {{bug|909048}}, {{bug|910668}}, {{bug|919835}}).
* Small regression when restarting in safe-mode ({{bug|919532}}).
* A couple of smaller issues fixed that were spotted lately ({{bug|921311}}, {{bug|921870}}, {{bug|921310}}).
* Started working on marionette tests to test our startup paths.

===Places API asyncification===
===Social API===
===e10s===

* Content zoom work in progress: {{bug|691614}}
* SessionStore: e10s style sessionstore landed {{bug|894595}} and wip for sessionstore using cpows {{bug|919835}}
* Browser-chrome tests: Passed: 3079 Failed: 240 Todo: 86
* Crashes: {{bug|920397}}

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Firefox/Meeting/24-Sep-2013

2013-09-24T16:59:50Z

P.A.: /* Downloads API */ Done!

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/10:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
* Akshat Kedia for their work on {{bug|914806}} and {{bug|895429}}
* The MSU students are working hard on widget add-ons for Australis. Follow along at their blogs at http://ericproper.blogspot.com/, http://slenkeri.wordpress.com/, and http://weeblwobble.blogspot.com/

== Project Updates ==
===Australis===
* Notable bugs fixed within the past week:
** {{bug|881905}} - Can't drag Facebook button to main customization palette
** {{bug|881905}} - Make Downloads Panel anchor to the chevron if it is overflowed
** {{bug|885086}} - Overflow panel looks kinda wild when wide items get in there
** {{bug|868640}} - Implement private browsing indicator
** {{bug|916735}} - Add a pref to disable animation when entering/exiting customization mode (Improved run time of tests by 30%!)
** {{bug|919541}} - Consider not animating the opacity for Australis tabs
*** [from mconley] This seemed to cut our total regression by over 37.9% on XP. We started with a total TART regression in the neighbourhood of 6.35%, and ended up with a total TART regression of 3.94%
** {{bug|885579}} - Narrow widgets dropped on a wide widget should place the narrow widget above the wide widget

* Landing blockers (outside of perf tracking):
** {{bug|874674}} - Clean up menu panel icons for Linux GTK theme
** {{bug|875479}} - Australis toolbar buttons for Linux
** {{bug|916953}} - Bookmarks button in overflow panel looks broken

* Net bug changes
** P1: -4 (was 10, now 6)
** P2: -2 (was 17, now 15)

===Downloads API===

'''[https://mail.mozilla.org/pipermail/firefox-dev/2013-September/000982.html Done!]'''

===Thumbnailing===
'''Foreground thumbnailing'''

* WIP patch awaiting Tim's feedback: {{Bug|809056}} - reduce thumbnailing impact when there are no thumbnail service consumers

'''Background thumbnailing'''

* landed: {{Bug|919438}} - Disable browser_thumbnails_background_crash.js in non-crashreporter builds
* landed: {{Bug|915384}} - Intermittent ASAN browser_thumbnails_background.js,browser_thumbnails_update.js,browser_thumbnails_background_crash.js | This test exceeded the timeout threshold.
* landed: {{Bug|917610}} - backgroundPageThumbsContent.js's use of nsIDOMWindowUtils.preventFurtherDialogs doesn't work as expected
* landed: {{Bug|917609}} - browser_thumbnails_background.js noAlert test should catch window.alert exception
* investigating: {{Bug|909933}} - Intermittent browser_thumbnails_update.js | thumbnail is still green - Got 255,0,0, expected 0,255,0
* new: {{Bug|917659}} - localStorage not isolated for background thumbnail captures
* new: {{Bug|917517}} - Intermittent browser_thumbnails_background_crash.js | dumpID is present and not an empty string
* new: {{Bug|919467}} - Dig into why browser_thumbnail_background_crash test is disabled on ASan builds
* new: {{Bug|919096}} - Intermittent ASAN TEST-UNEXPECTED-FAIL | browser_thumbnails_background.js | Second file should exist after capture | [Exception... "Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) | Test timed out | and more
* new: {{Bug|919068}} - Intermittent ASAN TEST-UNEXPECTED-FAIL | browser_thumbnails_background.js | Thumbnail for {original,final} URL should be cached
* new: {{Bug|919305}} - Intermittent ASAN browser_thumbnails_background.js | [Exception... "Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) and more

===SessionStore===
* Async data collection got backed out but re-landed next day. No problems so far. ({{bug|894595}})
* Work on cookie collection regression still going on. ({{bug|912717}})
* Proposal to remove sync fallbacks is looking good. ({{bug|918024}})
* Global value API should also be close to landing. ({{bug|899213}})
* :billm worked on moving more data collection to content scripts. ({{bug|910668}} and {{bug|909048}})
* :billm wrote another patch to make SessionStore work in e10s using CPOWs. ({{bug|919835}})

===Places API asyncification===
===Social API===

last week:

* re-landed 3 of 4 backed out patches last week (the fabulous Monday uplift), bug 914435 still needs a little work to validate my theory (to myself at least) that it was an e10s related crash.
* good set of meetings with mconnor, boriss and others to start process of next round of work on socialapi
* planning with talkilla group on a bunch of stuff. e10s/frameworker a major problem for a limited user test in Q1
* biz-dev meetings

this week:

* work on outline for long term architecture goals for social
* documentation
* bug fixes (first up bug 914435 and bug 919803
* any summit prep

===e10s===

* Findbar follow-ups being fixed
* FullZoom in progress {{bug|691614}}
* Mark looking into browser chrome tests and e10s crashes

=== UX Updates ===
* By the way, if you're wondering who the UX people are, they're these guys: https://etherpad.mozilla.org/ux-team-intro-bios
* Some of us are working on prototype projects called "cupcakes," which can be seen here: http://cupcake-dashboard.paas.allizom.org/projects
** If any engineers are interested in any of these, please contact any of the UX people in the etherpad above
* Most of UX will be in Belgium for Summit. Our sessions are here: https://etherpad.mozilla.org/ux-summit-sessions

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Features/Desktop/Downloads API

2013-09-24T14:20:14Z

P.A.:

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Landed
|Feature status=In progress
|Feature version=Firefox 26
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
|Feature implementation notes===== Bugs list and patch queue ====

'''Feature tracking bug:'''

* {{bug|825588}} (covers work across all Mozilla products)

'''Key implementation bugs:'''

* {{bug|847863}}: Use the JavaScript API instead of nsIDownloadManager as the back-end for the panel.

'''Additional steps needed to test the feature:'''

* In Firefox 25, the feature can be enabled by toggling the <code>browser.download.useJSTransfer</code> preference and restarting.
** ''This is only useful for early testing by add-on developers, as the feature is not ready in Firefox 25.''
* In Firefox 26, the feature is enabled by default.

'''Work required to release and enable the feature for everyone:'''

* Work is completed and the feature is now enabled.
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature list=Desktop
|Feature project=Responsiveness
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Firefox/Meeting/17-Sep-2013

2013-09-17T17:08:43Z

P.A.: /* Downloads API */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/10:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''

* Luís Miguel (aka Quicksaver) for reviewing, testing and providing feedback on all the findbar bugs that we've been working on the past couple of months!

== Project Updates ==
===Australis===
* We've backfilled the TART performance data for Windows XP going back to about mid-April, and dumped it into Datazilla (thanks jmaher!).
** [https://datazilla.mozilla.org/?start=1374858213&stop=1379431813&product=Firefox&repository=Firefox&os=win&os_version=5.1.2600&test=tart&compare_product=Firefox&compare_repository=UX&project=talos The graphs paint a pretty interesting tale.] Green is m-c, purple is UX. Each graph that you're looking at is one of the subtests for TART. These graphs just came in, so we're still verifying their accuracy.
* We've identified a m-c merge changeset that caused a regression across the board for UX, but didn't seem to affect m-c. See {{bug|916859}}. Now the challenge is to determine *which* changeset in that merge caused the problem. Mike is going to chat with graphics and layout to see if they can point out any obvious culprits to try backing out. Failing that, manual bisection - which is going to be a real trick, since we'll need to merge from UX every time.

===Downloads API===
Current:
* Development finished
* Landing features for the first Aurora build
Next:
* Fix intermittent failures
* Downloads Panel and Library front-end update
* Decommission <tt>nsIDownloadManager</tt>

===Thumbnailing===
'''Foreground thumbnailing'''

* fixed in {{bug|906615}} (below): {{Bug|809051}} - Limit how often we thumbnail the page using the foreground service
* WIP patch: {{Bug|809056}} - reduce thumbnailing impact when there are no thumbnail service consumers

'''Background thumbnailing'''

* landed: {{Bug|912763}} - Disable background thumbnails on Beta
* landed: {{Bug|906615}} - Background thumbnail service shouldn't overwrite existing thumbnails, or at least foreground thumbnails should be preferred
* landed: {{Bug|910563}} - gracefully handle remote process crashing
* landed: {{Bug|898156}} - crash in Background thumbnail generation @ mozilla::net::FTPChannelParent::OnStartRequest
* landed: {{Bug|913171}} - Intermittent browser_thumbnails_background.js | Captured URL should be currently expected URL
* resolved invalid: {{Bug|903840}} - Requests from BackgroundPageThumbs service show up in devtools panels
* resolved WFM due to {{bug|875986}}: {{Bug|908962}} - Investigate using bypass-history and -cache load flags in background thumbnail browser
* making progress: {{Bug|896912}} - Investigate test failures muted by bug 892875
* new: {{Bug|916497}} - Intermittent TEST-UNEXPECTED-FAIL | browser_thumbnails_redirect.js | Test timed out
* new: {{Bug|915384}} - Intermittent ASAN browser_thumbnails_background.js,browser_thumbnails_update.js

===SessionStore===
===Places API asyncification===
* Little progress across the board: Some undo-manger work is in review stage. Raymond updates his patch for Bug 887043 to support GUIDs - that's also waiting for review. Marco is planning to all of these reviews done in the next couple of days.

===Social API===
* some important bug fixes backed out (914435, 904104, 914927, 914926), need to re-land, one has strings
* in SF this week for socialapi and talkilla meetings

===e10s===

* {{bug|666816}} - Find bar
* {{bug|913155}} - Submit crash reports
* {{bug|910436}} - Helper App Service
* {{bug|910523}} - Intermittent prob in about:home fixed
* Markh is investigating running browser-chrome tests with e10s
* Tom Schuster internship presentation on Thursday 1pm PDT

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Firefox/Meeting/10-Sep-2013

2013-09-10T17:01:50Z

P.A.: /* Downloads API */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
* [http://arewemeetingyet.com/Los%20Angeles/2013-08-20/10:00/w/Firefox%20development%20meeting Handy local meeting time link]
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
== Project Updates ==
===Australis===
* TART performance
** We're bisecting UX like crazy. It's a little tricky because there seems to be some noise in the measurements as we go, and we're a little wary that the total regression is the sum of many small ones...but there is at least one changeset range where there's been a pretty substantial regression, and we're peeling into that.
** MattN has noted that, at least locally, SVG clip-paths are pretty expensive on his XP machine, and removing them saw a [http://compare-talos.mattn.ca/breakdown.html?oldTestIds=130&newTestIds=132&testName=tart&osName=MattN-WinXP&server=graphs.mattn.ca 12% performance improvement] compared to having the clip-paths. We're going to pursue Graphics on the possibility of caching clip-paths in {{bug|914617}}.
** Vladan has found a solution to our XP pseudostack problem - one simply needs to copy a more recent version of dbghelp.dll (he tested with DLL version 6.12.2.633) into the firefox directory. Once we've confirmed on a few other machines, we'll update MDN (and possibly pursue getting that DLL put on all of the talos slaves)

===Downloads API===
* Significant reduction in the Slow SQL queries since landed in Nightly
* Plan to remove the preference that disables the new code in Firefox for Desktop
* Active outreach to extension developers this week before the Aurora migration
* Planned API changes, and final review before the Aurora migration
* Feedback on known temporary regressions and also on positive additions
* Tremendous progress this week on 10 of 12 bugs tracking release
*: The 2 remaining bugs are the DownloadTaskbar front-end and one minor regression to investigate
* Conversation with Sam Foster of the Metro Firefox team to evaluate switching to the new API
* Upcoming firefox-dev post

===Thumbnailing===
'''Foreground thumbnailing'''

* addressed by patch in {{bug|906615}} (below): {{Bug|809051}} - Limit how often we thumbnail the page using the foreground service

'''Background thumbnailing'''

* landed: {{Bug|875986}} - BackgroundPageThumbs should be able to capture private thumbnails while private browsing is active
* landed: {{Bug|909218}} - Allow a docShell to have default load flags that will be applied to every request made from it.
* landed: {{Bug|912763}} - Disable background thumbnails on Beta
* landed: {{Bug|910563}} - gracefully handle remote process crashing
* landed: {{Bug|906713}} - Intermittent browser_thumbnails_background.js | Thumb browser should exist immediately after capture.
* landed: {{Bug|903299}} - Modal dialog / prompt failures when running browser_thumbnails_background.js
* should be fixed by {{bug|875986}}'s landing: {{Bug|899064}} - Profiler won't turn on because it thinks I'm in private browsing mode [due to background thumbnails]
* new patch for review: {{Bug|906615}} - Background thumbnail service shouldn't overwrite existing thumbnails, or at least foreground thumbnails should be preferred
* waiting on review: {{Bug|910036}} - about:newtab shouldn't load thumbnails in background when hidden by preloader
* patch for review: {{Bug|913171}} - Intermittent browser_thumbnails_background.js | Captured URL should be currently expected URL

===SessionStore===

(Steven and I are unfortunately unable to attend the meeting today. Feel free to read this out loud or just read it on your own :)

* SessionStore is affected by a possible data loss due to ChromeWorkers being aborted on shutdown, patches under way to fix this ({{bug|913899}}).
* The recent session cookie refactorings introduced a regression for huge sessions with lots of (nested) history entries, patches waiting for review ({{bug|912717}}).
* Telemetry for TabStateCache landed ({{bug|896545}}) and shows that our [http://bit.ly/188LAUs cache hit rates] are great.
* We're working on tests for the TabStateCache ({{bug|911115}}).
* Global Value API has been backed out to fix regressions before landing again ({{bug|899213}}).
* With nsIAppStartup.willRestart and .wasRestarted in the making ({{bug|911146}}) we will be able to get rid of some more ugly code ({{bug|914062}}).
* Missing tests are the last thing blocking us from landing the first async data collection patches ({{bug|894595}}).

===Places API asyncification===
* Raymond has posted most of the patches needed for the bookmarks backups improvements. Mak going to review them by the end of the week, then will go through the goal target and file any missing bugs to complete the project.
* Mano is working towards a solution to a problem with guids and the new async transactions, as well as on a regression fix due to recent related changes. Patches are in the bugs and Mak going to review them.
* Mak currently working on regression fixes for issues introduced by automatic batches in Places views.

===Social API===
===e10s===

* {{bug|899348}} Tab crashed page
* {{bug|913155}} Submit crash report from tab crashed
* Many bug fixes work

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Toolkit/Submodules

2013-08-23T17:01:02Z

P.A.: Add Neil Deakin as preferred reviewer for the Download Manager module

{{ToolkitModule
|name=Bootstrapping, startup and chrome registry
|description=
|owner=[mailto:benjamin@smedbergs.us Benjamin Smedberg]
|peers=[mailto:rstrong@mozilla.com Robert Strong], [mailto:dtownsend@mozilla.com Dave Townsend], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|source_dirs=toolkit/xre, toolkit/library, toolkit/profile, toolkit/components/startup, toolkit/components/commandlines, toolkit/components/remote, toolkit/components/build, chrome
|components=Toolkit::Startup and Profile System
}}

{{ToolkitModule
|name=Breakpad (crash reporter)
|description=
|owner=[mailto:ted.mielczarek@gmail.com Ted Mielczarek]
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:mark@moxienet.com Mark Mentovai]
|source_dirs=toolkit/crashreporter
|components=Toolkit::Breakpad Integration
}}

{{ToolkitModule
|name=XUL Language
|description=
|owner=[mailto:enndeakin@gmail.com Neil Deakin]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:aromano@mozilla.com Asaf Romano]
|source_dirs=toolkit/content,
toolkit/components/autocomplete
|components=Toolkit::XUL Widgets, Toolkit::Toolbars and Toolbar Customization, Toolkit::Autocomplete
}}

{{ToolkitModule
|name=Add-ons
|description=
|owner=[mailto:bmcbride@mozilla.com Blair McBride]
|peers=[mailto:dtownsend@mozilla.com Dave Townsend], [mailto:rstrong@mozilla.com Robert Strong]
|source_dirs=toolkit/mozapps/extensions, toolkit/mozapps/plugins
|components=Toolkit::Add-ons Manager, Toolkit::Plugin Finder Service
}}

{{ToolkitModule
|name=Installer
|description=
|owner=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:netzen@gmail.com Brian Bondy]
|source_dirs=toolkit/mozapps/installer
|components=Toolkit::NSIS Installer
}}

{{ToolkitModule
|name=Application Update
|description=
|owner=[mailto:rstrong@mozilla.com Robert Strong]
|peers=[mailto:netzen@gmail.com Brian Bondy], [mailto:dtownsend@mozilla.com Dave Townsend]
|source_dirs=toolkit/mozapps/update
|components=Toolkit::Application Update
}}

{{ToolkitModule
|name=Download Manager
|description=
|owner=[mailto:paolo.mozmail@amadzone.org Paolo Amadini]
|peers=[mailto:enndeakin@gmail.com Neil Deakin], [mailto:mak77@bonardo.net Marco Bonardo]
|source_dirs=toolkit/components/downloads, toolkit/mozapps/downloads, toolkit/components/jsdownloads
|components=Toolkit::Download Manager
}}

{{ToolkitModule
|name=Password Manager/Satchel
|description=
|owner=[mailto:dolske@mozilla.com Justin Dolske]
|peers=[mailto:mnoorenberghe+bmo@mozilla.com Matthew Noorenberghe]
|source_dirs=toolkit/components/passwordmgr, toolkit/components/satchel
|components=Toolkit::Password Manager, Toolkit::Form Manager
}}

{{ToolkitModule
|name=XULRunner
|description=
|owner=[mailto:mark.finkle@gmail.com Mark Finkle]
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg], [mailto:ted.mielczarek@gmail.com Ted Mielczarek]
|source_dirs=xulrunner
|components=Toolkit::XULRunner
}}

{{ToolkitModule
|name=Themes
|description=
|owner=[mailto:dao@mozilla.com Dão Gottwald]
|peers=[mailto:rflint@ryanflint.com Ryan Flint], [mailto:gavin@gavinsharp.com Gavin Sharp]
|source_dirs=toolkit/themes
|components=Toolkit::Themes
}}

{{ToolkitModule
|name=Locales (build/packaging only)
|description=
|owner=[mailto:axel@pike.org Axel Hecht]
|peers=[mailto:benjamin@smedbergs.us Benjamin Smedberg]
|source_dirs=toolkit/locales
|components=
}}

{{ToolkitModule
|name=Video/Audio Controls
|description=
|owner=[mailto:dolske@mozilla.com Justin Dolske]
|peers=[mailto:jaws@mozilla.com Jared Wein]
|source_dirs=toolkit/content/widgets
|components=Toolkit::Video/Audio Controls
}}

{{ToolkitModule
|name=OS Integration
|description=
|owner=
|peers=
|source_dirs=toolkit/system
|components=
}}

{{ToolkitModule
|name=OS.File
|description=The JS file access API
|owner=[mailto:dteller@mozilla.com David Rajchenbach-Teller]
|peers=[mailto:froydnj@mozilla.com Nathan Froyd]
|source_dirs=toolkit/components/osfile
|components=
}}

{{ToolkitModule
|name=Content Preferences
|description=
|owner=[mailto:adw@mozilla.com Drew Willcoxon]
|peers=[mailto:mak77@bonardo.net Marco Bonardo]
|source_dirs=toolkit/components/contentprefs
|components=Toolkit::General
}}

Snappy/AsyncShutdown

2013-08-23T13:09:41Z

P.A.: /* Use cases */ Add Downloads API

= Our objective =

At the moment, Firefox shuts down mostly sequentially. Waiting until an asynchronous task is complete before proceeding with shutdown is complicated and requires spinning the event loop, which is generally Not a Good Idea.

We need to start thinking about a way to shutdown asynchronous services.

= Use cases =
== Asynchronous databases need to be AsyncClosed() ==
(TBD)

== Telemetry data must be saved asynchronously ==
(TBD)

== Downloads API may have a pending "downloads.json" write ==
Before saving the list of in-progress downloads, the Downloads API waits 1.5 seconds after every change in state of downloads.

Being able to force an asynchronous write of the JSON file in case the browser is closed during the 1.5 seconds window might be useful.

= Related bugs =
- https://bugzilla.mozilla.org/show_bug.cgi?id=722648 - Asynchronous observers.
- https://bugzilla.mozilla.org/show_bug.cgi?id=881667 - Expose startup/shutdown stage to components.

Firefox/Meeting/20-Aug-2013

2013-08-20T17:01:12Z

P.A.: /* Downloads API */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
* [[Firefox/Get_Involved]]
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''

* Andrew Wang (:velocirabbit) and Jesse Fox (:jfox) for helping to fix their first bugs in SessionStore. [ttaubert]

== Project Updates ==
===Australis===
* Character encoding widget has landed ({{bug|865916}})! Great work from mikedeboer, dao and Gijs.
* The tpaint regression ({{bug|889758}})
** For non-PGO Windows XP is in the ~0.5% range! \o/
** For PGO Windows XP is in the ~3.3% range. o_O
* We've been working with avih and vladan from perf on dealing with our TART regressions
* mconley's been working with BenWa to get [http://benoitgirard.wordpress.com/2012/09/21/video-synced-profiling/ Video Sync'd Profiling] working properly on Windows to make it easier to identify what is causing dropped frames.
* Markus Stange has the beginnings of [https://bugzilla.mozilla.org/show_bug.cgi?id=902857#c11 a reflow profiler] that we could use to find out why UX's reflows are more expensive than m-c's. [http://tests.themasta.com/cleopatra/?report=e67ac706f10f1c717933f2cd35e7682d77ba6d5c Here's an example profile].

===Downloads API===
* Almost enabled in Nightly!
* Regressions to be filed as blocking {{bug|825588}}.
* [https://mail.mozilla.org/pipermail/firefox-dev/2013-August/000804.html More details in the firefox-dev post.]

===Thumbnailing===
'''Foreground thumbnailing'''

* {{Bug|809051}} - Limit how often we thumbnail the page using the foreground service
** patch posted for feedback

'''Background thumbnailing'''

* {{Bug|897880}} - Background thumbnail service must not overwrite existing thumbnails if it gets an error response
** landed
* {{Bug|901294}} - Unexpected downloading will be started by after every restart of the browser due to background thumbnailing
** patch r+'ed, but depends on {{bug|906276}}, in review
* {{Bug|896912}} - Investigate test failures muted by bug 892875
** discussion about how the about:newtab preloader affects background thumbnail generation
* {{Bug|903949}} - about:memory and the background thumbnails process are combining to cause hangs and unexpected behaviour
** fixed
* Mark [https://groups.google.com/forum/#!topic/mozilla.dev.tech.network/X8t4Sob3l9U posted to dev.tech.network] about using the LOAD_ANONYMOUS flag to better sandbox background thumbnail page loads
* {{Bug|904341}} - Content-blocking addons not working with background thumbnails
** Bill is working on a back-end patch that may be helpful

===SessionStore===
===Places API asyncification===
* Mak going to investigate intermittent failures and incompatibilites (Xmarks) introduced by automatic batching
* Mano should have patches for async transaction manager and consumers ready by the end of the week
* Raymond has new patch for GUIDs in json backups, Mano reviewing it soon

===Social API===
===e10s===

* {{bug|899222}} About:home relanded
* {{bug|897060}} Select Dropdown on review
* {{bug|906237}} Mac input bug landed today on central
* {{bug|896748}} Notification API support
* {{bug|899348}} Tab crashed page
* {{bug|905436}} Add-ons tracking bug for work needed to make some add-ons work

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Features/Desktop/Downloads API

2013-08-20T16:48:39Z

P.A.: Clarify feature state on Firefox 25

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 26
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
|Feature implementation notes===== Bugs list and patch queue ====

'''Feature tracking bug:'''

* {{bug|825588}} (covers work across all Mozilla products)

'''Key implementation bugs:'''

* {{bug|847863}}: Use the JavaScript API instead of nsIDownloadManager as the back-end for the panel.

'''Additional steps needed to test the feature:'''

* In Firefox 25, the feature can be enabled by toggling the <code>browser.download.useJSTransfer</code> preference and restarting.
** ''This is only useful for early testing by add-on developers, as the feature is not ready in Firefox 25.''
* In Firefox 26, the feature is enabled by default and cannot be disabled.

'''Work required to release and enable the feature for everyone:'''

* Bugs listed as blocking {{bug|907082}}:

<bugzilla>{ "blocks": 907082, "status": ["NEW", "ASSIGNED"] }</bugzilla>
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature list=Desktop
|Feature project=Responsiveness
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Features/Desktop/Downloads API

2013-08-20T08:50:42Z

P.A.: Set feature list and project

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 26
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
|Feature implementation notes===== Bugs list and patch queue ====

'''Feature tracking bug:'''

* {{bug|825588}} (covers work across all Mozilla products)

'''Key implementation bugs:'''

* {{bug|847863}}: Use the JavaScript API instead of nsIDownloadManager as the back-end for the panel.

'''Additional steps needed to test the feature:'''

* In Firefox 25, the feature can be enabled by toggling the <code>browser.download.useJSTransfer</code> preference and restarting.
* In Firefox 26, the feature is enabled by default and cannot be disabled.

'''Work required to release and enable the feature for everyone:'''

* Bugs listed as blocking {{bug|907082}}:

<bugzilla>{ "blocks": 907082, "status": ["NEW", "ASSIGNED"] }</bugzilla>
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature list=Desktop
|Feature project=Responsiveness
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Features/Desktop/Downloads API

2013-08-20T08:45:38Z

P.A.: Edit bug query

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 26
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
|Feature implementation notes===== Bugs list and patch queue ====

'''Feature tracking bug:'''

* {{bug|825588}} (covers work across all Mozilla products)

'''Key implementation bugs:'''

* {{bug|847863}}: Use the JavaScript API instead of nsIDownloadManager as the back-end for the panel.

'''Additional steps needed to test the feature:'''

* In Firefox 25, the feature can be enabled by toggling the <code>browser.download.useJSTransfer</code> preference and restarting.
* In Firefox 26, the feature is enabled by default and cannot be disabled.

'''Work required to release and enable the feature for everyone:'''

* Bugs listed as blocking {{bug|907082}}:

<bugzilla>{ "blocks": 907082, "status": ["NEW", "ASSIGNED"] }</bugzilla>
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Features/Desktop/Downloads API

2013-08-20T08:39:05Z

P.A.: Fix typo

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 26
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
|Feature implementation notes===== Bugs list and patch queue ====

'''Feature tracking bug:'''

* {{bug|825588}} (covers work across all Mozilla products)

'''Key implementation bugs:'''

* {{bug|847863}}: Use the JavaScript API instead of nsIDownloadManager as the back-end for the panel.

'''Additional steps needed to test the feature:'''

* In Firefox 25, the feature can be enabled by toggling the <code>browser.download.useJSTransfer</code> preference and restarting.
* In Firefox 26, the feature is enabled by default and cannot be disabled.

'''Work required to release and enable the feature for everyone:'''

* Bugs listed as blocking {{bug|907082}}:

----
<bugzilla>{ "blocks": 907082, "status": "ASSIGNED" }</bugzilla>
<bugzilla>{ "blocks": 907082, "status": "NEW" }</bugzilla>
----
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Features/Desktop/Downloads API

2013-08-20T08:37:24Z

P.A.: Add bug references

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature version=Firefox 26
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
|Feature implementation notes===== Bugs list and patch queue ====

'''Feature tracking bug:'''

* {{bug|825588}} (covers work across all Mozilla products)

'''Key implementation bugs:'''

* {{bug|847863}}: Use the JavaScript API instead of nsIDownloadManager as the back-end for the panel.

'''Additional steps needed to test the feature:'''

* In Firefox 25, the feature can be enabled by toggling the <code>browser.downloads.useJSTransfer</code> preference and restarting.
* In Firefox 26, the feature is enabled by default and cannot be disabled.

'''Work required to release and enable the feature for everyone:'''

* Bugs listed as blocking {{bug|907082}}:

----
<bugzilla>{ "blocks": 907082, "status": "ASSIGNED" }</bugzilla>
<bugzilla>{ "blocks": 907082, "status": "NEW" }</bugzilla>
----
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Features/Desktop/Downloads API

2013-08-20T08:18:50Z

P.A.: Add release target

Performance

2013-08-20T08:16:52Z

P.A.: /* Downloads API Rewrite */ Update target and add link to feature page

=Performance=
Mozilla's performance program focuses on improvements to the Gecko platform and the Firefox Desktop, Firefox for Android, and Firefox OS products.

==Projects==
===Active===
====Incremental Cycle Collection (ICC)====
{{PerfProject
|impact={{desktop}} {{mobile}} {{b2g}}
|team=Andrew McCreight (lead)
|duration=TBD
|goal=Implement incremental cycle collection to reduce1 cycle collector pauses in the Firefox UI.
1Reduction in cycle collector pauses will be measured with the [http://mzl.la/XLsAoB CYCLE_COLLECTOR_FULL Telemetry probe]. The degree of reduction that can be achieved is currently unclear.
|reports=TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/mccr8 Andrew McCreight]
|work={{bug|850065}}
|dependencies=
|notes=
}}
----

====Keep JS-accessible APIs from blocking the main thread====
{{PerfProject
|impact={{desktop}} {{mobile}} {{b2g}}
|team=David Rajchenbach-Teller (lead), Paolo Amadini
|duration=TBD
|goal=Refactor existing and provide new JS APIs to either migrate services, components, and add-ons off the main thread or at least prevent them from blocking the main thread.
|reports=TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/Yoric David Rajchenbach-Teller]
|work=[http://mzl.la/ZJaowA Bugzilla query]
|dependencies=
|notes=This project focuses on JS-accessible APIs in the context of Web Workers.
}}
----

====Profiler Backend for Mobile====
{{PerfProject
|impact={{mobile}} {{b2g}}
|team=Julian Seward (lead), Benoit Girard, Mike Hommey
|duration=TBD
|goal=Accurate1, crash-free, deadlock-free, low overhead2 stack unwinding for the SPS profiler for Firefox for Android and Firefox OS.
[1]The correct sequence of code return addresses on the stack, ideally without the unwind terminating before it gets back to main(). 
[2]Average unwind cost of 500 microseconds for a 30-frame backtrace on one core of a 1 GHz Cortex A9
|reports=[https://blog.mozilla.org/jseward Julian Seward's blog], TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/sewardj Julian Seward], [http://teamstat.us/#show/irc.mozilla.org/perf/BenWa Benoit Girard], [http://teamstat.us/#show/irc.mozilla.org/perf/glandium Mike Hommey]
|work={{bug|863453}}
|dependencies=
|notes=May impact desktop Linux as well.
}}
----
====Reducing time to first paint - Phase 1====
{{PerfProject
|impact={{desktop}}
|team=Vladan Djeric (lead)
|duration=TBD
|goal=A 10% reduction1 in time between XRE_Main and first paint2 during cold starts3 on Windows 7 with no extensions installed4, on reference slow hardware5, 30 seconds after an OS reboot.
[1]Currently, after an OS restart, XRE_Main to firstPaint takes about 4.2 seconds on the reference hardware. A 10% reduction will be ~400ms. 
[2]XRE_Main as the starting point to exclude the impact of loading Firefox binaries as they grow bigger with every release. First paint to exclude the impact of Yoric's session store refactor work. 
[3]Cold start because a lot of the work will be focused on reducing the amount of I/O done during startup. 
[4]No extensions to exclude the impact of Irving's Add-on Manager work. 
[5]The reference hardware is a recent, slow Win7 laptop with an AMD C-50 dual-core @ 1 GHz, magnetic HDD, and 2GB shared RAM. A slow Windows laptop is used because it is consistently slow and can be easily debugged.
|reports=[https://blog.mozilla.org/vdjeric/category/start-faster/ Vladan Djeric's blog], TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/vladan Vladan Djeric]
|work= {{bug|810156}}
|dependencies= [[Performance#Replace_Add-on_Manager_SQLITE_with_JSON_file|Replace Add-on Manager SQLITE with JSON file project]]
|notes=Will measure with about:telemetry on reference hardware as aggregate Telemetry includes both warm and cold starts and a variety of hardware confirgurations.
}}
----

====Replace Add-on Manager SQLITE with JSON file====
{{PerfProject
|impact={{desktop}} {{mobile}}
|team=Irving Reid (lead), Felipe Gomes
|duration=6 weeks (approx week of May 27, 2013)
|goal=Goal: Reduce Add-on Manager impact on start-up time1 and runtime pauses2 by removing SQLITE database from XPI Provider and Add-on Repository and replacing with JSON3.
1Start-up time reduction by reducing the amount of I/O required before first paint. 
2Runtime pause reduction by reducing I/O required during add-on up-to-date checks and updates, and making sure as much as possible is off main thread. 
3New implementation will do no blocking I/O except minimal loading of required data during start-up.
|reports=[http://www.controlledflight.ca/category/mozilla Irving Reid's blog], TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/irving Irving Reid], [http://teamstat.us/#show/irc.mozilla.org/perf/felipe Felipe Gomes]
|work= {{bug|853388}}, {{bug|853389}}
|dependencies=
|notes=
}}
----

====Smooth Tab Animation====
{{PerfProject
|impact={{desktop}}
|team=Avi Halachmi (lead), Tim Taubert
|duration=TBD
|goal=Reasonably1 smooth tabstrip animation on modern low-end AMD/Intel CPUs. The specific focus will be on use cases 1-8 defined below.
# New tab open of about:blank where other tabs are unaffected. (not common, this is our raw baseline)
# Tab close where other tabs are unaffected, and where the newly focused tab is empty. (also raw baseline)
# New tab open - with thumbnails preview - where other tabs are unaffected.
# Tab close where other tabs are unaffected, where the newly focused tab is heavy (e.g. GMail).
* 5-8. Same as the above, when other tabs are affected (shrunk/expanded) - up to 10 changing tabs.
1The last 70% of the animation is not lower than 50fps.
|reports=[http://avih.github.io/blog/categories/tabstrip/ Avi Halachmi's blog], TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/avih Avi Halachmi]
|work={{bug|815354}}
|dependencies=OMTC
|notes=
}}
----

====Network Cache Rewrite====
{{PerfProject
|impact={{desktop}} {{mobile}} {{b2g}}
|team=Honza Bambas (lead), Michal Novotny, Jason Duell (manager)
|duration=Goal is to have new code in production by end of Q4 2013
|goal=A cache that causes no main thread I/O jank (directly or indirectly via locks)1, and that avoids losing the entire cache during crashes or unclean shutdown.2 
[1]Currently the cache causes jank (sometimes in excess of 1 second) via main thread waiting while cache thread holds lock and does I/O. 
[2]Cache is currently thrown away unless clean shutdown. Cache loss rates per startup are 9% on windows desktop, 11% OSX, 22% Linux desktop, 25% metro. New design will keep all cache entries and detect corruption on a per-entry basis. 
|reports=
|work={{bug|877301}}
|dependencies=
|notes= [https://wiki.mozilla.org/Necko/Cache/Plans Cache rewrite project wiki page]
}}
----

====Downloads API Rewrite====
{{PerfProject
|impact={{desktop}}
|team=Paolo Amadini (lead), Raymond Lee, Felipe Gomes, Neil Deakin
|duration=Mid August for reaching the initial goal in Nightly.
Probably another month or two (with lower bandwidth) for follow-ups.
|goal=To improve responsiveness when downloads are started, by removing the main-thread I/O caused by access to "downloads.sqlite". The concrete goal is to ensure that SQL statements involving moz_downloads no longer appear in the "slow SQL" Telemetry dashboard.
|reports=firefox-dev mailing list, [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com weekly updates tool].
|work={{bug|825588}}, [[Features/Desktop/Downloads_API|Feature Page]]
|dependencies=
|notes=The project should include a follow-up time frame to accommodate any changes identified after Firefox for Desktop has migrated to the new API, as well as handle requests to facilitate other Mozilla products and add-ons to migrate to the new API.
}}
----

====Remove localStorage From Browser Pages====
{{PerfProject
|impact={{desktop}}
|team=Marco Bonardo
|duration=
|goal=Replace about: pages use of DOM Storage with more performant storage, like indexedDB, to remove UI hangs due to main-thread IO.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|729777}} and dependencies
|dependencies=
|notes=
}}
----
====Complete Asynchronous History API====
{{PerfProject
|impact={{desktop}}
|team=Marco Bonardo, Asaf Romano, Raymond Lee
|duration=
|goal=Replace all remaining synchronous history APIs with asynchronous alternatives. This will reduce possibilities of contention between the synchronous and the asynchronous APIs, that can cause long hangs of the UI.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|699850}} and dependencies
|dependencies=Ensure to properly communicating add-ons compatibility issues before APIs removal, through blog post, Mozilla.dev.extensions, AMO team.
|notes=We should replace synchronous API that reports history status (bug 834541), this may be tricky since it’s required to be synchronous by some UI features and could slip off to the future, luckily it’s currently served through a cache that reduces its negative impact.
}}
----
====Reduce Impact Of Bookmarks Backups On Shutdown====
{{PerfProject
|impact={{desktop}}
|team=Raymond Lee, Marco Bonardo
|duration=
|goal=Replace synchronous main-thread bookmarks backups with asynchronous background backups.

Bookmarks backups currently only run on idle, but some instances never hit idle causing the backups to occur on shutdown, which negatively impacts the shutdown time of the browser.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|843357}} and dependencies, https://etherpad.mozilla.org/places-backups-changes
|dependencies=Ensure to properly communicating add-ons compatibility issues before APIs removal, through blog post, Mozilla.dev.extensions, AMO team.
|notes=This project will be completed in 3 parts:
#Convert APIs from synchronous to asynchronous - done
#Various improvements to ensure we store backups only when really needed, by skipping duplicates and giving better information to the users
#Async conversion, although some minor parts of the code should already be async converted as we go
}}
----
====Reduce Storage Connections Main-Thread Operations====
{{PerfProject
|impact={{desktop}} {{mobile}}
|team=David Teller, Marco Bonardo
|duration=
|goal=Setting up and closing a Storage database connection happens on main-thread, even if then the connection is only used through the asynchronous API. This may cause visible jank, especially when there’s other IO ongoing. Introduce a new purely asynchronous connection that never hits the main-thread and update consumers to use it. This will also ensure consumers of this connection can’t wrongly abuse of the synchronous APIs and create thread contention.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|702559}}, {{Bug|874814}}, {{Bug|885732}} and dependencies
|dependencies=
|notes=Need to blog about this change and update the documentation.
The asynchronous connection landed, though it still closes the database handle on main-thread though, so fixing that is the next goal for July. Consumers conversion may take some time, Sqlite.jsm has already been converted, autocomplete is ongoing, but each consumer has very specific requirements. Goal is to complete the connection and convert most common consumers by the end of September.
}}
----
====Asynchronous Places Annotations====
{{PerfProject
|impact={{desktop}}
|team=Asaf Romano, Marco Bonardo
|duration=
|goal=Annotations allow to set specific flags on bookmarks and pages in history, to identify them or attach additional information, but they are synchronous, so bookmarks conversion to an asynchronous API is blocked on them and they are currently causing unpredictable main-thread IO. Introduce a new asynchronous API that allows to annotate pages and bookmarks asynchronously, convert internal consumers to it.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|699844}} and dependencies
|dependencies=Ensure to properly communicating add-ons compatibility issues before APIs removal, through blog post, Mozilla.dev.extensions, AMO team.
|notes=The old service will keep living in parallel for a while, for compatibility reasons.

A first draft of the new API has been created. Asaf is going to create a first mock of the service and verify consumers requirements with it. Marco will work on the database schema and performances. Consumers conversion may take the most time and will likely be an iterative process once the API and the service are complete, by the end of the third quarter.
}}
----
====Improve Text Performance====
{{PerfProject
|impact={{desktop}} {{mobile}} {{b2g}}
|team=John Dagget, Jonathan Kew, Simon Montagu
|duration=
|goal=??
|reports=
|work={{Bug|863248}}, {{Bug|834609}}, {{Bug|885689}}
|dependencies=
|notes=Need to sync with Jet on this project definition.

A first draft of the new API has been created. Asaf is going to create a first mock of the service and verify consumers requirements with it. Marco will work on the database schema and performances. Consumers conversion may take the most time and will likely be an iterative process once the API and the service are complete, by the end of the third quarter.
}}
----
====Reduce impact of thumbnailing====
{{PerfProject
|impact={{desktop}}
|team=Drew Willicox, Mark Hammond
|duration=6 months
|goal=Toolkit has two services that capture thumbnails of pages: a "foreground" service and a new "background" service. The foreground service draws the content windows of pages that the user has opened to canvases on the main thread. The background service exposes an API that uses a remote xul:brower to load pages on demand in the hidden window and then in the content process draws the resulting content windows to canvases. Both services write thumbnails to disk on a background thread from the main process. The goal here is to minimize the impact in the broadest sense of both services: the user's perception of jank, resource use, time taken to draw to canvas, capturing only when necessary, etc.
|reports=[https://wiki.mozilla.org/Firefox/Meeting Desktop weekly meeting notes], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com/posts Drew's] and [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com/posts Mark's] weekly updates
|work={{Bug|899401}}
|dependencies=
|notes=

Ultimately we want to move all thumbnail capturing off the main thread, probably using the background service that landed in Fx 25. This service currently uses the Private Browsing feature to sandbox page loads, but declines to capture when a private browsing window is open, but can still have side-effects related to this (eg, if a capture is in-progress when PB mode is entered, it might cause cookies for a site to exist when they otherwise would not). We plan to avoid using PB mode once we have identified a technique to make these requests totally isolated.
}}
----

===On Hold===
====Shutdown====
{{PerfProject
|impact={{desktop}}
|team=Benoit Girard (lead)
|duration=TBD
|goal=Ensure 95% of Firefox desktop instances shutdown in 3 seconds or less.
|reports=[http://benoitgirard.wordpress.com Benoit Girard's blog], TeamStatus: [http://teamstat.us/#show/irc.mozilla.org/perf/BenWa Benoit Girard]
|work={{bug|819063}}
|dependencies=
|notes=
}}
{{PerfProjectHold|Resource availability}}
----
====Improve Places Hosts Storage====
{{PerfProject
|impact={{desktop}}
|team=Marco Bonardo
|duration=
|goal=Change the way we store hosts in Places to reduce work needed for inserting and querying pages. Currently we split www. and non www. hosts but we always use them as a single thing in all of the UI pieces, so we have to double the querying work to gather both.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|843357}} and dependencies
|dependencies=
|notes=It's a one bug project, most of the time is needed to verify if the change may cause any issues and designing the new queries. It may take about a week.
}}
{{PerfProjectHold|Resource availability, lower priority in comparison with other perf projects}}
----
====Improve Space Efficiency Of Places URL Index====
{{PerfProject
|impact={{desktop}}
|team=Marco Bonardo, Taras Glek
|duration=
|goal=The current URL index in places.sqlite database takes up to 30% of the database size. The features it provides can be obtained through a smarter hashing method that should improve the space efficiency by an order of magnitude. A smaller database has positive effects on IO and fragmentation.
|reports=[http://blog.bonardo.net/tag/performance Marco's blog], [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com weekly updates tool].
|work={{Bug|889561}}
|dependencies=
|notes=
}}
{{PerfProjectHold|Resource availability, lower priority in comparison with other perf projects}}
----
===Proposals===
Project proposals should be listed on the [https://etherpad.mozilla.org/perf perf etherpad].

===Archive===
Completed/terminated projects are listed in the [[Performance/ProjectArchive|project archive]].

==Tools==
*[[Telemetry|Telemetry]]
* [https://github.com/mozilla/jydoop jydoop: Efficient and Testable hadoop map-reduce in Python] ([http://benjamin.smedbergs.us/blog/2013-04-09/introducing-jydoop-fast-and-sane-map-reduce/ Introduction from Benjamin Smedberg])
* [https://developer.mozilla.org/en-US/docs/Performance/Profiling_with_the_Built-in_Profiler SPS Profiler]
* [[Buildbot/Talos]]

==Communication==
{| class="wikitable fullwidth-table"
! Communication Type !! Mechanism !! Audience
|-
| Announcements || [https://lists.mozilla.org/listinfo/dev-platform dev-platform] list || all
|-
| Meetings || First Thursday of each month, 11am PT
{{conf|99355}}
* Vidyo: Performance
* IRC: [irc://irc.mozilla.org/perf #perf]
* Agenda: [https://etherpad.mozilla.org/perf https://etherpad.mozilla.org/perf]
|| all
|-
| Meeting summaries || [[Performance | this wiki]] || all
|-
| Micro status || [http://teamstat.us/#browse/irc.mozilla.org/perf TeamStatus] || devs
|-
| Weekly status || [http://benjamin.smedbergs.us/weekly-updates.fcgi/ Mozilla Status Board] || devs
|}

===Press & Blog Posts===

===Progress Reports ===
{| class="wikitable collapsible" style="width: 100%"
! style="background-color: rgb(221, 221, 221);" colspan="2" | 2013
|-
|
* August 2013 [[Performance/2013-08-01|Meeting Minutes]], [[Performance/Report-2013-08|Report]]
* [[Performance/2013-07-11|July 2013 Meeting Minutes]]
* [[Performance/2013-06-06|June 2013 Meeting Minutes]]
* [[Performance/2013-05-02|May 2013 Meeting Minutes]]
|}

==People==
list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project
{| class="wikitable fullwidth-table"
| Project Champion ||
|-
| Program Management || Lawrence Mandel
|-
| Product ||
|-
| Engineering || Taras Glek, Vladan Djeric
|-
|}

==References==

===Related Projects===
* [[Performance/MemShrink|MemShrink]]

==Archive==
===Old Projects===
* [[Firefox/Projects/Mobile_Startup_Shrink|Mobile Startup Shrink]]
* [[Firefox/Projects/Startup_Time_Improvements|Startup Performance]]
* [[Firefox:FrontEndPerformance|Front-end Performance]] (i.e., responsiveness)
* [[Performance/Addons|Add-on Performance]]
* [[Performance/Snappy|Snappy]]
* [[Mobile/Performance|Mobile Performance Info]]

===Tools===
* [[Codesighs]] - a tool which analyzes code and data size.
* [[Performance:Tools]]. For measuring performance. Tip o' the propeller-cap to [mailto:zuperdee@penguinpowered.com Daniel Roberts] (zuperdee@penguinpowered.com) for the pointers.
* [[Performance:Probes]]. Project to integrate a system of performance probes into Gecko.

===Documentation and Presentations===
* Code Footprint [[Performance:Footprint_Reduction_Techniques]] explains common bad patterns and how to correct them.
* [[Performance:Profiling_JuJu]]. Things you should know about doing profiling. Tips and tricks for some of the tools, and lots of other Good Things To Know.
* [http://www.mozilla.org/performance/mac-performance.html Profiling and leak analysis] on the Mac.
* [[Performance:Footprint_Tools]]. Presentation on footprint tools
* [[Performance:Startup]] [http://www.mozilla.org/performance/perf-intro/slide1.xml slides] Presentation on general performance tools
* [[Performance:Leak_Tools]]. Presentation on memory leaks detection tools
* [http://www.mozilla.org/performance/mac-performance.html Mac Performance Tools] Presentation on performance tools that work on Mac

Features/Desktop/Downloads API

2013-08-20T08:13:08Z

P.A.: Fixes

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature requirements=The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[User:P.A./Download_architecture_improvements|download architecture improvements]]''' page.
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Features/Desktop/Downloads API

2013-08-20T08:10:00Z

P.A.: Create feature page for the Downloads API

{{FeatureStatus
|Feature name=Downloads API
|Feature stage=Development
|Feature status=In progress
|Feature health=OK
|Feature status note=https://wiki.mozilla.org/Performance#Downloads_API_Rewrite
}}
{{FeatureTeam
|Feature feature manager=Paolo Amadini
|Feature lead engineer=Paolo Amadini
|Feature additional members=Neil Deakin, Felipe Gomes, Raymond Lee
}}
{{FeaturePageBody
|Feature overview=The current storage back-end for downloads, based on the synchronous <code>nsIDownloadManager</code> interface and an associated SQLite database, causes noticeable performance issues when starting and finishing downloads.

The new Downloads API will improve the responsiveness of Firefox for Desktop, by removing the main-thread I/O caused by access to <code>downloads.sqlite</code>. The concrete goal is to ensure that SQL statements involving <code>moz_downloads</code> no longer appear in the "slow SQL" Telemetry dashboard.
|Feature users and use cases=The Downloads Panel is the main user of the Downloads API in Firefox for Desktop. Since the new API is part of Toolkit, other Mozilla products will be able to adopt it for improved performance.
|Feature non-goals=This feature does not involve changes to the user interface and interaction model. Minor changes in behavior are expected, because the API is a complete reimplementation of the back-end.
|Feature functional spec=The overall design is documented in the '''[[download architecture improvements|User:P.A./Download_architecture_improvements]]''' page.
}}
{{FeatureInfo
|Feature priority=Unprioritized
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Firefox/Meeting/13-Aug-2013

2013-08-13T17:02:15Z

P.A.: /* Downloads API */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
*Removal of "Enable JavaScript" and "Load images automatically" in Firefox 23
**For me, this has rendered this version of Firefox unusable, and my only alternative was to uninstall it and reinstall 22. I hope that these option checkboxes will be restored in Firefox 24.

== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''

* brinks7 who (although ~2.5 years ago) provided a great STR that helped _a lot_ with finally fixing {{bug|637020}}. [ttaubert]
* onemen.one for providing lots of helpful comments on recent SessionStore improvements and regressions. [ttaubert]

== Project Updates ==
===Australis===
===Downloads API===
* It is a matter of days before switching the <code>browser.download.useJSTransfer</code> preference
* Will wait before posting the bi-weekly update to firefox-dev

===Thumbnailing===
===SessionStore===
* Lots of smaller code cleanups that help us understand more details and maintain SessionStore.
* Work on reducing SessionStore impact when creating tabs to restore a session ({{bug|900803}} and {{bug|901137}}) in progress.
* We are working on introducing an API to store data per session {{bug|899213}}, just like Scratchpad does.
* Fixed a very long-standing data loss issue {{bug|637020}} that could make us lose whole windows when crashing at or shortly after startup.
* Getting closer to move first parts of the data collection to content scripts, {{bug|894595}}, {{bug|903388}}, and {{bug|904003}}.

===Places API asyncification===
===Social API===
===e10s===

* Landed:
** {{bug|516753}} context area menu (using CPOWs)
** {{bug|897062}} middle click support (for links/scroll)
** {{bug|902695}} openURIInFrame (support for opening in new window)
** {{bug|870625}} Make add-on installation work
* {{bug|899222}} About:home backed out
* Three bugs of interest
** {{bug|897060}} - Dropdown menus (<select>)
** {{bug|899648}} - alert()/prompt()
** {{bug|896787}} - URL bar gets cleared after opening a tab

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Firefox/Meeting/6-Aug-2013

2013-08-06T16:50:31Z

P.A.: /* Downloads API */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''

* billm for fixing error reporting in {{bug|899812}}. <3 (ttaubert).

== Project Updates ==
===Australis===
* Matt, Jared, Gijs and Mike Conley continue to hammer on performance. We're *so close*. ~3.2% tpaint and 1.5-3% ts_paint regressions for XP
* Mike de Boer's been dropping an elbow on P1 and P2 bugs
* Marco finished the initial styling work on the Bookmarks widget

===Downloads API===
* Can be activated in Nightly and Aurora using the <code>browser.download.useJSTransfer</code> preference
* More details in the [https://groups.google.com/forum/#!topic/mozilla.dev.extensions/ltOB3MzVwcI mozilla.dev.extensions and mozilla.dev.platform post]
* Working on remaining blocking features before switching the preference

===Thumbnailing===
===SessionStore===
* Steven restored important telemetry measurements that got lost when moving the I/O code to a worker.
* David is working on improving sessionstore communication, removing private tabs from the state.
* Work on e10s in continuing, blocked by rewriting the current cookie collection methods.
* We landed a patch that fixes blank new windows and prevents about:home from loading when we restore a session ({{bug|893061}}).
* Landed two patches that remove a whole chunk of sessionstore code \o/ ({{bug|898755}} and {{bug|898775}}).

===Places API asyncification===
===Social API===
===e10s===

* {{bug|617804}} SetStatus landed (link hover support)
* {{bug|897066}} switch browser remote/non-remote landed
* {{bug|899222}} about:home in child process getting close
* {{bug|516753}} nsContextMenu patch using CPOWs

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!

===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin%40gavinsharp.com Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/pamadini%40mozilla.com Status Board])

===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak%40mozilla.com Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/enndeakin%40gmail.com Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipc%40gmail.com Status Board])

===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano%40mozilla.com Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert%40mozilla.com Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/adw%40mozilla.com Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mhammond%40mozilla.com Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod%40mozilla.com Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske%40mozilla.com Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley%40mozilla.com Status Board])

===dao===

===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mdeboer%40mozilla.com Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs%40mozilla.com Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/bmcbride%40mozilla.com Status Board])

===MattN===
(MattN's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mozilla%40noorenberghe.ca Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws%40mozilla.com Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/scaraveo%40mozilla.com Status Board])

Firefox/Meeting/30-Jul-2013

2013-07-30T16:58:27Z

P.A.: /* Downloads API */ Add status update

Firefox/Meeting/23-Jul-2013

2013-07-23T17:01:37Z

P.A.: /* Downloads API */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
* Using fx-team

== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
== Project Updates ==
===Australis===
===Downloads API===

Work on the assigned bugs is continuing.
* Felipe posted first patch iteration on {{bug|852482}} - Add methods to execute actions on completed downloads.
* Paolo posted test updates and first patch on {{bug|836437}} - Add the ability to resume a download from where it stopped.
** Landing dependency {{bug|896179}} - Crash in BackgroundFileSaver when append is enabled and hashing is disabled.

===Thumbnailing===
===SessionStore===

* Close to landing Promise.jsm patches.
* Working on a prototype and discussing e10s approaches.
* Session Data Cache for tabs should lange soon.
* Working on moving more I/O logic to the worker.

===Places API asyncification===
===Social API===
===e10s===

* e10s team in Toronto this week for a hackfest
* Identifying dogfooding bugs and working on them
* http://etherpad.mozilla.org/e10s
* Work in progress in various fronts (focus, find bar, favicons, etc)
* more details next week

=== UX Updates ===

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!
===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/paolo Status Board])
===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/Enn Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe Status Board])
===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/drew Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/markh Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley Status Board])

===dao===
===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mikedeboer Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/Unfocused Status Board])

===MattN===
([http://benjamin.smedbergs.us/weekly-updates.fcgi/user/MattN MattN's Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mixedpuppy Status Board])

Firefox/Meeting/16-Jul-2013

2013-07-18T12:51:47Z

P.A.: /* Project Updates */ Add Downloads API update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
* MattN nominates Adam [:hobophobe] for his work on find in page improvements (meta bug: {{bug|565552}})
* mak nominates Roberta for her work on removing an old feature from Storage, that could have been abused by add-ons ({{bug|865188}})

== Project Updates ==
===Australis===
* Still making progress on [https://people.mozilla.com/~mnoorenberghe/australis/?list=tab-perf&resolved=0&whiteboard=m8&meta=1 perf bugs]
* MattN and jaws are primarily focused on investigating and fixing the perf bugs, while Gijs, mconley, Unfocused, and mikedeboer are primarily focused on fixing P1 and P2 Australis bugs.

===Downloads API===
* Posted [https://mail.mozilla.org/pipermail/firefox-dev/2013-July/000567.html bi-weekly update] to firefox-dev
* Replacing use of nsIFile and nsIURL in JavaScript with strings, changing property names and types
* All the bugs that are required to complete the API are now assigned

===Thumbnailing===
* Remaining blocker: {{Bug|870100}}, actually using the background service in about:newtab. The patches there are r+'ed but cause lots of orange, so Mark filed {{Bug|892875}} to disable the service during non-thumbnail tests, but Dão and Gavin have raised questions about doing that. Discussion in progress.
* Other remaining blockers are ready to land: telemetry ({{bug|870104}}) and fixing a private browsing bug that caused an intermittent orange ({{bug|891169}} and {{bug|893404}} together).

===SessionStore===

* f+ for cutting saveState() into chunks
* fixed sessionstore regression (Fx 25)
* introduced dedicated sessionstore I/O worker
* work on converting sessionstore to Promise.jsm is continuing

===Places API asyncification===
* Mak fixed regression due to getPlacesInfo API code
* lots of brainstorming ongoing
* Mano working on design of a new async transactions manager
* Mak will investigate smart batches in Places views, needed for async transactions manager

==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!
===gavin===
(gavin's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gavin Status Board])

===paolo===
(paolo's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/paolo Status Board])
===mak===
(marco's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mak Status Board])

===enn===
(Neil's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/Enn Status Board])

===felipe===
(felipe's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe Status Board])
===mano===
(Mano's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mano Status Board])

===ttaubert===
(Tim's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert Status Board])

===adw===
(Drew's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/drew Status Board])

===markh===
(Mark's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/markh Status Board])

===smacleod===
(Steven's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/smacleod Status Board])

===dolske===
(dolske's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/dolske Status Board])

===mconley===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mconley Status Board])

===dao===
===mikedeboer===
(Mike's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mikedeboer Status Board])

===gijs===
(gijs' [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs Status Board])

===Unfocused===
(Blair's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/Unfocused Status Board])

===MattN===
([http://benjamin.smedbergs.us/weekly-updates.fcgi/user/MattN MattN's Status Board])

===jaws===
(jaws's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws Status Board])

===mixedpuppy===
(mixedpuppy's [http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mixedpuppy Status Board])

== UX Updates ==
===lco===
* Traveling for conference and meeting next week, 7/22 to 8/1. Will not be very responsive.
* Security and Privacy principles postcard
** http://people.mozilla.com/~lco/ProjectSPF/Principles/130711-2%20postcard.pdf
** I have some hard copies if you want one, but there will be a website coming soon
* A broader range, more consistent set of permissions doorhanger + icon combos?
** very early draft: http://people.mozilla.com/~lco/Permissions%20UI/130715%20concepts-permissions%20UI.pdf

Firefox/Meeting/Template

2013-07-18T12:45:10Z

P.A.: /* Project Updates */ "Downloads API"

Performance

2013-07-02T12:01:22Z

P.A.: /* Downloads API Rewrite */ Minor edit: typo, formatting

Firefox/Meeting/4-Jun-2013

2013-06-04T17:26:43Z

P.A.: /* paolo */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
; Work week bug triage
; [[Performance#Projects|Performance projects]]
* Goals
** Timely completion of larger performance work
** Increased visibility for your performance work
* Project definition
** Product impact - what products will this work impact?
** Goal - what will your project achieve and how will you know that you're done?
** Duration - what is the rough estimate for your project's completion? (ex, June, 2-3 months, Q3)
** Team - who is the project lead and who else is working on the project?
** Progress reports - how can others get updates without bugging you? Benjamin's weekly status tool, TeamStatus, and bi-weekly blog posts
** Work - how can others track your work? link to bugs, etherpad, wiki

== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
* Florian Bender, who's been helpful in filing bugreports, triage, and also in helping out users complaining on the Techcrunch article about Australis ( http://techcrunch.com/2013/06/01/mozilla-readies-major-firefox-redesign-as-it-ponders-what-the-browser-of-the-future-should-look-like/ )
* Christian Ascheberg contributed 2 patches for the download manager in {{bug|863063}} and {{bug|872330}}
* Xidorn Quan contributed a patch for the Downloads Panel in {{bug|861613}}
* Optimizer's Downloads Panel patch for {{bug|844606}} landed in Nightly and Aurora
* Lizzard for triaging good first bugs and figuring some of those are WFM

== Decisions needed/Action items ==
==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!
===gavin===
===paolo===
(from http://benjamin.smedbergs.us/weekly-updates.fcgi/user/paolo)

Done:

* Landed: {{bug|810490}} - Constant stack space promise
* Reviewed: {{bug|858234}} - merge ExecuteDesiredAction paths into nsDownloadManager
* Various reviews on the Downloads API

Next:

* Prioritize remaining work on the Downloads API
* Continue reviews and coding on the Downloads API
* Work on converting promise consumers to the new module

===mak===
* Done:
** Bug 769348 - URLs auto-completed in address bar might unexpectedly use ftp:// instead of http://
** Bug 858377 - Intermittent test_393498.js | false == true
** Bug 874407 - new history displays incorrectly in Library window/sidebar
** Feedback Bug 702559 - Create a pure-async mozIStorageAsyncConnection
** Review Bug 794323 - Remove the legacy JSON parsing mode
** Review Bug 860119 - Live-update about:home when defaultEngine changes
** Review Bug 863063 - quitting private browsing mode does not delete partially downloaded files
** Review Bug 872317 - Download indicator toolbar button depends on an odd XBL quirk
** Review Bug 874171 - (SQLite3.7.17) Upgrade to SQLite 3.7.17
** Feedback Bug 878411 - crash in mozilla::storage::Connection::internalClose @ sqlite3WalClose
** Review Bug 878690 - SafariProfileMigrator.js should use FormHistory.jsm
** Other minor reviews
* Next:
** Complete tests for Bug 769348 - URLs auto-completed in address bar might unexpectedly use ftp:// instead of http://
** Help Yoric with Bug 702559 - Create a pure-async mozIStorageAsyncConnection
** Review UP Places approach (bug 864918, bug 864925)

===enn===
===felipe===

(copied from http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe)

* {{bug|853389}} - AddonRepository - 3 patches are r+, just one left now!
* {{bug|862519}} - Backspace key for e10s - started drafting a patch

* Reviews
** {{bug|860421}}
** {{bug|875949}}
** {{bug|666809}}
** {{bug|820601}}
** {{bug|805684}}
** {{bug|821073}}

* Getting my GSOC student started
** https://github.com/abhishekchoudhary/fx-statistics
** http://trystswithcode.quora.com/

===mano===
I probably won't get home on time, so here are the notes for today.

Async login manager: XPCOM and js-module APIs, plus a fake-async implementation are posted on the bug for review and feedback. Once the APIs are finalized and approved, we're going to land this and start fixing all in tree callers (mostly tests). The callers will be fixed incrementally.
In parallel, the fake-async implementation will be replaced by Neil's work (It's still unclear if we can do that gradually. I'll comment on that later).

===ttaubert===

* Continued the fight against reflows.
* Added nsIDOMWindowUtils.getBoundsWithoutFlushing() ({{bug|878801}}).
* Landed support for reflow observers ({{bug|453650}}).
* Almost ready to enable newtab page preloading by default ({{bug|791670}}).
* Worked on getting rid of browser.stop() call in addTab() ({{bug|878747}}).
* Reviews.

===adw===
===markh===
===dolske===
===mconley===
===dao===
===mikedeboer===

===gijs===
See http://benjamin.smedbergs.us/weekly-updates.fcgi/user/gijs

===Unfocused===
===MattN===

(couldn't stay in meeting. Will update later)

===jaws===
See http://benjamin.smedbergs.us/weekly-updates.fcgi/user/jaws

===mixedpuppy===
http://benjamin.smedbergs.us/weekly-updates.fcgi/user/mixedpuppy

== UX Updates ==

Firefox/Meeting/28-May-2013

2013-05-28T17:42:58Z

P.A.: /* paolo */ Add status update

== Details ==

* Tuesdays - 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
{{conf|91337}}
* irc.mozilla.org #fx-team for backchannel
* "Firefox" Vidyo Room

== General Topics ==
== Friends of the Firefox team ==
''Give a shoutout/thanks to people for helping fix and test bugs.''
== Decisions needed/Action items ==
==Stand ups==
Suggested format:
* What did you do last week?
* What are working on this week?
* Anything blocking you?
Please keep your update to under 1 minute!
===gavin===
===paolo===
(details: http://benjamin.smedbergs.us/weekly-updates.fcgi/user/paolo)

Last week:
* Reviews on features added to the JavaScript API for downloads
* Documentation:
** [https://developer.mozilla.org/en-US/docs/Mozilla/JavaScript_code_modules/Downloads.jsm Downloads.jsm]
** [https://developer.mozilla.org/en-US/docs/Mozilla/JavaScript_code_modules/Promise.jsm Promise.jsm]
** [https://developer.mozilla.org/en-US/docs/Mozilla/JavaScript_code_modules/Task.jsm Task.jsm]

Next week:
* Continue with reviews on features added to the JavaScript API for downloads

===mak===
Last Week:
* Mostly reviews
This Week:
* Bring reviews queue to a manageable size
* Tracked regression {{bug|874407}} - new history displays incorrectly in Library window/sidebar
* Re-prioritized {{bug|769348}} - URLs auto-completed in address bar might use unexpected url prefix
* other pending patches if time allows

===enn===
===felipe===

* (copied from http://benjamin.smedbergs.us/weekly-updates.fcgi/user/felipe)
* {{bug|853389}} - AddonRepository - implementing Blair's feedback
* {{bug|875463}} - Implemented --run-until-failure option for mochitests
* {{bug|666809}} - started reviewing SecurityUI for e10s
* {{bug|812573}} - with the hotfix deployed it looks like we're seeing -20% people stuck on versions 10-16

===mano===
===ttaubert===

(details: http://benjamin.smedbergs.us/weekly-updates.fcgi/user/ttaubert)

* Backed out sessionstore changes because of add-on compatibility.
* Prototype for using speculative connect when restoring a session ({{bug|874533}}).
* Worked on reflow observers for docShells ({{bug|453650}}).
* Working on getting rid of an uninterruptible reflow in adjustTabstrip() when opening tabs ({{bug|876374}}).
* Improved tabopen animation by delaying pre-rendering of next newtab page ({{bug|875509}}).
* Eliminated reflow after swapping in preloaded newtab page ({{bug|875257}}).
* Still trying to enable about:newtab preloading by default ({{bug|794041}}).
* Reviews.

===adw===
===markh===

A little more on e10s form/autocomplete.

Started looking into background thumbnail service stuff. Learnt lots, solved nothing :)

Put together a relatively complex patch so console and standard handles work as expected in child processes.

===dolske===
===mconley===
===dao===
===mikedeboer===

===gijs===
Australis

Fixed:
* {{bug|874051}} - Fixing a11y test failures on UX
* {{bug|874601}} - Social API test failures (test finnickiness also fixed on m-c!)
* {{bug|874448}} - OS X dropmarkers
* {{bug|875163}} - new icons hugeness on OS X hidpi
* {{bug|873518}} - removing throbber (activity indicator) and individual cut/copy/paste buttons, plus a sneaky off-by-one error in customize mode

Reviewed:
* {{bug|823237}} - new tab button paths fixing tab close overflow cases
* {{bug|857886}} - tab image updates for OS X hidpi

WFM:
* {{bug|874819}} seems to have gone away after a merge; this means we now have green UX trees apart from the jetpack tests. Thanks to mconley and everyone else who helped fix this. If anyone breaks tests and introduces more orange, I will personally come and find you. :-)

(the jetpack tests depend on some SDK work as well as decisions regarding the addon bar, probably followed by more SDK work. I may help out with that if I have cycles within M6 still)

Other:

* {{bug|872455}} - Fixed some Social button weirdness, backported to Aurora
* {{bug|865806}} - Backed out, relanded with my crashfix to avert Aurora nightly crashiness

Next:

* {{bug|870849}} - (windows-only gap between titlebar and tabstrip; need to address Dao's review comments)
* {{bug|873501}} - make the customization code spacer/spring-proof
* {{bug|870014}} - address the issues mconley identified

I also need to organize one of my mentored bugs now that Matt has cleared one up so they can work on that one.

===Unfocused===
===MattN===
===jaws===
===cers===
===mixedpuppy===

* various intermittent test failure work
* investigation on improvements for webrtc apps/talkilla

== UX Updates ==
=== lco ===
* UX discussion on next steps for Boriss' New Tab page design
** New Tab tracking page: https://wiki.mozilla.org/Firefox/Features/New_Tab_Page_v2
** our intern, Jack is going to be building an addon prototype of the basic framework for us to play with internally (and for whoever wants to try it)
** at the same time, we're also in the process of coming up with concepts to show to users

* "Task Continuity"
** Brief summary + help us find a codename! - https://firefox-ux.etherpad.mozilla.org/TC-codename
** will be scheduling presentations soon...

Firefox/Meeting/21-May-2013

2013-05-21T16:52:52Z

P.A.: /* paolo */ Add status update