MozillaWiki - User contributions [en]

Features/Desktop/TelemetryOptIn

2011-08-30T22:08:59Z

Faaborg:

{{FeatureStatus
|Feature name=Opt in Dialog for Telemetry
|Feature stage=Feature Inbox
|Feature health=OK
}}
{{FeatureTeam
|Feature ux lead=Faaborg
|Feature additional members=Chris Jung, Taras Glek
}}
{{FeaturePageBody
|Feature overview=The purpose of this project is to create a modal (but beautiful) dialog box that will prompt users on Nightly / Aurora / Beta to ask if they would like to opt in to telemetry and send anonymous performance data about Firefox. Modal dialogs are interuptive and anoying, but this data is important, and we aren't considering one for the mainstream product, just testing builds.

For context, the current notification bar approach is only generating around a 2% opt-in, which isn't generating enough data.
|Feature users and use cases=user: trying out a test build of Firefox (nightly, aurora, beta)
use case: see a dialog asking you to opt in to sending performance data, and deciding that it sounds like a fantastic idea!
|Feature requirements=If we are going to intrupt the user, we need to at least show them some good artwork, this dialog box requires some Sean Martell artwork.
|Feature ux design=https://bug683340.bugzilla.mozilla.org/attachment.cgi?id=557012
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus}}

Features/Desktop/TelemetryOptIn

2011-08-26T00:03:36Z

Faaborg: Created page with "{{FeatureStatus |Feature name=Opt in Dialog for Telemetry |Feature stage=Feature Inbox |Feature health=OK }} {{FeatureTeam |Feature ux lead=Faaborg |Feature additional members=Ch..."

{{FeatureStatus
|Feature name=Opt in Dialog for Telemetry
|Feature stage=Feature Inbox
|Feature health=OK
}}
{{FeatureTeam
|Feature ux lead=Faaborg
|Feature additional members=Chris Jung, Taras Glek
}}
{{FeaturePageBody
|Feature overview=The purpose of this project is to create a modal (but beautiful) dialog box that will prompt users on Nightly / Aurora / Beta to ask if they would like to opt in to telemetry and send anonymous performance data about Firefox. Modal dialogs are interuptive and anoying, but this data is important, and we aren't considering one for the mainstream product, just testing builds.

For context, the current notification bar approach is only generating around a 2% opt-in, which isn't generating enough data.
|Feature users and use cases=user: trying out a test build of Firefox (nightly, aurora, beta)
use case: see a dialog asking you to opt in to sending performance data, and deciding that it sounds like a fantastic idea!
|Feature requirements=If we are going to intrupt the user, we need to at least show them some good artwork, this dialog box requires some Sean Martell artwork.
|Feature ux design=[mockup coming soon]
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus}}

Notifications

2011-08-19T19:06:37Z

Faaborg:

{{FeatureStatus
|Feature name=Notifications
|Feature stage=Definition
|Feature health=OK
|Feature status note=Just getting started
}}
{{FeatureTeam
|Feature ux lead=Faaborg
}}
{{FeaturePageBody
|Feature overview=The purpose of this project is to expose an API for various types of notifications, both real time and ambient. This API should manifest itself on desktop and mobile.
|Feature users and use cases=Lots of use cases, but here are some examples of incoming messages from:

Ping/Pulse/Bounce
*real time chat
*asynchronous (but important) direct messages through social networks

Ambient
*asynchronous email
*asynchronous (and not important) messages through social networks
*various random niche sites that need to notify you of events
|Feature non-goals=*Interrupt the user's cognitive flow with notifications that are not relevant or important (the growl effect)

*[b]Badging is a non-goal[/b]. The increasing size of the badge creates a game mechanic where users must get the number down to zero, which isn't a good pattern, and ultimately makes them feel like they are failing.

*Panel notifications need to be user opt in, because they are so destructive to the user's attention and cognitive flow.
|Feature functional spec=Two different API calls:
#Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it)
#Ping (for direct messages, real time chat, etc. The message captures your attention and continues to bounce, pulse, glow until you interact with it)
|Feature ux design=http://people.mozilla.com/~faaborg/files/projects/notifications/desktop%20notifications%20i1.png
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus}}

Notifications

2011-08-19T19:05:52Z

Faaborg:

{{FeatureStatus
|Feature name=Notifications
|Feature stage=Definition
|Feature health=OK
|Feature status note=Just getting started
}}
{{FeatureTeam
|Feature ux lead=Faaborg
}}
{{FeaturePageBody
|Feature overview=The purpose of this project is to expose an API for various types of notifications, both real time and ambient. This API should manifest itself on desktop and mobile.
|Feature users and use cases=Lots of use cases, but here are some examples of incoming messages from:

Pulse/bounce/glow
*real time chat
*asynchronous (but important) direct messages through social networks

Ambient
*asynchronous email
*asynchronous (and not important) messages through social networks
*various random niche sites that need to notify you of events
|Feature non-goals=*Interrupt the user's cognitive flow with notifications that are not relevant or important (the growl effect)

*[b]Badging is a non-goal[/b]. The increasing size of the badge creates a game mechanic where users must get the number down to zero, which isn't a good pattern, and ultimately makes them feel like they are failing.

*Panel notifications need to be user opt in, because they are so destructive to the user's attention and cognitive flow.
|Feature functional spec=Two different API calls:
1) Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it)
2) Ping (for direct messages, real time chat, etc. The message captures your attention and continues to bounce, pulse, glow until you interact with it)
|Feature ux design=http://people.mozilla.com/~faaborg/files/projects/notifications/desktop%20notifications%20i1.png
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus}}

Notifications

2011-08-19T19:04:07Z

Faaborg:

{{FeatureStatus
|Feature name=Notifications
|Feature stage=Definition
|Feature health=OK
|Feature status note=Just getting started
}}
{{FeatureTeam
|Feature ux lead=Faaborg
}}
{{FeaturePageBody
|Feature overview=The purpose of this project is to expose an API for various types of notifications, both real time and ambient. This API should manifest itself on desktop and mobile.
|Feature users and use cases=Lots of use cases, but here are some examples of incoming messages from:

**real time chat
**asynchronous (but important) direct messages through social networks
-asynchronous email
-asynchronous (and not important) messages through social networks
-various random niche sites that need to notify you of events
|Feature non-goals=Interrupt the user's cognitive flow with notifications that are not relevant or important (the growl effect)

Badging is a non-goal. The increasing size of the badge creates a game mechanic where users must get the number down to zero, which isn't a good pattern, and ultimately makes them feel like they are failing.
|Feature functional spec=Two different API calls:
1) Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it)
2) Ping (for direct messages, real time chat, etc. The message captures your attention and continues to bounce, pulse, glow until you interact with it)
|Feature ux design=http://people.mozilla.com/~faaborg/files/projects/notifications/desktop%20notifications%20i1.png
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus}}

Notifications

2011-08-19T19:01:58Z

Faaborg: Created page with "{{FeatureStatus |Feature name=Notifications |Feature stage=Definition |Feature health=OK |Feature status note=Just getting started }} {{FeatureTeam |Feature ux lead=Faaborg }} {{..."

{{FeatureStatus
|Feature name=Notifications
|Feature stage=Definition
|Feature health=OK
|Feature status note=Just getting started
}}
{{FeatureTeam
|Feature ux lead=Faaborg
}}
{{FeaturePageBody
|Feature overview=The purpose of this project is to expose an API for various types of notifications, both real time and ambient. This API should manifest itself on desktop and mobile.
|Feature users and use cases=Lots of use cases, but here are some examples of incoming messages from:

-real time chat
-asynchronous (but important) direct messages through social networks
-asynchronous email
-asynchronous (and not important) messages through social networks
-various random niche sites that need to notify you of events

|Feature non-goals=Interrupt the user's cognitive flow with notifications that are not relevant or important (the growl effect)

Badging is a non-goal. The increasing size of the badge creates a game mechanic where users must get the number down to zero, which isn't a good pattern, and ultimately makes them feel like they are failing.
|Feature functional spec=Two different API calls:
1) Ambient (for email messages, etc. this messages does not capture your attention, you have to direct your attention to it)
2) Ping (for direct messages, real time chat, etc. The message captures your attention and continues to bounce, pulse, glow until you interact with it)
|Feature ux design=http://people.mozilla.com/~faaborg/files/projects/notifications/desktop%20notifications%20i1.png
}}
{{FeatureInfo
|Feature priority=Unprioritized
}}
{{FeatureTeamStatus}}

Firefox/Features/streamline-search

2011-08-01T22:08:49Z

Faaborg:

