Mozilla Add-ons BlogSeptember 2015 Featured Add-ons

Pick of the Month: Facebook™ Disconnect

by morni colhkher
Facebook™ Disconnect is an efficient firewall to disconnect third-party websites from accessing to your Facebook.

Featured: Web Developer

by chrispederick
The Web Developer extension adds various web developer tools to the browser.

Nominate your favorite add-ons

Featured add-ons are selected by a community board made up of add-on developers, users, and fans. Board members change every six months, so there’s always an opportunity to participate. Stayed tuned to this blog for the next call for applications.

If you’d like to nominate an add-on for featuring, please send it to for the board’s consideration. We welcome you to submit your own add-on!

Mozilla Add-ons BlogTurning the queues around, and a new forum

We have an extraordinary community of contributors helping us succeed. Without their continuous support over the years, the add-on community wouldn’t be able to function. I want to highlight the great work some of them have been doing recently.

The Review Queues

Since we announced required signing for add-ons, all review queues have had significantly increased activity. The unlisted queues have been handled by Mozilla employee Andreas Wagner, who has been doing a heroic job keeping them mostly empty and performing most reviews within a day or two.

The listed queues have been handled mostly by volunteer reviewers. Due to so many more submissions by add-on developers, the queues ballooned to almost 800 add-ons awaiting review in early August.

Motivated by the slow review times and recent changes, we have received a record amount of reviewer applications. In the last 3 months, we have added 10 new reviewers. For reference, in all of 2014 there were only 11 reviewers added to the team.

Thanks to the efforts of our volunteer reviewers, new and veteran, the review queues now have a little over 300 add-ons awaiting review, a significant drop since August. In August alone, over 4000 reviews were performed, twice as many as July and way more than previous averages (usually ~1200 reviews per month).

I should also note that the majority of add-ons currently in the queues are flagged for admin review, which means they can’t be reviewed by volunteers. Since Andreas is busy with unlisted entries and I’m doing other work, those add-ons have been sitting in the queues unchecked for a while. We have two contractors who will join us in the coming days and will help us address this problem.

I’d like to highlight the incredible efforts done by Amir Faryar Zahedi and Teo Życzkowski; the two of them have contributed thousands of reviews in the last couple of months.

The New Forum

The migration to the new Discourse forum is now complete. The old phpBB forum has now been taken down and its former URL redirects to the new one. The add-ons category is, by far, the most active one in the community Discourse. So, thanks to all the people participating in the discussions.

Special thanks to Arenlor and Noitidart for being so helpful in the new forum, as well as our IRC channels and other places.

SUMO BlogWhat’s up with SUMO – 4th September

Hello, SUMO Nation! Hi there, universe! How are you doing today? We hope you’ve had a good week and invite you to take a look at what’s fresh and new in the world of SUMO.

Hello To All New Contributors!

If you joined us recently, don’t hesitate – come over and say “hi” in the forums!
Don’t forget that if you are new to SUMO and someone helped you get started in a nice way you can nominate them for the Buddy of the Month!

Contributors of the week

We salute you!

Last Monday’s SUMO Community meeting

Reminder: the next SUMO Community meeting…

  • …is going to take place on Monday, 7th of September. Join us!
  • If you want to add a discussion topic to upcoming the live meeting agenda:
    • Start a thread in the Community Forums, so that everyone in the community can see what will be discussed and voice their opinion here before Monday (this will make it easier to have an efficient meeting).
    • Please do so as soon as you can before the meeting, so that people have time to read, think, and reply (and also add it to the agenda).



Support Forum

  • Firefox for iOS is here!
  • We had awesome SUMO Day last week, thanks to you all! 90% questions answered across the board, 96% for Firefox questions, 42 participants from all around the globe!
  • The screensharing experiments results shall be made public soon!

Knowledge Base


  • (for iOS) IT’S HERE! In case you missed that ;-)
  • (for Desktop) Mark is currently AFK, but the latest updates are as follows:
    • 40.0.3 update was released last Thursday, including fixes for 2 security vulnerabilities, a Linux crash and minor compatibility issues
    • 40.0.3 brought a new bug, as well.
    • version 41 (due to be released in three weeks): will include add-on signing, removal of the browser.newtab.url preference and updates for sponsored tiles/sites
    • the 64-bit builds for Windows will probably delayed until Firefox 42, due to ongoing work on flash plugin sandboxing
  • (OS) All the devices in Botswana have sold out, so the team is working on providing more (hooray for all the new users in Botswana!)

Let’s finish the week with a bang, shall we? Who is cuter? Vote in the comments!

…see you next week!

Mozilla SecurityImproving Security for Bugzilla

The Bugzilla bug tracker is a major part of how we accomplish our mission of openness at Mozilla. It’s a tool for coordinating among our many contributors, and a focal point for community interactions. While most information in Bugzilla is public, Bugzilla restricts access to security-sensitive information, so that only certain privileged users can access it.

It is in the same spirit of openness that we are disclosing today that someone was able to steal security-sensitive information from Bugzilla.  We believe they used that information to attack Firefox users. Mozilla has conducted an investigation of this unauthorized access, and we have taken several actions to address the immediate threat.  We are also making improvements to Bugzilla to ensure the security of our products, our developer community, and our users.

The account that the attacker broke into was shut down shortly after Mozilla discovered that it had been compromised.  We believe that the attacker used information from Bugzilla to exploit the vulnerability we patched on August 6.  We have no indication that any other information obtained by the attacker has been used against Firefox users.  The version of Firefox released on August 27 fixed all of the vulnerabilities that the attacker learned about and could have used to harm Firefox users.

We are updating Bugzilla’s security practices to reduce the risk of future attacks of this type. As an immediate first step, all users with access to security-sensitive information have been required to change their passwords and use two-factor authentication. We are reducing the number of users with privileged access and limiting what each privileged user can do. In other words, we are making it harder for an attacker to break in, providing fewer opportunities to break in, and reducing the amount of information an attacker can get by breaking in.

Openness, transparency, and security are all central to the Mozilla mission. That’s why we publish security bugs once they’re no longer dangerous, and it’s why we’re writing a blog post about unauthorized access to our infrastructure. We have notified the relevant law enforcement authorities about this incident, and may take additional steps based on the results of any further investigations.

For more details, please see our FAQ document.

hacks.mozilla.orgImplementing Air Mozilla’s Related Events Feature

Editor’s note: It’s not often that we hear from web developers and software engineers at the start their careers here on the Hacks blog. This post is a great reminder of what it’s like.

Mozilla participates in Outreachy, and offers internship opportunities to bring women and other under-represented groups into the world of free and open source software. The application process for the upcoming round will open on September 22, 2015. The application deadline is October 26. Internship dates will be December 7, 2015 to March 7, 2016. If you’ve been thinking of applying, read this, be like Gloria – and go for it!

How I became a Mozilla intern

It was a spring night in Greece when I got the news I’d been selected by Mozilla to be an Outreachy intern. Outreachy is a project of the Software Freedom Conservancy that helps people from groups underrepresented in FOSS (free and open source software) to get involved by offering focused internship opportunities with a number of open source software organizations. That night, I was the happiest person in my town, I believe. I remember rushing to say a big thank you to my mentor Peter Bengtsson, before I got too overwhelmed with happiness to the point that I forgot to be grateful. It was a two-way street. I chose Mozilla and Mozilla chose me.

I started contributing to Air Mozilla in March 2015, by solving beginner-friendly bugs. Initially I didn’t want to apply at all, because there were too many wonderful contributors, and in some way I felt overwhelmed by how rigorous the process was. I told several people I won’t apply because I am afraid I won’t be getting it, and sometimes it is okay to be afraid, but it is not okay to be afraid of something you are capable of achieving to the point of sabotaging yourself.

After several pep talks, I went to view the list of the companies and decided to apply only for Mozilla. It will be a hit or miss, I told myself. I noticed it listed “Python” and I was aware that I didn’t know Python that well as it was something I self-studied briefly in the past, but I told myself to go ahead and try. Sometimes you need to do hard things to get the experience you want. Every expert was once a newbie. I went to check Bugzilla to see what I could fix. One bug looked very easy, so I thought I should work on that. That’s how it all started. Feedback after feedback, perseverance, pull, merge, merge conflicts, and getting a deeper understanding of how the code base functions made me able to contribute a lot more. One thing I loved about interning with open source is the fact that everything is open. I was asked to blog about what I worked on, and I didn’t need to hide anything that concerned it. Well… that doesn’t mean I shared my passwords too though! Passwords need to be protected and secret for a reason.

Getting to work on Air Mozilla

The internship day officially started on May 25th. I was told that after discussions I am being assigned to add a new feature. That new feature will act as a recommendation system suggesting similar events to Air Mozilla viewers while they view a specific event. Air Mozilla is a platform for Mozilla’s online multimedia presence that provides live and pre-recorded shows, interviews, news snippets, tutorial videos, and features about the Mozilla community.

That sounded fascinating. I wasn’t nervous at all, it seemed pretty interesting and I always wondered how those things worked, that’s until I started getting really stuck down the road. Then I realized the complexity of it. I had to either build my own algorithms and computations to do the job, or find an open source tool we could use instead of reinventing the wheel. After several days of research we decided Elastic Search seemed like a good fit. Elastic Search, is a search server. It has a function called “More Like This” and that helps you search for similar events based on your set parameters. I went and read the documentation of Elastic Search but to be honest, I had a very hard time navigating it. Mostly because I couldn’t find enough examples on how to use it with Python. At some point we decided pyelasticsearch might make things easier; it’s a Python library version of Elastic Search that has the functionalities we were looking for.

For a short recap, Elastic Search creates a mapping and indexes all the events on Air Mozilla. When you visit an event page, with the “More Like This” feature, we ask it to search the indexed events that are similar to the event you are currently viewing and return back the title, id, tags and its similarity scores on the back-end. For events to be considered related, their tags, channel and titles must be very much alike, but that’s not where we stop.

We also need to be able to set someone’s level of access: a person who is logged in as a Mozilla employee will have more access than an anonymous guest would. A logged in volunteer contributor will have more access than an anonymous guest, but less than a Mozilla employee. You get the idea. Each event has its own access level setting. Some events are private and limited to employees, while the majority of Air Mozilla events are accessible to the public or to members of the entire Mozilla community. Regardless, the Related Events feature lets people see a list of similar events, filtered for their level of access, with the most similar “related events” appearing on top.

Implementing Elastic Search

In the code below we are using the more_like_this (mlt) query. We break the tags and the titles into different queries because we want to boost the relevance score of each one to a different degree. In this case we want a similar title to have a higher relevance score than the similar tags. The field parameter is used to determine which field we are trying to run mlt against, the docs parameter is the documents we are trying to find similar events for. You can read more about this at the More Like This Query page.

