No More Snappy Meetings and Other Changes from the Snappy Team

I want to summarize a few operational changes coming out of a team discussion during this week’s Snappy work week.

Snappy is a collection of mostly discreet sub-projects. For example, Paulo’s work to make downloads async does not overlap with Benoit’s work on the profiler or Vladan’s work on improving start-up. The changes listed below are based on suggestions from the Snappy team for ways to better support Snappy’s project structure, improve project predictability, and reduce meeting inefficiency.

Project definition and leadership

We are going to be more explicit with our project definitions by listing high level requirements. There is also now a stronger requirement to scope the project. This means spending time thinking through the project before starting to code.

We will also identify the key project team members and a project tech lead.

Project tech lead responsibilities

In addition to providing technical direction for a project, the project tech lead will be responsible for:

  • organizing and running project meetings
  • blogging biweekly about the project

No more Snappy meetings

In an attempt to make better use of our collective time, the Snappy meeting will be cancelled in favour of project specific meetings. The goal is to have shorter meetings that are more on point for the attendees.

Monthly performance program reviews

A new, monthly performance meeting will be established to review quarterly progress and discuss project delays. This meeting will also be an opportunity to discuss new project proposals and review overall performance goals.

Daily updates

Due to the increased time between larger project meetings (monthly instead of biweekly), we will try short, daily updates via IRC. We will experiment with statusbot for managing and logging daily updates and aggregate updates in Benjamin Smedberg’s weekly updates tool. The goal of daily updates is that each team member’s work should be visible. i.e. Managers and tech leads should not need to ask what you are currently doing. Each team member is responsible for pinging statusbot in the #perf channel daily.

Posted in mozilla | Tagged , , , | 4 Comments

Horsehead Saga Timeline

The Mozilla Toronto office has been horsing around with our neighbours across the way. Johnath wrote up a very nice account of what has transpired over the last few weeks. For those that are following along, I present the Horsehead Saga Timeline. (I’ve done my best with dates and pics but am open to corrections and additions.)

Posted in mozilla | Tagged , , ,

Help wanted: Firefox OS UA detection

Firefox for Android and Firefox OS, while based on the same Gecko platform, have one key difference with respect to compatibility: their user agent (UA) string. The difference between the UA strings for these two products is the inclusion of the “Android” token in the Firefox for Android UA. The lack of an “Android” identifier for Firefox OS is a good thing, in that it provides sites that employ UA detection to detect Firefox OS as a non Android device and subsequently suppress their Android specific endorsements. However, our research has shown that a large number of sites detect the presence of the “Android” token rather than the “Mobile” token to indicate that a client is a mobile device. Firefox OS, therefore, is frequently misidentified as a non mobile device and served desktop content.

For the initial launch of Firefox OS, we created an UA override mechanism the allows Firefox OS to identify itself as Firefox for Android. This mechanism ensures that Firefox OS receives mobile content for top sites. However, this mechanism is a short term solution and does not scale to the scope of the Web. What we want is to clear out this list by having sites recognize Firefox OS as mobile.

The UA override list currently contains 132 entries. All of these sites have undergone some measure of quality assurance from Mozilla or one of our partners and each has been demonstrated to be functional on Firefox OS.

Here’s where we need your help.

Do you, your friend, your relative, or other acquaintance work for one of the sites on this list? If so, please speak with them about changing the site’s UA detection to recognize Firefox OS. If UA detection is to be used, Mozilla’s recommendation is to detect the “Mobi” token, which will allow for the identification of the greatest number of mobile clients.

For your reference, the Firefox OS UA is:

Mozilla/5.0 (Mobile; rv:18.0) Gecko/18.0 Firefox/18.0

Don’t know anyone at any of these sites but would still like to help? Look for other ways to contact the sites. Other ways that we have found to be effective are to ping the site on Twitter, submit a trouble ticket via the site support or feedback forms on their website, or try e-mailing catchall addresses like

The open list of sites with UA overrides can be found in Bugzilla. For your reference, I have also listed the sites that currently have an UA override below.

2013-09-03 Update: Further overrides removed.

2013-03-06 Update: Great support and progress thus far! I will cross off the sites on the list as they are fixed.

Posted in mozilla | Tagged , , , , | 22 Comments

DateCountdown Wikimo Template

Have you ever wanted your wiki page to include an automatically updated countdown of the number of days until some event? Well now you can. I have added a DateCountdown template on that does just this. Using this template you specify a date and the wiki will automatically display the number of days left until that date. After the date passes, the wiki will display “0”. This is useful for event countdowns like, days to the next merge, days to next release, or days left in a sprint or iteration.

Use the DateCountdown template as follows:


