667
edits
Changes
Add more potential projects (still a draft)
References: see [https://bugzilla.mozilla.org/show_bug.cgi?id=294608 bug 294608]
== Full-Text History Search extension ==
Firefox3 probably won't ship with support for full-text history search, even though url-bar autocomplete (with urls/titles) is a really great feature/idea. Write an extension in order to add this feature.
References: http://skrul.com/blog/projects/xpclucene/
== Improve Mozilla Application and Platform Documentation ==
* See also: http://starkravingfinkle.org/blog/2007/06/xulrunner-wishlist/ and http://www.songbirdnest.com/node/1826
* Contacts: plasticmillion
== Localize Mozilla ==
Join a localization team (see http://developer.mozilla.org/en/docs/Localization) and help localize Mozilla into a language other than English, for example, [http://blog.mozilla.com/ligong/2007/07/11/firefox-cn-localization-liaison-group-started/ Chinese].
== Testing of Canadian Banking and Financial Sites in Mozilla ==
This project will focus on improving the user experience at banking and other financial sites for Canadian Mozilla users. This includes determining which sites are relevant, insuring proper behavior for Firefox 3 on these sites, etc.
References: http://quality.mozilla.org/node/293
== My Favicons extension ==
Write an extension to allow the user to pick his/her own favicons for sites, based on a URL regexp. The image should get stored as part of the user’s profile, so that it doesn’t have to live in the same place on the user’s disk. Ideally, it should also be possible to export the regexp -> icon mapping as a regexp -> data URI mapping that can be imported into another profile.
References: http://blog.vlad1.com/archives/2007/08/10/151/
== Tbeachball - Quantifying Mozilla's Responsiveness ==
This project will add instrumentation to Mozilla in order to determine how much time is spent away from the main event loop, and therefore from the user's mouse/keyboard input. When the user does something, how long does it take for Mozilla to act on that stimulus? One thing that sometimes interferes with interface responsiveness is spending too long away from the main event loop, perhaps in layout or some other intensive computation. This leads to new events from the user, such as mouse clicks or keypresses, not being noticed and acted upon. This could also be expanded in order to include the triggering of log points and specific dialog openings, etc. with a view to understanding what the long-running events actually are.
References: http://shaver.off.net/diary/2007/08/25/tbeachball/ and http://shaver.off.net/misc/latency-tracing-patch.txt
== Mozilla Developer Virtual Appliance ==
