Meeting Notes Meetings notes from the Mozilla community


Mobile Meeting Minutes: 2011-11-09

Filed under: Posts — Tags: — Jesper Kristensen @ 12:00 am



  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 95312
    • US/International: +1 650 903 0800 x92 Conf# 95312
    • US toll free: +1 800 707 2533 (pin 369) Conf# 95312
    • Canada: +1 416 848 3114 x92 Conf# 95312
  • #mobile for backchannel
  • vidyo: Warp Core


  • Merge happened yesterday
  • Next merge date is 2011-12-20

Major Topics for This Week

  • A release roadmap for Fennec Native is coming soon
    • Trying to overlap with normal release channels
    • Likely release 1.0 from birch
  • Working on a change to UA
    • The big issue is how do we get websites to send Firefox Mobile ideal content
    • The UA itself is only seen as a step to get better content
    • See bug 701056 for a different approach
  • Landing of the Pan/Zoom patch queue
    • kats/cwiis/dougt/blassey/patrick looking a general test failure
  • Adobe dropping Flash


Native Front-end

Android Platform

Stand ups

Suggested format:

  • What did you do last week?
  • What are working on this week?
  • Anything blocking you?



Last week

  • Started looking at find-in-page, then dropped it for higher priority things
  • Mostly working on the pan-zoom patch queue:
    • Fixed up some pinching/panning behaviour
    • Put up a patch for having per-tab scroll/zoom information
    • Put up a patch for saving/restoring scroll/zoom information for the screenshot
  • This morning: fixed a bug causing crashes on Honeycomb
  • Hopefully figured out what was causing the pan-zoom build to fail tests

Next week

  • Continue working on pan-zoom issues
  • Pick up other P1/P2 issues as needed


  • Need to land birch-pan-zoom! Working in patch queues has very high overhead, and generally is FAIL.


Last week:

  • mobile network disk cache has been enabled (finally!)
    • 10 M capacity
    • see about:cache
  • build startup cache at package time: works for development environment, but there are complications for nightly builds — discussing with ted and jmaher (bug 696095)
  • network cache compression: testing, analysis in progress

Next week:

  • wrap up startup cache
  • concentrate on disk cache


  • Last week
    • Investigated IME bugs: 630576, 632538, 696319, 698419, 698352, 697838, 699465, 667619.
    • Implemented a WIP patch for the bug 630576
    • Finally got a phone with hardware keyboard to work on the HKB-specific bugs
    • Submitted a patch for hardware keyboard bug 697773 “Cannot type in AwesomeBar URL bar with hard keyboard”, but this broke the touch mode, so needs another solution.
  • This week
    • Continue working on IME bugs, focus on HKB-specific ones

Chris Lord


  • Last week: Finished popup doorhangers. Doing some UrlClassifier patches.
  • Now: Finishing up those patches wrt review comments. Will be looking at bugs. If no more urgent issues, will look at Download Manager.
  • Blockers: Nothing

Brian N

  • Last week
    • Search engines
    • Pan/zoom dead space patch
    • Telemetry opt-in UI
  • This week
    • Finish search engines
    • Pan/zoom
  • Blocked on
    • Nothing


  • Last Week:
    • Completed the tabs-list as per UI Spec
    • Implemented stacking of doorhangers
    • Moved doorhangers to the top
  • This Week:
    • Landed fixing the “drawable” folders for menu
    • Working on reskinning doorhangers
    • Working on animating tab increment/decrement counter
  • Blockers:
    • Resources for doorhangers from Patryk


Last week:

  • Touch events – bug 603008 -> Patches are up. There’s a build at if people want to play/compare to others. Report problems in the bug. Waiting for review. Also, the layers stuff breaks the widget half of this in major ways.
  • UA string stuff. Happy to let dicussion continue for another few days. Then want to make a final decision.

This week:

  • Double Tap zoom
  •  ? Responsiveness ?
  • More context menu entries

Blocked on:

  • Startup crash for new ‘layers’ builds
  • UX for context menus. What do we want to keep? Throw out?


Last week

  • AwesomeBar screen as per design
  • Favicon caching
  • Misc cleanups

Next week

  • Follow-up bugs on favicon cache and awesome screen
  • Misc bug fixing

Blocked on

  • Nothing.



Last week:

This week:

  • Continue work on form history and about:config


Last week:

  • fixed usage of Cursors bug 700218 and bug 700922
  • fixed incorrect screenshot after clearing app data bug 699716 (hasn’t landed)
  • fixed usage of AsyncTasks bug 700354 (hasn’t landed)
  • fixed screenshot behavior with user defined profiles (for testing) bug 700917
  • added support for overriding package name with test scripts bug 700797

This week:

  • help land patch queue

Blocked on:

  • landing of patch queue


  • lots of merging
  • lots of reviews
  • lots of meetings
  • Helping land the panning zooming patch queue
  • fixed some of the offline mode bugs we had



  • More reviews!
  • Landed basic Password Manager prompts
  • Close to asking for review on the new add-ons manager
  • Banging head on mobile UA story


  • Add support for new DoorHanger features so we can finish PasswordManager w/ Doorhangers
  • Land basic add-on manager rewrite
  • Encourage some additional context menus – great first bugs for contributors!
  • Get around to blogging

See online status


  • Last week: Add-ons flow revisions (done), cataloging missing pieces
  • This week: sync setup and pref flow, prefs, bugs open on missing pieces (i.e. these and these

Ian Barlow

  • Last week:
    • Lots of mocks and specs
    • Awesomescreen [1]
    • Tab menu [2]
    • Header / URL Bar states [3]
    • Menu Icons [4] 🙂
  • This week:
    • UI Reviews, filing bugs
    • Working on new designs for a Start Page, Reading Mode,
  • Blockers: Nope

Patryk Adamczyk

Last Week
+ Door hanger designs: updated as per Sriram request included in bug #698598
+ Add ons: created a flow / mock up designs with various scenarios and attached them to the add ons bug #696532

This Week
Supporting dev in implementation if any new graphics are needed.


Round Table


Talos has been random orange since last thursday. We need to address this. I propose we back everything out since the last solid green (Doug’s push on Wednesday). People will need to reland their patches after that.

Going forward, we may need a birch sheriff or some other mechanism to make things better.


  • P0, P1 features have all been assigned to Test Owners. Next step, testcases; bug triaging; testday (this friday)
  • Flash is now on Aurora are we still planning on disable by default?
  • Crash report changing from this to more simplified version of Native only crashes.
    • will continue to report and monitor other channels, report is just simplified
    • If there are any more improvements to make it easier to look at please let nhirata know.
    • big crash following the quit – bug 700720 (not in the current report as of yet) Kats got this fixed.
  • Performance :
    • Working with Waverly to crunch numbers
    • cTalbert has stuff automated as can be seen in elancaster’s video; missing part is that it needs to log to a server. he will have something towards the end of the week.


  • (aki)
    • Tegras have low wait times + are afaik on par with n900s. Is there anything preventing us from turning off Maemo builds/tests?
    • Who should I speak with re: Android single locale repacks?
    • Do we still have a need for linux qt builds?
    • Do we need mobile desktop builds on checkin on all branches?
    • Now that FF8.0 has shipped, and 7.0 is EOL’d, we’re going to close out remaining maemo bugs.

No Comments

No comments yet.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Powered by WordPress