{{FeatureStatus
|Feature name=Streamline the visual appearance of the search field
|Feature stage=Development
|Feature status=In progress
|Feature health=OK
|Feature status note=Final work occurring here: https://bugzilla.mozilla.org/show_bug.cgi?id=675753
}}
{{FeatureTeam
|Feature product manager=Asa Dotzler
|Feature feature manager=Alex Faaborg
|Feature lead engineer=Margaret Leibovic
|Feature qa lead=Simona Badau
|Feature ux lead=Alex Faaborg
|Feature additional members=Kev Needham (bizdev)
}}
{{FeaturePageBody
|Feature open issues and risks=* If we default the search button to green (same as the go button in the location bar) if the search engine has not provided us with a color, will that cause any issues with our relationship with them?
|Feature overview=The favicons in the search field are creating a significant amount of visual complexity in our product. They are using a wide range of colors, and they reduce the relative discoverability of nearby controls like reload and stop. Additionally the search field is causing a large number of mode errors, as users search the previous engine they selected for a new search term. This project aims to solve both of these problems.

This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.)

==== Goals ====
* Pretty
* Reduced mode errors
* Increased focus on various engines as verbs (not that we care that much, but a side effect of the design)
* Increased brand awareness (not that we care that much, but a side effect of the design)
|Feature users and use cases=* Search with a greater awareness of which search engine is activated
* Return to the search field after a long period of time and realize that your default search engine is not the currently active one
* Enjoy the visual simplicity and streamlined appearance of the field when it is not currently focused
|Feature requirements=* Getting major search engines to optionally specify a color that they would like to use when they are active {{bug|634140}}
* Implementing the changes, with engines without specified colors falling back to the same color as the active go button {{bug|592909}}
|Feature non-goals=* Merge the search bar with the location bar (at this point)
|Feature ux design=[https://bug592909.bugzilla.mozilla.org/attachment.cgi?id=500550 Mockup]
|Feature implementation notes=* Reaching out to search engines to get colors {{bug|634140}}
* Implementation {{bug|592909}}
}}
{{FeatureInfo
|Feature priority=P3
|Feature roadmap=User Experience
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}

Firefox/Features/windows-scrolling

2011-08-01T20:09:41Z

Faaborg:

{{FeatureStatus
|Feature name=Support High Resolution Scrolling on Windows
|Feature stage=Landed
|Feature status=Complete
|Feature version=Firefox 6
|Feature health=OK
|Feature status note=Main implementation bugs point to Firefox 6 as Milestone. Please correct me if I am wrong.
}}
{{FeatureTeam
|Feature product manager=Asa Dotzler
|Feature feature manager=Alex Faaborg
|Feature lead engineer=Masayuki Nakano
|Feature qa lead=George Carstoiu
|Feature ux lead=Alex Faaborg
}}
{{FeaturePageBody
|Feature overview=We need to enable users on windows to scroll with pixel level precision (when using a non-discrete wheel), similar to the fine grained level of control that users currently have on OS X. Windows Vista introduced standard mouse events that contain a higher level of scrolling precision for mouse wheel movement in 2006. Non discrete mouse wheels have been in the marketplace for awhile now, and mouse drivers are sending these events to applications.

We're doing this because:
*Moving to pixel scrolling where possible will make a very common browser activity feel faster, more responsive, and improve the general feel of the application.

This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.)

==== Goals ====
The goal is to scroll on Windows as well as Firefox on OS X. The fact that we only do line scrolling on windows impacts our perceived performance and responsiveness, and the general feel of the application. Scrolling is something that users do literally constantly with a Web browser (much more than any other interaction or UI control), so changes to how the application scrolls should respectively be prioritized extremely high. The fact that we don't support an important scrolling feature of Windows that was introduced 5 years ago may be indicative of just how few people at Mozilla actually use Firefox on Windows.
|Feature users and use cases="Scrolls like butter"
|Feature non-goals=Note that this bug is different than {{bug|590022}}. Our smooth scrolling preference simply draws 10 frames when we receive an event that the user has moved their mouse wheel a single discrete step. This project is about fine grained precision, and non-discrete mouse wheels.
|Feature ux design=Just pixel level scrolling precision, similar to scrolling in Firefox on OS X. Currently on Windows we only do line scrolling.
|Feature qa review=* drivers need to send small delta value than 1 line (or, send 1.x lines)
* non-Logitech's user will not feel scroll smoother in default settings
|Feature implementation notes=* [https://bugzilla.mozilla.org/show_bug.cgi?id=605648 Bug 605648 - Support high resolution scrolling on Windows]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=658111 Bug 658111 - Enable Windows high resolution scrolling in default settings]
|Feature landing criteria=After we land the patch we need enough time for testing, since there is a wide range of mouse hardware out on the market (especially on Windows).
}}
{{FeatureInfo
|Feature priority=P1
|Feature roadmap=User Experience
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus
|Feature products notes=Setting to complete since this has now landed.
|Feature security status=pass
}}

User:Faaborg

2011-07-14T21:54:15Z

Faaborg:

__NOTOC__
{| cellpadding="10"
|-valign="top"
|http://people.mozilla.com/~faaborg/files/profile/faaborg-128.png
|
==Alex Faaborg's Contact Info==
http://people.mozilla.com/~faaborg/files/20061027/faaborgAtMozilla.jpg

==Links==
* [http://blog.mozilla.com/faaborg/ Blog]

Firefox/Team/whois

2011-07-14T21:53:15Z

Faaborg:

= Who is Team Firefox? =
The Mozilla Corporation employs a group of people to work on Firefox. The Mozilla Corporation tasks this group with the responsibility for the successful delivery of the Firefox product to our millions of users. It's important to note, though, that this isn't an exhaustive list of people who work on Firefox or are imperative to its success!

{| class="fullwidth-table sortable"
|'''Fotograff'''
|'''Name'''
|'''irc nick'''
|'''Group'''
|-
|http://a1.twimg.com/profile_images/555933154/me_bigger.jpg
|Dietrich Ayala
|dietrich
|Toolkit & Services
|-
|http://it.gravatar.com/userimage/11967298/9385580927bd91d98d06369fa4e2808d.png
|Marco Bonardo
|mak
|Toolkit & Services
|-
|https://wiki.mozilla.org/images/3/37/Mozthumbnailself.png
|Jennifer Boriss
|Boriss
|User Experience
|-
|http://en.gravatar.com/userimage/248986/72054ae630b90d6f196304fbccfc5d6b.jpg
|Dave Camp
|dcamp
|Devtools
|-
|http://farm4.static.flickr.com/3277/3082768677_347ee67b04_t.jpg
|Rob Campbell
|robcee
|Devtools
|-
|http://s3.amazonaws.com/twitter_production/profile_images/181775998/ddahl_bigger.JPG
|David Dahl
|ddahl
|Toolkit & Services
|-
|
|Neil Deakin
|Enn
|Toolkit & Services
|-
|https://people.mozilla.com/~dolske/headshot-73.jpg
|Justin Dolske
|dolske
|Application
|-
|http://people.mozilla.com/~faaborg/files/profile/faaborg-128.png
|Alex Faaborg
|faaborg
|User Experience
|-
|https://si0.twimg.com/profile_images/414664441/gtalk_bigger.jpg
|Felipe Gomes
|felipe
|Application
|-
|http://design-noir.de/Bilder/Portrait/7.png
|Dão Gottwald
|dao
|Application
|-
|http://www.stephenhorlander.com/images/random/profile-picture-wiki.jpg
|Stephen Horlander
|shorlander
|User Experience
|-
|http://a2.twimg.com/profile_images/1207134514/Screen_shot_2011-01-04_at_9.50.16_PM_reasonably_small.png
|Margaret Leibovic
|margaret
|Application
|-
|http://en.gravatar.com/userimage/3196797/ab07fe36c994648dab7f45cf9ef7d09c.jpeg
|Alex Limi
|limi
|User Experience
|-
|http://s3.amazonaws.com/twitter_production/profile_images/353573692/me_bigger.jpg
|Blair McBride
|Unfocused
|Application
|-
|https://si0.twimg.com/profile_images/1113196848/DSC_1222-square-lighter_reasonably_small.jpg
|Johnathan Nightingale
|johnath
|*
|-
|http://a3.twimg.com/profile_images/399482199/photo_bigger.jpg
|Paul O'Shannessy
|zpao
|Toolkit & Services
|-
|http://www.gravatar.com/avatar/34b251cf082c202fb3160b1afb810001.png
|Jan Odvarko
|Honza
|Firebug
|-
|https://secure.gravatar.com/avatar/bce42959556d5e8ddac1e73649883c55.jpg
|Mike Ratcliffe
|mikeratcliffe (creative eh?))
|Devtools
|-
|
|Asaf Romano
|Mano
|Tookit & Services
|-
|
|Gavin Sharp
|gavin
|Application
|-
|
|Kyle Simpson
|getify
|Devtools
|-
|http://exchangecode.com/robert/work/me_moz_whois.png
|Robert Strong
|rs
|Application
|-
|http://en.gravatar.com/userimage/2989565/3b9443433e604986a3cd9e2967321827.jpg
|Dave Townsend
|Mossop
|Application
|-
|http://a3.twimg.com/profile_images/328802425/vlad-sm_bigger.jpg
|Vlad Vukicevic
|vlad
|Product Management
|-
|http://en.gravatar.com/userimage/16621043/f841c328e630faee05a68548b3f851e4.jpeg
|Joe Walker
|joe_walker
|DevTools
|-
|http://msujaws.files.wordpress.com/2011/06/jared.jpg
|Jared Wein
|jwein
|Application
|-
|
|Drew Willcoxon
|adw
|Toolkit & Services
|-
|
|Frank Yan
|fryn
|Application
|-
|http://en.gravatar.com/userimage/3670555/f0155479954cbd6c6b040b10f48430d9.jpg
|Panos Astithas
|past
|Devtools
|-
|https://si0.twimg.com/profile_images/1222293146/profile_reasonably_small.jpg
|Tim Taubert
|ttaubert
|Application
|-
|
|Nick Fitzgerald
|fitzgen
|DevTools
|}

DevTools/DesignMockups

2011-07-14T05:33:48Z

Faaborg:

= DevTools Future Planning =

This is a document based on mockups created by Paul Rouget. Notes taken to synthesize bugs from features and hopefully, features from bugs.

== Possible Visual Design ==
Here is a possible aesthetic for the interface by Faaborg: [http://mzl.la/o5ytgB]

== Developer Tools Toolbar ==

[[File:1.devtoolbar.png|400px]][[File:2.devtoolbar.details.png|400px]]

=== buglist ===
* create toolbar for developer tools
* migrate command line to developer tools toolbar
** Some interesting challenges with this, will possibly need additional bugs around popping up doorhangers for output, including output in the commandline itself, what happens with positioning the console in other locations, etc.
* create API for registering tools with main developer toolbar
* create API for adding badges to toolbar buttons
* create "Web Developer" toolbar button
** popup menu that derives its contents from the Web Developer menu

== Highlighter ==

[[File:5.inspector.png|400px]]

[[File:5.1.inspector.folded.png|400px]]

[[File:5.4.inspector.annotations.png|400px]]

=== buglist ===

* Dockable* HTML panel
* Inspector Toolbar
** Expand/collapse HTML+Style panels.
** Create auto-truncating nodepath (XPath) selection tool
** querySelector search box
* Dockable* Style inspectors
* create highlighter infobar for selected node
* Layout Information
** Layout info in the inspector toolbar
** Layout box in the highlighter (margins, borders and paddings)
* Highlighter background controls
** Grids
** Light
** Dark
** Checkerboard
* Annotations
** Inspector toolbar button
** Doorhanger style editor for entering code to evaluate
** Highlighter display of annotations on selected node

== Web Console ==

[[File:3.console.png|400px]]

=== buglist ===
* Dockable "HTTP Requests" and "Object Inspector"

Firefox/Features/InstallerUIRewrite

2011-07-01T05:19:55Z

Faaborg: /* Designs */

Firefox/Features/50ms ASSERT

2011-06-01T03:16:04Z

Faaborg: /* Designs */

{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
<section begin="status" />
|-
| [[Firefox/Features/50ms_ASSERT|Understand when user interface feels laggy]]
|{{StatusHealthy|status=Core instrumentation landed}}
SDR: N || SIR: N
| 2011-06-30
| [[User:Dietrich|dietrich]]
<section end="status" />
|}

== Summary ==

Any time the user interface takes more than 50ms to respond to an action, the application will appear sluggish to the user. To determine how often this happens, and what parts of our code are frequent offenders, we should add the ability to detect when the main-thread event loop is delayed by more than 50ms and log it as an ASSERT.

However, just an ASSERT does not tell developers *what caused* the delay. In order to be useful, we must provide the ability for developers to easily get information about what code is slow.

There are generally two scenarios in which the browser UI is non-responsive.

# When a direct action by the user causes the app to be non-responsive. For example, a menu option that executes an action synchronously, and takes >50ms to return.
# When a background action blocks the event loop for >50ms, causing the whole app to be non-responsive.

The goal of this project is to get developer visibility into both scenarios with easy-to-use tools.

== Release Requirements ==

*Does not affect performance in production or beta builds
*Can be logged to screen or file
*Logging has been added to all primary user interface events

== Next Steps ==

*Complete project definition (ETA: 2011/04/01, Beltzner, Complete)
*Work with UX to identify 15 primary UI events (ETA: 2011/04/01, [http://j.mp/ihM1wc google doc], Dietrich, Complete)
*Implement core instrumentation of event loop ({{bug|601268}}, Ted, Complete)
*Investigate options for correlation of event loop delays with high and low level code (ETA: xxx, Ted, in progress)
*Investigate methods of identifying slow front-end UI (ETA: 2011/05/06, Dietrich, in progress)
*Identify and publish top 10 code points causing event loop delays (Ted)
*Identify and publish top 10 slowest-responding primary UI pieces (Dietrich)
*Publish the tools and methods developed in this project (Ted, Dietrich)

== Related Bugs & Dependencies ==

'''Tracking Bugs'''

*{{bug|651580}} - main project tracking bug

'''Related Bugs'''

*{{bug|601268}} - adds "canary in a coal mine" instrumentation to nsThread.cpp
*{{bug|606574}} - adds ability to report information in Talos
*{{bug|653701}} - adds ability to dump JS function calls executed when non-responsiveness is detected
*{{bug|653703}} - adds ability to hook into a profiler (eg Shark) when non-responsiveness is detected

'''Related Projects'''
* [https://github.com/autonome/about-response About:Response] - add-on that tracks response time of browser features

'''Related Documents'''
* [https://wiki.mozilla.org/Fennec/Features/Gestures Fennec Gestures project] - lists a bunch of features identified

*''no test plan needed''
*''no product marketing plan needed''

== Team ==

Anyone interested in this project is encouraged to jump in and get involved. The list here is to provide contact and ownership information:

*'''Development Lead:''' dietrich
*'''Infrastructure Lead:''' ted
*'''QA contact''' Andrei (mirc: andreid)

== Designs ==

No designs required

--[[User:Faaborg|Alex]] 20:16, 31 May 2011 (PDT): Here's a [http://people.mozilla.com/~faaborg/files/daf/eventVisualization.png possible UI for visualizing responsiveness]. Note that the 50ms ASSERT is for discrete actions, anything that is continuous would need to log when the responsiveness was higher than 16.6ms during the action. In the visualization these appear as lines instead of dots (scrolling, moving the window, etc.)

== Goals/Use Cases ==

*provide insight to developers into what is causing the Firefox user interface to feel slow or unresponsive to users
*identify high impact areas for UI responsiveness work

== Non-Goals ==

*provide information to end-users about what is causing Firefox to feel slow or unresponsive
*provide UI profiling
*integration of responsiveness testing into Talos

== Other Documentation ==

*[http://www.useit.com/papers/responsetime.html Jakob Neilson's UseIt article on Response Time Limits for User Interfaces]

== Security ==

Security Contact: Curtis Koenig

*No security review necessarily for this feature

__NOTOC__

[[Category:Features]] [[Category:Firefox]] [[Category:Performance]] [[Category:P1]]

Firefox/Features/InstallerUIRewrite

2011-06-01T00:58:17Z

Faaborg: /* Designs */

Import settings from Sync

2011-05-16T07:38:15Z

Faaborg:

Firefox/Features/Sync Device Management

2011-04-25T01:04:20Z

Faaborg: /* Related Bugs & Dependencies */

Firefox/Features/streamline-search

2011-04-25T00:27:38Z

Faaborg: Created page with "{| class="fullwidth-table" |- | style="font-weight: bold; background: #DDD;" | Feature | style="font-weight: bold; background: #DDD;" | Status | style="font-weight: bold; backgro..."

Firefox/Features/windows-scrolling

2011-04-24T23:47:35Z

Features/Desktop

2011-04-24T23:14:19Z

Faaborg: /* Firefox */

Prioritization has not been finalized, but the P1/P2/P3 buckets are accurate. If you have any questions, please contact [[User:Dria|Deb]].

__TOC__
== Firefox ==
{| class="fullwidth-table sortable" style="width: 950px"
|-
| style="font-weight: bold; background: #DDD; width: 100px" | Roadmap
| style="font-weight: bold; background: #DDD; width: 100px" | Team
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD; width: 50px" | Rank
| style="font-weight: bold; background: #DDD; width: 150px" | Owner
|-
| User support
| Front-end
| [[Support/Firefox Features/Clean install|Provide an intuitive path to clean install]]
| {{Pr1}}
| Cheng Wang
|-
| User support
| Front-end
| [[Support/Firefox Features/Clean up user profile|Ability to clean up user profile]]
| {{Pr1}}
| Michael Verdi
|-
| Privacy
| Front-end
| [[Privacy/Features/Site-based data management UI|Site-based data management UI]]
| {{Pr1}} (1)
| Sid Stamm
|-
| Release Mgmt
| Front-end
| [[ChannelSwitching/ChannelSwitchingFeature|Channel Switching]]
| {{Pr1}} (1)
| Sheila Mooney
|-
| Search
| Front-end
| [[Firefox/Features/keywordurl_follows_searchbar|Replace keyword.URL to follow Search Bar and/or allow independent setting of provider]]
| {{Pr1}} (1)
| Kev Needham
|-
| Sharing
| Front-end
| [[Labs/F1|Sharing]] UI in Firefox
| {{Pr1}} (1)
| Bryan Clark
|-
| Sync
| Front-end
| [[Firefox/Features/Sync_Discoverability|Improve discoverability of Sync]]
| {{Pr1}} (1)
| Ragavan Srinivasan
|-
| UX
| Front-end
| [[Firefox/Features/50ms_ASSERT|Understand when user interface feels laggy]]
| {{Pr1}} (1)
| Jay Sullivan
|-
| UX
| Front-end
| [[Firefox/Features/URL_Autocomplete |Inline URL autocomplete]]
| {{Pr1}} (1)
| Alex Limi
|-
| Web Apps
| Front-end
| App install/uninstall APIs in Firefox
| {{Pr1}} (1)
| Ragavan Srinivasan
|-
| Plugins
| Front-end
| Add link to plugincheck from AOM
| {{Pr1}} (2)
| Kev Needham
|-
| UX
| Front-end
| [[Firefox/Features/Electrolysis|Execute chrome in separate process]]
| {{Pr1}} (2)
| Jay Sullivan
|-
| UX
| Front-end
| [[Firefox/Features/Persist_Panorama_Groups|Panorama groups should always persist]]
| {{Pr1}} (2)
| Alex Limi
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Third Party Add-on Warnings|Ensure user accepts add-ons installed by third-party apps]]
| {{Pr1}} (3)
| Mossop
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Confirm on Upgrade|Confirm add-ons on upgrade]]
| {{Pr1}} (3)
| Mossop
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Improve_Add-on_Installation|Improve Add-on Installation]]
| {{Pr1}} (3)
| Boriss
|-
| Plugins
| Front-end
| Use PFS2 for pfs.datasource.url in Mozilla product(s)
| {{Pr1}} (3)
| Kev Needham
|-
| UX
| Front-end
| Don't resize when closing tabs
| {{Pr1}} (3)
| Alex Limi
|-
| Web Apps
| Front-end
| HTML5 Web App dashboard
| {{Pr1}} (3)
| Ragavan Srinivasan
|-
| Add-ons
| Front-end
| [[Firefox/Features/Easier_Add-on_Compatibility|Solution to frequent compatibility updates]]
| {{Pr1}} (4)
| Justin Scott
|-
| Identity
| Front-end
| [[Identity/Features/In-browser_sign-in_UI|In-browser sign-in UI]]
| {{Pr1}} (4)
| Dan Mills
|-
| UX
| Front-end
| Tab move/detach animations
| {{Pr1}} (4)
| Alex Limi
|-
| UX
| Front-end
| Toolbar-less app tabs
| {{Pr1}} (5)
| Alex Limi
|-
| Web Apps
| Front-end
| [[Firefox/Features/Home_Tab|Home Tab as Permanent App Tab]]
| {{Pr1}} (5)
| Jay Sullivan
|-
| UX
| Front-end
| Inactive Panorama groups should load on-demand
| {{Pr1}} (6)
| Alex Limi
|-
| UX
| Front-end
| Plugins should not steal keyboard focus
| {{Pr1}} (7)
| Alex Limi
|-
| Distribution
| Front-end
| Bundled Extension Update/Enhancement
| {{Pr2}}
| Kev Needham
|-
| Distribution
| Front-end
| Group Policy Support for Deployment/Configuration
| {{Pr2}}
| Kev Needham
|-
| Distribution
| Front-end
| distribution.js Enhancements
| {{Pr2}}
| Kev Needham
|-
| Identity
| Front-end
| Sign into the browser: master password/profile/sync account redesign
| {{Pr2}}
| Dan Mills
|-
| Privacy
| Front-end
| [[Privacy/Features/Mixed-Content Lockdown|Safer mixed-content SSL/TLS mode with UI indicators]]
| {{Pr2}}
| Sid Stamm
|-
| Installers
| Front-end
| Multi-locale installers (Windows)
| {{Pr2}}
| Kev Needham
|-
| Installers
| Front-end
| Microsoft Scriptable Installer (.msi) for single and multi-locales
| {{Pr2}}
| Kev Needham
|-
| Installers
| Front-end
| Post-intstallation customization options (network and local storage)
| {{Pr2}}
| Kev Needham
|-
| Personas
| Front-end
| [[Firefox/Features/Personas Plus Merge|Build useful Personas Plus features into Firefox, obsolete the add-on]]
| {{Pr2}}
| Deb Richardson
|-
| Plugins
| Front-end
| Add plugincheck functionality to Add-on Manager
| {{Pr2}}
| Kev Needham
|-
| Plugins
| Front-end
| Blocklist UX enhancements
| {{Pr2}}
| Kev Needham
|-
| Plugins
| Front-end
| Improved Plugin installation/management experience
| {{Pr2}}
| Kev Needham
|-
| Privacy
| Front-end
| [[Privacy/Features/Geoloc UI respin|Better, more obvious geolocation UX]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Per-Tab Private Mode|Per-tab/window private mode]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Tracking Alert|Tracking alert to informs users when an entity is tracking them across sites]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Privacy Icons for Add-ons|Privacy icons to show what capabilities add-ons have]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Authentication State UI|Improve transparency of authentication state so users know when they're sending credentials to sites (and which ones)]]
| {{Pr2}}
| Sid Stamm
|-
| Sync
| Front-end
| Snippet view on Start Page
| {{Pr2}}
| Ragavan Srinivasan
|-
| User support
| Front-end
| More understandable way to clean cache and cookies
| {{Pr2}}
| Jay Sullivan
|-
| User support
| ???
| Make about:support API
| {{Pr2}}
| Jay Sullivan
|-
| User support
| Front-end
| Provide intuitive steps when Firefox can't connect
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| Animations in the UI
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| 20 high priority polish bugs
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| Panel-based download manager window
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Improved AwesomeBar results design
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Convert remaining window-modal dialogs to tab-modal
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Expose prefs for tabs-on-demand, DNT, always restore tabs
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Opt-in activation for plugins that are unknown/slow
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Find-in-page behavior and UI improvements
| {{Pr2}}
| Alex Limi
|-
| Web Apps
| Front-end
| In App experience v2
| {{Pr2}}
| Ragavan Srinivasan
|-
| Web Apps
| Front-end
| In App experience v1 (Site specific browser ++)
| {{Pr2}}
| Ragavan Srinivasan
|-
| Add-ons
| Front-end
| [[Firefox/Features/Expose_Add-on_Performance|Expose add-on performance information in Firefox]]
| {{Pr3}}
| Justin Scott
|-
| Distribution
| Front-end
| Distribution Automatic Update Service
| {{Pr3}}
| Kev Needham
|-
| Identity
| Front-end
| Account Manager: account information sprinkled on site-specific prefs
| {{Pr3}}
| Dan Mills
|-
| Installers
| Front-end
| Stub/Web-installer
| {{Pr3}}
| Kev Needham
|-
| Installers
| Front-end
| Multi-locale installers (Non-windows)
| {{Pr3}}
| Kev Needham
|-
| Personas
| Front-end
| Enhanced Personas (to be defined)
| {{Pr3}}
| Deb Richardson
|-
| User Engagement
| Front-end
| Allow engagement through Firefox Start Page based on browser's knowledge of the user
| {{Pr3}}
| Jay Sullivan
|-
| User support
| Front-end
| If Firefox won't start X times, try harder
| {{Pr3}}
| Jay Sullivan
|-
| User support
| Front-end
| [[Firefox/Features/about-crashes|Make crash reports helpful and easier to access]]
| {{Pr3}}
| Sheila Mooney
|-
| UX
| Front-end
| Download Manager Revision
| {{Pr3}}
| Jay Sullivan
|-
| UX
| Front-end
| Full set of HTML5 form controls
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Download file type cursors
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Continued menu cleanup (OS X, context, tab menu)
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Caps lock indicator in password field
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| File upload indicators on HTTP POST
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Better default new tab and tab siebling/parent behavior
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Reusable Panorama grouping API for e.g VerticalTabs
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| [[Firefox/Features/windows-scrolling|Support high resolution scrolling on windows]]
| Triage
| Faaborg
|-
| UX
| Front-end
| [[Firefox/Features/streamline-search|Streamline the visual appearance of the search field]]
| Triage
| Faaborg
|}

== Developer Tools ==
{| class="fullwidth-table sortable" style="width: 950px"
|-
| style="font-weight: bold; background: #DDD; width: 100px" | Roadmap
| style="font-weight: bold; background: #DDD; width: 100px" | Team
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD; width: 50px" | Rank
| style="font-weight: bold; background: #DDD; width: 150px" | Owner
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Highlighter|Highlighter]]
| {{Pr1}} (1)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/StyleInspector|Style Inspector]]
| {{Pr1}} (2)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/WebConsoleUpgrade|Console Improvements]]
| {{Pr1}} (3)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/GCLI|Graphical Command Line Interface (GCLI) Prototype]]
| {{Pr1}} (4)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Workspaces|Workspaces First Take]]
| {{Pr1}} (5)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/ViewSource|View Source Reboot]]
| {{Pr1}} (6)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/CSSEditor|CSS Editor]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/CSSDoctor|CSS Doctor]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Debugger|Debugger]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/SDK|DevTools SDK]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Object Inspector Plus
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Graphical Command Line Interface (GCLI) Release
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/WorkspacesRefined|Workspaces Refined]]
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Gauges
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Memory Snapshots
| {{Pr3}}
| Kevin Dangoor
|-
|}

[[Category:Features]]
[[Category:Firefox]]
[[Category:DevTools]]

Features/Desktop

2011-04-24T23:11:48Z

Faaborg: /* Firefox */

Prioritization has not been finalized, but the P1/P2/P3 buckets are accurate. If you have any questions, please contact [[User:Dria|Deb]].

