MozillaWiki - User contributions [en]

Platform/2012-05-01

2012-05-01T18:01:54Z

Zpao: /* Firefox Development */

[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|« previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week »]]

<div class="h-event vevent">
'''Platform Meeting Details'''
* Tuesday {{#time: Y-m-d | {{SUBPAGENAME}} }} - 11:00 am <abbr class="value" title="-0700">Pacific</abbr>
{{conf|95312}}
* [https://v.mozilla.com/flex.html?roomdirect.html&key=UK1zyrd7Vhym Warp Core Vidyo Room] / SFO-7N Noise Pop
* join irc.mozilla.org [irc://irc.mozilla.org/planning #planning] for back channel
</div>

==Kilimanjaro==
* Efforts continue to "define" k9o
** Excellent conversations on the list
** https://wiki.mozilla.org/Kilimanjaro/ProductDraft - continue to add bugs
** Some outstanding items to triage - happening after this meeting
* There is an App/Site compat effort to ensure content works on the Mozilla platform
** Involvement from business dev, QA, product, engineering, dev evangelism, market insights, press
** Information and details being documented [[Program_Management/Programs/Apps/Site_Compatibility|on the wiki]]
** Lawrence Mandel (lmandel) for questions, to get involved

==Notices / Schedule==

==Firefox Development==
* Firefox team sprinted to get a prototype of "sign in to browser" working
** links a profile with an email address (browserid/persona)
*** signin/signout "work" to the extent that profiles are switched and a default fallback profile is used on logout
** no tie-in with browserid service yet
** progress available at https://hg.mozilla.org/users/poshannessy_mozilla.com/signin/

==Firefox Developer Tools==

==Add-on SDK==
* HTML localization landed
* SDK context inside scratchpad: https://github.com/Gozala/scratch-kit/

==Performance==
* This week's [http://blog.mozilla.org/tglek/2012/04/26/snappy-april-26/ Snappy summary]
* Kyle landed a very significant Snappy fix this week as part of memshrink that reduces leaks in chrome ({{bug|695480}}). It should significantly reduce memory usage and thus cycle-collector pauses, etc.
* Patrick landed a change to have Firefox now hedge bets and warm up a TCP connection while checking the cache ({{bug|729133}}). More details on [http://bitsup.blogspot.com/2012/04/making-firefox-search-snappier.html Patricks’s blog].
* Work going into improving setTimeout ({{bug|743877}}, {{bug|715376}}).

==GFX==

==JS==

*FIXED: {{bug|750424}} nsXULPrototypeNode::Release should add itself to the purple buffer. This was blocking {{bug|735099}} Re-enable incremental GC

==Layout==

==Video==

* Nothing to report

==DOM==

==WebAPI==

==Network==

==Identity==

==Plugins==

==Mobile==

==Accessibility==
* Accessibility engine is now built by default on Mac FF nightlies so that we can widen testing for ~5 weeks. Will likely revert for Aurora.

==Tree Management==

==Security==

==Stability Report==

===Socorro===
*Wednesday's release will feature a new reports of crash trends based on build dates ({{bug|640238}}).
*Plan for rapid beta support is being worked on, will delay work on other planned features.

===Desktop===

====Trunk====
*{{bug|750556}} crash in mozilla::dom::Element::ClearStyleStateLocks

====Aurora====
*{{bug|750019}} crash in js::types::TypeSet::addType @ nsIDOMHTMLDocument_Write

====Beta====
*{{bug|750625}} crash in nsUrlClassifierPrefixSet::GetPrefixes

===Mobile===
[[File:CrashStats_2012-04-30.png]] 
* New crash in nightly with epoll_wait
* Mobile specific socorro/breakpad integration issues : see [https://wiki.mozilla.org/Mobile/Notes/02-May-2012#QA Mobile Notes]
==== Nightly Native ====
* {{Bug|746946}} - Fennec crashes repeatedly after opening the bookmarks or history section with a clean profile
** Landed 4/30 on Aurora; Landed 4/29
* {{bug|748721}} - crash in mozilla::layers::BasicTiledLayerTile::BasicTiledLayerTile
** Does not occur on 4/27 and later.
* {{Bug|749816}} - crash in epoll_wait after changing display: table-column style to display:none on body
* {{Bug|738198}} - crash in nsPluginInstanceOwner::~nsPluginInstanceOwner @ nsPluginInstanceOwner::RemovePluginView

==== Aurora Native ====
* Top 2 are the same as in Nightly
* {{Bug|730890}} - crash [@ libdvm.so@<address>]

==Roundtable==
* mozilla-central and mozilla-inbound CLOSED for {{bug|750661}}. Need help from everyone to get as much code out of libxul as possible. Ping ehsan if you can help.

User:Zpao/SessionStore2

2011-10-10T21:13:16Z

Zpao:

This is currently just a place to collect thoughts on problems I've seen with session restore and where I think we should go.

== Random Thoughts ==

*Caching - do we do it hard enough? We often seem to throw out all data we have when we don't necessarily need to.
*SessionStorage - can we do something so when google puts 300K in there

== API improvements ==

with e10s, we may need to make things async, which could have interesting results for consumers like private browsing

As we store more data, we may want to allow APIs get at data without collecting other data. For example, if we store a lastAccessed timestamp for each tab, it would make sense to make that easily accessible without having to collect all history for that tab.

== Plugins ==

We've sort of had this notification system and the ability to store arbitrary strings on a tab or window. But there are things like Scratchpad who would benefit from having a more general use (see {{bug|644409}} - the general idea is that it's doing session restore for scratchpad windows, which is something session restore core doesn't need to know how to do). In the future Panorama might be able to use this.

So I'm thinking of having an XPCOM interface that could be implemented and registered. Or the ability to register an object that conforms to the same methods. I think registering to a "key" makes sense. When session restore is saving, it would iterate over the "observers" and get a JS object back. It could be saved at the top level for that "key". Data would be collected fairly often when browsing, so caching would have to happen on the implementer side. On restore, sessionstore would call each plugin's restore method with the JS object that got saved.

We may be able to break down session restore into smaller components this way. We have a core data storage service. That could be in toolkit. Then have plugins implemented to implement collection for app specific things. Taken to an extreme, we could replace some of the things that end up in localstore.rdf (oh god).

== Requests ==

Have you been frustrated by how sessionstore works? Or had an idea for a specific API? List them here (along with your name/nick so I ;can followup)

User:Zpao/SessionStore2

2011-09-05T22:26:11Z

Zpao: Created page with "This is currently just a place to collect thoughts on problems I've seen with session restore and where I think we should go. * Caching - do we do it hard enough? We often seem..."

This is currently just a place to collect thoughts on problems I've seen with session restore and where I think we should go.

* Caching - do we do it hard enough? We often seem to throw out all data we have when we don't necessarily need to.
* SessionStorage - can we do something so when google puts 300K in there

## API improvements
with e10s, we may need to make things async, which could have interesting results for consumers like private browsing

As we store more data, we may want to allow APIs get at data without collecting other data. For example, if we store a lastAccessed timestamp for each tab, it would make sense to make that easily accessible without having to collect all history for that tab.

User:Zpao

2011-09-02T18:12:31Z

Zpao: /* Writing/Planning */

= Who is zpao =

I am Paul O’Shannessy. I started at Mozilla when I interned in the summer of 2008. I came on full-time in February of 2009.

= What do I work on? =

I've worked on a number of different things. You can see the code I've written by [http://hg.mozilla.org/mozilla-central/log?rev=paul%40oshannessy.com searching pushlog]. In general, I've primarily done stuff in Password Manager & Session Restore and have dabbled in a bunch of other places.

= Writing/Planning =

I also have started doing some writing to plan out some major features or changes.

* [[User:Zpao/mozStorageAndSessionStore|mozStorage and SessionStore]]
* [[User:Zpao/SessionStore2|SessionStore 2]]

= Current Projects =

* [[User:Zpao/SessionstoreClearnup|Sessionstore Cleanup]]

Global App Tabs

2011-08-01T20:17:51Z

Zpao:

{{FeatureStatus
|Feature name=Global App Tabs
|Feature stage=Development
|Feature status=In progress
|Feature health=OK
}}
{{FeatureTeam
|Feature product manager=Asa Dotzler
|Feature feature manager=Paul O'Shannessy
|Feature lead engineer=Paul O'Shannessy
|Feature qa lead=Vlad Ghetiu (irc: vladg)
|Feature ux lead=Alex Limi
}}
{{FeaturePageBody
|Feature overview=App Tabs were always meant to be global across windows, but because of release constraints and timing issues, this didn't happen in Firefox 4. We'd like to complete this feature.

This feature falls primarily in the '''Experience''' category (from the "Discover, Experience, and Connect" vision statement.)
|Feature users and use cases=Users: People who use app tabs
|Feature non-goals=* Tab groups won't become global
* App tab UI in panorama
* Not changing UI (toolbars, notifications, etc)
|Feature ux design=* App tabs should appear on every window, and be global
** Title changed notifications are propagated (and cleared) across all windows
* If two windows are showing the same app tab, we use our ability to re-parent the tab to the other window to make the transition between the two as seamless as possible.
** We will not update both windows, e.g. if you type in one window, it won't be updated in the other window until that window is activated.
* This will also make it harder to accidentally lose app tabs — since they'll be global in every window.
* It also makes it possible to simplify how we handle app tabs in Panorama quite a bit, both on the UI and implementation side of things.
|Feature implementation notes=* {{bug|587873}}
|Feature landing criteria=* It's capable of showing app tabs across all windows (but not popups)
* Handle having the same app tab open in multiple windows

}}
{{FeatureInfo
|Feature priority=P1
|Feature roadmap=User Experience
|Feature list=Desktop
|Feature engineering team=Desktop front-end
}}
{{FeatureTeamStatus}}
We'll want some documentation about the upgrade path. People may be used to the current behavior of app tabs being per window.

WeeklyUpdates/2011-06-06

2011-06-06T16:35:25Z

Zpao: /* Introducing New Hires */

[[WeeklyUpdates/2011-05-23|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-06-13|next week »]]

= Video for today's meeting =

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

= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =
* Alex Rodionov for his contributions to WebQA Automation from the test day and on going!

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

'''Monday, 6 June'''
* [https://wiki.mozilla.org/MDN/Doc_Sprints/2011June MDN documentation sprint through Wednesday]

'''Tuesday, 7 June'''

'''Wednesday, 8 June'''

'''Thursday, 9 June'''

* [[Mozilla.org/Contribute/Group/06_09_11|Contribute Group]] at 10 AM PDT -- forum for discussing helping people get involved with Mozilla

'''Friday, 10 June'''
* [http://quality.mozilla.org/events/2011/06/03/developer-tools-testday-friday-june-10th/ Developer Tools Testday] - QA

'''Next Week'''

= Product Status Updates =

== Firefox Future (5, 6, 7) ==
* Firefox 5 is getting very close
** If we're shipping Jun 21, then we need to be making that call this week
** Watching addon compat closely
** Likewise reports from our 1M+ beta users

* Firefox 6 moving through Aurora now, a few backouts but mostly we just need more people on Aurora - tell your friends!

* 4 weeks left on the Firefox 7 train!

Remember to watch the [http://blog.mozilla.com/channels/ Channels Blog] for updates on the process.

== Firefox Current (3.5, 3.6, 4.0) ==

== Mobile Firefox ==

== Thunderbird ==

== 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
|-
|}

= Status Updates By Team =

== Firefox ==

== Platform ==

== Messaging ==

== Mobile ==

== IT ==

== Release Engineering ==

== QA ==

;Test Execution
* Fx5 Beta 4 Testing: Sign-off ETA, Monday.
* [https://quality.mozilla.org/events/2011/06/03/developer-tools-testday-friday-june-10th/ Developer Tools Testday]: Friday, June 10.

;WebQA

;QA Community

;Test Dev

;Friends of QA
* New tool [http://www.squarefree.com/2011/06/01/faster-crash-analysis-with-stack-blame/ Stack-blame] to help analyze crash regressions (Jesse)
* Updated [https://developer.mozilla.org/en/Bug_writing_guidelines Bug writing guidelines] (Jesse)
* The guided bug reporting form is about to be [https://bugzilla-stage-tip.mozilla.org/enter_bug.cgi?format=guided simplified] ([http://www.squarefree.com/temp2/enter-bug-guided-redesign/ screenshots]) (Gerv, glob)

== Automation & Tools ==

== Security ==
===Past===
* Reviewed / Triaged 14 items for FX5
===Current===
* 34 items "in flight" for FX6 / FX7
** 21 items already completed

Reminder: Please engage the security team (Curtis Koenig [curtisk] specifically) so that security discussions can occur at appropriate times for features and patches. Engaging the security team early on can help us ensure that we are landing things with high quality as quickly as possible. Patch reviewers / landers should also please engage the team when security could be at issue even if the chance of problems are remote.

===More Information===
* [[/Security/Reviews|Security Review Information]]
* [[/Security/Radar|Security Radar]]

== Engagement ==
* Launch of Mark Up is scheduled for June 8th, 9 am PST.
** See the staged site here: https://markup.allizom.org
***Username : markup Password : cho9Oh

'''PR'''

'''Events'''

'''Creative Team'''

'''Community Marketing'''

== Support ==

== Metrics ==

== Evangelism ==

== Labs ==

== Developer Tools ==
* [https://quality.mozilla.org/events/2011/06/03/developer-tools-testday-friday-june-10th/ Developer Tools Testday]: Friday, June 10.

== Add-ons ==

== Webdev ==

== L10n ==

= Introducing New Hires =

* Lilian Weng, intern for User Research
* Sinchan Banerjee, intern for User Experience
* Ali Juma, for Platform/Gfx
* JB Piacentino, Managing Director for Thunderbird
* Eddy Bruël, Software Engineer for Jetpack
* Matteo Ferretti, Software Engineer for Jetpack
* Riccardo Pelizzi, intern for Security
* Jezreel Ng, Firefox intern

= Foundation Updates =

= Roundtable =

Features/Desktop/Expose prefs for tabs-on-demand

2011-05-16T21:11:26Z

Zpao:

{| 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" />
| [[Expose prefs for tabs-on-demand]]
| {{StatusHealthy|status=Feature already exists, should be a simple matter of exposing the setting}}
| N/A
| Alex Limi
<section end="status" />
|-
|}

== Summary ==
Firefox 4 has the hidden ability to load tabs on-demand by setting the maximum number of concurrent tabs being restored to “0” — now that the feature has been in the wild for a while, we'd like to expose it as part of the session restore preferences. Since this makes startup a lot faster, and uses a lot less memory, it's an option we'd like our power users to make use of.

== Team ==
* '''Feature Manager''': Alex Limi
* '''Lead Developer''': Paul O’Shannessy
* '''Product Manager''':
* '''QA''':
* '''UX''': Alex Limi
* '''Accessibility''':
* '''Security''':
* '''Privacy''':

== Release Requirements ==
* Ability to toggle on-demand loading of tabs.

== Designs ==
When you select “Show my windows and tabs from last time” in Prefs -> General, we should show an indented checkbox “Load on demand” that toggles this setting.

== Next Steps & Open Issues ==
* Talk to Paul about estimates & tracking

== Related Bugs & Dependencies ==
* {{bug|648683}}

== Risks ==

== Test Plans ==

== Goals ==

== Non-Goals ==

== Other Stuff ==

[[Category:Features]]
[[Category:Firefox]]
[[Category:Platform]]

__NOTOC__

LandingQueue

2011-01-21T20:14:36Z

Zpao:

'''Check with the sheriff in #developers if you have any questions.'''

{{Queue|
{{QueueEntry
|name=''pcwalton''
|bugs=''{{bug|625454}}''
|approval=''clegnitto''
|available=''Anytime''
}}
}}

Security/Reviews/Firefox4/App Tabs Security Review

2011-01-19T19:34:38Z

Zpao: Created page with "= Security Review Pre-Work = ''Please fill our the short section below prior to the review, and make sure you contact security@mozilla.org to schedule your actual review.'' == O..."

= Security Review Pre-Work =
''Please fill our the short section below prior to the review, and make sure you contact security@mozilla.org to schedule your actual review.''

== Overview ==
We wanted to make sticky tabs that were the same in every window and persisted between sessions. We didn't get the "same in every window" feature done, so they are merely "pinned tabs" which will persist between sessions.

;Background links
* {{bug|575560}} - hook into session restore
* {{bug|563730}} - pinned tabs
* {{bug|551849}} - meta home/app tabs

== Threats ==
''Please list the top 3 security threats you have considered during the design and implementation of this feature.'' Consider attack points as well as code that feels fragile.

I (zpao) only did some of the followup work and have had to deal with app tabs in session restore. I haven't encountered any security threats while doing this work.

What mitigations have you implemented?

None.

= Topics To Discuss During The Review =
== Privacy ==
* Does the feature cache or store data that could strengthen super-cookies?

Since app tabs persist, their session cookies do too (for the current page anyway). App tabs follow the browser.sessionstore.privacy_level pref.

* How are transitions in/out of Private Browsing mode handled?

App tabs are removed & restored just like normal tabs.

* How is "Clear Recent History" handled?

App tabs are treated just like normal tabs here.

= Review comments =
''Notes and bug numbers will be recorded here. Let's try not to spend too much time on any one topic during the meeting.''

Security/Reviews/Firefox4/Deferred Session Restore Security Review

2011-01-19T19:16:38Z

= Security Review Pre-Work =
''Please fill our the short section below prior to the review, and make sure you contact security@mozilla.org to schedule your actual review.''

== Overview ==
The goal here was part of the process towards removing dialogs when quitting Firefox. We wanted to make it possible to restore your previous session at startup instead of being forced to decide when your quitting Firefox.

;Background links
* {{bug|588482}}

== Threats ==
''Please list the top 3 security threats you have considered during the design and implementation of this feature.'' Consider attack points as well as code that feels fragile.

I think this falls under privacy more than security, but since we save cookies by default and we're saving the session without an explicit action of the user, there's a chance login information could be compromised.

What mitigations have you implemented?

There are new preferences for privacy levels that are used instead of the ones used when it's an explicit user action to save the session when quitting.

= Topics To Discuss During The Review =
== Privacy ==
* Does the feature cache or store data that could strengthen super-cookies?

Yes? Like I mentioned, we're saving session cookies for open pages. {{bug|424872}} changed the preference levels to save session cookies for HTTPS pages.

* How are transitions in/out of Private Browsing mode handled?

While in PB mode, you can't restore your previous session.

* How is "Clear Recent History" handled?

It's not... That should probably be fixed...

= Review comments =
''Notes and bug numbers will be recorded here. Let's try not to spend too much time on any one topic during the meeting.''

Security/Reviews/Firefox4/Cascade Session Restore Security Review

2011-01-19T17:40:35Z

= Security Review Pre-Work =
''Please fill our the short section below prior to the review, and make sure you contact security@mozilla.org to schedule your actual review.''

== Overview ==
The goal here was to make the browser more responsive while performing a session restore. We did this by only allowing a few tabs to be loading at a time (after some quick experimentation to determine this would in fact work)

;Background links
* {{bug|586068}}

== Threats ==
''Please list the top 3 security threats you have considered during the design and implementation of this feature.'' Consider attack points as well as code that feels fragile.

Nothing I can think of. We're hanging information we need from each <xul:browser> but not exposing any more information than is otherwise available.

What mitigations have you implemented?

None needed.

= Topics To Discuss During The Review =
== Privacy ==
* Does the feature cache or store data that could strengthen super-cookies?

No more than session restore does otherwise. Nothing particular to this feature.

* How are transitions in/out of Private Browsing mode handled?

Transitions also cascade. However transitioning into PB mode doesn't need to cascade (only 1 tab) so we don't need to hang any data on the tab. Since we didn't hang any data on the tab while in PB mode, there's nothing special that needs to be done transitioning out.

* How is "Clear Recent History" handled?

For tabs that hadn't been properly restored yet, we delete the data we were hanging off each tab and remove the listeners we added.

= Review comments =
''Notes and bug numbers will be recorded here. Let's try not to spend too much time on any one topic during the meeting.''

Security/ReviewTemplate

2011-01-19T17:40:21Z

Zpao: Undo revision 278403 by Zpao (talk)

= Security Review Pre-Work =
''Please fill our the short section below prior to the review, and make sure you contact security@mozilla.org to schedule your actual review.''

== Overview ==
''Describe the goals and objectives of the feature here. What needs or problems does it address?''

;Background links
* feature-tracking bug links
* public specifications (RFC's, W3C specs, IETF Drafts, etc)
* design docs or internal specifications
* data flow or entity relation diagrams
* links to other implementations of the feature

== Threats ==
''Please list the top 3 security threats you have considered during the design and implementation of this feature.'' Consider attack points as well as code that feels fragile.

* Threat 1
* Threat 2
* Threat 3

What mitigations have you implemented?

= Topics To Discuss During The Review =
''Please be prepared to discuss the topics listed at [[Security/ReviewTopics|ReviewTopics]] as they relate to your feature / project. Optionally, you may copy the most relevant questions here and answer them before the review, which could speed up the review meeting.''

= Review comments =
''Notes and bug numbers will be recorded here. Let's try not to spend too much time on any one topic during the meeting.''

Security/ReviewTemplate

2011-01-19T17:39:00Z

Zpao:

= Security Review Pre-Work =
''Please fill our the short section below prior to the review, and make sure you contact security@mozilla.org to schedule your actual review.''

== Overview ==
The goal here was to make the browser more responsive while performing a session restore. We did this by only allowing a few tabs to be loading at a time (after some quick experimentation to determine this would in fact work)

;Background links
* {{bug|586068}}

== Threats ==
''Please list the top 3 security threats you have considered during the design and implementation of this feature.'' Consider attack points as well as code that feels fragile.

Nothing I can think of. We're hanging information we need from each <xul:browser> but not exposing any more information than is otherwise available.

What mitigations have you implemented?

None needed.

= Topics To Discuss During The Review =
== Privacy ==
* Does the feature cache or store data that could strengthen super-cookies?

No more than session restore does otherwise. Nothing particular to this feature.

* How are transitions in/out of Private Browsing mode handled?

Transitions also cascade. However transitioning into PB mode doesn't need to cascade (only 1 tab) so we don't need to hang any data on the tab. Since we didn't hang any data on the tab while in PB mode, there's nothing special that needs to be done transitioning out.

* How is "Clear Recent History" handled?

For tabs that hadn't been properly restored yet, we delete the data we were hanging off each tab and remove the listeners we added.

= Review comments =
''Notes and bug numbers will be recorded here. Let's try not to spend too much time on any one topic during the meeting.''

WeeklyUpdates/2011-01-03

2011-01-03T18:11:54Z

Zpao: /* Introducing New Hires */

[[WeeklyUpdates/2010-12-27|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-01-10|next week »]]

= Video for today's meeting =

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

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

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

'''Monday, 3 January'''

'''Tuesday, 4 January'''

'''Wednesday, 5 January'''

'''Thursday, 6 January'''

'''Friday, 7 January'''

'''Next Week'''

= Product Status Updates =

== Firefox 4 ==
Blocker Summary
* [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED,VERIFIED&chfieldfrom=2010-12-14%2016%3A19&chfield=resolution&query_format=advanced&chfieldto=Now&product=Core&product=Firefox&product=NSPR&product=NSS&product=Toolkit Fixed in Beta 9]
* Beta 9: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0:beta9 50 blockers]
* Beta: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Abeta 279 blockers]
* Final: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Afinal 176 blockers]
** TOTAL: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Afinal,beta 455 blockers]
** nominations: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20blocking2.0%3A%22%3F%22 82 nominations]
** ready to land: [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0:beta,final%20sw:land,checkin 13 blockers ready]

== Firefox 3.6 ==

== Mobile Firefox ==
* (Read the wiki)
* Continuing on beta 4 work
* please continue to provide feedback!

== Thunderbird ==

== 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
|-
|}

= Status Updates By Team =

== Firefox ==

== Platform ==

== Messaging ==

== Mobile ==

== IT ==

== Release Engineering ==

== QA ==

;Automation

;Desktop Firefox

;Browser Technologies
* Fennec: Android nightly build updates were broken last week. Please download the latest nightly build to fix it.

;Services
* "Making Mozilla Better" video completed last week. Planning to present workbook and video for feedback at QA team meeting.
* Kept on top of new crashes last week. One trunk regression was reported. Bugs are on file for top B8 crashes and well as trunk crashes.

;Web QA

== Automation & Tools ==

== Security ==

== Engagement ==

'''PR'''
*[http://www.conceivablytech.com/4815/products/mozilla-says-its-time-to-create-firefox-4-add-ons-now/ Mozilla Says Its Time To Create Firefox 4 Add-Ons Now]
*[http://www.conceivablytech.com/4829/business/firefox-now-ahead-of-ie-in-europe/ Firefox Now Ahead of IE in Europe]

*[http://www.theregister.co.uk/2010/12/28/mozilla_password_snafu/ Mozilla exposes 44,000 passwords]
*[http://www.t3.com/news/mozilla-accidentally-publishes-44000-user-account-details?=52137 Mozilla accidentally publishes 44000 user account details]
*[http://news.cnet.com/8301-30685_3-20026701-264.html Mozilla exposes older user-account database]

'''Events'''

'''Creative Team'''

'''Community Marketing'''

== Support ==

== Metrics ==

== Evangelism ==

== Labs ==

== Developer Tools ==

== Add-ons ==

== Webdev ==

== L10n ==

= Introducing New Hires =

* Mehdi Mulani - Firefox team intern

= Foundation Updates =

= Roundtable =

LandingQueue

2010-09-24T05:43:14Z

Zpao: /* Landing Queue for Mozilla-Central */

= Landing Queue for Mozilla-Central =

*

== Ride-along patches ==

'''Patches must have blocking2.0:beta7+''' ''or explicit "approval for beta 7". betaN+ or general approval are not valid until after b7 is tagged.''

LandingQueue

2010-09-24T00:11:41Z

Zpao: /* Landing Queue for Mozilla-Central */

= Landing Queue for Mozilla-Central =

* zpao (after 7pm PST): {{bug|597933}}, {{bug|598011}}, {{bug|597901}} (all b7 blockers)

== Ride-along patches ==

'''Patches must have blocking2.0:beta7+''' ''or explicit "approval for beta 7". betaN+ or general approval are not valid until after b7 is tagged.''

Security/Reviews/Firefox4

2010-09-22T00:37:46Z

Zpao: /* Front End */

== Pending Reviews ==
Please complete the [[Firefox3/Security_Review_Template|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.

<onlyinclude>
=== Platform ===
{| border="1"
! feature || who || review date || interested
|-
|[[Security/Reviews/Firefox4/AudioAPI_Security_Review|Audio API]] ||David Humphrey || ||
|-
|[[Security/Reviews/Firefox4/mozGetAsFile_Security_Review|canvas.mozGetAsFile]] ||khuey || ||
|-
|[[Security/Reviews/Firefox4/Cookie_Security_Review|Cookie changes]] ||dwitte || ||
|-
|[[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/Desktop_Notifications_Security_Review|Desktop Notifications]] ||dougt || ||
|-
|[[Security/Reviews/Firefox4/FileAPI_Security_Review|File API changes]] ||sicking || || khuey
|-
|[[Security/Reviews/Firefox4/FormData_Security_Review|FormData]] ||sicking || ||
|-
|[[Security/Reviews/Firefox4/HistoryState_Security_Review|History pushState/replaceState]] ||jlebar || ||
|-
|[[Security/Reviews/Firefox4/HTML5_Forms_Security_Review|HTML5 Forms]] || || || khuey
|-
|[[Security/Reviews/Firefox4/HTML5_Parser_Security_Review|HTML5 Parser]] || || ||
|-
|[[Security/Reviews/Firefox4/IndexedDB_Security_Review|IndexedDB]] ||bent || ||
|-
|[[Security/Reviews/Firefox4/Jaegermonkey_Security_Review|Jägermonkey]] || || ||
|-
|[[Security/Reviews/Firefox4/JS_Animation_Scheduling_Security_Review|JS animation scheduling]] ||bzbarsky || ||
|-
|[[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_in_CSS_Security_Review|SVG in CSS Background]] ||dholbert || ||
|-
|[[Security/Reviews/Firefox4/SVG_as_IMG_Security_Review|SVG as IMG]] ||dholbert || ||
|-
|[[Security/Reviews/Firefox4/TabModal_Dialogs_Security_Review|Tab Modal dialogs]] ||dolske || ||
|-
|[[Security/Reviews/Firefox4/TouchEvents_Security_Review|Touch Events]] ||felipe || ||
|-
|[[Security/Reviews/Firefox4/TLS_FalseStart_Security_Review|TLS False Start]] || || ||
|-
|[[Security/Reviews/Firefox4/WebGL_Security_Review|WebGL]] ||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? || ||
|-
|[[Security/Reviews/Firefox4/XHR.mozResponseArrayBuffer_Security_Review|XHR.mozResponseArrayBuffer]] ||vlad || ||
|-
|}

=== Front End ===
{| border="1"
! feature || who || review date || interested
|-
|New Theme (code/bindings) ||gavin || ||
|-
|Auth door-hangers ||dolske || || dao
|-
|Web console || kdangoor || ||
|-
|Jetpack modules||dietrich || ||
|-
|App Tabs ||zpao || || dao
|-
|New Start Page ||mak || ||
|-
|Post-update actions ||rs || ||
|-
|Update billboard changes ||rs || ||
|-
|Download mgr improvements/MIME type defaults ||limi || ||
|-
|Port satchel to js ||dolske || ||
|-
|Tab Panorama ||aza || ||
|-
|Add-on UI ||dietrich || ||
|-
|Places API redesign ||marco || ||
|-
|about:addons ||mossop || ||
|-
|Doorhanger notifications ||gavin || ||
|-
|Sync || || ||
|-
|Cascade Session Restore ||zpao || ||
|-
|Deferred Session Restore ||zpao || ||
|-
| || || ||
|-
|}
</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 || review date || who || review comments
|-
|[[Firefox3.1/SMIL_Security_Review|SVG Animation (SMIL)]] ||dholbert || ||
|-
| || || ||
|-
|}

=== Firefox ===
{| border="1"
! feature || review date || who || review comments
|-
| || || ||
|-
|}

LandingQueue

2010-09-20T20:50:38Z

Zpao: /* Ride-along patches */

= Landing Queue for Mozilla-Central =
* volkmar - {{bug|596455}} and {{bug|595507}}

== Ride-along patches ==
* {{bug|596087}} - update shipped locales for Firefox 4 Beta 7, NPOTB, a=blocking-b7

LandingQueue

2010-09-17T22:15:52Z

Zpao: /* Landing Queue for Mozilla-Central */

= Landing Queue for Mozilla-Central =
* zpao - {{bug|586068}} - b7 blocker!
* volkmar - {{bug|595457}}

== Ride-along patches ==

LandingQueue

2010-09-17T21:35:57Z

Zpao: /* Landing Queue for Mozilla-Central */

= Landing Queue for Mozilla-Central =
* jlebar
* {{bug|586068}} - b7 blocker! - zpao

== Ride-along patches ==

LandingQueue

2010-09-16T18:04:24Z

Zpao: /* Ride-along patches */

= Landing Queue for Mozilla-Central =

== There is no landing queue ==

== Ride-along patches ==
* Taras Glek {{bug|592520}} blocking2.0
* Steve Fink {{bug|593483}} r=gal, a=NPOTB+bustage
* Frank Yan {{bug|593646}}, STRING, a2.0=gavin

LandingQueue

2010-09-10T17:12:24Z

Zpao: /* Landing Queue for Mozilla-Central */

= Landing Queue for Mozilla-Central =

Please add an item containing your name, the bugs you want to land, and what the blocking status of them is to the bottom of the list. After you push, remove yourself from the top of the list. You should only push after consulting with the tree sheriff.

* Your name, bug numbers and their blocker-status here.
* Clint {{bug|591325}} and {{bug|592859}}, both on behalf of jmaher, both NPOTB, both test cleanup an 591325 fixes a regression inside of xpcshell test harness.
* robcee - {{bug|583476}}, {{bug|580454}}, {{bug|586142}}, {{bug|586388}}, {{bug|591937}}, {{bug|593003}}, {{bug|585195}}, {{bug|583476}} - blocking or approved, web console
* dholbert - {{bug|594941}} (fallout from blocker, has approval2.0+)
* zpao - {{bug|588482}} (beta 6 blocker)

* Not around (add yourself back when you're ready):
** tnikkel - plan to land friday, skip me until then
** volkmar - {{bug|561636}}, {{bug|595067}}, {{bug|582277}}, {{bug|556013}} and {{bug|589696}}

== Ride-along patches ==

Add yourself here if you would prefer that some kind soul check your patch in on your behalf. '''And make sure you've read [http://blog.bonardo.net/2010/06/22/so-youre-about-to-use-checkin-needed  So You're About To Use checkin-needed]!'''

* Priority ride-alongs are these [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=blocking2.0%3Abeta6%20:toolkit,firefox%20kw%3Acheckin-needed checkin-needed B6 blockers].

Approval+ ride-alongs:
* khuey {{bug|578096}} a=test-only (Try approves)

Labs/Jetpack/JEP

2010-08-05T21:46:29Z

Zpao: /* Proposals */

= Introduction =

JEP stands for Jetpack Enhancement Proposal. A JEP is a proposal for an enhancement to the Jetpack add-ons development platform. JEPs are a mechanism for collecting ideas and influencing Jetpack development.

Each JEP has a champion who is responsible for writing the proposal and driving the discussion of its merits. Any Jetpack project participant can be a champion. JEPs are numbered by increasing consecutive integers, listed on this page, and discussed in the [http://groups.google.com/group/mozilla-labs-jetpack Jetpack discussion forum].

JEPs are not the only mechanism for influencing Jetpack development, and they're often not the best one. Consider proposing and discussing new APIs and enhancements to existing ones in the [http://groups.google.com/group/mozilla-labs-jetpack Jetpack discussion forum] without writing a JEP, since most changes can be proposed, discussed, agreed upon, and implemented without the heavyweight formal process of a JEP. Other options include:

* file [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Labs&component=Jetpack%20SDK bug reports] about bugs;
* go ahead and implement APIs that don't need to be in the core Jetpack library (or for which it's not clear whether or not they belong in the core), then distribute them to add-on developers via your own website (or, once available, via FlightDeck).

= Process =

To champion a JEP, assign it the next available integer and create a wiki page for it. Name the page after its number, and put it in the /Labs/Jetpack/JEP/ namespace. Refer to existing JEPs for guidance on formatting. Reference the page in the list below.

Assign the new JEP the initial status {{proposed|}}. Announce it and solicit feedback in the [http://groups.google.com/group/mozilla-labs-jetpack Jetpack discussion forum]. Revise it as appropriate in response to feedback.

After discussion of the proposal, if it is approved by Jetpack leads, mark it {{approved|}}. Otherwise, mark it {{declined||}}. Reference bugs tracking the implementation status of an approved proposal in the list of proposals below. Once an approved proposal has been implemented (which may uncover issues that necessitate changes to the proposal), mark it {{implemented|}}.

= Proposals =

{| class="fullwidth-table sortable"
|- style="background:#efefef"
| '''#'''
| '''Title'''
| '''Owner'''
| '''Status'''
| '''Version'''
| '''Bug'''
|-
| 101
| [[Labs/Jetpack/Reboot/JEP/101|No-Restarts]]
| Atul
| {{implemented|}}
| Firefox 3.7a5
| {{bug|542385}}
|-
| 102
| [[Labs/Jetpack/Reboot/JEP/102|Single UI Element]]
| Aza
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.4|SDK 0.4]]/[[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|543585}}
|-
| 102.1
| [[Labs/Jetpack/Reboot/JEP/102.1|Extension Auto-Detection]]
| Daniel
| {{proposed|}}
|
|
|-
| 103
| [[Labs/Jetpack/Reboot/JEP/103|Panel]]
| Myk
| {{approved|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|494238}}
|-
| 104
| [[Labs/Jetpack/Reboot/JEP/104|Simple Storage]]
| Drew
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.4|SDK 0.4]]
| {{bug|548589}}
|-
| 105
| [[Labs/Jetpack/Reboot/JEP/105|Life-cycle]]
| Aza
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|549324}}
|-
| 106
| [[Labs/Jetpack/Reboot/JEP/106|Registered Jetpack URLs]]
| Atul
| {{declined|}}
|
| {{bug|549319}}
|-
| 107
| [[Labs/Jetpack/Reboot/JEP/107|Page Mods]]
| Daniel
| {{proposed|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|546739}}
|-
| 108
| [[Labs/Jetpack/Reboot/JEP/108|Page Worker]]
| Daniel
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.4|SDK 0.4]]
| {{bug|546740}}
|-
| 109
| [[Labs/Jetpack/Reboot/JEP/109|Request]]
| Myk
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|547091}}
|-
| 110
| [[Labs/Jetpack/Reboot/JEP/110|Tabs]]
| Myk
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|549317}}
|-
| 111
| [[Labs/Jetpack/Reboot/JEP/111|Selection]]
| Myk
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|547092}}
|-
| 112
| [[Labs/Jetpack/Reboot/JEP/112|Context Menu]]
| Drew
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.3|SDK 0.3]]
| {{bug|548590}}
|-
| 113
| [[Labs/Jetpack/Reboot/JEP/113|Localization]]
| Gandalf
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|549315}}
|-
| 114
| [[Labs/Jetpack/Reboot/JEP/114|Places]]
| Ddahl
| {{proposed|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|545700}}
|-
| 115
| [[Labs/Jetpack/Reboot/JEP/115|Content Frames]]
| Brian
| {{approved|}}
| [[Labs/Jetpack/SDK/0.5|SDK 0.5]]
| {{bug|549316}}
|-
| 116
| [[Labs/Jetpack/Reboot/JEP/116|Private Browsing]]
| Ehsan
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.4|SDK 0.4]]
| {{bug|503233}}
|-
| 117
| [[Labs/Jetpack/Reboot/JEP/117|URL]]
| Myk
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.4|SDK 0.4]]
| {{bug|564524}}
|-
| 118
| [[Labs/Jetpack/Reboot/JEP/118|JetpackID]]
| Brian
| {{implemented|}}
| [[Labs/Jetpack/SDK/0.4|SDK 0.4]]
| {{bug|553020}}
|-
| 119
| [[Labs/Jetpack/Reboot/JEP/119|ctypes]]
| Dan Witte
| {{proposed|}}
|
|
|-
| 120
| [[Labs/Jetpack/Reboot/JEP/120|Audio]]
| Garrison
| {{proposed|}}
|
|
|-
| 121
| [[Labs/Jetpack/Reboot/JEP/121|SQLite]]
| JCeb
| {{proposed|}}
|
| {{bug|553020}}
|}

