These Weeks in Firefox: Issue 17

Highlights

Friends of the Firefox team

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

  • Resolved bugs (excluding employees):
    • More than one bug fixed: https://mzl.la/2rwO12P
      • Dan Banner
      • Kevin Jones
      • Milind L (:milindl)
      • Swapnesh Kumar Sahoo [:swapneshks]
      • tfe
    • New contributors (🌟 = First Patch!)
      • 🌟 jomer14 got rid of some leftover l10n files that Firefox Accounts didn’t need anymore!
      • 🌟 Pauline got rid of PlacesUtils.asyncGetBookmarkIds (which isn’t needed anymore thanks to Bookmarks.jsm), which also reduced our memory footprint!
      • 🌟 Shashwat Jolly cleaned up some of our strings in about:license!

Project Updates

Activity Stream

  • ‘Graduation’ team is getting close to preffing on Activity Stream in Nightly and working on Search Suggestions, about:home, cleaning up tests, and perf telemetry
    • Aiming for more regular / weekly landings from github to mozilla-central
    • Replaced custom React search suggestions from Test Pilot with existing contentSearchUI used for about:home/about:newtab simplifying tests
  • Test Pilot team is finishing up customization (drag’n’drop, add/edit topsite), as well as beginning work on Sections
  • Activity Stream, when enabled on m-c runs in the content process!
  • Removed most of Content Services / Suggested Tiles code from about:newtab resulting in perf improvements and removed / ~8x fewer intermittent test failures

Electrolysis (e10s)

  • The e10s-multi team is still looking over the data being gathered from the Beta population against the release criteria to determine whether or not e10s-multi will ship in Firefox 54, or will have to wait until Firefox 55
  • e10s-a11y support in Firefox 55 has been marked “at risk” due to stability issues. A go/no-go will be happen no later than June 3rd
  • erahm has a blog post about how memory usage with 4 content processes continues to be the sweet spot

Firefox Core Engineering

  • Reminder: Firefox 55 is also installing 64-bit by default on 64-bit OS’s; updates will come later.
  • Resolved race condition in Rust runtime. This may have been bugging some tests (no pun intended).
  • We have preliminary top crashers lists from crash stacks sent via crash pings. Expanding that analysis is pending review of the data & correlation with crash reports.

Form Autofill

Photon

Performance

  • More rigorous reflow tests have landed for window opening, tab opening and tab closing.
  • Kudos to the Structure / Menus team for making the subview animations smooth as silk! (Notice that Oh no! Reflow! is detecting no synchronous reflows in that video)
  • Task.jsm and Promise.defer() removal big patches landed as pre-announced during the last meeting. This covered the browser/ and toolkit/ folders, more patches coming soon for other folders.

Structure

  • The page action menu has started taking shape and now has items to copy/email links, and will soon have a ‘send to device’ submenu;
  • Tomorrow’s nightly will have Firefox Account and cut/copy/paste items in the main hamburger panel;
  • Main work on the permanent overflow panel (as a replacement for the customizable bits of the existing hamburger panel) is done, working on polish and bugfixes;
  • Work will start on the new library button this week;
  • We’ll be working to flip the photon pref by default on Nightly in the next week or two;

Animation

Visuals

Onboarding

Preferences

  • Search is taking shape on Nightly! It now comes with the right highlight color, tooltips for sub-dialog search results. With the help from QA engineers, we are closing the gap between implementation & spec.
  • UX team asked us to revise re-org. The change will likely postpone re-org shipping by one release (to 56); the good news is the release population will be presented with the new search & re-org at the same time, if that happens.

Project Mortar (PDFium)

  • peterv made some progress of the JSPlugin architecture – the last few pieces of work are reviewing. Hopefully this is the final round of review, and we will land all of them (8 patches!) soon.

Search

  • One-off buttons in the location bar are ready to ride the trains in 55.
  • Search suggestions are now enabled by default. Users who had explicitly opted out of search suggestions in the past, will not see them.
  • Hi-res favicon improvements: the default globe favicon is now hi-res (SVG) everywhere in the UI and some ugly icon rescaling was fixed.

Sync / Firefox Accounts