__TOC__
== Firefox ==
{| class="fullwidth-table sortable" style="width: 950px"
|-
| style="font-weight: bold; background: #DDD; width: 100px" | Roadmap
| style="font-weight: bold; background: #DDD; width: 100px" | Team
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD; width: 50px" | Rank
| style="font-weight: bold; background: #DDD; width: 150px" | Owner
|-
| User support
| Front-end
| [[Support/Firefox Features/Clean install|Provide an intuitive path to clean install]]
| {{Pr1}}
| Cheng Wang
|-
| User support
| Front-end
| [[Support/Firefox Features/Clean up user profile|Ability to clean up user profile]]
| {{Pr1}}
| Michael Verdi
|-
| Privacy
| Front-end
| [[Privacy/Features/Site-based data management UI|Site-based data management UI]]
| {{Pr1}} (1)
| Sid Stamm
|-
| Release Mgmt
| Front-end
| [[ChannelSwitching/ChannelSwitchingFeature|Channel Switching]]
| {{Pr1}} (1)
| Sheila Mooney
|-
| Search
| Front-end
| [[Firefox/Features/keywordurl_follows_searchbar|Replace keyword.URL to follow Search Bar and/or allow independent setting of provider]]
| {{Pr1}} (1)
| Kev Needham
|-
| Sharing
| Front-end
| [[Labs/F1|Sharing]] UI in Firefox
| {{Pr1}} (1)
| Bryan Clark
|-
| Sync
| Front-end
| [[Firefox/Features/Sync_Discoverability|Improve discoverability of Sync]]
| {{Pr1}} (1)
| Ragavan Srinivasan
|-
| UX
| Front-end
| [[Firefox/Features/50ms_ASSERT|Understand when user interface feels laggy]]
| {{Pr1}} (1)
| Jay Sullivan
|-
| UX
| Front-end
| [[Firefox/Features/URL_Autocomplete |Inline URL autocomplete]]
| {{Pr1}} (1)
| Alex Limi
|-
| Web Apps
| Front-end
| App install/uninstall APIs in Firefox
| {{Pr1}} (1)
| Ragavan Srinivasan
|-
| Plugins
| Front-end
| Add link to plugincheck from AOM
| {{Pr1}} (2)
| Kev Needham
|-
| UX
| Front-end
| [[Firefox/Features/Electrolysis|Execute chrome in separate process]]
| {{Pr1}} (2)
| Jay Sullivan
|-
| UX
| Front-end
| [[Firefox/Features/Persist_Panorama_Groups|Panorama groups should always persist]]
| {{Pr1}} (2)
| Alex Limi
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Third Party Add-on Warnings|Ensure user accepts add-ons installed by third-party apps]]
| {{Pr1}} (3)
| Mossop
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Confirm on Upgrade|Confirm add-ons on upgrade]]
| {{Pr1}} (3)
| Mossop
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Improve_Add-on_Installation|Improve Add-on Installation]]
| {{Pr1}} (3)
| Boriss
|-
| Plugins
| Front-end
| Use PFS2 for pfs.datasource.url in Mozilla product(s)
| {{Pr1}} (3)
| Kev Needham
|-
| UX
| Front-end
| Don't resize when closing tabs
| {{Pr1}} (3)
| Alex Limi
|-
| Web Apps
| Front-end
| HTML5 Web App dashboard
| {{Pr1}} (3)
| Ragavan Srinivasan
|-
| Add-ons
| Front-end
| [[Firefox/Features/Easier_Add-on_Compatibility|Solution to frequent compatibility updates]]
| {{Pr1}} (4)
| Justin Scott
|-
| Identity
| Front-end
| [[Identity/Features/In-browser_sign-in_UI|In-browser sign-in UI]]
| {{Pr1}} (4)
| Dan Mills
|-
| UX
| Front-end
| Tab move/detach animations
| {{Pr1}} (4)
| Alex Limi
|-
| UX
| Front-end
| Toolbar-less app tabs
| {{Pr1}} (5)
| Alex Limi
|-
| Web Apps
| Front-end
| [[Firefox/Features/Home_Tab|Home Tab as Permanent App Tab]]
| {{Pr1}} (5)
| Jay Sullivan
|-
| UX
| Front-end
| Inactive Panorama groups should load on-demand
| {{Pr1}} (6)
| Alex Limi
|-
| UX
| Front-end
| Plugins should not steal keyboard focus
| {{Pr1}} (7)
| Alex Limi
|-
| Distribution
| Front-end
| Bundled Extension Update/Enhancement
| {{Pr2}}
| Kev Needham
|-
| Distribution
| Front-end
| Group Policy Support for Deployment/Configuration
| {{Pr2}}
| Kev Needham
|-
| Distribution
| Front-end
| distribution.js Enhancements
| {{Pr2}}
| Kev Needham
|-
| Identity
| Front-end
| Sign into the browser: master password/profile/sync account redesign
| {{Pr2}}
| Dan Mills
|-
| Privacy
| Front-end
| [[Privacy/Features/Mixed-Content Lockdown|Safer mixed-content SSL/TLS mode with UI indicators]]
| {{Pr2}}
| Sid Stamm
|-
| Installers
| Front-end
| Multi-locale installers (Windows)
| {{Pr2}}
| Kev Needham
|-
| Installers
| Front-end
| Microsoft Scriptable Installer (.msi) for single and multi-locales
| {{Pr2}}
| Kev Needham
|-
| Installers
| Front-end
| Post-intstallation customization options (network and local storage)
| {{Pr2}}
| Kev Needham
|-
| Personas
| Front-end
| [[Firefox/Features/Personas Plus Merge|Build useful Personas Plus features into Firefox, obsolete the add-on]]
| {{Pr2}}
| Deb Richardson
|-
| Plugins
| Front-end
| Add plugincheck functionality to Add-on Manager
| {{Pr2}}
| Kev Needham
|-
| Plugins
| Front-end
| Blocklist UX enhancements
| {{Pr2}}
| Kev Needham
|-
| Plugins
| Front-end
| Improved Plugin installation/management experience
| {{Pr2}}
| Kev Needham
|-
| Privacy
| Front-end
| [[Privacy/Features/Geoloc UI respin|Better, more obvious geolocation UX]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Per-Tab Private Mode|Per-tab/window private mode]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Tracking Alert|Tracking alert to informs users when an entity is tracking them across sites]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Privacy Icons for Add-ons|Privacy icons to show what capabilities add-ons have]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Authentication State UI|Improve transparency of authentication state so users know when they're sending credentials to sites (and which ones)]]
| {{Pr2}}
| Sid Stamm
|-
| Sync
| Front-end
| Snippet view on Start Page
| {{Pr2}}
| Ragavan Srinivasan
|-
| User support
| Front-end
| More understandable way to clean cache and cookies
| {{Pr2}}
| Jay Sullivan
|-
| User support
| ???
| Make about:support API
| {{Pr2}}
| Jay Sullivan
|-
| User support
| Front-end
| Provide intuitive steps when Firefox can't connect
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| Animations in the UI
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| 20 high priority polish bugs
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| Panel-based download manager window
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Improved AwesomeBar results design
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Convert remaining window-modal dialogs to tab-modal
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Expose prefs for tabs-on-demand, DNT, always restore tabs
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Opt-in activation for plugins that are unknown/slow
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Find-in-page behavior and UI improvements
| {{Pr2}}
| Alex Limi
|-
| Web Apps
| Front-end
| In App experience v2
| {{Pr2}}
| Ragavan Srinivasan
|-
| Web Apps
| Front-end
| In App experience v1 (Site specific browser ++)
| {{Pr2}}
| Ragavan Srinivasan
|-
| Add-ons
| Front-end
| [[Firefox/Features/Expose_Add-on_Performance|Expose add-on performance information in Firefox]]
| {{Pr3}}
| Justin Scott
|-
| Distribution
| Front-end
| Distribution Automatic Update Service
| {{Pr3}}
| Kev Needham
|-
| Identity
| Front-end
| Account Manager: account information sprinkled on site-specific prefs
| {{Pr3}}
| Dan Mills
|-
| Installers
| Front-end
| Stub/Web-installer
| {{Pr3}}
| Kev Needham
|-
| Installers
| Front-end
| Multi-locale installers (Non-windows)
| {{Pr3}}
| Kev Needham
|-
| Personas
| Front-end
| Enhanced Personas (to be defined)
| {{Pr3}}
| Deb Richardson
|-
| User Engagement
| Front-end
| Allow engagement through Firefox Start Page based on browser's knowledge of the user
| {{Pr3}}
| Jay Sullivan
|-
| User support
| Front-end
| If Firefox won't start X times, try harder
| {{Pr3}}
| Jay Sullivan
|-
| User support
| Front-end
| [[Firefox/Features/about-crashes|Make crash reports helpful and easier to access]]
| {{Pr3}}
| Sheila Mooney
|-
| UX
| Front-end
| Download Manager Revision
| {{Pr3}}
| Jay Sullivan
|-
| UX
| Front-end
| Full set of HTML5 form controls
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Download file type cursors
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Continued menu cleanup (OS X, context, tab menu)
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Caps lock indicator in password field
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| File upload indicators on HTTP POST
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Better default new tab and tab siebling/parent behavior
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Reusable Panorama grouping API for e.g VerticalTabs
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| [[Firefox/Features/windows-scrolling|Support High resolution scrolling on windows]
| Triage
| Faaborg
|}

== Developer Tools ==
{| class="fullwidth-table sortable" style="width: 950px"
|-
| style="font-weight: bold; background: #DDD; width: 100px" | Roadmap
| style="font-weight: bold; background: #DDD; width: 100px" | Team
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD; width: 50px" | Rank
| style="font-weight: bold; background: #DDD; width: 150px" | Owner
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Highlighter|Highlighter]]
| {{Pr1}} (1)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/StyleInspector|Style Inspector]]
| {{Pr1}} (2)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/WebConsoleUpgrade|Console Improvements]]
| {{Pr1}} (3)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/GCLI|Graphical Command Line Interface (GCLI) Prototype]]
| {{Pr1}} (4)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Workspaces|Workspaces First Take]]
| {{Pr1}} (5)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/ViewSource|View Source Reboot]]
| {{Pr1}} (6)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/CSSEditor|CSS Editor]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/CSSDoctor|CSS Doctor]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Debugger|Debugger]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/SDK|DevTools SDK]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Object Inspector Plus
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Graphical Command Line Interface (GCLI) Release
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/WorkspacesRefined|Workspaces Refined]]
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Gauges
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Memory Snapshots
| {{Pr3}}
| Kevin Dangoor
|-
|}

[[Category:Features]]
[[Category:Firefox]]
[[Category:DevTools]]

Firefox/Features/Persist Panorama Groups

2011-04-24T23:04:30Z

Faaborg: /* Non-Goals */

Extension Manager:Projects:Improve Add-on Installation

2011-04-24T22:44:21Z

Faaborg: /* Related Bugs & Dependencies */

Features/Desktop

2011-04-24T21:21:37Z

Faaborg: /* Firefox */

Prioritization has not been finalized, but the P1/P2/P3 buckets are accurate. If you have any questions, please contact [[User:Dria|Deb]].

__TOC__
== Firefox ==
{| class="fullwidth-table sortable" style="width: 950px"
|-
| style="font-weight: bold; background: #DDD; width: 100px" | Roadmap
| style="font-weight: bold; background: #DDD; width: 100px" | Team
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD; width: 50px" | Rank
| style="font-weight: bold; background: #DDD; width: 150px" | Owner
|-
| User support
| Front-end
| [[Support/Firefox Features/Clean install|Provide an intuitive path to clean install]]
| {{Pr1}}
| Cheng Wang
|-
| User support
| Front-end
| [[Support/Firefox Features/Clean up user profile|Ability to clean up user profile]]
| {{Pr1}}
| Michael Verdi
|-
| Privacy
| Front-end
| [[Privacy/Features/Site-based data management UI|Site-based data management UI]]
| {{Pr1}} (1)
| Sid Stamm
|-
| Release Mgmt
| Front-end
| [[ChannelSwitching/ChannelSwitchingFeature|Channel Switching]]
| {{Pr1}} (1)
| Sheila Mooney
|-
| Search
| Front-end
| [[Firefox/Features/keywordurl_follows_searchbar|Replace keyword.URL to follow Search Bar and/or allow independent setting of provider]]
| {{Pr1}} (1)
| Kev Needham
|-
| Sharing
| Front-end
| [[Labs/F1|Sharing]] UI in Firefox
| {{Pr1}} (1)
| Bryan Clark
|-
| Sync
| Front-end
| [[Firefox/Features/Sync_Discoverability|Improve discoverability of Sync]]
| {{Pr1}} (1)
| Ragavan Srinivasan
|-
| UX
| Front-end
| [[Firefox/Features/50ms_ASSERT|Understand when user interface feels laggy]]
| {{Pr1}} (1)
| Jay Sullivan
|-
| UX
| Front-end
| [[Firefox/Features/URL_Autocomplete |Inline URL autocomplete]]
| {{Pr1}} (1)
| Alex Limi
|-
| Web Apps
| Front-end
| App install/uninstall APIs in Firefox
| {{Pr1}} (1)
| Ragavan Srinivasan
|-
| Plugins
| Front-end
| Add link to plugincheck from AOM
| {{Pr1}} (2)
| Kev Needham
|-
| UX
| Front-end
| [[Firefox/Features/Electrolysis|Execute chrome in separate process]]
| {{Pr1}} (2)
| Jay Sullivan
|-
| UX
| Front-end
| [[Firefox/Features/Persist_Panorama_Groups|Panorama groups should always persist]]
| {{Pr1}} (2)
| Alex Limi
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Third Party Add-on Warnings|Ensure user accepts add-ons installed by third-party apps]]
| {{Pr1}} (3)
| Mossop
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Confirm on Upgrade|Confirm add-ons on upgrade]]
| {{Pr1}} (3)
| Mossop
|-
| Add-ons
| Front-end
| [[Extension Manager:Projects:Improve_Add-on_Installation|Improve Add-on Installation]]
| {{Pr1}} (3)
| Boriss
|-
| Plugins
| Front-end
| Use PFS2 for pfs.datasource.url in Mozilla product(s)
| {{Pr1}} (3)
| Kev Needham
|-
| UX
| Front-end
| Don't resize when closing tabs
| {{Pr1}} (3)
| Alex Limi
|-
| Web Apps
| Front-end
| HTML5 Web App dashboard
| {{Pr1}} (3)
| Ragavan Srinivasan
|-
| Add-ons
| Front-end
| [[Firefox/Features/Easier_Add-on_Compatibility|Solution to frequent compatibility updates]]
| {{Pr1}} (4)
| Justin Scott
|-
| Identity
| Front-end
| [[Identity/Features/In-browser_sign-in_UI|In-browser sign-in UI]]
| {{Pr1}} (4)
| Dan Mills
|-
| UX
| Front-end
| Tab move/detach animations
| {{Pr1}} (4)
| Alex Limi
|-
| UX
| Front-end
| Toolbar-less app tabs
| {{Pr1}} (5)
| Alex Limi
|-
| Web Apps
| Front-end
| [[Firefox/Features/Home_Tab|Home Tab as Permanent App Tab]]
| {{Pr1}} (5)
| Jay Sullivan
|-
| UX
| Front-end
| Inactive Panorama groups should load on-demand
| {{Pr1}} (6)
| Alex Limi
|-
| UX
| Front-end
| Plugins should not steal keyboard focus
| {{Pr1}} (7)
| Alex Limi
|-
| Distribution
| Front-end
| Bundled Extension Update/Enhancement
| {{Pr2}}
| Kev Needham
|-
| Distribution
| Front-end
| Group Policy Support for Deployment/Configuration
| {{Pr2}}
| Kev Needham
|-
| Distribution
| Front-end
| distribution.js Enhancements
| {{Pr2}}
| Kev Needham
|-
| Identity
| Front-end
| Sign into the browser: master password/profile/sync account redesign
| {{Pr2}}
| Dan Mills
|-
| Privacy
| Front-end
| [[Privacy/Features/Mixed-Content Lockdown|Safer mixed-content SSL/TLS mode with UI indicators]]
| {{Pr2}}
| Sid Stamm
|-
| Installers
| Front-end
| Multi-locale installers (Windows)
| {{Pr2}}
| Kev Needham
|-
| Installers
| Front-end
| Microsoft Scriptable Installer (.msi) for single and multi-locales
| {{Pr2}}
| Kev Needham
|-
| Installers
| Front-end
| Post-intstallation customization options (network and local storage)
| {{Pr2}}
| Kev Needham
|-
| Personas
| Front-end
| [[Firefox/Features/Personas Plus Merge|Build useful Personas Plus features into Firefox, obsolete the add-on]]
| {{Pr2}}
| Deb Richardson
|-
| Plugins
| Front-end
| Add plugincheck functionality to Add-on Manager
| {{Pr2}}
| Kev Needham
|-
| Plugins
| Front-end
| Blocklist UX enhancements
| {{Pr2}}
| Kev Needham
|-
| Plugins
| Front-end
| Improved Plugin installation/management experience
| {{Pr2}}
| Kev Needham
|-
| Privacy
| Front-end
| [[Privacy/Features/Geoloc UI respin|Better, more obvious geolocation UX]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Per-Tab Private Mode|Per-tab/window private mode]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Tracking Alert|Tracking alert to informs users when an entity is tracking them across sites]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Privacy Icons for Add-ons|Privacy icons to show what capabilities add-ons have]]
| {{Pr2}}
| Sid Stamm
|-
| Privacy
| Front-end
| [[Privacy/Features/Authentication State UI|Improve transparency of authentication state so users know when they're sending credentials to sites (and which ones)]]
| {{Pr2}}
| Sid Stamm
|-
| Sync
| Front-end
| Snippet view on Start Page
| {{Pr2}}
| Ragavan Srinivasan
|-
| User support
| Front-end
| More understandable way to clean cache and cookies
| {{Pr2}}
| Jay Sullivan
|-
| User support
| ???
| Make about:support API
| {{Pr2}}
| Jay Sullivan
|-
| User support
| Front-end
| Provide intuitive steps when Firefox can't connect
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| Animations in the UI
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| 20 high priority polish bugs
| {{Pr2}}
| Jay Sullivan
|-
| UX
| Front-end
| Panel-based download manager window
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Improved AwesomeBar results design
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Convert remaining window-modal dialogs to tab-modal
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Expose prefs for tabs-on-demand, DNT, always restore tabs
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Opt-in activation for plugins that are unknown/slow
| {{Pr2}}
| Alex Limi
|-
| UX
| Front-end
| Find-in-page behavior and UI improvements
| {{Pr2}}
| Alex Limi
|-
| Web Apps
| Front-end
| In App experience v2
| {{Pr2}}
| Ragavan Srinivasan
|-
| Web Apps
| Front-end
| In App experience v1 (Site specific browser ++)
| {{Pr2}}
| Ragavan Srinivasan
|-
| Add-ons
| Front-end
| [[Firefox/Features/Expose_Add-on_Performance|Expose add-on performance information in Firefox]]
| {{Pr3}}
| Justin Scott
|-
| Distribution
| Front-end
| Distribution Automatic Update Service
| {{Pr3}}
| Kev Needham
|-
| Identity
| Front-end
| Account Manager: account information sprinkled on site-specific prefs
| {{Pr3}}
| Dan Mills
|-
| Installers
| Front-end
| Stub/Web-installer
| {{Pr3}}
| Kev Needham
|-
| Installers
| Front-end
| Multi-locale installers (Non-windows)
| {{Pr3}}
| Kev Needham
|-
| Personas
| Front-end
| Enhanced Personas (to be defined)
| {{Pr3}}
| Deb Richardson
|-
| User Engagement
| Front-end
| Allow engagement through Firefox Start Page based on browser's knowledge of the user
| {{Pr3}}
| Jay Sullivan
|-
| User support
| Front-end
| If Firefox won't start X times, try harder
| {{Pr3}}
| Jay Sullivan
|-
| User support
| Front-end
| [[Firefox/Features/about-crashes|Make crash reports helpful and easier to access]]
| {{Pr3}}
| Sheila Mooney
|-
| UX
| Front-end
| Download Manager Revision
| {{Pr3}}
| Jay Sullivan
|-
| UX
| Front-end
| Full set of HTML5 form controls
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Download file type cursors
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Continued menu cleanup (OS X, context, tab menu)
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Caps lock indicator in password field
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| File upload indicators on HTTP POST
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Better default new tab and tab siebling/parent behavior
| {{Pr3}}
| Alex Limi
|-
| UX
| Front-end
| Reusable Panorama grouping API for e.g VerticalTabs
| {{Pr3}}
| Alex Limi
|}

== Developer Tools ==
{| class="fullwidth-table sortable" style="width: 950px"
|-
| style="font-weight: bold; background: #DDD; width: 100px" | Roadmap
| style="font-weight: bold; background: #DDD; width: 100px" | Team
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD; width: 50px" | Rank
| style="font-weight: bold; background: #DDD; width: 150px" | Owner
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Highlighter|Highlighter]]
| {{Pr1}} (1)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/StyleInspector|Style Inspector]]
| {{Pr1}} (2)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/WebConsoleUpgrade|Console Improvements]]
| {{Pr1}} (3)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/GCLI|Graphical Command Line Interface (GCLI) Prototype]]
| {{Pr1}} (4)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Workspaces|Workspaces First Take]]
| {{Pr1}} (5)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/ViewSource|View Source Reboot]]
| {{Pr1}} (6)
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/CSSEditor|CSS Editor]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/CSSDoctor|CSS Doctor]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/Debugger|Debugger]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/SDK|DevTools SDK]]
| {{Pr2}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Object Inspector Plus
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Graphical Command Line Interface (GCLI) Release
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| [[DevTools/Features/WorkspacesRefined|Workspaces Refined]]
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Gauges
| {{Pr3}}
| Kevin Dangoor
|-
| DevTools
| DevTools Front-end
| Memory Snapshots
| {{Pr3}}
| Kevin Dangoor
|-
|}

[[Category:Features]]
[[Category:Firefox]]
[[Category:DevTools]]

Firefox/Features/UX Priorities

2011-04-02T20:33:19Z

Faaborg: /* Polish/cleanup */

{{Restricted}}

Want help make the user experience of Firefox the best it can be? Here are the top priorities identified by the UX team. They are in order of priority, grouped under new features, revised features, and polish/cleanup.

If you want to help out with any of these, get in touch with Alex Limi to coordinate, limi@mozilla.com.

== New features ==
# Sharing (UX tracked in {{bug|642684}})
# Identity (UX tracked at http://areweprettyyet.com/5/accountManager for now)
# Home tab, putting it in an app tab ({{bug|544819}}) is the first step
# New tab page
# Taskbar Web Apps
# In-browser preview + Save of common content (PDF, cd:attachment, mp3, etc)
# Add-ons: Standardized toolbar/doorhanger (pane) support
# Tab multiselect: {{bug|566510}}
# File upload indicators: We should supply a standard way of showing progress on file uploads via forms, people are using Flash to do this right now, and it sucks.

