Browser Window

designer handbag kate replica spade wholesale replica coach handbag coach signature replica handbag wholesale aaa replica handbag aaa chloe handbag replica aaa grade handbag replica handbag lv replica wholesale hermes handbag replica cheap replica handbag cheap replica chanel handbag cheap replica coach handbag cheap wholesale replica handbag cheap designer replica handbag wholesale replica chloe handbag chloe handbag paddington replica chloe designer handbag replica fendi replica handbag fendi and gucci replica handbag wholesale designer replica handbag replica designer handbag at wholesale prices wholesale replica handbag handbag wholesale replica watch wholesale replica lv handbag replica handbag wholesale price replica chanel handbag replica designer handbag chanel discount chanel handbag replica handbag louis replica theda vuitton handbag louis replica shopping vuitton bag image louis mirror replica vuitton bag designer diaper replica bag dior replica bag christian dior replica bag hermes replica bag birkin hermes replica bag burberry replica

=== Introduction ===Several elements of the browser front end code are what could optimistically be described as a sewer. The main browser javascript file has for the past six years been a poorly thought out, dumping ground. We have all contributed. The browser code in general is hard to follow, lightly if at all documented, and miserable for extension developers. We have also discovered limitations of the <tabbrowser/> widget (though I want to point out its limitations are not related so much to code quality as intent-vs.-use and lack of documentation) - it is difficult to extend and embellish. As a result, I would like us to embark on an adventure to fix this code. This involves:* identifying target uses* auditing the existing code for behavior* developing a general design for the new browser* incrementally refactoring existing code to achieve this design=== Browser Uses ===# Clearly identified ways of inserting per-tab content. (e.g. InfoBars)# Clearly identified ways of attaching progress listeners to tabs# Ability to listen for new tab creation/tab removal etc. (basically an interface to allow clients - whether they be XUL UI or completely external to detect for new content windows and hook into them)# Clear integration points for extension menuitem insertion into menus# Simple, well-documented code that encourages the same from our extension development community.=== Stages ======= Code Audit ======== Tasks ====# Kill nsBrowserInstance
The browser "appCore" appears to be used for nothing more these days than the Page Cycler, which is used by some tinderbox tests. The Page Cycler should be redeveloped as an extension, and this dependency on xpfe/ excised completely.# Organize Event Handlers
# Organize Components
# Organize Pref Observers
=== Other Things ===Some other things that need to be done elsewhere in the codebase to generally make the browser better from an extensibility and code quality point of view:# Improve the Search Service (sherlock files in profile, support postdata, more attributes, better management, no advanced search service cruft)# Improve the <toolbar/> widget and its customization capabilities - especially for extensions