Test Pilot

  • Containers experiment release 2.3.0 coming this week
    • adds a “site assignment” on-boarding panel to increase site assignments
      A screenshot of a panel explaining how you can choose sites that will always open in a container.
    • Also removes SDK code!
  • Screenshots feature is now aiming for 55
    • We’re hoping WebExtensions start-up will be performant enough by 55
    • Our backup plan: move UI (toolbar button, context menu item) into bootstrap.js code, lazy-load WebExtension on click
  • We’re planning to start a Test Pilot blog (with help from Marketing)
  • Test Pilot and experiments are moving away from the SDK

Looking into replacing Test Pilot addon functionality with a WebExtension API Experiment (learn more)

Here are the raw meeting notes that were used to derive this list.

Want to help us build Firefox? Get started here!

Here’s a tool to find some mentored, good first bugs to hack on.

Preview Form Autofill in Firefox Nightly

An early version of the new Form Autofill feature is ready for testing by early adopters with U.S. addresses and websites using Firefox Nightly on desktop. Form Autofill helps you fill out addresses in online forms. You can give the work-in-progress a try and watch it improve over time but keep in mind there are many more months of work left to go.

An address is selected from the autocomplete dropdown on the email field and the rest of the address fields are filled with the related saved information for that profile.

Firefox has an existing form history feature, which helps you fill out one field at a time using frecency. In contrast, Form Autofill completes all related address fields when you select a suggestion from the autocomplete dropdown on the focused field. Autofill profiles can contain one or more of the following: name, mailing address, phone number, and/or email. Multiple profiles are supported, so, for example, you can have separate personal and work profiles.

What’s currently supported

  • Basic address profile management for addresses that follow United States formats. For now you need to use this interface to create profiles for testing
  • Enabling/disabling the feature in preferences
  • Filling a form which uses the @autocomplete attribute on <input> elements for the supported fields, and with minimal transformations. This means it won’t work yet on most websites. Try it on our demo page, Macy’s, or any Shopify-powered store.

Coming soon on Nightly

  • Heuristics to determine field data types when @autocomplete isn’t used. This will make autofill work on many more sites.
  • In-content add/edit dialog UX
  • Support for <select> dropdowns
  • Automatic saving of submitted addresses and prompts to confirm changes after autofilling
  • Showing a preview of what will be autofilled upon highlighting an address in the autocomplete dropdown
  • Full UI translation

Before release

  • Support for credit cards
  • More data validation and cleansing
  • Sync between desktops with your Firefox Account
  • Significantly improved heuristics… there is a lot of work to do here yet
  • Support for more countries based on feedback from our localization communities
  • Support for data transformations on more types e.g. splitting a phone number into country code, area code, exchange, and number when required by sites
  • UI polish
  • Telemetry to measure accuracy of autofilled data as a quality metric

Try it out