where DATE should be of the form yyyyMMdd. For example,

Days to Firefox 17 release: {{DateCountdown|20121120}}

The output of which is (today only):

Days to Firefox 17 release: 11

For a date that has passed, like the Firefox 16 release date:

Days to Firefox 16 release: {{DateCountdown|20121009}}

The output is:

Days to Firefox 16 release: 0

For live examples, see the platform meeting agenda, where the release management team has used the template to show the days left until the next merge and release. It has similarly been used for the coordination meeting agenda.

Posted in mozilla | Tagged , ,

Mobile Web Compatibility Nov 9, 2012 – Video update, UA detection tools, Phony for B2G?

Video update

I gave a short update about mobile Web compatibility during the Oct. 22, 2012, Mozilla project meeting. This update should bring you up-to-speed on the problem and the various initiatives that we have underway to tackle it. The video is available via Air Mozilla (skip to 4:00).

Help wanted: deep dive investigation

Are you a Web dev? We need your help deep dive testing a short list of sites. The goal of this exercise is to understand why after spoofing the user agent and aliasing Webkit prefixed CSS properties these sites are still broken. Details and the site list are in my post Call for Help: Broken Site Deep Dive Investigation.

Phony functionality in B2G

To better support mobile Web compatibility testing on B2G, we need Phony type functionality to switch the user agent. I have started a discussion on the dev-b2g list and filed bug 810075. If you have ideas or can help with the implementation, please comment.

Site testing and outreach

Over the past couple of week I have spoken with Categorizr,, and WURFL, all user agent detection tools/frameworks. Categorizr and 51degrees correctly identify Firefox for Android mobile + tablet and Firefox OS. I am working to provide WURFL with an update as well.

Joe Drew spoke with, who will start recognizing Firefox OS shortly.

Facebook has fixed their drop-downs for Friend Requests, Messages and Notifications (bug 715515).

Jason Smith and I held a test event in the Mozilla Mountain View office and on Air Mozilla on Oct. 23. Test results were submitted for 45 additional sites. Thank you to everyone who contributed.

Want more debugging tools for Firefox for Android? Mark Finkle blogged about the new remote console for Firefox for Android.

Interested in helping with site testing and evangelism? See Gerv Markham’s blog post Website Evangelism: Mobilizing Mozilla.

Posted in mozilla | Tagged , , , , , , , , , , ,

Call for Help: Broken Site Deep Dive Investigation

Not too long ago we kicked off an analysis to answer the question,

Does aliasing a subset of Webkit CSS properties in Gecko improve mobile Web compatibility?

The preliminary results of our small study showed little improvement. The next step in this analysis is to understand why the sites that were tested are broken even when aliasing Webkit prefixes in Firefox.

This is a call for help and your call to action. The sites to test are listed below. We need to know as much detail about why each site is broken as possible. Ideally, the for each site we will have a report that includes the lines of code that are broken and a suggested fix. It will benefit us to know any JavaScript frameworks that have issues. As we have already seen, it is common that the resolution of one site issue causes a new issue to become exposed. We need a complete list of issues in order to best decide how to target fixes. Ultimately, we will need to answer question like, can we make a set of changes to Gecko, possibly including Webkit CSS prefix aliasing, that does make a significant difference for mobile Web compatibility? Are the issues primarily in site specific code or a common set of frameworks?

Results can be reported by filing bugs against the Tech Evangelism: Mobile component or by sending them to the compatibility mailing list.

Site list with visible issues (as reported by Mozilla QA)

    1. Completely broken on FF Android. Appears to be broken by looking for the Webkit JavaScript value “WebkitPoint” that does not exist in Gecko.
    1. White screen renders on page
    1. Slideshow of icon shortcuts don’t allow swiping left and right
    2. Missing colors on certain buttons.
    1. ads and transitions within ads are not shown correctly
    1. colors for refresh button are not right
    2. text is occasionally blacked out when scrolling page
    1. ads don’t render
    1. very obvious layout issues in comparison to Android stock browser
Posted in mozilla | Tagged , , , , , , ,

Come Test the Mobile Web! Tues Oct 23, 2012 – 12pm PT

To support our mobile Web compatibility evangelism efforts, we need to understand the top site issues. Come out tomorrow at 12pm PT to test the mobile Web and report issues. No experience necessary. We’ll help you get your test environment set up and get testing with Firefox for Android.

For those in Mountain View, we’ll be in 10 forward with what I’m told is most excellent pizza. We’ll also be streaming live on Air Mozilla.

Want to learn more about mobile Web compatibility? Watch my presentation from today’s Mozilla project call.

Posted in mozilla | Tagged , , , , , , , ,