From MozillaWiki
Jump to: navigation, search
« previous week | index | next week »

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

These notes are read by people who weren't able to attend the meeting. Please make sure to include links and context so they can be understood.

Schedule & Progress on Upcoming Releases (Lukas/Sylvestre/Lawrence)

  • 32.0.1 updates are disabled
  • 32.0.2 driver
    • bug 1063052 Firefox 32+ startup crash in nsFrame::BoxReflow
  • 33 beta4 desktop released yesterday
  • 33 beta4 mobile released today
  • lmandel is soliciting feedback on 32. If you didn't attend yesterday's post mortem, please send feedback via e-mail.

Firefox Desktop & Platform (Javaun/Chad/Martin)

Summary of Work In Progress

  • You can find the most recently completed iteration (35.1) performance report here
  • You can see the status of the current iteration (35.1) in progress here
  • OMTC maybe in 33 if some linger issues can be resolved, more next week on this once final determination can be made. (Bug 899785)
  • Picture Tag is currently slated for 33 but may push back to 34 depending on the outcome of some bugs currently being investigated. (Bug 1017875)


Beta (128)
  • Enhance tiles more specifically than eTLD+1/baseDomain (e.g., no enhance for ( Bug 1045760 )
  • Include OpenH264 plugin in FHR data ( Bug 1053745 )
  • Avoid flushing layout and making it dirty repeatedly in ToolbarIconColor.inferFromText ( Bug 1061947 )
Aurora (54)
  • Undo the pref for the temporary hangserver for beta channels until Socorro is awesome ( Bug 791244 )
  • Backslashes included in a location bar input are converted to forward slashes on submission ( Bug 1042521 )
  • Tab-modal onbeforeunload dialog can automatically be dismissed by navigation ( Bug 1046022 )
  • Missing inverted panel help icon on Yosemite ( Bug 1060944 )
  • toolkit/themes/osx/global/in-content/common.css uses broken @focusRingShadow@ - focused link styling on about:preferences et al. can't be parsed correctly ( Bug 1062843 )
  • disable unified autocomplete for Firefox 34 ( Bug 1064776 )

Summary of Recent Landings

  • Team landed 42 bugs over the last week, to close out the 35.1 iteration.
  • Details of landings from the past week can be seen here

UX (Madhava)

Firefox Mobile (Mark/Brad/Jenn)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Uplifts from the past week

Beta (128)
  • Remove gradients from form elements ( Bug 763671 )
  • Lightweight theme preview is broken ( Bug 887755 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange( ( Bug 1041448 )
  • crash in mozilla::layers::TileClient::GetBackBuffer(nsIntRegion const&, mozilla::layers::TextureClientPool*, bool*, bool) ( Bug 1041744 )
  • Regression: Back button icon missing in menu on some small screen (?) hardware (?) devices ( Bug 1062338 )
  • "Learn More" link for the Mozilla Location Service is visible on Beta/Release despite MLS setting not available ( Bug 1063518 )
  • crash in webrtc::ViEInputManager::NumberOfCaptureDevices() ( Bug 1063547 )
  • crash in java.lang.NoSuchMethodError: android.os.Bundle.getString at org.mozilla.gecko.preferences.GeckoPreferences.setupPreferences( ( Bug 1065531 )
Aurora (54)
  • Regression: Browser menu has width issues ( Bug 1020505 )
  • Too many differing background greys throughout the browser ( Bug 1055536 )
  • crash in java.lang.IllegalStateException: Already registered Wifi:Enable at org.mozilla.gecko.EventDispatcher.registerListener( ( Bug 1061030 )
  • Regression: No context menu action is invoked on long-tapping some links ( Bug 1062307 )
  • Use empty string as title if no title provided when adding a bookmark ( Bug 1062552 )

Landings from the past week

Nightly (129)
  • Synchronous initialization of search service when handling open search tag ( Bug 1017903 )
  • [Roku] Removing an entry from history will only take effect after restarting the Roku app ( Bug 1025923 )
  • about:home is unresponsive to hardware menu button on returning to main activity on 2.3 devices ( Bug 1058027 )
  • [roku] update wording in the public roku channel app ( Bug 1064222 )
  • Search activity startup crash @ java.lang.IllegalArgumentException: Couldnt find search engine for identifier: yahoo at ( Bug 1065123 )
  • Regression: Downloading is broken ( Bug 1066671 )

UX (Robin)

Developer Tools (Jeff/Rob/Dave)

Feedback Summary (Cheng/Tyler/Matt)



Market Insights from the Market Strategy Team (Kev)

Something to Think About

The stock Android browser, which is the default browser on Android versions below 4.4, has a vulnerability that allows malicious sites to bypass the same-origin policy and execute an XSS attack. Metasploit contains a live exploit for the bug, which could potentially affect more than half of Android browser users. Updating the stock browser is not really something that's been done since Kitkat came out, although Google has apparently said they'll launch a fix, it's just unclear how that fix will be delivered.
Why we should care: A continually updated, modern browser that works on the majority of Android devices is something every Android user should want (and know about). Firefox for Android meets that need, and we should consider reminding people of the risk and solutions that Firefox brings to older versions of Android.

Worth a Read

  • Google launched Android One in India Monday. They're using a familiar "the next x billion Internet users" line, and tying "One" to the user. Lots of hardware partners with MediaTek and Qualcomm as the chipset providers, with some phones coming with data included for installing apps from Google Play to help drive use, some region-specific features (like dual sim support, offline YouTube, monthly included data for the play store, etc.), and Google managing the software update process. Also notes on intent to expand through Southeast Asia in the near future. Android One website
  • Google appears to be experimenting with making simple searches a little more useful in Chrome on Android. A flag can be set to enable answers (accessed via chrome:flags), which makes use of the search suggest facility to deliver more than just keywords. Search monetization and use has been more difficult on mobile, and this is a good example of some of the ways search providers are going to look to make search more of a go-to, and perhaps generate revenue from for things like location specific results, promotion weighting, etc. Answers has also been available on Desktop Chrome for a while, but the answers delivered are more limited than what's being delivered on mobile.


Marketing, Press & Public Reaction (Arcadio)

Questions, Comments, FYI