To give Form Autofill a try, make sure you’re running Firefox Nightly and open Privacy preferences (you can type about:preferences#privacy in the address bar). Click the “Saved Profiles…” button beside “Enable Profile Autofill” and then click “Add” and save a new address. Then visit our demo page or other sites using the HTML5 autocomplete attribute, and you should see the autofill dropdown as seen in the image above.

Take a look at the Form Autofill wiki page for much more information and to get involved.

Thanks,
The Form Autofill Team

Try to find the patch which caused a crash.

For some categories of crashes, we are automatically able to pinpoint the patch which introduced the regression.

The issue

Developers make mistakes, not because they’re bad but most of the time because the code is complex and sometimes just because the modifications they made are so trivial that they don’t pay too much attention.

In parallel, the sooner we can catch these mistakes, the easier it is for developers to fix them. At the end, this strongly improves the user experience.
Indeed, if developers are quickly informed about new regressions introduced by their changes, it becomes much easier for them to fix issues as they still remember the changes.

How do we achieve that?

When a new crash signature shows up, we retrieve the stack trace of the crash, i.e. the sequence of called functions which led to the crash: https://crash-stats.mozilla.com/report/index/53b199e7-30f5-4c3d-8c8a-e39c82170315#frames .

For each function, we have the file name where it is defined and the mercurial changeset from which Firefox was built, so in querying https://hg.mozilla.org  it is possible to know what the last changes on this file were.

The strategy is the following:

  1. we retrieve the crashes which just appeared in the last nightly version (no crash in the last three days);
  2. we bucketize crashes by their proto-signature;
  3. for each bucket, we get a crash report and then get the functions and files which appear in the stack trace;
  4. for each file, we query mercurial to know if a patch has been applied to this file in the last three days.

The last stage is to analyze the stack traces and the corresponding patches to infer that a patch is probably the responsible for a crash and finally just report a bug.

Results

As an example:

https://bugzilla.mozilla.org/show_bug.cgi?id=1347836

The patch https://hg.mozilla.org/mozilla-central/diff/99e3488b1ea4/layout/base/nsLayoutUtils.cpp modified the function nsLayoutUtils::SurfaceFromElement and the crash occured in this function (https://crash-stats.mozilla.com/report/index/53b199e7-30f5-4c3d-8c8a-e39c82170315#frames), few lines after the modified line.

Finally the issue was a function which returned a pointer which could be dangling (the patch).

https://bugzilla.mozilla.org/show_bug.cgi?id=1347461

The patch https://hg.mozilla.org/mozilla-central/diff/bf33ec027cea/security/manager/ssl/DataStorage.cpp modified the line where the crash occured (https://crash-stats.mozilla.com/report/index/c7ba45aa-99a9-448b-91df-37da82170314#frames).

Finally the issue was an attempt to use an uninitialized object.

https://bugzilla.mozilla.org/show_bug.cgi?id=1342217

The patch https://hg.mozilla.org/mozilla-central/diff/e6fa8ff0d0be/dom/media/platforms/wrappers/MediaDataDecoderProxy.cpp added the function where the crash occured (https://crash-stats.mozilla.com/report/index/6a96375e-5c83-4ebe-9078-2d4472170222#frames).

Finally the issue was just a missing return in a function (the patch).

In these differents bugs, the volume is very low so almost nobody care about them but finally they reveal true mistakes in the code, so the volume could be higher in beta or release.
For the future, we hope that it will be possible to automate most of that process and file automatically a bug.

These Weeks in Firefox: Issue 16

Highlights

  • about:addons now has a legacy tag to show when an extension is not a WebExtension and addons.mozilla.org now specifically tags WebExtensions as compatible on Firefox 57!
  • The Activity Stream Test Pilot now shows recommended stories from Pocket, and you can  try the first bits of the Activity Stream integration in Firefox on Nightly by switching the pref browser.newtabpage.activity-stream.enabled

The new about:newtab featuring Activity Stream!

Friends of the Firefox team

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

Project Updates

Add-ons

Electrolysis (e10s)

  • gabor turned on the pre-allocated process manager, which should improve the perceived performance of opening tabs and windows in new processes
  • mconley is currently fixing a regression in the tab switch spinner metric
  • e10s-multi A/B test is currently underway on Beta
  • e10s-a11y support still targeted for Firefox 55

Firefox Core Engineering

  • Shield Study defaulting Flash to click-to-play (Plugin Safety) has begun on Release 53 and will run through June 15.

Form Autofill

Mobile

Photon

Performance
  • We are working on deterministic perf tests for sync reflows and files loaded too early during startup
    • Sync layout and style flush tests will be in browser/base/content/test/performance. When these become available, make sure to run these when you add Photon-y things!
  • Expect big patches to land to stop using Task.jsm in browser/ and toolkit/, and stop using the non standard Promise.defer from promise.jsm
    • If you have WIP patches for these folders, consider landing them soon to avoid bitrot.
Animation
Visuals
Onboarding
  • Fischer and Rex and Fred report that the team has been iterating on the overlay prototype for the onboarding experience
    • The team is in discussions with the Activity Stream team to figure out how the overlay will integrate with the Activity Stream page
    • The team is also sorting out integration with Firefox Account log-in, and Automigration
    • The onboarding overlay experience is currently being developed as a system add-on
Preferences
  • timdream reports that the team has almost finished scoping out the work for this project, and that this wiki page is a great way to track the team as they work
  • Please file about:preferences bugs! Preferably blocking the right meta bugs.

Privacy/Security

  • jkt is looking into rewriting containers to use WebExtensions instead of the Addon SDK
  • Our three Outreachy interns for May 30 – August 30 were announced last week:

Project Mortar (PDFium)

Search

Sync / Firefox Accounts

Test Pilot

Here are the raw meeting notes that were used to derive this list.

Want to help us build Firefox? Get started here!

Here’s a tool to find some mentored, good first bugs to hack on.

These Weeks in Firefox: Issue 15

A big thank you goes out to Johann Hofmann who put these headlines together while I was away on vacation!

Highlights

  • The Form Autofill feature is being enabled on Nightly this week (for @autocomplete on <input>). Stay tuned!
  • Firefox Screenshots is in Beta 2 preffed-off by default.  We’ll enable it very soon for everyone, or you can jump the gun by toggling extensions.screenshots.system-disabled .  If you run into anything fishy, please let #screenshots know

Friends of the Firefox team

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

Project Updates

Add-ons

Activity Stream

  • Test Pilot Activity Stream
    • Activity Stream support for Pocket has landed in Test Pilot version.  Experiment launches May 1st (thanks csadilek!)
    • You can try it now by using the Activity Stream Dev channel
    • Updated to latest eslint-plugin-mozilla which now supports mozilla-central external repositories, but need to disable no-useless-parameters as we support older than Firefox 55 (thanks Standard8!)
  • Activity Stream system add-on
    • Search feed and UI landed
    • TelemetrySender landed
    • Top Sites feed landed

Firefox Core Engineering

  • Flash
    • Telemetry experiment ran on Nightly 55 from April 14 – April 23.
    • Shield Study defaulting to click-to-play will start on Release 53 in the next week and run for six weeks.
    • Default and (slight) additional UI land in 55.
  • Crash
    • Crash pings contain raw stacks (opt-out) as of Beta 54.
    • Crash pings exist for main, content, and GPU processes as of Beta 54.
    • Crash pings are sent via pingSender (i.e. right away) as of Beta 54.
    • Only one bug did not get uplifted to 54 — a new data point added to the crash ping (a form of client crash id) as of 55.
    • Working on identifying top crashers (by signature) currently. Intending to land while 55 is on Nightly.
  • Install/Update
    • Continue with phase 1 of the Update Agent, which will continue/complete the download of an update even if a session ends.
    • Looking into trying to encourage users on FF4.0 – FF35.0 to update past 35 prior to September 2017 (when their update server, aus3, expires).
    • Fun with Nahimic: it can (and has) prevented updates. Follow 1356637 for updates.

Form Autofill

Mobile

Photon

Performance
  • Lots of sync reflow bugs filed, thanks! We now have a big backlog to triage.
  • Several fixes landed for sync reflows, especially around interactions with the tab bar (thank Dão!) and the awesomebar.
  • Starting to profile startup, and there’s a lot of room for improvement there (loading JS modules lazily from nsBrowserGlue, loading the blocklist from JSON instead of parsing a big XML file).
  • A few tips:
    • Avoid calling .focus() several times in a row, each focus call currently flushes layout.
    • Avoid using setTimeout(…, 0), Services.tm.dispatchToMainThread(…) has less overhead.
    • Avoid using Preferences.jsm (especially during startup) if it’s only to have support for default values.
    • Avoid importing NetUtil.jsm only to use newURI, use Services.io.newURI directly instead.
Structure
  • Work starting on page action menu
  • Ongoing work on the hamburger and overflow panel
  • Ongoing work on having more than one level of nesting within panel subviews (the slide-to-the-side thing in panels) and update their styling
    • All the previous stuff is / will be behind a pref. We aim to flip that pref on Nightly in the near future!
  • We swapped the sidebar to the right… and then swapped it back again. Expect more updates to sidebars in the future (with the side of the window stuff still under investigation).
Animation
  • Animations themselves are in-progress. We intend to use svg spritesheet animations for animating icon states
Visuals
Onboarding
  • Have walked through questions about the UX and visual specs with verdi from UX in today’s onboarding team meeting.
Preferences

Platform Audibles

  • Pending results of experiment, Flash will be marked as click-to-activate by default starting soon in nightly. Pending results of SHIELD study this will ride to 55 release.
  • We’ve got initial page navigation numbers comparing Chrome and Firefox
    • In general we’re competitive with Chrome (+-20%), but a few cases show us far worse, in particular back navigation: filed bug 1359400
  • A bug that caused windows to be ghosts if touch events were sent is causing large CC pauses in Nightly and Beta. Fix in tomorrow’s Nightly.
  • Initial data shows that mean-time-between-failure (MTBF) for input jank:
  • 70+% of nightly users last week saw GC pauses >0.5s
  • ASK: if you see slow things, please install/use the gecko profiler and file bugs!

Privacy/Security

  • jkt wrote a blog post about the new “Always Open In This Container” feature in containers.
  • freddyb is writing a series of ESLint rules to catch common security problems in Firefox code. First victim: Eval and implied eval.

Project Mortar (PDFium)

  • Three milestones are set for better estimating our release schedule
    • Milestone 1 (target on Q2): feature landing. We are still trying to land our significant bits into mozilla-central, which are:
      • bug 558184 and 1344942: JSPlugin and plugin binary process creation and loading
      • bug 1345330: pull in Chromium source code (PDFium + Pepper API layer) into the tree and build with Firefox
      • bug 1269760: pdf printing (to paper). The most challenged part is converting PDF to EMF printing format on Windows, because we rely on PDFium to do the conversion. This means that the sandbox for plugin binary processes should allow PDFium to create device contexts and even access files. We are discussing with the Sandbox team
    • Milestone 2: release polish. (We haven’t figured out the release target but the conversation is ongoing)
      • focus on performance and stability (meta bug 1286791), telemetry and test automation for future proofing
  • Milestone 3: script support. will NOT in the first release. Still investigating its product value

Search

Test Pilot

  • Min Vid is celebrating its largest release yet with the addition of a play and history queue.  Add media you want to watch to your upcoming queue, or replay something you missed by clicking the history tab.  Min Vid currently works on YouTube, SoundCloud, Vimeo, and direct links to audio or video.
  • Pulse has added occasional (less than once a day) prompting for feedback to help avoid biased data.  If you want to help Firefox improve performance on your favorite sites, this is your chance.  The data from this experiment goes directly to the Firefox Product team to help prioritize improvements.
  • Snooze Tabs has gone world wide now supporting 23 locales.  In addition to using Snooze Tabs in your favorite language, you’ll also find an Undo button when deleting a snoozed tab.

Here are the raw meeting notes that were used to derive this list.

Want to help us build Firefox? Get started here!

Here’s a tool to find some mentored, good first bugs to hack on.

Guest post: India uses Firefox Nightly: Kick off on May 1, 2017

Biraj Karmakar This is a guest post by Biraj Karmakar, who has been active promoting Mozilla and Mozilla software in India for over 7 years. Biraj is taking the initiative of organizing a series of workshops throughout the country to convince technical people to (mozillians or not) that may be interested in getting involved in Mozilla to use Firefox Nightly.

 

 

In my last blog, I have announced that Mozilla India is going to organize a special campaign on Firefox Nightly Usage in India. RSVP here.

Everything is set. Gearing up for the campaign.

#INUsesFxNightly_fb

BTW Recently we have organized one community call on this campaign. You can watch it to know more about how to organize events and technical things.

  • How to get involved:
    • Online Activities
      • Telling and inviting friends!
      • Create the event in social media!
      • Writing about it on Facebook & Twitter.
      • Posting updates on social media when the event is running.
      • Running an online event like webinar for this campaign. Please, check the event flow.
      • Blog posting regarding Firefox Nightly technical things, features and events.
    • Offline Activities
      • Introduction to Mozilla
      • Introduction to Firefox Nightly Release cycle details
      • Why we need Firefox Nightly users?
      • Showing various stats regarding firefox
      • Installing Nightly on participant’s PC
      • WebCompat on Firefox Nightly
      • How they can contribute in Nightly (QA and Promotion)
      • Swag Distribution
  • Duration of Campaign: 2 months
  • Total Number of offline events: 15 only. 
  • Hashtag: #INUsesFxNightly
  • Duration of each event: 3-5 hours

Swag is ready! 

 

IMG_20170425_174228.jpg

Swag for offline events

For requesting swag, please read here.

Also, we have the budget for these events. You can request it. Know more here .

Other than that if you want to know more about activity format, event flow, resource and more thing, please read the wiki.

If you have a special query, please send a mail to Biraj Karmakar [brnet00 AT gmail DOT com]. Don’t forget to join our telegram group for a realtime chat. 

Release Notes for Nightly

release notes for NightlyEvery day, multiple changesets are merged or backed out on mozilla-central and every day we compile a new version of Firefox Nightly based on these changes so as to provide builds that our core community can use, test and report feedback on.

This is why we historically don’t issue release notes for Nightly, it is hard to maintain release notes for software to gets a new release every day. However, knowing what happens, what’s new, what should be tested, has always been a recurring request from our community over the years.

So as to help with this legitimate request, we set up a twitter account that regularly informs about significant new features, and we also have the great “These weeks in Firefox” posts by Mike Conley every two weeks. These new communication channels certainly did improve things for our community over the last year.

We are now going a step further and we just started maintaining real release notes for Nightly at this address: Release Notes for Firefox Nightly

But what does it mean to have release notes for a product released every day?

It means that in the context of Project Dawn, we have started monitoring all the commits landing on mozilla-central so as to make sure changes that would merit a mention in Firefox final release notes are properly documented. This is something that we used to do with the Aurora channel, we are just doing it for Nightly instead and we do that several times a week.

Having release notes for Nightly of course means that those are updated continuously and that we only document features that have not been merged yet to Beta. We also do not intend to document unstable features or features currently hidden behind a preference flag in about:config.

The focus today is Firefox Desktop, but we will  also  produce release notes for Firefox Nightly for Android at a later stage, once we have polished the process for Desktop.

These Weeks in Firefox: Issue 14

Highlights

Friends of the Firefox team

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

Project Updates

Add-ons

Activity Stream

  • 1.8.0 released to Test Pilot with more customization: editing top sites, showing 2 rows
  • Initial Pocket integration discussion targeting 57 as in-addition or replacing highlights
  • Greening of exported system add-on on pine branch to reduce starring efforts
    • Thanks aki for tweaking build configs
  • Progress with mozilla-central patches adding react / redux / reselect with related licenses, data storage / reducer framework, Places query optimizations

Electrolysis (e10s)

  • Still on target to ship e10s-multi (4 content processes) in 55
    • A bunch of work is also being uplifted to 54 to support this. If it turns out that we pass our release criteria on 54 on beta, we may consider turning on e10s-multi to some non-zero segment of our release population in 54. More details here.
  • a11y support currently targeting Firefox 55

Firefox Core Engineering

  • Doug Thayer is also working on porting the Gecko Profiler to a WebExtension! 🎉🎉🎉
  • Client-side stackwalking:
    • The client-side machinery for sending stacks in crash pings (M+C) — and using pingSender to send it right away — has landed in 55. All but two of those bugs have been uplifted to Aurora 54.
    • We’re working on the server-side processing for crash stacks to identify top crashers during 53 release.
  • Updater:
    • The Update Agent is going to begin as just a continuation of the download of the update, targeted for 55.

Form Autofill

Mobile

  • The Fennec team reports better push support for account sign-in verification
  • The Fennec team has also fixed a regression preventing Nightly and Aurora users from syncing history, tabs, etc

Photon

Privacy/Security

Search

  • Not much changed since last meeting: hi-res favicons and one-offs are almost ready to land and search suggestions are soon going to become opt-out.
  • Miscellaneous fixes still happening.

Storage Management

  • Engaging with SV for testing, front-end devs moved to Photon now.

Test Pilot

  • Snooze Tabs did a release last week!
  • Activity Stream, Tab Center and Pulse did releases this week
  • Min Vid playback queues coming next week
  • Test Pilot release going out today which uses mozAddonManager much more, fixing many weird corner case bugs
    • The non-mozAddonManager code path still works for older Firefox, but will be removed soonish
  • Finalized our Q2 OKRs
  • As requested, Brown Bag about Screenshots engineering and product roadmap coming soon

Here are the raw meeting notes that were used to derive this list.

Want to help us build Firefox? Get started here!

Here’s a tool to find some mentored, good first bugs to hack on.

Guest post: India uses Firefox Nightly – A Campaign especially for India

Biraj Karmakar This is a guest post by Biraj Karmakar, who has been active promoting Mozilla and Mozilla software in India for over 7 years. Biraj is taking the initiative of organizing a series of workshops throughout the country to convince technical people to (mozillians or not) that may be interested in getting involved in Mozilla to use Firefox Nightly.

 

 

Fellow mozillians, I am super excited to inform you that very soon we are going to release a new campaign in India  called “India uses Firefox Nightly“. Behind this campaign, our mission is to increases Firefox nightly usages in India.

Why India?

As we all know we have a great Mozilla community around India. We have a large number of dedicated students, developers and evangelists who are really passionate about Mozilla.

We have seen that very few people in India actually know about Firefox Nightly. So we have taken an initiative to run a pilot campaign for Firefox Nightly throughout India.

Firefox Nightly, as a pre-release version of Firefox targeting power-users and core Mozilla contributors, is a glimpse of what the future of Firefox will be for hundreds of millions of people. Having a healthy and strong technical community using and testing Nightly is a great way to easily get involved in Mozilla by providing a constant feedback loop to developers. Here you can test lots of pre-release features.

So it needs a little bit of general promotion, which will help bring a good number of tech-savvy, power-users who may become new active community members.

Few Key points

Time Frame: 2 months Max              Hashtag: #INUsesFxNightly

Event Duration: 3 – 5 Hours              Total events: 15

Who will join us: We invite students, community members, developers, open source evangelists to run this campaign.

Parts of Campaign

Online activities:

Mozillians spread the message of this campaign around India as well as through social media (Facebook, Twitter, Instagram), blogs, promotional snippets, email, mailing list, website news items etc.

Offline activities:

Here, any community member or open source enthusiast can host one event in their area or join any nearby event to help organizers. The event can be held at a startup company, Schools, Universities, Community centres, Home, Cafés.

Goals for this initiative

Impact:

  • 1000 Nightly Installed
  • 20 New Active Contributors

Strength:

  • 30 Mozillians run events (2 mozillians per event)
  • 500 Attendees

 

BTW have you tried Firefox Nightly yet, download it now?

 

More details will come soon. Stay tuned!

 

We need many core campaign volunteers who will help us to run this initiative smoothly. If you are interested in joining the campaign team, please let me know.

Have design skills? We need a logo for this campaign, please come and help us here.

These Weeks in Firefox: Issue 13

Highlights

 

Friends of the Firefox team

Project Updates

Add-ons

Activity Stream

  • timspurway reports that the team has re-evaluated their schedule for landing in Nightly – new estimate puts Activity Stream in Fx57

Electrolysis (e10s)

Firefox Core Engineering

Form Autofill

Mobile

  • The team ran user testing of Prox v2, which emphasizes local sights, events, and multiple sources – full conclusions upcoming!
  • Firefox for Android 53 coming soon with RTL support for Urdu, Persian, Hebrew and Arabic!
  • Activity Stream is going live for 50% of the Firefox for Android Nightly audience this week. All Nightly users will see a setting to opt-in / opt-out (Settings -> Advanced -> Experimental Features).

Platform UI and other Platform Audibles

Privacy/Security

Project Mortar (PDFium)

  • evelyn reports that the front-end work for Mortar is almost done! A few bugs remaining, but it’s getting pretty polish-y.
  • The team is currently dealing with process separation work, and waiting on this bug to land which will allow us to create a special type of JS-implemented plugin
  • The team is also tackling the printing engine as well, as we want to make sure we print PDFs as accurately as possible
  • Blocked on spinning up QA help for manual testing, but we will first add more automation test and compare the result of pdf.js to understand how much improvement we gain. (Thanks to bsmedberg’s suggestion!)
  • Talking to release team on release to-dos, and how best to keep the system add-on up to date

Quality of Experience

  • New preferences organization should land sometime this week
  • Engineers now mostly segueing into Photon stuff (which should will probably get its own section in future meetings?).

Search

  • Phase 1 of the hi-res favicons work should land before the next meeting.
  • The last big issue with one-off search buttons in the awesomebar is very close to landing.
  • Various miscellaneous fixes for the search and location bars.

Sync / Firefox Accounts

  • Fixes:
    • Sync will discard folder child order if the local timestamp is newer than the remote. This shows up most frequently on first syncs.
    • First sync for passwords was broken in Aurora and Nightly.
  • Push-driven sign-in confirmation is coming! Design doc in progress; should have more updates in the next meeting.
  • If you’re curious…

Storage Management

  • [fischer] The project target due date is 4/17.
  • [fischer] The implementations are almost done. The remained 3 bugs are expected to be resolved before the target 4/17.
  • [fischer] Bug 1312349: Hide the section of Offline Web Content and User Data in about:preferences
    • Because the Storage management handles appcache as well, after the Storage management completes, the Offline(Appcache) group will be hidden.
    • The pref to control hide the Offline group is browser.preferences.offlinegroup.enabled

Test Pilot

  • We are trying to track down some performance issues with the Test Pilot addon (“Test Pilot is making FF run slowly”). Any advice is welcome, ping fzzzy in #testpilot
  • First ever Test Pilot QA community event happened in Bangladesh last week!
    • Volunteers installed Test Pilot & did some manual testing of the Test Pilot addon and experiment addons
    • Event page
    • Tweets and photos of the event!

Here are the raw meeting notes that were used to derive this list.

Want to help us build Firefox? Get started here!

Here’s a tool to find some mentored, good first bugs to hack on.