mlt_query1 = { 
    'more_like_this': { 
        'fields': ['title'], 
        'docs': [ 
                '_index': index, 
                '_type': doc_type, 
        'min_term_freq': 1, 
        'max_query_terms': 20, 
        'min_doc_freq': 1, 
        'boost': 1.0, 
mlt_query2 = { 
    'more_like_this': { 
        'fields': ['tags'], 
        'docs': [ 
                '_index': index, 
                '_type': doc_type, 
        'min_term_freq': 1, 
        'max_query_terms': 20, 
        'min_doc_freq': 1, 
        'boost': -0.5, 


Below we are asking that one or more of the given mlt queries should match the documents, i.e., list of events:

query_ = { 
    'bool': { 
        'should': [mlt_query1, mlt_query2], 


Below, with request.user.is_active we are checking if the user is logged in and what their access level is. If the user is logged in as a volunteer the events that appear must not contain events that are restricted to Mozilla employees only.

If the user is logged in and is not a volunteer, that means they are Mozilla paid staff members. Their “related events” results should contain all events that are similar to the event we are currently viewing.

In the case of an anonymous user, the “related events” results must contain only events that are accessible to everyone.

if request.user.is_active: 
  query = { 
    'fields': fields, 
    'query': query_ 
  query = { 
    'fields': fields, 
    'query': query_, 
    "filter": { 
      "bool": { 
        "must": { 
          "term": {"privacy": Event.PRIVACY_PUBLIC} 

In the code above you see we used the more_like_this query along with a filter. More_like_this does return similar events based on title, tags and channels but it doesn’t ensure that the events returned are filtered by access level. So this is where “filter” comes in. It makes sure to filter the relevant events and allow only the ones the user can view based on their level of access.

With the use of cron jobs I completely delete and re-index the index for the week, and every 10 minutes we re-index (without first deleting) all events that have changed in the last 10 minutes.

AJAX queries were used to get the thumbnails and links of the related events. AJAX loads asynchronously, so running those queries doesn’t slow the pageload. When I view an event, I want it to load the page fully without waiting for Elastic Search to finish running the queries. Elastic Search queries run pretty fast but it still takes some time. Sometimes, it can be slow. The relevant events section appears under the events’ details. Ideally, someone watching an event won’t mind if there is a slight delay in the loading of the related events while they view the event, however a page that loads slowly as a whole can be frustrating. Through AJAX our Elastic Search queries can run in the background after the page has loaded.

In the screenshots below, you can see how it works. I have added red arrows to the title of event we are on and the title of the first recommended event. If you compare both pictures you can see how the events we are viewing, and/or recommending, relate to each other.

Example of Related Events for volunteers and staff

A second example of Related Events

Examples of related events for signed-in users


4 key things that make you realize how much you enjoyed your internship:

  • Your mentor made sure you took the right steps to learn a lot.
  • You feel that every portion of it, even the frustrating moments, made you grow not only in skills but as a person.
  • You were extremely happy you got it.
  • You are extremely sad it is ending.

That’s exactly how it’s been for me. I want to take a moment to thank Outreachy, my mentor Peter, and the other Mozillians I met on IRC and in email during my internship. Thank you for being helpful, welcoming, and for contributing to my learning experience.

What made the pensive ending of my internship bright and merry is a motto Mozilla takes pride in: Once a Mozillian, Always a Mozillian.

SeaMonkeyThe Next Beta…


We’re now spinning the next beta, dub “Ranch Flavor”…

No.  Not really.  We’re really spinning the next beta.  It’s SeaMonkey 2.38b1.

We are expecting a lot less problems, though the following issue (as of this writing) will persist:

1) Source tarball upload will most likely be done manually.  The reason is that the c-b source needed updating and the code that’s supposed to help us in this regard, hasn’t been reviewed (and ergo, pushed to c-*).  That isn’t a problem since I am at the terminal and readying myself to do it manually.

In the light of being transparent, at the get go for this beta, I goofed up (again) and had to restart the process.  I will just blame the gremlins this time. (Actually, I won’t.  I ‘fess.)

Anyway… will post news on the progress…



Firefox AppsFriend of Marketplace: Trishul Goel

Our newest Friend of Marketplace is Trishul Goel! Trishul is a web developer, tech evangelist, Marketplace code mentor, and community builder based in Jaipur, India.

He is also a Mozilla Rep, Marketplace app reviewer, and India Task Force member. When he’s not contributing in all these areas within Mozilla, he enjoys exploring on his motorcycle. He feels “awesome and super excited” about being the newest Friend of Marketplace, and we feel awesome and super excited that he is a member of our community.

Thank you to everyone who contributed to the Marketplace codebase in August, including several brand-new contributors! If you’re interested in contributing code, please check out our new onboarding process.

The new contribution wiki for September is now available. Please check it for projects that might interest you, and be sure to report your contributions as well as the contributions of others in your community!

Air MozillaWeb QA Weekly Meeting

Web QA Weekly Meeting This is our weekly gathering of Mozilla'a Web QA team filled with discussion on our current and future projects, ideas, demos, and fun facts.


I say… I say…


This is the moment we have all been waiting for!


Yes.  Out!  After the long delay… we finally have a SeaMonkey release that we can call our own!


I am stunned.  Really stunned.  After so many screwups (no thanks to me), we finally HAVE A RELEASE!

Next stop: SeaMonkey 2.38b1.


Meeting NotesMobile: 2015-09-02


Tracking Review


  • Next Build:
ID Summary Status Assigned to Last change time
1016555 Disable OCSP checking for certificates covered by OneCRL ASSIGNED David Keeler [:keeler] (use needinfo?) 2015-08-28T15:55:13Z
1170651 crash in js::jit::GetPropertyIC::update(JSContext*, JS::Handle<JSScript*>, unsigned int, JS::Handle<JSObject*>, JS::MutableHandle<JS::Value>) NEW Kevin Brosnan [:kbrosnan] 2015-08-06T17:42:20Z

2 Total;
2 Open (100%);
0 Resolved (0%);
0 Verified (0%);


  • Next Build:
ID Summary Status Assigned to Last change time
1137898 Use a hierarchical pattern for computing version codes ASSIGNED Nick Alexander :nalexander 2015-09-02T19:23:36Z
1156553 Tab queue makes captive portal use annoying ASSIGNED Martyn Haigh (:mhaigh) 2015-08-20T17:14:28Z
1172359 (Android) WebRTC crashes when microphone is enabled UNCONFIRMED Randall Barker [:rbarker] 2015-08-20T17:58:02Z
1177414 Queued tabs stall on load ASSIGNED Martyn Haigh (:mhaigh) 2015-08-20T18:14:05Z
1186020 Download icon is very dark NEW Michael Comella (:mcomella) 2015-09-03T00:09:12Z
1190301 Refine appearance of tab audio indicator NEW Michael Comella (:mcomella) 2015-09-03T01:01:39Z
1191330 Autophone – July 31 regression in Throbber start nexus 5 Android 4.4 NEW GaryChen [:GaryChen][:PYChen][:gchen][:陳柏宇] 2015-08-06T17:35:10Z
1191918 Round battery level to integers (or tens?) to mitigate finger printing NEW James Willcox (:snorp) ( 2015-08-06T17:40:13Z
1194049 NsdManager increases power consumption NEW Gary Chen [:xeonchen] 2015-09-01T03:15:17Z
1198084 Tab audio indicator is not a11y friendly NEW :Margaret Leibovic (PTO Aug 27 – Sept 14) 2015-09-03T01:42:00Z
1200665 Update to SUMO URL on restricted profile Splash screen (internally known as KidFox) ASSIGNED Sebastian Kaspari (:sebastian) 2015-09-02T21:38:40Z

11 Total;
11 Open (100%);
0 Resolved (0%);
0 Verified (0%);


  • Next Build:
ID Summary Status Assigned to Last change time
776030 Allow Fennec to use the AsyncPanZoomController NEW Randall Barker [:rbarker] 2015-09-02T19:15:23Z
886969 Fennec allows scrolling of pages with overflow:hidden on the body element NEW Randall Barker [:rbarker] 2015-09-01T14:29:56Z
1047127 Panning very stuttery on this page with overflow-x NEW 2015-06-10T18:43:44Z
1131084 Can not mirror tab to Chromecast device NEW Randall Barker [:rbarker] 2015-06-17T18:31:14Z
1144534 fuzzy/bad looking text depending on scroll position, or fuzziness coming and going NEW 2015-08-06T17:41:46Z
1168867 Size of new Gecko selection carets doesn’t take font inflation into account NEW 2015-07-31T02:27:20Z
1171860 Tapping the tab queue notification will open the link in normal browsing with “Open links in Private browsing” pref enabled NEW 2015-08-20T17:15:28Z

7 Total;
7 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs. Make sure friends also get awarded a badge. New contributors are highlighted in bold. Want to update this section?

  • mzpppp fixed bug 1199981 – Cannot launch due to dynamic loading error.
  • Ahmed Khalil fixed bug 1180287 – Hide client records that are likely to be duplicates or stale
  • Dominique Vincent [:domivinc] fixed bug 1190332 – Zoomed View appears in textareas
  • Dominique Vincent [:domivinc] fixed bug 1191041 – Increase the likelihood of “zoomed view” triggering for small elements but decreased the likelihood for large elements
  • Garvan fixed bug 1195854 – TelephonyManager.getNeighboringCellInfo() is deprecated in API level 23 (Android 6.0)
  • Kartikaya Gupta ( fixed bug 1197228 – Transparent BrowserSearch when searching on Android 2.3 phone when web content is in background
  • Kartikaya Gupta ( fixed bug 1199768 – Long-pressing at top of page with URL bar hidden triggers URL bar context menu
  • Kartikaya Gupta ( fixed bug 1200402 – Reader mode pages can get load with a desktop mode viewport
  • Mantaroh Yoshinaga[:mantaroh] fixed bug 1177510 – HTML input element’s max / min attribute does not work on Fennec.
  • Mark Finkle (:mfinkle) fixed bug 1078432 – Use Android print service to enable cloud printing
  • Mark Finkle (:mfinkle) fixed bug 1129614 – Regression: Sometimes thumbnails in the tabs drawer are not updated, they expire
  • Mark Finkle (:mfinkle) fixed bug 1196897 – Integrate Switchboard with onboarding for A/B testing
  • Mike Taylor [:miketaylr] fixed bug 976616 – Support dynamic viewport changes (changing meta viewport tag from JavaScript)
  • Myk Melez [:myk] [@mykmelez] fixed bug 1197920 – TypeError: DOMApplicationRegistry.getAll is not a function on Fennec
  • [:fabrice] Fabrice Desré fixed bug 1180358 – Add the b2gdroid sub-product
  • [:fabrice] Fabrice Desré fixed bug 1180461 – Package gaia in b2gdroid
  • [:fabrice] Fabrice Desré fixed bug 1181209 – [b2gdroid] Make it boot!
  • [PTO Until 02/Sep] Jean-Yves Avenard [:jya] fixed bug 1188871 – Loading a page with media content on hangs indefinitely

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 2 minutes!

James W. (snorp), Android Platform Team (Jim, Randall, Eugen, Randall)

  • I’m working on updating our tile size and pool size to account for modern devices. Right now we barely cache enough tiles to even cover the screen on many devices, and with quad HD ones coming out soon (or already?) it will get worse. Once fixed, this should help alleviate checkerboarding some. Paint suppression work also continues, need to refactor a bit. I’m also looking into a hack using ‘screenrecord’ for the devtools guys.
  • Jim continues on JNI changes. We will soon be opening the browser window with a JNI call instead of the commandline, which allows us to easily hook up to the GeckoView that requested it.
  • Dylan is working on some bugs, including some JNI stuff
  • Randall is making good progress on APZ. He figured out some of the causes of bad event coordinates, and continues to fight through more of the same. It feels like we’re getting close to solving all of the really bad stuff here.
  • Eugen is fixing some media bugs, including getting hardware-decoded VP8/VP9 to work with MSE. This is important because YouTube really wants to use that. He also has some results from a tool he’s working on to time how long JS imports take. It is depressing. 2.9s to import all of our stupid JS on startup!



  • Landed video sandboxing work
  • Followups for intermittent oranges
  • Attempted to land new TP/SafeBrowsing prefs, needs Talos update


  • bug 1037560 Safebrowsing pleasereset resets all tables
  • bug 1175562 Persist last update time for updates/gethash completion
  • Working on other e10s + WebRTC bugs

Brian Nicholson

  • bug 1197465 – Session restore sends along a localhost referrer
  • bug 1191687 – Opening some links with VoiceOver shows context menu
  • Swift 2.0
    • bug 1199808 – Fix Client build optimization settings
    • bug 1199368 – Sites don’t load from entered URLs or top sites
    • bug 1199836 – Session restore broken after Swift 2.0 changes
    • bug 1199849 – Reader View broken after Swift 2.0 changes
    • bug 1200715 – Swift 2.0 crash when selecting Reader panel
    • bug 1199814 – Invert nil try? assertion in SearchEngines.swift
  • Briefly looked into using window.find() for Find in Page



  • First run and Switchboard A/B testing




Last week :(


  • 1196950 – Use font downscaling for (possibly) truncated strings
  • Integrate Home Feeds add-on to Fennec


  • Home Feeds cleanup
  • Home Feeds network performance






  • Updated 3-dot menu & add tab icons to Material design & cleaned up menu




  • Writing about deXULification.
  • Writing about bookmarks. Comments, please.
  • Reviews.
  • Triage, meetings, 1:1s, etc.


  • Landed build system bits of b2gdroid \o/
  • Sign in to Firefox Accounts on the web
    • bug 1191067
    • First round of patches will land shortly, thanks to sebastian for reviews
    • Meeting with rfkelly, markh, zaach re: Device Handshake to determine capabilities with fxa-content-server
    • Meeting with stomlinson, zaach re: context=fx_fennec_v1 requirements
    • Discussed “new account” and “re-linked account” UX with antlam
      • Approach will be to briefly animate notification icon, then clear notification after first Sync
    • Second round of patches up for review in next couple days
  • android:versionCode
    • bug 1137898
    • patch is reviewed and about to land
    • let me know about local or remote failures to push APKs to device (this should not happen)
    • plan to uplift to Aurora immediately, so that it’s in Beta (and the Play Store) in ~3 weeks
  • pinning Android version dependencies using AAR files at configure time
    • bug 1108782
    • will help us keep build working across Google upstream changes
    • first round of patches got very helpful glandium feedback
    • thanks to Sebastian for testing \o/
  • also helping jrconlin land GCM and Push Notifications bridge



  • PTO Friday and next week
  • bug 1194338 – Support for downloadable content / fonts
    • bug 1200291 – Implement simple package registry for downloadable content
  • “Project KidFox” bugs


Martyn Haigh

  • UK bank holiday Monday just gone.
  • Looking at set a homepage





  • Fixing 1.0.5 issues
  • Resolving Swift-2.0 crashes after master merge
  • Working on a a small feature for reorganizing home panels

James Hugman


  • Working on addons/WebExtensions runtime; got minimal ‘Cloud To Butt’ working.
  • background pages & manifest.json parsing work in progress.


  • Swift 2.0, FxA tests hitting live servers. I do not like this arrangement.
  • Bugs are coming! from New Zealand!





  • Saved search suggestions have landed. Have an opinion? LMK


  • Swift 2.0 now compiles!




  • Upcoming
    • Follow up with Awesomescreen search bugs, Hello, and TV
    • Connected reading list co-ordination for Android
    • bug 1195721: Set a Homepage UX
    • bug 1069035: Settings re-org (Research pending)


  • Pocket integration mocks, continued (Android and iOS)

Still working on:

  • bug 1186013 Offer to open URLs on the clipboard when entering Firefox
  • bug 1162778 When disconnecting account, give user option to clear browsing data
  • bug 1193363 Determine how to maintain relationship between panels and webview
  • bug 1197337 Improve clarity of on-boarding tour first slide string (String chosen)


  • bug 1145228 Allow collapsing and expanding Synced (Remote) Tabs clients
  • bug 1182303 Firefox iOS susceptible to infinite alert loops
  • bug 1196950 Use font downscaling for (possibly) truncated strings



Feature Focus


  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 99998
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 99998
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 99998
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 99998
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 99998
    • UK/London: +44 (0)207 855 3000, x92 Conf# 99998
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
  • #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2015-09-02

Schedule & Progress onUpcoming Releases (Liz/Sylvestre/Lawrence/Ritu)

  • 40
    • Intent to ship an hotfix for bug 1197944
      • change the value of pref “network.auth.allow-subresource-auth” from 1 to 2
  • 41
    • Desktop and Mobile 41.0b6 pushed on 09/01
    • Gtb Desktop 41.0b7 Thursday 09/03

Feedback Summary (Rob/Tyler/Matt)

No updates

Questions, Comments, FYI

New meeting schedule:

Planning Meeting Details

  • Wednesdays – 11:00am PT, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Finch Conference Room
  • #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

SeaMonkeySierra Mike…

“This is Release approach.  You are cleared for approach on runway 32 right.”

“Roger… Runway 32 right.”

With that intro, I’d like to say that we are pretty much close to release.  Just only a couple of things to do.  Once the website is updated, I, or someone else, will announce the release.

After that, I’ll be prep’ing for SeaMonkey 2.38beta1.


PS: It’s kind a pretentious, sorry.  Just very happy that we’ve finally gotten to this point and it only took a week.

Mozilla Web DevelopmentNode.js static file build steps in Python Heroku apps

I write a lot of webapps. I like to use Python for the backend, but most
frontend tools are written in Node.js. LESS gives me nicer style sheets, Babel
lets me write next-generation JavaScript, and NPM helps manage dependencies
nicely. As a result, most of my projects are polyglots that can be difficult to

Modern workflows have already figured this out: Run all the tools. Most
READMEs I’ve written lately tend to look like this:

$ git clone
$ cd git
$ pip install -r requirements.txt
$ npm install
$ gulp static-assets
$ python ./ runserver

I like to deploy my projects using Heroku. They take care of the messy details
about deployment, but they don’t seem to support multi-language projects easily.
There are Python and Node buildpacks, but no clear way of combining the two.

Multi Buildpack

GitHub is littered with attempts to fix this by building new buildpacks.
The problem is they invariable fall out of compatibility with Heroku. I could
probably fix, but then I’d have to maintain them. I use Heroku to avoid
maintaining infrastructure; custom buildpacks are one step forward, but two
steps back.

Enter Multi Buildpack, which runs multiple buildpacks at once.

It is simple enough that it is unlike to fall out of compatibility. Heroku has a
fork of the project on their GitHub account, which implies that it will be
maintained in the future.

To configure the buildpack, first tell Heroku you want to use it:

$ heroku buildpacks:set

Next, add a .buildpacks file to your project that lists the buildpacks to run:

Buildpacks are executed in the order they’re listed in, allowing later
buildpacks to use the tools and scripts installed by earlier buildpacks.

The Problem With Python

There’s one problem: The Python buildpack moves files around, which makes it
incompatible with the way the Node buildpack installs commands. This means that
any asset compilation or minification done as a step of the Python buildpack
that depends on Node will fail.

The Python buildpack automatically detects a Django project and runs
./ collectstatic. But the Node environment isn’t available, so this
fails. No static files get built.

There is a solution: bin/post_compile! If present in your repository, this
script will be run at the end of the build process. Because it runs outside of
the Python buildpack, commands installed by the Node buildpack are available and
will work correctly.

This trick works with any Python webapp, but lets use a Django project as an
example. I often use Django Pipeline for static asset compilation. Assets
are compiled using the command ./ collectstatic, which, when properly
configured, will call all the Node commands.

export PATH=/app/.heroku/node/bin:$PATH
./ collectstatic --noinput

Alternatively, you could call Node tools like Gulp or Webpack directly.

In the case of Django Pipeline, it is also useful to disable the Python
buildpack from running collectstatic, since it will fail anyways. This is done
using an environment variable:

heroku config:set DISABLE_COLLECTSTATIC 1

Okay, so there is a little hack here. We still had to append the Node binary
folder to PATH. Pretend you didn’t see that! Or don’t, because you’ll need
to do it in your script too.

That’s it

To recap, this approach:

  1. Only uses buildpacks available from Heroku
  2. Supports any sort of Python and/or Node build steps
  3. Doesn’t require vendoring or pre-compiling any static assets


Mozilla Add-ons BlogAdd-ons Update – Week of 2015/09/02

I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.

The Review Queues

  • Most nominations for full review are taking less than 10 weeks to review.
  • 110 nominations in the queue awaiting review.
  • Most updates are being reviewed within 6 weeks.
  • 69 updates in the queue awaiting review.
  • Most preliminary reviews are being reviewed within 10 weeks.
  • 149 preliminary review submissions in the queue awaiting review.

The unlisted queues aren’t mentioned here, but they are empty for the most part (there are actually a couple hundred add-ons awaiting review there but they are awaiting a bulk-review tool that is being worked on, since they belong to a couple of large sets of almost identical add-ons). We’re in the process of getting more help to reduce queue length and waiting times for all queues.

If you’re an add-on developer and would like to see add-ons reviewed faster, please consider joining us. Add-on reviewers get invited to Mozilla events and earn cool gear with their work. Visit our wiki page for more information.

Firefox 41 Compatibility

The compatibility blog post has been up for a while. The compatibility bump should be run soon.

Firefox 42 Compatibility

Expect the blog post to come up sometime next week.

As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition (formerly known as Aurora) to make sure that they continue to work correctly. End users can install the Add-on Compatibility Reporter to identify and report any add-ons that aren’t working anymore.

Add-ons Forum

As we announced before, there’s a new add-ons community forum for all topics related to AMO or add-ons in general. The old forum is now gone, and just redirects to the new one.

Extension Signing

The wiki page on Extension Signing has information about the timeline, as well as responses to some frequently asked questions. The new add-on installation UI and signature warnings are now enabled in release versions of Firefox.


Electrolysis, also known as e10s, is the next major compatibility change coming to Firefox. In a nutshell, Firefox will run on multiple processes now, running content code in a different process than browser code. This should improve responsiveness and overall stability, but it also means many add-ons will need to be updated to support this.

If you read Kev’s post on the future of add-on development, you should know there are big changes coming. We’re investing heavily on the new WebExtensions API, so we strongly recommend that you start looking into it for your add-ons. If you have requests for new APIs, please suggest them in the uservoice forum.

Air MozillaQuality Team (QA) Public Meeting

Quality Team (QA) Public Meeting This is the meeting where all the Mozilla quality teams meet, swap ideas, exchange notes on what is upcoming, and strategize around community building and...

Air MozillaProduct Coordination Meeting

Product Coordination Meeting Duration: 10 minutes This is a weekly status meeting, every Wednesday, that helps coordinate the shipping of our products (across 4 release channels) in order...

hacks.mozilla.orgScroll snapping explained

Have you ever tried to snap your page’s contents after scrolling? There are many JavaScript libraries out there providing this functionality. Here are a few examples:

As this is a common use case related to page layout and behavior, the W3C has published a pure CSS approach to scroll snapping.

CSS scroll snapping, (available since July’s Firefox 39 release), allows you to control where to stop on an overflowing element when it’s scrolled. This lets you section your page into logical divisions and thus create smoother, easier-to-interact-with user interfaces. Touch devices in particular benefit from this feature, where it is easier for people to pan through pages instead of tapping through hierarchical structures.

Image gallery

Image galleries are surely the most common use case for scroll snapping: Users can flip through the images, viewing one image at a time by swiping or scrolling the page. So let’s see how this can be achieved with the new properties:

img {
  width: 200px;

.photoGallery {
  width: 200px;
  overflow: auto;
  white-space: nowrap;
  scroll-snap-points-x: repeat(100%);
  scroll-snap-type: mandatory;

The related HTML code looks like this:

<div class="photoGallery">
  <img src="img1.png"><img src="img2.png"><img src="img3.png">

Here’s a live demo:

See the Pen wKvYdK by Potch (@potch) on CodePen.

The code above creates a simple image gallery with three images, which can be scrolled through horizontally.

In this case the size of the images and their containing <div> are set to 200 pixels. The overflow: auto; displays a scrollbar on clients that support it. white-space: nowrap; serves to keep all images horizontally aligned. The definition “scroll-snap-points-x: repeat(100%);” sets a repeated horizontal snap point at 100% of the viewport width of the container <div>, in this case at 200 pixel intervals. Setting scroll-snap-type: mandatory; has the effect that snapping is forced. The viewport will always snap at a snap point, so the display will never stay in between two images.

Item lists

You’ve probably seen plenty of online product pages listing different features with an image of each feature and a description next to it, or an interface displaying a series of user testimonials.

In these cases, scroll snapping lets you align the sections so that maximal display space is used.

.features {
  width: 400px;
  height: 250px;
  padding: 0;
  overflow: auto;
  scroll-snap-type: proximity;
  scroll-snap-destination: 0 16px;

.features > section {
  clear: both;
  margin: 20px 0;
  scroll-snap-coordinate: 0 0;

img {
  width: 50px;
  height: 50px;
  margin: 5px 10px;
  float: left;

section:last-child {
  margin-bottom: 60px;

And here’s the related HTML code:

<div class="features">
  <section id="feature1">
    <img src="feature1.png"/>
    <p>Lorem ipsum...</p>
  <section id="feature2">
    <img src="feature2.png"/>
    <p>Lorem ipsum...</p>

Here’s a live demo:

See the Pen NGWOjN by Potch (@potch) on CodePen.

When you scroll within the example above, each feature section is positioned so that the top is aligned with the top of the viewport to display as much text as possible. This is achieved by applying scroll-snap-coordinate: 0 0; to the sections. The two zeros refer to the x and y coordinates of the element where it will snap to the container element. scroll-snap-destination: 0 16px; defines the offset position within the container element to which the inner elements should snap. In this case, that’s 16 pixels below the top of the container so that the text at top of the section has some margin at the top.

In addition to the properties currently defined within the CSS Scroll Snap Points specification, Gecko implements the additional properties scroll-snap-type-x and scroll-snap-type-y, for setting the snap type individually per axis. These long-hand properties may be added to the specification in the future.

Currently snap points can only be set through coordinates, either referring to the start edge of the container element or the ones within it. Sometimes this requires some calculation to set them at the right position. Future extensions to this feature may extend the functionality to be able to set snap points on the box model instead, which would make it easier to place them. There’s already a discussion about this within the www-style mailing list.

Has this new functionality caught your interest? Then it’s time to give it a try! And if you don’t remember how to use the different properties, you can always refer to the documentation on MDN.

SeaMonkeySource tarball update

This manual generation wasn’t as hairy as I thought it’d be.  Maybe fuzzy… but not hairy.

Just wanted to mention that the source tarball has been uploaded to the release candidates section.


SeaMonkeyGood News… bad news.. (part deux)

We’re nearing the final stretch in that the updates succeeded… the update verifications were good (though the osx64 one is still pending).

So all in all, the updates part seemed a lot less hectic than the earlier part; but then again, that’s only because Callek was there to help.

So we’re nearly set for the final release.

That’s the good news part of this post.

The bad news is that even though the source step was green… it failed. (Reminds me of the ‘it’s so good.. it’s bad’, but I digress).  The source tarball was not uploaded.  (*that’s my fault again *sigh**).  It required a source change in comm-release that I overlooked (I assumed that suite’s was |make upload| and not |make source-upload|).  It ends up that |make source-upload| *was* needed, but that needs to be changed in suite/

(Thanks to the SeaMonkey Gentoo package maintainer for pointing out my faux-pas.)

That said, I will need to do that manually.  (*Damn well serves me right for choking up the source step.*)




Firebug BlogFirebug 2.0.12

The Firebug team released Firebug 2.0.12. This is a maintenance release ensuring compatibility with latest Firefox releases.


The beta channel on AMO is not updated due to a new signing process (support for beta channels is currently in open beta phase). It’s recommended to use standard release channel on AMO (if you don’t know what AMO beta channel is, you are most likely using the right release channel).


Firebug 2.0.12 is compatible with Firefox 30 – 42

Firebug 2.0.12 fixes the following issues: 7916, 7922, 7928, 7917, 7923, 7931, 7918.


Please post feedback in the newsgroup, thanks.

Jan ‘Honza’ Odvarko


Meeting NotesChannel: 2015-09-01


sylvestre, lmandel, lizzard, kbrosnan, dougt, ritu, kairo, milan, bhearsum, rrayborn, jlund, ashughes, roland

Schedule Update

  • 41
    • Fennec: Beta6 pushed to play store
    • Desktop: QE Sign offs done, waiting for push to beta-cdntest and update testing
    • EARLY_BETA_OR_EARLIER just landed (will be in beta 7)
  • 40
    • Nothing to report!


  • No updates.



  • Overall rate: 4.1; browser: 1.2, content: 2.9
  • Did go down, then rise again, probably bug 1199794 to a good part (see below)
  • Nightly miraculously has a slightly better (lower) crash rate than Dev Edition now


  • Overall rate: 0.94 (rising somewhat)
  • bug 1199794 (current_stream_delay) is 3.7% of 41.0b5 data, fix uplifted for b6
  • bug 1158189 (HTTP shutdownhangs) is 2%, still hoping to get bug 1152046 as that hopefully will help
  • bug 1178271 (dom::Promise::Settle) is 1.4%, still unclear what’s up there
  • bug 1196696 (MediaFormatReader::DecoderData::ResetDemuxer) is 0.9%, patch in b6


  • Overall rate: 0.9 (unchanged)
  • bug 1198884 (ubuntu, GStreamer 1.0)
  • bug 1189940 (Nvidia) still #1 Win10 issue


  • Beta rate ~3, Release rate 1.3
  • Release rate has dropped over the last few months from 1.7-1.8 to 1.3



  • push to beta slightly delayed due to issues with test CI machine


  • disabling e10s for the last one/two weeks of the aurora cycle?
    • people might be confused by disabling e10s
    • we want a clean beta 1
    • action: Sylvestre will contact the e10s team to discuss with them

Special Topics

Aurora/Beta Feature Review

  • Allow Heartbeat to target Private Browsing Mode users (bug 1184338)
    • Partially Landed in 41.0b6
    • Server-side changes are next
  • Importing Edge cookies, favorites/bookmarks (bug 1192032)
    • Landed in 41.0b6
    • Softvision found an issue with this: bug 1200598
  • MSE blanket uplift not landed yet: found a regression ( )

Post-Mortem (Tues 2wks from GA Release)

Channel Meeting Details

Video/Teleconference Details – NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 99951 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99951 (US)
  • Vidyo Room: ReleaseCoordination
  • Vidyo Guest URL

Meeting NotesFirefox Status: 2015-09-01

Actions from last meeting

  • None

General Topics / Roundtable

(tips/tricks/FYI, productivity improvements, industry news)

Friends of the Firefox team

(Give a shoutout/thanks to people for helping fix and test bugs.)

  • Resolved bugs (excluding employees):
    • More than one bug fixed:
      • Aryx [:archaeopteryx][:aryx]
      • Marina Rodríguez [:mai]
      • Steffen Wilberg
      • aleth [:aleth]
      • rthyberg

Project Updates

Go Faster

  • Support for loading system add-ons shipped with the application should land this week
  • Updating system add-ons mid-cycle to follow


  • Working on a visual refresh of the entire UI – desktop & standalone.
  • Next up: if you click your own link, we’ll open it up in a conversation window as if you’d clicked it from the Hello menu.


  • Deploying a heartbeat survey within the next week on 41+ to measure data on private browsing if the user opts-in to via the info bar. The survey will get a baseline in 41 and compare that with 42+ which has tracking protection.
  • A diary study will also soon be taking place to get a different type of feedback on tracking protection
  • Intern presentation: “Firefox Helps You Log In” Presented by Bernardo Rittmeyer
    • This is the last week of Bernardo’s internship.


  • Working on final fixes to let search suggestions ride the trains, accessibility is being a particular issue

Windows 10

  • Continuing work on data migrators from Edge. Check QA/Firefox_migrators if you’re ever interested in knowing what we can migrate and to find related bugs.


Meeting NotesSeaMonkey: 2015-09-01


  • Who’s taking minutes? -> TBD
  • Nominees for Friends of the Fish Tank:
    • TBD

Action Items

(who needs to do what that hasn’t been recorded in a bug)
We should assign people to the open items.


  • Need to port Sync 2.0 to SeaMonkey – IanN to talk to ewong about options.


  • bug 1198340 The carousel within Add-On Manager can be used for SeaMonkey specific content. TO DO: Find out what sort of format AMO needs for the carousel. Get our webdev person to create necessary content. Submit content for upload to AMO.
  • bug 1121281 tracks the RelEng automation migration off CVS. Everything is now in a single repo, patches for using that new repo are awaiting a review from Callek.


Status of the SeaMonkey Buildbot Master and Tree

  • Notes:
    • Windows nightly trunk builds are unavailable due to various bugs such as bug 1092468 and bug 1108970. Migrating our Windows builders to Win2008 and our compiler toolchain to VS2013 would likely solve this and other bustages.
    • There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
    • Buildmaster is up and running, and produces en-US builds, see 9/16 meeting’s Friends of the Fish Tank. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
    • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey because they aren’t uploaded to AMO. The solution requires changes in SeaMonkey RelEng (and possibly AMO).
    • For various reasons we don’t have a working SeaMonkey Treeherder.
    • wrt bug 1155011, we already have a Soccoro token. The patches on bug 1155013 require approval and then pushed and the work-around patches backed out.
  • [1st September 2015]
    • All trees:
      • Windows platform still busted due to needing Win2008R2 installed.
      • We have a loaner which ewong is working on (see blog for more information).
    • comm-central & comm-aurora:
  • See RelEng page for the RelEng status history.

Release Train

  • SeaMonkey 2.33.1 was released on 23 March and is the most recent release.
  • Useful Firefox Release Schedule link: Releases Scheduling
    • merge day was 10 August as scheduled
  • SeaMonkey 2.35 release:
    • (ewong) is expected this week, along with, hopefully, 2.38 beta. Due to certificate server issues, we need to do a beta release from 2.38 at the latest (2.39 would have problems).
SeaMonkey 2.35 Release
  • We plan to release SeaMonkey 2.35 asap in August. We missed this deadline but should have a release this week (September).
    • For windows builds, we have a loaner win machine from Mozilla for us (i.e. ewong) to do manual window builds.
    • (ewong): Suggesting early September, but we shall see.
  • I have done nothing on the Nightlies/Aurora as I’ve been concentrating on getting Win32 builds and repacks done.
    • The Win32 2.35 release builds was completed on Friday (28th August 2015).
    • The 2.35 l10n Win32 repacks were done on late Sunday/Early Monday (30th/31st August 2015)
      • The busted l10n linux/osx repacks (ca, fi, ja(linux), ja-JP-mac(osx), sv-SE, pt-PT) were retriggered on Monday 31st August 2015.

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • We are looking for a new place to host the Addon Compatibility Listings for the Add-on Converter in order to make it easy to maintain and to serve as the main database for the AMO browsing extension in the future. The details are in this post.
  • Firefox & Thunderbird Add-on Converter for SeaMonkey
    This tool goes a little further beyond simply modifying install.rdf – it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there’s only so much an automated tool like that can do.
    • Lemon Juice continues to improve his already impressive Addon Converter. The source is now available on GitHub [1].
    • looking for a better(?) home for extension-converter pages, along with a way to track successful and conversion-failed add-ons, and respective integration into SeaMonkey by add-on or manager overlay [2], bug 1145026.
    • Rainer Bielefeld will no longer update the list of Firefox addons that have been successfully converted by the Addon Converter. — Rrbd (talk) 09:59, 16 August 2015 (PDT)
    • Ratty filed bug 1130390 to add a link on to the Firefox & Thunderbird Add-on Converter for SeaMonkey.
  • The Thunderbird team is now shipping Lightning with Thunderbird. IanN will work on shipping lightning too. Related bugs:
    • bug 516026 Integrate Lightning Into SeaMonkey by Default and Ship SeaMonkey with Lightning Enabled
    • bug 1130854 Package Lightning with Thunderbird for c-c and c-a builds.
    • bug 1113183 Integrate Lightning Into Thunderbird by Default.
    • bug 1130852 Add opt-in dialog to promote Calendar integration [Thunderbird].
  • Proposed replacement for Venkman for shipping with SeaMonkey: Tiny JavaScript Debugger. TinyJSD is a JavaScript debugger for privileged code running Mozilla products like Firefox, Thunderbird, SeaMonkey. It serves to debug the application as well as extensions written in JavaScript.
    • IanN filed bug 1133723 Investigate options for replacing Venkman with the TinyJSDebugger.

2.x (Last, Current, Next)


open tracking (0)
tracking requests (1)
targeted (0)
fixed (21)


open tracking (1)
tracking requests (2)
targeted (0)
fixed (45)


open tracking (0)
tracking requests (0)
targeted (0)
fixed (7)

  • SeaMonkey 2.36 Release Notes (yet to come)
  • SEAMONKEY_2_36_RELEASE_BRANCH has been established in comm-release.
  • [Ratty] We will probably skip to SeaMonkey 2.38 after releasing SeaMonkey 2.35.
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
  • Mozilla-central bugs that affect us:
    • Change to Safe Browsing
    • Change of printing API bug 1146454 needs to be ported, immediate bustage was fixed in bug 1190344.
      • IanN is working on migrating comm-central to the new API [bug 1195863].
    • Firefox is currently changing styles of several Toolkit pages
      • already affected: config.xul for about:config, bug 1125636
      • Toolkit meta bug for about:* pages: bug 1097111 – SeaMonkey tracking in bug 1133743
      • Modern may need updating as IDs are changing, Default needs forking if we want to roll back to previous styles
      • Fallout thus far: bug 1133380 about:privatebrowsing (Default), bug 1133582 about:config (Modern)
      • further work to separate function from style in CSS for about:privatebrowsing in bug 1178008 (3rd-party themes)
      • Ratty restored about:privatebrowsing UI to before it was messed up by Project Chameleon styles [bug 1192276]
    • Our front end Sync UI needs to be updated as the old backend has gone away. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
      • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
      • bug 1003434 Add support for about:sync-progress.
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • bug 769764 move proxy resolution to separate thread and remove sync api. Tracked in:
      • MailNews bug 791645 Rewrite calls to synchronous nsIProtocolProxyService::DeprecatedBlockingResolve with Async code before DeprecatedBlockingResolve disappears as well.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox and Thunderbird have migrated to jsdownloads.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned. Neil has a WIP patch on hand.
    • Removal of SSL 3.0 support after POODLE Attack with 2.36, see bug 1106470.
      • bug 1137991 has removed SSL 3.0 checkbox from SSL preferences
      • bug 1149581 covers removal of the related strings
      • Firefox has proceeded with the removal in 39.0 given that Chrome goes the same way [3]
    • We’ve picked up he default for security.tls.version.min from Mozilla Core, but security.tls.version.fallback-limit is new. So we need to consider adding the latter to our preferences UI (bug 1123673).
      • Currently unclear whether or not this should be done after bug 1084025 disable insecure TLS version fallback entirely by default [4]
      • alternative proposal is to make whitelist for acceptable fallback sites available in the UI, which seems to make more sense.

Feature List, Planning

Bug statistics for the last two (full) weeks: 17 new, 8 fixed, 18 triaged.

  • Medium-low triaging effort, low number of new bugs filed.
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.
    • The draft is currently at
    • Progress is stalled due to hardware/firmware problems with Tonymec’s current computer. Current ETA for newer computer is after Easter but this is a rough estimate. Anyone with a wikimoz account can edit the page (and is welcome to). — Tonymec (talk) 17:35, 21 January 2015 (PST)

Open reviews/flags:
49 review
5 super-review
5 ui-review
13 feedback

  • See Feature List page for major wanted/needed features.
  • TODO:
    • bug 1127784 proposes to add a preference and UI to enable/disable playback of Encrypted Media Extensions.
      • FIXED has landed, with UI seen in non-release builds only
      • but uncertain if it does anything useful to be tested

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

  • Usual testing, reviewing, commenting and approving.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i/fx-i:
  • Pending tree opening:
  • Pending approval for check in:
  • Checked in pending review:
  • Waiting for feedback/review/information:
    • bug 1061348 Port |bug 575283 – Cleanup mozconfig files on all platforms| to SeaMonkey
    • bug 1163441 Use FINAL_TARGET_FILES and DIST_FILES for Thunderbird themes
    • bug 1195129 Port |bug 1027890 – Remove all sorts of build system code dedicated to pymake| and |bug 1082323 – Reject pymake in| to comm-central
    • bug 1195246 Port changes from |bug 1188766 – sccache setup with UPLOAD_EXTRA_FILES makes some files uploaded multiple times| to comm-central
    • bug 1195258 Port |bug 710147 – Pass more targets from to the build system| and |bug 911936 – Kill make depend| to comm-central
    • bug 1195264 Port |bug 741839 – consolidate $(wildcard calls) to reduce overhead| and parts of |bug 774106 – Change how virtualenv is populated| to comm-central
    • bug 1195331 Port |bug 762358 – .mozconfig changes don’t cause configure to run| to comm-central
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1200199 Update en-GB for Gecko 41
    • bug 1101381 Printing throws error: DEPRECATION WARNING: getWebBrowserPrint is now deprecated, and fully unsupported for multi-process browsers. Please use a frame script to get access to nsIWebBrowserPrint from content
    • bug 1190179 Port |bug 1067325 – Add an option to view html source in a tab| to SeaMonkey
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.

Sorry, I’ve not done much at all this fortnight due to illness.


Has Review. Waiting for a greener tree before checking in:

  • bug 507676 Port bug 435804 Remaining rdf cleanup for FilterListDialog| to SeaMonkey.
  • bug 640420 Add draggable splitter between urlbar and searchbar.
  • bug 1176602 Make sure that the dictionary stored in spellchecker.dictionary is valid (Adapt Thunderbird bug 1175908).
  • bug 1192276 Restore about:privatebrowsing UI to before it was messed up by Project Chameleon styles.


  • bug 1196422 error LNK2001: unresolved external symbol GetAsciiHostPort(class nsACString_internal &) [MailNewsCore].

In Progress:

  • bug 1011857 Implement CustomizableUI shim for SeaMonkey.
  • bug 1022354 SeaMonkey forces 3rd-party themes to not use defaultFavicon.png but hardcode a bookmarks-item.png.
    • bug 1189918 Theme overrides should work in safe mode for comm-central applications too. [Toolkit]
    • bug 1190465 Move default theme overrides into separate chrome.manifest for other non-firefox toolkit consumers too. [Toolkit].
    • Thunderbird defaut theme overrides.

Other stuff:

  • Did some reviews and approvals.
  • Bug triage and Bug discussions.
  • Usual end user support and PR in newsgroups and Mozillazine.

Any other business?

Mozilla KoreaMozilla l10n 도쿄 해커톤 후기

안녕하세요. 저는 Mozilla 한국 커뮤니티에서 Firefox for Android 지역화를 하고 있는 이병주(pillarlee16)라고 합니다. 여러분도 아시다시피 Mozilla는 Firefox, Thunderbird와 같은 제품들을 전 세계의 더 많은 사람들이 사용할 수 있도록 커뮤니티 자원봉사자들이 각 나라의 언어로 번역하여 출시하고 있습니다. 현재 총 90개가 넘는 언어를 지원하고 있는데요, 이는 커뮤니티에 의해 출시되는 제품 중 가장 많은 수입니다. 지난 8월 26일, 27일 양일간 Mozilla l10n(Localization, 지역화) 도쿄 해커톤이 열렸습니다. 아시아 지역 l10n 커뮤니티에서 활동하는 멤버들이 모여 Mozilla의 Mission(사명)을 다시 공유하고, 더 나은 제품을 만들기 위해 아이디어를 모으는 자리입니다. 한국 커뮤니티에서는 저와 Firefox 지역화를 맡고 있는 이진규(jincreator)님이 참여하였는데요, 이 글을 통해 여러분들과 그 날 있었던 이야기들을 나눠보면 어떨까 합니다.



해커톤은 도쿄에 있는 Mozilla Japan 오피스에서 열렸습니다. 한국뿐만 아니라 일본, 대만 커뮤니티의 멤버들이 참여하였습니다. 같은 일들을 하고 있는 다른 국가의 멤버들을 직접 만나는 자리는 처음이라 매우 신기하기도 했습니다. 행사 진행은 이번 해커톤을 기획한 Mozilla l10n 드라이버 Jeff Beatty가 맡았습니다. 우선 Mozilla l10n 제품들의 앞으로의 소식들을 공유해주었는데요, Firefox 42 버전을 기점으로 Seasonal Release를 한다고 합니다. Seasonal Release는 1년에 2번 진행되는데 대규모 마케팅도 동반되는만큼 제품뿐만 아니라 웹 사이트 등 모든 곳에 있어서 퀄리티를 높이기 위해 최선을 다해주기를 당부했습니다.

제품의 번역 품질에 대한 이야기도 나누었습니다. 번역 품질을 수치 측정하기 위해 지난 2년간 파일럿 테스트를 돌렸다고 합니다. 이를 통해 번역 품질 향상을 꽤하기도 하지만, 파트너들에게 제품의 우수성을 설득하기 위한 지표로 사용 가능합니다. 자세한 내용은 l10n 커뮤니티 블로그의 Mozilla l10n efforts to measure translation 글을 통해 보실 수 있습니다.



해커톤에 참여한 모든 멤버들과 함께 l10n 아시아 팀의 성장을 도모하기 위한 아이디어를 얻기 위해 Sustainability(지속가능성), Recruiting(리쿠르팅), Recognition(인정), Gathering(모임) 카테고리로 나누어 토의하였습니다. 각 팀별로 그간 자신들의 경험을 토대로 어려웠던 점, 앞으로 개선되었으면 하는 점들을 공유하였습니다.

Mozilla의 많은 활동들이 Mozilla의 Mission에 동의하는 사람들이 이를 실현하기 위해 기여를 하고, 이를 통해 나온 제품과 서비스들을 이용하는 사용자들이 감동하여 다시 Mozilla에 기여하게 되는 선순환 구조로 이루어지는데요, 해커톤에서 나온 많은 아이디어들이 이 고리를 더욱 견고하게 만드는데 도움이 되기를 기대해봅니다.



이틀간의 해커톤을 통해 Mozilla에 대한 소속감도 더 느끼게 되고, 다른 지역화 팀들을 통해 많은 노하우들을 배울 수 있는 시간이었습니다. 하지만 무엇보다 개인적으로는, 앞으로 Mozilla 활동을 해나가는데 있어 주변에 함께 할 수 있는 친구들이 많다는 걸 알게된 것이 가장 큰 수확이 아닐까 싶습니다. Mozilla는 언제나 열려있습니다. 앞으로 더 많은 분들이 함께하게 되면 좋겠습니다.


[참고] Mozilla l10n 커뮤니티 소통 창구


about:communityParticipation Lab Notes: Short Simple Tasks Increase Engagement

The Mozilla Participation Lab is an initiative that focuses on experimenting and surfacing new approaches to Participation. Read more about the Lab on our wiki page.

Every year, about 7 million people come to the contribute page on looking for information about how to get involved with Mozilla. These visitors represent an exciting opportunity to increase the number of long-term relationships Mozilla has with people who are passionate about the open web.

Right now, however, only about 0.76% of those people ever register to contribute. Even once they’re registered, how we connect them to their contribution area of interest is far from optimized.

In partnership with the team, the Participation Team has set out on a medium-term project to try and maximize the potential of this page. Our aim is to make it a better tool for potential contributors, Mozilla, and the mission.

This first experiment set out to figure out how to increase engagement with tasks presented to a visitor after they said they were interested in contributing. We designed and ran an A/B test over a few weeks, presenting visitors with different types of tasks.


  • we were able to increase the engagement rate to 60% (from 15%) in selecting tasks
  • visitors preferred simple tasks to challenging tasks, and shorter tasks to long tasks
  • presenting more options (6) versus fewer options (2) increased the number of people who chose to pursue a task

Keep reading to learn more about the results and the future iterations and experiments we have planned.


In this A/B test we created four new versions of the contribute sign-up page. Each page presented viewers with a number of tasks categorized either as simple/challenging (variation a) or as taking a little time/more time (variation b). For each of these variations we displayed either 2 or 6 tasks per page.

Variation B : Simple vs. Challenging

Variation B : Simple vs. Challenging

Variation A : Little Time vs. More Time

Variation A : Little Time vs. More Time

For the purpose of this first test we did not track engagement past choosing the specific task, and we did not track engagement with individual tasks, measuring only the category of the tasks selected (eg. simple/challenging or little/more time).


The major findings from this first round of testing were that visitors to the contribute page preferred simple tasks to challenging tasks, and shorter tasks to long tasks. We also found that presenting more options (6) increased the number of people who chose to pursue a task instead of selecting the “not ready” button. Finally across all of the page variations we found the percentage of people who engaged with the pages (either by choosing a task or selecting not-ready) was 60%, much higher than the 15% engagement rate of the original page.

Based on all of the results we can infer that majority of visitors to the contribute page prefer easier, low-barrier tasks, and prefer a handful of choices to just 2.

However there were still a minority of individuals who expressed a preference for more challenging tasks — they may represent skilled contributors who are ready to become deeply engaged in complex projects. In coming iterations of this experiment we will be exploring the level of readiness and skill of these contributors, and whether individuals from this group are more likely to become core contributors than those who selected simpler tasks.

Overall, the enormous engagement rate by both groups further supports the amazing opportunity latent in this page.

Next Steps

Over the coming months we will undertake several rapid iterations on this test. There is a great deal still to be learned, however we believe that through experimenting with participation in venues like this we can unlock huge potential to help people engage with Mozilla in high impact ways.

Over the next few weeks the Participation team will be working to design a second experiment and we will focus on:

  • Enhancing our understanding of the specific kinds of tasks contributors are most interested in
  • How the task completion rate varies among types of tasks and levels of difficulty and what this tells us about the contributors we are able to attract through this page
  • How wording and framing of tasks effects task selection and completion

Other topics we will seek to explore in the longer-term include:

  • Understanding best practices for how to setup second and third tasks to engage contributors in a more long-term way
  • How presenting localized tasks affects completion rate How to identify and present tasks with the maximum appeal to contribute page contributors
  • How to provide “off-shoots” for the non-typical contribute page contributors (such as those who want to contribute code)
  • How to increase the conversion rate from the homepage to the contribute sign-up page If, when and how to collect email sign-ups and what the process is for engaging contributors by email

This project is currently owned by Lucy from the Participation Team in conjunction with the Team. If you have any questions, ideas for future tests, or if you just want to chat about the future of this page please do not hesitate to get in touch!

Air MozillaWebdev Extravaganza: September 2015

Webdev Extravaganza: September 2015 Once a month web developers across the Mozilla community get together (in person and virtually) to share what cool stuff we've been working on.


My journey with Mozilla is not a very old one. But in this brief partnership of 4 odd months I feel like I have learnt so much that it can fill an entire library. So here I am sharing a milestone event, what many might call a game changer. It was the golden  opportunity to be a Speaker in Dayanand Sagar Institution,Bangalore on 30th March.

“Behind every successful man there is a woman” goes the saying of yore, but in my case it turned out to be quite the opposite and the person I owe my success to is Shreyas, my co-speaker. He coaxed me to come out of my shy and reserved cocoon and go out of my comfort zone into the foray of public speaking. So, after lots of convincing, I packed my bags and traveled  all the way to Bangalore to attend this event. At 2 in the afternoon, sheltered in the comfortable IBM labs away from the blistering summer sun, Shreyas actuated the event with a very interesting activity named “The Spectrogram“.

The game started with this question: “Are women  good managers or not?” As per the rules, the students had to split themselves into three groups: yes, no and maybe.This game paved the way for a healthy discussion on WoMoz, as we like to call us Women in Mozilla. Everyone teamed up and started putting forth their views and opinions. It was  really refreshing to see such an enthusiastic and opinionated crowd.

After this ice breaker in the form of a game, Shreyas gave everybody an introduction to Mozilla, our mission, the open source projects and how to contribute to Mozilla. He also talked about the Mozilla web maker tools(popcorn maker,x-ray goggles,thimble,app maker) and also gave a demo of the  popcorn maker and the Webmaker App. He then asked the students to design their own video. This served the dual purpose of cementing the use of popcorn maker in their minds as well as opening them up for an interactive session rather than a boring presentation. To add spice to the event we came up with the most talked about, the passion and religion of every Indian, the one and only ICC cricket world cup.

I have no qualms in admitting that I suggested the topic purely because I am also one of the gazillion ardent devotees of cricket in India. More so, I was also intrigued to know what was their take on it as they had already proved themselves to be quite the intelligent batch. All the students started working on it with all guns blazing, we also made an announcement that the winner would get the Mozilla swags.

After an hour or so, the new session started, where I was to take the lead. I started the session with a very rudimentary question “ why don’t women contribute to Open source” , “ why don’t they come forward?” I asked every single girl sitting in the room what is the reason behind less participation? (Why) do they feel inferior when it comes to technology and coding? The answers that I received were not very far from what I had expected. phrases such as  “they believe they are not good when it comes to coding” , “women are usually stereotyped in non technology roles”, “women are not cut out for technology” etc etc. The question that followed in natural progression was How to get more women into tech ?

I addressed them more as a peer and tried to break the mental block that women had or what was drilled in their heads by the bias of our patriarchal society. Something that said “women cannot be in technology”. But, the legitimate truth is  Anyone can do it , especially women themselves  😉  and we’ll allow them to get bolder and getting greater appreciation for what they do !! I also spoke about IRC, bugzilla  and mailing lists to get in touch with the Mozillians and WoMoz. I had a discussion with the girls ,talked about their problems in participating and tried solving their issues. Then we distributed the goodies to the winners of popcorn maker. The students were pretty awesome when they have come up with their videos.

I’m still walking the path to achieve the dream I’m chasing after.Don’t know if I can succeed and achieve the ultimate goal of empowering every single mother, daughter and female friends through techs and FOSS . I dare to dream , I dare to dream a country where a girl will prefer to be techie or web maker rather than being a house-hold worker. I know it’s a long way to go but not impossible though.


WoMozWomaniya – Empowering more WOMEN in Tech(expanding woMoz)

From Ada Lovelace , women have played an important part in driving technology forward…..

I was lucky enough to get the invitation for Womaniya from the woMoz organizer Komal Ji Gandhi from India which took place this 8-9th March in Bhopal, Madhya Pradesh.
On 6th January early in the morning I started for Delhi from Dhaka,Bangladesh and got connected with Bhopal flight. The organizer herself came to the airport to receive me warmly with a local volunteer, Vaibhab Bajaj. We went to our desired hotel and as I was tired so that day was an ‘Off’ for me to take rest. The next day early in the morning both of them came to pick me up to the volunteers stay place. Keeping my luggages we went to many places like meeting with the police AIG for confirming agenda and speakers, picking up womaniya teeshirts etc.
In the evening , I was just surfing around after taking some rest in the garden of the hotel while other mozillians Umesh Agarwal and Jafar Muhammad joined me in the hotel. Soumya Deb joined us later at night and Sumantro mukharjee joined us the next day during we were having our breakfast at hotel.

Day 1 starts:


Womaniya welcomes us :)

As it was the first day of the event and all of our guests were supposed to come there on time we rushed there just after we had our breakfast to just check everything was perfect.
The event started sharp at 10.30. All the chief guests gave their valuable speech about women in the society, their safety, womens’ day celebration etc.


We, MOZILLIANS started our main event after the lunch. Me and Komal gave brief idea about what woMoz and womaniya is and how it is related to each other. To make the brief talk more interactive we both asked each other about the reason why we are womoz and what inspired us to be a mozillian or contribute to Mozilla as a women.


Later, Faisal sir explained what mozilla is and how it works.



The crowd!




Day 2 starts:
The next day we volunteers woke up early just to be before time to make sure that everything is going to be perfect. At 10.30 people started coming. We were amused to see that at least 70% people from the previous day joined us. “Passionate” – I MUST SAY!
Once they started taking place, we started with our first session(s). People were divided into small groups. FSA, APP DEV and Webmaker. Me, along with Umesh took the responsibility of FSA team.



Deb was incharge of App Dev and Sumantro, along with me again in Webmaker. Komal helped all the volunteers during the sessions.
Faisal sir took an awesome session on l10n. Later on stage Deb showed app development.


Following him, Faisal sir took Mozquiz. We also helped him with making questions on the spot! People were called on the stage and were given away cool swags by Pawan sir.



Before wrapping up the event I ended up with my session. I explained what woMoz is, why we need more woMoz, the mission of Mozilla, how and who can contribute with us, how to get over from the restrictions, how to shine in life in tech as women etc. People seemed much energetic till the event ended. They were responsive during my session as well. After wrapping up with the event some girls seemed interested to join the winning team of woMoz and were very much impressed with my session.



People taking swags, closing the event. They loved ’em



A MUST group photo!

To be honest I am now missing Bhopal because every part of the city I visited during the event and free time, has given me such pleasure of travelling.

Slides I used to speak out through my session .

Day 1 pictures

Day 2 pictures

I recently got one make from webmaker about the event which is made by a local volunteer, chandan . I loved this make!

Covers by newspapers about the event:




Online coverage by radio:

WoMozGeek Girls Hangout @Dhaka, Bangladesh

We the WoMoz are mainly dedicated to improving women’s visibility and involvement in Free/Open Source and Mozilla, and to increase the number of women contributors. So we the Bangladeshi WoMoz along with the help of MozBD had a small informal meet up planning about the future events of WoMoz.

Event was conducted by me(Tanha Islam), Laila Mustari. We were 6 in numbers. We had girls from 2 different institute. We talked about how to get more women from different aspects. We had 2 newbie with us who were Tahmima Chowdhury Nawrin and her classmate. We had a s.w.o.t analysis of our past activities and planned about future events, how to make them successful ! Our short meet up for 2 hours was successful!



Points we discussed:
-Firefox club (what to & how to)
-Future events(types)
-Hangouts to brainstorm awesome ideas to get more women in tech & Mozilla
-Firefox OS(we had hands on experience as well 😉 )


At last we had a group photo! :)

Event on REPS portal :
On FB:
Hashtag was : #gghangoutdhk , #MozBDEventIdea
WoMoz BD on fb: Group , Page

The Mozilla BlogForging an Alliance for Royalty-Free Video

Things are moving fast for royalty-free video codecs. A month ago, the IETF NETVC Working Group had its first meeting and two weeks ago Cisco announced Thor. Today, we’re taking the next big step in this industry-wide effort with the formation of the Alliance for Open Media. Its founding members represent some of the biggest names in online video, such as Netflix, Amazon, and YouTube, multiple browser vendors including Mozilla, Microsoft, and Google, and key technology providers like Cisco and Intel. The Alliance has come together to share technology and run the kind of patent analysis necessary to build a next-generation royalty-free video codec.

Mozilla has long championed royalty-free codecs. The Web was built on innovation without asking permission, and patent licensing regimes are incompatible with some of the Web’s most successful business models. That’s why we already support great codecs like VP8, VP9, and Opus in Firefox. But the Web doesn’t stand still and neither do we. As resolutions and framerates increase, the need for more advanced codecs with ever-better compression ratios will only grow. We started our own Daala project and formed NETVC to meet those needs, and we’ve seen explosive interest in the result. We believe that Daala, Cisco’s Thor, and Google’s VP10 combine to form an excellent basis for a truly world-class royalty-free codec.

In order to allow us to move quickly, the alliance is structured as a Joint Development Foundation project. These are an ideal complement to a larger, open standards organization like the IETF: One of the biggest challenges in developing open standards in a field like video codecs is figuring out how to review the patents. The Alliance provides a venue for us to share the legal legwork without having to worry about it being used against us down the road. That distributes the load, allows us to innovate faster and cheaper, and gives everyone more confidence that we are really producing a royalty-free codec.

The Alliance will operate under W3C patent rules and release code under an Apache 2.0 license. This means all Alliance participants are waiving royalties both for the codec implementation and for any patents on the codec itself. The initial members are just a start. We invite anyone with an interest in video, online or off, to join us.

For further information please visit or view the press release.

Air MozillaMartes mozilleros

Martes mozilleros Reunión bi-semanal para hablar sobre el estado de Mozilla, la comunidad y sus proyectos.

hacks.mozilla.orgFlash-Free Clipboard for the Web

As part of our effort to grow the Web platform and make it accessible to new devices, we are trying to reduce the Web’s dependence on Flash. As part of that effort, we are standardizing and exposing useful features which are currently only available to Flash to the entirety of the Web platform.

One of the reasons why many sites still use Flash is because of its copy and cut clipboard APIs. Flash exposes an API for programmatically copying text to the user’s clipboard on a button press. This has been used to implement handy features, such as GitHub’s “clone URL” button. It’s also useful for things such as editor UIs, which want to expose a button for copying to the clipboard, rather than requiring users to use keyboard shortcuts or the context menu.

Unfortunately, Web APIs haven’t provided the functionality to copy text to the clipboard through JavaScript, which is why visiting GitHub with Flash disabled shows an ugly grey box where the button is supposed to be. Fortunately, we have a solution. The editor APIs provide document.execCommand as an entry point for executing editor commands. The "copy" and cut" commands have previously been disabled for web pages, but with Firefox 41, which is currently in Beta, and slated to move to release in mid-September, it is becoming available to JavaScript within user-action initiated callbacks.

Using execCommand("cut"/"copy")

The execCommand("cut"/"copy") API is only available during a user-triggered callback, such as a click. If you try to call it at a different time, execCommand will return false, meaning that the command failed to execute. Running execCommand("cut") will copy the current selection to the clipboard, so let’s go about implementing a basic copy-to-clipboard button.

// button which we are attaching the event to
var button = ...;
// input containing the text we want to copy 
var input = ...;

button.addEventListener("click", function(event) {
  // Select the input node's contents;
  // Copy it to the clipboard

That code will trigger a copy of the text in the input to the clipboard upon the click of the button in Firefox 41 and above. However, you probably want to also handle failure situations, potentially to fallback to another Flash-based approach such as ZeroClipboard, or even just to tell the user that their browser doesn’t support the functionality.

The execCommand method will return false if the action failed, for example, due to being called outside of a user-initiated callback, but on older versions of Firefox, we would also throw a security exception if you attempted to use the "cut" or "copy" APIs. Thus, if you want to be sure that you capture all failures, make sure to surround the call in a try-catch block, and also interpret an exception as a failure.

// button which we are attaching the event to
var button = ...;
// input containing the text we want to copy
var input = ...;

button.addEventListener("click", function(event) {
  event.preventDefault();; // Select the input node's contents
  var succeeded;
  try {
    // Copy it to the clipboard
    succeeded = document.execCommand("copy");
  } catch (e) {
    succeeded = false;
  if (succeeded) {
    // The copy was successful!
  } else {
    // The copy failed :(

The "cut" API is also exposed to web pages through the same mechanism, so just s/copy/cut/, and you’re all set to go!

Feature testing

The editor APIs provide a method document.queryCommandSupported("copy") intended to allow API consumers to determine whether a command is supported by the browser. Unfortunately, in versions of Firefox prior to 41, we returned true from document.queryCommandSupported("copy") even though the web page was unable to actually perform the copy operation. However, attempting to execute document.execCommand("copy") would throw a SecurityException. So, attempting to copy on load, and checking for this exception is probably the easiest way to feature-detect support for document.execCommand("copy") in Firefox.

var supported = document.queryCommandSupported("copy");
if (supported) {
  // Check that the browser isn't Firefox pre-41
  try {
  } catch (e) {
    supported = false;
if (!supported) {
  // Fall back to an alternate approach like ZeroClipboard

Support in other browsers

Google Chrome and Internet Explorer both also support this API. Chrome uses the same restriction as Firefox (that it must be run in a user-initiated callback). Internet Explorer allows it to be called at any time, except it first prompts the user with a dialog, asking for permission to access the clipboard.

For more information about the API and browser support, see MDN documentation for document.execCommand().

QMOFirefox 41 Beta 7 Testday, September 4th

I’m writing to let you know that this Friday, September 4th, we’ll be hosting the Firefox 41.0 Beta 7 Testday. The main focus of this event is going to be set on Flash on 64-bit Firefox builds and plug-ins testing. Detailed participation instructions are available in this etherpad.

No previous testing experience is required so feel free to join us on the #qa IRC channel and our moderators will make sure you’ve got everything you need to get started.

Hope to see you all on Friday! Let’s make Firefox better together!

Meeting NotesMozilla Project: 2015-08-31

  • Every Monday @ 11:00am Pacific Time (19:00 UTC)
  • to watch and listen
  • join #airmozilla for backchannel discussion
  • Presenters only: Vidyo room “Brownbags”. Do not use this room if you’re not planning to speak.
  • Dial-in: conference# 8600
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 8600
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 8600
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 8600
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 8600
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 8600
    • UK/London: +44 (0)207 855 3000, x92 Conf# 8600
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 8600

All-hands Status Meeting Agenda

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

Friends of Mozilla

  • Thanks to everyone who helped at the SuMo Day on Thursday
  • A big thanks to Florian Merz for kickstarting the Berlin community! He has organized a #FoxYeah event back in June and now hosts bi-weekly developers meetups in Berlin. He’s a great help in growing our community in Berlin! Keep it going!
  • Erin Lancaster for being so enthusiastic. It’s great to work with her together on projects so we can bridge the gap between employees and volunteers :)
  • A big thanks to Ian IRC NICK iann for approving all of the translations for the en-gb on Pontoon, for all of the Mozilla websites
  • Thanks to :rbillings for leading QA of the new Firefox iOS product download page with some Kiwi Mozillians (including Chris, Bram, Nick, and Karl) for our preview release in New Zealand!
  • Our awesome volunteer add-on review team reviewed more than a thousand add-ons last week–more than any other week in the past two years!

Upcoming Events

Monday, 31 August
Tuesday, 01 September
Wednesday, 02 September
Thursday, 03 September
  • KB day – this is a day for all contributors to help update the SuMo knowledge base

Project Status Updates (voice updates)

Firefox OS

Peter Dolanjski, Ontario, Canada (remote)

Foxfooding Update

  • B2GDroid: Android Launcher – Early nightly .apk build now available: [1]. Follow progress in bug 1170323
    • Feel free to file bugs on issues and inconsistencies under B2GDroid Product in Bugzilla, noting device used
  • Firefox OS ports for unlocked Android devices: Reach out to Brian King to get involved.

Firefox OS Key Initiatives

  • 18 Month Initiatives identified
  • Expect Roadmap Wiki updates over coming weeks
  • Have your voice heard: vote on feature requests and highlight important defects here: Foxfooding dashboard
  • #b2g for more information
  • Questions: pdol on irc,
Mozilla Learning Networks

Hannah Kane, Portland: Introducing the new Thimble, a better educational code editor. Visit


The limit is 3 minutes per topic. 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.

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
Havi Hoffman Developer Relations Content Wrangler & Cat Herder Mozilla Tech Speakers & DevRel Summer Update Mountain View no Video : Tech Speakers, Developer Relations team
George Roter Head of Core Contributors, Participation Applications open for Global Gatherings (participation leaders at MozFest, All Hands Orlando, and a NEW Leadership Summit) Toronto yes Presentation Global Gatherings Information


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

New Volunteer Introduced by Speaker location New Volunteer location Will be working on
Who is the new volunteer? Who will be introducing that person? Where is the introducer? Where will the new person be contributing from? What will the new person be working on?
Chiriru David (satdav) THe UK on Vidyo Philippines Helping other users on the Support website
Philip David (satdav) THe UK on Vidyo South Africa Helping other users on the Support website
Andrey Meshkov Jorge Villalobos Vidyo (Costa Rica) Russia AMO add-on reviewer.
Michel Gutierrez Jorge Villalobos Vidyo (Costa Rica) France AMO add-on reviewer.

Introducing New Hires

New Hire Introduced by Speaker location New Hire location Will be working on
Priti Prabhakar Erica McClure Mountain View Mountain View HRIS
Preeti Sanketh Dylan Oliver Mountain View Mountain View Firefox OS
Jennifer Douglas Alex Costello Mountain View Mountain View Engagement


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

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

Engineering Productivity

QMOAn open letter about Mozilla QA

Dear people of the web,

As some of you may already be aware, Mozilla has experienced a lot of change over the years. Most teams and projects within Mozilla have felt this change in some way, either directly or indirectly. The QA Team is no exception.

As a microcosm of the Mozilla Project, people involved in many disparate projects, QA has changed course many times. To many of you, these changes may have passed by unnoticed. Perhaps you noticed something was different about QA but were not able to understand how or why things had changed. Perhaps it was a feeling, that some of us seemed more distant, or that it just felt different.

This may come as a surprise to some, but there is no longer a single, unified QA team at Mozilla. After going through a few re-organizations, we are spread across the organization, embedded with — and reporting to — various product teams.

Those teams have benefited by having a dedicated QA person on staff full time. However, with so few of us to go around, many teams find themselves without any QA. In this state, we’ve lost the distinguished central QA organization that once was and in doing so we’ve lost a central QA voice.

As a result of these changes and a sense of perpetual reorganization we have reached a tipping point. We’ve lost some very talented and passionate people. Change within itself isn’t a bad thing. The loss of cohesion is. It is time to break this pattern, regain our cohesion and regain our focus on the community.

The core group of QA community members, paid and volunteer, will soon be getting together to formulate a mission statement. We’ll do this with a series of one-on-one conversations between core individuals who are interested in architecting a new QA community.  This will serve as the guiding light of our journey toward a more optimistic future together.

In recognition of those who might feel excluded from this process, we want to assure you that there will be opportunity to contribute very early on. Conducting these one on ones is just the  first step in a very long journey. We plan to bring everyone along who wants to be here, but this process requires great care and it will take time. If you’d like to help us build the future please get in touch with us.

Please read our wiki page to find out more about what we’re doing and where we’re going.



Anthony Hughes and Matt Brandt

WebmakerIntroducing the New Thimble, an Educational Code Editor for Teaching and Learning the Web

Today, Mozilla is introducing the new Thimble, an upgraded tool for teaching and learning web literacy in a simple, hands-on and visual fashion.

We believe the Web is a better place when everyone can read, write and participate online, a belief that served as our inspiration for first creating Thimble in 2012. With Thimble, users write and edit HTML, CSS, and JavaScript on the left side of their screen, and watch their code come to life on the right. Learners can start with simple remixes, changing words and images on a page to familiarize themselves with code and build confidence. Learners can also work their way toward creating entire web pages from scratch. We’ve seen Thimble used by educators in amazing ways: middle schoolers in Virginia building apps, activists in Barcelona designing net neutrality posters, and university students in Mombasa hacking together projects.

Screen Shot 2015-08-31 at 3.50.34 PMThimble exemplifies the hands-on, collaborative learning philosophy at the core of Mozilla’s work. Thimble can be used by educators to create a customized and interactive classroom experience, or used by independent learners eager to teach themselves via step-by-step tutorials. All of Thimble’s creations are open source and fully remixable. And Thimble itself is free and open source, always. In 2014, Thimble was recognized with the ON for Learning Award from Common Sense Media, an accolade for outstanding digital media products that educate and engage young people.

So, what’s new with this version of Thimble? We’ve built enhancements that transform Thimble into not just a better code editor, but also a rich platform for educators to build curriculum on. Updates include:

  • Expanded capabilities. Users can now build and link multiple web pages, rather than just one, within a single project
  • A helping hand. A more guided learning experience featuring easy-to-use tutorials, auto-closing tags and autocomplete
  • A streamlined interface. A sleeker look and feel with light and dark theme options, an easy-to-use color picker, and easy access to all of your files and projects
  • Drag, drop and unzip. You can now drag and drop a zipped website into the editor, expand it, and start hacking immediately
  • Better previews. A mobile browser preview mode, to see how your project will appear on the mobile Web
  • So much more. Auto save, extensions, a selfie-taker and other new features

The new Thimble is the result of collaboration between Mozilla and the Seneca College Centre for Development and Open Technology, and research was funded by the Natural Science and Engineering Research Council of Canada (NSERC). The new, more powerful Thimble is also made possible through our incorporation of the open source text editor Brackets. Read more about Seneca and Brackets here.

The Thimble community has a rich history of creativity: teachers create template projects for their students to remix; students remix each others projects for collaborative learning; and educators share their curriculum and teaching activities with colleagues. We’re excited to see what educators and learners create next. Use Thimble to help others read, write and participate online — and make the Web a better place.

Questions? Reach us anytime at @MozTeach or, and watch our introduction video below:


SeaMonkeyGood news…bad news..

Not beating around the bush with this.  [wanted to have a catchy title… not being good with topics and all that, but.. no one cares about the title.  It’s the content..]

Well, the release will be done within this week, just not today (31st August 2015, PST(or whatever it is now)).  Really sorry about that.  I realize we said end of August, but … ok.  No buts.

Ok. There is a but.

But we are in the final stretch.  And of course, the disclaimer here is that ‘final’ is loosely termed as within this week (and dare I even say, ‘at the earliest’ – reason? .. oh you don’t want to know the excuses..  Would gremlins be satisfact… no? Um.. the dog?  umm the misalignment of… ).

The real reason is that with our infrastructure code, we don’t have the necessary infrastructure to support a testing environment.  So any changes we do to the infra code is live every time we post(and even though the infra code is reviewed, like everything else), there could be unforeseen circumstances that give our infra a fit.  (Yes. I know. In this day and age of DevOps and CI, this shouldn’t be the case; but, really..  the resources issue.  I’ve been planning to find a way to get some sort of CI/testing env for our infra code locally..  just haven’t been able to… work and family and other RL issues.)

So, please do bear with us just for a little bit longer.



PS: I realize this isn’t a proper PR ditty.  I’m not a PR person and therefore the aforementioned would probably get someone fired somewhere.  Anyway… no offense to anyone.   All I hope is that I can help this project in any way I can, even if it’s small.


Mozilla India[Call for Action] Pan India Mozilla Geolocation Pilot v3.0

After the grand success of the first  and second experimental Pilot, the Mozilla Geolocation team is excited to run another pilot in India.

Mozilla  Geolocation service is so far the most open & public location service in the world, and now you have  the opportunity to help  make it  better. We have formed a Geolocation Taskforce for India which will be  helping the volunteers to carry out the Third pilot in their region.
It’s been a little more than one year since the last pilot event but we still have small events happening all over India and now, let’s take the opportunity of the third pilot & break our own past record!
Event Details
In order to improvise from our last pilot, we’ve figured that there’s no need for it to be an offline, single venue event. This time we’re going with pan-India scope right from the beginning & kicking-off with a virtual event (Video Conference over hangout), for anyone to join in, from anywhere in India.The kick off event has been scheduled at 8:00PM IST on 1st  Sept, 2015. 

Once kicked off, y’all will have 21days [3 week] (ending on 22st Sept, 2015 at 8:00PM IST) to scout all over India with MozStumbler. But make sure to register yourselves as a Geolocation scout (detailed later; registering is important).

Remote Sites
As the event will be kicked off with a virtual event, we’ve primarily selected a few remote sites where we’ll be having teams who will be joining us over the video conference. Here’s the list of locations we have so far:
          City                   Curator                  
    Bangalore              Galaxy
    Hyderabad             Ajay Jogawath         
    Indore                    Mrinal Jain
    Kerala                    Kumaresan.C.S.
    Kolkata                   Sumantro Mukherjee 
    Nashik                    Ronit Jadhav
    Odisa                      Rishu Goenka
    Pune                       Sayak Sarkar      
    UP                           Vnisha Srivastav
    Tamil Nadu            Viswaprasath
If you’re from the listed cities, please contact the respective curators from your city for details on how to join; OR, if you’re planning to host a remote site & your city isn’t listed above, please contact me with the details & I’ll have the list updated.
How to participate
Please fill up this form to register yourself as a scout of Mozilla Geolocation Pilot 3:
Here’s how:
  1. Download & install MozStumbler(add play store link) on your GPS enabled Android phone 
  • You may have to enable installing apps from SD card security lock
2.Open the App, visit settings & set a Nickname and email id
  • Share the nick by filling up the form embedded below
3. on about Stumbling all over the places, throughout India 
  • The app doesn’t need an active data connection
  • You can upload all collected data whenever you get online
4.On 10th,Sept 2015 12:00 UTC, we’ll publish the custom leaderboard 
  • We’ll look up for scores only among the form-submitted Nicks
If you are already stumbling ,please sync all the remaining points to make sure everyone is on the same page.


Reward & Recognition
As Mozilla Location Service’s community is growing, we’ll count on you to make your region brightest on the MLS’s Map; and all your contributions will be recognized with a follow-up post.
That’s not all. To further appreciate the top contributors, we’ll be giving surprise gifts.
  • Topper
  • Runner-up
  • 2 runner-ups
  • Most New cells
  • Most New Wifi Networks
All other geolocation-scouts with valiant contributions will also be recognized in the follow-up blog post.
So, go on now… the time is ticking! 

SeaMonkeyWin32 build/repack status

The Win32 2.35 release build is done.  By ‘done’, I mean the compile and pushing to the staging area has been completed.  The actual release *isn’t* complete.

The win32 2.35 l10n repacks are also done. (Again, like above, in staging area).

Next up, I’m waiting for the busted l10n repacks to be done (linux/osx: ca, ja, fi, sv-SE and pt-PT).  Once they’re done, we’ll be working on the next part (which will involve a bit of infra structure code changes).




Mozilla Add-ons BlogAMO T-shirt Update

Just want to give a quick update on the snazzy t-shirts designed by Erick León Bolinaga. They were finally done printing this week, and are headed to a fulfillment center for shipping. We expect them to begin shipping by the end of next week.

Thanks for your patience!

SUMO BlogWhat’s up with SUMO – 28th August

Hello SUMO Nation, hello world! The end the summer break is almost upon us. We hope you had the time to get out there, discover, have fun, relax, and rest. Autumn is almost here… Let’s get the latest news and updates before the first leaves fall from the trees, hm?

Hello To All New Contributors!

If you joined us recently, don’t hesitate – come over and say “hi” in the forums!
Additionally, if you are new to SUMO and someone helped you get started in a nice way – don’t forget you can nominate them as a Buddy of the Month!

Contributors of the week

We salute you!

Last Monday’s SUMO Community meeting

Reminder: the next SUMO Community meeting…

  • …is going to take place on Monday, 31st of August. Join us!
  • If you want to add a discussion topic to upcoming the live meeting agenda:
    • Start a thread in the Community Forums, so that everyone in the community can see what will be discussed and voice their opinion here before Monday (this will make it easier to have an efficient meeting).
    • Please do so as soon as you can before the meeting, so that people have time to read, think, and reply (and also add it to the agenda).



Support Forum



  • Desktop: the hotfix for an Async Plugin bug that was apparently causing issues with the rather popular Farmville 2 has been shipped.
  • Android: new content for Firefox 42 about signed add-ons, editing passwords, tab queues, and other features is getting written.
  • iOS: the articles have been written and we are steadily nearing iDay, at a pace of about 24 hours each day ;-)

Big things coming up all over the place… But not before this weekend! Unless you’re preparing something big and haven’t told us ;-)

Stay tuned, take care, have a great time, and see you soon!

The DenAll about that space


If the discovery of Kepler-452b has you glancing skyward, planet hunting and stargazing, we have a cosmic theme collection for you. Gravity belt recommended before installing.

Blast off to space themes.

Meeting NotesChannel: 2015-08-27


Jorge, KaiRo, lizzard, RRayborn, Sylvestre, ritu, rolandtanglao

Schedule Update

  • ESR 38.2.1
    • Affected by the security issues too
    • just waiting on QE signoff
    • need to do the release notes
  • 41
    • gtb Beta5 Desktop and Mobile today
    • One of the security fixes affects Fennec and so the need for a Fennec 41.0b5

Performance (Thu)

Aurora / Dev Edition

  • Overall rate: 4.0 (same as Tue)


  • Overall rate: 0.9 (same as Tue)
  • bug 1178271 (mozilla::dom::Promise::Settle) is 1.3% on b4
  • bug 1196696 (MediaFormatReader::DecoderData::ResetDemuxer) probably needs uplift


  • Overall rate: 0.9 (same as Tue)



  • working on all the sign-offs for release and ESR today, thanks to Florin for staying around long to handle ESR


Special Topics

Aurora/Beta Feature Review

  • Telemetry opt-in for 41 & sample opt-out for 5% of users (bug 1192906)
  • Allow Heartbeat to target Private Browsing Mode users (bug 1184338)
  • “blanket approval” for ~17 patches for MSE to aurora (bug 1197083)

Post-Mortem (Tues 2wks from GA Release)

Channel Meeting Details

Video/Teleconference Details – NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 99951 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99951 (US)
  • Vidyo Room: ReleaseCoordination
  • Vidyo Guest URL

SeaMonkeyupdate on 2.35 news


Another update on 2.35.

1) build3 was ‘somewhat’ done but needs to be rebuilt due to  some misconfiguration on my part.  It doesn’t mean that  build3 is a bust.  It isn’t.  It’s just that it’s uploading  the files to the wrong places. (First time it uploaded was   to the nightlies tree. :P)

2) l10n repacks needs fixing.  I’ve been told it won’t  require a build4(read: Callek’s gonna do his cset magic),   but I guess we shall see.

3) Once the repacks are done, the *real* work is on getting  the CVS-based-system-now-migrated-to-Mercurial part of  the release process working.  But thankfully, this part  is automated, so I won’t be the reason for the slow down.

Again, thanks for your patience while I work on this.


NB: Due to my concentrating on getting the release done, I haven’t done a single Windows nightly in a while, and even then, it was in fit and starts due to tree bustage.   I humbly apologize for that (for the not getting a windows nightly released… not the tree bustage.  )

NB2: Comm-central AND comm-aurora are in a painful state due to a bunch of interrelated bugs, so there haven’t been any builds or nightlies in  some time.  While the patches are up for review(iirc), it just needs time to review them and I could do a post-land-review, but these patches *also* affect the Release builds and I think it was a good idea NOT to fix those bugs (at the sacrifice of c-c and c-a).  But once this release is done, we *will* fix the tree.

Air MozillaIntern Presentations

Intern Presentations Bernardo Rittmeyer Jatin Chhikara Steven Englehardt Gabriel Luong Karim Benhmida Eduoard Oger Jonathan Almeida Huon Wilson Mariusz Kierski Koki Yoshida

Air Mozilla"Firefox Helps You Log In" Presented by Bernardo Rittmeyer

"Firefox Helps You Log In" Presented by Bernardo Rittmeyer Firefox Helps You Log In: Seamless password management for your daily browsing.

Mozilla Web DevelopmentBeer and Tell – August 2015

Once a month, web developers from across the Mozilla Project get together to spend an hour of overtime to honor our white-collar brethren at Amazon. As we watch our productivity fall, we find time to talk about our side projects and drink, an occurrence we like to call “Beer and Tell”.

There’s a wiki page available with a list of the presenters, as well as links to their presentation materials. There’s also a recording available courtesy of Air Mozilla.

openjck: Discord

openjck was up first and shared Discord, a Github webhook that scans pull requests for CSS compatibility issues. When it finds an issue, it leaves a comment on the offending line with a short description and which browsers are affected. The check is powered by doiuse, and projects can add a .doiuse file (using browserslist syntax) that specifies which browser versions they want to be tested against. Discord currently checks CSS and Stylus files.

The Discord team (mrmakeit, groovecoder, davidwalsh, and openjck) is looking for sites to test Discord out. Work on the site is currently suspended (which is why it’s a side project, the team may work on it in their free time) so that feedback can be gathered to determine where the site should go next. If you’re interested in trying out Discord, let groovecoder know!

peterbe: Activity and

Next up was peterbe, with an update to Activity. The site now uses and a message queue to improve how activity items are fetched from GitHub and other sources. The site queues up jobs to fetch data from the Github API, and as the jobs complete, they send their results to Fanout. Fanout’s JavaScript library maintains an open WebSocket with their service, and when Fanout receives the data from the completed jobs, it notifies the client of the new data, which gets written to localStorage and updates the React state. This allows Activity to remain structured as an offline-ready application while still receiving seamless updates if the user has an internet connection.

There’s a donation jar near the exit; for just $25 you can pay for an hour of time for an Amazon engineer to spend with their family. Checks may be made payable to No Questions Asked Laundry, LLC.

If you’re interested in attending the next Beer and Tell, sign up for the mailing list. An email is sent out a week beforehand with connection details. You could even add yourself to the wiki and show off your side-project!

See you next month!

The DenMeet Emma, Web Wizard

web-wizardEmma has her Firefox working like magic with Sync. Since her home bookmarks and passwords are synced to her Android, she can easily sign in to her favorite sites on her mobile. She can quickly pick up at home where she left off at work by accessing her open tabs from the office on her home computer. Emma prefers to keep her home browsing history private and unsynced so it doesn’t appear on her work computer. Sync is flexible that way. It puts her Web at her fingertips, just the way Emma wants.

Put some magic in your Firefox. Sign up for Sync.

Air MozillaWeb QA Weekly Meeting

Web QA Weekly Meeting This is our weekly gathering of Mozilla'a Web QA team filled with discussion on our current and future projects, ideas, demos, and fun facts.

Meeting NotesMobile: 2015-08-26


Tracking Review


  • Next Build:
ID Summary Status Assigned to Last change time
1016555 Disable OCSP checking for certificates covered by OneCRL ASSIGNED David Keeler (on PTO) [:keeler] (use needinfo?) 2015-08-06T16:19:58Z
1129614 Regression: Sometimes thumbnails in the tabs drawer are not updated, they expire ASSIGNED Mark Finkle (:mfinkle) 2015-08-06T17:41:28Z
1170651 crash in js::jit::GetPropertyIC::update(JSContext*, JS::Handle<JSScript*>, unsigned int, JS::Handle<JSObject*>, JS::MutableHandle<JS::Value>) NEW Kevin Brosnan [:kbrosnan] 2015-08-06T17:42:20Z
1180597 Wrong display for more than two doohangers NEW Chenxia Liu [:liuche] 2015-07-17T18:48:50Z

4 Total;
4 Open (100%);
0 Resolved (0%);
0 Verified (0%);


  • Next Build:
ID Summary Status Assigned to Last change time
776030 Allow Fennec to use the AsyncPanZoomController NEW Danilo Cesar Lemes de Paula 2015-08-24T14:28:45Z
1156553 Tab queue makes captive portal use annoying ASSIGNED Martyn Haigh (:mhaigh) 2015-08-20T17:14:28Z
1164449 Startup crash on Moto X (2nd Gen) in android.database.sqlite.SQLiteDatabaseCorruptException: database disk image is malformed (code 11) at android.database.sqlite.SQLiteConnection.nativeExecuteForString(Native Method) NEW Nick Alexander :nalexander 2015-08-12T19:37:09Z
1172359 (Android) WebRTC crashes when microphone is enabled UNCONFIRMED Randall Barker [:rbarker] 2015-08-20T17:58:02Z
1177414 Queued tabs stall on load ASSIGNED Martyn Haigh (:mhaigh) 2015-08-20T18:14:05Z
1181881 Disabling Location is not user friendly – Android M NEW Sebastian Kaspari (:sebastian) 2015-07-13T11:22:10Z
1186020 Download icon is very dark NEW Michael Comella (:mcomella) 2015-08-26T23:09:49Z
1190301 Refine appearance of tab audio indicator NEW :Margaret Leibovic (PTO Aug 27 – Sept 14) 2015-08-25T01:49:13Z
1191330 Autophone – July 31 regression in Throbber start nexus 5 Android 4.4 NEW GaryChen [:GaryChen][:PYChen][:gchen][:陳柏宇] 2015-08-06T17:35:10Z
1191918 Round battery level to integers (or tens?) to mitigate finger printing NEW James Willcox (:snorp) ( 2015-08-06T17:40:13Z
1196198 After uninstalling a default add-on panel the 4th panel is the new default NEW Sebastian Kaspari (:sebastian) 2015-08-20T17:48:57Z
1196553 Add to Reading list icon in menu doesn’t look disabled when disabled on phone NEW Michael Comella (:mcomella) 2015-08-27T01:14:04Z

12 Total;
12 Open (100%);
0 Resolved (0%);
0 Verified (0%);


  • Next Build:
ID Summary Status Assigned to Last change time
886969 Fennec allows scrolling of pages with overflow:hidden on the body element NEW James Willcox (:snorp) ( 2015-08-06T17:42:00Z
1047127 Panning very stuttery on this page with overflow-x NEW 2015-06-10T18:43:44Z
1114096 Wrong tab got mirrored NEW 2015-06-17T18:30:58Z
1131084 Can not mirror tab to Chromecast device NEW Randall Barker [:rbarker] 2015-06-17T18:31:14Z
1144534 fuzzy/bad looking text depending on scroll position, or fuzziness coming and going NEW 2015-08-06T17:41:46Z
1168867 Size of new Gecko selection carets doesn’t take font inflation into account NEW 2015-07-31T02:27:20Z
1171860 Tapping the tab queue notification will open the link in normal browsing with “Open links in Private browsing” pref enabled NEW 2015-08-20T17:15:28Z

7 Total;
7 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs. Make sure friends also get awarded a badge. New contributors are highlighted in bold. Want to update this section?

  • Boris Dušek fixed bug 1195204 – iOS 9: VoiceOver presents lock image and reader button even when those are not visible
  • Dominique Vincent [:domivinc] fixed bug 1192075 – Change copy in Settings for Zoomed View/ magnifying glass preference
  • Jeff Beatty [:gueroJeff] fixed bug 1197219 – [hr] Add hr to mobile/android/locales/maemo-locales
  • Justin Inouye [:inouju] fixed bug 1146735 – Change outer container in @layout/anchored_popup to FrameLayout
  • Kartikaya Gupta ( fixed bug 1180267 – Update Fennec code to use MobileViewportManager instead of the big pile of browser.js code
  • Kartikaya Gupta ( fixed bug 1180295 – Redo Fennec dynamic toolbar implementation
  • Kartikaya Gupta ( fixed bug 1195401 – Assertion failure while playing a video on Fennec (Preferences accessed off-main-thread)
  • Kartikaya Gupta ( fixed bug 1196593 – Sometimes when reaching the bottom of the page the toolbar doesn’t automatically appear
  • Kartikaya Gupta ( fixed bug 1196594 – Transition the toolbar to fully shown/hidden after finger is lifted
  • Kartikaya Gupta ( fixed bug 1196914 – When the toolbar is shown/hidden while an input field has focus, the scroll position jumps
  • Kartikaya Gupta ( fixed bug 1197176 – Coming back to fennec from the task switcher sometimes doesn’t repaint the content area
  • Kartikaya Gupta ( fixed bug 1197233 – When fullscreening a video while the dynamic toolbar is showing, the toolbar area shows garbage
  • Kartikaya Gupta ( fixed bug 998929 – Title bar obscures top of page after returning from fullscreen with title bar auto-hide disabled
  • Mike Taylor [:miketaylr] fixed bug 1175378 – Audit /mobile/android/themes/core/images for unused images
  • Mike Taylor [:miketaylr] fixed bug 717822 – Tapping 2 times on a button causes its size to decrease for a brief moment
  • Milan Sreckovic [:milan] fixed bug 1161083 – Fixed position elements with bottom: 0 are misplaced when scrolled to the bottom of the page
  • Robin Andersen [:tecgirl] fixed bug 1196913 – Firefox for iOS v1.0 App Store Icon

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 2 minutes!

James W. (snorp), Platform Team (Randall, Jim, Eugen, Dylan)

  • It looks like I finally might be able to land the paint suppression patches, got some r+ and good comments. Also looked into web-page-replay, and put up a PR to make it work with Firefox. Nice tool, but could use some love. Profiled some other page load performance issues and found that handling redirects (302) on the main thread can really hurt us. Need to file a bug about that.
  • Randall is working through some tough problems with the native APZ. The fact that we do not use e10s is making some things very complicated.
  • Eugen is working on some media issues (MP4, MP3, VP8/9 w/ MSE) and trying to land some changes to nsIPerformance that will allow you to see thread and cpu time in addition to wall time.
  • Jim continues to land a bunch of JNI changes and refactoring. See his blog post here. He may also work on decoupling BHR from breakpad so we can update to a newer version and fix some of the bad crash reports we’re seeing.
  • Dylan is hammering away on bugs, currently moving some of the native calls in AndroidJNI to the new hotness that Jim wrote. He also helped me look into Web Page Replay.


  • Video Sandboxing, final touchups.
  • Tracking Protection/SafeBrowsing, multiple provider support.
  • Reviewing SafeBrowsing specs for v4.

Brian Nicholson

  • Spent some time investigating the web view white screen issue (bug 1194726). Not much success.
  • Some Swift 2 fixes
  • Looking into failing tests



  • First run on Samsung
  • Reviews, interviews





  • Wrapping up on home feeds integration



  • Manager stuff
  • Trying to finish tab audio indicator
  • PTO August 27 – September 14



  • Tracking down test failures related to click-to-play images
  • Playing around with hyphenation stuff (testing out by using an addon – not much success)
  • Making intern presentation prep! (Will send an invite/reminder today)


  • Menu polish (w/ some Material updates!)
  • Misc. bugs
  • Going to work on distinguishing between remote and local visits in synced data




  • Firefox for iOS v1.0 submitted to the app store. oof.
  • Spending a little time on Xcode 7/Swift 2.0 port that Emily’s driving.
  • Lots of reviews. I’m catching up!
  • Lots of emails and writing, including:
    • Go Faster and Fennec update PRDs
    • Investigating GMP updater numbers (thanks Ben and Sheeri!)
  • Lots of triage and meetings, including:
    • about:newtab remote loading
    • iOS 1.1
    • Go Faster
    • Hello
    • TAG, particularly dexulification


<Read Only>

  • Fallout from moving so a little behind
  • Moving b2gdroid ahead with fabrice
    • Second round of patches ready to land
    • Many thanks to glandium for reviews
  • First round of patches for Sign in to Firefox Accounts on the web
    • Mostly r+, thanks to sebastian for reviews
  • Lots of issues with Android SDK 23 and versions — thanks to sebastian for handling these, including a mobile-firefox-dev post.
    • One more reason to pin versions (Bug 1108782).
  • Looking at android:versionCode future-proofing.




Martyn Haigh




Things I’ve fixed!




Other:* PSA please remember that changes to histogram.json need a p={data steward} attached or we’ll back you out.


  • FxiOS 1.0 out the door
  • Swift 2.0 Migration Hell
  • looking ahead to V1.0.1/V1.1




  • Past
    • TRIBE
    • Interview & debrief
    • TV meetings and stuff
    • bug 1170725: Click-to-play images
    • bug 1189719: Display search history in Awesomescreen
  • Upcoming
    • Mocks for TV stuff
    • Mocks for Hello integration
    • Privacy/security co-ordination
    • bug 1195721: Set a homepage
    • Filing some UI polish bugs


  • Pocket integration mocks (Android and iOS)


  • bug 1186013 Offer to open URLs on the clipboard when entering Firefox
  • bug 1162778 When disconnecting account, give user option to clear browsing data
  • bug 1193363 Determine how to maintain relationship between panels and webview


  • bug 1182303 Firefox iOS susceptible to infinite alert loops
  • bug 1145228 Allow collapsing and expanding Synced (Remote) Tabs clients
  • bug 1183905 Add Sync Now button timestamps
  • bug 1193462 Tapping Sign in on Empty Sync panel should take you to the Sign in flow, not Settings first


Feature Focus


  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 99998
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 99998
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 99998
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 99998
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 99998
    • UK/London: +44 (0)207 855 3000, x92 Conf# 99998
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
  • #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2015-08-26

Firefox Desktop & Platform (Javaun/Chad/Martin)

Current Releases

A new point release for 40 is coming tomorrow, including some security and crash fixes.

Beta (41)

Beta 5 is on track to release Friday. Crash rate is unusually good for beta so far!

  • question from javaun about uplifts for heartbeat to beta.
    • talk with ritu, who is working on beta 41. IN general we’re looking to mitigate risks, not take major feature changes in beta.
Aurora (42)

MSE work will be landing here as well as work for the features for the special release.

Nightly (43)
  • questions from Pike for javaun – how can we better describe the localizing work to localizers related to features?
    • there is a lot of work to do on private browsing. conversation will continue later!

Feedback Summary (Rob/Tyler/Matt)

No updates

Questions, Comments, FYI

New Meeting Format:
Based on a few conversations last week, I’m going to work on solidifying the schedule and content this week to present at the next meeting. Please give any last feedback before Friday!

Planning Meeting Details

  • Wednesdays – 11:00am PT, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Finch Conference Room
  • #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

SUMO BlogSUMO Questions Day this Thursday, 27 August 2015

The summer holidays are now over  so it’s time to start organizing a new SUMO Day!

What are SUMO Days?

A SUMO Day is that time of the week where everybody who loves doing support, contributors, admins, moderators gather together and try and answer all the incoming questions on the Mozilla support forums. This is a 24 hour event, we will start early during European mornings  and finish late during US Pacific evenings.

We are also hanging out having fun and helping each other in #sumo on IRC.

I want to participate! Where do I start?

Just create an account and then take some time to help with unanswered questions. We have an etherpad ready with all the details plus additional tips and resources.

If you get stuck with questions that are too difficult feel free to ping us on IRC #sumo or ask for help on the contributors forums.


SUMO Day will be moderated by madasan (EU morning/afternoon), marksc (EU afternoon/US morning), guigs (US morning/afternoon). We can always use more people to help moderate through the day so if you would like to do this just add your name in the etherpad!

What does it mean to be a SUMO Day moderator?

It’s easy! Just check out the forums and monitor incoming questions. Don’t forget to hang out on IRC on #sumo and the contributor forums and chat with the other SUMO Day participants about possible solutions to questions. As a moderator you also help out contributors who are stuck with difficult questions and need help.

Screensharing experiment

During this SUMO Day some of us will experiment with helping users via screen sharing. This is only open to senior contributors and forum moderators so if you’re one of them and you would like to participate please PM madasan.

 We’re trying to answer each and every incoming question on the support forum on Thursday so please join us. The more the merrier!


See you online and happy SUMO Day!

Air MozillaProject Beehive: A HW/SW co-designed stack for runtime and architectural research.

Project Beehive: A HW/SW co-designed stack for runtime and  architectural research. In this talk we will present an overview of our recent research efforts focusing on Hw/Sw co-designed platform for heterogeneous many-core architectural research. The presented...

Air MozillaProduct Coordination Meeting

Product Coordination Meeting Duration: 10 minutes This is a weekly status meeting, every Wednesday, that helps coordinate the shipping of our products (across 4 release channels) in order...

WebmakerReflections on the Webmaker Launch

With the official launch of Webmaker last week, we wanted to share some early results, talk about our ongoing promotion of the new app and reflect a bit on how we’ll be evaluating success and impact in the weeks and months to come.


Assessing Product/Market Fit

With this launch we’ll be refining our understanding of product market fit, specifically as it relates to target markets and audiences and future product iterations: Is it a compelling experience for a large number of people, how and what do they do with the app, do they find the app useful over time and do they share it with friends and community? Furthermore, does it have meaningful impact as a learning and content creation tool in support of our goal to get more people reading, writing and participating on the Web?

“It’s now feasible for many people to access the web, but contributing to the web? That’s harder, since you usually need money, know-how or both to create much more than a Tumblr page. Mozilla thinks it can help, though. Its just-finished Webmaker app lets anyone with an Android phone create web content.” –Jon Fingas, Engadget

Initial Results

  • over 21K active users of the app and nearly 31K total downloads since the Beta launch in late-June.
  • users in 188 different countries
  • Top 5 countries of use are India (13%), US (12%), Indonesia (10%), Bangladesh (5%) and Brazil (5%)
  • over 20K projects created and nearly 5K projects shared
  • 69 press stories, in 22 countries, and nearly 5K social media mentions
(snapshot of real-time app usage from 8/24)

(snapshot of real-time app usage from 8/24)

What It Means

We don’t have enough time elapsed or enough feedback – yet – to make any real assumptions about the relative success of the launch. But, it definitely feels like a good start. The buzz was significant, overwhelmingly positive in tone, and thousands of people are downloading and using the app. And our initial focus on a small number of communities appears to be paying off – those are the places where we are seeing the most activity.

To help us answer the core question of product/market fit, we’ll be looking at a variety of quantitative and qualitative metrics over the next 30-60 days:

  • Active users, particularly as it relates to acceleration and week-over-week and month-over-month growth rates
Retention rates, measured by how many users are still active at 7 days and 30 days, or inversely by churn and uninstalls
  • Engagement rates, by looking at number of makes and shares per user, to evaluate stickiness
  • Virality, as measured by total shares and, more importantly, new users added via shared projects
Locale-specific growth and retention rates, to evaluate cost/benefit in our core locales and to identify additional locales to focus on
  • Popular content types as measured by makes and shares
Qualitative feedback from Google Play reviews and support channels
  • Qualitative feedback from community

The Launch Campaign

The secret to our success has been – and will continue to be – an incredible community of Mozillians passionate about the work we are doing and showing incredible effort and initiative in promoting Webmaker. In Indonesia, Bangladesh and Brazil in particular, small teams of motivated individuals have stood up over 40 events (with more planned), deployed social media campaigns and effectively reached out to media to have our story told publicly. There’s a lot more planned in the coming weeks and it’s already clear that we have community-generated momentum on our side.

In support of the remarkable effort by the community, we also deployed a campaign through our marketing and communications channels, including:

  • Launch blog on and, which was quickly translated by many of our communities
  • Global promotion on the snippet
  • Promotion on, and on new tab page in Firefox
Emails to Webmaker, Mozilla Learning Network and Reps communities
Heavy promotion on social through @mozilla, @webmaker and @mozteach
Localized ad campaign on Facebook in ID, BR, BD and KE
Press outreach in North America, Brazil, Indonesia and Bangladesh
Webmaker workshops in Indonesia, including more than 40 school visits
Message testing on landing page, email, snippet and paid Facebook ad campaign

In the weeks to come, we’ll be doubling down on the tactics above, testing additional channels, expanding our grassroots events to more places, optimizing messaging and creative, focusing on onboarding and retention communications and expanding support for community and partner initiatives.

Cool Things People Have Made with Webmaker This Week

The most fun part of the first week has been seeing the incredible things people are creating with the app. We’ve seen wonderful, diverse and creative examples of what’s possible with the app:

This list is just a small sampling of what we’ve seen to-date and we’ll be featuring more of this great content in the weeks to come. Spread the word about Webmaker by sharing this graphic on your favorite social network:


Air MozillaBugzilla Development Meeting

Bugzilla Development Meeting Help define, plan, design, and implement Bugzilla's future!

Meeting NotesChannel: 2015-08-25


  • bhearsum, hwine, KaiRo, lizzard, jst, rrayborn, sylvestre, milan, ritu, jlund

Schedule Update

  • 40.0.3
    • Dot release & chemspill
    • Go to build planned for tomorrow (Wed)
      • Might conflict with the ftp changes
    • Top crash on GNU/Linux – bug 1145230
    • Two webcompat issues:
      • ja web compat issue – bug 1194055
      • can’t select value in combobox controls using the mouse on some sites – bug 1194733
    • Yahoo partner change – bug 1195683
    • Graphic startup crash (DisplayLink) – bug 1195844
    • 3 security fixes
  • ESR 38.2.1
    • Affected by the security issues too
  • 41
    • Beta4 (Desktop) was pushed to Beta channel
    • Beta4 Mobile SignOffs pending. ETA: Tomorrow
    • Security fixes will most likely be included in Beta5



  • Overall rate: 4.0 (target: <1.5), browser: 1.3, content: 2.7 (similar to last week)
  • top browser process issues: bug 1127270, bug 1188415
  • top content process issues: bug 1116884, bug 1163735, bug 1196799


  • Overall rate: 0.9 (even improved from last week)
  • bug 1158189 (HTTP shutdownhang) is 2% of all 41.0b3 crashes
  • bug 1196859 (probably Roboform) is 1.6% and #1 Top Crash Score, needs uplift
  • bug 1178271 (dom::Promise::Settle) is 1.4%
  • bug 1196696 (MediaFormatReader::DecoderData::ResetDemuxer) is 0.9% but media code
  • bug 1173579 (startup, gfxFontGroup::GetDefaultFont) is high (#5) in Top Crash Scores


  • Overall rate: 0.9 (unchanged)
  • bug 1145230 (linux, gstreamer) and bug 1195844 (DisplayLink, startup) uplifted for 40.0.3
  • bug 1189940 (NVidia) still dominating Win10 topcrashes (>15%)


  • beta crash rates still somewhat high
  • kindle tablet users are downloading the wrong version of firefox (bug XXXXX?)

Performance (Thu)


  • final sign-off for b4 coming after this meeting


User Advocacy

No updates

Special Topics

Post-Mortem (Tues 2wks from GA Release)

Channel Meeting Details

Video/Teleconference Details – NEW

  • 650-903-0800 or 650-215-1282 x92 Conf# 99951 (US/INTL)
  • 1-800-707-2533 (pin 369) Conf# 99951 (US)
  • Vidyo Room: ReleaseCoordination
  • Vidyo Guest URL

Meeting NotesThunderbird: 2015-08-25

Thunderbird meeting notes 2015-08-25. NOON PT (Pacific). For meeting time, previous notes and call-in details see


  • wsmwk, aceman, fallen, makemyday, jorgk, rkent, mkmelin, clokep

Action items from last meetings

  • Get release documentation into wiki

Current status and discussions

Critical Issues

Leave critical bugs here until confirmed fixed. If confirmed, then remove.

  • needs assignee after solution identified – bug 1196662 not checking mails after hibernation, caused by core bug 1178890 (and we may be seeing other issues from 1178890, like hangs)
  • aceman is assignee – bug 1183490 – (dataloss) New emails do not adhere to sort by order received
  • status TBD – bug 1182629 – update to 38.1.0 from 38.0.1 re-enables disabled Lightning
  • status TBD – bug 1176399 – Multiple master password when GMail OAuth2 is enabled
  • status ??? – bug 1176748 – Someone needs to add additional main thread proxies to the migration code (jorgk and m_kato have in previous years been the major drivers of fixes)
  • topcrash bug 1149287 is ** 31% of our crashes** – see below

removing from critical list/fixed:

Critical for TB42 and beyond:
bug 1193200 – Blocker: Permissions manager/Remote content exceptions


  • Past
    • 38.0.1 nominally shipped 2015-06-12
    • 38.1.0 shipped 2015-07-10
    • 31.8.0 shipped 2015-07-17
    • 40.0beta shipped 2015-07-27 (skipping 39.0b)
    • 38.2.0 shipped 2015-08-14
  • Upcoming
    • 38.3.0 ~2015-09-23
    • 41.0beta ~2015-08-10
    • 42.0beta ~2015-09-26


Past releases:

Upcoming releases:


  • Still need help rewriting SUMO help articles on Lightning
  • Need to fix bug 1194997 for calendars disabling themselves

Round Table

Jorg K

  • bug 772796bug 1174452 – M-C Editor problems to do with pre and “white-space: pre;” currently stalled.
  • bug 368915 – change language in subject (language button), ready to land.
  • bug 1197687 – Font menu again, waiting for Neil.
  • bug 1020181 – Set spell check language for recipient (published add-on as quick fix).


  • developers need to be thinking about landing stuff now, and in the next 2 months, for version 45 moves to aurora dec 14
  • HWA – collected more data and filed bug 1195947 Track HWA issues
  • crashes
    • 38.2.0 crash rate ~0.35, dramatically reduced from ~.5 for 38.1.0 likely mostly due to disabling HWA. Only ~6 GPU crash signatures in top 200 and the highest rank is 80 (vs several in top 20 for 38.2.0), so most GPU driver crashes seem to be gone (but not all of the crash rate reduction will have been just from disabling HWA)
    • topcrash bug 1149287 is **31% of crashes (1)** and needs much work because it’s got multiple causes. Some reports implicate McAfee, some are not “shutdown” because user is hung or waiting on some prompt or protocol issue (only then does user try to close and crashes). (speculating) Are some caused by timer issues from bug 1178890? See the comments (1)
    • lacking time to follow up on other signatures in the “new” topcrash rankings (but that’s OK because we’re very well off compared to 38.1.0)
  • following progress of Thunderbird web pages moving to bedrock – they are close to being done
  • beware – ishikawa in the next several weeks will be landing big changes from many (>12?) bugs, both core and Thunderbird, for IO performance and error checking, eg bug 1116055


  • Patched a lot of build issues, together with aleth



  • I think we have made progress on maildir issues, I hope to get two critical issues fixed before the next release.

I’m finally starting to turn more of my attention to management issues rather than urgent TB 38 problems. In the long run, those are very important, but the urgent easily crowds out the important. Kudos to those trying to get the tree usable again!

We could talk about:

  • Our thoughts on the announced changes to addons (Including not only
    • require signed vs unsigned?
      • no upside? i.e. we have no identified exploits
      • need to wait for enterprise impacts to be resolved
      • concerned that because the “unsigned process” will be no longer used by AMO, it may impact ability to push out unsigned THunderbird addons using the script they used to mass sign Firefox’s unsigned addons
    • XPCOM/XUL deprecation
      • need to make sure we are involved in the conversation and decisions so that developers have what they need in the “new environment”
  • Patrick is happy to do Enigmail integration into Thunderbird, I think we should agree. comments?
  • Joshua, Suyash, and I are working on the SkinkGlue (now JsAccount) integration, which will be the basis of both JMAP and CARDDAV support. –> consider using for carddav support
  • Volker Birk of Pretty Easy Privacy is *very* serious about heavily engaging his Foundation with Thunderbird. Concerns?
  • Then there is the legal and financial home issue …
    • Expect a full-court press on MoFo by me soon, if you have contacts there please advise. One thing that is clear to me after talking to people is how critical Thunderbird is in the greater software world. We DO have a place at the table! How to get MoFo to see that?
    • We have submitted a formal application to Software Freedom Conservancy to affiliate with them, now we wait for their evaluation queue.
    • Very interesting talks with The Document Foundation(TDF)/LibreOffice. #1 concern: All of our energy goes into keeping up with Mozilla to allow us to optimize some future code development that we never actually have time for. Their funding model is very interesting, would be worth discussing.
    • hoping to meet with postbox in a few weeks
  • It would be really great if someone could lead efforts to prototype a fund-raising drive web page in-product. (hoping to target Oct/Nov)


  • looking at bug 1183490 (the order received regression), 2 options:
    1. back out bug 854798. Should be safe. I recommend this.
    2. finally drop msgkey=offset in mbox and just increment by 1. May be risky but there is already a precedent that msgs moved by filters already get key+1 so code expecting key==offset should have already been uncovered. However, there are still some unsure places, fixing which means basically bug 793865 (the 64bit envelope and msgkey!=offset cleanup). I would not recommend this for ESR.
  • finally looking to finish some feature patches (compose font selector, saved files tab, show map widget)

Question Time


  • Note – meeting notes must be copied from etherpad to wiki before 5AM CET next day so that they will go public in the meeting notes blog.

Help Wanted

SeaMonkeyCut….cut…. Take 3…

Wanna know what?

I goofed.  I messed up… a little.  ok. A bit more than a little; but nonetheless, I pushed the wrong patch (can I squirm for an excuse?  like…  gremlins?  aliens abducted my brain temporarily…though.. I don’t think they’d find anything great… ;P ) . This in turn, well… botched the build process.  Well, not the build itself, but the upload process.

Ergo… I now introduce to you all,  build 3.   I can tell you that this is the HIGHEST build number I’ve ever done before (and probably in the  history of SeaMonkey… *sigh*).

As I write this,  the Linux build was green and the upload was ok.  Now, it’s at the Linux l10n repacks.  Once those go green (here’s hoping), it will be my turn to work on the Win32 builds/repacks.  (Didn’t I say this was going to be ‘fun’ and ‘challenging’ earlier?… yup… I did… and boy is this nerve wracking.)

So again, we really do appreciate your patience, especially with my fumblings.  But, as I quote, ‘if you don’t succeed, try try try again…’



Air MozillaMozilla Learning Community Call Aug 25

Mozilla Learning Community Call Aug 25 Mozilla Learning community calls are open to all. The goal: work on the Mozilla Learning plan together.