Navigator: Who to bug?
This document lists what features the Navigator team members currently work on --both developers and QA. In an effort to more quickly get bugs to the right people, use this as a guide when assigning bugs or cc'ing others for input or help.
- Who works on what?
- What is worked on by whom?
- What bugs should or should not be filed under XP Apps?
|Who in development||What|
|email@example.com||accessibility, keyboard navigation|
|firstname.lastname@example.org||directory viewer (ftp and http listings), ftp & gopher networking|
|email@example.com||Preferences code module, Profile Manager frontend, download manager, XUL, full screen mode|
|firstname.lastname@example.org||turbo mode & QuickLaunch, global history, drag & drop, context menus, download manager, Bookmarks, other XP Apps features|
|email@example.com||XUL file picker, tabbing navigation, event handling, mousewheel, XBL form controls|
|firstname.lastname@example.org||View Source UI|
|email@example.com||tabbed browsing, Linux integration, Strings, performance|
|firstname.lastname@example.org||Win32 integration, Win32 file picker, helper applications, file download UI, printing frontend, command-line options|
|email@example.com||Form, Cookie, Password & Image Managers, context menus, full screen mode|
|firstname.lastname@example.org||Search, Sidebar, Preferences, What's Related, Internet Keywords, printing frontend|
|Who in QA||What|
|email@example.com||URL Bar, Search, What's Related, Internet Keywords, bookmark & site/fav icons, bookmarks, group bookmarks (tabbed groups), history, Tasks switching|
|firstname.lastname@example.org||download manager, helper applications, file saving, OJI (Java)|
|email@example.com||Themes, skinability, Open Web Location, View Source UI, Page Info, Find in web page, selection, copy & paste, drag & drop, Win32 integration, tabbed browsing|
|firstname.lastname@example.org||keyboard navigation, preferences (Preferences dialog & about:config), main menus & context menus in Navigator, directory viewer UI, file pickers, Properties|
|email@example.com||plug-ins, XP Toolkit (XUL, etc.)|
|firstname.lastname@example.org||editor (Composer), Sidebar, DOM to text conversion, printing|
|email@example.com||Form, Password & Image Managers, online help, imageLib & imaging, tooltips, turbo mode & QuickLaunch, HTML form controls|
The following table isn't the exact converse of the one above --mainly since some of the features are also worked on by people in other groups. Hence, some features might not be listed, and there might be more than one person per feature.
This is not meant as a comprehensive listing. The table below focuses primarily on what features the Navigator group are working on. Do check the Bugzilla component lists for further information.
The XP Apps and XP Apps: GUI Features are a couple of the highest-traffic Bugzilla components, as they cover rather broad areas. Many bugs are simply duplicates of existing ones. However, many are not filed appropriately, and should therefore live in another component. Putting such bugs in the best (or, perhaps just better) Bugzilla components sends them to development and QA owners who can attend to them more quickly and effectively.
Okay, so what are appropriate bugs?Read the Bugzilla component descriptions for the browser. As well as this page. :-)
...And, what should NOT be filed in XP Apps or XP Apps: GUI?
Some examples, though not necessarily a comprehensive list:
- Problems with how web pages are displayed (appearance, rendering of page content) should probably go to Layout or one of the more specific HTML components
- Likewise, problems with how graphical content appears should probably go to ImageLib
- Problems with submitting a form should likely go to Form Submission; likewise, issues with how form controls behave or appear belong in HTML Form Controls
- Helper Application and downloading UI bugs belong in the File Handling component
- Problems concerning plug-ins (eg, QuickTime, Flash) should go to the Plug-ins component
- Problems with the tabbed browsing interface belong in the in Tabbed Browser component
- Problems which occur in one theme but not another should probably go to the Themes component; likewise, problems encountered after switching or installing themes belong in Skinability
- Problems with UI/management of passwords belong in Password Manager
- Problems with Java
- Problems with DHTML
- Problems with secure (https) pages
- Problems with Mail or News, eg, issues with any of the Mail & Newsgroups preferences panels
- Problems with Composer (editor)