Firefox/Goals/2013Q2: Difference between revisions

From MozillaWiki
< Firefox‎ | Goals
Jump to navigation Jump to search
Line 22: Line 22:


=== Australis ===
=== Australis ===
* Merged to mozilla-central for Firefox 24 (with intent to ride that train)
Merged to mozilla-central for Firefox 24 (with intent to ride that train)


=== Profile Reset ===
=== Profile Reset ===

Revision as of 20:16, 19 March 2013

Firefox Desktop

Search Hijacking

  • remove use of keyword.URL
  • add prefs UI for selecting default engine
  • prompt-on-engine-change dialog/notification

Performance

  • Add-on manager startup
    • eliminate unnecessary main-thread I/O
    • investigate simplified storage back-end (SQLite->JSON)
  • Thumbnail service
    • no main thread impact from thumbnailing
  • New download back-end
    • landed and used by at least one consumer (no main thread I/O)
  • New tab page
    • reduce impact on tab animation
  • Password Manager
    • eliminate main-thread I/O
  • localStorage
    • Eliminate all uses of localStorage in application code

Australis

Merged to mozilla-central for Firefox 24 (with intent to ride that train)

Profile Reset

Improve functionality and expose it more. (Gathering in bug 851364)

Permissions UI

Expose a lightweight UI (not about:permissions) for managing permissions you have granted to a site. (old mockup: http://cl.ly/image/3u3M2w3O3w1X)

Stability

  • Develop and deploy a system to allow 3rd parties to submit encrypted/obfuscated symbols to Mozilla, and get popular addons and driver vendors to send us symbols.
  • Develop reports to allow prioritization of potentially exploitable crashes.

Plugins

  • Make plugin and plugin instance instantiation asynchronous
  • Profile Flash IPC messages and rearrange event delivery to delay painting and networking events when synchronous events are pending.

Firefox Developer Tools

Add-on SDK

  • UX work
  • Places API
  • Add-ons run with access to a DOM window

Script and Performance Tools

  • Scratchpad remoted and integrated with the debugger.
  • FPS monitor, frame boundaries in the profiler.
  • tagStack, XHR breakpoints.

Content Tools

  • Finish remoting the Inspector
  • Plan and begin executing authoring strategy
    • (Which means: iterate on UX for in-browser authoring, better integrate Style Editing, prototype external editor integration)
  • Provide metrics on Developer Tool usage through FHR probes

Firefox for Android

Profile Related Work

Various things that are based on profiles, while trying to avoid Sync/PiCL dependencies:

  • Profile Reset
  • Guest Mode (Switching to a temporary profile)
  • Kid Mode (A profile with strong parental controls)
  • Senior Mode (A profile with less options and designed pure ease-of-use)

Reader Enhancements

Reader is one of Firefox Android's most differentiating features. We have plans to add more to the core in Q2:

  • Night Mode (ambient light based background toggle)
  • Sans Serif/Serif font toggle
  • Open into Reading List from home screen
  • Add to Reading List from external apps (twitter)
  • Text-to-Voice investigations (investigate the technology)
  • Twitter card support for richer Reading List (investigate the design)

WebRT

  • Packaged app support
  • APK wrapper support (goal is to uplift to Marketplace)
  • Turn off some browser-centric features while in App mode

Game/TV Form Factor

  • Gamepad controller support
  • TV layout support

User Efficency/Cleanup

  • Hostname completion
  • Keyboard shortcuts
  • SNAV
  • Quickly share using last "Share App" from menu
  • Improve Settings UI
  • Improve Session Restore

Firefox for Metro

  • Feature-complete awesome/start screen
  • Uplift from mozilla-central to mozilla-aurora

Community Development

  • Make Mozillians a useful repository of information about core and new contributors, including all employees.
  • Establish a roadmap for contributors so that they can view their progress on Mozillians and can see what the next "level up" is.
  • Implement engineering contributor rewards program, including both recognition/badges and "stuff".
  • Request from creative team: help provide art (art competition?) to support engineering badge recognition efforts .
  • Automate, either through bugzilla-anthropology or Bugzilla proper, the awarding of many of the badges in the Engineering badging effort.
  • Design and implement a set of metrics to measure Mozilla's support for volunteer engineering, and volunteer participation/effectiveness.
  • Request for every team in engineering: describe what a "minimum viable contributor" is for participating on that team, including time commitments and resources required.
  • Request from bugzilla team: automate regular data dumps of bugzilla data for researchers by 1-May