== Feature revision ==
# Install/Update: Channel switcher, {{bug|644517}}
# Install/Update: Silent updates & on shutdown where we can't do silent
# User control of extensions & plugins, {{bug|596343}}
# Panorama groups should persist, load on-demand
# In-line autocomplete, {{bug|566489}} — how quickly a user can get to a site is a key part of the perceived performance, we also need to do a better job with the audience that “speaks URLs”
# Opt-in activation for plugins that are unknown/slow (similar to Flashblock), better missing plugin experience, ability to soft-block 0-day using click-to-play. Settings: Render (Always|when clicked|never), "Don't ask me to install this plugin again"
# Panorama improvements
# Panel-based Download Manager (see [Limi's article http://limi.net/articles/improving-download-behaviors-web-browsers] [[Improved download manager]])
# Find-in-page cleanup
# OS X 10.7 features: scrollbar, full screen mode, three-finger gestures
# Self-sharing feature for F1, aka. "For Later"
# Install/Update: Mac improvements, {{bug|516362}}
# Install/Update: Stub installer
# Install/Update: Easier fresh install
# Add zoom controls to the Firefox menu: {{bug|592147}} or should show an indicator when the zoom level deviates from the standard. Also: ability to set a global zoom level.
# Default UI for contentEditable, cleanup, make it output better code
# Improved discovery pane in add-ons manager
# Backgrounds and themes view in the add-ons manager/live preview
# Sync Promotion
# Private browsing windows open without restart
# Private browsing theme change (darkened)
# Import dialog doesn't offer Sync import or Chrome import
# Don't let add-ons that are not compatible with an unsupported version of Firefox stop you from upgrading: {{bug|597598}} — i.e. an add-on that doesn't work with 3.6 nor with 4.0 shouldn't stop you from upgrading your Firefox 3.5 to 4.0
# Better missing plugin experience
# Improve fullscreen experience, especially in preparation for OS X 10.7
# Self-documenting keyboard shortcut overview, (generated from the code?) — should inform a keyboard shortcut cleanup

== Polish/cleanup ==
# High resolution scrolling on windows {{bug|605648}}
# Back button hit area is a small circle, doesn't touch screen edge {{bug|590945}}
# Overall UI responsiveness and drawing operations
# Tab animations: tab close behavior, tab open behavior ({{bug|578327}} and/or {{bug|530203}}?), tab drag ({{bug|455694}}) tab detach ({{bug|485105}}), eliminate redundant title text ({{bug|583890}})
# Location/Search bar cleanup, {{bug|592909}}
# App tabs: chromeless app tabs, {{bug|585445}} (includes: Cmd/Ctrl-L doesn't bring up the AwesomeBar when location bar is hidden)
# App tabs: Global app tabs, {{bug|587873}}
# Fix Firefox menu rendering, {{bug|594821}}
# Make Search local to the tab (at least for tabs-on-top): {{bug|565740}}
# Remove 3-second delay from AMO installs {{bug|646602}}
# Put back keyboard shortcuts that went "missing", F6 on Windows is a big one, possibly Ctrl-E too
# Don't show "about:blank" in URL bar of new tabs
# Mac windows without tabs render incorrectly
# AwesomeBar results visual design, {{bug|587909}}
# File type cursors, especially useful for binary downloads + PDFs (“the land mines of the internet”)
# Find bar should disappear on navigation events, {{bug|628179}}
# New tab should never lose focus from URL/search bar (this got implemented only halfway)
# Web sites should never be allowed to resize main window, only pop-ups
# Display the domain in black and the path in grey: {{bug|451833}} — makes domains more readable and prominent, parity with other browsers# Papercuts: Flash stealing focus, copy/paste rich vs plain text
# Doorhangers + modal dialogs cleanup, keep eliminating notifications (e.g. update -> Home tab): httpauth {{bug|567804}}, Popups blocked {{bug|588317}}, XPI install {{bug|588266}}, onunload {{bug|588292}}
# Expose prefs that made it too late (tabs-on-demand, DNT, always restore tabs, switch-to-tab in location bar prefs)
# List All Tabs menu should list closed tabs/windows for more obvious undo: {{bug|597593}}
# Animation for doorhangers, so it's obvious that you can bring them back
# Styling for indicators in the URL bar (password, geo, etc)
# Favicon outside SSL indicator, improve visual design
# Improved about:sessionrestore
# Context menu cleanup
# Extract PDF to main menu (windows)
# Better about:config — make it easier to reset to defaults, to view only changed values, and make boolean values checkboxes instead of text labels, add autocomplete for “about:”
# Remove the flash message on new tab on open
# full screen on windows (display the firefox button, normal window controls)
# Update default fonts
# In-content windows like Add-ons manager should remember if you pulled them out to separate windows.
# Caps Lock indicator in password field
# Multiselect support for disable/remove add-ons
# Don't import useless bookmarks: We currently import bookmarks from IE (Windows Marketplace, Windows Update, etc) that aren't even usable from Firefox, and that the user didn't add. With Sync, suddenly you have this on your phone too.
# Improve OS X "select" tag rendering, dropdown menu should look like OSX dropdown menus rather than windows in more cases (it drops down to platform-independent version now)
# Get rid of tab overflow indicators (might need some simple user testing to make sure)
# Allow shorter tabs, use gradients instead of ellipses for text overflow
# Visually distinguish visible tabs in List All Tabs menu
# [[Firefox/Projects/Eradicate Startup Dialogs]]
# Attach “create custom search” onto search form completion dropdowns (possibly with threshold, detect search fields, 3rd time etc)
# Improve session restore screen to support groups/windows better
# Move "Know your rights" {{bug|571584}} and Firefox update available {{bug|588227}} to home tab snippets
# Ctrl-tab should know about tab order instead of just moving left-to-right
# Clone tab history (and form/session data?) from parent tab when opening a new one
# Tooltips stick around and overlay other apps on OS X when switching apps

== Infrastructure (with no UI) ==
Projects we care about that have UX impact, but little to no UI.
# Bundle Flash with Firefox
# In-browser PDF display — PDFkit on Mac? http://code.google.com/p/firefox-mac-pdf/
# Detection of captive portals
# JägerMonkey for UI
# Resource Packages
# jemalloc support on Mac
# Smarter disk cache
# More performance data, memory usage data, CPU usage data, hang detection as part of system pings — what we can't measure, we can't improve
# SSL should support form restore too, possibly with timeout
# Reusable grouping API for tabs (so other extensions, e.g. VerticalTabs, can reuse Panorama groups), tabs need UUIDs.
# Gmail/GC + Netflix
# Reinstall experience: a way to ask if they want fresh settings or keep their old ones

== Research projects ==
Projects we need to get started early, since they need more data and/or design explorations.
# Combine URL and search bar: We should make common actions available in the location bar, and do some user testing to figure out what patterns people use while searching vs. entering URLs. Also figure out what the percentages are via metrics.
# Do user testing on various SSL/identity variants, see if there's a difference and whether we can help people understand it better when they want to.
# In-content preferences (including unifying customization/appearance/themes, eliminating unneeded windows), faster navigation, better grouping
# User test various progress indicator variations (perception of speed): Better indicator for how much of a page is downloaded, maybe even separate indicator for page vs resources on the page.
# Unify bookmarks/history/tabs and make the transition between them more seamless, browse + search UIs for these
# Better Customization UI, should be in-content, include appearance and toolbar customization in one.
# Ability to manage hundreds of tabs in low memory situations (serialization, freeze JS, etc)
# Look into network latency issues, prefetch, preload-on-hover, "optimize away the network when we can", etc
# Tablet UI
# Design and plan for "Actions" (include menu items in this, like Dietrich's extension?)
# New design for "Find text in page"
# Built-in translation: Capability of selecting text and translating it, offer to translate page when not in user's selected language
# Improved content authoring/editing: Provide a great, default UI for contentEditable: Everyone constructs their own UI on top of contentEditable at the moment, we should supply a good default implementation, like we do for video controls. Table editing in particular is bad ,the inner workings of contentEditable need some love too.
# Merge folders & tags
# "The Vault", a way to save/freeze content, save encrypted to Sync container, and have them follow you around (receipts, tickets, etc)
# Combine URL/search bar, support actions
# Multiuser support, logging in to your browser, sandboxed secure profiles
# Collecting people/locations/time, service discovery, navigable pages in the browser include meta-pages of location, people, etc.
# Global Undo: For closing tabs, closing windows, figure out what should and shouldn't be in the undo stack.
# Saving web pages in a way that doesn't suck: Receipts, offline reading (“read later”), Paolo has a related project here, MAF: http://maf.mozdev.org/
# New interface primitives for extensions: combine the multitude of hook-in points to a single interface.
# Unify plugins and extension listings, straighten out the language (add-ons)
# Volume per tab and/or some way to indicate "which tab is making noise"
# Sidebar tabs: A power-user interface that gives you better control of large number of open pages. Partial thumbnails, grouping, filtering. [http://limi.net/articles/reinventing-tabs-for-the-browser/ blog post #1], [http://limi.net/articles/tabs-and-the-mozilla-design-challenge/ blog post #2] (limi)
# History as a parallel timeline? Better indication in human terms and navigation of sites in history ([http://weizhou.wordpress.com/2008/07/07/prototype/ wei's sprint] [http://weizhoudesign.com/browserin2015.swf wei's video] [http://www.simile-widgets.org/timeline/ Simile Timeline] [http://www.slifelabs.com/ Slife]
# Sync my contacts across sites, let me use my Facebook people elsewhere, autocomplete people (with faces)
# Web page quick look: User-triggered way to get an idea of where a link will go, possibly show a preview or some information about where a link leads
# Vista/Win7 explorer-like interface for navigating favorites, get rid of URLs when displaying favorites

== Tool & process improvements ==
* community for design discussion?
* omnigraffle stencils for awpy
* new nighly build icon
* visualization tool for progress on a feature over time: treadmill
* HTML bugmail / new bugzilla theme

Firefox/Features/UX Priorities

2011-04-01T16:50:57Z

Faaborg: /* Polish/cleanup */

{{Restricted}}

Want help make the user experience of Firefox the best it can be? Here are the top priorities identified by the UX team. They are in order of priority, grouped under new features, revised features, and polish/cleanup.

If you want to help out with any of these, get in touch with Alex Limi to coordinate, limi@mozilla.com.

== New features ==
# Sharing (UX tracked in {{bug|642684}})
# Identity (UX tracked at http://areweprettyyet.com/5/accountManager for now)
# Home tab, putting it in an app tab ({{bug|544819}}) is the first step
# New tab page
# Taskbar Web Apps
# In-browser preview + Save of common content (PDF, cd:attachment, mp3, etc)
# Add-ons: Standardized toolbar/doorhanger (pane) support
# Tab multiselect: {{bug|566510}}
# File upload indicators: We should supply a standard way of showing progress on file uploads via forms, people are using Flash to do this right now, and it sucks.

== Feature revision ==
# Install/Update: Channel switcher, {{bug|644517}}
# Install/Update: Silent updates & on shutdown where we can't do silent
# User control of extensions & plugins, {{bug|596343}}
# Panorama groups should persist, load on-demand
# In-line autocomplete, {{bug|566489}} — how quickly a user can get to a site is a key part of the perceived performance, we also need to do a better job with the audience that “speaks URLs”
# Opt-in activation for plugins that are unknown/slow (similar to Flashblock), better missing plugin experience, ability to soft-block 0-day using click-to-play. Settings: Render (Always|when clicked|never), "Don't ask me to install this plugin again"
# Panorama improvements
# Panel-based Download Manager (see [Limi's article http://limi.net/articles/improving-download-behaviors-web-browsers] [[Improved download manager]])
# Find-in-page cleanup
# OS X 10.7 features: scrollbar, full screen mode, three-finger gestures
# Self-sharing feature for F1, aka. "For Later"
# Install/Update: Mac improvements, {{bug|516362}}
# Install/Update: Stub installer
# Install/Update: Easier fresh install
# Add zoom controls to the Firefox menu: {{bug|592147}} or should show an indicator when the zoom level deviates from the standard. Also: ability to set a global zoom level.
# Default UI for contentEditable, cleanup, make it output better code
# Improved discovery pane in add-ons manager
# Backgrounds and themes view in the add-ons manager/live preview
# Sync Promotion
# Private browsing windows open without restart
# Private browsing theme change (darkened)
# Import dialog doesn't offer Sync import or Chrome import
# Don't let add-ons that are not compatible with an unsupported version of Firefox stop you from upgrading: {{bug|597598}} — i.e. an add-on that doesn't work with 3.6 nor with 4.0 shouldn't stop you from upgrading your Firefox 3.5 to 4.0
# Better missing plugin experience
# Improve fullscreen experience, especially in preparation for OS X 10.7
# Self-documenting keyboard shortcut overview, (generated from the code?) — should inform a keyboard shortcut cleanup

== Polish/cleanup ==
# High resolution scrolling on windows {{bug|605648}}
# Overall UI responsiveness and drawing operations
# Tab animations: tab close behavior, tab open behavior ({{bug|578327}} and/or {{bug|530203}}?), tab drag ({{bug|455694}}) tab detach ({{bug|485105}}), eliminate redundant title text ({{bug|583890}})
# Location/Search bar cleanup, {{bug|592909}}
# App tabs: chromeless app tabs, {{bug|585445}} (includes: Cmd/Ctrl-L doesn't bring up the AwesomeBar when location bar is hidden)
# App tabs: Global app tabs, {{bug|587873}}
# Fix Firefox menu rendering, {{bug|594821}}
# Make Search local to the tab (at least for tabs-on-top): {{bug|565740}}
# Remove 3-second delay from AMO installs {{bug|646602}}
# Put back keyboard shortcuts that went "missing", F6 on Windows is a big one, possibly Ctrl-E too
# Don't show "about:blank" in URL bar of new tabs
# Mac windows without tabs render incorrectly
# AwesomeBar results visual design, {{bug|587909}}
# File type cursors, especially useful for binary downloads + PDFs (“the land mines of the internet”)
# Find bar should disappear on navigation events, {{bug|628179}}
# New tab should never lose focus from URL/search bar (this got implemented only halfway)
# Web sites should never be allowed to resize main window, only pop-ups
# Display the domain in black and the path in grey: {{bug|451833}} — makes domains more readable and prominent, parity with other browsers# Papercuts: Flash stealing focus, copy/paste rich vs plain text
# Doorhangers + modal dialogs cleanup, keep eliminating notifications (e.g. update -> Home tab): httpauth {{bug|567804}}, Popups blocked {{bug|588317}}, XPI install {{bug|588266}}, onunload {{bug|588292}}
# Expose prefs that made it too late (tabs-on-demand, DNT, always restore tabs, switch-to-tab in location bar prefs)
# List All Tabs menu should list closed tabs/windows for more obvious undo: {{bug|597593}}
# Animation for doorhangers, so it's obvious that you can bring them back
# Styling for indicators in the URL bar (password, geo, etc)
# Favicon outside SSL indicator, improve visual design
# Improved about:sessionrestore
# Context menu cleanup
# Extract PDF to main menu (windows)
# Better about:config — make it easier to reset to defaults, to view only changed values, and make boolean values checkboxes instead of text labels, add autocomplete for “about:”
# Remove the flash message on new tab on open
# full screen on windows (display the firefox button, normal window controls)
# Update default fonts
# In-content windows like Add-ons manager should remember if you pulled them out to separate windows.
# Caps Lock indicator in password field
# Multiselect support for disable/remove add-ons
# Don't import useless bookmarks: We currently import bookmarks from IE (Windows Marketplace, Windows Update, etc) that aren't even usable from Firefox, and that the user didn't add. With Sync, suddenly you have this on your phone too.
# Improve OS X "select" tag rendering, dropdown menu should look like OSX dropdown menus rather than windows in more cases (it drops down to platform-independent version now)
# Get rid of tab overflow indicators (might need some simple user testing to make sure)
# Allow shorter tabs, use gradients instead of ellipses for text overflow
# Visually distinguish visible tabs in List All Tabs menu
# [[Firefox/Projects/Eradicate Startup Dialogs]]
# Attach “create custom search” onto search form completion dropdowns (possibly with threshold, detect search fields, 3rd time etc)
# Improve session restore screen to support groups/windows better
# Move "Know your rights" {{bug|571584}} and Firefox update available {{bug|588227}} to home tab snippets
# Ctrl-tab should know about tab order instead of just moving left-to-right
# Clone tab history (and form/session data?) from parent tab when opening a new one
# Tooltips stick around and overlay other apps on OS X when switching apps

== Infrastructure (with no UI) ==
Projects we care about that have UX impact, but little to no UI.
# Bundle Flash with Firefox
# In-browser PDF display — PDFkit on Mac? http://code.google.com/p/firefox-mac-pdf/
# Detection of captive portals
# JägerMonkey for UI
# Resource Packages
# jemalloc support on Mac
# Smarter disk cache
# More performance data, memory usage data, CPU usage data, hang detection as part of system pings — what we can't measure, we can't improve
# SSL should support form restore too, possibly with timeout
# Reusable grouping API for tabs (so other extensions, e.g. VerticalTabs, can reuse Panorama groups), tabs need UUIDs.
# Gmail/GC + Netflix
# Reinstall experience: a way to ask if they want fresh settings or keep their old ones

== Research projects ==
Projects we need to get started early, since they need more data and/or design explorations.
# Combine URL and search bar: We should make common actions available in the location bar, and do some user testing to figure out what patterns people use while searching vs. entering URLs. Also figure out what the percentages are via metrics.
# Do user testing on various SSL/identity variants, see if there's a difference and whether we can help people understand it better when they want to.
# In-content preferences (including unifying customization/appearance/themes, eliminating unneeded windows), faster navigation, better grouping
# User test various progress indicator variations (perception of speed): Better indicator for how much of a page is downloaded, maybe even separate indicator for page vs resources on the page.
# Unify bookmarks/history/tabs and make the transition between them more seamless, browse + search UIs for these
# Better Customization UI, should be in-content, include appearance and toolbar customization in one.
# Ability to manage hundreds of tabs in low memory situations (serialization, freeze JS, etc)
# Look into network latency issues, prefetch, preload-on-hover, "optimize away the network when we can", etc
# Tablet UI
# Design and plan for "Actions" (include menu items in this, like Dietrich's extension?)
# New design for "Find text in page"
# Built-in translation: Capability of selecting text and translating it, offer to translate page when not in user's selected language
# Improved content authoring/editing: Provide a great, default UI for contentEditable: Everyone constructs their own UI on top of contentEditable at the moment, we should supply a good default implementation, like we do for video controls. Table editing in particular is bad ,the inner workings of contentEditable need some love too.
# Merge folders & tags
# "The Vault", a way to save/freeze content, save encrypted to Sync container, and have them follow you around (receipts, tickets, etc)
# Combine URL/search bar, support actions
# Multiuser support, logging in to your browser, sandboxed secure profiles
# Collecting people/locations/time, service discovery, navigable pages in the browser include meta-pages of location, people, etc.
# Global Undo: For closing tabs, closing windows, figure out what should and shouldn't be in the undo stack.
# Saving web pages in a way that doesn't suck: Receipts, offline reading (“read later”), Paolo has a related project here, MAF: http://maf.mozdev.org/
# New interface primitives for extensions: combine the multitude of hook-in points to a single interface.
# Unify plugins and extension listings, straighten out the language (add-ons)
# Volume per tab and/or some way to indicate "which tab is making noise"
# Sidebar tabs: A power-user interface that gives you better control of large number of open pages. Partial thumbnails, grouping, filtering. [http://limi.net/articles/reinventing-tabs-for-the-browser/ blog post #1], [http://limi.net/articles/tabs-and-the-mozilla-design-challenge/ blog post #2] (limi)
# History as a parallel timeline? Better indication in human terms and navigation of sites in history ([http://weizhou.wordpress.com/2008/07/07/prototype/ wei's sprint] [http://weizhoudesign.com/browserin2015.swf wei's video] [http://www.simile-widgets.org/timeline/ Simile Timeline] [http://www.slifelabs.com/ Slife]
# Sync my contacts across sites, let me use my Facebook people elsewhere, autocomplete people (with faces)
# Web page quick look: User-triggered way to get an idea of where a link will go, possibly show a preview or some information about where a link leads
# Vista/Win7 explorer-like interface for navigating favorites, get rid of URLs when displaying favorites