= Archive =

These JEPs were written during the experimental phase of the project, when we were developing the prototype. Now that we are no longer working on the prototype, these JEPs are no longer applicable. They are archived here for reference purposes.

* [[Labs/Jetpack/JEP/10|JEP 10 - Clipboard Support]]
* [[Labs/Jetpack/JEP/11|JEP 11 - Simple Persistent Storage]]
* [[User:Rektide/JEP-WebStorage|JEP 11B - Simple Persistent Storage Alternate]]
* [[Labs/Jetpack/JEP/12|JEP 12 - Selections]]
* [[Labs/Jetpack/JEP/13|JEP 13 - Enabling Experimental Jetpack Features]]
* [[Labs/Jetpack/JEP/14|JEP 14 - Menus]]
* [[Labs/Jetpack/JEP/16|JEP 16 - SlideBar]]
* [[Labs/Jetpack/JEP/17|JEP 17 - Page Mods]]
* [[Labs/Jetpack/JEP/18|JEP 18 - Audio]]
* [[Labs/Jetpack/JEP/19|JEP 19 - JavaScript Injection Toolkit]]
* [[Labs/Jetpack/JEP/20|JEP 20 - System Information]]
* [[Labs/Jetpack/JEP/21|JEP 21 - Toolbar]]
* [[Labs/Jetpack/JEP/22|JEP 22 - Places (bookmarks and history)]]
* [[Labs/Jetpack/JEP/23|JEP 23 - Panels]]
* [[Labs/Jetpack/JEP/24|JEP 24 - Settings]]
* [[Labs/Jetpack/JEP/25|JEP 25 - Boosters]]
* [[Labs/Jetpack/JEP/26|JEP 26 - Music]]
* [[Labs/Jetpack/JEP/27|JEP 27 - Video]]
* [[Labs/Jetpack/JEP/28|JEP 28 - The Cuddlefish Minilib]]
* [[Labs/Jetpack/JEP/29|JEP 29 - Jetpack Security Model]]
* [[Labs/Jetpack/JEP/30|JEP 30 - First-run Pages]]
* [[Labs/Jetpack/JEP/30A|JEP 30A - onInstall Hook]]
* [[Labs/Jetpack/JEP/31|JEP 31 - CFX, the Cuddlefish Build/Packaging System]]
* [[Labs/Jetpack/JEP/32|JEP 32 - Awesomebar]]
* [[Labs/Jetpack/JEP/33|JEP 33 - Gadget]]
* [[Labs/Jetpack/JEP/34|JEP 34 - Notification Boxes]]
* [[Labs/Jetpack/JEP/35|JEP 35 - Localization API]]
* [[Labs/Jetpack/JEP/36|JEP 36 - L10n environment]]
* [[Labs/Jetpack/JEP/37|JEP 37 - JPX, the Jetpack build tool]]
* [[Labs/Jetpack/JEP/38|JEP 38 - IconJet]]
* [[Labs/Jetpack/JEP/39|JEP 39 - DNS support]]