== Tool & process improvements ==
* community for design discussion?
* omnigraffle stencils for awpy
* new nighly build icon
* visualization tool for progress on a feature over time: treadmill
* HTML bugmail / new bugzilla theme

Extension Manager:Projects:Third Party Add-on Warnings

2011-03-08T01:52:16Z

Faaborg:

__NOTOC__
Current options for managing add-ons installed by third parties and system administrators are limited. We allow disabling but not uninstalling. We also currently do not provide adequate warning to users that new third-party provided add-ons have been installed.

* '''Module owner:''' Mossop
* '''Available reviewers:''' Mossop, Unfocused, rs

=Status=

* AVAILABLE
* {{bug|476430}}

=Goals=

* Make users aware when new add-ons have been installed that they may not know about
** Users should be able to opt out of such add-ons before the add-on's code haa a chance to run
* Allow uninstalling third party add-ons in some way
** Consider how to allow "reinstalling"

=Non-Goals=

* Support removing other applications on the system from within Firefox

=Design=
[http://people.mozilla.com/~faaborg/files/firefox4Mockups/userAddonSelection/addOnLocalInstall-i2.png Design mockup]

=Milestones=

# Initial designs
# Specification
# Implementation
# Testing
# Release

Extension Manager:Projects:Third Party Add-on Warnings

2011-03-08T00:15:43Z

Faaborg:

__NOTOC__
Current options for managing add-ons installed by third parties and system administrators are limited. We allow disabling but not uninstalling. We also currently do not provide adequate warning to users that new third-party provided add-ons have been installed.

* '''Module owner:''' Mossop
* '''Available reviewers:''' Mossop, Unfocused, rs

=Status=

* AVAILABLE
* {{bug|476430}}

=Goals=

* Make users aware when new add-ons have been installed that they may not know about
** Users should be able to opt out of such add-ons before the add-on's code haa a chance to run
* Allow uninstalling third party add-ons in some way
** Consider how to allow "reinstalling"

=Non-Goals=

* Support removing other applications on the system from within Firefox

=Design=
[http://people.mozilla.com/~faaborg/files/firefox4Mockups/userAddonSelection/addOnLocalInstall-i1.png Design mockup]

=Milestones=

# Initial designs
# Specification
# Implementation
# Testing
# Release

Extension Manager:Projects:Confirm on Upgrade

2011-03-08T00:13:31Z

Faaborg:

__NOTOC__
When upgrading to a new major version of Firefox we should show users a list of installed extensions and confirm that they still want to keep all of them enabled. This would replace the existing compatibility wizard.

* '''Module owner:''' Mossop
* '''Available reviewers:''' Mossop, Unfocused, rs

=Status=

* AVAILABLE
* {{bug|596343}}

=Goals=

* Do compatibility and update checks for all installed extensions
* Show users a list of installed extensions
* Allow disabling extensions before startup

=Non-Goals=

=Design=
[http://areweprettyyet.com/5/userAddOnSelection/ Design mockup]

=Milestones=

# Initial designs
# Specification
# Implementation
# Testing
# Release

File:Bracket.png

2011-02-28T11:32:23Z

Faaborg:

Bugzilla:Pretty

2011-02-28T11:30:08Z

Faaborg:

__NOTOC__
=Make Bugzilla Pretty=

As of Bugzilla 4.0, most of Bugzilla's major ''usability'' problems will have been addressed. There are still some rough edges, but for the most part, we've improved usability to the point where it's much less of a problem than it used to be, and we don't have to worry about it as much.

Now it's time to make Bugzilla '''look nice'''. However, we are not experts in this area. So, we are turning to '''you'''.

This is the "Make Bugzilla Pretty Contest". We are looking for designers to submit images of redesigned Bugzilla pages. If we choose your design, you will get:

* Prominent credits in the Bugzilla Release Notes, with a link to your web page.
* A link in the Bugzilla 5.0 release announcement on the bugzilla.org website.
* A case study for your web site that we can work with you to help create.

Most importantly, you will be able to say that you were the person or company that ''made Bugzilla pretty''--a career-changing (and very marketable) accomplishment, at the least.

==How To Enter==

To enter, all you have to do is submit an image that is a redesign of this exact bug view page:

[[File:Ugly bug.png|thumb|none]]

There is also an [https://docs.google.com/drawings/edit?id=1A7drQ16X5lr_STUSlqpX8eAviDXUb2HfuCAAx5tAxTA&hl=en annotated version of the image] that shows which pieces are optional or not shown to all users.

You don't need to submit a working HTML page, and in fact we don't want one--we just want an image.

To make your submission, just create a new sub-section of the "Entries" section below. You can see a sample entry there. If you have any trouble, you can also just email your submission to mkanat@bugzilla.org.

The deadline for submission is '''February 28, 2011'''.

You may want to start with something simpler than the bug view page, so you can first submit a redesign of the front page, if you want. The front page looks like:

[[File:Bugzilla 4.1 Index.png|thumb|none]]

==The Rules==

* You must preserve all of the functionality of the current bug view page. Mostly, this means that you can't remove any field or link from the current image above.
* You may move anything on the page around to anywhere, including hiding things (though be wary of adding extra clicks to the page).
* This is not a usability contest, only a contest for how ''nice'' the resulting user interface looks. We have already done heavy usability work on Bugzilla--you are certainly welcome to improve visual usability aspects, but remember that other significant usability changes should happen as part of a separate project, not here.
* The winner's design will become the official design of Bugzilla 5.0, although we may make modifications to it as we implement it. We may choose to only use part of the winning design, and we may choose to combine multiple designs (in which case all designs used will be considered to have "won").
* The judges are the Bugzilla Reviewers, with the Bugzilla UI Lead (Guy Pyrzak) having veto power and two votes.
* We do not have to pick ''any'' of the entries. If we don't like any of the entries enough to make them our official design, then we simply won't choose any of them.

= Entries =

== Sample Entry ==

Here's a little description of what I did, some of my thoughts about this design, and who I am.

From [http://www.everythingsolved.com/ Everything Solved, Inc.]

Contact us using the information at http://www.everythingsolved.com/contact/.

[[Image:Ugly bug-grayscale.png|thumb|none]]

== David Elliott ==

[[Image:Bz-david-elliott-index.jpg|thumb|none]]

== Nisse Nordin ==

[[Image:Bugzilla-pretty-nuss.png|thumb|none]]

N.b. this was made quite a while ago and is by no means a finished entry (the entry do not comply to the rules), but I chose to add it anyway knowing I probably not finish it in the time frame due to lack of time. I hope it shows parts of the essence of my idea. [[User:Nuss|Nuss]] 15:25, 27 January 2011 (PST)

= Long Duong =
[[File:Bugzilla-Intro-Design-lduong.jpg|thumb|none]] [[File:Bugzilla-Design-lduong.jpg|thumb|none]]

Worked on it since late November. Majority of the design work is in place, but fine details aren't quite there yet. Enhancements can be made as you go along. If you have any questions, I can be contacted through here - http://lduong.com/contact/

[[File:BugZilla-Intro-Design-lduong-V3.jpg|thumb|none]] [[File:Bugzilla-Design-lduong-V3.jpg|thumb|none]]

Here's another design with much emphasis on details. Forms are the same from previous submission, but added some visual cues to improve recognition. This layout is also designed to adapt whatever brand you may have.

= Shibu Abraham =

{| width="200" border="0" align="center" cellpadding="1" cellspacing="1"
|-
| [[Image:Bz home.png|thumb|none]]
| [[Image:Bz home2.png|thumb|none]]
| [[Image:Bz home3.png|thumb|none]]
|-
| [[Image:Bz home4.png|thumb|none]]
| [[Image:Bz home5.png|thumb|none]]
| [[Image:Bz home6.png|thumb|none]]
|}

 

{| width="200" border="0" align="center" cellpadding="1" cellspacing="1"
|-
| [[Image:Bz bug1.png|thumb|none]]
| [[Image:Bz bug2.png|thumb|none]]
| [[Image:Bz bug3.png|thumb|none]]
|-
| [[Image:Bz bug4.png|thumb|none]]
| [[Image:Bz buglist.png|thumb|none]]
|}

 Designers Comments: There isn't too much of a difference between the options provided, just a little rearranging and some fun while at it. Personally, for the bug page, my most preferred design is Bz_Bug3.png as I believe it puts most of the necessary input right in front of the user in a meaningful way and the screen does not look so busy when Advanced fields are hidden. I however had some concerns over future bugzilla iterations and the flexibility of this layout when new fields are added.

= Martijn Ras =
[[Image:Bugzilla-Martijn Ras-20110207-1.png|thumb|none]]
[[Image:Bugzilla-Martijn Ras-20110207-2.png|thumb|none]]
[[Image:Bugzilla-Martijn Ras-20110207-3.png|thumb|none]]
[[Image:Bugzilla-Martijn Ras-20110207-4.png|thumb|none]]

The idea is to make a block with the most important options, followed by the comments. In case javascript is available all other blocks of information can be show in a series of tabs, otherwise they simple move to the bottom of the page. A side-thought while working on this was to add a button to collapse all but the topmost comment or even add a preference to do so by default.

= Jonathan Wilde =

[[File:JWilde-BugzillaPretty-Bug-27-2-2011.png|thumb|none]]

This design's goals are pretty simple: to push lots of information up to the top of the page and to be lightweight.

The fields at the top of the page are compressed using a Drupal-style tabbed container. The text below the title of each tab provides a summary of the values of the fields in the tab. The sections not rendered in the mockup above are as follows:

* Visibility - The settings for which groups can view the bug.
* Extras - Flags, custom fields, whiteboard, bug blocking information, attachments.
* Time tracking - The estimate and time spent table.

The design is intended to be both visually lightweight and, after implementation, lightweight in terms of page size. The design should be easily implementable using CSS3's gradients, border-radius, text-shadow, and box-shadow for the special-effects. It will probably still look decent in browsers where these features aren't available.

The mockup is typeset in Nobile, which is available for CSS @font-face embedding. While I am fond of that typeface, Verdana can be easily substituted to cut down on loading time.

Implementation of the design entails a few background images for the faint texture on the search box and gradient backgrounds, but it can still hold together with plain CSS3 gradients instead. The gear, search, and down-triangle icons--which can't easily be reproduced with special characters in HTML can be easily sprited into a single, small image.

If you have any questions about the design, feel free to contact me. My email address is in the bottom right corners of the design note images below.

'''Note #1: Extraneous Element Hiding'''
[[File:JWilde-BugzillaPretty-HidingDetail-27-2-2011.png|thumb|none]]

This note shows how to simplify the design and reduce clutter even more.

'''Note #2: Navigation Bar Interaction'''
[[File:JWilde-BugzillaPretty-NavBar-27-2-2011.png|thumb|none]]

This note shows the interactive aspects of interaction with the navigation bar.

= Alex Faaborg =

[http://mzl.la/bracketTheme http://mzl.la/bracketTheme]

Design Principles:
* Clean stark lines
* Data over metadata
* Color represents value
* Spatially organized around the core journalistic questions

The theme [bracket] uses crisp, stark lines to organize content. To help quickly convey information, color is used only for the properties that have a value (in transition, positive, negative). Also, to help people quickly parse the page to answer questions, properties are spatially organized based on some of the core journalistic questions (what / who / when / how). Visually ones sees a series of colorful blocks link together, as people collaborate over time. The comment thread becomes sort of a software development DNA. The design focuses on data over metadata, and maintains a feeling of minimalism while still conveying a massive amount of information.

[https://bug607829.bugzilla.mozilla.org/attachment.cgi?id=515285 Example of how this design works with HTML email]

WeeklyUpdates/2010-11-15

2010-11-13T21:16:27Z

Faaborg: /* Speakers */

[[WeeklyUpdates/2010-11-08|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-22|next week »]]

= Video for today's meeting =

<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-15.ogg" type="video/ogg; codecs="theora, vorbis"" /></video>

= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =

= Upcoming Events =
'''This Week'''

'''Monday, 15 November'''

'''Tuesday, 16 November'''

'''Wednesday, 17 November'''

'''Thursday, 18 November'''

'''Friday, 19 November'''

'''Next Week'''

= Product Status Updates =

== Firefox 4 ==

== Firefox 3.6 ==

== Mobile Firefox ==

== Thunderbird ==
* We are preparing a 3.3a1 release and are looking for some help on [http://perso.hirlimann.net/~ludo/blog/archives/2010/11/33a1-approching-looking-for-some-help-fr.html the testing side]

== Older Branch Work ==

== Drumbeat ==

= Speakers =

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.

{| class="fullwidth-table"
|-
! Title
! Presenter
! Topic
! Media
! More Details
|-
| Your Title Here
| Your Name Here
| What are you going to talk about?
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Tracking Polish Bugs in Firefox 4
| Alex Faaborg
| Now that all of the major features have landed for Firefox 4, we are shifting our focus towards small polish bugs. We want Firefox 4 to looks and feel like a finely crafted product.
| [http://people.mozilla.com/~faaborg/files/firefox4Mockups/polishMainWindow-i1/polishMainWindow-i1.htm Main Window]

[http://people.mozilla.com/~faaborg/files/firefox4Mockups/polishFirefoxMenu-i1/polishFirefoxMenu-i1.htm Menus]
| Learn more about [https://github.com/toolness/bugzilla-dashboard/blob/master/js/bugzilla.js Atul's buzilla.js] which was used to provide the live data in these mockups. Also thanks go to Gerv for building the API we're accessing!
|}

= Status Updates By Team =

== Firefox ==

== Platform ==

== Messaging ==

== Mobile ==

== IT ==

== Release Engineering ==

== QA ==

;Test Execution

;WebQA

;QA Community

;Test Dev

== Automation & Tools ==

== Security ==

== Engagement ==

'''PR'''

'''Events'''

'''Creative Team'''

'''Community Marketing'''

== Support ==

== Metrics ==

== Evangelism ==

== Labs ==

== Developer Tools ==

== Add-ons ==

== Webdev ==

== L10n ==

= Introducing New Hires =
* William Reynolds - User Engagement
* Cameron McCormack - Web standards, platform work of some variety

= Foundation Updates =

= Roundtable =

Security/Reviews/Firefox4

2010-10-27T21:41:45Z

Faaborg: /* Front End */

== Pending Reviews ==
Please complete the [[Security/ReviewTemplate|Security Review Template]] for your feature before scheduling your review. For small features or changes we will likely group several together into one session. Immediately after the Platform meeting often works well for that. For larger topics we should schedule them for a longer timeslot. Please add that time in the date column (use Mountain View time (Pacific)).

The "who" is responsible for filling out the review template and scheduling the review. Please email secteam at mozilla dot com when reviews are scheduled and if times change. Please also email any other folks in the "interested" column. If not immediately after a [[Platform#Meetings | Platform meeting]], dial in will be 650-903-0800 x92 Conf# 215 (US/INTL). Default IRC backchannel is #planning.

Features that get cut from Firefox 4 should be moved to the [[Security/Reviews/Firefox4.next|Firefox4.next]] page rather than simply deleted.

<onlyinclude>
=== Platform ===
All times are Mountain View local time (Pacific)
{| border="1"
! feature || who || review date || interested
|-
|[[Security/Reviews/Firefox4/AudioAPI_Security_Review|Audio API]] ||David Humphrey || ||
|-
|[[Security/Reviews/Firefox4/CSS_features_Security_Review|CSS calc(), CSS transitions, and CSS :-moz-any()]] ||dbaron || ||
|-
|[[Security/Reviews/Firefox4/CSS_Element_Security_Review|CSS -moz-element/document.mozSetImageElement]] ||mstange || ||
|-
|[[Security/Reviews/Firefox4/moz-font-feature-opentype_Security_Review|CSS -moz-font-feature-opentype]] ||jdagget/jkew || ||
|-
|[[Security/Reviews/Firefox4/harfbuzz_Security_Review|harfbuzz]] ||jdagget/jkew || ||
|-
|[[Security/Reviews/Firefox4/HistoryState_Security_Review|History pushState/replaceState]] ||jlebar || ||
|-
|[[Security/Reviews/Firefox4/HTML5_Parser_Security_Review|HTML5 Parser]] ||hsivonen || ||
|-
|[[Security/Reviews/Firefox4/Jaegermonkey_Security_Review|Jägermonkey]] || || ||
|-
|[[Security/Reviews/Firefox4/JS_Animation_Scheduling_Security_Review|JS animation scheduling]] ||bzbarsky || ||
|-
|[[Security/Reviews/Firefox4/JS-ctypes|JS-ctypes]] ||dwitte || ||
|-
|[[Security/Reviews/Firefox4/JS_ES5_Security_Review|JS ES5]] || || ||
|-
|[[Security/Reviews/Firefox4/JS_Proxies_Security_Review|JS Proxies]] || || ||
|-
|[[Security/Reviews/Firefox4/JS_Compartments_Security_Review|JS Compartments]] || || ||
|-
|[[Security/Reviews/Firefox4/ByteArray_Security_Review|JS/WebGL byte arrays]] || || ||
|-
| || || ||
|-
| || || ||
|-
|[[Security/Reviews/Firefox4/Media_Buffer_Security_Review|Media Buffer API]] || || ||
|-
|[[Security/Reviews/Firefox4/DPI_Security_Review|New DPI System?]] ||roc || ||
|-
|[[Security/Reviews/Firefox4/SVG_as_IMG_Security_Review|SVG as IMG/background]] ||dholbert || ||
|-
|[[Security/Reviews/Firefox4/TabModal_Dialogs_Security_Review|Tab Modal dialogs]] ||dolske || ||
|-
|[[Security/Reviews/Firefox4/TouchEvents_Security_Review|Touch Events]] ||felipe || ||
|-
|[[Security/Reviews/Firefox4/WebGL_Security_Review|WebGL]] ||vlad || ||
|-
|[[Security/Reviews/Firefox4/ANGLE_Security_Review|ANGLE]] ||vlad || ||
|-
|[[Security/Reviews/Firefox4/WebM_Security_Review|WebM]] ||roc? || ||
|-
|[[Security/Reviews/Firefox4/WebM3D_Security_Review|WebM 3D]] ||Matthew Gregan || ||
|-
|[[Security/Reviews/Firefox4/WebSocket_Security_Review|Web Sockets]] ||Fernando?, Olly || ||
|-
|[[Security/Reviews/Firefox4/XHR.mozResponseArrayBuffer_Security_Review|XHR.mozResponseArrayBuffer]] ||vlad || ||
|-
|}

=== Front End ===
{| border="1"
! feature || who || review date || interested
|-
|about:addons ||mossop || ||
|-
|Add-on UI ||dietrich || ||
|-
|App Tabs ||zpao || || dao, faaborg
|-
|Auth door-hangers ||dolske || || dao, faaborg
|-
|Doorhanger notifications ||gavin || || faaborg
|-
|Download mgr improvements/MIME type defaults ||limi || ||
|-
|Jetpack modules||dietrich || ||
|-
|New Start Page ||mak || ||
|-
|New Theme (code/bindings) ||gavin || ||
|-
|Places API redesign ||marco || ||
|-
|Port satchel to js ||dolske || ||
|-
|Cascade Session Restore ||zpao || ||
|-
|Deferred Session Restore ||zpao || ||
|-
|Sync || || || faaborg
|-
|Tab Panorama ||aza || ||
|-
|Update billboard changes ||rs || ||
|-
|Update: Post-update actions ||rs || ||
|-
| || || ||
|-
|}
</onlyinclude>

== Completed Reviews ==
Please add a link to the review comments in the appropriate column. There is a section in the template that can be used for this, but it's fine to have the comments in a separate document as long as it's linked to here.

=== Platform ===
{| border="1"
! feature || who || date || review comments
|-
|[[Security/Reviews/Firefox4/Desktop_Notifications_Security_Review|Desktop Notifications]] ||dougt ||2010-10-18 || [[Security/Reviews/Firefox4/Desktop_Notifications_Security_Review#Review_comments|comments]]
|-
|[[Security/Reviews/Firefox4/IndexedDB_Security_Review|IndexedDB]] || bent ||| 2010-09-30 || [[Security/Reviews/Firefox4/IndexedDB_Security_Review#Review_comments|comments]]
|-
|[[Security/Reviews/Firefox4/mozGetAsFile_Security_Review|canvas.mozGetAsFile]] ||khuey ||2010-09-29 ||
|-
|[[Security/Reviews/Firefox4/FileAPI_Security_Review|File API changes]] ||sicking ||2010-09-29 ||
|-
|[[Security/Reviews/Firefox4/FormData_Security_Review|FormData]] ||sicking ||2010-09-29 ||
|-
|[[Security/Reviews/Firefox4/HTML5_Forms_Security_Review|HTML5 Forms]] ||Mounir ||2010-09-29 ||[[Security/Reviews/Firefox4/HTML5_Forms_Security_Review#Review_comments|comments]]
|-
|Cookie changes ||dwitte ||2010-09-22 || [[Security/Reviews/Firefox4/Cookie_Security_Review|comments]]
|-
|[[Firefox3.1/SMIL_Security_Review|SVG Animation (SMIL)]] ||dholbert || 2008-09-03 || [[Firefox3.1/SMIL_Security_Review#Review_comments|comments]]
|-
|}

=== Front End ===
{| border="1"
! feature || who || date || review comments
|-
|[[Security/Reviews/Firefox4/Web_Console_Security_Review|Web console]] || kdangoor ||2010-10-05 ||[[Security/Reviews/Firefox4/Web_Console_Security_Review#Review_comments|comments]]
|-
| || || ||
|-
|}

File:Beta feedback i4.png

2010-06-02T22:53:02Z

Faaborg:

File:Beta feedback i3.png

2010-06-02T18:59:41Z

Faaborg:

Firefox/Projects/SiteIdentity

2010-03-31T01:22:02Z

Faaborg: Created page with '= Pitch = = Goals = * Reduce the current amount of redundancy in the UI * Provide the ability to display persistent indicators (like the privilege to access the user's geo loca…'

= Pitch =

= Goals =
* Reduce the current amount of redundancy in the UI
* Provide the ability to display persistent indicators (like the privilege to
access the user's geo location)
* Integrate with the new panel-based notification system
* Present a more obvious absence of a cue in the event that there is no sll or
ev connection

= Non-Goals =

= Status =

* '''Tracking Bug:''' {{bug|556172}}

= Design =

= Timeline / Milestones =

= Delivery Requirements =

= Constraints =

= Dependencies =

= Testing =

= Related Projects =

Firefox/Projects/FirefoxButton

2010-03-31T01:19:53Z

Faaborg: Created page with '= Pitch = = Goals = * Integrate with the general interactive design of Windows Vista and 7 * Create a single locus of control for the entire application * Streamline how user's…'

= Pitch =

= Goals =
* Integrate with the general interactive design of Windows Vista and 7
* Create a single locus of control for the entire application
* Streamline how user's interact with Firefox's command stucture
* Reduce redundancy in the application

= Non-Goals =

= Status =

* '''Tracking Bug:''' {{bug|556174}}

= Design =
* Very first initial details here: [http://blog.mozilla.com/faaborg/2010/03/23/visualizing-usage-of-the-firefox-menu-bar/ http://blog.mozilla.com/faaborg/2010/03/23/visualizing-usage-of-the-firefox-menu-bar/]

= Timeline / Milestones =

= Delivery Requirements =

= Constraints =

= Dependencies =

= Testing =

= Related Projects =

Firefox/Projects

2010-03-31T01:15:41Z

Faaborg:

__NOTOC__
{| style="width: 100%" class="fullwidth-table sortable"
|-
| style="background:#efefef" width="25%" | '''Description'''
| style="background:#efefef" | '''Leader'''
| style="background:#efefef" | '''Goal'''
| style="background:#efefef" | '''ETA'''
| style="background:#efefef" | '''Status'''
|-
| [[Firefox/Projects/StartupPerformance|Startup Time Improvements]]
| Dietrich
| Reduce warm and cold startup of Firefox, Fennec
|
| {{:Firefox/Projects/StartupPerformance#Status}}
|-
| [[Firefox/Goals/2010Q1/IO_Reduction|I/O Reduction]]
| sdwilsh
| > 50% reduction of main thread I/O
|
| {{:Firefox/Goals/2010Q1/IO Reduction}}
|-
| [[Firefox/Projects/OOPP|Out-Of-Process Plugins]]
|
| Ship out of process plugins and associated UI pieces to Windows users
|
| {{:Firefox/Projects/OOPP}}
|-
| [[Firefox/Projects/E10S Scope Investigation]]
| dolske
| Document scope of work for process separation in Firefox & port one feature as an experiment
|
| {{:Firefox/Projects/E10S_Scope_Investigation}}
|-
| [[Firefox/Projects/New Theme|New Theme]]
| shorlander, gavin
| Implement alpha quality Windows implementation of refactored browser.js & new theme for Windows on trunk or as XPI
|
| IN FLIGHT
|-
| [[Firefox/Projects/Weave|Weave]]
| zpao
| Improve Weave extension & prepare for integration
| Ongoing
| {{:Firefox/Projects/Weave}}
|-
| [[Firefox/Projects/Extension_Manager_Redesign|Addons Manager UI Redesign]]
| Boriss
| Design and implement unified web services & customization interface on trunk
| TBD
| {{:Firefox/Projects/Extension Manager Redesign|/Extension Manager Redesign}}
|-
| [[Firefox/Projects/Extension Manager API|Extension Manager API Rewrite]]
| Mossop
| {{#lst:Firefox/Projects/Extension Manager API|overview}}
| April
| {{:Firefox/Projects/Extension Manager API|Extension Manager API Rewrite}}
|-
| [[Firefox/Projects/Console|Debug console for web pages]]
| robc
| Implement alpha quality integrated developer tool set on trunk
|
| {{:Firefox/Projects/Console}}
|-
| [[Firefox/Projects/Inspector|Web page inspector]]
| robc
| Implement alpha quality integrated developer tool set on trunk
| Late March
| {{:Firefox/Projects/Inspector}}
|-
| [[Firefox/Projects/Multitouch|Multitouch]]
| felipe
| Bring multitouch support to the web
|
| Working on user experience features and moving ahead with experimental Events API support
|-
| [[Firefox/Projects/Jetpack|Jetpack on Trunk]]
| adw
| Ensure that Jetpack extensions can be developed for production use on trunk Firefox.
|
| {{:Firefox/Projects/Jetpack}}
|-
| [[Firefox/Projects/Resource Packages|Resource Packages]]
| limi
| Backwards compatible way of serving up multiple resources in a streamable file
| ON RUNWAY: Proposal finalized
| Next steps: Work with jlebar/vlad to get the project started
|-
| [[Firefox/Projects/Home Tab|Home Tab and App Tabs]]
| faaborg
| Investigate a full window, client side, browse-based UI to serve as the user's home on the Web, and the ability to create chromeless app tabs.
| First round of mockups complete: 10/23
| Just getting started
|-
| [[Firefox/Projects/Tab_Matches_in_Awesomebar|Tab Matches In Awesomebar]]
| Unfocused
| Make it possible to switch tabs using the AwesomeBar
| March 2009
| Landed!
|-
| [[Firefox/Projects/PlacesQueryAPIRedesign | Places Query API Redesign]]
| ddahl
| Simple, elegant Places Query API that is focused on 3.7 Places work
| TBD
| Patches up and have review + for the Jetpack implementation. bug 522572 (Sync impl.) / Async in progress as well bug 534983, Filed bug 543888 to craft in a skeleton a more comprehensive API for the async patch
|-
| [[Firefox/Projects/Async Places containers|Async Places containers]]
| adw
| Perf: non-blocking Places operations
| TBD
| {{:Firefox/Projects/Async_Places_containers}}
|-
| [[Firefox/Projects/Action based on update xml after app update|Action based on update xml after app update]]
| rs
| Perform action after update based on update xml attribute.
| Client side 03/10, AUS 04/10
| IN FLIGHT - requested strings - last client side patch submitted for review - tests almost complete
|-
| [[Firefox/Projects/Simplify Update UI size for billboard and l10n|Simplify Update UI size for billboard and l10n]]
| rs
| Simplify verification of the billboard for all locales and all platforms and make the UI look *better*.
| 03/11/10 (on trunk) 3/31/10 (1.9.1 and 1.9.2)
| LANDED (on trunk)
|-
| [[Firefox/Projects/Download manager improvements|Improve Download Manager + MIME type defaults]]
| limi
| Move download manager to panel, coordinated with new theme, improve default behaviors.
|
| ON RUNWAY: Blog post published, filing bugs and bootstrapping next
|-
| [[Firefox/Projects/FTS_and_Awesomebar|Full Text Search and Awesomebar]]
| adw
| Improve performance of the awesomebar by using full text search.
|
| TAKING OFF
|-
| [[Firefox/Projects/IndexedDB/|IndexedDB]]
| sdwilsh
| Implement the W3C IndexedDB specification.
|
| {{:Firefox/Projects/IndexedDB/}}
|}

= Inactive Projects (need to finish) =

{| class="fullwidth-table sortable"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Participants'''
| '''Goal'''
| '''ETA'''
| '''Target'''
| '''Status'''
|-
| [[Labs/Test Pilot Planning|Test Pilot]]
| jinghua
|
| Add Test Pilot check-box (opt-in) in Firefox installer.
| Test Pilot 1.0 release in mid Q2, server upgrade in mid Q2
| Starting with 3.7
| 1.0 beta will be released by March, feedback coming in.
|-
| [[Firefox/Projects/Connect|Connect]]
| dmills (for now)
|
| Design and implement chrome to sign-in/out of sites, as well as manage accounts and do one-click registration.
| TBD
| TBD
| {{:Firefox/Projects/Connect#Status}}
|-
| [[Firefox/Projects/Preferences UI|Preferences UI]]
| faaborg
|
| Refresh and streamline the Firefox preferences window
| First round of mockups complete: 10/23
| Starting with 3.7
| Just getting started
|-
| [[Firefox/Projects/Places UI|Places UI]]
| faaborg
| 
| Investigate changes to the places UI for 3.7 and 4.0, focusing on mixing search + browse operations, and leveraging the content area.
| Breaking UI apart into separate bugs: 10/23
| Starting with 3.7
| Mockups complete, feedback coming in.
|-
| [[Firefox/Projects/Doorhanger_notifications|Doorhanger notifications]]
| dolske
| faaborg (UI), ashughes (QA)
| get'r'dun
| As early in 3.7 as possible
| TBD
|
|-
| [[Firefox/Projects/Binding for untrusted text in security dialogs|Binding for untrusted text in security dialogs]]
| Unfocused
| Jesse
| Provide a common way for security dialogs to include untrusted text without compromising the rest of the dialog
| TBD
| 1.9.3
| Gathering info, planning
|-
| [[Firefox/Projects/PersonalIdentity|Personal Identity]]
| ragavan (lead) faaborg (Firefox)
| thunder, aza, messina
| Explore integrating personal identity management into Firefox
|
|
|
|-
| [[Firefox/Projects/Herdict|Herdict]]
| atul (lead) boriss (Firefox)
| faaborg
| Explore integrating the functionality of [http://www.herdict.org Herdict] with Firefox's network error page.
|
|
|
|-
| Print preview in a separate window
| rflint
|
| Remove the fragile XBL binding and create a separate XUL document
|
| 1.9.3
|
|-
| [[Firefox/Projects/FirefoxButton|Firefox Button]]
| faaborg
|
| Create a single high contrast control in the title bar to integrate with the interactive design of Windows Vista and 7
|
|
|
|-
| [[Firefox/Projects/SiteIdentity|Site Identity]]
| faaborg
|
| Refresh how Firefox surfaces the identity of a site to integrate with our new notification system, reduce redundancy, and allow for persistent indicators like geo location access.
|
|
|
|}

*[[Firefox/Projects/AcceleratedScrolling|Accelerated Scrolling]]
*[[Firefox/Projects/Multitouch Polish|Multitouch Polish]]
*[[Firefox/Projects/Eradicate Startup Dialogs|Eradicating Startup Dialogs]]
*[[Firefox/Projects/Network Error Pages|404 Error Pages]]
*[[Firefox/Projects/Unbreak RSS|Unbreak RSS]]

== Prioritized ==

* [[Firefox/Projects/Improve Mac installer|Improve Mac installer]]
*[[Firefox/Projects/System Extension Notification|System Extension Notification]]
*[[Firefox/Projects/StrandedUsers|Understand why we strand users on point releases]]
*[[Firefox/Projects/Always have option to Add Search|Always have option to Add Search]]
*[[Firefox/Projects/Add Search to Awesomebar|Add Search to Awesomebar]]
*[[Firefox/Projects/App-wide Database Vacuum|App-wide Database Vacuum]]
*[[Firefox/Projects/About:newtab|about:newtab]]
*[[Firefox/Projects/Improve Plugin Find and Install|Improve Plugin Find and Install]]
*[[Firefox/Projects/Visual Affordance for Tear Off Tabs|Visual Affordance for Tear Off Tabs]]
*[[Firefox/Projects/Control Tab|Control-Tab]]
*[[Firefox/Projects/Update hunspell|Update dictionaries]]
*[[Firefox/Projects/about:problems|about:problems]]
*[[Firefox/Projects/Automatic Recovery|Automatic Recovery]]
*[[Firefox/Projects/about:me|about:me (first-pass addon done, uplift approach still open)]]
*[[Firefox/Projects/Video Controls|Video Controls]]
*[[Firefox/Projects/Tab_animation|Tab & Menu item animation]]
*[[Firefox/Projects/Find_on_Page|Find on Page improvements]]

== Unprioritized ==

*[[Firefox/Projects/Jetpack Uplift Exploration|JetPack Uplift]]
*[[Firefox/Projects/PanelImprovements|Panel Improvements]]

= Additional Projects Ideas (Need more definition) =

*[[Firefox/Cleanup|Areas that need code cleanup or overhaul]]
*[[Firefox/Projects/App-wide Database Integrity Check|App-wide Database Integrity Check]]
*[[Firefox/Projects/Create a Places page thumbnail service|Create a Places page thumbnail service]]
*[[Firefox/Projects/Crowdsource Performance Data|Crowdsource Performance Data]]
*[[Firefox/Projects/Migration Component JS Porting|Migration Component JS Porting]]
*[[Firefox/Projects/ExperimentalPlacesSchema|Places Schema Redesign]]
*[[Firefox/Projects/View Source in Tab|View Source in Tab]]

= Completed Projects / Archive =

*[[Firefox/Projects/Places async expiration|Places Async Expiration]] (LANDED 1.9.3)
*[[Firefox/Projects/WindowsCE|Firefox WinCE]] (minor stuff still to do)
*[[Firefox/Projects/Places Vacuum]] (LANDED 1.9.2)
*[[Firefox/Projects/Perception of Performance|Perception of Performance]] (Investigation, see wiki page for follow up projects)
*[[Firefox/Projects/Async Annotation Protocol Handler|Asynchronous Annotation Protocol Handler]] (LANDED 1.9.1)
*[[Firefox/Projects/Places Expiration Performance Refactoring|Places Expiration Performance Refactoring]] (LANDED 1.9.1)
*[[Firefox/Projects/Bookmark Dialog Focus|Bookmark Dialog Focus]] (LANDED 1.9.1)
*[[Firefox/Projects/Restore Visible Tabs First|Restore Visible Tabs First]] (LANDED 1.9.1)
*[[Firefox/Projects/Privacy Prefpane Refresh|Privacy Prefpane Refresh]] (LANDED 1.9.1)
*[[Firefox/Projects/Clear Recent History by Time Range|Clear Recent History by Time Range]] (COMPLETED WITH NOTES)
*[[Firefox/Projects/Undo Close Window|Undo Close Window]] (LANDED 1.9.1)
*[[Firefox/Projects/Windows Theme Polish|Windows Theme Polish]] (LANDED 1.9.1)
*[[Firefox/Projects/Focus Ring Cleanup|Focus Ring Cleanup]] (LANDED 1.9.1)
*[[Firefox/Projects/Places DB Creation Scripts|Places DB Creation Scripts]] (COMPLETED)
*[[Firefox/Projects/Asynchronous Location Bar|Asynchronous Location Bar]] (LANDED 1.9.2)
*[[Firefox/Projects/Awesomeformcomplete|Form Awesomecomplete]] (LANDED 1.9.2)
*Focus rewrite (LANDED, NO WIKI PAGE)
* [[Firefox/Projects/Animation priorities|Animation priorities]] (became two child-sprints: [[Firefox/Projects/Tab_animation|Tab & Menu item animation]] and [[Firefox/Projects/Find_on_Page|Find on Page improvements]])
* [[Firefox/Projects/about:support|about:support]] (LANDED 1.9.2)
* [[Firefox/Projects/Plugin Update Referrals|Plugin Update Referrals]] (LANDED 1.9.2)
* [[Firefox/Projects/Personas Uplift Exploration|Personas Uplift Exploration]] (LANDED 1.9.2)
* [[Firefox/Projects/Reduce Places Views Overhead|Reduce Places Views Overhead]] (LANDED 1.9.2)
* [[Firefox/Projects/Per Tab Network Prioritization|Per Tab Network Prioritization]] (LANDED 1.9.2)

= Template =

(Mostly) [[Firefox/Projects/Template|Blank Template]] for new projects.

= All pages =
[[Special:PrefixIndex/{{PAGENAME}}/| All subpages of {{PAGENAME}}]]
(most are described on this page).

XUL:Panel Improvements

2010-03-24T21:37:07Z

Faaborg:

==Panel Improvements==

Currently, three types of floating popups are supprted, menupopups, panels and tooltips. Menupopups and tooltips have a specific purpose and isn't part of the descriptions below. Assume they work as normal.

Panels have a number of uses. Currently, they are intended as temporary floating popups to interact with a few controls and then it goes away. The user isn't expected to interact with the rest of the application until they are finished with the panel. The panel goes away if the user presses Escape or if the user clicks outside the panel.

The 'noautohide' feature provides a somewhat different purpose. When enabled, by setting 'noautohide' to true, it makes the panel more permanent. It only disappears when the application requests it by hiding the panel via script. The application could provide a close or cancel button in the panel that does this.

A window is distinct from a panel. A window participates in normal window ordering with other windows and other applications. Clicking on a window raises it to the front. In addition, a window appears on the taskbar, the list that appears on Alt+Tab and so on. A panel, on the other hand in expected to be a helper subwindow for another window. It does not appear in any operating system window lists such as the taskbar. Normally, a panel will float above the main window.

The idea here is to improve panels with additional features found in other typical application.

Desired behaviours of panels:

;Close on outside click/escape key: When clicking outside of a panel, or pressing the Escape key, the panel will be closed. This is currently controlled via the noautohide attribute, which can be set to either true or false. The default value is false, which makes the panel close in this way. If true, the panel will only be closed if a call to hidePopup is made.
:This feature is already implemented.

;Titlebar: By default panels, do not have a titlebar. Support is desired for both normal size and thin titlebars. When a titlebar is present, the panel can be moved around by dragging the titlebar. The titlebar can optionally have a label. This is possible via a new attribute titlebar which can be set to false (the default), 'normal' for a normal titlebar or 'thin' for a thin titlebar. The titlebar attribute has no effect unless the noautohide attribute is set to true.

:See [https://bugzilla.mozilla.org/show_bug.cgi?id=552982 bug 552982] Displaying a titlebar is quite simple, but complications arise due to the manner in which views and widgets are positioned that cause coordinates to be calculated incorrectly and the popup to jump about the screen.

;Close button: A close button, off by default, to close the popup. A new attribute, closebutton, set to either true or false. Has no effect if the titlebar attribute isn't set to 'normal' or 'thin'.
:One potential complexity here is that on Mac, the window close button is implemented via two callbacks, one to ask to close and the other upon closing. This means that the manner in which popuphiding and popuphidden events need to fire may need to be changed to accomidate this.

;Dockable: A dock button on the titlebar to dock the panel into the main window. It would appear as, for example, a sidebar. Events would be needed when a panel switches between these states to update any UI that might be different. For instance, while a titlebar might appear while docked, it won't be a native titlebar, although some platforms may be able to render it as such. In the future, drag and drop of panels to dock them may be an option. A dockbutton attribute would put a button on the titlebar to dock and undock the panel. The attribute would have no effect if a titlebar wasn't present. An API should exist to dock and undock the panel; this would ideally work even if the button wasn't present.
:Docking is pretty simple, but implementing docked titlebar UI and a dock button on the undocked panel titlebar is more difficult.

;Moves with its parent: A panel can optionally maintain its position relative to its parent window, when the parent moves. This also implies that when the main window is minimized or restored, the panel minimizes or restores as well. Currently, this behaviour is implied when noautohide is set to true, but it would be better if this would independently adjustable. A new attribute dependent can be set to true or false, where false is the default.
:This feature is already implemented but should have a separate attribute to control it.

;Window level: Control over the window level of the panel. Three levels are desired, a panel which floats above all windows (including those of other applications), a panel which floats above only its parent main window, and a panel that participates in the normal window ordering. The 'level' attribute currently exists to control this, set to either 'top' or 'parent'. The default value is platform specific.
:The 'parent' and 'top' levels are already implemented.

;Only visible when main window active: The floating panel is only visible while the main window is frontmost. If another window is made active, it disappears. It reappears when the window is made frontmost again. It may be desirable to have this only disappear for any window of the same application or of a certain type.

;Independently focusable: The panel can be raised and focused independently of its parent main window. When this happens, the main window loses its active status (its titlebar becomes inactive). In some cases, it is only needed when certain elements in the panel become focused. For instance, a panel that contains a number of tool buttons and a textbox doesn't need to focus when the buttons are clicked, but only when the textbox is focused.
:How this should and can work relies on the underlying platform support.

;Background drag to move: The panel can be moved by dragging its background, whether there is a titlebar or not.
:This is fairly simple to implement and could be done simply by modifying WindowDraggingUtils.jsm.

;Arrow to the panel's anchor: For panels that are click outside to close, it is important to establish what target created the panel so that it can be accessed again. This target also serves in some ways as the panels "title" (although in more of a visual sense). For instance the current bookmark panel draws a half diamond to the star icon that creates it. The location of the half diamond needs to change based on where the panel is drawn. (moving the Firefox window to the far bottom of the screen and clicking the star demonstrates the current problem)
:This would involve implementing an event or callback when a popup is properly positioned and sized so that the arrow could be positioned to match.

; Fade in and fade out: not as visually noisy as the next feature, and works particularly well with partially transparent panels that are click outside to close.
; Animation showing panel's originator: Applications like iCal and google maps on the iPhone have a nice animation where the panel grows out of the thing that creates it, gets a little bit too large, and then springs back to the correct size. The result is an interface that feels very dynamic, bouncy and happy.
:For this and the previous feature, it would be ideal to have a means of setting animated effects when a popup is shown or hidden that work more automatically. This will need underlying work. Implementing this should also allow for an easier way to implement the Mac-style flash when a menu item is selected.
;Resizable: I'm conflicted on if we would actually turn this functionality on for some of the Firefox panels, but it is nonetheless probably an important feature of the general purpose widget. See {{bug|418864}} for all the hate mail on the bookmarks panel not being resizable.

==Planed Future Use of Panels in Firefox==
This is a tentative list of how we may use panels in Firefox's UI in the future:
* [currently in use] Bookmark properties
* [currently in use] Site identity
* Context menu on hyperlink > "Bookmark This Link"
* Context menu on bookmark > "Properties"
* Notification of site level events (password manager, geolocation, popups blocked, xpi install, etc.)
* Download progress (Limi is the main contact, he'll post details soon)
* Items on the extension bar, both jetpacks and converted traditional toolbars (Boriss is the main contact)
* Test pilot notifications from the extension bar, not technically part of Firefox but nonetheless a good example of extensions using panels for parts of their UI.

==Random Thoughts==
*Should we automatically set the transparency level if the panel is set to click outside to close? We are currently doing this for the custom panels in Firefox for bookmarking and identity on OS X, so that they appear light and ephemeral. We were going to do it on Windows as well but ran out of time right before shipping. (Linux is I believe still blocked by {{bug|408284}}
* We need to figure out the correct default appearance for each platform. The tool tip appearance being used on Vista wasn't entirely intentional. Should have shorlander think about this.
* Since extensions may commonly use panels for notification, should we have some type of standard "notification panel" that takes an icon, a message, and an action/actions and handles the layout to match all of the other instances of panel-based notification?

==Focus Issues in Panels==

A number of platform-specific focus related problems exist with panels. Child frames (<iframe> elements for example) should be avoided in panels, mainly due to the mouse not functioning in them on Windows. In addition, noautohide panels have significant problems on Linux. The following summarizes these issues with panels on each platform.

; Mac
* mouse and keys works ok in popup parent and child
* issue: mouse click propagates to parent button when <button type="panel"/>
* issue: if another window is currently focused, clicking somewhere in the panel raises, focuses and activates what was clicked immediately instead of just raising the window
; Windows
* mouse and keys works ok in popup parent
* mouse works ok in child
* issue: keys do not work in child
* issue: tabbing between parent popup parent and child causes the titlebar to flicker
* issue: sometimes, clicking the mouse in child causes the parent to flicker
* issue: sometimes, clicking the mouse in child just causes the previous focused element to be focused. Effectively, as if the popup was just being raised.
; Linux
* for normal panels, mouse and keys works ok in popup parent and child
* noautohide panels:
** issue: mouse works in popup parent and child, but focus is not set on the element
** issue: keys do not work in popup parent or child
** issue: parent window loses active state when the panel is opens
** issue: parent window loses active state when the mouse is pressed in popup parent or child
** if the parent window titlebar is clicked, the window becomes active and keys work ok in the popup parent and child again, but a mouse click will cause the active state to be lost again
** issue: minimizing the window and restoring causes the element in the popup parent or child to look focused, but keys still don't work

XUL:Panel Improvements

2010-03-23T01:20:15Z

Faaborg: /* Random Thoughts */

XUL:Panel Improvements

2010-03-23T01:17:09Z

Faaborg:

Firefox/Projects/Notification

2010-03-12T01:33:05Z

Faaborg: Created page with '= Pitch = This is a meta tracking bug for all UI changes in Firefox that are related to user notification. This includes: *Transitioning notification bars to the "door hanger" …'

= Pitch =
This is a meta tracking bug for all UI changes in Firefox that are related to
user notification. This includes:

*Transitioning notification bars to the "door hanger" click outside to close
panel design
*Dealing with Application level notifications, like important security updates
*Dealing with all startup and on close dialog box
*Dealing generally with pop-up dialog boxes across the application, including
attempts to create javascript dialogs modal their their particular execution
stack

= Goals =
*

= Non-Goals =
*

= Status =

* Tracking Bug: {{bug|551861}}

* Project Lead: TBD
* Design team: faaborg
* Implementation team: TBD

= Design =
*

= Timeline / Milestones =

= Delivery Requirements =
*

= Constraints =
*

= Dependencies =
*

= Testing =
*

= Related Projects =
*

Firefox/Projects/Weave

2010-03-12T01:01:45Z

Faaborg: /* Status */

__NOTOC__
This project is to track Weave uplift into Firefox. We're doing this by iterating on the extension and preparing that code for eventual inclusion in mozilla-central.

* Champion: mconnor
* Project Lead: zpao
* Project Members: Mardak, faaborg

== Status ==
* <onlyinclude>TAKING OFF</onlyinclude>
** Meaning... Work is being done to improve the addon and looking at necessary changes for this project to be IN FLIGHT.
* Tracking bug for all UI changes: {{bug|551853}}

== Goals ==
* Get Weave extension prepared for mozilla-central. Includes:
** Auditing API usage by appropriate peers ({{bug|548373}})
** Making necessary UI changes
** Moving code (no bug yet, [[User:Mconnor/WeaveSourceReorg]])
** Integrating build system ({{bug|433926}})
** Automated tests (no bug yet)

== Non-Goals ==
* Re-implementing Weave

== Timeline / Milestones ==
See [[User:Mconnor/Weave1H2010]]

== Requirements ==

== Dependencies ==

== Testing ==
* Will need to write a lot of tests (in goals)
* Will need to work with QA to make sure we start getting automated (mozmill) tests written

== Related Projects ==

Firefox/Projects/Customization

2010-03-12T00:53:26Z

Faaborg: /* Status */

= Pitch =
Customization is one of the core values of Firefox, however there are a number
of significant limitations to how users can currently customize their Firefox
UI. This project will cover both the user interface and underlying platform
improvements related to the customization of Firefox's interface. The set of
dependent bugs lists the specific set of enhancements, but this project will in
general include aspects ranging from limitations like having multiple instances
of the same control in the toolbar customization pallet (separate back/forward
controls and the keyhole, combined stop/reload and separate stop and reload,
etc.), to the design and implementation of a unified Firefox customization
interface that covers both toolbar customization and applying themes and
personas.

= Goals =
*

= Non-Goals =
*

= Status =

* Tracking Bug: {{bug|551843}}

* Project Lead: faaborg (or possibly boriss)
* Design team: faaborg, boriss
* Implementation team: TBD

= Design =
*

= Timeline / Milestones =
Initial timeline is expected to be mostly Act4, placing this work after a lot
of the interfaces that will need to be customized (like the location of the tab
strip) have landed.

= Delivery Requirements =
*

= Constraints =
*

= Dependencies =
*

= Testing =
*

= Related Projects =
*

Firefox/Projects/Home Tab

2010-03-12T00:53:07Z

Faaborg:

== Summary ==
This project covers the design and creation of a Firefox Home Tab, a small persistent tab placed at the far left of the tab strip that will serve as the user's home on the Web. The plan is for this interface to be locally hosted, customizable, and personalized to the needs of each individual user.

The second aspect of this project is allowing users to create "App Tabs," small persistent tabs placed to the right of the Home Tab that contain home pages or Web applications that the user very regularly interacts with. App tabs can not be accidentally closed, and they do get lost when viewing a large number of documents in separate tabs.

== Current Status ==

Very early conceptual design work.

== Next Steps ==

* Post first round of mockups for feedback

== Related Bugs ==

* Tracking bug: {{bug|551849}}

== Team ==

*'''Project Lead''': faaborg
* everyone

== Designs ==

[http://people.mozilla.com/~faaborg/files/firefox4Mockups/homeTab-i1.png Extremely early conceptual mockup]

Notable aspects:
* no browser chrome
* entirely zero configuration by default (ambient news)
* mouse-based access to bookmarks and history
* ability to change the search engine (drop down to the right of it)
* (more frequently visited sites and the ability to customize with a persona below the fold)

[http://blog.seanmartell.com/wp-content/uploads/2009/04/newtab_1.jpg Great thumbnail idea by Sean Martell]

== Goals/Use Cases ==

Designs will explore a range of ideas, including:
* Frequently visited sites with ambient news
* Leveraging the user's social graph for ambient social news
* Access to all available search engines
* Browse-based interface into bookmarks and history (ties into the [https://wiki.mozilla.org/Firefox/Projects/Places_UI Places UI] project)
* Increasing the discoverability of personalization with personas
* Message snippets
* Fully localized season and holiday changes (could be lots of fun, also really lots of work, but worth exploring).

== Non Goals ==

* Non goal 1: A streamlined and simplistic page. This page is going to provide a rich experience, with an expressive visual design and a range of features, it might even be a bit distracting (er, engaging). This is a fully recognition-based interface (the new tab page will likely remain fully recall-based).

* Non goal 2: The traditional home page portal slum of tabloid level celebrity news, sensationalistic titles, and pathetic attempts to leverage the screen real estate to promote unrelated products (instant messenger apps, iPods, etc.). This page will be 100% about the specific user and their fully personalized experience on the Web, it is not about the company that created the browser.

Firefox/Projects/Customization

2010-03-12T00:39:46Z

Faaborg: /* Status */

= Pitch =
Customization is one of the core values of Firefox, however there are a number
of significant limitations to how users can currently customize their Firefox
UI. This project will cover both the user interface and underlying platform
improvements related to the customization of Firefox's interface. The set of
dependent bugs lists the specific set of enhancements, but this project will in
general include aspects ranging from limitations like having multiple instances
of the same control in the toolbar customization pallet (separate back/forward
controls and the keyhole, combined stop/reload and separate stop and reload,
etc.), to the design and implementation of a unified Firefox customization
interface that covers both toolbar customization and applying themes and
personas.

= Goals =
*

= Non-Goals =
*

= Status =

* Tracking Bugs: {{bug|551843}}

* Project Lead: faaborg (or possibly boriss)
* Design team: faaborg, boriss
* Implementation team: TBD

= Design =
*

= Timeline / Milestones =
Initial timeline is expected to be mostly Act4, placing this work after a lot
of the interfaces that will need to be customized (like the location of the tab
strip) have landed.

= Delivery Requirements =
*

= Constraints =
*

= Dependencies =
*

= Testing =
*

= Related Projects =
*

Firefox/Projects/Customization

2010-03-12T00:37:27Z

Faaborg:

= Pitch =
Customization is one of the core values of Firefox, however there are a number
of significant limitations to how users can currently customize their Firefox
UI. This project will cover both the user interface and underlying platform
improvements related to the customization of Firefox's interface. The set of
dependent bugs lists the specific set of enhancements, but this project will in
general include aspects ranging from limitations like having multiple instances
of the same control in the toolbar customization pallet (separate back/forward
controls and the keyhole, combined stop/reload and separate stop and reload,
etc.), to the design and implementation of a unified Firefox customization
interface that covers both toolbar customization and applying themes and
personas.

= Goals =
*

= Non-Goals =
*

= Status =
*

* '''Tracking Bugs:'''
**

* '''Project Lead:'''
* '''Project Members:'''

= Design =
*

= Timeline / Milestones =
Initial timeline is expected to be mostly Act4, placing this work after a lot
of the interfaces that will need to be customized (like the location of the tab
strip) have landed.

= Delivery Requirements =
*

= Constraints =
*

= Dependencies =
*

= Testing =
*

= Related Projects =
*

Firefox/Projects/Customization

2010-03-11T01:08:39Z

Faaborg: Created page with '= Pitch = = Goals = * = Non-Goals = * = Status = * * '''Tracking Bugs:''' ** * '''Project Lead:''' * '''Project Members:''' = Design = * = Timeline / Milestones…'

= Pitch =

= Goals =
*

= Non-Goals =
*

= Status =
*

* '''Tracking Bugs:'''
**

* '''Project Lead:'''
* '''Project Members:'''

= Design =
*

= Timeline / Milestones =
*

= Delivery Requirements =
*

= Constraints =
*

= Dependencies =
*

= Testing =
*

= Related Projects =
*

Firefox/Projects

2010-02-23T01:26:21Z

Faaborg:

= Active Projects =

{| class="fullwidth-table sortable"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Participants'''
| '''Goal'''
| '''ETA'''
| '''Target'''
| '''Status'''
|-
| [[Firefox/Projects/Startup Time Improvements|Startup Time Improvements]]
| dietrich
| ddahl, rflint, adw
| reduce warm and cold startup of Firefox, Fennec
|
| 1.9.3
| [http://autonome.wordpress.com/tag/startup/ Most recent status update]
|-
| [https://wiki.mozilla.org/Firefox/Goals/2010Q1/IO_Reduction I/O Reduction]
| sdwilsh
| mak, rflint
| > 50% reduction of main thread I/O
|
| 1.9.3
| {{:Firefox/Goals/2010Q1/IO Reduction}}
|-
| Out-of-process plugins
| Dolske
| gavin
| Ship out of process plugins and associated UI pieces to Windows users
|
| 1.9.3
| {{bug|538910}}
|-
| Process Separation
|
|
| Document scope of work for process separation in Firefox & port one feature as an experiment
|
| TBD
|
|-
| [[Firefox/Projects/3.7 and 4.0 Theme and UI Revamp|Theme]]
| shorlander, gavin
| faaborg, dao
| Implement alpha quality Windows implementation of refactored browser.js & new theme for Windows on trunk or as XPI
|
| TBD
| [http://blog.stephenhorlander.com/2010/02/08/theme-bugs-filed-wiki-updated/ Feb 8 Update]
|-
| [[Firefox/Projects/Weave|Implement native Weave client on trunk]]
| mconnor (lead), faaborg (Firefox)
| boriss, ragavan, thunder
| Add bookmark sync to Firefox 3.7
| Ongoing
| TBD
| mconnor is iterating on the UI based on feedback
|-
| [[Extension Manager:UI Update|Addons Manager UI Redesign]]
| Boriss
| Unfocused, Mossop, Nick, Fligtar, Tony (QA)
| Design and implement unified web services & customization interface on trunk
| TBD
| 1.9.3
| Starting to build prototype using new API
|-
| [[Firefox/Projects/Extension Manager API|Extension Manager API Rewrite]]
| Mossop
| Unfocused, Tony (QA)
| Improve the usability and extensibility of the add-ons manager APIs. Make it easier to create custom and complex UIs for the add-ons manager.
| Mid-End of Feb
| 1.9.3
| {{:Firefox/Projects/Extension Manager API|Extension Manager API Rewrite}}
|-
| [[Firefox/Projects/Console|Debug console for web pages]]
| robc
| johnath, limi, ddahl
| Implement alpha quality integrated developer tool set on trunk
|
| hopefully 1.9.3
| {{:Firefox/Projects/Console}}
|-
| [[Firefox/Projects/Inspector|Web page inspector]]
| robc
| johnath, limi
| Implement alpha quality integrated developer tool set on trunk
| Late March
| 1.9.3
| {{:Firefox/Projects/Inspector}}
|-
| [[Firefox/Projects/Jetpack|Stabilize Jetpack API]]
| adw
| mossop
| Make sure Jetpack's needs in Firefox/Platform are taken care of
|
| TBD
| {{:Firefox/Projects/Jetpack}}
|-
| [[Firefox/Projects/Resource Packages|Resource Packages]]
| vlad, limi (until spec is good enough)
| 
| Backwards compatible way of serving up multiple resources in a streamable file
| Feedback for r2 of proposal received
| Starting with 3.7
| Next step: Find a way to declare manifest inline, then it should be ready for a prototype implementation.
|-
| [[Firefox/Projects/Home Tab|Home Tab and App Tabs]]
| faaborg
|
| Investigate a full window, client side, browse-based UI to serve as the user's home on the Web, and the ability to create chromeless app tabs.
| First round of mockups complete: 10/23
| Starting with 3.7
| Just getting started
|-
| [[Firefox/Projects/Tab_Matches_in_Awesomebar|Tab Matches In Awesomebar]] (+ retiring old URL dialog) 
| Unfocused 
| limi, gavin, ashughes (QA)
| Make it possible to switch tabs using the AwesomeBar 
| Jan 2009
| 3.7a1
| Code review. Some UI tweaks may still be needed.
|-
| [[Firefox/Projects/PlacesQueryAPIRedesign | Places Query API Redesign]]
| ddahl
| TBD 
| Simple, elegant Places Query API that is focused on 3.7 Places work
| TBD
| 1.9.3
| Patches up and have review + for the Jetpack implementation. bug 522572 (Sync impl.) / Async in progress as well bug 534983, Filed bug 543888 to craft in a skeleton a more comprehensive API for the async patch
|-
| [[Firefox/Projects/Async Places containers|Async Places containers]]
| adw
|
| Perf: non-blocking Places operations
| TBD
| 1.9.3
| {{:Firefox/Projects/Async_Places_containers}}
|-
| Print preview in a separate window
| rflint
|
| Remove the fragile XBL binding and create a separate XUL document
|
| 1.9.3
| Basic implementation working; cruft removal and refinement in progress.
|-
| [[Firefox/Projects/Action based on update xml after app update|Action based on update xml after app update]]
| rs
|
| Perform action after update based on update xml attribute.
| Client side should be done by 2/12
| 1.9.3
| Patches for app update r+'d. Finishing tests. ddahl taken off of this work so patches for Firefox still need to be done... hopefully this week.
|}

= Inactive Projects (need to finish) =

{| class="fullwidth-table sortable"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Participants'''
| '''Goal'''
| '''ETA'''
| '''Target'''
| '''Status'''
|-
| [[Firefox/Projects/Preferences UI|Preferences UI]]
| faaborg
|
| Refresh and streamline the Firefox preferences window
| First round of mockups complete: 10/23
| Starting with 3.7
| Just getting started
|-
| [[Firefox/Projects/Places UI|Places UI]]
| faaborg
| 
| Investigate changes to the places UI for 3.7 and 4.0, focusing on mixing search + browse operations, and leveraging the content area.
| Breaking UI apart into separate bugs: 10/23
| Starting with 3.7
| Mockups complete, feedback coming in.
|-
| [[Firefox/Projects/Doorhanger_notifications|Doorhanger notifications]]
| dolske
| faaborg (UI), ashughes (QA)
| get'r'dun
| As early in 3.7 as possible
| TBD
|
|-
| [[Firefox/Projects/Binding for untrusted text in security dialogs|Binding for untrusted text in security dialogs]]
| Unfocused
| Jesse
| Provide a common way for security dialogs to include untrusted text without compromising the rest of the dialog
| TBD
| 1.9.3
| Gathering info, planning
|-
| [[Firefox/Projects/PersonalIdentity|Personal Identity]]
| ragavan (lead) faaborg (Firefox)
| thunder, aza, messina
| Explore integrating personal identity management into Firefox
|
|
|
|-
| [[Firefox/Projects/Herdict|Herdict]]
| atul (lead) boriss (Firefox)
| faaborg
| Explore integrating the functionality of [http://www.herdict.org Herdict] with Firefox's network error page.
|
|
|
|}

*[[Firefox/Projects/AcceleratedScrolling|Accelerated Scrolling]]
*[[Firefox/Projects/Multitouch Polish|Multitouch Polish]]
*[[Firefox/Projects/Eradicate Startup Dialogs|Eradicating Startup Dialogs]]
*[[Firefox/Projects/Network Error Pages|404 Error Pages]]
*[[Firefox/Projects/Unbreak RSS|Unbreak RSS]]

== Prioritized ==

*[[Firefox/Projects/Inline PDF display|Inline PDF display]] - Has legal ok, needs engineering estimate, and targeting (for 3.7?)
* [[Firefox/Projects/Download manager improvements|Improve Download Manager + MIME type defaults]]
* [[Firefox/Projects/Improve Mac installer|Improve Mac installer]]
*[[Firefox/Projects/System Extension Notification|System Extension Notification]]
*[[Firefox/Projects/StrandedUsers|Understand why we strand users on point releases]]
*[[Firefox/Projects/Always have option to Add Search|Always have option to Add Search]]
*[[Firefox/Projects/Add Search to Awesomebar|Add Search to Awesomebar]]
*[[Firefox/Projects/Rebuild Software Update without browser element|Rebuild Software Update without browser element]][[Firefox/Projects/Places UI Overhaul Exploration| ]]
*[[Firefox/Projects/App-wide Database Vacuum|App-wide Database Vacuum]]
*[[Firefox/Projects/About:newtab|about:newtab]]
*[[Firefox/Projects/Improve Plugin Find and Install|Improve Plugin Find and Install]]
*[[Firefox/Projects/Visual Affordance for Tear Off Tabs|Visual Affordance for Tear Off Tabs]]
*[[Firefox/Projects/Control Tab|Control-Tab]]
*[[Firefox/Projects/Update hunspell|Update dictionaries]]
*[[Firefox/Projects/about:problems|about:problems]]
*[[Firefox/Projects/Automatic Recovery|Automatic Recovery]]
*[[Firefox/Projects/about:me|about:me (first-pass addon done, uplift approach still open)]]
*[[Firefox/Projects/Video Controls|Video Controls]]
*[[Firefox/Projects/Tab_animation|Tab & Menu item animation]]
*[[Firefox/Projects/Find_on_Page|Find on Page improvements]]

== Unprioritized ==

*[[Firefox/Projects/Jetpack Uplift Exploration|JetPack Uplift]]

= Additional Projects Ideas (Need more definition) =

*[[Firefox/Cleanup|Areas that need code cleanup or overhaul]]
*[[Firefox/Projects/App-wide Database Integrity Check|App-wide Database Integrity Check]]
*[[Firefox/Projects/Create a Places page thumbnail service|Create a Places page thumbnail service]]
*[[Firefox/Projects/Crowdsource Performance Data|Crowdsource Performance Data]]
*[[Firefox/Projects/Migration Component JS Porting|Migration Component JS Porting]]
*[[Firefox/Projects/ExperimentalPlacesSchema|Places Schema Redesign]]
*[[Firefox/Projects/View Source in Tab|View Source in Tab]]

= Completed Projects / Archive =

*[[Firefox/Projects/Places async expiration|Places Async Expiration]] (LANDED 1.9.3)
*[[Firefox/Projects/WindowsCE|Firefox WinCE]] (minor stuff still to do)
*[[Firefox/Projects/Places Vacuum]] (LANDED 1.9.2)
*[[Firefox/Projects/Perception of Performance|Perception of Performance]] (Investigation, see wiki page for follow up projects)
*[[Firefox/Projects/Async Annotation Protocol Handler|Asynchronous Annotation Protocol Handler]] (LANDED 1.9.1)
*[[Firefox/Projects/Places Expiration Performance Refactoring|Places Expiration Performance Refactoring]] (LANDED 1.9.1)
*[[Firefox/Projects/Bookmark Dialog Focus|Bookmark Dialog Focus]] (LANDED 1.9.1)
*[[Firefox/Projects/Restore Visible Tabs First|Restore Visible Tabs First]] (LANDED 1.9.1)
*[[Firefox/Projects/Privacy Prefpane Refresh|Privacy Prefpane Refresh]] (LANDED 1.9.1)
*[[Firefox/Projects/Clear Recent History by Time Range|Clear Recent History by Time Range]] (COMPLETED WITH NOTES)
*[[Firefox/Projects/Undo Close Window|Undo Close Window]] (LANDED 1.9.1)
*[[Firefox/Projects/Windows Theme Polish|Windows Theme Polish]] (LANDED 1.9.1)
*[[Firefox/Projects/Focus Ring Cleanup|Focus Ring Cleanup]] (LANDED 1.9.1)
*[[Firefox/Projects/Places DB Creation Scripts|Places DB Creation Scripts]] (COMPLETED)
*[[Firefox/Projects/Asynchronous Location Bar|Asynchronous Location Bar]] (LANDED 1.9.2)
*[[Firefox/Projects/Awesomeformcomplete|Form Awesomecomplete]] (LANDED 1.9.2)
*Focus rewrite (LANDED, NO WIKI PAGE)
* [[Firefox/Projects/Animation priorities|Animation priorities]] (became two child-sprints: [[Firefox/Projects/Tab_animation|Tab & Menu item animation]] and [[Firefox/Projects/Find_on_Page|Find on Page improvements]])
* [[Firefox/Projects/about:support|about:support]] (LANDED 1.9.2)
* [[Firefox/Projects/Plugin Update Referrals|Plugin Update Referrals]] (LANDED 1.9.2)
* [[Firefox/Projects/Personas Uplift Exploration|Personas Uplift Exploration]] (LANDED 1.9.2)
* [[Firefox/Projects/Reduce Places Views Overhead|Reduce Places Views Overhead]] (LANDED 1.9.2)
* [[Firefox/Projects/Per Tab Network Prioritization|Per Tab Network Prioritization]] (LANDED 1.9.2)

= Template =

(Mostly) [[Firefox/Projects/Template|Blank Template]] for new projects.

= All pages =
[[Special:PrefixIndex/{{PAGENAME}}/| All subpages of {{PAGENAME}}]]
(most are described on this page).

Firefox/Projects/New Theme

2010-02-18T03:01:28Z

Faaborg: /* Platform Capabilities */

= Overview =
'''Sprint lead:''' shorlander 
'''Sprinters:''' faaborg, limi, boriss 
'''Timeframe:''' (beginning 2009/07/13)–(ending ?) 

'''Description:''' Exploring a revamp of the Firefox Theme/UI. Identifying current issues and weaknesses. Focus on modernizing and streamlining. Specific emphasis on appearance and behavior on Windows Vista/7. Increased cross-platform cohesiveness.

= Goals =
* Streamline UI Elements
* Reduce Visual Footprint
* Modernize Look and Feel
* Retain Visual Integration While Still Being Attractive
* Increased Cross Platform Consistency (Where Applicable)

= Windows =
== Current Theme Issues ==
[[Firefox/3.0 Windows Default Theme Issues|3.0 Windows Default Theme Issues]]: This is a good starting point that identifies problems and shortcomings with the current Theme/UI on Windows. Focus on Windows Vista and 7.

== Visually Appealing Windows Applications ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Visually_Appealing_Windows_Applications|Visually Appealing Windows Applications]]: Some examples of Windows applications that are visually appealing and/or have good UI design.

== Design: ==
* Make use of Aero Glass on Windows 7 and Vista
* Move to tabs-on-top by default (option to move back underneath navigation bar and possibly left or right as well)
* Combine Reload/Stop/Go (Separate Stop and Reload buttons in Customization dialog)
* Move Reload/Stop/Go to the LocationBar
* Addition of thin progress bar (tied to LocationBar in active tab and top of tab for background tabs)
* Sort and Trim Menu Items
* Hide the MenuBar and create replacement AppMenu. ("Firefox" Button)
* Remove the bookmarks bar(if never user altered)
* Addition of a Bookmarks Widget on the main toolbar that replicates the Bookmarks Menu
* Move "Home" button to Home Tab
* Changes to the TabBar to make it more streamlined
* Shift towards more unified look across Windows variations(while still retaining platform look & feel "spirit")
** Less "bright and colorful" icons
** More tangible button appearance
** Perhaps more glyphs
* General icon cleanup/polish

=== Mockups ===
* [[Firefox/4.0 Windows Theme Mockups]]

== Proposed Theme/UI Direction and Feedback ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|Direction and Feedback]]: In depth exploration of proposed ideas for Firefox 3.7 and 4.0.

 

= Mac =
== Design: ==
The design for Mac is very similar to what has been [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|proposed for Windows]]. With some exceptions:
* The Menubar, being a system wide element, will stay
* The absence of the App Button and App Menu

=== Mockups ===
* [[Firefox/4.0 Mac Theme Mockups]]

== Mac Specific Visual Refresh ==
There are many stylistic changes that are addressed in depth in the [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh|Mac Specific Visual Refresh]] article.

 

= Linux =
== Design: ==
The Linux design picks up many aspects from the ideas [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|proposed for Windows]]. With specific emphasis on how to integrate with various system themes.

=== Mockups ===
* [[Firefox/4.0 Linux Theme Mockups]]

== Linux Specific Visual Refresh ==
There are some stylistic changes that are addressed in depth in the [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Linux_Specific_Visual_Refresh|Linux Specific Visual Refresh]] article.

 

= Theme/UI Implementation Bugs =

* {{bug|544815}} - Allow for placing Tabs over the Navigation Bar with option for Tabs under the Navigation Bar
* {{bug|544816}} - Attach combined Stop/Go/Refresh button to the Location Bar
* {{bug|544817}} - Create Bookmarks Widget with placement dependent on Bookmarks Bar status
* {{bug|544818}} - Progress "Line" indicator for background loading tabs
* {{bug|544819}} - Create a basic Home Tab linking to the current Home Page
* {{bug|544823}} - [Meta] Theme Visual Refresh
** {{bug|544820}} - [Windows] Theme Visual Refresh
** {{bug|544821}} - [OS X] Theme Visual Refresh

 

= Platform Capabilities =

These are all things that we would need to be able to do to create the theme changes that have been mocked up.  As new limitations emerge I'll add them to this list as well.

== Required ==

=== Main Window ===

* {{bug|513157}} Ability to draw the title bar ourselves (used for tabs, weave, OS theme integration, personas, private browsing mode)
** OS X: {{bug|513158}} Josh will look into this more for OS X
** Windows: {{bug|513162}} talk to Jim or rstrong
** Linux: {{bug|513159}} only gnome for overlaying the title bar? need to talk to karl tomlinson, zwol

* {{bug|546822}} OS Theme detection
** OS X: (not applicable)
** Windows: {{bug|543910}}
** Linux: {{bug|546816}}

=== Transparency ===

*Windows: {{bug|506124}} Aero Glass support
** Glass support and personas {{bug|513170}}
** Glass support and private browsing {{bug|513418}}

*Linux: Transparent Windows {{bug|408284}}

*Ability to draw persistent translucent areas over content {{bug|546844}}

=== Customization ===

*Platform capabilities for UI customization {{bug|}}
**Ability to have multiple instances of the same control {{bug|}}
**Ability to change the appearance of a control based on its location relative to other controls on the toolbar {{bug|}}
**Animate toolbar elements while the user is customizing the toolbar {{bug|}}

=== Animation ===

**Animating tabs
**Animate toolbar elements while the user is customizing the toolbar {{bug|}}

== Optional (but highly desired) ==

=== Animation ===

*Platform capabilities for animation {{bug|}}
**Widget animation {{bug|}}
***Windows {{bug|392644}}
***OS X
***Linux
**Animating panels

=== Cursor changes ===

= Possible Theme Re-factoring =

*Icons: refactor how the mozilla platform deals with icons
**proposed approach for feedback: [[Firefox/Projects/IconRefactor]]

*Colors: about:colors, single file with all hard coded colors, new primitives (moz-red)
**Dao got started on doing this, need to check on the current status

Firefox/Projects/New Theme

2010-02-03T06:13:55Z

Faaborg: /* All Platforms: General */

= Overview =
'''Sprint lead:''' shorlander 
'''Sprinters:''' faaborg, limi, (martell) 
'''Timeframe:''' (beginning 2009/07/13)–(ending ?) 

'''Description:''' Exploring a revamp of the Firefox Theme/UI. Identifying current issues and weaknesses. Focus on modernizing and streamlining. Specific emphasis on appearance and behavior on Windows Vista/7. Increased cross-platform cohesiveness.

= Goals =
* Streamline UI Elements
* Reduce Visual Footprint
* Modernize Look and Feel
* Retain Visual Integration While Still Being Attractive
* Increased Cross Platform Consistency (Where Applicable)

= Windows =
== Current Theme Issues ==
[[Firefox/3.0 Windows Default Theme Issues|3.0 Windows Default Theme Issues]]: This is a good starting point that identifies problems and shortcomings with the current Theme/UI on Windows. Focus on Windows Vista and 7.

== Visually Appealing Windows Applications ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Visually_Appealing_Windows_Applications|Visually Appealing Windows Applications]]: Some examples of Windows applications that are visually appealing and/or have good UI design.

== Design: ==
* Make use of Aero Glass on Windows 7 and Vista
* Move to tabs-on-top by default (option to move back underneath navigation bar and possibly left or right as well)
* Combine Reload/Stop/Go (Separate Stop and Reload buttons in Customization dialog)
* Move Reload/Stop/Go to the LocationBar
* Addition of thin progress bar (tied to LocationBar in active tab and top of tab for background tabs)
* Sort and Trim Menu Items
* Hide the MenuBar and create replacement AppMenu. ("Firefox" Button)
* Remove the bookmarks bar(if never user altered)
* Addition of a Bookmarks Widget on the main toolbar that replicates the Bookmarks Menu
* Move "Home" button to Home Tab
* Changes to the TabBar to make it more streamlined
* Shift towards more unified look across Windows variations(while still retaining platform look & feel "spirit")
** Less "bright and colorful" icons
** More tangible button appearance
** Perhaps more glyphs
* General icon cleanup/polish

=== Mockups ===
* [[Firefox/4.0 Windows Theme Mockups]]

= Mac =
== Design: ==
The design for Mac is very similar to what has been [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|proposed for Windows]]. With some exceptions:
* The Menubar, being a system wide element, will stay.
* The Page and Tools buttons will be hidden by default.

There are many stylistic changes that are addressed in depth in the [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh|Mac Specific Visual Refresh]] article.

=== Mockups ===
* [[Firefox/3.7 Mac Theme Mockups]]
* [[Firefox/4.0 Mac Theme Mockups]]

= Linux =
== Design: ==
The Linux design picks up many aspects from the ideas [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|proposed for Windows]]. With specific emphasis on how to integrate with various system themes.

There are some stylistic changes that are addressed in depth in the [[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Linux_Specific_Visual_Refresh|Linux Specific Visual Refresh]] article.

=== Mockups ===
* [[Firefox/3.7 Linux Theme Mockups]]
* [[Firefox/4.0 Linux Theme Mockups]]

= Proposed Theme/UI Direction and Feedback =
== Direction and Feedback ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Direction_and_Feedback|Direction and Feedback]]: In depth exploration of proposed ideas for Firefox 3.7 and 4.0.

== Mac Specific Visual Refresh ==
[[Firefox/Projects/3.7_and_4.0_Theme_and_UI_Revamp/Mac_Specific_Visual_Refresh|Mac Specific Visual Refresh]]: Proposed Mac specific visual refresh.

= Platform Capabilities =

These are all things that we would need to be able to do to create the theme changes that have been mocked up.  As new limitations emerge I'll add them to this list as well.

== All Platforms: General ==

* {{bug|513157}} Ability to draw the title bar ourselves (possibly tabs, weave, OS theme integration, personas)
** {{bug|513158}} Josh will look into this more for OS X
** {{bug|513162}} Windows: talk to Jim or rstrong
** {{bug|513159}} Linux: only gnome for overlaying the title bar? perhaps consider dropping, need to talk to karl tomlinson, zwol

*Additional OS theme resource extraction (are there things we should expose to the platform from the new OS themes?)
**Nothing comes to mind right now on things that are available

*Full OS theme detection
**{{bug|543910}}

*Icons: refactor how the mozilla platform deals with icons
**proposed approach for feedback: [[Firefox/Projects/IconRefactor]]

*Colors: about:colors, single file with all hard coded colors, new primitives (moz-red)
**Dao got started on doing this, it's a build time thing

== All Platforms: Customization ==

*Ability to have multiple instances of the same control in the customization palette
**Not a problem, just need to actually do it

*Ability to change the appearance of a control based on its location relative to other controls on the toolbar
**Possible, but a lot easier to just do it based off of the immediate right and left items. We can go farther than that but it starts to get intractably complex.

== Windows ==

*Ability to package multiple themes (XP, Vista, 7) instead of relying on chrome overrides
**Showing both in the theme manager might be difficult, need to follow up on the

*Ability to package different .ico files for different versions of Windows
**First icon embedded in the firefox.exe, so we would have to have different exe files.
**However, we can control the icon used for shortcuts (start menu, quick launch, desktop) so that very well could be good enough, especially if we are drawing our own title bar so can use whatever

*{{bug|506124}} Glass support (already well discussed and on track, but a platform capability nonetheless)
** Some interesting cases with personas {{bug|513170}} and also private browsing {{bug|513418}}