Labs/Jetpack/Release Notes/0.4

2010-05-20T21:29:41Z

Zpao: /* About the SDK */

== About the SDK ==

The Jetpack SDK is a set of tools and APIs for building, testing, and packaging Firefox add-ons.

Version 0.4 features ...

Notable enhancements:

*'''Page Worker API''' - The [https://jetpack.mozillalabs.com/sdk/0.4/docs/#module/jetpack-core/page-worker page-worker] module provides a way to create a permanent, invisible page and access its DOM.
*'''Widget API''' - The [https://jetpack.mozillalabs.com/sdk/0.4/docs/#module/jetpack-core/widget widget] module provides a visually consistent way for add-ons to show themselves in the browser.
*'''Simple Storage API''' - The [https://jetpack.mozillalabs.com/sdk/0.4/docs/#module/jetpack-core/simple-storage simple-storage] module provides a way to easily, privately, and persistently store data across application restarts.
*'''Private Browsing API''' - The [https://jetpack.mozillalabs.com/sdk/0.4/docs/#module/jetpack-core/private-browsing private-browsing] module provides access to the private browsing service - detecting if it is active and adding callbacks for transitioning into and out of private browsing mode.

Notable bug fixes:

*

A complete list of changes is available in the [http://hg.mozilla.org/labs/jetpack-sdk/ source code repository].

== Installation ==

First, obtain the SDK in your favorite compression format:

* [https://ftp.mozilla.org/pub/mozilla.org/labs/jetpack/jetpack-sdk-0.4.tar.gz jetpack-sdk-0.4.tar.gz]
* [https://ftp.mozilla.org/pub/mozilla.org/labs/jetpack/jetpack-sdk-0.4.zip jetpack-sdk-0.4.zip]

Once you've got that, just unpack the archive, open the <tt>jetpack-sdk/README.txt</tt> file, and follow its instructions.

== Known Issues ==

*

== Feedback and Bug Reports ==

We'd love to hear any feedback you have regarding this release. Feel free
to post it to the [http://groups.google.com/group/mozilla-labs-jetpack discussion forum] or [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Labs&component=Jetpack%20SDK&version=0.4 file a bug].

Labs/Jetpack/Reboot/JEP/109

2010-05-07T21:06:45Z

Zpao: /* References */

= JEP 109 - XHR =

* Champion: Myk Melez <myk@mozilla.org>
* Status: Accepted/Pre-Production
* Bug Ticket: {{bug|547091}}
* Type: API

= Introduction =

Jetpack extensions should have a simple interface for making the common kinds of asynchronous network requests for which the XMLHttpRequest object is frequently used in both web content and traditional extensions.

The interface should permit cross-domain requests, which are often used by extensions. But it should not provide synchronous requests, which are uncommon, inconsistent with the asynchronous callback-based design of Jetpack APIs, and usually not actually synchronous (except possibly in the case of local file loads, for which a local file API should be used instead.

The first version of the interface should not provide the full configurability of XMLHttpRequest, although it may evolve to include more such functionality in the future. Its initial focus is the smallest set of features that satisfies the needs of the majority of users of XMLHttpRequest.

= Use Cases =

The primary use case is retrieving data from web services.

For example, an extension that provides access to your twitter stream might use this functionality to retrieve your stream from Twitter. And an extension that displays the weather might use it to retrieve data about the weather from Google's or Wunderground's web services.

A secondary use case is sending data to web services.

For example, that Twitter extension might allow you to input a new status that it then sends to Twitter.

= Implementation =

== Module ==

The API is implemented by a Cuddlefish module named "request". The module exports the following symbols:

; Request: <cite>function</cite>; a constructor for Request objects

== Request ==

Request objects perform requests. They are configurable by setting their properties directly or passing a property collection as the <code>options</code> parameter of their constructors and methods.

=== Constructor ===

The Request constructor has the following parameters:

; options: a property collection that configures the object

=== Properties ===

; url: String; the URL of the resource to request
; headers: Object; an unordered collection of name/value pairs representing headers to send with the request
; onComplete: Function; a callback function to call after the request is completed; is passed one parameter, <code>response</code>, which is a Response object
; content: String; the content to send to the server
; contentType: String (default: application/x-www-form-urlencoded); the type of the content to send to the server

If the <code>content</code> property is set to an object, it will be converted to a query string before being sent with the request. The <code>content</code> property is appended to the URL of a GET request and made the body of a POST request.

In the <code>onComplete</code> callback function, <code>this</code> is the Request object.

=== Methods ===

; get: send the request using the HTTP GET method; accepts one parameter, <code>options</code>, a property collection that configures the request; returns the Request object
; post: send the request using the HTTP POST method; accepts one parameter, <code>options</code>, a property collection that configures the request; returns the Request object

== Response ==

Request objects provide information about a server's response to a request. They are passed to a request's onComplete handler upon completion of the request.

=== Properties ===

; text: String; the content of the response as plain text
; xml: DOMDocument; for XML responses (text/xml), the content of the response as a DOM document
; json: Object; for JSON responses (application/json), the content of the response as JavaScript object
; status: String; the HTTP response status code
; statusText: String; the HTTP response status line
; headers: Object; the HTTP response headers

The <code>xml</code> and <code>json</code> properties should be lazily computed.

= Examples =

Get a web page and log it to the console:

const Request = require("request").Request;
new Request({
url: "http://example.com/",
onComplete: function() console.log(this.response.text)
}).get();

= Issues =

= References =

* [https://developer.mozilla.org/en/XMLHttpRequest XMLHttpRequest]
* [http://api.jquery.com/jQuery.ajax/ jQuery.ajax()]
* Prototype
** [http://api.prototypejs.org/ajax/ajax/request/ Ajax.Request]
** [http://api.prototypejs.org/ajax/ajax/response/ Ajax.Response]
* [http://mootools.net/docs/core/Request/Request MooTools Request]

Firefox/Projects/Jetpack

2010-04-19T17:46:30Z

Zpao: /* Status */

__NOTOC__

Work with the Jetpack team to implement a core set of modules. This is currently looking like JEPs 102 - 116, over releases 0.3, 0.4 and 0.5.

== Status ==

<onlyinclude>
'''IN FLIGHT''' JEPs are owned, and in development.
</onlyinclude>

'''Team:'''
* Lead: Dietrich
* Members: Drew, Paul, Felipe, Marco

'''Modules owned by Fx-team members'''
{| style="width: 100%" class="fullwidth-table sortable"
|-
| style="background:#efefef" | '''JEP'''
| style="background:#efefef" | '''Module'''
| style="background:#efefef" | '''Owner'''
| style="background:#efefef" | '''Target'''
| style="background:#efefef" | '''Status'''
| style="background:#efefef" | '''Notes'''
|-
| 102
| Single UI (Addon Bar)
| Marco/Dietrich
| 0.4
| on track
| Had a meeting with all the UX and Jetpack people about this. Boriss estimating full design delivery by 5/1. Going to implement infrastructure first, estimating two weeks for basic "Phase 1" implementation, as of 4/16.
|-
| 104
| Simple storage
| Drew
| 0.5
| blocked
| Blocked by {{bug|553020}} (which is at-risk for 0.3). Estimates 4 weeks of work for implementation.
|-
| 105
| Lifecycle
| Dietrich
| 0.4
| planning stage
| {{bug|549324}}. Blocked by {{bug|553020}} (which is at-risk for 0.3), and on the EM's support for reboot-less extension installs ({{bug|555349}}. Estimate 2 weeks for implementation.
|-
| 108
| Page Worker
| Felipe
| 0.4
| on track
| Felipe has a first-cut patch up.
|-
| 109
| Request
| Paul
| 0.4
| planning stage
| Some implementation already done. Paul estimates 2 weeks for implementation.
|-
| 112
| Context menu
| Drew
| 0.3
| on-track
| {{bug|548590}}, has patch, in reviews.
|-
| 114
| Places
| Marco
| 0.4
| in-progress
| Core work done by ddahl, but needs API review for Jetpack API consistency. Marco is out on vacation, but said some API and code work still needs to happen, but nothing major. Still targeting 0.4 for now.
|-
| 116
| private browsing
| Paul
| 0.4
| in-progress
| Paul talked with Myk about the spec, estimates 2 weeks for implementation. Will require some coordination with Drew to extract some functionality into a core module.
|}

'''Other modules, assist if necessary'''
{| style="width: 100%" class="fullwidth-table sortable"
|-
| style="background:#efefef" | '''JEP'''
| style="background:#efefef" | '''Module'''
| style="background:#efefef" | '''Owner'''
| style="background:#efefef" | '''Target'''
| style="background:#efefef" | '''Status'''
| style="background:#efefef" | '''Notes'''
|-
| 103
| Panels
| Myk
| 0.3
| at risk
| ping enn to see if need anything
|-
| 106
| Registered urls
| Brian
| 0.4
| on track
|
|-
| 107
| Page mods
| Nicolay
| tbd
| on track
| Myk's working w/ him
|-
| 110
| Tabs
| Atul
| 0.3
| on track
| might need owner for post-0.3 development
|-
| 111
| Selection
| Eric Jung
| 0.3
| on track
|
|-
| 113
| Localization
| Gandalf
| 0.3
| on track
| for client, need webdev for server, likely later release
|-
| 115
| Content frames
|
|
| completed
| spec, no impl
|}

== Goals ==

* Help Labs implement modules for JEPs 102 - 116.
* Bonus goal: Drive code reviews core Jetpack code ({{bug|551311}})

== Roadmap ==

* Fri Apr 09
** Core JEPs selected, owners found, estimates given
* Fri Apr 16 (0.3 freeze on 18th)
** Drew mostly finished with Context Menu module for 0.3
* Fri Apr 23 (0.3 release on 26th)
** Paul finishes Private Browsing module for 0.4
** Felipe finishes Page Worker module for 0.4
** Dietrich finishes Lifecycle module for 0.4
* Fri Apr 30
** Dietrich finishes initial implementation of SingleUI module for 0.5
* Fri May 07
** Marco finishes Places module for 0.4
** Paul finishes Request module for 0.4
* Fri May 14 (0.4 freeze on 18th)
* Fri May 21 (0.4 release on 26th)
** Drew finishes Storage module for 0.5
* Fri May 28
* Fri Jun 04
* Fri Jun 11
* Fri Jun 18 (0.5 freeze)
* Fri Jun 25 (0.5 release on 26th)

Not slotted in yet:
* Single UI module completion, no design delivery from UX until 5/1, will estimate then.

== Background ==

Jetpack's architecture under versions 0.8 and earlier (now called the Jetpack Prototype) is being phased out for a new architecture called the Jetpack SDK. Check the SDK [https://jetpack.mozillalabs.com/sdk/latest/docs docs] and [[Labs/Jetpack/Reboot|wiki]] for details, but briefly, the differences between the two:

* '''The Jetpack SDK is a framework for making (traditional) extensions.'''
* "Jetpacks" produced under the SDK are actually XPIs. They're real extensions. Under the Prototype they were single JS files.
* Since jetpacks are now extensions, it no longer makes sense to say "I made a jetpack." It's more like, "I made an extension using Jetpack."
* Jetpack itself is no longer an extension. It no longer makes sense to say, "I installed Jetpack."
* The SDK is basically a toolchain, runtime, and API -- a framework.
* The SDK is very loosely integrated with Firefox. The runtime is bundled in each XPI. Aside from changes required to support the SDK's high-level APIs, the runtime doesn't require any significant changes to Firefox or Gecko. A [https://bugzilla.mozilla.org/show_bug.cgi?id=542385 (re)loadable extension mechanism] is being worked on, but it's like icing on the cake.
* The SDK has a security model, the Prototype didn't.
* Roughly speaking, there are two layers of APIs under the SDK. There's a low-level, chrome-privileged layer that wraps the platform. And there's a high-level, secure, low surface area, and friendly layer that builds on the lower. It's the higher layer that might be thought of as "the Jetpack API," but it's entirely possible to use the lower to build an extension.
* The Bespin IDE of the Prototype will be replaced with a contracted-out in-browser IDE called "[[Labs/Jetpack/FlightDeck|FlightDeck]]." (Maybe you've heard of it?) FlightDeck provides a nice UI to the SDK's toolchain. It will be available as a Web app.

== Related Links ==

* [[Labs/Jetpack/Reboot|Jetpack SDK wiki]]
* [[Labs/Jetpack/Weekly_Meeting|Jetpack team weekly meetings wiki]]
* [irc://irc.mozilla.org/jetpack #jetpack]
* There's a Jetpack drivers mailing list. Ping adw or Daniel Buchner if interested.
* [[Labs/Jetpack/Design_Guidelines|Module coding guidelines]]

Labs/Jetpack/Reboot/JEP/116

2010-04-12T17:59:15Z

Zpao: /* Events */

== JEP 116 - Private Browsing ==

* Champion: Ehsan Akhgari - ehsan@mozilla.com
* Status: Under Review
* Bug Ticket:
* Type: API
* Difficulty: 1

=== Proposal ===

This JEP describes an API for querying the current private browsing mode status, and responding to its changes. In particular, it gives a Jetpack a property for getting the current status of the private browsing mode and entering or leaving the private browsing mode, and for registering event handlers for getting notified about private browsing mode transitions, and canceling them if needed.

==== Properties ====

This JEP provides the <code>active</code> property which allows Jetpacks to query the current status of the private browsing mode. If the private browsing mode is active, the value of the <code>active</code> property will be false, otherwise it will be true.

<pre class="brush:js;">
var pb = require("private-browsing");

var insidePB = pb.active;

if (insidePB) {
// We're inside the private browsing mode
} else {
// Private browsing is not activated
}
</pre>

Jetpacks can also set the <code>active</code> property to change the current status of the private browsing mode. Setting this property to true will tell Firefox to enter the private browsing mode, and setting it to false will tell Firefox to leave the private browsing mode. Setting this property to its current value doesn't have any effect.

<pre class="brush:js;">
var pb = require("private-browsing");

// Enter the private browsing mode
pb.active = true;

// Do something...

// Leave the private browsing mode
pb.active = false;
</pre>

==== Events ====

The events are used for Jetpacks which want to respond to changes made to the private browsing status by the user or other Jetpacks/extensions.

The first class of event handlers are used to notify Jetpacks about changes in the global private browsing status. These event handlers can be used like this:

<pre class="brush:js;">
var pb = require("private-browsing");

pb.onActivate = function() {
// Oh, the private browsing mode has just started!
};

pb.onDeactivate = function() {
// The private browsing mode just ended!
};
</pre>

Some Jetpacks may need to cancel the transition of the private browsing mode in certain cases. Such Jetpacks can use the following event handlers. The activation or deactivation of the private browsing mode will be canceled '''only''' if these event handlers explicitly cancel the event. It should be noted that if another Jetpack or extension also implements these event handlers and cancels a transition, the event handler on the remaining Jetpacks will not be called.

<pre class="brush:js;">
var pb = require("private-browsing");

pb.onBeforeActivate = function(pb) {
// We don't want to allow entering the private browsing mode.
pb.cancel();
};

pb.onBeforeDeactivate = function(pb) {
// We don't want to allow leaving the private browsing mode.
pb.cancel();
};
</pre>

=== Difficulty ===

Rating: '''Easy'''

=== Key Issues ===

None so far!

=== Dependencies & Requirements ===

This JEP is not dependent on any other JEPs.

=== Internal Methods ===

The JEP will be implemented in terms of nsIPrivateBrowsingService for implementation of the <code>active</code> property, and nsIObserverService for implementation of event handlers.

=== Use Cases ===

* Provide a different appearance for the Jetpack when the private browsing mode is active.
* Avoid writing data containing the web page URLs and domains that the user has visited inside the private browsing mode.
* Prevent the transition of the private browsing mode if a non-resumable and non-cancelable operation is in progress.

Firefox/Projects/Weave

2010-03-29T17:36:41Z

Zpao: /* Requirements */

__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
* QA: tchung, tracy

== 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 ==
* (mostly complete) Weave 1.2
* (complete?) Draft schedule for inclusion
* Audit current API usage
** (complete) Places ({{bug|548382}})
** (complete) Password Manager ({{bug|548383}})
** (complete) Form Manager ({{bug|548384}})
** (incomplete) Prefs ({{bug|548385}})
** (complete) Firefox Tabs ({{bug|548386}})
** (mostly complete) Fennec Tabs ({{bug|548387}})

== Requirements ==
* Server side must be scalable to handle X00 million users

== 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/Weave

2010-03-29T05:30:04Z

Zpao: /* Timeline / Milestones */

__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
* QA: tchung, tracy

== 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 ==
* (mostly complete) Weave 1.2
* (complete?) Draft schedule for inclusion
* Audit current API usage
** (complete) Places ({{bug|548382}})
** (complete) Password Manager ({{bug|548383}})
** (complete) Form Manager ({{bug|548384}})
** (incomplete) Prefs ({{bug|548385}})
** (complete) Firefox Tabs ({{bug|548386}})
** (mostly complete) Fennec Tabs ({{bug|548387}})

== 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

2010-03-03T20:20:00Z

Zpao:

__NOTOC__
{| class="fullwidth-table sortable" border="1" cellspacing="0" cellpadding="2"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Goal'''
| '''ETA'''
| '''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
| 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.
| 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|Stabilize Jetpack API]]
| adw
| Make sure Jetpack's needs in Firefox/Platform are taken care of
|
| {{: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
| 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
| 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
| Waiting for SR.
|-
| [[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 is taking longer than expected
| Patches for app update r+'d. Test changes waiting on review. Still hoping to finish this soon.
|-
| Billboard should extend to available space and the update UI should be the same width for all locales {{bug|480178}}
| rs
| Simplify verification of the billboard for all locales and all platforms and make the UI look *better*.
| TBD
| Client side looks good and has UI review +. Still need to verify remote content sizing for all platforms.
|}

= 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.
|
|
|
|-
| Print preview in a separate window
| rflint
|
| Remove the fragile XBL binding and create a separate XUL document
|
| 1.9.3
|
|}

*[[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/Weave

2010-03-03T20:00:41Z

Zpao:

Firefox/Projects/Weave

2010-03-03T19:57:59Z

Zpao:

__NOTOC__
= Weave Integration =
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.

== Team ==

== 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

2010-03-01T20:19:52Z

Zpao: /* Active Projects */

= 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|Weave (improve extension, begin integration)]]
| mconnor (lead), zpao (Firefox)
| faaborg, boriss, ragavan, thunder
| Add bookmark sync to Firefox 3.7
| Ongoing
| Future (on m-c)
| zpao is working on improving API usage, data syncing behavior
|-
| [[Firefox/Projects/Extension_Manager_Redesign|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
| {{:Firefox/Projects/Extension Manager Redesign|/Extension Manager Redesign}}
|-
| [[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/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|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]]
| Unfocused
| limi, gavin, ashughes (QA)
| Make it possible to switch tabs using the AwesomeBar 
| March 2009
| 3.7a1
| Waiting for SR.
|-
| [[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
| ddahl
| Perform action after update based on update xml attribute.
| Client side is taking longer than expected
| 1.9.3
| Patches for app update r+'d. Test changes waiting on review. Still hoping to finish this soon.
|-
| Billboard should extend to available space and the update UI should be the same width for all locales {{bug|480178}}
| rs
| faaborg
| Simplify verification of the billboard for all locales and all platforms and make the UI look *better*.
| TBD
| 1.9.1
| Client side looks good and has UI review +. Still need to verify remote content sizing for all platforms.
|}

= 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/Weave

2010-03-01T18:32:26Z

Zpao:

== Summary ==

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.

== Current Status ==

Paul is working on various Weave improvements, working with peers to audit API usage.

Design work for the front end has gone through a few iterations and reviews, and mconnor is making regular changes based on the feedback.

== Next Steps ==

Adjust API usage, move code around to make integration easier.

== Related Bugs ==

== Team ==

*'''Project Lead''': mconnor
*'''Developer''': zpao, Mardak
*'''UX''': faaborg, boriss

== Designs ==

== Goals/Use Cases ==

* Get Weave extension prepared for mozilla-central. Includes:
** Auditing API usage by appropriate peers
** Making necessary UI changes
** Moving code, integrating build system
** Writing tests

== Non Goals ==

* Re-implementing Weave

Labs/Jetpack/JEP/21

2010-01-28T22:13:37Z

Zpao: /* Initial Implementation API */

== JEP 21 - jetpack.toolbar ==

* Champion: David Dahl <ddahl at mozilla dot com>
* Status: Planning
* Type: API Track
* Created: 27 July 2009
* Reference Implementation: jetpack.toolbar
* [[Labs/Jetpack/JEPs|JEP Index]]

=== Introduction and Rationale ===

The 'toolbar' namespace will provide Jetpack developers the ability to modify toolbars in chrome space in the browser.

=== Proposal ===

Create an easy way to get a handle on the navigation toolbar, the bookmarks toolbar. Provide an elegant API to add, modify and remove items for each bar, as well as hiding and showing the toolbars.

<pre class="brush:js;">
// get an abstracted "jetpacky" nav bar object / bookmarks bar object
var navBar = jetpack.toolbar.navigation();

// return the array of 'toolbarbutton' objects
navBar.children();

// remove the 3rd child:
navBar.children()[2].remove();

// get a button labeled 'my button'
var btn = navBar.find({label:"my button"});

// replace the function bound to the button
btn.click = function ClickerFunk(){ alert("I clicked my button");};

// number of toolbar buttons: acts like an array
navBar.length;

// make a button
var button = {
// 'self' would refer to the button
// 'self.toolbar' would refer to the parentNode
id: 73, // or "foobutton"
label: "my button",
imageDefault: "http://mybutton.com/image.png",
imageAlternate: "http://mybutton.com/imageAlt.png",
click: function(){self.image(self.imageAlternate);},
mouseover: function(){jetpack.audio.play(self.customAttribute);},
customAttribute: "http://mybutton.com/yelling.ogg"
};

// change the image displayed
button.image("http://foobar.com/foopy.png");

// move the button
button.moveRight(); // move to the right 1 slot

button.moveLeft(3); // move to the left 3 slots

// .append() and .prepend():

//append button to the end of the toolbar
navBar.append(button);

// prepend button to the beginning of the toolbar
navBar.prepend(button);

// find a button by label or other string or number attribute
var anotherButton = navBar.find({label:'their button'});

// append button to toolbar after 'anotherButton'
navbar.append(button, anotherButton);

// find and append after the button labeled "their button"
navbar.append(button, 'their button');

// get the bookmarks toolbar
var bookmarksBar = jetpack.toolbar.bookmarks();

//make a bookmark button
var bookmarkButton = {label: "GrouchoMarx.com",
url:"http://grouchomarx.com/",
image: "http://groucho.com/image.png",
type: 'bookmark' // the default
}

// bookmark and feed buttons use the same methods to attach, move, find vis a vis the toolbar

var feedButton = { label: "my RSS feed",
image: "http://myfeed.com/feed.png",
url: "http://www.rssfeed.com/rss.xml",
type: "feed"
};

// make an entirely new toolbar
var newToolbar = { id: 'myGreatAppToolbar'};

// append it to the toolbar box
jetpack.toolbar.append(newToolbar);

jetpack.toolbar.prepend(newToolbar);
</pre>

=== Initial Implementation API ===

For the initial implementation, the api will be restricted to:

<pre class="brush:js;">
jetpack.future.import("toolbar");

// Create button options. This can be done in a separate object like this,
// or passed inline to append.
var myButton = {
id: "fooButton",
label: "FOO!",
tooltip: "Click on my to do something.",
image: "http://www.mozilla.org/favicon.ico",
click: function(event) { console.log("FOO! has been clicked") }
}

// Append the button to the toolbar
jetpack.toolbar.navigation.append(myButton);

// Remove the button from the toolbar
jetpack.toolbar.navigation.remove("fooButton");

// Create button options for the bookmarks toolbar.
var myOtherButton = {
id: "barButton",
label: "BAR!",
tooltip: "Go to http://www.mozilla.org",
image: "http://www.mozilla.org/favicon.ico",
url: "http://www.mozilla.org"
}

// Append the button to the toolbar
jetpack.toolbar.bookmarks.append(myOtherButton);

// Remove the button from the toolbar
jetpack.toolbar.bookmarks.remove("barButton");
</pre>

Releases/Firefox 3.6RC1/Test Plan:FFTs

2010-01-20T00:35:34Z

Zpao: /* FFT Results (full run) */

[https://wiki.mozilla.org/Releases/Firefox_3.6RC1/Test_Plan 3.6RC1 Test Plan]

= Firefox 3.6 RC1 FFTs =
We are going to run a subset of the FFTs on a combination of Windows XP and Windows 7. We'll prioritize Windows, for now. Get your [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6rc1-candidates/build1/ '''3.6 RC1 builds here'''].

== FFT Results (full run) ==
We'll divide the full functional tests in several choice sections so multiple people can join in and help. Please alternate sections between operating system versions, for example run some on XP and some on Windows 7, some on Mac OS 10.5 and some on 10.6.

# [https://litmus.mozilla.org/run_tests.cgi?test_run_id=92 Litmus FFT Testrun]
# Date: 01/07 - 01/?
# Build Versions:
* Windows:
** Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6 (.NET CLR 3.5.30729)
**Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6 (.NET CLR 3.5.30729)
* Mac:
** Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6
** Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6
* Linux:
** Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6
**

'''Assignments'''
*1) Section: Installation --> General:
** Windows: retornam '''Pass'''
** Mac OS: Tracy - '''Pass''' - 10.6
** Linux: Dietrich - '''Fail'''
*** migration bugs: {{bug|539133}}, {{bug|539139}}
*** find bar sound: {{bug|539388}}
*** [https://litmus.mozilla.org/single_result.cgi?id=230895 weird geolocation test failure]
** Notes:
*2) Section: Awesome Bar:
** Windows: retornam '''Pass'''
** Mac OS: abillings '''Pass''' - Aravind '''Fail'''
***Context Menu: Undo - {{bug|540590}}
*** Notes: [https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=8480 Test Case 8480] and [https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=8543 Test Case 8543] fail.
** Linux: tester ddahl - Aravind
** Notes: Run on Windows 7, found an issue with https://litmus.mozilla.org/show_test.cgi?id=8950 [screencast] http://screencast.com/t/YjBhZjIxYmU
*3) Section: Tabbed Browsing:
** Windows: abillings - '''Pass'''
** Mac OS: Aravind - '''Pass'''
** Linux: Aravind - '''In Progress'''
** Notes:
*4) Section: Search --> Find in Page:
** Windows: retornam '''Pass'''
** Mac OS: Tracy - '''Pass''' - 10.4
** Linux: tester
** Notes: Follow pattern above, alternating between XP and Windows 7
*5) Section: Bookmarks --> History:
** Windows: retornam - '''PASS'''
** Mac OS: Aravind - '''Fail'''
***Regression Bug : {{bug|440093}}
***New Bugs : {{bug|540595}}, {{bug|540593}}
** Linux: beltzner - '''Fail'''
** Notes: Linux
*** {{bug|540474}} - drag and drop from Bookmarks Menu to desktop is fragile; not a regression
*** {{bug|540493}} - drag and drop doesn't work for History items
*6) Section: Add-ons Manager --> Lightweight Themes
** Windows: abillings - '''Pass'''
** Mac OS: Tracy - '''Pass''' - 10.4 - Aravind - '''Pass'''
** Linux: beltzner - '''Fail'''
** Notes: Windows
*** Run on XP
** Notes: Linux
*** {{bug|539862}} filed for failure w/drag&drop of theme

*7) Section: Downloading:
** Windows: gmontagu - Run on XP.'''PASS: 69; NOT RUN: 25; UNCLEAR: 19; FAIL 1'''
** Mac OS: shorlander - '''Fail''' - 10.6 - Aravind '''Pass'''
** Linux: Aravind - '''In Progress'''
** Notes:
*8) Section: Printing:
** Windows: tchung - '''FAIL'''
** Mac OS: tchung - '''PASS'''
** Linux: tester
** Notes:
*** Windows printing is a mess.
*** Filed {{Bug|539339}} - Printing websites with multiple divs cause ill printing issues
*** Filed {{Bug|539322}} - Printing formfields on Windows does not show text in buttons nor dropdown arrows
*** Filed {{Bug|539365}} - Lightweight themes text-shadow exists on print-preview screen
*9) Section: Password Manager --> Private Browsing:
** Windows: juanb, XP(vm) - '''PASS'''
** Mac OS: Tracy - '''Pass''' - 10.6 - Aravind - '''Pass'''
** Linux: juanb - Ubuntu 9.10 - '''PASS'''
** Notes: XP
*10) Section: Cookies, Plug Ins, Layout, Content Handling:
** Windows: marcia - Win7 - '''Pass, individual failures noted below'''
** Mac OS: Tracy - '''Fail''' - 10.6
** Linux: juanb, beltzner - '''Pass'''
*** Notes: Linux
**** {{bug|495609}} and {{bug|492200}} resulted in expected APNG errors
**** {{bug|539866}} - drag and drop XPI isn't compatible with Firefox 3.6
**** {{bug|539871}} - Yahoo! Mail mailto: handler doesn't accept body: and subject: values
**** In general, the plugins tests for Linux need some simplification. They are very time consuming to setup.
** Notes: Mac 10.6:
*** {{bug|539763}} - Remnant across all tabs from Windows Media Player Test
*11) Section: Security, Session Store:
** Windows: marcia - Security '''Pass'''
** Windows: rstrong - Session Store '''Fail'''
*** Notes: Windows 7, 92% completed - didn't test forms due to issues that I passed to juanb.
** Mac OS: Tracy, Aravind '''Fail'''
***{{bug|540602}}, {{bug|540610}}
** Linux: zpao, juanb - '''(mostly) PASS'''
*** Fail: https://litmus.mozilla.org/show_test.cgi?id=9299
*** '''Still need to run:''' [https://litmus.mozilla.org/show_test.cgi?id=8214 8214] [https://litmus.mozilla.org/show_test.cgi?id=9012 9012] [https://litmus.mozilla.org/show_test.cgi?id=9013 9013] [https://litmus.mozilla.org/show_test.cgi?id=9015 9015] [https://litmus.mozilla.org/show_test.cgi?id=9031 9031] [https://litmus.mozilla.org/show_test.cgi?id=9330 9330] [https://litmus.mozilla.org/show_test.cgi?id=9323 9323] [https://litmus.mozilla.org/show_test.cgi?id=9383 9383] [https://litmus.mozilla.org/show_test.cgi?id=9384 9384]
** Notes: Windows 7
*12) Section: Online/Offline Events, Technical Tools:
** Windows: gmontagu '''Pass'''
** Windows 7: marcia - Ran Technical Tools - '''Pass'''
** Mac OS: mak - '''PASS'''(but missing Online/Offline ones from 6 on(campd.org is timing out)) - 10.6
** Linux: juanb - Ubuntu 9.10(vm) - '''Pass'''
*** Notes: I edited several test cases in the ''offline'' section; and I found a bug with clearing the cache which is present in 3.5.7, and which had already been filed.
** Notes: Run on XP. Online/Offline Events: Test cases 2 to 9: '''BROKEN'''. Technical Tools: no issues.
*13) Section: Multitouch (not part of FFT):
** Windows: juanb - Windows 7 - '''PASS'''
** Mac OS: mak - '''pass''' - 10.6 (https://litmus.mozilla.org/show_test.cgi?id=9243)
** Linux: n/a
** Notes: This is a separate test group, and can only be used on machines with a touch screen. Please ask Marcia or juanb for details.
*14) Uninstall:
**Windows:retornam '''pass'''
**Mac OS: mak - '''Pass''' - 10.6
**Linux : juanb - Ubuntu 9.10 - '''PASS'''

== Mozmill Tests ==
All the tests run with Mozmill have been synced with Litmus.

* Windows Vista [[http://pastebin.mozilla.org/696326 results]]
* OS X 10.6 [[http://pastebin.mozilla.org/696333 results]]
* OS X 10.4 [[http://pastebin.mozilla.org/696452 results]]

== Litmus Test Case Failures on Windows 7 ==
*Layout
**https://litmus.mozilla.org/single_result.cgi?id=228900 - Fails on Windows Vista and Mac. mw22 indicates Bug 463465 was not checked into 1.9.2. So this bug should probably be nominated for 1.9.2.1

*Cookies
**https://litmus.mozilla.org/single_result.cgi?id=229631

*Content Handling
**https://litmus.mozilla.org/single_result.cgi?id=231819

*Security
**https://litmus.mozilla.org/single_result.cgi?id=230801
**https://litmus.mozilla.org/single_result.cgi?id=230798
**https://litmus.mozilla.org/single_result.cgi?id=230798
**https://litmus.mozilla.org/single_result.cgi?id=230796
**https://litmus.mozilla.org/single_result.cgi?id=230794
**https://litmus.mozilla.org/single_result.cgi?id=230785
**https://litmus.mozilla.org/single_result.cgi?id=232421

== Crashes during FFT testing ==
*Windows 7
**http://crash-stats.mozilla.com/report/index/194ac4a1-15ab-49f4-9367-711742100108 - May be [https://bugzilla.mozilla.org/show_bug.cgi?id=536272 Bug 536272]

**http://crash-stats.mozilla.com/report/index/bp-291dd72c-fa33-4b8d-bd1a-839d92100111
***[https://bugzilla.mozilla.org/show_bug.cgi?id=535873 Bug 535873]
***Now we have a set of STR to reproduce this crasher.
***Plugin is only compatible with Firefox 2.0. Filed [https://bugzilla.mozilla.org/show_bug.cgi?id=539282 Bug 539282] to blocklist it and remove it from PFS.

== Extension Related Issues? ==
*Installed Skype 4.0 which includes Skype for Firefox Browser Highlighter. Extension version is 3.3.0.3971. Experienced some freezes after this installation.
**Most likely [https://bugzilla.mozilla.org/show_bug.cgi?id=530995 Bug 530995 Skype addon causes perf hit]

== Let's Not Forget ==
Please make sure to check the features you signed up to test, because some of these features' tests may not be in the FFT, such as ''multitouch''. For reference, check the areas that went in 3.6 and make sure you run the tests you created for your features:

# [https://wiki.mozilla.org/QA/Firefox3.6/TestPlan#Firefox_Features: 3.6 Fx Features]
# [https://wiki.mozilla.org/QA/Firefox3.6/TestPlan:Feature_Improvements Feature Improvements]

Releases/Firefox 3.6RC1/Test Plan:FFTs

2010-01-14T23:59:05Z

Zpao: /* FFT Results (full run) */

[https://wiki.mozilla.org/Releases/Firefox_3.6RC1/Test_Plan 3.6RC1 Test Plan]

= Firefox 3.6 RC1 FFTs =
We are going to run a subset of the FFTs on a combination of Windows XP and Windows 7. We'll prioritize Windows, for now. Get your [ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6rc1-candidates/build1/ '''3.6 RC1 builds here'''].

== FFT Results (full run) ==
We'll divide the full functional tests in several choice sections so multiple people can join in and help. Please alternate sections between operating system versions, for example run some on XP and some on Windows 7, some on Mac OS 10.5 and some on 10.6.

# [https://litmus.mozilla.org/run_tests.cgi?test_run_id=92 Litmus FFT Testrun]
# Date: 01/07 - 01/?
# Build Versions:
* Windows:
** Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6 (.NET CLR 3.5.30729)
**Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6 (.NET CLR 3.5.30729)
* Mac:
** Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6
** Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2) Gecko/20100105 Firefox/3.6
* Linux:
**
**

'''Assignments'''
*1) Section: Installation --> General:
** Windows: retornam '''Pass'''
** Mac OS: Tracy - '''Pass''' - 10.6
** Linux: Dietrich - '''Fail'''
*** migration bugs: {{bug|539133}}, {{bug|539139}}
*** find bar sound: {{bug|539388}}
*** [https://litmus.mozilla.org/single_result.cgi?id=230895 weird geolocation test failure]
** Notes:
*2) Section: Awesome Bar:
** Windows: retornam '''Pass'''
** Mac OS: abillings '''Pass''' - Aravind '''Pass'''
*** Notes: [https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=8480 Test Case 8480] and [https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=8543 Test Case 8543] fail.
** Linux: tester
** Notes: Run on Windows 7, found an issue with https://litmus.mozilla.org/show_test.cgi?id=8950 [screencast] http://screencast.com/t/YjBhZjIxYmU
*3) Section: Tabbed Browsing:
** Windows: abillings - '''Pass'''
** Mac OS: Aravind - '''Pass'''
** Linux: tester
** Notes:
*4) Section: Search --> Find in Page:
** Windows: retornam '''Pass'''
** Mac OS: Tracy - '''Pass''' - 10.4
** Linux: tester
** Notes: Follow pattern above, alternating between XP and Windows 7
*5) Section: Bookmarks --> History:
** Windows: retornam - '''PASS'''
** Mac OS: Aravind - '''Pass'''
** Linux: tester
** Notes:
*6) Section: Add-ons Manager --> Lightweight Themes
** Windows: abillings - '''Pass'''
** Mac OS: Tracy - '''Pass''' - 10.4 - Aravind - '''Pass'''
** Linux: beltzner - ''in progress''
** Notes: Run on XP
*7) Section: Downloading:
** Windows: gmontagu - Run on XP.'''PASS: 69; NOT RUN: 25; UNCLEAR: 19; FAIL 1'''
** Mac OS: shorlander
** Linux: tester
** Notes:
*8) Section: Printing:
** Windows: tchung - '''FAIL'''
** Mac OS: tchung
** Linux: tester
** Notes:
*** Windows printing is a mess.
*** Filed {{Bug|539339}} - Printing websites with multiple divs cause ill printing issues
*** Filed {{Bug|539322}} - Printing formfields on Windows does not show text in buttons nor dropdown arrows
*** Filed {{Bug|539365}} - Lightweight themes text-shadow exists on print-preview screen
*9) Section: Password Manager --> Private Browsing:
** Windows: juanb, XP(vm) - '''PASS'''
** Mac OS: Tracy - '''Pass''' - 10.6 - Aravind - '''In Progress'''
** Linux: juanb - Ubuntu 9.10 - '''PASS'''
** Notes: XP
*10) Section: Cookies, Plug Ins, Layout, Content Handling:
** Windows: marcia - '''in progress'''
** Mac OS: Tracy - '''Fail''' - 10.6
** Linux: tester
** Notes: Windows 7
** Notes: Mac 10.6:
*** {{bug|539763}} - Remnant across all tabs from Windows Media Player Test
*11) Section: Security, Session Store:
** Windows: marcia - '''in progress'''
** Mac OS: Tracy
** Linux: zpao - '''in progress'''
** Notes: Windows 7
*12) Section: Online/Offline Events, Technical Tools:
** Windows: gmontagu '''Pass'''
** Windows 7: marcia - Ran Technical Tools - '''Pass'''
** Mac OS: mak - '''PASS'''(but missing Online/Offline ones from 6 on(campd.org is timing out)) - 10.6
** Linux: juanb - '''in progress'''
** Notes: Run on XP. Online/Offline Events: Test cases 2 to 9: '''BROKEN'''. Technical Tools: no issues.
*13) Section: Multitouch (not part of FFT):
** Windows: juanb
** Mac OS: mak - '''pass''' - 10.6 (https://litmus.mozilla.org/show_test.cgi?id=9243)
** Linux: n/a
** Notes: This is a separate test group, and can only be used on machines with a touch screen. Please ask Marcia or juanb for details.
*14) Uninstall:
**Windows:retornam '''pass'''
**Mac OS: mak - '''Pass''' - 10.6
**Linux : juanb - Ubuntu 9.10 - '''result'''

== Mozmill Tests ==
All the tests run with Mozmill have been synced with Litmus.

* Windows Vista [[http://pastebin.mozilla.org/696326 results]]
* OS X 10.6 [[http://pastebin.mozilla.org/696333 results]]
* OS X 10.4 [[http://pastebin.mozilla.org/696452 results]]

== Litmus Test Case Failures on Windows 7 ==
*Layout
**https://litmus.mozilla.org/single_result.cgi?id=228900 - Fails on Windows Vista and Mac. mw22 indicates Bug 463465 was not checked into 1.9.2. So this bug should probably be nominated for 1.9.2.1

*Cookies
**https://litmus.mozilla.org/single_result.cgi?id=229631

*Security
**https://litmus.mozilla.org/single_result.cgi?id=230801
**https://litmus.mozilla.org/single_result.cgi?id=230798
**https://litmus.mozilla.org/single_result.cgi?id=230798
**https://litmus.mozilla.org/single_result.cgi?id=230796
**https://litmus.mozilla.org/single_result.cgi?id=230794
**https://litmus.mozilla.org/single_result.cgi?id=230785

== Crashes during FFT testing ==
*Windows 7
**http://crash-stats.mozilla.com/report/index/194ac4a1-15ab-49f4-9367-711742100108 - May be [https://bugzilla.mozilla.org/show_bug.cgi?id=536272 Bug 536272]

**http://crash-stats.mozilla.com/report/index/bp-291dd72c-fa33-4b8d-bd1a-839d92100111
***[https://bugzilla.mozilla.org/show_bug.cgi?id=535873 Bug 535873]
***Now we have a set of STR to reproduce this crasher.

== Extension Related Issues? ==
*Installed Skype 4.0 which includes Skype for Firefox Browser Highlighter. Extension version is 3.3.0.3971. Experienced some freezes after this installation.

== Let's Not Forget ==
Please make sure to check the features you signed up to test, because some of these features' tests may not be in the FFT, such as ''multitouch''. For reference, check the areas that went in 3.6 and make sure you run the tests you created for your features:

# [https://wiki.mozilla.org/QA/Firefox3.6/TestPlan#Firefox_Features: 3.6 Fx Features]
# [https://wiki.mozilla.org/QA/Firefox3.6/TestPlan:Feature_Improvements Feature Improvements]

Tree Closures

2009-12-02T00:06:46Z

Zpao: /* Recent Closures */

=== Overview ===

Whenever the main tinderbox tree has to be closed, please record the date, the close start time, a rough time when the problem first started (if different from the close start time), and eventually, a tree open time. We need this information in order to track infrastructure problems, and try to resolve them in the future.

Please keep all times in Mozilla Standard Time (US Pacific, same time as on tinderbox). Put more recent closures on top of old ones. Please include links to any relevant bugs.

=== Recent Closures ===
* Tue Dec 1 4:00pm PST - ??? - buildbot master is overloaded & misreporting failures ({{bug|532228}}
* Tue Nov 24 6:05pm PST - 8:15pm PST - buildbot master restart needed for Firefox 3.6b4 builds
* Fri Nov 20 6:05pm PST - 1.9.2+mobile for Mountain View power outage {{bug|524047}}
* Thu Nov 19 4:10pm PST - 5:45 PST - ftp.m.o & stage.m.o broken {{bug|529961}}
* Mon Nov 2 1:59pm PST - 2:32pm PST - Closed to let HG recover from a DoS
* Thu Oct 22 5:48am PDT - 12:30pm PDT - Closed for scheduled testing of split mochitest setup
* Sun Oct 11 9:38pm PDT - Mon Oct 12 2:40am PDT - Only one Windows build slave still working ({{bug|521722}}), trying to cover all the builds for trunk and 1.9.2 and falling further and further behind
* Fri Sep 25 3:41am PDT - 9:47am PDT - Lots of orange. Caused by fallout from {{bug|473506}} (backed out), with some contribution from {{bug|518274}} (test disabled).
* Thu Sep 24 5:14am PDT - Scheduled RelEng maintenance
* Sun Aug 09 4:15pm - midnight PDT - Air conditioning failure at colo, {{bug|509351}} for unfixed fallout
* Wed July 22 6am - 11am PDT - Adding electrolysis branch {{bug|500755}}, Maemo TraceMonkey builds {{bug|505219}}, enabling TraceMonkey leaktest builds {{bug|504435}}
* Wed July 21 10:15pm - 11:30pm - {{bug|505669}}, buildbot master died
* Sat Apr 18 11am - ? Talos downtime, roll out of: {{bug|480413}} - Bug 480413 (design test to monitor browser shut down time)
* Wed Mar 25: 3:30pm - Thu 4:45am, too much randomness while storage array recovering {{bug|485123}}
* Tue Mar 17: 11:50 am - 2pm build timeouts due to swapping? {{bug|472463}} is related
* Tue Mar 3: 11:30am - ??

=== Older Closures ===
** Closed by platform meeting to let Beta 3 blockers land cleanly
* Wed Jan 9: 10.30am (approx) - ?
** Closed because of orange in the tree.
* Wed Jan 6: 14.30pm (approx) - 15:07pm
** Closed because of orange and red trees.
* Wed Dec 31: 9.30am (approx) - 17:25pm PST
** Closed because of DHCP problem in build network. See details in {{bug|471679}}.
* Tuesday Dec 23, 19:30-20:20PST
** Closed For Joe Drew to work on {{bug|455508}} - 20% Tp regression on linux, September 5
* Tuesday Dec 23, 14:00-17:30 PST
** Talos maintenance {{bug|463020}}
*** https://bugzilla.mozilla.org/show_bug.cgi?id=470113 (move talos jss machines from firefox3.0 to moz-central)
*** https://bugzilla.mozilla.org/show_bug.cgi?id=379233 (pageload tests should flush out layout before timing load end)
**** backed out, caused browser freeze ups
*** https://bugzilla.mozilla.org/show_bug.cgi?id=444174 (more readable/compact talos output to waterfall)
* Friday Dec 12, 06:00-10:57
** planned release team maintenance downtime (06:00-08:00), see [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/a2add6959ff0bda8# the dev.planing post] for details
** unit test boxes did not cycle green until 10:57
* Tuesday Dec 9, 13:50-Wed 02:25
** Emergency ESX maintenance (note from Aravind in dev.planning) took out boxes like graph server, caused rampant network related bustage.
** Could have reopened much earlier than this, just no-one round to do it
* Monday, Dec 8, 10:25 - 13:11
** reftests had been broken for 10.5 hours due to error in manifest file that wasn't actually causing orange ({{bug|468476}})
** closed tree until fix cycled to prevent more from piling on
** hg.mozilla.org also misbehaving (pushlog db locked); hard to push fixes or load pushlog
* Friday, Dec 5, 18:20 - 19:05
** Waiting on Windows talos machines to start a run that includes the perf-sensitive [http://hg.mozilla.org/mozilla-central/rev/a0c0ed9f461f changeset a0c0ed9f461f]. (Talos had ignored the last 6 completed builds)
* Thursday, Dec 4, 15:00 - 20:10
** {{bug|468014}} Investigating mozilla-central Vista TS, TP3, and TSVG increases. This is likely due to rebooting the Vista talos servers {{bug|463020}} especially since it brought these numbers up to around the same range as 1.9.1 as well as XP on both 1.9.1 and 1.9.2
** Rebooted 1.9.2 Vista talos boxes and waiting on the results.
** After further investigation it appears that rebooting the talos systems caused this. See {{bug|468014}} for more details.
* Thursday, Dec 4, 12:10 - 13:10
** Talos server reboots performed by Chris AtLee - catlee {{bug|463020}}, {{bug|467797}}, and {{bug|467796}}
* Tuesday, Nov 12, 15:35
** null pointer dereference causing crashes on linux and OSX leak test build boxes; {{bug|464571}}
* Tuesday, Nov 12, 08:00
** Tinderbox and various other infrastructure down
* Friday, Nov 7, 0200 - 05:00
** Backing out changesets to find the cause of the 10% Ts on OSX
* Friday, Oct 24, 09:00 - 12:30
** Talos Maintenance - {{bug|443979}}, {{bug|459598}}, and {{bug|457885}}
* Sunday, Sep 28, 17:54 -
** performance regression tracked in {{bug|457607}}
* Friday, Sep 26, 13:54 - 15:32
** reftests orange due to botched reftest.list change by sgautherie
** windows still leaking from sdwilsh's landing and backout
*** required multiple corrections to patch to {{bug|455940}}
* Friday, Sep 26, 10:45 - 13:52
** sdwilsh is trying to land the places fsync work again and wants the tree closed for stable perf numbers
** sdwilsh backed out
** tree remained closed for tracking down performance regression from day before, {{bug|457288}}
** sdwilsh backed out more
* Wednesday, Sep 24, 12:00 - 7:00
** New Windows boxes moz2-win32-slave07 / 08 are orange due to leaks
** Old qm-win2k3-moz2-01 box had been leaking too
** Tracked down to bug 454781 from 9/20, which had unfortunately landed in the middle of a period with other bustage and leaks. Fun!
* Tuesday, Sep 23, 9:00
** Closed because of MPT power outage.
* Monday, Sep 22, 3:30
** Closed for bug {{bug|456463}}
* Thursday, Sep 18, 6:30 - Friday 8:00
** Places fsync work will be landing once the tree gets greener - possible perf regressions
** Window unit test boxes appeared to be hanging, so places fsync was backed out
** Places fsync work backout caused leaks; clobber requested {{bug|455934}}
** Closed for {{bug|455791}}, resolved by backing out {{bug|454735}}.
** Talos bustage may or may not be fixed, see discussion in {{bug|455791}}... but it's all green currently, so reopening the tree
* Tuesday, Sep 16, 12:50 - Wednesday, Sep 17, 3:20
** sdwilsh's third landing of the new SQLite {{bug|449443}} is still causing a huge Ts spike on Linux, despite no hit on tryserver.
** Rather than immediately backing it out, we are trying to gather a little bit of data to help him understand what's going on, since he can't reproduce this offline.
** First step is clobbering the linux machines that feed talos, since tryserver is always a clobber build, but the tinderbox machines aren't, and that's the only real difference (identical images, same hardware).
* Friday, Sep 12, 10:00 - 11:45
** Fix up windows talos boxes {{bug|430832}}, {{bug|419936}}
* Thusrday, Sep 11, 13:00 - 17:30
** memory usage regression (working set/rss) {{bug|454865}} - Started on 09-09-2008 ~ 18:40.
* Tuesday, Sep 9, 15:30 -
** Talos maintenance {{bug|419935}}
* Thursday, Sep 4, 16:00 - 19:45
** Scheduled downtime to make talos mac machines boot cleanly {{bug|419935}} {{bug|419933}}
* Tuesday, Sep 2, 16:15 -
** Closing tree to get it green in order to land tracemonkey updates, and update tinderbox.
* Tuesday, Aug 26, 05:40 - 10:00
** Tree closed to track the perf impact of landing {{bug|432131}}
* Wednesday, Aug 13, ~8am - 10:20pm
** Tree closed due to perf regression (bug 450401). Unable to find cause, reopened tree.
* Tuesday, Aug 12, 8:00 -
** Scheduled unit-test master migration/downtime
* Saturday, July 26, 09:22 - 11:53, 12:30 - Sun 04:30
** Mac OS X builder out of disk space, {{bug|448115}}
** problem seems to have gone away on its own, although disk space probably still low
* Friday, July 25, 09:45 - Saturday, July 26, 09:10
** talos machines all broke due to stage.mozilla.org
*** no ETA given
** turned green around 19:00-20:00
** turned red again around 21:30
*** dbaron filed {{bug|448079}}
** {{bug|448019}} had already been filed earlier in the day, but not linked from here or tinderbox
** hardware on stage was replaced; talos went green again
* Friday, July 18, 20:30-23:00
** brendan checked in a patch ({{bug|445893}}) that made xpcshell hang or crash on Windows
** {{bug|446143}} filed to get tinderboxes fixed
*** since this requires manual maintenance, see {{bug|445578}}
*Wednesday, July 16, 10am-5pm
** tree effectively closed most of the day due to multiple sources of orange
*** no active fixing until around noon, when dbaron backed out {{bug|431842}}
** Windows tinderboxes needed manual maintenance ({{bug|445571}}) after xpcshell test hang
*** filed {{bug|445578}} on making this case not require manual maintenance
** filed {{bug|445610}} on making it more likely that multiple simultaneous failures will all be caught
*Friday, July 11, 4:10pm-6:10pm
** multiple failures on linux and windows unit tests prompted closure. Backed out a test change that broke other tests that relied on the changed one.
*Friday, July 11, 7:30am - 11:30am PDT
** both linux and both windows test boxes were orange, so the tree was closed.
** WINNT 5.2 mozilla-central qm-win2k3-moz2-01 dep unit test went green all by itself
** Linux mozilla-central qm-centos5-moz2-01 dep unit test went green all by itself
** The browser window was not focused for WINNT 5.2 mozilla-central qm-win2k3-03 dep unit test (45 reftests were failing). Box was stopped, focus restored, and a new test run was kicked off by bhearsum (no bug filed).
** Linux mozilla-central qm-centos5-03 dep unit test went green all by itself.
** Linux mozilla-central qm-centos5-moz2-01 dep unit test went orange
*** leaked 124036 bytes during test execution
** WINNT 5.2 mozilla-central qm-win2k3-03 dep unit test went orange
*** 28 reftest failures
** Linux mozilla-central qm-centos5-03 dep unit test went orange again failing [http://mxr.mozilla.org/mozilla-central/source/toolkit/components/downloads/test/unit/test_bug_406857.js test_bug_406857.js]
** Linux mozilla-central qm-centos5-moz2-01 dep unit test still orange
*** leaked 124036 bytes during test execution
*** failed an xpcshell test case ([http://mxr.mozilla.org/mozilla-central/source/toolkit/components/downloads/test/unit/test_sleep_wake.js test_sleep_wake.js]) with lots of Gdk-CRITICAL assertions
*** failed one chrome test ({{bug|443763}})
** WINNT 5.2 mozilla-central qm-win2k3-03 dep unit test still orange.
*** No more test failures.
*** leaked 292389 bytes during test execution
** Linux mozilla-central qm-centos5-moz2-01 dep unit test still orange.
*** failed one chrome test ({{bug|443763}})
*** leaked 124036 bytes during test execution
** Linux mozilla-central qm-centos5-03 dep unit test went green.
** Linux mozilla-central qm-centos5-moz2-01 dep unit test.
*** Tree re-opening since we have coverage on at least one windows machine for metered checkins (11:30am)
** WINNT 5.2 mozilla-central qm-win2k3-03 dep unit test went green (11:36am)

* Thursday, July 10, 12:49pm - 10:44pm PDT
** qm-moz2mini01 went orange, reporting 300k of leaks, and enough other tinderboxes were orange or red (although the issues were understood and being addressed) to warrant the precaution of closing the tree while investigating qm-moz2mini01.
** qm-moz2mini01 subsequently went green in the following cycle without explanation.
** After that, the sheriff (Myk) held the tree closed until at least one of the two windows unit test boxes (which had both been clobbered to resolve a residual problem from an earlier checkin that had been backed out) finished building successfully.
** But those machines both went orange with 45 MochiTest failures, so the sheriff had the four patches since the previous build backed out.
** After those patches were backed out, the next cycle, which included all the backouts, showed the same problem.
** The 45 failures all looked popup-related, so maybe the wrong thing was focused on the test machines.
** The sheriff requested another clobber from IT.
** IT performed another clobber, which didn't work. IT also confirmed that the machines were in the appropriate state (the cmd window open and minimized, no other windows open) after both clobbers (although later there was discussion that perhaps the window was still focused after minimization, and perhaps it was necessary to click on the desktop to unfocus the window).
** The sheriff escalated to build, cc:ing robcee and bhearsum on the latest bug about the clobber ( {{bug|444674}}), per [[Unittest:Win2k3:Moz2:ITSupport]].
** lsblakk did a source clobber, and qm-win2k3-moz2-01 cycled green after that (with qm-win2k3-03 expected to do so as well once out-of-space issues were resolved by coop), but qm-pxp-fast03 and mozilla-central turned red in the meantime, so the sheriff left the tree closed and went to look at those.
** The problem looked related to various IT maintenance that evening (kernel upgrades on hg, ftp, and other servers as well as some DNS changes), so the sheriff waited.
** qm-pxp-fast03 and mozilla-central turned green on their next cycle, so the sheriff reopened the tree.
* Tuesday, July 8, 9:30am PDT-1:15pm
** unit-test failures caused by a typo in code, plus a tinderbox that hung due to a code error and didn't come back up correctly (no display)
* Friday, July 4, 5am PDT - 10am PDT
** Closed for The Great Tinderbox Move {{bug|441945}}
* Tuesday, July 1, 02:04 - 10:57
** {{bug|442875}} - graph server cause most things to go orange
** {{bug|442887}} - 1.9-only: qm-xserve01 needs repair
** {{bug|442843}} - trunk-only: qm-moz2-unittest01 is out of space
* Wednesday June 25, 08:20 - 12:20
** Planned downtime for VM host maintenance
* Sunday, June 8, 11:55 - Tuesday, June 10, 15:57
** Linux build tinderbox and unit test machine went read-only around 5am
** all talos machines stopped reporting around 3:30am
** filed {{bug|437877}}
** filed {{bug|437893}}
** netapp migration started a day early (Sunday) due to failures
** Tuesday morning status:
*** unit test machines intermittently failing leak check on mochitests on their return
*** talos machines occasionally appearing but still not functional
* Saturday, June 7, 9:00 - 14:27
** windows builders (main and debug) both went red due to open files
** filed {{bug|437785}}
* Friday, June 6, 15:00 - 23:15
** brendan broke the tree in two different ways
*** windows crashing
*** failing JSON test
** DNS outage slowed down the fixing
* Friday, June 6, 5:15 - 9:00
** Scheduled closure to clobber and land NSPR/NSS
*** bsmedberg goofed and the client.py step had to be removed from the master.cfg of builders and unit-testers, which took longer than expected
* Tuesday, June 3, 10:00 - 15:20
** Windows build red for some reason
*** clobbered by bhearsum, didn't help for some reason
* Sun, May 25 15:51 - Monday, May 26 01:25
** We are currently experiencing intermittent VMware/netapp problems, which causes entire sets of machines to start failing with cvs conflicts, corrupted .o files, etc, even when no checkins have occurred. Tree reopened to load-test fix. See bug 435134 for details.
* Fri, May 23
** 12:45 - 18:25
*** Buildbot master for Talos and Unittest went down (all talos boxes went red)
*** fx-linux-tbox also had cvs conflicts in browser/ and accessible/, tree clobbered

* Wed, May 7
** 8:00 AM - 12:50 PM
*** Waiting on backout of ({{bug|432492}}) to cycle through.

* Tuesday, May 6
** 8:20 - 9:00 PM
*** Talos machines were failing due to cvs-mirror issues ({{bug|432570}}).

* Thursday, May 1
** Start 12:00 PM
*** TUnit does not complete, qm-centos5-02 orange since yesterday. jst and mkaply in range, jst and sicking investigating.

* Friday, April 25
** 11:40 AM - 2:00 PM
** {{bug|430820}}

* Thursday, April 24
** 8pm - 11pm
*** expected outage for graph server and buildbot maintenance

* Wednesday April 16
** 3PM - 1AM
*** Unexpected outage started ~3pm, {{bug|429406}}
*** Tree closed at 8:10 due to qm-xserve-01 still not working

* Tuesday April 8
** 2:24AM PDT - 4:31AM
*** Tree closed due to {{bug|427723}} and {{bug|427728}}.
*** Windows nightly box restarted and completed, talos boxes started testing

* Monday April 7
** 7 PM PDT
*** Tree has been orange for too long (unit test failures) and then someone checked in theme changes (bug 427555) that caused red.
*** The orange was fixed after {{bug|426501}} was backed out.

* Saturday April 5
** 00:48 PDT - 20:45
*** unit test failures across 3 platforms
*** filed {{bug|427248}}, remaining issues spun off to:
**** {{bug|425987}} worked around reftest failures with a larger timeout
**** {{bug|426997}} for the new PGO test box - still burning, will ignore.

* Friday April 4
** 03:24 PDT - 09:05PDT
*** Announced closure to get clean perf numbers from {{bug|425941}}
*** See dev.planning/d.a.f thread: http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/d02e523b8483c914#

* Friday, Mar 28, 2008
** 16:23 PDT - 22:40 PDT
*** Bonsai DB replication issues

* Tuesday, Mar 25, 2008
** 14:30 PDT - 15:05 PDT
*** Leak test machines orange
**** Kai's patch for bug 420187 caused a leak, he fixed it
** 14:30 PDT - 16:10 PDT
*** Windows unit test failures
**** the Windows unit test machine (qm-win2k3-01) had failed for a few cycles for various reasons, wanted to get a green cycle in before accepting more checkins.
**** {{bug|425081}} filed about machine trouble

* Saturday, Mar 22, 2008
** 13:48 PDT - 18:10 PDT
*** Windows talos machines are all red
**** fallout was from enabling strict file: URI security policy
**** alice checked in a config change to talos to disable strict URI policy on talos, filed {{bug|424594}} to get talos in line with this strict policy
**** still closed waiting on unit test orange to resolve.

* Tuesday, March 18, 2008
** 12:03 Wednesday, Mar 19, 2008
*** johnath re-opened tree after test failures cleared and rapid cycle test boxes were reporting numbers in the pre-closure range
** 20:22
*** Major network issues at the MPT colo which hosts... everything. Closed until services are back online (including IRC).
*** {{bug|423882}} for details on the missing talos boxes.
** 17:31 - 17:39
*** Network issues at moco, closing to avoid a mess if tinderboxes and/or bonsai is taken down by it.

* Friday March 14, 2008
** 14:25 - 16:03
*** mac and windows unit test boxes stopped cycling sometime between 2am and 7:45am
*** dbaron noticed when firebot announced tinderbox falling off 12hr waterfall page at 14:23, Waldo had noticed and commented in #developers at 12:16 (and again at 12:42) but was preoccupied and only had time to really follow up at 14:23 to ask for tree closure
*** tree closed, {{bug|423015}} filed
** 6:00am - 07:40am
*** stage migration, closed to make sure Talos reconfig works OK and builds keep flowing
* Thursday March 6, 2008
** 7:00pm - 7:40pm
*** closed due to fx-win32-tbox bustage. Cleared stuck process, reopening assuming that was the issue rather than wait another hour for the PGO-lengthened build to finish
* Wednesday March 5, 2008
** 2:40pm - 4:00pm
*** Closed for orange on win3k3-01 that looks like memory corruption
*** Caused by {{bug|418703}}, backed out
** 8am - 11:30am
*** bugzilla/CVS down, closed tree for talos bustage because of no-CVS
* Wednesday, February 27, 2008
** 9:30pm - 12:10am
*** Overlooked 2 tests that had also broken during the day ({{bug|420028}} due to removal of DOMi, {{bug|384370}} due to incomplete backout) and were not focus issues
*** Box has some other test/build failures that went away by themselves after being kicked
** 7:40pm - 9:30pm
*** Windows box was orange with focus problems ([https://bugzilla.mozilla.org/show_bug.cgi?id=420010 bug 420010])
*** Missed from earlier in day due to expected issues while PGO was landing
** 5:30pm - 7:40pm
*** Closed to do Linux kernel upgrades ([https://bugzilla.mozilla.org/show_bug.cgi?id=407796 bug 407796])
*** Quiet tree due to B4 freeze, and holding approval1.9b4 flags for enabling PGO on Windows, so closure has minimal impact
*** Took a bit longer than expected due to a reboot problem ([https://bugzilla.mozilla.org/show_bug.cgi?id=420007 420007])

* Tuesday, February 26, 2008
** 22:38 - 00:49
*** problem started at 22:33 when qm-win2k3-01 turned red again
*** same problem as earlier in the day: "Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill process" during tests
*** myk closed the tree around 22:38 to wait out the bustage, since the machine is our only windows unit testerbox
*** got stuck with an open file such that each build failed really quickly
*** {{bug|419799}} filed to get sysadmin help to fix unit test box
*** mrz, who was on-call that evening, jumped into IRC and then went and kicked buildbot; first he closed some dialog about some process having crashed; then he restarted buildbot, but it didn't start building; then he killed both buildbit and its cmd process and then restarted it, after which it started building and completed successfully
*** dbaron reopened the tree to metered checkins of b4 blockers

* Tuesday, February 26, 2008
** 18:44 - 19:40
*** problems started with linux txul perf regression
*** continued with fxdbug-win32-tb reporting: ###!!! ASSERTION: invalid active window: 'Error', file e:/builds/tinderbox/Fx-Trunk-Memtest/WINNT_5.2_Depend/mozilla/embedding/components/windowwatcher/src/nsWindowWatcher.cpp, line 1086
*** continued with five cross-platform unit test failures, three reftests and two mochitests
*** reed backed out {{bug|419452}}, one of two candidates for the perf regression
*** dbaron fixed the three reftests and one mochitest, which were from his checkin for {{bug|363248}}
*** myk backed out sicking's fix for {{bug|416534}}, which had caused the last mochitest failure
*** various folks speculated that the fxdbug-win32-tb assertion was random (it didn't show up on Mac or Linux)
*** myk reopened the tree, feeling that things were under control
*** reed backed out second perf regression candidate ({{bug|395609}}) when initial backout didn't resolve it
*** sicking fixed test failure in {{bug|416534}} and relanded
*** others started landing again
*** unit test tinderboxes cycled green
*** reed's second backout fixed perf regression
*** reed's first or second backout also fixed the fxdbug-win32-tb assertion

* Tuesday, February 26, 2008
** 5:10pm - 5:46pm
*** problem started at 5:06pm when qm-win2k3-01 turned red
*** reed said that machine frequently hits this random bustage and then recovers
*** reed previously noted at the top of the page that "qm-win2k3-01 is the only Windows unit test machine, so if it is orange or red, you should NOT check in."
*** myk, the sheriff for the day, closed the tree to wait out the apparently random failure and then reopened it when the next build came up green
*** reed thought there might be an old bug on the problem but wasn't sure, so dbaron filed bug {{bug|419761}} on the problem to make sure it's tracked and not forgotten
*** wolf also filed {{bug|419759}} on fixing or replacing winxp01 so we aren't entirely reliant on win2k3-01 for windows unittests

* Sunday, February 24, 2008
** 11:30am - 4:45pm (with orange lasting longer, with tree open)
*** problem started 9:23am, amid some other bustage
*** closed by dbaron a little after 11:30am
*** filed {{bug|419328}}: Windows unit test box stopped cycling
*** aravind hard-rebooted the box, came back with a bunch of popup tests orange.
*** test still orange after another cycle (forced by dbaron)
*** dbaron reopened tree 4:45pm despite the unfixed machine-related orange
*** joduinn rebooted the box again around 4:30pm
*** this time it came back with the color depth wrong, so the PNG reftests failed (but the mochitests worked)
*** color depth issue fixed 6:45am '''Monday'''

* Thursday, February 21, 2008
** 10pm - 12am
*** Dietrich
*** Closed to facilitate l10n string freeze

* Tuesday, February 19, 2008
** 9:10 PM - 10:45 PM
*** No sheriff (night)
*** Closed due to at least three people landing on orange ([http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1203480120.1203482373.3631.gz seemingly random TUnit failure on Windows]). The tree was too wide for anyone to notice the orange. [http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1203480120.1203484232.8866.gz A mochitest timeout on Linux], also seemingly random, occurred almost immediately after.
** 1:00 AM - 3:00 AM (guess)
*** No sheriff (night) (guess)
*** Closed for experimental landing of {{bug|399852}}. The checkin stuck.

* Wednesday, February 13, 2008
** 1:00 PM - 1:40 PM (problem first noticed around 9:40 AM)
*** No sheriff
*** {{bug|417313}} -- graphs.mozilla.org can't keep up with data being submitted
*** reopened after machines started going green; db load lessened, but underlying issue has not been fixed.

Releases/Firefox 3.6Br4/Test Plan:l10n

2009-11-25T20:04:05Z

Zpao: /* Windows (tchung, tester2...) */

[https://wiki.mozilla.org/Releases/Firefox_3.6Br4/Test_Plan 3.6Br4 Test Plan]

= L10n Spot Checks =
We will test a couple of tier 1 locales per platform, using the l10n test suite in Litmus. Please check with QA lead or l10n driver should there be new locales in this release.

'''If you file a bug''', please add "[3.6Br4]" without the quotes on the ''Whiteboard'' field so we can query the bugs filed during this testing cycle.

== Windows (tchung, zpao) ==
* fr - '''in progress - zpao'''
** Notes: ''any problems found?'''
* pl - '''Pass/Fail/in progress'''
** Notes: ''any problems found?'''

== Mac (tchung, tester2...) ==
* de - '''in progress'''
** BuildID: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; de; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4
** Notes: ''any problems found?'''

== Linux (tchung, tester2...) ==
* ja - '''Pass/Fail/in progress'''
** Notes: ''any problems found?'''

User:Zpao

2009-11-22T02:19:43Z

Zpao:

= Who is zpao =

I am Paul O’Shannessy. I started at Mozilla when I interned in the summer of 2008. I came on full-time in February of 2009.

= What do I work on? =

I've worked on a number of different things. You can see the code I've written by [http://hg.mozilla.org/mozilla-central/log?rev=paul%40oshannessy.com searching pushlog]. In general, I've primarily done stuff in Password Manager & Session Restore and have dabbled in a bunch of other places.

= Writing/Planning =

I also have started doing some writing to plan out some major features or changes.

* [[User:Zpao/mozStorageAndSessionStore|mozStorage and SessionStore]]

= Current Projects =

* [[User:Zpao/SessionstoreClearnup|Sessionstore Cleanup]]

Firefox/Projects

2009-11-16T19:24:43Z

Zpao: move PTNP from active to completed

= Active Projects =

{| class="fullwidth-table sortable"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Participants'''
| '''Goal'''
| '''ETA'''
| '''Target'''
| '''Status'''
|-
| [[Firefox/Projects/Startup Time Improvements|Ts Improvements]]
| dietrich
| ddahl, rflint, adw
| reduce warm and cold startup of Firefox, Fennec
| 11/06/09
| 1.9.2/1.9.3/infra
| cold ts on windows, "all dirty" profile, micro-testing perf, dictionary delay, mmap io measurement
|-
| [[Firefox/Projects/3.7 and 4.0 Theme and UI Revamp|Theme and UI Revamp]]
| shorlander
| faaborg, limi
| update Wiki, line-up of capabilities priorities, steps towards approval.
| 10/19/09
| 1.9.3
| solid direction for 3.7 and 4.0. in the refinement stage on Mac and Windows. Linux in initial stage.
|-
| [[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/Download manager improvements|Improve Download Manager + MIME type defaults]]
| limi
| 
| Streamline download behaviors
| Did a "research presentation" to get additional feedback
| Starting with 3.7
| Currently prioritizing what should go into 3.7, and what should wait for 4.0
|-
| [[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
| Rev 2 of the proposal is up
| Starting with 3.7
| Next step is a version using offline manifest file spec
|-
| [[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/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) 
| limi 
| Unfocused
| Make it possible to switch tabs using the AwesomeBar 
| TBD
| 1.9.3 
| UI mostly done, autocomplete code needs more testing
|-
| [[Firefox/Projects/Improve Mac installer|Improve Mac installer]]
| limi
| community volunteers, for now
| Detect when we launch from disk image/downloads folder, offer to move to Apps
| 
| 1.9.3?
|-
| [[Firefox/Projects/Places async expiration|Places Async Expiration]] 
| mak 
| mano 
| Make Places expiration async 
| 
| 1.9.3 
| Posting patches, 1 leak to investigate, needs new unit tests. 
|-
| [[Firefox/Projects/Unbreak RSS|Unbreak RSS]] 
| cbartley 
| TBD 
| RSS preview is difficult to maintain (C++), privileged (and hence a risk), etc. Make it better. 
| TBD 
| 1.9.3 
| Initial investigation 
|-
| [[Firefox/Projects/Extension Manager API|Extension Manager API Updates]]
| Mossop
| TBD
| 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.
| TBD
| 1.9.3
| Initial prototyping and API designs
|-
| [[Extension Manager:UI Update|Addons Manager Redesign]]
| Boriss
| Mossop, Nick, Fligtar
| Update the add-ons manager UI
| TBD
| 1.9.3
|
|-
| [[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
| Initial api designs
|-
| [[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/Async Places containers|Async Places containers]]
| adw
|
| Perf: non-blocking Places operations
| TBD
| 1.9.3
| Filing, fixing blocking bugs
|}

= Inactive Projects (need to finish) =

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

== Prioritized ==

*[[Firefox/Projects/Inline PDF display|Inline PDF display]]
*[[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/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

2009-11-02T20:32:25Z

Zpao: /* Active Projects */

Firefox/Projects/Per Tab Network Prioritization

2009-10-26T19:50:03Z

Zpao: /* Overview */

= Overview =

'''Sprint lead:''' zpao

'''Sprinters:''' zpao, limi

'''QA Contact:''' whimboo

'''Description'''

:We want to do some network prioritization such that the tab / window that you are currently using have higher network priority than the ones you aren't using.

''The goal is to optimize tab loading and performance on startup.''

We propose to do this in two stages: 

*'''Firefox 3.6''': A simple enhancement where we assign priorities to the network loading of the different tabs. This should give us a quick win and make the initial page load of the focused tab complete earlier.
*'''Firefox 3.7''': A more comprehensive enhancement to make it possible to load tabs in most-recently-used order, as well as possibly set a threshold for how many tabs get loaded at once. This should take care of the more extreme cases where people are opening 30+ tabs on restore. 

= Goals / Use Cases =
* Make Firefox feel like it's starting up faster.
** While Firefox (or at least the tab / window being used) should become more immediately usable, I don't think total load time will be faster.
* Make current tab more responsive than background tabs.

= Non-Goals in this iteration =

The first iteration will be a simpler version, for the next iteration (3.7?) we should consider:

*MRU network prioritization.
*A threshold on how many tabs are loaded in parallel to control cpu/network load.
*Batch up these groups based on MRU order. 

= Design =

There are a couple ways we could do this:

*Put it all in tabbrowser.xml & browser.js & just jigger priorities directly.
*Put it in a new component (or whatever) that listens for TabSelect (and window select) 

If possible, we also want to be able to have an interrupt give higher priority to a tab if you switch to it during the initial page load. E.g. if you switch to the unfocused window, the priorities mirror what was in the initial focused window had, and the now-unfocused window has its priorities downgraded. 

= Prioritization =
== Priorities ==
[https://developer.mozilla.org/en/nsISupportsPriority Priorities] range from 20 to -20 with -20 being the highest. There are 5 presets (highest, high, normal, low, lowest).

== What To Do With Priorities ==

The general proposition here is as follows:

{|
|-
! 
! Focused Tab
! Unfocused Tab
|-
! Front-most Window
| high
| normal
|-
! Background Window
| normal
| low
|-
! Minimized Window
| low
|
lowest

|}

A visual way of looking at it — [] indicates frontmost tab:

'''Focused window:'''
<pre> ________ ________ ________
| Medium || [High] || Medium |
</pre>
'''Unfocused (but visible) window:'''
<pre> _____ __________ _____
| Low || [Medium] || Low |
</pre>
'''Minimized window:'''
<pre> ________ _______ ________
| Lowest || [Low] || Lowest |
</pre>

= Bugs =
* {{bug|514490}} Actual implementation bug
* {{bug|511503}} Window activate/deactivate DOM events

= Resources =
* [http://groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/94bf663f787b711e Limi's dev.apps.firefox thread] (has some useful implementation insight from bz)

Firefox/Projects

2009-10-26T19:14:27Z

Zpao: /* Active Projects */

Firefox/Projects

2009-10-19T20:05:08Z

Zpao: /* Active Projects */

Firefox/Projects

2009-10-19T20:04:23Z

Zpao: /* Active Projects */

Firefox/Projects

2009-09-28T20:03:17Z

Zpao: /* Active Projects */

= Active Projects =

{| class="fullwidth-table sortable"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Participants'''
| '''Goal'''
| '''ETA'''
| '''Target'''
| '''Status'''
|-
| [[Firefox/Projects/WindowsCE|Firefox WinCE]]
| vlad
| dolske, rstrong
| finalize
| 21 Sep 2009
| 1.9.2
| doneish -- final package delivered to nvidia, waiting on QA results)
|-
| [[Firefox/Projects/Startup Time Improvements|Ts Improvements]]
| dietrich
| ddahl, rflint, adw
| reduce warm and cold startup of Firefox, Fennec
| 09/25/09
| 1.9.2
| windows timing and analysis, getService consolidation, stat and syscall removal, more dirty profiling
|-
| [[Firefox/Projects/Network Error Pages|404 Error Pages]]
| cbartley
| Boriss, johnath
| Override server-supplied 404 error pages in certain cases to provide tools we think will be more useful to the user.
| 2 Oct 2009
| 1.9.3
| Places C++ code has been rewritten in JavaScript. Still some L10N issues and general touch up to do.
|-
| [[Firefox/Projects/Video Controls|Video Controls]]
| Boriss
| limi, mano
| Fullscreen patch has landed thanks to dao (yay!), getting UI & code reviews. Other bugs finished are (), in progress are ()
| 02/10/09
| 1.9.3
| Solid direction for 3.6 (finishing remaining bugs) and 3.7 (starting work)
|-
| [[Firefox/Projects/Windows Theme Revamp|Update Default Theme]]
| shorlander
| faaborg, limi
| finalized mac concepts, initial linux concepts of proposed ideas, line-up of capabilities priorities, steps towards approval.
| 09/25/09
| 1.9.3
| solid direction for 3.7 and 4.0
|-
| [[Firefox/Projects/Personas Uplift Exploration|Personas Uplift Exploration]]
| Dao
| Mossop
| include support for lightweight themes in Firefox 3.6
| 09/21/09
| 1.9.2
| Large chunks have landed, {{bug|511771}} is awaiting vlad's SR
|-
| [[Firefox/Projects/Animation priorities|Animation priorities]] (tear-off, find, movement of menu items)
| Boriss
| shorlander
| "Next steps" document outlining what will be needed to move forward on implementation
| 09/28/09
| future (possibly about to be deleted in favor of two child-sprints: [[Firefox/Projects/Tab_animation|Tab & Menu item animation]] and [[Firefox/Projects/Find_on_Page|Find on Page improvements]])
| Have mockups & interaction flows, but nothing yet implemented
|-
| [[Firefox/Projects/Plugin Update Referrals|Plugin Update Referrals]]
| Mossop
| beltzner, johnath, morgamic, lmesa, alix, blizzard, Unfocused
| Firefox checks for outdated plugins and takes you to a page on mozilla.com to get updated plugins.
| 09/28/2009
| 1.9.2
| Patch is waiting for review, strings have landed
|-
| [[Firefox/Projects/Per Tab Network Prioritization|Per Tab Network Prioritization]]
| zpao
| limi
| Get reviews, write tests (not in that order)
| 2009/09/30 (for next step)
| 1.9.2
| getting people to review it, writing tests...
|-
| [[Firefox/Projects/Places Vacuum|Places Vacuum]]
| mak
| sdwilsh
| Fragmented databases are known to cause performance problems. Try a Places implementation before investigating an app-wide vacuum.
| 03/09/2009
| 1.9.2
| Landed on trunk and 1.9.2, new tests landing.
|-
| [[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.
| 3.7 mockups done by 9/25, all mockups done by 10/2
| the future
| Creating mockups based on work week meetings.
|-
| [[Firefox/Projects/Reduce Places Views Overhead|Reduce Places Views Overhead]]
| Mano
| mak
| 
| 20/09/2009
| 1.9.2
| Landed on trunk.
|-
| [[Firefox/Projects/about:support|about:support]]
| cbartley
| TBD
| Create an in-content about:support page that support can use to help users with problems.
| 25 Sept 2009
| 1.9.2
| Landed on mozilla-central and 1.9.2.
|-
| [[Firefox/Projects/Tab_Matches_in_Awesomebar|Tab Matches In Awesomebar]] 
| limi 
| dietrich/marco? 
| Make it possible to switch tabs using the AwesomeBar 
| 
| 1.9.3 
| Next up: blog post 
|-
| [[Firefox/Projects/Improve Mac installer|Improve Mac installer]]
| limi
| community volunteers, for now
| Detect when we launch from disk image/downloads folder, offer to move to Apps
| 
| 1.9.3?
|-
| [[Firefox/Projects/Tab_animation|Tab & Menu item animation]] 
| boriss 
| none yet (shorlander?) 
| Add intuitive, subtle motion to the menu bar including tab tearoff and rearrangement of menu items 
| 
| 1.9.3 
| 
|-
| [[Firefox/Projects/Find_on_Page|Find on Page improvements]] 
| boriss 
| none yet (zpao? shorlander?) 
| Make finding text on a page easier through more intuitive controls & subtle animation 
| 
| 1.9.3 
| Getting started 
|}

= Inactive Projects (need to finish) =

*[[Firefox/Projects/AcceleratedScrolling|Accelerated Scrolling]]
*[[Firefox/Projects/Multitouch Polish|Multitouch Polish]]
*[[Firefox/Projects/Doorhanger notifications|Doorhanger notifications]]
*[[Firefox/Projects/Eradicate Startup Dialogs|Eradicating Startup Dialogs]]

== Prioritized ==

*[[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/Unbreak RSS|Unbreak RSS]]
*[[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/Extension Manager API|Extension Manager API Updates]]
*[[Extension Manager:UI Update|Addons Manager Redesign]]
*[[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)]]

== Unprioritized ==

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

= Additional Projects Ideas (Need more definition) =

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

= Completed Projects / Archive =

*[[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)

= Template =

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

Firefox/Projects

2009-09-21T20:09:29Z

Zpao:

= Active Projects =

{| class="fullwidth-table sortable"
|-
| width="25%" | '''Description'''
| '''Leader'''
| '''Participants'''
| '''Goal'''
| '''ETA'''
| '''Target'''
| '''Status'''
|-
| [[Firefox/Projects/WindowsCE|Firefox WinCE]]
| vlad
| dolske, rstrong
| finalize
| 4 Sep 2009
| 1.9.2
| final todo list and roadmap for platform-complete release (both technical and delivery reqs checklist)
|-
| [[Firefox/Projects/Startup Time Improvements|Ts Improvements]]
| dietrich
| ddahl, rflint, adw
| reduce warm and cold startup of Firefox, Fennec
| 09/25/09
| 1.9.2
| windows timing and analysis, getService consolidation, stat and syscall removal, more dirty profiling
|-
| [[Firefox/Projects/Network Error Pages|404 Error Pages]]
| cbartley
| Boriss, johnath
| Override server-supplied 404 error pages in certain cases to provide tools we think will be more useful to the user.
| 12 Sept 2009
| 1.9.3
| Patch is awaiting review. Goal is to get it landed on trunk this week. Need to ping reviewers.
|-
| [[Firefox/Projects/Video Controls|Video Controls]]
| Boriss
| limi, mano
| Fullscreen patch has landed thanks to dao (yay!), getting UI & code reviews. Other bugs finished are (), in progress are ()
| 02/10/09
| 1.9.3
| Solid direction for 3.6 (finishing remaining bugs) and 3.7 (starting work)
|-
| [[Firefox/Projects/Windows Theme Revamp|Update Default Theme]]
| shorlander
| faaborg, limi
| finalized mac concepts, initial linux concepts of proposed ideas, line-up of capabilities priorities, steps towards approval.
| 09/25/09
| 1.9.3
| solid direction for 3.7 and 4.0
|-
| [[Firefox/Projects/Personas Uplift Exploration|Personas Uplift Exploration]]
| Dao
| Mossop
| include support for lightweight themes in Firefox 3.6
| 09/21/09
| 1.9.2
| Large chunks have landed, {{bug|511771}} is awaiting vlad's SR
|-
| [[Firefox/Projects/Animation priorities|Animation priorities]] (tear-off, find, movement of menu items)
| Boriss
| shorlander
| initial sketches and requirements documentation
| 14/08/09
| future
| Have brainstormed animation priorities and have three to propose, next steps will be feedback on those priorities and iteration on them.
|-
| [[Firefox/Projects/Plugin Update Referrals|Plugin Update Referrals]]
| Mossop
| beltzner, johnath, morgamic, lmesa, alix, blizzard, Unfocused
| Firefox checks for outdated plugins and takes you to a page on mozilla.com to get updated plugins.
| 09/28/2009
| 1.9.2
| Patch is waiting for review, strings have landed
|-
| [[Firefox/Projects/Per Tab Network Prioritization|Per Tab Network Prioritization]]
| zpao
| limi
| Wrap up "rewrite" and start getting reviews. Figure out testing plan.
| 2009/09/25 (for next step)
| 1.9.2
| Converting to JSM, Setting up prefs
|-
| [[Firefox/Projects/Places Vacuum|Places Vacuum]]
| mak
| sdwilsh
| Fragmented databases are known to cause performance problems. Try a Places implementation before investigating an app-wide vacuum.
| 03/09/2009
| 1.9.2
| Landed, needs refinements to tests.
|-
| [[Firefox/Projects/Places UI|Places UI]]
| faaborg
|
| Investigate changes to the places UI for 3.6 and 3.7, focusing on mixing serach + browse operations, and leveraging the content area.
|
|
| Creating mockups based on work week meetings.
|-
| [[Firefox/Projects/Reduce Places Views Overhead|Reduce Places Views Overhead]]
| Mano
| mak
|
| 20/09/2009
| 1.9.2
| Near final patch.
|-
| [[Firefox/Projects/about:support|about:support]]
| cbartley
| TBD
| Create an in-content about:support page that support can use to help users with problems.
| ???????
| 1.9.3 (1.9.2?)
| Getting up to speed.
|-
|}

= Inactive Projects (need to finish) =
* [[Firefox/Projects/AcceleratedScrolling|Accelerated Scrolling]]
* [[Firefox/Projects/Multitouch Polish|Multitouch Polish]]
* [[Firefox/Projects/Doorhanger notifications|Doorhanger notifications]]
* [[Firefox/Projects/Eradicate Startup Dialogs|Eradicating Startup Dialogs]]
== Prioritized ==

*[[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/Tab Matches in Awesomebar|Tab Matches In Awesomebar]]
*[[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/Unbreak RSS|Unbreak RSS]]
*[[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/Extension Manager API|Extension Manager API Updates]]
*[[Extension Manager:UI Update|Addons Manager Redesign]]
*[[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)]]

== Unprioritized ==
* [[Firefox/Projects/Jetpack_Uplift_Exploration|JetPack Uplift]]

= Additional Projects Ideas (Need more definition) =
* [[Firefox/Projects/ExperimentalPlacesSchema|Places Schema Redesign]]
* [[Firefox/Cleanup|Areas that need code cleanup or overhaul]]
* [[Firefox/Projects/App-wide Database Integrity Check|App-wide Database Integrity Check]]
* [[Firefox/Projects/Migration Component JS Porting|Migration Component JS Porting]]
* [[Firefox/Projects/Rewrite Places SQL Query Builder|Rewrite Places SQL Query Builder]]
* [[Firefox/Projects/Create a Places page thumbnail service|Create a Places page thumbnail service]]
* [[Firefox/Projects/Crowdsource_Performance_Data|Crowdsource Performance Data]]

= Completed Projects / Archive =
* [[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)

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

Firefox/Projects/Per Tab Network Prioritization

2009-09-03T19:01:27Z

Zpao: /* Bugs */

= Overview =

'''Sprint lead:''' zpao

'''Sprinters:''' zpao, limi

'''Description'''

:We want to do some network prioritization such that the tab / window that you are currently using have higher network priority than the ones you aren't using.

''The goal is to optimize tab loading and performance on startup.''

We propose to do this in two stages: 

*'''Firefox 3.6''': A simple enhancement where we assign priorities to the network loading of the different tabs. This should give us a quick win and make the initial page load of the focused tab complete earlier.
*'''Firefox 3.7''': A more comprehensive enhancement to make it possible to load tabs in most-recently-used order, as well as possibly set a threshold for how many tabs get loaded at once. This should take care of the more extreme cases where people are opening 30+ tabs on restore. 

= Goals / Use Cases =
* Make Firefox feel like it's starting up faster.
** While Firefox (or at least the tab / window being used) should become more immediately usable, I don't think total load time will be faster.
* Make current tab more responsive than background tabs.

= Non-Goals in this iteration =

The first iteration will be a simpler version, for the next iteration (3.7?) we should consider:

*MRU network prioritization.
*A threshold on how many tabs are loaded in parallel to control cpu/network load.
*Batch up these groups based on MRU order. 

= Design =

There are a couple ways we could do this:

*Put it all in tabbrowser.xml & browser.js & just jigger priorities directly.
*Put it in a new component (or whatever) that listens for TabSelect (and window select) 

If possible, we also want to be able to have an interrupt give higher priority to a tab if you switch to it during the initial page load. E.g. if you switch to the unfocused window, the priorities mirror what was in the initial focused window had, and the now-unfocused window has its priorities downgraded. 

= Prioritization =
== Priorities ==
[https://developer.mozilla.org/en/nsISupportsPriority Priorities] range from 20 to -20 with -20 being the highest. There are 5 presets (highest, high, normal, low, lowest).

== What To Do With Priorities ==

The general proposition here is as follows:

{|
|-
! 
! Focused Tab
! Unfocused Tab
|-
! Front-most Window
| high
| normal
|-
! Background Window
| normal
| low
|-
! Minimized Window
| low
|
lowest

|}

A visual way of looking at it — [] indicates frontmost tab:

'''Focused window:'''
<pre> ________ ________ ________
| Medium || [High] || Medium |
</pre>
'''Unfocused (but visible) window:'''
<pre> _____ __________ _____
| Low || [Medium] || Low |
</pre>
'''Minimized window:'''
<pre> ________ _______ ________
| Lowest || [Low] || Lowest |
</pre>

= Bugs =
* {{bug|514490}} Actual implementation bug
* {{bug|511503}} Window activate/deactivate DOM events

= Resources =
* [http://groups.google.com/group/mozilla.dev.apps.firefox/browse_thread/thread/94bf663f787b711e Limi's dev.apps.firefox thread] (has some useful implementation insight from bz)

User:Beltzner/feedsforplanetfirefox

2009-08-30T23:51:51Z

Zpao:

Feeds of content specific to Firefox development (use a tag or category with your blogging software, and post the specific feed here):

* beltzner: [http://beltzner.ca/mike/tag/firefox/feed/ http://beltzner.ca/mike/tag/firefox/feed/]
* vlad: http://blog.vlad1.com/category/firefox/feed/
* gavin: http://www.gavinsharp.com/blog/tag/firefox/feed/
* ryan: http://screwedbydesign.com/blog/category/firefox/feed
* johnath: http://blog.johnath.com/category/mozilla/feed/
* Blair: http://theunfocused.net/category/firefox/feed/
* Boriss: http://jboriss.wordpress.com/tag/firefox/feed/
* MattN: http://matthew.noorenberghe.com/tags/firefox/feed
* dietrich: http://autonome.wordpress.com/tag/firefox/feed/
* felipe: http://felipe.wordpress.com/category/firefox/feed/
* adw: http://blog.mozilla.com/adw/tag/firefox/feed/
* dao: http://design-noir.de/log/category/planet-mozilla/feed/
* ddahl: http://www2.blogger.com/feeds/12940211/posts/default/-/firefox
* rstrong: http://blog.mozilla.com/rstrong/tag/firefox/feed/
* mossop: http://www.oxymoronical.com/blog/tag/firefox/feed/atom
* limi: http://feeds.limi.net/on-firefox
* zpao: http://zpao.com/tags/firefox.rss

;How to get a tag-specific feed out of Wordpress
:In Wordpress you can get a feed per tag; for example, the tag of "firefox" will result in a feed at http://url.of.blog/path/tag/firefox/