https://wiki.mozilla.org/api.php?action=feedcontributions&user=DJ+Doena&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T12:25:36ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=User:DJ_Doena/Tab_Features&diff=36987User:DJ Doena/Tab Features2006-10-16T07:01:18Z<p>DJ Doena: /* "New Tab" Button in Tabbar */</p>
<hr />
<div>== Multi-Line Tabs ==<br />
<br />
Tabs shouldn't be smaller than a defined width because then the tab headers become unreadable. If this width is to fall short a second row should be opened. Like a multi-line Windows taskbar.<br />
<br />
== "New Tab" Button in Tabbar ==<br />
With the "Tabbrowser Preferences" ([https://addons.mozilla.org/firefox/158/] [http://216.55.161.203/theonekea/tabprefs/]) extension it is possible to have a "new tab" button at the begin of the tab bar. Firefox itself has such a button, too. But one cannot drag it onto the tabbar itself.<br />
<br />
== "Open Link in New Tab" should remain history ==<br />
If I mid-click a link then it opens in a new tab. Unfortunately the history is lost and the opened link is the "first one". The history should be preserved.</div>DJ Doenahttps://wiki.mozilla.org/index.php?title=Firefox/Feature_Brainstorming&diff=36973Firefox/Feature Brainstorming2006-10-16T06:01:47Z<p>DJ Doena: /* Tabs, sidebar, and windows */</p>
<hr />
<div>We are currently in the early development stage for Firefox 3, and would like to collect all the ideas for feature enhancements in a single place. Our goal is to create a single index that lists what sorts of things we're thinking of doing, with links to more detailed ideas about implementation specifics or concerns, and targets for inclusion in the project.<br />
<br />
'''Note: This is a list of feature enhancement ideas for ''all'' future Firefox releases, not just Firefox 3. Firefox 3 will include a subset of the items on this list.'''<br />
<br />
'''How to use this page'''<br />
* ''If you have ideas about features listed here'' please create a new wiki page off of your user page that outlines your ideas (mockups welcome!) and add a link to that page in the "References" column, or link to existing pages with examples, design thoughts, interesting articles, etc.<br />
<br />
* ''If you have ideas for features not listed here'' please add them to the most appropriate group below. Include any references to more detailed implementation ideas.<br />
<br />
* ''If you would like to comment on features listed here'' please do so on the [[Talk:Firefox/Feature Brainstorming|discussion]] page rather than in the list itself.<br />
<br />
* ''Etiquette:''<br />
** Please include a summary comment that describes your change so that it shows up in the page history view. <br />
** Please make a User page for yourself with contact information so that if we need clarification of your idea, we can get in touch with you.<br />
<br />
= Platform Integration =<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th></tr><br />
<br />
<tr><td><br />
; Integrate the KDE certificate Management<br />
* Firefox includes a lot of cryptographic code, as does KDE/Windows. This is redundant and not very user friedly. For example, when I import a certificate with Konqueror, it can automatically be used in KMail as well, this doesn't work with Firefox.</td></tr><tr><td><br />
; Integrate the Platform's password management<br />
* KDE and Mac OS X both provide facilities (keyring and kwallet) to store passwords. Firefox should use them so that one can use passwords originally entered in Konqueror in Firefox (or vice versa)<br />
</td></tr><tr><td><br />
; Port to Qt for better optical Integration<br />
* Even with the gtk-qt theme, Firefox still doesn't look good in KDE :(<br />
</td></tr><tr><td><br />
; Use the DE's settings to determine programs<br />
* On Windows, this works well already (you can for example download a zip file and it'll be opened with WinZip or whatever you are using. On Linux, this doesn't quite work yet (at least not with KDE) and you often have to choose your application manually.</td></tr><tr><td><br />
; use a KDE-style settings dialog<br />
* KDE Applications (unlike GNOME Apps) all use the same settings dialog, which is very user friendly because one doesn't have to learn how to handle yet another settings dialog. </td></tr><tr><td><br />
; use a KDE-style keyboard shortcut dialog <br />
* Similarly to the settings dialog, KDE offers a standardized dialog to set up keyboard shortcuts. Again, this is very handy because it's in the same place for _all_ KDE applications and it behaves the same and you don't have to search for it. (nb: even if you don't use KDEs dialog (you probybly won't), at least provide _some_ user-friendly way to configure keyboard shortcuts) </td></tr><br />
<tr><td><br />
; Better integration of other desktops<br />
* I happen to work with KDE a lot, but certainly, other Desktops provide similary interesting facilities as well<br />
</td></tr><br />
<tr><td><br />
; Optionally use WININET for URL fetching on Windows<br />
* Occasionally (e.g. behind a firewall with centrally administered settings, or in low-resource setups) it might be helpful if Firefox could alternatively use the HTTP implementation in Windows (WININET) instead of its own, as a result also sharing the contents of the cache, cookie jar and network settings with IE. This would effectively separate Firefox-the-Browser from Firefox-the-HTTP-client, and could be a high-level choice e.g. during installation.</td></tr><br />
<tr><td><br />
; Download Progress in OSX<br />
* Implement the download progress icon on incomplete file downloads on Mac OS X like Safari and Cyberduck.<br />
</td></tr><br />
<tr><td><br />
; Services Integration in OSX<br />
* Firefox does not supports Mac OS X services so that all the commands available in the "Services" menu are disabled. Other OS X applications (es. Safari) allows the user to use a services when some data, like a text, is selected.<br />
</td></tr><br />
<tr><td><br />
; Search Integration<br />
* Integrate history, bookmarks, or other forms of harvested micro-formatted content with OS search platforms such as Vista Search or Spotlight in Mac OS X.<br />
</td></tr><br />
</table><br />
<br />
= Browser chrome =<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
</table><br />
<br />
== Menus and Toolbars ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Make back button not break forward button<br />
<br />
*If you are at a site (site A), and push back a bunch of times to get to (site B), are then follow a different site to get to another site (site C) it is no longer possible to use the forward button to get to site A again. This should be fixed by storing a tree of the forward and backward locations, a use an interface that allow you to branch when going forward. (This UI could be part of the UI that shows when you click the little down arrow beside the forward button.) THIS IS A VERY GOOD FEATURE!<br />
<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Tool bars & menus<br />
* About 15% of screen real-estate is occupied by tabs, navigation bars, menu items, window name, scroll bars & status bar. Maximize this space by allowing the user to pull all toolbars off the top of the window and create a floating toolbar. These floating bars could be overlapped, tiled, etc to save screen real-estate. As discussed further below, add an option to make these floating toolbars partially transparent onto the viewer screen, i.e. blend them into the background of whatever webpage is being viewed.<br />
<br />
The browser window then looks more like a desktop than a window.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Adjustable menu and toolbar fonts<br />
* Allow much more menu flexibility in general, such as dragging buttons to precise places (possibly adding options such as the "align to grid" feature on Windows desktops), instead of having them snap into place.<br />
* Allow the user to specify the font (and especially the font size) used in menus and toolbars. This is especially useful for those of us with failing eye sight or those with high resolution screens (that cause the fonts to be too small).<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Custom toolbars<br />
* Allow the user to create custom toolbars that can be stacked or aligned to the left or right or bottom of the window.<br />
* You can put any kind of icon on these toolbars including shortcuts to websites (use favicons) or external apps.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Transparent Interface<br />
* If this will not already be applied in Windows Vista with Aero Glass, allow the user to make the address bar/buttons/bookmark toolbar transparent, except for on scroll over. In this way the user has another inch or two of website that is just a little obscured (better than all-the-way obscured)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Adjustable menu<br />
* Make it much easier for users to hide items from menus. A complete list of chrome names would be a start.<br />
* A configuration menu, within the Options menu should list all of the right-click menu options currently available. This would be done via a simple check mark box to either add or remove that function from the menu. A sub-option to move around the position (Either higher or lower, or possibly cascaded into other options) should be available as well. <br />
</td><td><br />
[http://kb.mozillazine.org/UserChrome.css_Element_Names/IDs Chrome element names and IDs - MozillaZine]<br />
</td></tr><br />
<br />
<tr><td><br />
; Back and Forward buttons<br />
* Create an HTML "Next Page" extension for the mouse forward button. See posting under Accessibility > General tasks.<br />
* Include right click options on back/forward buttons to open the previous/next page in a new window or tab. It would need to preserve the browse history in new window/tab. <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; View Page Info Improvements<br />
* Improvements for the <u>L</u>inks tab<br />
** Let the list be sorted by clicking on the table header (name, address, type)<br />
** Having selected some entries on the <u>L</u>inks tab, add the command "open selected link(s) in new tab(s)" to the context menu.<br />
** Add a column to the list from what the link has its anchor. For example text or image. In addition it would be cool if you could see which links lead offsite (and which not) in an additional colomn so that you could also sort for it.<br />
<br />
* Improvements for the <u>M</u>edia tab<br />
** Let the list be sorted by clicking on the headers of the list (Address, Type,...).<br />
** Having selected some of the items add the command "save media to ..."<br />
** Add a column "Type" that shows the "ending of the files for example "jpg, gif, png". Perhaps this could also use the content-type returned for the file.<br />
** Add a column "Size" that shows the size of the file, in human terms such as 1/3 Meg or some such, but will sort on # of bytes.<br />
<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Autohide<br />
* Add an option to the View menu to hide all the top toolbars and the tab bar when the mouse is not over the window header or, when in fullscreen mode, not at the top of the window.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Ability to view and print specific table element<br />
* Create a right-mouse button to view (or cut & paste) a portion of a tabled webpage by highlighting onto another tab, especially useful for printing text and/or an article without the page-hogging advertisements or webpage navigation menus, i.e. useful for pages that don't show a "Print-friendly" link.<br />
<br />
* A way to print Google maps and directions without having to go to their print-friendly version which lacks resolution, and has limited print options for maps that are printed with directions.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
== Browser customization ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Automatic update for Driver<br />
*An engine that recognize what kind of peripheral you have in your computer and automatically goes on the support site to compare the driver and eventually download it. not so hard because almost every manufacturers use unified driver for their products. ;)<br />
<br />
*Bah, Firefox shouldn't do everything for you. That sounds rediculously complicated, especially because Firefox is not only a Windows application.<br />
<br />
*you and me are problably able to do it by ourself, but thuosand of people, no! could be another useful thing that could bring more user!<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Fonts and Colors needs work<br />
* Fonts and colors (tools/options/content) needs totally re-worked. If you use your default colors and fonts, pages refuse to work correctly. At least they turn all white (all colors is turned off), and often, they won't render correctly at all. (This is a problem in most browsers I found.)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Opera Like Mouse Usage<br />
* Allow the user to use Opera like mouse gestures (like right click followed by left click for 'back' etc)...<br />
</td><td><br />
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]<br />
</td></tr><br />
<br />
<tr><td><br />
; File management<br />
* Improve and expand file management options (ie: "Open with")<br />
* "Open with" should allow open to specify the application from the keyboard. When given a pdf file, if I want to open it with /usr/bin/gv I need to click to the directory, and wait 3 minutes until the contents of /usr/bin load. I would like to be able to enter this from the keyboard.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<tr><td><br />
; Save a Website<br />
* Improve saving of a Website (ie: include originating URL in the saved file - as IE does)<br />
* Optionally compress additional files (usually stored in an extra directory) together with the Website to save in an archive, because it sucks having a directory with the debris of a hundred of files named e.g.: "img0,0aa1781,21aa12.gif" and the like<br />
see MAF (mozilla Archive format which was perfect but doesn't work with newer versions of firebird on Linux and is not improved anymore.-<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Fast Profile Switching<br />
* Allow for profile switching within FireFox. This would allow two versions (Lean & Extended) to run as the user chooses. <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<br />
<tr><td><br />
; Add-on management<br />
* Version compatibility<br />
* Options management<br />
* Integration with AMO<br />
* Support for remote extensions (i.e. dev tools package)<br />
* Allow user to disable plugins via "about:plugins", Options/Prefs, or Extensions<br />
* Export/Import of Addons Information.<br />
* Ability to store/receive plugin configuration metadata (ie. which plugins are installed and what is their configuration). With this, we could fine-tune the config of our Firefox at home, then we could have the same configuration installed at work, without remembering all the plugin names and configuration quirks. I guess this could be done at a central server. Items would be accessible with a simple username/password (without any other data and account creation hassle). This might be integrated with the Mozilla site account system, too (so a save could open an account, if the user click the relevant checkbox). NB. some plugins might store private information and that should not be stored.<br />
* Make it easier to find high-quality and reliable add-ons<br />
* Have "Extension Packs" available for download immediately upon completing a Firefox install (also see "Installer" notes)<br />
* "Update All" extensions button<br />
* When the plugin finder doesn't find any suitable plugin, show a description for making easier to the user to find it (show data type?)<br />
* Make extensions "cleanware". Let all of their configuration lie in their own file directory instead of mashing it together with other extensions' configuration in One Big File. This reeks of Windows' "Registry Hell". Cleanly uninstalling an extension should be as simple as deleting its subdirectory.<br />
* Dynamic loading/unloading of extensions. No more restarting just because an extension was installed/uninstalled/updated.<br />
* Provide changelogs for extension updates (Do I really want to update?)<br />
</td><td><br />
- [http://forums.mozillazine.org/viewtopic.php?t=197645 FAQ on forum]<br /><br />
- [http://www.extensionsmirror.nl/index.php?showtopic=1048 Extensions summary on TEM]<br /><br />
- [[User_talk:Autodmc#Lean_and_Mean_vs._Super_Install | "Extension Packs" from installer idea]]<br /><br />
- [[User_talk:Topa#Import/Export_of_Addons_Information | Provide functionality to export and import addons-information using RDF]]<br /><br />
- [[Extension compatibility ideas]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Optional IE theme<br />
* Same size and button positioning<br />
* Tab opening like IE7<br />
* Back/forward buttons under same dropdown (forward is rarely used)<br />
* Go/Reload button occupies same space<br />
* Menus hidden by default (press alt to show)<br />
* Avoid a blatant ripoff of IE7<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; External editing<br />
* Allow an external editor (emacs, textpad, etc) to edit text in form text boxes<br />
* Currently supported by plug-ins, but only on some platforms; should be available everywhere<br />
* As more and more apps move towards web services, the ability to effectively edit large blocks of text (wikis, blogs, forums, webmail) becomes more and more critical.<br />
* Include ability to save/restore the text box contents.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<tr><td><br />
; Time/day sensitive home page(s)<br />
* Change Home page or pages depending on the day or time of day, e.g. the first time the browser is opened the Home pages might be woot.com and some news sites. Later in the day, opening the browser or clicking on 'Home' might open slashdot and fark.<br />
* Could be sensitive to time/day/date and whether the browser has already been opened today.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve extension installation/management UI<br />
* Unify add-ons management (extensions, themes, search engines, dictionaries, plugins)<br />
* Improve interaction design around customizing browser interfaces<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Customizable Status Bar<br />
* Allow the Status Bar to be customized like the toolbars can. Any toolbar button should be able to be put on the status bar and vice/versa<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Capturing pages to PDF file<br />
* Capture all pages in the window (including links upto user selectable depth) directly to PDF file<br />
* This is similar to ScrapBook extension with additional functionality of saving in PDF.<br />
</td><td><br />
[https://addons.mozilla.org/firefox/427/ ScrapBook :: Mozilla Addons]<br />
<br />
</td></tr><br />
<br />
<tr><td><br />
; elinks-style unified customization hooks<br />
* elinks has an array of useful customization hooks encoded (typically) in lua that unify url shortcuts, greasmonkey-like content-rewriting, etc. it is not so much the lua integration i am highlighting (although i prefer it to javascript), but the fact that elinks does not delegate customization to disparate extensions and tools.<br />
</td><td><br />
</td></tr><br />
</table><br />
<br />
== Preferences ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Saved Form Information<br />
* It is very handy to have this information when filling out a form. But, as humans, sometimes we make a typo. Or, the entered information becomes outdated, etc. Please add the option to edit or remove individual entries in the Preferences dialog. <br />
* An alternate solution for the above problem: pressing the "del" button (instead of Ctrl+Shift+Del which is not really intuitive) in a form control history dropdown control could remove that entry off the history.<br />
* Another concern: saving of credit card information. When on a secure site, I can go to the credit card field, start typing in my card number, expiration date, etc and it will be in the autocomplete. Same thing with my SSN, address, phone number, etc. I would appreciate an option to disable the saving of form information on https (secure) pages. Another approach would be to include an option (not mandatory), to pop up a dialog.. something like: "This appears to be a credit card (SSN, etc) number, do you want it to be saved?"<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
Allow a time set feature to open a set of specific tabs at a desired time of day.<br />
<tr><td><br />
; Multiple Configuration states<br />
* Many customizations provide a lot of features, but also a lot of clutter. Rather than manually adjusting toolbars to fit your current activity, it would be much more efficient to store multiple customized states that can be easily selected from, by name. There are multiple state categories, such as toolbar layout, bookmarks, skins, etc. A saved configuration state could be defined to include only a subset of states.<br />
* This information could be saved to/retrieved from a central server with a username/password (without any prior account creation hassle), so we could have the same environment on every Firefox installation.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; "Tabbed" Toolbars<br />
* Multiple toolbars could be stacked and "tabbed" similar to tabbed pages, which is a popular feature. Rather than tabs, the selection could be similar to a pull-down menu, where each entry is a toolbar. Instead of selecting a toolbar, one could also click the pulldown button, then click one button on any of the transiently displayed toolbars.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Preference Locking<br />
* Make it easier to lock preferences. For example make it possible to make pref.js and bookmarks.html write protected. As of now Firefox creates lots of copies if you make those files not writeable.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; List filtering <br />
* add filtering to the following lists (like the filtering for the Cookies list):<br />
** Allowed Sites - Popups<br />
** Black list sites (this sites won't be allowed to open popups)<br />
** Exceptions - Images<br />
** Exceptions - Cookies<br />
** Allowed Sites - Add-ons Installation<br />
** Don't Remember Passwords by full URL<br />
** Remember Passwords by full URL<br />
** Open External Links in (by application? by param?) <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Per-Site Preferences <br />
* Allow the user to specify blocking of images, use of specified fonts & colors, allowance of JavaScript, etc. on a per-site basis. Similar to the above suggestion, but more fine-grained and implemented in an (IMO) easier-to-use manner.<br />
** Could also store if Java and Flash is enabled on that site.<br />
** Examples: current NoScript and AdBlock plugins. The features of them could be integrated.<br />
*** NoScript shows what rules are active on the page, without having to go into the prefs. Also, rules can be changed right there.<br />
*** With AdBlock, you can see what objects are accessed on the page and you can add a new blacklist rule based on this info.<br />
*** This could be extended with the ability to sort by extension or MIME info.<br />
*** Also, a possibility of whitelisting object(s) would be a good idea.<br />
</td><td><br />
[http://www.omnigroup.com/applications/omniweb/gallery/content.html#8 OmniWeb Features:Site Preferences]<br />
</td></tr><br />
<br />
<tr><td><br />
; User controlled alternative style sheets. <br />
* Allow the user to specify what style sheet shall be used for a page using a regular expression (regexp).<br />
</td><td><br />
See [[feature request for Firefox 3]].<br />
</td></tr><br />
<br />
<tr><td><br />
; Shortcut Key Configuration<br />
* Creating customized shortcuts to preferred Firefox functions using unassigned keyboard combinations.<br />
* Creating shortcuts for sites/links/bookmarks<br />
* UI for displaying/searching/modifying existing key combinations, displaying what does every keyboard shortcut mean in every context (much like Opera does).<br />
</td><td><br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
When firefox is installed in a system behind a firewall and proxy needs to be set to access the web, we need to go to preferences and set the proxy. Instead we can have a popup coming up if there is no proxy setup. And we can enter the proxy details in that popup.<br />
<br />
If not completely automated, at least proxy settings should be saved in profiles, so that when changing network (more and more common with laptops and various wlan accesses) settings can be changed in a fast way<br />
</td><td>Check out the extension [http://mozmonkey.com/switchproxy/ SwitchProxy]. It adds a status bar menu to quickly switch between proxy cfgs.<br />
</td></tr><br />
<tr><td><br />
When Netscape 4 was around it supported a users full profile being stored in LDAP. This operated in much the same way for the user as Google browser sync does now but the data was stored in an LDAP directory. This functionality should be returned to Firefox probably supporting multiple backend stores, sql, ldap, webdav etc.<br />
</td><td><br />
</td></tr><br />
<tr><td><br />
Early Netscape allowed the user to "save as" a web page as text, postscript, HTML,pdf, etc. These days, we seem to be only allowed to "save as" in HTML. This then means we have to use time-consuming external programs instead of it being a quick and easy drop-down selection. Please give us back our old "save as" options and also include a new ODF "save as" option. That would be a great improvement. Thanks<br />
</td><td><br />
</td></tr><br />
<tr><td><br />
Allow user to add file types in addition to being able to change how Firefox "manages" them.<br />
<br />
Allow Firefox to search inside text typed in textboxes (available in IE).<br />
<br />
Allow image placeholders to appear before the image starts being displayed (available in IE).<br />
<br />
Allow "View Image" to display the image right where it is (available in IE). [Last three entries by [[User:CarlRogerson|CarlRogerson]] 23:52, 14 October 2006 (PDT)]<br />
</td><td><br />
* FF 2.0 supports searching in textareas.<br />
</td></tr><br />
<br />
<br />
</table><br />
<br />
== Tabs, sidebar, and windows ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Tabs<br />
* The close [X] button should only be shown on the open tab to prevent people from accidentally closing tabs upon selecting them. Close buttons on out-of-focus tabs should only show after a 1 second mouse-over.<br />
* Allow the tab-bar relocation, probably with a simple pull-down, that includes top, bottom, left and right.<br />
** When left or right are selected (or perhaps all the time), provide the ability to specify a fixed width for tabs/tab-bar.<br />
** When left or right are selected provide option which displays tabs in a tree based on ancestry relation ship of a tab like in [http://piro.sakura.ne.jp/xul/tabextensions/index.html.en Tabbrowser Extensions]<br />
* A right-click option to pop an existing tab out into a new window.<br />
* Thunderbird Tab -- Opens Thunderbird within a tab rather than a separate Thunderbird window<br />
* Sunbird Tab -- Opens Sunbird within a tab rather than a separate Sunbird window<br />
* Tab collections used to organize tabs, think Linux virtual desktops <br />
* Multiple initial pages with tabs<br />
* Displaying tabs over multiple rows<br />
* Give the option in the preferences menu to allocate a 'unique' close tab button in the right like 1 and 1.5 versions of firefox instead of 1 close button per tab like Firefox 2---so you can choose---<br />
* Option to open default page when creating a new tab<br />
* Tab drag and detach<br />
* Window drag and attach as tabs<br />
* Drag tabs between windows<br />
* Make middle-clicking/open link in new tab work for javascript links (e.g. by duplicating current page in a new tab then executing the javascript on the new tab and forcing any 'pop-up' links to stay in that new tab)<br />
* "Open this tab in a new window" added to context menu (when right clicking on existing tab). Preserve history so back button works in new window just as it would on existing tab.<br />
* Select on close behavior<br />
* Tab switching via Mouse Scroll Wheel (on all Platforms) while mouse is on/over the tab bar<br />
* Add arrows to the right and left ends of the tab bar when it gets full to unhide/allow to see all tabs<br />
* Grouping of tabs (possibly by multiple tab rows)<br />
* Open tabs one upon the other and/or side by side in a single window<br />
* Shading of Tabs denoting time since it started (On the scale of white to black, white is more recent than black)<br />
* Recursive tabs for better tab grouping ("Open in new tab under current tab")<br />
* Tab exposé<br />
* Option to view tabs in sidebar (with thumbnails)<br />
* Multiple tabstrips<br />
* Tab dock<br />
* Finding tabs<br />
* select tab from command line mozilla -remote "selecttab(http://www.mozilla.org)"<br />
* Improved UI for finding and reopening any one or more closed tabs (including shortcut key)<br />
* UI for modifying tab width (f.e. splitter between tabs that can be dragged to change the width of all tabs)<br />
* Tab opening + closing animation<br />
* Allow "open in new tab/new window/same window" settings to be set per tab. Allows use of a home page like Google or Yahoo to open links in a new tab, but other tabs links can open in the same tab.<br />
* Allow opening new tab when domain name is different from current page<br />
* Allow opening in new tab for form submits. Allows user to type several consecutive searches into a search box while opening the results in new tabs in the background.<br />
* Allow relative opening of Tabs, i.e. child tabs open next to parent tab in opening order (and not at the end of Tab bar)<br />
* Display multiple tabs in tiled panes (both vertical and horizontal panes, preferably mixed.<br />
* Cascade tabs<br />
* Allow for windowblind treatment of tabs<br />
* Faster tab mouseover feedback, i.e. show in status bar or set tooltip delay to 0<br />
* More detailed tab mouseover feedback, i.e. thumbnail image of page with some options on what you want to do with this page like bookmark it, reload tab, protect tab without right clicking it<br />
* Multiple tab selection via Ctrl + left click on desired tabs. Feature would allow users to use the right click options on only the selected tabs. EXAMPLE: Right click on one of the selected tabs and select "Close Other Tabs" leaving only the selected tabs behind.<br />
* To save a lot of space, make the favicon on each tab into the "X" on hover.<br />
* Instead of the "..." in long tab titles, change to a fade to grey on the last three letters.<br />
* A right click option for when highlighting plain text urls to open in new tab as opposed to having to copy then paste in a new tab address bar; available as an add-on https://addons.mozilla.org/firefox/1864/<br />
*Allow tabs to not be full window. If a js opened window is redirected to a tab, and the size is smaller then the window, make the tab like a little window inside the window.<br />
* When a tab ask for identification, it shouldn't get on top automatically<br />
* Make the current tab not shrink with the others, so is more visible.<br />
* Copy the (back button) history of the current tab when a link is opened in a new tab (so that the user can go back in the new tab).<br />
* Allow the user to "lock open" a tab or window to prevent accidental closure. Implement an easy way of "undoing" the last window or tab closure.<br />
* Like eclipse on mouse over a tab the close button will appear<br />
* Ability to change tab titles and save tab titles so that when you enter the site again you will see your own tab titles (Different from page title)<br />
* Sort tab according to time opened, title, time idle<br />
* Options to have no title and Icon only with 32x32 icon with a close button located bottom right of the icon<br />
* Panels of tabs - by grouping of tabs you can have groups of multiple tab in a panel, like linux panels<br />
* Be able to display two tabs side-by-side, very useful on widescreen monitors<br />
* Tabbed source viewer<br />
* Nested tabs (eg. drag tabs into a tab) and multiple rows of tabs (see this mockup: [[media:Nested-tabs.png]]).<br />
* A button on the right click menu (on web pages) to open all links on this page in new tabs<br />
* A button on the right click menu for back/forward to open the back or forward in a new tab<br />
* Opera remembers which tabs were open when the user last closed the browser and opens all these tabs again upon relaunch. Firefox should do the same and should also remember each tab's browsing history; allowing the user to reopen Firefox, have all the tabs that were open available again, and be able to click back and forward for each individual tab.<br />
* Have a configurable option so that when a user does "Open All In Tabs", they do NOT replace all the current tabs, but open IN ADDITION to the current tabs already open.<br />
</td><td><br />
[http://kb.mozillazine.org/Category:Tabbed_browsing Tabbed Browsing -MZKB]<br /><br />
- [[Link_Targeting|design thoughts for tabs instead of windows]].<br /><br />
- [http://weblogs.mozillazine.org/ben/archives/009210.html Ben Goodger blogs about tabs].<br /><br />
- Whether [[Ctrl_W_not_close_app|Ctrl+W should not close the app]].<br /><br />
- [[User:Ge.diego|Ge.diego]] made some [[User:Ge.diego/Tab_Management_Comments|comments on Ben Godger test build that includes new tab management]] and gave an [[User:Ge.diego/User_Interface_Mockup|alternative user interface mockup proposal]]<br /><br />
- [http://users.blueprintit.co.uk/~dave/web/firefox/TabSidebar/index.html Tab Sidebar extension homepage]<br /><br />
- [http://guides.macrumors.com/Show_Safari_Form_Results_In_New_Tab Show Safari form results in new tab]<br /><br />
[http://www.extensionsmirror.nl/index.php?showtopic=2959 Tab Related Ext - TEM]<br /><br />
[https://addons.mozilla.org/firefox/1122/ Tab Mix Plus - UMO]<br /><br />
[http://userstyles.org/style/show/1136 Active Tab Flex at userstyles.org <br>]<br />
[http://wiki.mozilla.org./User:Tuomaz Two tabs side-by-side]<br />
<br /><br />
[http://piro.sakura.ne.jp/xul/tabextensions/index.html.en Tabbrowser Extensions] has some really great ideas.<br />
<br/><br />
[[User:DJ_Doena/Tab_Features|Current problems with tabs and their probable solution]] by DJ Doena<br />
</td></tr><br />
<br />
<tr><td><br />
; Browser Window<br />
* Ability to split the browser window vertically or horizontally, similar to emacs windows, and load different urls into each. Common usage cases for this are when you want to see two different pages at once conveniently, monitoring multiple sites at once, etc.<br />
** Simply allow to split the window vertically with the same page for working with long pages, as in Visual Studio .NET.<br />
* UI-level Multicolumn mode, like Emacs Follow mode - split the browser window into two (or more) panes, showing the same page, the right pane leading on from the left pane. Excellent in these days of wide monitors and inexplicably narrow fixed-width web pages! <br />
* Allow 'drag & drop' of links anywhere on the browser window (not just the tab bar) to open the link in a new background tab (e.g. 'drag & drop' links from Google Search Results/Google News/Digg Front Page etc. to open several background tabs)<br />
* Allow 'drag & drop' of selected text on a web page anywhere on the browser window to conduct search on the selected text using the default search engine and opening the search results in a new background tab<br />
* Scroll document with middle mouse button click-drag-release. The reverse to the familiar glove that moves the document. This behaviour maps to how scrollwheels/scrollballs work, which often also occupy middle mouse button.<br />
* Open link in new window with middle mouse button. GUI-configurable option.<br />
* Create a way to rotate a window in four directions to allow viewing long web pages on a laptop by rotating the laptop sideways. This is one of my favorite commands in Preview in Mac OS X. Please make sure the command to do and undo this can be made a shortcut.<br />
* Open different windows each as a new browser instance so that a crash in one does not take down all other instances.<br />
* "Application Mode" - allow web applications to act more like native applications. Give them the ability to have their own launcher from the Start Menu or Dock, and their own icon and process so that the OS can treat apps like gmail just like any other app. Currently such apps are labelled "Firefox" by the OS. Hide unnecessary GUI elements such as Bookmarks bar and Address bar in this mode, for more screen real estate.<br />
* Better awareness of Multi-head environments. Under traditional X Windows dual head (so the two screens are two different X displays) you can't run the same firefox profile on both screens. Under Xinerama, everything appears as one very wide screen, but now it would be nice to have a "two window mode" analagous to "single window mode" although maybe this is an extensions question.<br />
<br />
</td><td><br />
[http://superdragandgo.mozdev.org/ Super DragAndGo Extension allows you to drag links and words in order to surf and search]<br /><br />
[[User:DGolden:Follow]]<br /> <br />
[[User:Jeric]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Session management<br />
* Ability to save and restore sessions (tabs, etc.)<br />
* Implement some method to deal with session sets<br />
* Make session restore fast and precise (save and restore DOM, or use FastBack data)<br />
</td><td><br />
[http://kb.mozillazine.org/SessionSaver SessionSaver - MZKB]<br /><br />
[https://addons.mozilla.org/firefox/436/ SessionSaver - UMO]<br /><br />
[http://forums.mozillazine.org/viewtopic.php?t=47184 SessionSaver (rewrite) - MZForum]<br /><br />
[http://sessionmanager.mozdev.org/ Session Manager Ext]<br /><br />
[http://tmp.garyr.net/ Tab Mix Plus with Session Managment]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Sidebar<br />
* Sidebar animation<br />
* RSS animation<br />
* Allow the windows from downloads,extensions,bookmarks and history to dock as sidebars. A bit like the extension All-In-One-Sidebar.\<br />
* Better handling of multiple searches in different windows (see [https://bugzilla.mozilla.org/show_bug.cgi?id=45082 Bug 45082])<br />
</td><td><br />
- [http://firefox.exxile.net/aios/screenshots.php?PHPSESSID=a4f4bfaacaa8c756b236f44315b3188d Screenshots of All-In-One-Sidebar extension].<br /><br />
</td></tr><br />
<tr><td><br />
; Web Page easy handling <br />
* Allow to put a tag on whatever place of a web page, like a gg map interface. The tag is remembered on the right side bar of the window, can be bookmarked. when the bokkmark is clicked, the window is open and focus down to the bookmark<br />
* Allow to do a "spreadsheet like behaviour on a web page" : you can click on th tag to say "freeze up" , and when you move the cursor down the lower part of the page is scrolling down, the upper part stay unmoved,<br />
* Allow to compact the web page between 2 vertical tags<br />
* Allow for a specific web page to apply tag rules : place tags automatically between paragraphs, to allow easy compacting of un-interesting ones , propose a default "compacted" presentation" or "fully opened" behaviour on those pages.<br />
* Multiple link selection <br />
** Click and drag to select multiple links on a page<br />
** Right click to open multiple link context menu<br />
*** Open multiple links in new tabs<br />
*** Open multiple links in new windows<br />
</td><td><br />
n/a<br />
</td></tr><br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
*Add "Login As" option under file menu for accessing FTP sites that do not allow anonymous logins. This was available in previous versions of Internet Explorer and was handled by an automatic opening of the FTP site in Windows Explorer.<br />
*Add an FTP manager, similar to Windows Explorer tracking of previously accessed FTP sites.<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Search/Find ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Search plugins<br />
* Ability to change search engine/plugin via keyboard<br />
* Ability to organize search plugins better<br />
* Ability to remove search engine addons from search box easily<br />
* Associate keywords to search plugins<br />
* Transient assignment of search plugin to search bar<br />
* To the extent reasonable, unify search plugin interface with bookmark interface: they both do many of the same things<br />
* No longer require an extension to add/remove search engines. This should be accomplished by simply copying the appropriate URL to a list like done in Galeon and AcidSearch for Safari.<br />
* Ability to highlight text and from the right click context menu send the text to any of the search engines you have installed ([https://bugzilla.mozilla.org/show_bug.cgi?id=248173 bug 248173] has been WONTFIX'd; hoping it can be revisited.)<br />
* Ability of search engine configuration saving to/restoring from a central server<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Search history<br />
* Browseable search history<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Search bar<br />
* Integrate browser search with desktop search<br />
* Multiple searchbars and/or multiple selectable engines for search<br />
* Default search engine assignment<br />
* One-click clear searchbar<br />
* Highlight terms in page from searchbar<br />
* Spotlight-like functionality<br />
* Search bar should allow the user to search for a string matching only a whole word.<br />
* Resizable search box<br />
* Ability to remove the magnifier-glass-icon from the searchbox<br />
* The box may extend as needed or be set to a new static size so users can see more of the searchbar content.<br />
* Keybindings: While the cursor is active and in the search bar <UP> moves the cursor to the start of the search string, and <DOWN> moves the cursor to the end.<br />
</td><td><br />
- [[Search for whole words only]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Find<br />
* Pre-populate ctrl-F with searchbox contents ([https://bugzilla.mozilla.org/show_bug.cgi?id=264123 Bug 264123])<br />
* Pre-populate ctrl-F with selected text ([https://bugzilla.mozilla.org/show_bug.cgi?id=250910 Bug 250910])<br />
* Tab-modal find bar<br />
* Find integration points for web applications<br />
* Add marker (+, -, <, etc) to scroll bar to emphasize location of found text<br />
* Improve highlighting behaviour<br />
** Allow user to configure highlight color<br />
** Highlight color is chosen to be in contrast to the page background<br />
* Add checkbox for "Match whole word"<br />
** If a user does a find for "plant", "Transplant" will not be considered a match<br />
* Give user ability to choose whether to display Find bar at the bottom (near the status bar) or at the top (above the page content). ([https://bugzilla.mozilla.org/show_bug.cgi?id=254687 Bug 254687])<br />
* Add a button next to the Find bar marked flash that flashes the highlighted text whcn clicked.<br />
* Give user ability to show all results for a search or find in a sidebar list.<br />
** Allow user to show/hide sidebar when performing find.<br />
** Allow the user to change the default behavior (show/hide sidebar) in options<br />
* Allow Regular Expressions<br />
* Ability to search on multiple tabs/windows<br />
* Ability to use one keyword for multiple search engines, each opening in their own tab (e.g. "CD Name" gives me 5 shops in 5 tabs)<br />
* Allow searches of bookmarks<br />
* Concordance style search results for whole search scope, sortable by relevance<br />
* Make it possible to search in the contents of all the pages you visited last x hours/days/months/years.<br />
* Allow Find in the content of textareas. (Anyone who tries to edit this very page will know why this is useful.)<br />
</td><td><br />
- [[Find_UI_enhancement|Visual feedback on text/link find]]<br /><br />
<br />
</td></tr><br />
<br />
<br />
<tr><td><br />
; Context Menu<br />
* Right mouse click onto link which points to a RSS feed shows "Add this link to LiveBookmarks"<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Search and replace for textareas and editable iframes<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Address bar ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<br />
<tr><td><br />
; Showing non-latin characters in address bar<br />
When nonlatin characters are used in address they are urlencoded. Many sites use them. Wikipedia is an example. But URL shown in an addressbar gets totally unreadable, like this one:<br />
http://uk.wikipedia.org/wiki/%D0%92%D1%96%D0%BA%D1%96%D0%BF%D0%B5%D0%B4%D1%96%D1%8F<br />
<br />
Such URL is not an easy thing write down on paper for example. It would be nice if such URLs were shown more like this (the non-latin part could be highlighted or formatted to prevent phishing):<br />
http://uk.wikipedia.org/wiki/Вікіпедія <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Auto-paging<br />
* When a numeric portion of the URL in the address bar is highlighted, allow it to be incremented/decremented using the mouse wheel, PgUp/PgDn, scroll arrows, or some other method. E.g., http://www.example.com/photo1.jpg; highlight '1' and scroll to view photo2.jpg, etc.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Search<br />
* When typing in the URL bar, have an option in the auto-complete menu to search for the entered text at the user's choice of Google, Yahoo, Ask.com, etc. Note: this feature already exists in the Mozilla SeaMonkey browser. If the code is compatible it could just be copied.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; RSS Feeds<br />
Right-clicking on the RSS Feed icon should give you the following tasks:<br />
* Copy RSS Feed URL<br />
* Open with default RSS application (like FeedDeamon etc.)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Autocomplete<br />
* middle of word<br />
* local filenames<br />
* user's bookmarks<br />
* using history frequency for relevance<br />
* Further refinement (and strengthening of match) could be made by offering a list of likely alternatives, selectable via arrow keys in a drop-down menu<br />
* using addresses for which a password is known, or are otherwise marked as 'trusted' (marked as allow script, allow cookie, allow xpi install, etc)<br />
* all of above make autocomplete still useful after clearing private data or migrating from IE<br />
</td><td><br />
- Similar to AppRocket on Windows and Quicksilver for OS X<br /><br />
- [[User talk:bur#Autocomplete_URL|remarks from bur]]<br /><br />
- [https://addons.mozilla.org/firefox/2300/ Autocomplete Manager] extension provides some of this<br />
</td></tr><br />
<br />
<tr><td><br />
; Remove single item from history/recent visit list<br />
* For when you entered a typo and got one of those squatter sites. Would be great to be able to remove that crappy address from the history so it doesn't keeps coming up.<br />
</td><td><br />
Can be done already: Control-Shift-Delete over a highlighted address bar history item will remove it.<br />
</td></tr><br />
<br />
<tr><td><br />
; take over Statusbar<br />
The only thing I really need the Statusbar for is to preview the target address of links before clicking them. Most of the time the statusbar is just taking away screen space without providing any useful information.<br />
<br><br />
If it would be possible to display the target location in the Address Bar (it really is the right part to show an address...), perhaps in another color (or perhaps only showing the changed part of the URL in a different color) then the statusbar would not be needed any more.<br />
</td><td><br />
[[User:Gerv/URL_mouseovers_in_address_bar|Terrible idea, says Gerv]]<br />
<br>[[User:Mgsloan/URL_Box|Could be workeable, says Mgsloan]]<br />
<br>[[User talk:JebusWankel#URL_tooltip|How about in a tooltip?]]<br />
</td></tr><br />
<tr><td><br />
; provide basic site navigation from address bar<br />
When I use news aggregation sites like slashdot and digg that provide deep<br />
links to stories on other sites, I invariably find myself wanting to look<br />
at the home page or perhaps even parent of the current URL.<br />
<br><br />
It would be a very useful feature to provide hotkeys that manipulate the<br />
URL in the addressbar. At least 2 operations spring to mind:<br />
* get server URL <br />
* get parent URL<br />
</td><td><br />
</td></tr><br />
<tr><td><br />
; Selective Autohide of Menus, Address, Bookmarks, Extensions<br />
I'd like to be able to set my menubars, bookmark bar, and (as an example) the Google toolbar to autohide. By this, I mean like the windows taskbar. This way I would be able to use that extra space for viewing, but wouldn't have to turn the bars on and off manually, or switch from the fullscreen mode.<br/><br />
<br/><br />
This idea could present a problem with being able to trigger the right bar for display, but I think if someone worked out the UI specifics for that, it would be a neat feature.<br />
</td><br />
<td>&nbsp;</td><br />
</tr><br />
<tr><td><br />
; Contextual menu<br />
On right click, adding also a "paste & go" item<br />
</td><td><br />
Like in Opera browser<br><br />
- Middle click already does this if you turn it on (and it's on by default on Linux)<br />
</td></tr><br />
<tr><td><br />
; Keybindings<br />
* Ability to customise what happens when ctrl-enter is pressed (command-enter for Macs) in the address bar and search bar. Some users want ctrl-enter to open a new tab. This will make the "ctrl == new tab" concept more pervasive. Currently, control-clicking on a link in a web page causes it to open a new tab. Also, most tabbed browsers open up a new tab upon ctrl-enter anyway, including older versions of Firefox itself. Whatever the default setting may be, it would be nice if the user could configure this. Also, some users want ctrl-enter behave just like plain enter. These users usually wanted to type ctr-v, enter, but accidentally held ctrl down too long, hence it gets registered ast ctrl-v, ctrl-enter.<br />
* Also, same thing goes for option-enter (alt-enter(?) on Windows). The "option == download url" concept has existed in older versions of Firefox as well as other tabbed browsers. While option-click still allows download of links, it's hard to remember what the keybinding is for downloading from the url bar anymore since there is no longer a consistent concept behind it and not compatible with other browsers.<br />
</td><br />
<td>&nbsp;</td><br />
</tr><br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Keybindings: When the cursor is active and in the address bar <UP> will move the cursor to the start of the address string, and <DOWN> will move the cursor to the end of the string.<br />
* Multi-line paste of URLs: When pasting a multi-line URL&#151;such as when one copies a large URL from a text-only shell-based e-mail program&#151;Firefox should automatically strip line breaks and elide what is pasted as a single line URL. <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
== Bookmarks ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Bookmark management<br />
* Bookmark thumbnails. Ability to view thumbnails of bookmarked pages. Size of thumbnails should be customizable. Thumbnails can be "live" updated.<br />
* Ability to associate automatically the favicon or manually any pictures to a bookmark.<br />
* integrated html presentation of the bookmarks using something like about:bookmarks for instance <br />
* Integration with address book. When contact has URL specified, it should be put into special bookmark folder automatically.<br />
* Give bookmark manager a decent database format, add tagging and tag cloud to interface, some way to support roaming, unlimited capacity. Boolean searching of any field. Let user define fields.<br />
* When clicking "Bookmarks" and all the bookmarks drop down (Bookmark This Page..., Bookmark All Tabs..., Manage Bookmarks...) should remain fixed and not scroll with the rest of the bookmarks.<br />
* Provide API for social bookmarking sites.<br />
* When using "Bookmark All Tabs..." it should let you choose an existing folder if you want instead of always creating a new one<br />
* Autodetect duplicates<br />
* Bookmark manager assistance/validation/cleanup<br />
* Frequently visited links automarking<br />
* Favicon management<br />
* Smart bookmark folders<br />
* Saved searches as smart bookmark folders<br />
* Category suggest for bookmarks via social web service<br />
* Virtual bookmark autofile view based upon most likely suggestions from a social web service<br />
* Remote bookmarks<br />
* Syncing bookmarks<br />
* Make it easier to directly add a keyword when saving bookmarks (i.e. you should see a keyword field when you press ctrl+D to bookmark a page)<br />
* Relevance based filtering<br />
* Leverage power of DB-based history/bookmarks<br />
* Auto-linking/smart tagging<br />
* Preserving DOM state<br />
* Import favorites from IE, Opera, AOL, Netscape, Avant, Konqueror...<br />
* Bayesian training/pruning<br />
* Option to open bookmarks in same tab, new tab, or new window<br />
* Allow user to search the bookmark list by fields other than Title, including URL.<br />
* Allow user to search bookmarked pages via a search engine, eg Google, so that the search performed will be for the bookmark('s/s') domain(s). <br />
* show/sort time and date of when bookmark was added<br />
* show/sort time and date of when bookmark was last-visited<br />
* toggle to indicate that site in bookmark no longer active (detect 404)<br />
* Bookmark filters - i.e. pages from domain X go in folder Y, pages with FOO in the title go in folder BAR<br />
* When deleting a bookmark from the bookmark menu (using the right click), bookmark menu should remain open, not close immediately.--[[User:CarlRogerson|CarlRogerson]] 00:44, 14 October 2006 (PDT)<br />
* Add option to rename bookmarks directly from the menu itself, not necessarily by going through the bookmark manager.--[[User:CarlRogerson|CarlRogerson]] 00:44, 14 October 2006 (PDT)<br />
* Ctrl+D should bookmark a page directly. The "Add Bookmark" dialogue/option box should be restricted to clicking on the Bookmarks menu and then choosing "Bookmark This Page" (this would imply that Ctrl+D and "Bookmark This Page" be separated).--[[User:CarlRogerson|CarlRogerson]] 00:44, 14 October 2006 (PDT)<br />
* Allow live bookmarks to be turned off and on.<br />
* A simple bookmark subscription function like was available on IE 4 where the browser scans for changes to bookmarked sites and presents a separate list marking ones have changed.<br />
* When creating a bookmark by drag and drop, firefox should pop a dialog so you can shorten most pages incredibly verbose titles to something you want to see in your bookmark list. <br />
* Timed bookmarks. The ability to set an experation on a bookmark that automatically deletes it. Many times I want to bookmark an article to read later but if I forget to read it, I don't want it cluttering up my bookmarks.<br />
* Display folder hierarchy when displaying results of bookmark search in sidebar and also include folder names in search.<br />
* Online bookmarks. Users can save bookmarks to bookmark services like google bookmark. There are firefox add-ons that do similar job, but they are not reliable and secure enough since user account information could be disclosed.<br />
* When searching for a bookmark in the Bookmarks sidebar it should be possible to also see the location (bookmark folder) of the bookmark, possibly the url, description, ... That would make it easier to remove duplicate bookmarks.<br />
* When opening a group of bookmarks in tabs, allow the group of bookmarks to be updated as a unit, replacing the old tab group with the existing set of visible tabs.<br />
</td><td><br />
- [[User:Dria/On_Tagging|On Tagging]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; In-page bookmarking<br />
* Easily-accessible, actual book-style bookmarks for long documents, where you can: <br />
** Preserve your position in the page<br />
** Move, rather than create new/delete old, the bookmark. This is useful when reading through e.g. the archives of an on-line comic, an e-book, or catching up after vacation on a blog like slashdot, <br />
* Allow the user to store the full text and images of bookmarked pages, just in case they go away (see discussion about archiving in "History" section)<br />
* Allow to set an expiration date for a bookmark, like [https://addons.mozilla.org/firefox/2886/ Tark] This is particularly useful for time constraint web pages such as auction items status, flight information, order status, track confimation, etc which are irrelevant after a short while.<br />
<br />
</td><td><br />
- [[User_talk:Topa#In-Page_Bookmarking | Provide in-page content-highlighting and saving page-state while bookmarking]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Bookmark toolbars<br />
* Revisit bookmark toolbars<br />
* Bookmark dock<br />
** A "bookmark dock" is conceptualized as a bookmark toolbar that allows a user to specify icons instead of text, and that could optionally be placed at the top, left, right, or bottom of the browser window. <br />
* Bookmark bar which allows to span multiple rows (to provide more one-click-to-go shortcuts)<br />
*Visually emphasize favorite bookmarks within a folder on the bookmark toolbar<br />
*Ease selection of favorite, most frequently visited bookmarks by displaying them in a larger font and/or with a larger icon than less regularly loaded bookmarks<br />
* Have the ability to use custom favicons/icons on bookmark folders added to the 'Bookmarks Toolbar Folder'instead of the default yellow folder.<br />
* As per [https://bugzilla.mozilla.org/show_bug.cgi?id=63295 bug 63295] (almost 6 years old), menus should auto-scroll if you hover above/below them.<br />
* Fix [https://bugzilla.mozilla.org/show_bug.cgi?id=186532 bug 186532]: wrong favicon displayed when page is switched while old page is loading.<br />
* When dragging a page (link) to a bookmark folder (to bookmark the page using drag-and-drop), if there are too many bookmarks in the folder to show them all at once, the list should scroll up/down when you hover over the little up/down arrows respectively. At the moment you have to first scroll up/down to the location in the list where you want to add the bookmark and then drag it to the folder.<br />
* If you delete a bookmark (by right-clicking the bookmark and clicking "Delete") it should be nice if the folder stayed opened so you can delete more bookmarks without having to navigate to the same folder each time. The same would be handy for opening a bookmark by right-clicking it and selecting "Open in New Tab" (and maybe for some of the other actions from the context menu too).<br />
* At the moment, if the name of the bookmark is too long to fit in the box, only a part of the name is shown (ending in "..."). It should be nice if more info about the bookmark would be displayed when hovering over the bookmark: its full name, maybe even the location (url of the page), its description, ... At the moment if two bookmarks have the same name or if the visible part of their names is the same there is no easy way to know the difference between them (apart from going to the bookmark manager or opening both links).<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Bookmarks in other parts of browser chrome<br />
* Let individual bookmarks live on the status and menu bars, and provide UI for putting them there (f.e. support for dragging and dropping bookmarks from the bookmarks sidebar and the bookmarks toolbar to the status and menu bars)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Bookmarks Timestamp and hide Inactive Bookmarks<br />
* Add a Date Timestamp to the properties of a bookmark<br />
* Keep track when last time was clicked on a bookmark<br />
* Add a option to hide Bookmarks that you haven't clicked on for more the 30, 60 or 120 days<br />
* Add a command to archive unused bookmarks into an "archived_bookmarks.html"<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Page change notification<br />
* Enable a system where the browser can check if a page has changed, without relying on Web feeds (any bookmark can be "live")<br />
</td><td><br />
The Suite used to have this; research why it was dropped before implementing it again<br />
</td></tr><br />
<br />
<tr><td><br />
; Erasing bookmark links<br />
* Find broken bookmark links: Automatically check for links that return 404s or other broken link behaviours.<br />
* Erasing links shouldn't erase it forever (aka "trash can", "recycle bin"). "Trash" could retain links for nn days or retain last nn deleted links.<br />
* Search and highlight duplicate entries. Then, user can erase manually those duplicate entries (...chosing were to place each duplicate entry or leaving them unchanged)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Bookmarks backend<br />
* Flexible bookmarks API<br />
* Smarter handling of bookmarking redirects<br />
* Ability to bookmark a POST response<br />
* Ability to bookmark a session (i.e. when bookmarking a single tab, the ability to bookmark the whole session in that tab rather than just the specific page; when bookmarking multiple tabs, the ability to bookmark the sessions in those tabs rather than just the specific pages)<br />
* Rich-text (i.e. HTML) microsummary bookmarks<br />
* Live titles extracted from feeds<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Bookmark Appearance<br />
* Let live bookmarks expand in a tool tip like way to view whole title<br />
* Let live bookmarks expand in a tool tip like way to view the associated text (usually the article's first paragraph) in the rss feed.<br />
* If text bookmarks are to stay, allow for the text size to be user-editable, so more bookmarks can fit onto the bookmarks toolbar (as an alternative to the icon idea above)<br />
* Display Separator text in Bookmark menu, if set.<br />
** Firefox allows setting a Name(via Property) for a Separator. Bookmarks in the menu does not display this text, but just Separator. <br />
** Display Text with Separator in Bookmark Menu, if set, like in Bookmark manager. e.g. "-- News ------" instead of "------------"<br />
** allow user to disable the text display, via a checkbox.<br />
** allow user to right-click on Separator in Bookmark menu, to set/update property value.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Dynamic Firefox Bookmark Menu<br />
* Allow "organizing bookmarks" functionality from firefox without opening Bookmarks Manager<br />
* Allow drag-and-drop to move bookmarks, folders, separators around in bookmarks menu<br />
* Allow right click to cut/copy/paste or delete bookmarks in bookmark menu<br />
* Allow right click to make new folder or separator<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Microsummaries<br />
* Allow customized update intervals, global enabling/disabling<br />
* Allow alerts for changes, open automatically in new window/tab, export to xml for RSS reader<br />
* Half-periodic: Start every day/weekday/week/month (now number of this) and check until microsummary changes all xx minutes<br />
</td><td><br />
[[Archaeopteryx/Customizable_Microsummaries|Customizable Microsummaries]]<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Completely rework bookmark manager<br />
* Toolbar enhancements<br />
** Allow user to move toolbars<br />
* Investigate the concept of bookmark data mining<br />
* Improve installation and management of microsummary generators<br />
* Allow firefox to create its own microsummaries ({{bug|356440}})<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
== History ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; History management<br />
* Ability to add annotations<br />
* Ability to automatically or manually tag history<br />
* Ability to automatically or manually archive contents in history in a variety of ways<br />
** Option to store all text from all pages (possibly excluding https and preset sites) ever visited -- this would let you revisit pages that disappeared off the internet, and also do very good search through history. At 100 pages per day, and a very generous 10k per page (storing text-only, not scripts and images), this would be about a third of a gig annually, so manageable storage requirements by modern standards.<br />
** Store the images and scripts too - I'm happy to spend $94 on a 320GB drive to dedicate to my Mozilla History - it'd save me accumulated days over a year of searching for stuff I've previously seen (coupled with the elsewhere mentioned full-text search). The above text-only suggestion could be a "Only Store Page Text" preference on a full history (and I'm sure would be useful for a subset of users). Anyway, this is going to require a retrieval engine faster than we currently have.<br />
* Ability not to add broken links (404) to the history<br />
* Ability to delete a page by rightclicking on the URL in the Location Bar dropdown<br />
* Ability to put a page on a blacklist (i.e. never show it in the history)<br />
* Maintain document state in history<br />
** You fill out a long form, click Submit, and an error occurs. You click Back and sometimes all of your form data is gone. I think it has to do with the page having a short TTL so it is re-requested from the server and re-rendered with a blank form.<br />
** Allow users to go back through history and see exactly what was entered in the forms on pages.<br />
** Never save password fields except through existing functionality<br />
** Allow user to enable/disable feature <br />
** Keep javascript engine state in memory for Ajax-heavy pages. Back button used in Ajax applications should take you back to the page as you last saw it, not as it was first requested from the server.<br />
</td><td><br />
- [[User:Dria/On_Tagging|On Tagging]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; History search<br />
* Full-text indexing of history<br />
* Search using metadata / full page text from cache<br />
</td><td><br />
<br />
[http://www.dustinkirk.com/search.png Design Composite -d-]<br />
</td></tr><br />
<br />
<tr><td><br />
; History browsing<br />
* Global history navigation & presentation<br />
* Session history navigation & presentation (handling iframes & modern DOM tricks)<br />
* Spatial history navigation. http://www.halfbakery.com/idea/Browser_20History_20Diagram (links down left hand side)<br />
* Full screen utilization for history browsing<br />
* Integrated Bookmarking<br />
* Integrated use of social bookmarking rankings to show page popularity<br />
* Sort history by time the page was closed, rather than opened. As such, if the browser crashes, everything that was open will automatically be at the top of the history. Likewise, if I close a page I opened last week, it will still be near the top of my history.<br />
* Right click context menu for new tab on list of previous sites from back button icon. Right click for new tab on home button icon. <br />
* History accessible via calendar views (day, week, month, year) and navigation-tree view<br />
</td><td><br />
<br />
[http://www.dustinkirk.com/last_visited.png Design Composite -d-]<br />
<br />
[http://weblogs.mozillazine.org/ben/archives/008250.html Thumbnail session history]<br /><br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Revisit location bar<br />
* Better management<br />
* Search enhancements<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">History and tabs</th></tr><br />
<tr><td><br />
Preserve history when ctrl-clicking to create a new tab. Essentially, let me ctrl-click to create a new tab, switch to that new tab, and then hit the 'back' button. <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
== Downloads ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Download control<br />
* Allow an option run a downloaded setup file (in the place of "open") instead of saving it, like in Internet Explorer<br />
* Interpret the meta tag "DownloadOptions" like Internet Explorer does<br />
* Ability to select a custom program ("other") to handle the download of an unknown file type (see [https://bugzilla.mozilla.org/show_bug.cgi?id=352142 bug 352142]<br />
* Ability to download all links<br />
* Ability to easily pass the url to third-party download manager to do the downloading instead of using firefox's built-in download manager<br />
* Ability to download selected links<br />
* Ability to create download queues so a user can add several links to a queue then fire off a batch download session<br />
* '''Fix download resume''' so it works reliably and as expected (for ex. by stopping download on Firefox exit, and restart it next time Firefox is launched, maybe with popup notice)<br />
* Integrate download status into the main browsing window<br />
** Display UI for each download somewhere in the window (in a sidebar, on a "downloads bar" either at the top or the bottom of the browsing window, etc.) so users can see the progress of their downloads without having to go to a different window<br />
** Alternately (or perhaps in conjunction), display a single UI element (like an icon or a throbber) that shows the status of the user's downloads (f.e. it might throb to indicate downloads in progress and display a number to indicate the number of downloads still in progress)<br />
* Schedule downloads<br />
* Ability to 'Add' file to be downloaded via URL<br />
* Make many connections (to different or same server)<br />
* p2p support (locating/participating)<br />
* Ability to restrict download bandwidth (aggregate or per stream)<br />
* Allow connection timeouts to pause the download instead of closing it. This will help people with slow or unreliable connections like [http://tor.eff.org tor] to continue downloading even if their connection fails on them.<br />
*Download Tagging. On a page where you wish to download from many links, it might be helpful to be able to to tag links for download. When you've finished tagging all the links you want, you could start a dedicated Download Manager session which would download all the links you've tagged to a specified folder, and even, perhaps, run certain actions on them like re-naming and unzipping, and other prcedures. Such features would put Firefox way ahead of the competition. Example: Scrolling through a site where you need to download a bunch of documents. You could download them normally, or you could tag them to be downloaded. Once you'd tagge everything you needed, you start the tagged Downloading Applet and it downloads all the files, one by one to the folder you specified, re-naming them according to a scheme you choose.This would be a very handy feature, especially for people who use image sites, or who need to download dependencies for open source projects. Initially, you could tag links from the same page, but eventually it might be feasible to keep a cross-site tag list. This would also be useful for people on dial up connections who need to download many large files, as it would allow them to tage the downloads during the day, and then download them at night, when they are less likely to need to use the phone.<br />
* Show the MD5 Checksum of each download after its finishied.<br />
* Be able to save the download history to a file.<br />
* On Unix, where just about all of your programs are in /usr/bin or /usr/local/bin it's really clumsy to have to use a file selector GUI to choose a program to open a download. There's no option to just type in the path, so I have to wait while a listing of my /usr/bin is populated and then find the program whose name I already know in an alphabetical list. Highly inefficient. There should be a text field as well as a "Browse..." button so I can just type in obvious names like /usr/bin/xpdf or /usr/bin/xv. Even better would be if it searched $PATH so I could just type "xpdf". And once you're in the browse dialog you should be able to type the program's name once you're in the right directory.<br />
* Fix webBrowserPersist to save @import-ed stylesheets and backgrounds referenced in stylesheets. See [https://addons.mozilla.org/firefox/2925/ Save Complete] for my work on an extension to fix this.<br />
*Simplify download pop-up. That thing hasn't been updated for ages. Maybe instead of radio buttons we have 3 buttons at the bottom: Save, Open, Cancel.<br />
*Add a persistent option that allows a file to be automatically renamed if exists instead of "Do you want to replace it?", is not nice to rename a pic and use the mouse with only one hand ;)<br />
<br />
In the Download window, there shouild be a button to reactivate the main ffox window. It nags me that i can close the main ffox window while a long download occurs, and then cannot reactivate it from the Download manager window<br />
<br />
Firefox 1.5.0.7 (tested on Ubuntu 6.06 LTS) has the following issues with the Download window. These should be fixed in Firefox 3:<br />
<br />
I recently started several larger downloads in Firefox and had to reboot my router while downloading.<br />
After this, I got to see several Firefox inadequacies or bugs, which I'll tell you about here:<br />
<br />
0:<br />
After the temporary network connectivity disruption, my downloads were left in limbo, with Firefox only giving me the option to Pause or Cancel; with the progress bar still showing, but not increasing, and the numbers (rate of transfer, ETA) not showing. At this point I could not get Firefox to resume the downloads, not even by clicking Pause and Resume.<br />
However, looking at the Desktop, I could see that the partial files where there. I then found that I could resume the downloads with wget -c <URL> from the command line. If I can resume from the command line, why can't I resume from Firefox?<br />
<br />
1: <br />
Upon now clicking Cancel in Firefox after the files were fully downloaded via wget, Firefox deleted the files. Also, where I resumed the download via wget and then clicked Cancel in Firefox, wget seemed to complete the download, but then threw an error message as the file was now nonexistant. I consider the fact that Firefox deleted the files upon clicking Cancel a bug. After all, after clicking Cancel, the download is still listed in Firefox' Download window. If anything, Firefox should delete the file upon clicking Remove. Which brings me to the next point.<br />
<br />
2:<br />
The user should be able to trigger the following three actions (and others, which are not the issue here) in the Firefox Download window: Cancel -- this should cancel a current download, but not remove the file. Remove -- this should remove the download item from the Download window list, but NOT remove the file. Remove from disk -- this should remove the item from the Download window list and delete the file from the hard drive. Alternatively, there could be just one Remove link that prompts the user whether they wish to remove the item listing only or also wish to delete the file; or this could be made a user preference.<br />
<br />
3:<br />
When clicking retry and a partially completed file of the same name already exists on the Desktop (e.g. because the user made a copy before clicking Cancel and then moved that copy back before clicking retry (cf. above broken Cancel behaviour), that file should be resumed. Instead Firefox currently attempts a new download from scratch and names it filename(2).ext. Firefox should resume the existing file, or give the user a choice.<br />
<br />
</td><td><br />
- [http://www.metalinker.org metalink (file distribution standard with mirrors and checksums)]<br />
<br />
- [[User_talk:Topa#Direct_Download_Button | Ability to Add file through URL]]<br />
</td></tr><br />
<br />
<tr><td><br />
; Download manager<br />
* Option to move the download manager into a tab instead of it's own window.<br />
* Improved file type handling - ie: always download specific filetypes to a set of default or user-specified folders (defaults: Audio, Video, Images, Zipped, Executable, etc.)<br />
* Speedy choice of downloading behaviour: sometimes I like to listen to an mp3 stream (clicking link), sometimes I want to download and save it without having to edit the settings (shift-clicking link, as it was in Mozilla)<br />
* Make the download manager take multiple download progress listeners so extensions can more easily present downloads in different ways<br />
* sort/display time and date (addtional column) of when files were downloaded<br />
* be able to sort/display by filetype (additional column) of downloaded files<br />
* Implement Categories, each category will have its own folder, so the downloads will be saved there.<br />
* Allow the user to select a Category for each download.<br />
* More control over clutter in the download history. Specifically, the abilities to select multiple completed downloads at once and remove them all with one button, remove all history items that point to files that are deleted or moved, or automatically remove history items older than X days, like with browsing history.<br />
* Show the Filesize on a finished Download e.g. Extras->Downloads->RMB->Properties->Filesize.<br />
* SeaMonkey's Downloadmanager is very clean and easy to use. It looks native, has no strange empty spaces like our current download manager and allows multiple selections and sorting and it has a detailed progress window. I would whish firefox had it, too...<br />
</td><td><br />
[http://home.arcor.de/jonha/mockup.png Seamonkey's Downloadmanager]<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Download history UI improvements<br />
* Content-disposition fixes<br />
* Option for turning computer off after downloads finish<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">Upload Improvements</th></tr><br />
<tr><td><br />
* Allow Upload Functionality Similar to the Download Manager (especially: show, how much has been uploaded already, not only a progress bar)<br />
* Should allow for Upload Resume<br />
* You should be able to Upload a Folder, rather than a single file at a time.<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Profiles ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Profile creation/switching<br />
* Improve profile/user management and switching<br />
** Make the profile manager accessible through the menu<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Profile privacy<br />
* Password-protected user profiles<br />
* Encryption of all stored data and profiles<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Profile data<br />
* Profile export/import<br />
* Remote profiles (remote profiles) hosted on a server and available to multiple installations. Being able to sync sessions would be fantastic too.<br />
* Full profile sync, including bookmarks, history, passwords, cookies, add-ons, preferences, etc.<br />
* Built-in AutoFill, which allows users to save their web passwords with Fiefox (like Avant Browser)<br />
* Encrypted during sync/transmission<br />
* Preference for where profile data is saved including settings, bookmarks, add-ons, passwords, etc.''<br />
</td><td><br />
RFC 2244 - Application Configuration Access Protocol<br />
</td></tr><br />
<br />
<tr><td><br />
; First run of new profile<br />
* Display EULA (required for distribution opportunities)<br />
** ''This is probably not required for distribution opportunities, and is indeed probably a bad idea (reduces usability, no benefit). This is only required for programs having license clauses stronger than copyright law (e.g. no reverse engineering), and not for GPL/MPL/NPL-style licenses.''<br />
** Firefox binaries are not under the GPL/MPL or NPL, they are under the (linked) EULA, which has clauses <b>unrelated</b> to copyright law (e.g. trademarks).<br />
*** Such things need no EULA. Trademarks, patents, and trade secrets are protected be default. No EULA is required to protect them. (What, you think GPL/MPL/NPL suddenly gives up your trademark rights??? Where is that?) It's like the lame statements that I can't export to North Korea: your EULA makes no difference, because I can't do that anyway.<br />
</td><td><br />
[[User:CBeard:Fx2_EULA_Requirements|End-User License Agreement (EULA) Requirements for Firefox 2]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Ability of corporatives integrations<br />
* Make ability to _FORCE_ profile to be stored in some location like \\server\user_home\firefox (for windows) and /mnt/nfs/users/firefox (linux)<br />
(existing abilities for profiles storage are not useful for making corporatives defaults settings for whole groups of users - so it is impossible to switch massively users to Firefox with corporative policy and same setting for all)<br />
<br><br />
* Make ability to make sets for multiple users at one editing of profile - changing their profiles<br />
<br><br />
* Ability to make MAIN profile.<br />
<br />
If firefox configured to use MAIN profile, then it gets policy sets from this profile (so, user can't make "not allowed" changes, until he switch off using of MAIN profile in browser (so, needs ability for administrators to block switch off MAIN profile) )<br />
Example: all default sets getting from MAIN profile and then firefox apply user settings, if this allowed by the MAIN profile for this group of sets)<br />
<br />
</td><td><br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Notification tools ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Page content notification<br />
* Some sort of unified system for informing users of all the various types of available content on a page, including Web feeds, Microformats, Microsummaries, and what-have-you. How could this information be best communicated to users through the browser? <br />
** Currently, when a Web feed is detected on a page, a Feed icon http://www.dria.org/images/onwebfeeds/feed-icon-16x16.png is displayed in the Location bar. If a page has multiple content types available, however (web feed, microformat(s), microsummary, etc), putting all those icons in the Location bar may not be feasible. What are the possible alternatives?<br />
**RSS in the URL bar, that's basically becoming a standard between all browsers so let's keep that. Clicking on it brings you to a built-in RSS reader (a la Safari). Left-hand side of the page will have the URL of the RSS feed so you can copy it into your favorite feed reader and all the other feed icons that are available (microformats and etc.) that you can cilck on. Clicking on one of those brings up the requested feed in the internal reader the same way. Also you should be able to select which you want via the View menu for quicker access, ex: View -> hCard, they will only show up under the view menu if available. All feeds and such should appear in the internal feed reader. I'll start a new section about it.<br />
* API and default UI for taking action on a notification (ie: subscribe to feed, import uFormat)<br />
** see this proposal for a [http://groups.google.com/group/mozilla.dev.apps.firefox/browse_frm/thread/16b9d61305fecba8 service for exposing metadata]<br />
* Implement a framework for pluggable back-ends for nsIAlertService, to use native desktop notification systems such as [http://www.galago-project.org/specs/notification/index.php Galago], or 3rd party tools such as [http://growl.info/ Growl], [http://www.fullphat.net/ Snarl].<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; New notification types<br />
* tab-modal alerts, more file formats, microformats, microsummaries<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Omnibus "Status" area<br />
* download status<br />
* popup/cookie/XPI blocker status<br />
* security/trustworthiness status<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Modified page warning<br />
* Warn User before closing page with modified form<br />
</td><td><br />
- [[Form Dirty Bit]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Backend changes<br />
* Get nsIAlertService working for Mac.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Move all MPL code to GPL <br />
* Improve error messages and the information they convey<br />
* Full language pass on error messages<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Printing ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Full page print preview/control<br />
* Better print preview<br />
* Print cropping<br />
* Custom margins (ideally adjustable in print preview)<br />
* User-controllable print scaling<br />
* Fully editable document within print preview utilizing simple text editor<br />
* Print documents last-page to first-page for printers that stack face up<br />
* Printing-related web standards support, e.g., page-break-after<br />
* Automatic resize-to-fit-on-paper (like febooti ieZoom or IE7 can do) and/or resize to x * y sheets of paper (like MS Excel)<br />
</td><td><br />
[http://wiki.mozilla.org/Firefox:Printing_and_Page_Setup Firefox:Printing_and_Page_Setup]<br> <br />
[https://addons.mozilla.org/firefox/282/ Print It! - MozAdd-ons]<br> <br />
[https://addons.mozilla.org/firefox/162/ Print - MozAdd-ons]<br><br />
[https://addons.mozilla.org/firefox/951/ Nuke Anything Enh]<br><br />
[https://addons.mozilla.org/firefox/10/ Adblock - MozAdd-ons]<br><br />
[http://karmatics.com/aardvark/ Aardvark Firefox Extension]<br><br />
[https://addons.mozilla.org/firefox/748/ Greasemonkey - MozAdd-ons]<br><br />
[http://www.w3.org/TR/REC-CSS2/page.html W3 - Paged Media]<br><br />
[http://www.febooti.com/products/iezoom/online-help/print-web-pages.html]<br><br />
</td></tr><br />
<br />
<tr><td><br />
; Selective printing<br />
* Print selected without requiring add-ons<br />
* "Print image" and "Print page" in context menu<br />
* Add Tab-related "Print Range" options to the Print Dialog, along the lines of "Print Active Tab" and "Print Selected Tabs". Requires ability to select multiple open tabs at once<br />
</td><td><br />
[http://wiki.mozilla.org/Firefox:Printing_and_Page_Setup Firefox:Printing_and_Page_Setup]<br><br />
[https://addons.mozilla.org/firefox/531/ Print Image - MozAdd-ons]<br />
</td></tr><br />
<br />
<br />
<tr><td><br />
; Settings management<br />
* Ability to set printing options (portrait/landscape, zoom, &c) so that they always return to the same desired settings each time the browser is closed (or each time it's started), rather than staying on the last-used setting.<br />
*Multiple saved settings<br />
* Option to overwrite CSS print styles with your own print-styles. Quick edit mode for headline, p, ul, li-Tags or choose from a list of preset skins.<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Backgrounds<br />
* Add an HTML DOM attribute that specifies whether a div's background image should be printed or not (since div background images are used frequently as "foreground images")<br />
* Add an option to include background images and/or background colors. Ultimately the print should look like a screenshot of the site.<br />
</td><td><br />
You can print backgrounds now; see File->Page Setup->Print Background.<br />
</td></tr><br />
<br />
<tr><td><br />
; Unix/Linux<br />
* Duplex printing (printing on both sides of the paper)<br />
* N-Up printing (multiple pages on the same sheet)<br />
* Get available paper sizes from the printing backend (e.g. CUPS)<br />
* Support PAPI<br />
* Autodetect printers when printing through lpr and lp<br />
</td><td><br />
[http://wiki.mozilla.org/Firefox:Printing_and_Page_Setup Firefox:Printing_and_Page_Setup]<br><br />
[http://www.linuxprinting.org/ LinuxPrinting.org]<br><br />
[http://www.freestandards.org/en/OpenPrinting/PAPI OpenPrinting PAPI]<br><br />
[http://www.mozilla.org/projects/xprint/ Xprint in Mozilla]<br><br />
[http://kb.mozillazine.org/PostScript_Module PostScript Module - MZKB]<br><br />
[http://kb.mozillazine.org/Dev_:_Plugins_:_Printing_:_Unix Plugin Printing on Unix - MZKB]<br><br />
{{bug|135695}} (lpr printer detection)<br><br />
{{bug|306122}} (lp printer detection)<br><br />
</td></tr><br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve Print UI and handling<br />
* Improve FLASH printing<br />
</td><td><br />
[http://wiki.mozilla.org/Firefox:Printing_and_Page_Setup Firefox:Printing_and_Page_Setup]<br><br />
[http://wiki.mozilla.org/Firefox:Printing_and_Page_Setup#Printing_UI Page Setup & Printing UI]<br><br />
</td></tr><br />
</table><br />
<br />
== Installer ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; MSI Installer<br />
* MSI installation package for corporate deployment<br />
</td><td><br />
[http://www.frontmotion.com/Firefox/ Frontmotion MSI packages]<br />
</td></tr><br />
<br />
<tr><td><br />
; Extensions<br />
* Offer to install extension packs while installing<br />
* Extension package manager (similar in concept to an Apt front end, searchable)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Internationalization<br />
* Improve internationalization support in Installer<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Editions<br />
* Create several Editions for example standard edition, web developer edition, low memory edition or even google edition<br />
* A non-install edition, which don't saves datas. That could be very useful in puplic places, where you don't have special user-right and no good browser. Or a variant that could be run from an usb stick, that you could use your personalised browser anywhere.<br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a <br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Software update ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Automatic updates<br />
* For those who opt out of auto-update, provide a "remind me later" feature<br />
* Allow users to select type of updates they want (security? feature?)<br />
* Allow users to revert to previous version<br />
* Better background downloading support (i.e. background downloads using idle bandwidth, easy on Windows with native pieces, harder elsewhere afaik)<br />
* Enable users to "bundle" extensions, bookmarks and other profile preferences into a package which can be deployed on multiple systems easily.<br />
* Make automatic updates work on Windows without need for logging in as administrator &mdash; automatic updates service or scheduler task.<br />
* Make the automatic updates feature optional at build time. Some users would prefer their system's package manager to handle software updates.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Manual updates<br />
* Regarding the "Help" -> "Check for updates" function: When no updates are available, Firefox tells the user that it may check periodically for new updates without giving any clues or functions on how the user can tune this functionality. I suggest to implement a UI regarding the setup of the update policy here so that the user right there in the dialogue box can tune the update policy without needing to open the Options dialogue box.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve UE for automatic updates so it is less instrusive/shocking<br />
* Improve UI for updates so it's easier to understand what you will be getting<br />
* Clean up major/incompat update UI<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Default browser UI ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
;Text link recognition<br />
* Double click on a text link (like: www.somesite.com/here.html or http://www.somesite.com/here.html) recognizes it and opens it like a regular link, a very simple feature.<br />
</td><td><br />
<br />
</td></tr><br />
<br />
<tr><td><br />
;Synesthetic Surfing<br />
*Synesthesia, or the cross-linking of senses, has been long known to be a powerful nmonic for anyone with the ability to tap it. Richard Feynman often thought of complex physics equations in colors, and these powerful associations can be used to assist in surfing the web. I am a synesthetic of a few different flavors, one of which is letter/number to color associations. Whole words have color averages usually dominated by the first letter. The word "Web" for example, is orange with some blue hues at the end. I found a plug-in for Firefox that colored your tabs, but it was random. I would like to see user-picked colors for specific domains. For example, www.google.com would be a yellowish-orange color on the tab. I would select the specific hue I wanted and the tab would be colored so. That way, if I have a many tabs open at the same time, I will know which one is google at a glance. The ability to associate tonal sounds with the tabs as a mouse-over function or click function would also be very helpful. Those who are more inclined to audio cues would benifit from this immensely! I love designing GUIs, so don't worry, if you don't code this, I will ;) -NeuralZen <br />
<br />
P.S.<br />
Check out wikipedia's write up on synesthesia for more info...<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Browser Loading Time<br />
* Make the browser open faster; that is the number one reason that I have heard for people not using Firefox or switching from Firefox<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Alternate UI modes<br />
* Togglable kiosk mode<br />
* More efficient layout for widescreen laptops<br />
* Minimal UI mode<br />
** Show and hide navigation/bookmark/menu bar via a right-click menu everywhere<br />
* (optional) full screen (or "resize to fit all content" ...a la Mac OS X) mode without toolbars, icons, navigation bar, etc <br />
</td><td><br />
- [[User talk:bur#Show_.26_Hide_bars|details & discussion]]<br />
</td></tr><br />
<br />
<tr><td><br />
; Choice of UI rendering mode<br />
* choice between displaying page when fully rendered (mozilla way) or display as it renders (Firefox way).<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Rationalize and reorganize browser and context menus<br />
* Remove some menu items<br />
* Move other menu items<br />
</td><td><br />
[[User talk:Steve_England|Reasoning and Arguments]]<br />
</td></tr><br />
<br />
<tr><td><br />
; Context Menu<br />
* Show an ''open url in new tab'' or ''open url'' option in the context menu when the user right-clicks on a plaintext url (text that is recognizably a url, but has no <nowiki><a></nowiki> tags).<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Display keyboard shortcuts when hovering over objects<br />
* When hovering over an object in the navigation toolbar the respective keyboard shortcut should be displayed as a tool tip.<br />
It could considerably improve the usage of keyboard shortcuts for new Firefox users that are not used to work with keyboard shortcuts (like old people).<br />
This should be a default-on feature with the option to turn off in Options -> Advanced -> General -> Accessibility<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Reconsider the idea of Home Page<br />
Home Page and Home button have been with us since forever. However, I have a strong feeling they are no longer relevant and no one uses them as they did in the old times of "web portals".<br />
I propose to create a task-oriented "start" pane - basically a question of "what do you want to do". It should have:<br />
* urlbar: "I want to go to that page".<br />
* history: "I want to go to the page I've been to recently"<br />
* web search: "I want to search"<br />
* a button that restores session from just-closed window: "I want to continue"<br />
* bookmarks and feeds, or otherwise Places<br />
<br />
I consider Thunderbird's start pane to be a good example of what I'm talking about.<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; OS X widgets<br />
Use OS X's provided widget set, especially for textarea, button, radio, checkbox and select elements. Native widgets feature spell check among other niceties. This would go a long way towards making Firefox feel more like a "real" OS X application. The current UI does not follow many of the common idioms on the Mac which causes confusion when switching between it and other Apple apps. This could greatly impact adoption on OS X, particularly among less savvy users who don't understand why it's different.<br />
</td><td><br />
* [http://www.apple.com/macosx/features/safari/ Apple Mac OS X Safari Browser]<br />
* [http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGIntro/chapter_1_section_1.html Apple Human Interface Guidelines]<br />
* [http://forums.mozillazine.org/viewtopic.php?t=363099 Hacking Aqua Widgets into Firefox]<br />
</td></tr><br />
<br />
<tr><td><br />
; Page Zoom<br />
*Instead of only increasing and decreasing the current page's font size, allow for the entire page to be zoomed in/out, like Opera. Make the zoom keys customizable.<br />
**Also, like Opera, make sure that all elements zoom, such as Flash.<br />
</td><td></td></tr><br />
<br />
<tr><td><br />
; Better autocomplete in form fields<br />
* Autocomplete list should be editable (like cookie-list) or erasable otherwise it will contain a lot of trash after some time and it is also a mild security risk because sometimes people demonstrate their actions and it is not nice previous entries pop-up; perhaps some toggle can help to disable/enable the feature<br />
* Also, Emacs-style autocomplete ("dynamic expansion") of words will increase input speed dramatically in input and textarea fields<br />
* It could go even further by having abbrev-list in a meta rel fashion (the same fashion as favicon is specifyed or other related documents)<br />
<br />
If implemented, this proposal can boost productivity for web-application users with technically simple (and known from many text-processors/editors) UI add-on<br />
<br />
</td><td><br />
* [http://www.cs.cmu.edu/cgi-bin/info2www?(emacs)Dynamic%20Abbrevs Emacs Dynamic Abbrevs]<br />
* [http://wiki.mozilla.org/DiscussionForBetterAutocompletesInForms Discussion]<br />
</td></tr><br />
<tr><td><br />
; Avoid caching sensitive data for autocomplete<br />
Use heuristics to try and avoid caching sensitive data for autocompletion. For example, if something looks like a credit card number or social security number, don't cache it. It's very disconcerting to start typing in your social security number on your bank's Web site, and realize your browser already knows it...<br />
</td><br />
<td></td><br />
</tr><br />
<tr><td><br />
; Editing HTML of opened page<br />
* Be able to edit the HTML source of a web page that is open and then save the changed version to the local hard disc.<br />
* Currently "View > Page Source" does not allow editing for a web based page. Make this editable and then give the ability to save the entire page with images etc, using the modified source to the local hard disc.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<br />
<tr><td><br />
; Color of visited links depending on time of last visit<br />
* Color of visited links should range from VLINK to LINK according to time passed.<br />
**I'd like that the color of visited links could range from the the color defined for visited links to the color of _un_visited links in proportion to the time passed since last visit.<br />
**This feature was present in early Mosaic, but I haven't seen it again in any browser.<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=211531 Bug 211531]<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Revisit default tab strip<br />
* Re-evaluate toolbar buttons<br />
* Re-evaluate status bar<br />
* Re-evaluate menus and context menus<br />
* Ensure shortcut consistency<br />
* Remove Truncation of Title and Alt Tags<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<br />
</table><br />
<br />
== Security ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Surf by IP protection<br />
* Two new security options, which should be checked by default...<br />
[ ] Disallow visiting sites by IP address (IP anywhere in the URL)<br><br />
[ ] Allow local LAN IPs<br><br />
(192.168.x, etc. for getting to your home router, access-point configuration pages, or some corporate intranets) By using these security options, you will quickly kill off all the "lasy phishers" who don't setup or register a domain-name for thier false site.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Security preferences<br />
* Automated user preference auditing with user notification of potentially problematic preference settings.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Phishing protection<br />
* Make it easier to report phishing sites<br />
* Implement a phishing filter that learns automatically<br />
** Consider intergration with something like PhishTank [http://phishtank.com]<br />
* Multi-provider support for local list checking (depending upon provider demand)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Safer Browsing<br />
* Like anti-phishing, but with a list of sites that are known or suspected of being a source of malware (virii, spyware, etc)<br />
</td><td><br />
See [https://bugzilla.mozilla.org/show_bug.cgi?id=347849 bug 347849]<br />
</td></tr><br />
<br />
<tr><td><br />
; Script execution<br />
* Integrate script execution whitelisting<br />
* Allow cross-site scripting between whitelisted sites (for mashups)<br />
</td><td><br />
[http://noscript.net NoScript]<br />
</td></tr><br />
<br />
<tr><td><br />
; Pop-ups<br />
* Implement one-click viewing of blocked pop-ups<br />
* Make printing popup windows possible<br />
* Implement a way to block every pop-up window, regardless of the way it was requested.<br />
</td><td><br />
- [[User talk:ThomasWaldmann|More on printing pop-ups]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Restricted Javascript<br />
* Prevent window resizing<br />
* Prevent hiding toolbar/controls<br />
* Prevent capturing mouse events (overriding clicks, and obnoxious mouse-tracking scripts)<br />
* Prevent floaters (or have some way to hide these layers)<br />
* Prevent automatic form submission (or "Did you really want to submit this?")<br />
* Trace window/panel with the history of form submissions and visited URLs, with the option of ask before submit everytime.<br />
* Provide a way to prevent a browser window from being locked up by a Javascript loop which repeatedly produces a Javascript dialog, e.g. a "Stop script" button in Javascript dialogs.<br />
* Per-site javascript settings, i.e. allow users to choose to enable "move/resize window", "replace context menu" etc, on a per-site basis, instead of just a single global option.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Cookies<br />
* Add cookie whitelist funcitonality<br />
* One-click block/allow cookies<sup>1</sup><br />
* Allow cookies from sites (on request) remain persistant even after the browser has been restarted<br />
* Allow session cookies per window/tab so that multiple logins can be had to services such as gmail/hotmail simultaneously.<sup>2</sup><br />
* "Supercookies"<br />
* Never accept cookies associated with invisuble images: single, pixel GIFs and so forth<br />
* Extensions like "Extended Cookie Manager" allow you to enable or disable cookies for the current site. However, it is common that sites use redirection, and a different site for actual authentication. Something like login.google.com when browsing www.google.com. So, simple "enable cookies for this site" features are not effective.<br />
* The "ask every time" cookie dialog box should have another checkbox: "Don't ask again". This is so you can deny a cookie, and not have many more dialogs pop up to deny. This would complement a "One-click block/allow cookies" feature.<br />
* More granular cookie controls - allowing regex definitions of what cookies should be accepted or declined. Not just based on the source site but also on the contents of the cookie. E.g. I don't care what site it is from, I never want to accept a cookie that contains the string AD_ID, even if I accept other cookies from a site.<br />
* Have an option to automatically allow session cookies, even if I asked to ask every time, like in Internet Explorer. The main use of asking every time is to be able to allow permanent cookies only for those sites you trust, and to make every one else to last only for the session. But session cookies will do it anyway, so it's a waste of time having to opt in each one.<br />
<br />
</td><td><br />
<sup>1</sup> Like "CookieCuller"<br /><br />
<sup>2</sup> Like "CookiePie"<br /><br />
</td></tr><br />
<tr><td><br />
; Exploit Mitigation<br />
* Please consider splitting all page rendering code into a seperate process running with reduced permissions, either using ACL on Windows, or as a seperate low-privilege user on Unix-style systems. Use IPC mechanisms to handle network interaction and requests to save files in non-sandboxed directories. Assume that a network deliverable attack will exist, please ensure that the worse that happens is that the rendering engine must be restarted.<br />
**To secure a process on Linux, simply write to the /proc/self/seccomp file. The process will then only be able to communicate via existing file descriptors (be sure to close the X11 one) and existing shared memory regions. Only about four system calls are allowed for a process in secure mode: read, write, exit, and signal handler return.<br />
**To secure a process on a domain/type enforcement system like SE Linux, use a separate executable for handling untrusted content. A separate executable is required so that the security system can wall it off, permitting only communication with the other components of the browser. (components being: separate UI, network, config file access, cookie access, cache access, other disk access)<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Extension installation<br />
* One-click to permanently add site to whitelist<br />
* One-click to temporarily add site to whitelist for this session<br />
* Third-party signing and authentication by Mozilla<br />
</td><td><br />
[[Firefox:1.5_Extension_and_Plugin_Blacklisting|Extension Blacklisting UI Spec]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Virus/Malware protection<br />
* Intergrate a sandboxing feature automatically. (Like Sandboxie -http://www.sandboxie.com/)<br />
* Integrate virus scanning and malware protection for retrieved content/files<br />
* Integrated support for 3rd party Anti-virus scanners<br />
* Firefox to run in a "Protected mode" like IE7/Vista (see the Sandboxing above)<br />
** See <b>Exploit Mitigation</b> comment above.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Spoofing<br />
* Employ some shared-secret anti-spoofing techniques<sup>1</sup><br />
* Prevent content and scripts from being able to spoof or mimic protected chrome<br />
* SSL auth required for send password<br />
** This is an optional, but strongly recommended feature suggested during install<br />
** Sending password with FORM.send or Javascript.Send check if the page is SSL encrypted and will display an error message if there's no valid SSL certificate.<br />
** Do not allow adding "*" to FORM.edit field from Javascript (avoid spoof)<br />
** This way a user will get warning when tries to log in to an unsafe service, like phishing sites. All sites with authentication should have valid SSL certificate or should be added to "safe to login" list.<sup>2</sup><br />
* Add some indication of which site produced a Javascript dialog, to prevent dialogs appearing to come from another site in a tabbed session.<br />
* Check digital signature of a web page based on some extended DNS records. That way if a site is defaced, it will be obvious. Note that SSL does not guard against defacement, but this will.<br />
</td><td><br />
<sup>1</sup> [http://passpet.org PassPet]<br /><br />
<sup>2</sup> [[User_talk:Csoma|details &amp; discussion]]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; New technology support<br />
* Extended Validation Certificate support<br />
* Integrated PGP/GPG to sign/encrypt/authenticate text (eg Web Mail)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; HTTP authentication improvements<br />
* Support for logging out of basic or digest HTTP authentication (RFC 2617 style)<br />
* Implement a somewhat secure HTTP shared-secret authentication scheme based on SRP. The RFC2617 schemes are both very vulnerable to phishing.<br />
* Show content of 401-unauthorized pages, and add widgets to login via forms instead of modal dialogs<br />
</td><td><br />
See [https://bugzilla.mozilla.org/show_bug.cgi?id=355319 bug 355319]<br />
</td></tr><br />
<br />
<tr><td><br />
; Keychain support for MAC OS X / KDE / Gnome<br />
* Save passwords in the OS-level Keychain on OS X, so that passwords can be shared between Safari / FIrefox / Camino / etc.<br />
* Ability to switch to external password manager like kwallet etc. and to disable firefox standard password manager<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve user notification of insecure browsing situations<br />
** Rather than pop up annoying dialogs when a site has a bad security certificate, simply perform the encryption without showing the lock icon. (make the https site happy without bothering or misleading the user)<br />
* Improve handling of digital certificates<br />
* Improve phishing protection UI<br />
* Improve overall security UI<br />
* Improve pop-up blocking UI and options<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
== Privacy ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Eliminate image based user tracking.<br />
* Do not load *any* invisible images. This includes single pixel and smaller pictures. It also includes images that are the same color as the background. Those can't be detected preload, but perhaps cookies could be refused to them. <br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Public Terminal Version.<br />
* The person installing the firefox can enter a password protected option which automatically converts the browser into a public terminal version where no passwords are stored and everything is cleared on exit.<br />
<br />
* The only way to override is when the user specifies a directory to store all ALL collected data (see suggested feature below) where the specified directory is on removable media. This setting will expire when the browser is closed or after 1 hour of use.<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; User specified directory to store ALL collected data.<br />
* Have one directory, where all history, cookies, bookmarks, and any other data that could be potentially used maliciously to be stored. And give the user the option of putting it elsewhere. Be it on a dongle, or an encrypted area/partition (like using TrueCrypt)<br />
</td><td><br />
</td></tr><br />
<tr><td><br />
<br />
; Private browsing<br />
* Implement a "private browsing" mode that prevents collection and recording of data. When privacy mode turned off previous history should be preserved.<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Privacy preferences<br />
* Add the option to suppress referrer information while browsing<br />
* Import/export passwords and/or privacy settings<br />
</td><td><br />
<sup>1</sup> {{bug|285790}} already exists for form history<br />
</td></tr><br />
<br />
<tr><td><br />
; Password management<br />
* Improve Master Password entry when viewing saved passwords.<br />
** Redundant master password entry fields: If the user has opted to set a master password for their browser's stored passwords, they have to enter it twice to actually view and show the passwords (once to View Saved Passwords, and then AGAIN to actually Show Passwords of those accounts). This redundancy is unnecessary.<br />
** on the Password Manager window, the Remove and Remove All buttons are right next to each other, however the Remove All button does NOT have a dialog that asks you if you are sure you want to remove all saved passwords. An accidental click on the Remove All button instantly deletes all of the user's saved accounts and passwords.<br />
* Improve password management - allowing multiple passwords (like opera, also see [http://www.melez.com/mykzilla/2006/02/improving-firefox-password-saving.html Myk's post])<br />
* Ability to edit saved usernames and their respective passwords via the Privacy > Passwords > View Saved Passwords dialog<br />
* Search Saved Passwords - Add search feature to the saved passwords list. <br />
** Enable users to search by specific field (URL, username, or password) or perform a general search.<br />
* Add date added/modified field to records in the password list<br />
* Don't just save passwords, ''create'' them like [http://labs.zarate.org/passwd/ Chris Zarate's Password Generator bookmarklet]. It generates a hex-encoded MD5 hash of your master password and the domain name of the website you are visiting, and shortens it to the desired length. This allows users to remember just one master password, but use a unique strong password for every website (so your blackhat.com password is not the same as your bank.com password).<br />
* Add preference to prompt user to update stored password after the next page loads when the user submits a password that does not match the password stored for the form/username combo. This would greatly smooth out the currently clunky common task of updating stored passwords without having to dig through the preferences.<br />
* Wait until the password has been accepted before offering to save it.<br />
* Modeless handling of new passwords. To avoid the intrusive dialog box popping up to ask users if they want to save passwords, you could signal this on the status bar or with a modeless pop-over, like Windows uses for warning about unused desktop icons. That way, it's a lot easier to just ignore this feature if you're in a hurry, or using someone else's computer, where you typically just want to get wherever you're going.<br />
* Instead of "Never for this site" blocking of password storage, have a "never for this password" feature. For example, I might have a general use email account, and a super-secret private email account, both on the same webmail system. I'd like the regular account password remembered, but not the super-secret one. To implement this, take the [domain+username+password+salt] as a long string and SHA1 hash it, and store the hash - and nothing else. That can be safely (verify this carefully!) stored in user preferences without revealing anything, and still block rememberence of that password.<br />
* Instead of requiring another click on every form submit "Do you want to remember...." have a button which gives the option to remember the password, and otherwise do not offer to remember passwords.<br />
* Just make password management EXACTLY like Opera. People have already mentioned support for multiple users, but what about automatically logging in with one click as well like Opera's wand? And make it work on ANY website like Opera (ignore the code that says "don't even ask to remember this password", people don't like entering their password every time they check their bank balance because their bank set it up that way.. that's what "never for this site" is for).<br />
<br><br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Secure Storage and Clearing of Private Data<br />
* Optional password Protection for ''all'' Private Data including cookies, browsing and form history, cache, etc. using strong cryptography.<br />
** could use same master password as password manager<br />
* Integrate a feature to securely "wipe" saved browser information using various data overwriting algorithms such as Peter Gutmann's 35-pass wipe and U.S. DoD 7-pass specification 5220.22-M.<br />
**This is obsolete. Useful levels of protection are:<br />
**#delete the file -- protects against non-admin users<br />
**#zero the file -- protects against nearly everyone outside of foreign intelligence agencies<br />
**#melt, dissolve, or powderize the hardware -- protects against everyone<br />
**Multiple overwrite is not stronger than merely zeroing the file. It is an attempt to beat the rare case of somebody who can examine the disk surface, but it fails because modern disks will commonly write to different locations. Disks do sector/track substitution and they have write heads that wander a bit.<br />
<br><br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Password Protect the Browser<br />
* Require a password to launch a new instance of the browser in order to allow users to allow the browser to save passwords for websites, but still protect them from guest users of the PC.<br />
* Detect if Master Password required dialog box is open. If it is open, and a link is clicked instead of opening another instance (which opens another Master Password dialog box) focus the existing dialog box and open the page in the original window instead of a new window.<br />
** Only open one Master Password dialog box when there are two extensions that auto-login to accounts upon launch instead of two separate Master Password boxes for the same window.<br />
<br><br />
</td><td><br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve overall Privacy UI<br />
* Improve "clear private data" UI and options<br />
* Fix this bug in the password manager: [https://bugzilla.mozilla.org/show_bug.cgi?id=112260 Password manager silently overwrites form-supplied values]<br />
</td><td><br />
<br />
N/A<br />
</td></tr><br />
<tr><td><br />
;The password dialog "Do you want Firefox to remember this password?" <br />
* This Prevents the "enter password" form action page from loading so that the user must answer the question *before* he/she actually knows whether the username/password is correct. Ideally the password dialog would not block the page from loading and close automatically when the user leaves the "password accepted" page.<br />
* Add a "Never Remember Passwords" button. Novice users may never realize this feature can be disabled in the Privacy section of the Options menu, and may become annoyed that they can never "really turn it off."<br />
</td></tr><br />
<tr><td><br />
;Option to clear Cache exit on window close/program exit<br />
* This option is a blatent ripoff of IE with its Empty Temporary Internet Files on Exit. <br />
* This option would be seperate from the Clear Private Data as to not interfere with the settings there. <br />
** This will allow the user to clear the Cache on exit but not other items leaving them availible for execution when in the Clear Private Data option is invoked.<br />
* This has been requested for some time and some work has been done on it.<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=17403 BugZilla for Auto Cache Clear]<br><br />
[https://bugzilla.mozilla.org/attachment.cgi?id=157797 Potential Patch previously submitted for feature]<br />
</td></tr><br />
<tr><td><br />
;Enhanced Certificate Management<br />
* This should enable users to preselect certificates for certficate enabled sites (if they have more than one certificate available for the site)<br />
* One-click editing and temporary dis- / enabling certificates via a better certificate-gui <br />
</td></tr><br />
<tr><td><br />
;Green Internet Zone<br />
* Analog to the Zones in the Internet Explore, Firefox should provide a "green zone". This "green zone" should only work over HTTPS and it should come without any trusted sites (no root ca at all). If Firefox is showing a page in the "green zone" he should paint the Adress bar green (or something similar).<br />
* A user should manually add .cer Files of sites he trusts. Obtaining a .cer File should be the responsibility of a user.<br />
* Purpose of such a zone: A user can always see if he does his homebanking (or other critical things) over exactly that site he wants to.<br />
* This feature would be nice as well, if it comes with mltiple empty zones, so a user could use it for different sites. <br />
</td></tr><br />
</table><br />
<br />
== Identity ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Identity management<br />
* Add identity management<br />
* Ability to fill in common form fields using 1..n identities<br />
* Enable some sort of single sign-on capability<br />
*: ''Use RDF and/or a [http://microformats.org/ Microformat] to define Fields for Username, Password, E-Mail, and the like. Filling a form tagged with a microformat can then be archived ie. by Drag&Drop a kind of vcards from a specific sidebar.''<br />
*Make it possible to hash the Password using the Domainname by default.<br />
</td><td><br />
[http://www.identity20.com/media/OSCON2005/ Identity 2.0 at OSCON]<br /><br />
</td></tr><br />
<br />
<tr><td><br />
; New technology support<br />
* Support for Microsoft's CardSpace (nee: InfoCard) protocol<br />
* Support for SXIP protocol<br />
* Support for [http://openid.net/ OpenID]<br />
** ''What does this mean? OpenID is something supported by websites...''<br />
** OpenID's are consumed by websites but users get their OpenID's from identity providers. This is where their personal information and list of trusted sites is kept. As OpenID becomes more prevalent, phishing for the user's password to their identity provider becomes more compelling because you could get access to all of the sites a user goes to. Having support for OpenID baked into Firefox would allow users to fight phishing by giving them the ability to specify who their identity provider is and then warn them with blinking lights and uber pop-ups when some site tries to phish them.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Feeds Handling ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Web feeds<br />
* Mark entries as read<br />
* Notification of feed update<br />
* Set refresh rates per feed<br />
* Set expiry options per feed<br />
* Set notification options per feed<br />
* Show # unread items in a feed<br />
* Enhanced Feed Preview rendering<br />
* Build Home Page from subscribed feeds<br />
* Show feed entry summaries & content<br />
* Remember 1..n system feed readers<br />
* Enable a "River of News" feed viewing option<br />
* The Sage extension is a good model for updated RSS handling<br />
* Add Live Boomark directly from feed link<br />
<br />
There should be 2 parts to the internal RSS reader: a sidebar on the left and the main content area.<br /><br />
Sidebar:<br />
*Include the URL of the feed so it can be copied easily to the user's favorite RSS reader (the URL bar should also display the feed URL)<br />
*Buttons for other available feeds such as an hCard feed, OPML feed, or whatever<br />
*Calendar so you can select a day to see all items on that day<br />
*Some way of selecting a date range that's not a blatant rip-off of Safari?<br />
Content:<br />
*Completely extendable: anyone can add their own way of rendering XML as simply as adding a search engine to the search box. That way Firefox can easily keep up with newer Microformats and such.<br />
*Themeable<br />
*List view and extended view, similar to Google Reader<br />
<br />
</td><td><br />
- [http://wiki.mozilla.org/User:Dria/On_Web_Feeds On Web Feeds]<br /><br />
- [http://www.techcrunch.com/2006/10/09/ten-things-i-wish-ie-7-was-about-to-deliver/ TechCrunch article about IE7]<br /><br />
- [http://reader.google.com Google Reader]<br /><br />
</td></tr><br />
<br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
<br />
== Microformat Handling ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Microformat Detection<br />
* Detect micro-formated content or implicit/latent micro-formats such as FedEx tracking numbers, AIM screen names, etc.<br />
* The detectors themselves could be plug-able, so that users may replace the default detectors or add new detectors for specific content types. Thus, research, innovation, and communities could form around creating the highest quality and most accurate content detectors.<br />
</td><br />
<td></td><br />
</tr><br />
<br />
<tr><td><br />
; Microformat Actions<br />
* Allow users to easily take action on detected data elements. For example, contextual menu actions for hCards could include "add to address book," "email contact," "dial number with Skype," etc. Additionally, services such as LinkedIn or Plaxo could develop their own contextual menu add-ons to allow users to do things like add detected hCards to their accounts.<br />
* Microformat actions could be plug-able so that users may replace the default actions or add new actions for specific content types. An open and extensible system would allow users to associate content types to their choice of desktop applications or online services, similar to how Firefox 2 handles feeds.<br />
</td><br />
<td></td><br />
</tr><br />
<br />
<tr><td><br />
; Microformat Collection and Storage<br />
* Once data elements are detected, they could then be normalized to a universal schema and added to a local data store.<br />
* User preferences or rules engines for web content could control how information is collected and saved. For example, a rule could allow a user to do things like save detected hCards found within a particular domain, etc. Distinctions would need to be made between data that is cached or explicitly saved.<br />
* Additionally, metadata such as timestamp, source, subject, annotations, tags, user context, etc. could also be captured, perhaps within some type of metadata index. Thus, the utility and value of collected data increases as information assets increase over time.<br />
</td><br />
<td></td><br />
</tr><br />
<br />
<tr><td><br />
; Microformat Visualization<br />
* Provide mechanisms to search, browse, and visualize micro-formated content that has been cached or saved, similar to history and bookmarks.<br />
* Firefox could ship with a set of default views, but developers could also create add-on views that range from simple data look-ups to data mining and analysis capabilities. <br />
* By treating data elements as simple building blocks, visualizations could occur in ways the original content providers didn't expect. Similar to how data service providers (Yahoo!, Amazon, eBay, Google) are enabling server-side data mash-ups through defined APIs, a platform for microformat visualizations could allow for client-side mash-ups from the local data store.<br />
<br />
</td><br />
<td><br />
- [http://simile.mit.edu/piggy-bank/ Piggy Bank]<br /><br />
</td><br />
</tr><br />
<br />
<tr><td><br />
; Microformat Sharing<br />
* Once data elements have been found within a view, there should be an easy way to share data with others. <br />
* Since email is the most ubiquitous, scalable, and widespread communications vehicle in use, why not leverage this as an initial sharing platform? For example, a user could select individual data elements or an entire result set within a view, input an email address (perhaps from the hCard store!), and simply click a send button. <br />
</td><br />
<td><br />
<br /><br />
</td><br />
</tr><br />
<br />
<tr><td><br />
; Microformat Backup and Synchronization<br />
* Provide mechanisms to back-up the local data store (perhaps only information that is explicitly saved), or sync these data stores across Firefox installations. Firefox could also interface with existing services such as .mac, Windows Live, Google Browser Sync, etc.<br />
<br />
</td><br />
<td><br />
<br /><br />
</td><br />
</tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Content filtering, manipulation, and control ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Content filtering<br />
* Ability to filter ads<br />
** Also, block links around ads. The whole pages shouldn't be a danger zone -- if I click somewhere blank on a web page to give my browser focus, I shouldn't be taken to the advertiser's web site. <br />
* Ability to filter Flash movies<br />
* Ability to filter plugin content generally (Flash movies, Java applets; basically anything included in the page via an object, applet, or embed element)<br />
* Ability to filter content which is positioned outside of the normal flow (i.e. where the CSS "position" property is set to "absolute", "fixed", or possibly "relative"), so users can filter CSS-based popups<br />
* Ability to filter content generally (f.e. a interface that enables users to select and persistently hide portions of a page)<br />
* All filtering should enable one-click to view blocked<br />
* Should be very easy to add items to white/blacklists<br />
* Better control over image blocking (f.e. a small button that appears in the corners of images you hover over which invokes the "block images from this server" operation when pressed)<br />
* Volume/Mute for any audio content<br />
* Ability to set a charset for a site<br />
* Text-only mode<br />
** You have the option to switch a tab between "Text Only" and "Graphical" modes, with faster downloads/rendering if browsing in text only mode<br />
* Sound blocking, aka Mute Button. Turned off by default, when turned on blocks all sound (flash sound too) and warns the user that the webpage is trying to make sounds (with the ability to allow sounds just this once, for this domain, etc. Like the popup blocker). Plugins that lack mute support should be paused if possible, or terminated if necessary.<br />
* Frozen mode. Stops all animated GIFs, videos, Flash, script-driven tickers and anything else that moves, flashes, or otherwise annoys. Pages can be frozen and unfrozen at any time, and the browser can be set to freeze all pages on load.<br />
* Opera had a great button whereby you could stop the downloads of not only graphics, but many other elements like Javascript, Java and the like. Lets now add Shockwave/flash to this as well. After the page loaded, you could then download graphics and such by another click. But I want to add, that if graphics are blocked, then a placeholder should be put on the page, in order to make it render right. Not jumbled all around.<br />
* Ability to filter scripts which disable browser functionality, such as scripts to hide the address bar or 'no right-click allowed' scripts. Firefox has no obligation to respect functionality-breaking scripts.<br />
<br />
</td><td><br />
- [[User talk:bur#Flash_blocker| Flashblock remarks from bur]]<br /><br />
- [[User talk:Max.e#Flash_block_-.3E_Plug-in_management|A couple things from Max.e]]<br /><br />
- [[User_talk:Autodmc#Text_Only_Mode | Text Only Mode]]<br /><br />
- [[User talk:JebusWankel#Mute_Functionality | Mute Functionality]] <br /><br />
</td></tr><br />
<br />
<tr><td><br />
; Content filtering preferences<br />
* Ability to set persistent global, per-site, and per-page preferences<br />
** We might create a "web control" panel/sidebar that displays common preferences such as font size and charset<br />
** We should make such a panel extensible, so extensions can add additional controls to it<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Content manipulation<br />
* ability to lock the page scroll. I may sound bizarre but I will explain how it is usefull. Imagine you are editing a blog. Generaly you work inside a text area. So, you use your mouse scroller to scroll inside that text area. When you reach the end, the browser always scrolls the page, so, you lost the text area out of sight and have to scroll it again to put the text area visible.<br />
* ability to copy text from tables;<br />
* ability to insert checkboxes on anything, to use as marks. Imagine you are copying data from a page where everyline is a record. So, you go forward and back, from your program and the browser, copying each line... won't be wonderful if you can mark the lines you just have processed? <br />
* ability to delete text from page. Wonderful for when you are copying texts or other stuff from pages.<br />
* ability to enlarge form fields;<br />
* ability to take notes on screen. I mean arrows you can point to elements and write notes, post it, etc.<br />
* ability to make a slideshow of all images on a page. This could be based on image's size, so the user could adjust to block, for example, icons to be on the slideshow;<br />
* ability to navigate at the same time with other person on another place of the web; <br />
* 'Filter chains'. There may be several plugins attempting to change or access the page content at any given time, sometimes conflicting with one another, other times it is not clear what will be 'executed' first. The user should be able to implement a processing hierarchy (filter/extraction stages) that process the page according to a fixed set of rules. (i.e. adblock -> extensionFoo -> XML extraction -> Greasemonkey -> Display)<br />
* Option to show an icon next to (and/or in the status bar) hyperlinks which open in a new window/tab (e.g. the icon next to external links on Wikipedia, etc).<br />
* Facilitation of console manipulation tools. It would be nice to be able to bring up a console in Firefox and use various tools to manipulate the page 'on the fly'. More precisely, it would be good if developers were able to easily write interfaces for doing this. For example, it would be nice if it was easy for someone to write a console tool that manipulates the DOM with Hpricot or BeautifulSoup. (Make it easy/feasible to write Chickenfoot like extensions).<br />
* Scaling of images as well as text when zooming (an Opera-like feature) -- [[User:STrRedWolf|Kelly Price]] 08:01, 14 October 2006 (PDT)<br />
* Sort table columns or rows by right clicking the topmost or leftmost sortable element and selecting sort criteria. [[User:Randomly|Randomly]] 01:42, 15 October 2006 (PDT)<br />
</td><td><br />
* n/a<br />
* [https://addons.mozilla.org/firefox/230/ TargetAlert] & [https://addons.mozilla.org/firefox/3199/ LinkAlert] will do this<br />
* n/a<br />
* n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Forms<br />
* Ability to resize textareas<br />
* Textareas should act more "dungeon style" like most text editors - when you use the up or down arrow to move to another row, the cursor should remain in the same column or as far to the right as text allows.<br />
* Ability to save text boxes (See defunct Scribe extension)<br />
</td><td><br />
- [https://addons.mozilla.org/firefox/102/ Scribe]<br />
</td></tr><br />
<br />
<tr><td><br />
; Parental control features<br />
* Implement a set of parental control features<br />
* Something like a password protected version of the Greasemonkey script Invisibility Cloak would be very useful<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Plugins<br />
* Run plugins as a independent process, that talks with firefox via a socket or something like this. If a plugin crash it doesn't take firefox with it. It also allow one to kill a locked or high load plugins and keep surfing.<br />
* Run plugins as a independent process, so that when they leak memory, that memory will be freed when the tab or window is closed.<br />
* Run plugins as a independent process, so that when a plugin refuses to shut down (like acroread), the browser can forcibly kill it.<br />
* Tighten down the plugin API so that plugins have no direct access to any kind of system calls (i.e. the symbol table for plugins is carefully controlled). (X.org does this to DDX modules.) This way, things like memory management and such can be "wrapped" by Firefox to ensure that plugins are well-behaved.<br />
</td><td><br />
- [http://www.gibix.net/projects/nspluginwrapper/ nspluginwrapper]<br />
</td></tr><br />
<br />
<tr><td><br />
; Fix broken images<br />
* Add "Reload Image" right-click option on broken image placeholders, or "Reload all broken images" right-click on page option, when network problem creates broken images. Current behavior requires a full page refresh to load 1 broken image.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Stability and resource-utilization improvements<br />
Put each document into an <b><i>independent process</i></b> (not thread: separate forked process) so that:<br />
* When a document causes Firefox to crash, the whole browser won't be taken with it.<br />
* When a bug in Firefox stomps on memory it doesn't own, other documents in memory are not corrupted.<br />
* When a document causes Firefox to leak massive amounts of memory, closing that tab or window will free up the wasted memory.<br />
* When a bug in Firefox or a script on the page locks up (infinite loop or whatnot), the whole browser will not hang up, just the one document. Closing the tab or window kills the aberrant process. This is also an issue for DNS lookup; the browser always freezes completely during DNS lookup. Make this affect only the document being loaded.<br />
* Obviously, this also means that the Firefox main UI should also be in a separate process, and you should use IPC and sharing of window-system resource IDs and handles to communicate between UI and document processes. <br />
* When the UI crashes, restarting the UI can sweep up documents that find themselves unattached and re-present them undisturbed.<br />
* Cross-site scripting and buffer overflow exploits have a much harder time hacking into information for other documents, because they are inaccessible in separate processes.<br />
**To secure a process on Linux, simply write to the /proc/self/seccomp file. The process will then only be able to communicate via existing file descriptors (be sure to close the X11 one) and existing shared memory regions. Only about four system calls are allowed for a process in secure mode: read, write, exit, and signal handler return.<br />
* Provide an about:top view that gives an accounting of which documents and plugins are using how much memory and CPU time.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Per-tab sound level control<br />
* Each tab can have a sound level knob next to the "x" button that will allow users to regulate the sound output level from the page on that specific tab. extremely useful when multiple pages are playing sound and are difficult to regulate seperately due to bad coding. Also useful for very loud (or very quiet) pages which need adjustment.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a <br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
= Browser Interaction =<br />
== Scripting ==<br />
<br />
<table class="fullwidth-table"><br />
<tr><th>Browser Automation</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Scripting<br />
* Implement a possibility to record short macros/scripts in order to automate task done on homepages, e.g. login and print a specific table, etc.<br />
</td><td><br />
<br />
</td></tr><br />
</table><br />
<br />
== Opening Links ==<br />
<table class="fullwidth-table"><br />
<tr><th>Link Activation</th><br />
<th width="30%">References</th></tr><br />
<br />
<br />
<tr><td><br />
; Link Activation<br />
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.<br />
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.<br />
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs<br />
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.<br />
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.<br />
* A simple example of where this would be useful is opening a number of items in a list of links, including the results of a search engine.<br />
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.<br />
*Any link will open in a new tab if dragged in any direction rather than being clicked.<br />
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back. <br />
*if a link links to an image an preview of that image after 1 second of hovering over that link would be nice. The picture should have some kind of [X] to close it (or clicking somewhere else) and a resizer of that preview image would be nice too.<br />
*if I mark a text which contains a URL that does is not clickable it would be nice to have a right click option to open that link (marked text need to be parsed. if a collection of links is in that marked text a chooser would be nice (seen in opera) + "open all links in tabs" would be nice too<br />
*an option to parse all links in a website for dead ends. example: software collection of a 5 month old website. with an option to check (behind the scenes) all links for working results would be nice. If a link returns a "not found" or so, FF could darken that link (or alter an tiny image in front of the link - sad skull - or so.<br />
* When downloading a pdf (non HTML file) with target="othertarget" in link check mime type first before opening another (empty) tab and download / process the file directly.<br />
</td><td><br />
<br />
</td></tr><br />
<br />
<tr><td><br />
; Link Context Menu<br />
* Add a command to open selected text in a new tab/window.<br />
* Allow to customise the links context menu. I for example have never clicked on the "Send Link", "Bookmark This Link" on purpose and i hate it when it starts my outlook or opens up the bookmark dialog.<br />
</td><td><br />
https://addons.mozilla.org/firefox/1472/<br />
</td></tr><br />
<br />
<tr><td><br />
; Additional Mouse Interactivity<br />
* Whitespace grabs within the document act as grabbing the icon in the address bar.<br />
* Draging links to whitespace opens the link in new tab or window<br />
* Highlighting text causes it to be treated as a link in all of it's functionality, including the I'm feeling lucky Google search.<br />
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object<br />
</td><td><br />
<br />
</td></tr><br />
<tr><td><br />
; Javascript Links<br />
* When ctrl+click or middle clicking a void() + onclick link browser opens current page in a new tab or window then performs a click on the requested link.<br />
</td><td><br />
<br />
</td></tr><br />
<br />
<tr><th>Tab Interaction</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Tab Refresh<br />
* Allow to refresh Tabs automatically by a counter<br />
</td><td><br />
<br />
</td></tr><br />
</table><br />
<br />
== Quick Top of page/Bottom of page ==<br />
<table class="fullwidth-table"><br />
<tr><th>Quick Top of page/Bottom of page</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Get back to top quickly.<br />
* Perhaps a Goto Top and Goto Bottom button in the Find bar at the bottom of the browser. This would be faster than using the scrollwheel, which many mice don't have. <br />
</td><td><br />
<br />
</td></tr><br />
<br />
</table><br />
<br />
= Compatibility =<br />
== Web standards compatibility ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; ACID 2 test<br />
* Make sure Firefox passes it<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=289480 Bug 289480]<br />
</td></tr><br />
<br />
<tr><td><br />
; Full SVG 1.1 support<br />
* Add full support (not a non-standard subset of it) of SVG 1.1 or TinySVG 1.2<br />
</td><td><br />
[http://www.w3.org/TR/SVG11/ W3C SVG1.1]<br />
</td></tr><br />
<br />
<tr><td><br />
; Content-editable<br />
* Add support for content-editable<br />
</td><td><br />
[http://www.w3.org/TR/SVGMobile12/text.html#text-edit tinysvg w3c]<br />
</td></tr><br />
<br />
<tr><td><br />
; CSS<br />
* Make "display: inline-block" work correctly<br />
* Support printing-related properties such as page-break-before and page-break-after<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=9458 Bug 9458 (inline-block)]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=24000 Bug 24000 (page-break)]<br />
</td></tr><br />
<br />
<tr><td><br />
; XForms<br />
* XForms supported and built-in.<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=326372 Bug 326372]<br />
</td></tr><br />
<br />
<tr><td><br />
; XHTML 2.0<br />
* Add support for current XHTML 2.0 draft<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=161463 Bug 161463],<br /><br />
[http://www.w3.org/TR/2006/WD-xhtml2-20060726/ XHTML2 Working Draft]<br />
</td></tr><br />
<br />
<tr><td><br />
; new DNS like system<br />
* invent a thing like DNS, but where new domain names can be added easily and free of charge.<br />
<!--dont now if this above is written in correct english, if not pls correct it. but hope that you understand what i am meaning--><br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<br />
<tr><td><br />
; XHTML ruby annotation<br />
* Ruby annotation has been included in XHTML spec since 2001, and there has been a great extension to implement it. Now, let's make it in Fx 3.<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=33339 Bug 33339 - XHTML ruby support], <br />[http://piro.sakura.ne.jp/xul/_rubysupport.html.en XUL Apps > XHTML Ruby Support]<br />
</td></tr><br />
<br />
<tr><td><br />
; shy<br />
* Add full support for soft hypens.<br />
</td><td><br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=9101 Bug 9101]<br />
</td></tr><br />
<br />
<tr><td><br />
; IE Compatibility<br />
* Answer to below suggestion: Integrate IE tab into firefox by default.<br />
* Add fallback mode to support non-standards based rendering when "IE only" features are present in a web page so that the page will render correctly. Allow feature to be turned on and off. Could be made into a plug-in instead of putting feature directly into Firefox. This feature would allow more people to convert to Firefox and leave IE behind forever.<br />
* Agreed with the above statement. I have companies that insist I use MSIE, even if I'm in linux. I believe Opera has the feature whereby it uses the MSIE engine, but I haven't tested it on these sites. This needs to fix the problem of a) a site refusing to even load, if your using anything but MSIE, b) allowing uploads of files even with FF (over IE)<br />
* Support for embedded managed code objects (ie .NET Windows Forms or platform independant MONO assemblies)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; XSLT 2.0<br />
* W3C Candidate Recommendation 8 June 2006<br />
</td><td><br />
[http://www.w3.org/TR/xslt20/ XSLT Candidate Recommendation]<br />
</td></tr><br />
<br />
<tr><td><br />
; Full HTML 4.01, and CSS 2.1 compatibility.<br />
* Increase the standard bar in HTML, and CSS standard.<br />
* Firefox should work hand-in-hand with the W3, to be 100% compabiable with the current CSS/HTML/XHTML standards, so we web site writers can write our sites with FF in mind, and let IE, and others play catch-up. Also, FF should be updated quickly in order to be current with the next versions of such. We've wanted CSS, and such for years, and now we get it, it's the browsers that stop us from accually using it fully. There is no really good reason why at least FF shouldn't be 100% compatible (IE has an exchuse but I'm not going to bash companies here :)<br />
</td><td><br />
[http://www.webdevout.net/browser_support.php Browser standard comparison]<br />
</td></tr><br />
<br />
<tr><td><br />
; iCab-Smiley analogue<br />
* This nice feature will promote standard-compliancy of the web.<br />
</td><td><br />
[http://en.wikipedia.org/wiki/ICab iCab wikipedia page]<br />
</td></tr><br />
<br />
<tr><td><br />
; Firefox prefix in CSS<br />
* Is it possible to be added some prefix for firefox in CSS<br />
Ex:<br />
body {<br />
f_color: red;<br />
f_width: 100%;<br />
}<br />
</td><td><br />
n/a<br />
</td></tr><br />
<tr><td><br />
;MHT / MHTML Support <br />
* Saveing / Reading of MIME Encapsulation of Aggregate Documents, such as HTML <br />
</td><td>RFC 2557<br />
<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=18764 BUG 18764]<br />
[https://bugzilla.mozilla.org/show_bug.cgi?id=40873 BUG 40873]</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve overall standards support<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Protocol and media support ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Improvements<br />
* Improve PDF support and handling (Built in PDF viewer with support for more exotic features like forms, javascript, etc.)<br />
* Save page as PDF<br />
* Improve Java support<br />
* Improve FTP support<br />
* Add support for SFTP and FISH (SSH2)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Desktop experience<br />
* Support X11 session management<br />
</td><td><br />
[http://en.wikipedia.org/wiki/X_session_manager X11 session manager]<br />
</td></tr><br />
<br />
<tr><td><br />
; New technology support<br />
* IPTV<br />
* IM<br />
* Integrated radio livestream<br />
* Open Document Format<br />
* BitTorrent<br />
* Magnet links<br />
* eDonkey links<br />
* SCTP <sup>1</sup><br />
* Jabber/XMPP<br />
* OBEX (Bluetooth, etc)<br />
* SyncML<br />
* SIP<br />
* Scriptable ZeroConf (Bonjour/Rendezvous)<br />
* WML. Would be grat if firefox could interpret WAP pages.<br />
* WebDAV and Secure WebDAV<br />
* SMIL 2.0<br />
* Microformat detection/notification with metadata<br />
* metalink (mirrors & checksums for downloads)<sup>2</sup><br />
* Ogg<sup>3</sup><br />
* WMV<br />
* Open Document Format<br />
* XBEL<br />
* SVG via img tag<br />
* JPEG2000<br />
* ANG<br />
* MNG<br />
* JNG<br />
* DJVU <sup>4</sup><br />
* Save page as image, this should save a complete page as an image just like a screenshot does. Optionally attach the image directly to a new e-mail. <br />
</td><td><br />
<sup>1</sup> [http://www.sctp.org/download.html SCTP patch]<br /><br />
<sup>2</sup> [https://bugzilla.mozilla.org/show_bug.cgi?id=331979 metalink]<br /><br />
<sup>3</sup> [http://meta.wikimedia.org/wiki/Firefox_Ogg_Support Firefox Ogg Support]<br /><br />
<sup>4</sup> [http://djvulibre.djvuzone.org/ Djvu support library]<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== UI compatibility ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<tr><th colspan="2">Linux</th></tr><br />
<tr><td><br />
* Render embedded buttons with native GTK2 widgets<br />
* Make keyboard shortcuts work with non-Latin keyboard layouts in GTK2 (currently, GTK1 builds work as they are supposed to, as well as GTK2 under GNOME. But wth, not all people use GNOME!)<br />
* Make sure GTK2 builds do not screw up the keyboard focus: focus is periodically placed to the improper widgets which effectively disables keyboard shortcuts until mouse click inside browser.<br />
</td><td><br />
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].<br />
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=340944 bug #340944], [https://bugzilla.mozilla.org/show_bug.cgi?id=69230 bug #69230], [https://bugzilla.mozilla.org/show_bug.cgi?id=295614 bug #295614].<br />
</td></tr><br />
<tr><th colspan="2">Mac OS X</th></tr><br />
<tr><td><br />
Support Command-Option-F to select search toolbar (standard for Mac applications).<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
= Global community =<br />
== Internationalization ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Language support<br />
* Improve complex glyph rendering<br />
* Support more complex languages (Hebrew, Arabic, pangool, all Indian dialects)<br />
* Multilingual browser, to allow single binary for multilingual systems<br />
* Being able to switch user-interface language ''without'' restarting the browser<br />
; Localisation<br />
* Times are converted local times<br />
* Units such as currency, weight, distance are converted or highlighted, and allow for right click interactions<br />
</td><td><br />
See [https://bugzilla.mozilla.org/show_bug.cgi?id=240914 bug #240914].<br />
(David Baron said: I expect this will be fixed for Gecko 1.9 (i.e., Firefox 3.0...)<br />
<br />
See [https://bugzilla.mozilla.org/show_bug.cgi?id=356184 bug #356184].<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
<li>Ability to highlight text/tables in a webpage and then right click and "Export to OpenOffice.org Calc/Writer or Microsoft Excel/Word" depending on users preference and operating system.</li><br />
</td><td><br />
Many people I have shown Mozilla Firefox to have missed such a feature as it is in Microsoft Internet Explorer.<br />
</td></tr><br />
</table><br />
<br />
== Accessibility ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Font deltas<br />
* Remember a users font delta for each site. If a user goes back to that site in another session, they should not have to re-adjust the font size every time they visit.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Zooming<br />
* Add smooth zooming<br />
* Implement full page zoom, including images (sub: have browser optionally store this setting per-page, per-site, or globally)<br />
* Zooming, panning, scaling for images<br />
* Add "Fit to width" option (like Opera)<br />
* Implement user-definable zoom levels<br />
* Make zoom levels settable preferences per page, per site, or globally<br />
* Menu entries for them in the view menu in a possible page zoom submenu and text zoom submenu<br />
* Also putting this in Tools > Options > Content > Page Zoom % and Text Zoom %<br />
* Prettier image resizing & scaling (Bilinear, Bicubic, anything better than Nearest Neighbor)<br />
<br />
</td><td><br />
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=4821 bug #4821].<br />
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=98971 bug #98971].<br />
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=276166 bug #276166].<br />
</td></tr><br />
<br />
<tr><td><br />
; Scrolling<br />
* Add smooth scrolling<br />
</td><td><br />
* ''How is this different to Preferences | Advanced | General tab | Use smooth scrolling?''<br />
* "Maybe refers to the Mac version, like how Safari allows scrolling 1 pixel at a time using a touchpad"<br />
* "The built in smooth scrolling in Firefox is very 'rough' compared to the way Opera seems to handle it."<br />
</td></tr><br />
<br />
<tr><td><br />
; Voice navigation<br />
* Add Support for Macintosh VoiceOver screenreader<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Create an html "Next Page" extension where, if there is no forward page to go to, it goes to the "next" page just by clicking the mouse "forward" button. Very useful for going through pages and pages of results just by clicking the forward mouse button instead of scrolling down, finding and clicking the "next page" link on the bottom of every page over and over again. This might have to be coded into webpages but it needs to be supported by the browser so it can start being used. This might need to be submitted as a W3C Open Standard.<br />
* Simplify process for creating accessible themes (dev? docs?)<br />
</td><td><br />
n/a<br />
</td>Why? To obtain accurate page output, PDF export would be more effective.</tr><br />
</table><br />
<br />
= Developer-facing elements =<br />
== Developer-facing UI ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Developer tools<br />
* Interface, to call JavaScript functions from XSLT<br />
* (You can take a look at [http://msdn2.microsoft.com/en-us/library/ms256042.aspx msxsl:script])<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Developer tools<br />
* Unified DOM/JS debugger with advanced logging<br />
* Live HTTPHeaders<br />
* Web developer toolbar<br />
* AJAXy stuff etc. (What does this mean?)<br />
** Some way to get feedback on XMLHttpRequest dispatches (which would otherwise be invisible)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Developer tools<br />
* Asynch-Panel to replace javascript div-update implementations<br />
<br />
It would be great to have mechanism to define a panel, where data may be send to a server and its response is rendered into a certain area like:<br />
<br />
<nowiki><br />
<asynch-panel refpanel="myPanel" refid="test" /><br />
<asynch-panel name="myPanel" target="http://blabla.de/bsp.jsp"><br />
<input type="text" id="test" value="<%="blabla"%>" /><br />
<input type="submit" /><br />
</asynch-panel><br />
</nowiki><br />
<br />
<br/><br />
Of course such panels would allow nested panels and form elements to have maximum control.<br />
<br/><br />
<br/><br />
I know that such an extension would be only usable for Firefox users, but it would speed up asynch development at leat in closed user groups with certain system requirements.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Developer tools<br />
* FAST! VM for client side scripting with extension API to add additional languages other than javascript<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; CSS Enhancements<br />
* anti-aliased rounded corners<br />
* gradient filled background <br />
(check out [http://www.terrainformatica.com/htmlayout/cssmap.whtm "HTMLayout CSS support map"], they have done gradient filled backgrounds very effectively)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Simplified Drag and Drop Support<br />
* I know it might be heretical, but it would make life easier for some of us Ajaxy types if Firefox bit the bullet and supported IE style drag and drop.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<tr><td><br />
; 'Official Generic' code release<br />
* Offer a 'generic' Firefox tree without trademarked elements or non-free plugins.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Create a "unified set of modern web developer tools"<br />
* Add a [http://en.wikipedia.org/wiki/.NET_Framework .NET]/[http://en.wikipedia.org/wiki/Mono_%28software%29 Mono]-Wrapper to host both the web browser and the WYSIWYG editor (if such a tool exists, I'm not sure about it) in my own .NET Windows Forms applications. Do this in a highly customizable way to control most aspects of how the browser appears. [[User:Uwe Keim|Uwe Keim]]<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Add-ons/Platform development ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Extensions<br />
* Finally codify and document all existing interfaces: chrome, DOM, XPCOM before inventing new ones.<br />
* Make it easier to write extensions (new sandbox for extensions, extension platform?)<br />
* Allow for limited types of sandboxes that bypass security by strongly limiting extension abilities.<br />
** Simple toolbar and toolbar button extensions which can only do anything when clicked and only do a limited number of things (make some HTTP request, change the location, open a window or tab, etc.) and can't do anything otherwise.<br />
** Similar menu operations<br />
** Extensions that auto-install and then show a permissions dialog.<br />
*** Enable/Disable reading or writing clipboard<br />
*** Enable/Disable reading or writing current DOM<br />
*** etc.<br />
** Most important, you could install these without trusting the sources. Special link elements or HTTP headers could even associate pages with special extensions to autoinstall and enable just while at the given page.<br />
* Provide a simpler API for functionality extensions commonly use, including:<br />
** accessing preferences<br />
** filesystem operations (f.e. rginda's [http://lxr.mozilla.org/mozilla/source/extensions/irc/js/lib/file-utils.js file utils library])<br />
** observing onLocationChange (i.e. getting notified whenever the page changes)<br />
* Provide support for hierarchical extension dependencies<br />
* Extension preferences export, sort of like an OPML for extensions that can get slurped in to another FF seat<br />
* Include Thunderbird in Firefox, like Sunbird was added to Thunderbird. ( guess you should use SeaMonkey !)<br />
* add a system to be able to choose what handle what in firefox (firefox built-in svg instead of an external SVG plugin for instance)<br />
* add a generic plugin like plugger so you are able to choose depending on a mime/type or file extension a program to handle it inside an html page.<br />
* allow extensions to expose individual buttons instead of toolbars, and allow buttons to be placed using "Customize Toolbar". This would allow individual features from different extensions (I.E. Google PageRank and Web Developer toolbar cache disabling) to be used without using the entire toolbar.<br />
* allow extensions access to content displayed by plugins. For example, I'd like to be able to mark up PDF files with the ScrapBook extension.<br />
** If Firefox and Thunderbird are integrated, please keep standalone versions of each available to download. Then users who only require one of the programs can still use it without wasting resources. Better yet, keep them separate.<br />
; Platform<br />
* A useable security model for remote XUL. Currently the restrictions on remote XUL cripple many possible uses for the platform, and there is no easy way to elevate the permissions for a remote application or domain.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><br />
<td>* A <b>loader</b> within the tray icon area which keeps the Firefox code loaded so it does'nt has to be reloaded all the time after you closed all windows of Firefox. An implementation is quiet easy: You just need to create another window like the download manager and drop it out of sight so Firefox is still open but invisible. This isn't wasting too much memory but saving a lot of time in starting Firefox again because its still loaded. A normal click on the tray-icon or another double click on the desktop will be handled the same way as now if Firefox is already running</td><br />
<td>FrenzyM6</td><br />
</tr><br />
<br />
<tr><td><br />
; APIs<br />
* Add a metadata handler extension API<br />
* SHA-2 hashes and AES-256 or other strong crypto in JavaScript (operate over base64 or binhex). Good for AJAX securty.<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Pages with wrong/unknown mime type<br />
* Often I will find a page that firefox can't display. Nearly always, such pages are plain ASCII text with a weird mime type. For example, firefox doesn't know how to display typical source code. (C, FORTRAN, BASIC, Pascal...) I get a dialog asking me to save the file to disk or choose an app for displaying the file. One particularly desirable display choice is missing: <b>the browser itself!!!</b> Come on now, it's plain ASCII text. Surely the browser can handle this.<br />
* Firefox can determine the mime type of a local file. (by magic or extension I suppose) For remote files, it always blindly trusts the server. Nearly always, the server just looks at the file magic or extension. This ought to not matter, but it does. Servers often lack a complete and modern mapping from extension/magic to mime type because people don't often install lots of multimedia apps on servers. Such servers will substitute a generic mime type. IE tolerates this just fine because IE determines mime type from the file extension alone. Firefox acts weird: if you "save link as..." and then view the local file, firefox will use a different (inconsistant) mime type. At the very least, IE-like behavior should be an option, and should always be used when the server-provided mime type is clearly useless. If firefox must pop up a dialog to ask the user about viewer apps, the default needs to be that of the file extension. Probably it is better to just bury this server-knows-best relic of the past though, standard or not.<br />
</td><td><br />
</td></tr><br />
<br />
<tr><td><br />
; Javascript improvements<br />
* Library improvements<br />
** Put atleast one of the most commonly used Javascript libraries in the browser (scriptaculous, etc) so users don't have to keep downloading them.<br />
** Throw in the Ruby interpreter and use its rich libraries.<br />
* Interpreter improvements<br />
** Include a step-through javascript debugger (or possibly include this in the Javascript Console).<br />
* Javascript Immediate Window<br />
** Add an Immediate Window to the Javascript Console (similar to the immediate window in Microsoft Visual Studio), that will allow you to dynamically view and change all javascript variables currently dimensioned on the page. Possibly a list of functions and/or methods that you can double-click to execute (and if it returns a value, it could present it in a messagebox or tab or something...) Also, if you could inject html and/or javascript method/functions into the page, it could be very useful for obvious debugging purposes.<br />
** Maybe a right-click + "Insert HTML here" contextual menu item.<br />
</td><td><br />
</td></tr><br />
<tr><td><br />
; Netscape Plugins<br />
* There should be a possibility to control the volume of Plugins such as flash or java. There are few things that are more annying than flash animations that make noises which you don't want them to make.<br />
</td></tr><br />
<tr><td><br />
; Architecture<br />
* Firefox should become a minimal browser<br />
** All features are provided by the plugin architecture<br />
*** Even basic functions like bookmark manager or history should be provided as extensions to become exchangable<br />
*** Extensions can be installed/uninstalled without restarting the browser<br />
*** Per-machine extensions, Per-user extensions<br />
*** Search plugins are provided as extensions<br />
** Even the rendering engine becomes exchangable and configurable<br />
*** Support for Gecko, Opera, KHTML, (IE)<br />
*** per-site configurable which engine to use<br />
<br />
; Developer focus should not be on features, but on architecture<br />
; Firefox should be distributed as package including the core browser plus a set of selected basic extensions like history and bookmark manager<br />
</td><td><br />
</td></tr><br />
<tr><td><br />
JavaScript Frame Sandbox<br />
* Have a way to mark the security level of a frame, for example - say you're writing a web app and you have a frame where you need to display a user uploaded web page - it would be great if you could prevent that frame from accessing it's parent, the cookie, etc. This would make it a lot easier to write a secure web app. AFAIK, the only way to do this is to give that frame a different subdomain - not always a convenient thing to do. Not sure exactly how to accomplish this while sticking to html standards ... any ideas?<br />
</td><td><br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Improve RDF support, or develop a better general-purpose data model<br />
* Improve support for multithreading<br />
* Implement more consistent data types ("Instead of JS + variant, mozStorage, RDF, etc. have universal data types (string, integer, decimal, date, blob) that are used everywhere")<br />
* Improve support for advanced UI features like notification icons, alert bubbles, shell integration<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Performance ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
Be the fastest browser on the market, not only on "fat" desktops, but also on bargain desktops with only 256MB of RAM.<br />
</td><td><br />
[http://www.howtocreate.co.uk/browserSpeed.html Mark Wilton-Jones' browser speed benchmarks]<br />
</td></tr><br />
<br />
<tr><td><br />
Try to implement an internal memory manager. It should, for example, pre-allocate about 10% of ram memory and try to operate within that memory. All calls to "free()" should release memory to this global memory pool and all calls to "malloc()" must allocate memory from this memory pool. If properly implemented, we can even reduce the overheads that may arise due to such an implementation.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Improve browser launch time on both Windows and Mac OS X. Currently IE and Safari launch much more efficiently, making it more sensible to open one of those browsers when quickly looking something up. Enduring the sluggish launch time again and again makes for an irritating experience.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Integrate a FF Preloader into the program. Currently the Preloader for Firefox 1.0 doesn't work for 2.0. A preloader option within FF that allows the user to choose whether to preload certain parts of FF could improve the boot time dramatically.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
At the very least, bring up a UI as quickly as possible. Show the splashscreen while loading. Often I find I don't know whether Firefox has started up and start up multiple copies.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Bring speed up to par with Safari/Opera on the Mac platform. Perhaps bring project into XCode/Objective-C/Cocoa? The Cocoa API is much more feature complete than the Carbon API, since the latter is more of a carry over from MacOS 9. With Cocoa, things like integerated spell checking would come 'free', since they are associated with the widgets being used.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Hardware accelerated graphics (perhaps use the Vista/Mac OS X/AIXGL/XGL engines to do the acceleration for us)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Make the javascript engine less cpu hungry.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Do more caching of the DOM. E.g. stacking several<br />
PNG-Images with alpha channel slows down the browser<br />
dramatically, even for unrelated DOM changes.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<br />
<tr><td><br />
Make the textarea performance better. Often, even on fast machines, I can type faster than the text appears. This doesn't happen all the time, but does often enough. As it catches up to me, I see all of the text in the textarea being cleared and flashing up for each character typed.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
It is very annoying to be typing into a text box and have the browser go unresponsive for a few seconds while in the middle of typing. This is caused by Javascript in other windows (like gmail) waking up and using the network. Threading needs work to fix this.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Include a language-neutral VM for a back-end for javascript. The benefits are quite significant, and include: JIT compling, with caches of compiled code (done when the VM is not busy); a better sandboxing model for compile-time overruns and exception handling; better threading model for managing multiple windows and tabs; language-neutral interface for extending or replacing the runtime language (i.e. changing it from something like "javascript-1.7" to "moz-cli-1.0", so that languages like Ruby and Python could be compiled into the cli); easier to add libraries of code to the base distribution or from external sources (code libraries that people could download to their computers and use for certain sites); the introduction of a unified object/exception/type model. Perhaps less important reasons include: businesses might be a little happier because their code wouldn't be completely "transparent" as it travels across the net if it's possible to send it already compiled to a person's computer; it might make it possible to add extensions, like signed code or an abstract threading model. <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Now multi-core CPUs are becomming standard it makes sense to improve multi-threading. Javascript or rendering on one tab should not lock up other tabs, for example. Even within a tab, image decoding, scripting, plugins and HTML rendering could all be separated.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td>Consider implementing IEView and IETab extensions funcitonality in FF itself. Many web pages (e.g. some online e-mail access services) still require the user to be running IE so a way for FF users to view those pages wityhout having to find out and install those extensions would be extremely useful.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td>Remove memory leaks (e.g. try using Firefox on the Typo3 Backend - you'll have to restart FF about once per hour, if you seriously use it)</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td>Make Firefox more crash resistant. I don't really know if it is the FF core which causes the crashes or one of the Extensions I run.<br />
<br />
Additional idea: Let Extensions run in a sandbox so they can't crash Firefox any more. Maybe that sandbox could also guard against unsafe Extensions which may try to compromise your computer.</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Develop new features as extensions (enabled in the default install) so that they can be disabled if un-needed. We MUST avoid bloat to stay in the lead, and forcing new features on people that just want a clean experience is not in our best interest.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
* Develop a set of Official Extensions such that most of these new features (and some of the old features) can be made optional for the basic user. Firefox's strength is that it is a low weight (rather than a kitchen sink+) browser. Creating Official Extensions which expand the useful feature set, but are optional, will keep Firefox lean and mean.<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
= Mobile and Enterprise support =<br />
== Mobile device integration/support ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Send content to device<br />
* Bluetooth support<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
* Support non-PC platforms (e.g. Palm OS)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; firefox mini/mobile<br />
cellphone browser using JAVA(like opera mini).<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
== Enterprise deployment ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Support w32 Group Policies<br />
* Allowed extensions<br />
* Basic customizations (eg. company homepage)<br />
* Requires that controls become disabled if overridden by policy. Use the normal Windows UI for editing the policy itself. See {{bug|267888}}.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Better automatic proxy configuration<br />
* Allow async (or in another thread) DNS resolution in proxy.pac so that isInNet doesn't lock ALL browser in a slow DNS query (see bug #208287)<br />
* Automatically discover proxy turn on by default (check if there is a wpad.dat in the install, turn on if true ?)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Updating<br />
* Implement a -update commandline switch which starts Firefox in an automated update mode (core+extensions). Further user interaction shouldn't be necessary<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
= More vs. Less =<br />
<br />
Well it seems like we could devide the users wishes into two overall categories: While the ones can�t get enough features, want more of them and through that keep pushing new technologies and conveniences for the user, the other fraction just want a quick and stable browser, supporting all the W3 standards.<br />
<br />
I belong the other category, I want a quick and stable browser with a lot of Extensions and at least 5 distinct good looking skins. Still, I've got to admit, that without the more-and-more fraction, I still would not use the Mouse Gestures. So on the one hand, I am by all means interessted in the ideas of the other users, on the other side, I got to admit that I am _saturated_. The new features in version 2.0, I do not want them. Honestly. Yeah. That's it. So, unlike most of the users who posted here, I simply do not have any _new_ ideas thus I would prefer to vote uppon the most wanted features. [[http://wiki.mozilla.org./Firefox/Feature_Brainstorming#Compatibility]]<br />
<br />
Instead, you could focus on Sunbird. And of course some of the more interessting extension could some help to improve faster. I do not want to tell anybody how to spent his or her time, but if I am asked, this is my answer.<br />
<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; Packaging<br />
* Distribute a single, lightweight feature-wise version of Firefox WITH a set of Mozilla Firefox developed and branded extensions in a specific extension pack (se the matching suggestion above). With this solution you will have:<br />
** A Firefox "Core" with just essential features (based upon XULRunner...)<br />
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".<br />
* Marketing wise, it could be like now a SINGLE installer, with an optional flag to be turned off during install. Still, after the setup, you could remove the extensions and you'll be "light" again.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
<br />
I fully support the idea of a minimal firefox with official extensions from the devs and unofficial extensions from the communitiy. Firefox is getting too big. The first time I used Firefox (around 0.5 ?), I used it, because it was small and fast! Now it just takes too long to load. This also helps the core team to do it's core stuff, and the extensions people to work on thier extensions separatly. If they want to update a feature or remove some bug, only the new extension has to be upgraded and not the full Firefox package. Official extensions would also allow the devs to adopt community extensions, if they are deemed usefull for (nearly) everyone, and add them to the offical Firefox extensions.<br />
<br />
<br />
----<br />
<br />
How about a extension 'mode' pack or something? This could be a bunch of plugins grouped under a certain name like 'Standard','Ultra Fast','WebDeveloper','Kiosk' etc... and then have a simple drop down where one could select the 'mode' and only plugins for that mode would be loaded. This way we get the fast version, and the features packed versions for those who want it (and we can easily switch). Ofcourse let the user modify the mode pack if they wish, but this can be hidden somewhere so beginners don't stumble upon it by mistake and mess things up.<br />
<br />
It really is not a 'fast mode' vs 'feature packed mode' only, as it depends very much on what features a user wants and what they are doing at the time. By creating a couple of common usage mode packs it will make it easy to customize without having to individually download and install each plugin (though one could still do this). Maybe this is what a 'profile' is all about, but then again I still like to share bookmarks no matter how I'm browsing.<br />
<br />
I for one sometimes like the browser to be very fast, at other times I prefer all the web developer options, and at other times when browsing for personal use I'd like other plugins loaded.<br />
<br />
This way the core can stay small but first time users still get the cool behaviours they like without having to understand this whole plugin install business.(so a standard download and a core download without the mode packs for example)<br />
<br />
The use case I see is that first time users will want all the whiz bang toys to atleast match other browsers, and don't want to go through and figure out what extensions are and how to install, they just want to click go and off they go. Experienced users on the other hand may want other features or a slimmed down feature set. I think this approach solves both issues.<br />
<br />
= User support and Testing =<br />
== Help documentation ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; In-browser<br />
* Integrate in-product help and first-run/updated pages with online help.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Website<br />
* Move the majority of Firefox Help online, except for a minimal set of "in-product" help pages. This online help system should include the ability for community to post comments, corrections, updates, etc.<br />
* Integrate instant IM chat and newsgroup search with help<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Intro/Tutorial mode<br />
* host it on mozilla.com as movies<br />
* have some UI hooks in the product<br />
</td><td><br />
- [[User:FunnyMan3595:Tutorial_Mode_Thoughts|thoughts from FunnyMan3595]]<br /><br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
</table><br />
<br />
== User-testing ==<br />
<table class="fullwidth-table"><br />
<tr><th>Specific features</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
; User testing extensions<br />
* Create extension to allow for remote user testing<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Development build UI changes<br />
* Add "send feedback" buttons to dialogs in development builds<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
; Improve Talkback: User Experience and Robustness<br />
* Talkback (and its report queue) should be more invisible to the user. Plus Talkback rarely seems to work for me. My Talkback report queue often ends up with 3-4 reports that never seem to get through to the Talkback server.<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><th colspan="2">General tasks</th></tr><br />
<tr><td><br />
n/a <br />
</td><td><br />
n/a<br />
</td></tr><br />
</table><br />
<br />
= Other resources =<br />
<br />
<table class="fullwidth-table"><br />
<tr><th>Misc Thoughts</th><br />
<th width="30%">References</th></tr><br />
<br />
<tr><td><br />
* An alternative view of the web browser<br />
** Firefox as a new kind of desktop manager.<br />
** Active front end.<br />
</td><td><br />
[[User:Anonymous42|Some thoughts]]<br />
</td></tr><br />
<br />
<tr><td><br />
Enabeling new Top-Level-Domains on browser basis<br />
* Top-Level-Domains for regions, cities and others<br />
* Top-Level-Domains with IDN characters<br />
</td><td><br />
[[User:Dotzone|New Top-Level-Domains]]<br />
</td></tr><br />
<br />
<tr><td><br />
Decentralized/distributed browsing: in case a website has been slashdotted, Firefox should still be able to reach to its data by using the offline website data which is stored locally at other Firefox users, who were able to connect to it, their disk. Firefox should act as a kind of a torrent client.<br />
Of course, there might be some security issues. Https websites should be denied and the user itself should be able to disable this "torrent functionality".<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
Please focus more on stability, robustness, and security than on adding fun features. New features are nice, and fixing bugs isn't so much fun, but I find Firefox to be more of a memory hog and less stable than IE, and that's pretty sad. Stop competing against other browsers because you're afraid of losing market-share. The only way Firefox will ever be truly great if it's designed to be great from the ground up. Focus on changes that are less glitzy and more on changes that are fundamental to making a good browser platform. When something needs to be re-architected, re-architect it. Don't assume that bugs will ultimately get fixed; so far, Firefox has added features faster than bug fixes. Rather, focus on design principles that minimize the chances that problems will happen and minimize the consequences when they DO happen (and they will!).<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
I agree with the above. Firefox also has a reputation for being fast and relatively slim and there already is a plugin system for those who want a feature laden browser, so the focus should be on essential improvements that will have an impact on usability for the majority of users. A lot of the proposals here go way beyond what a dedicated browser should be able to do (more or less why Firefox was created from the Mozilla suite in the first place, no?) and would just add a lot of bloat.<br />
</td><br />
<td>n/a</td><br />
</tr><br />
<br />
<tr><td><br />
I concur with the above two requests. Fix all the memory leaks! Firefox leaks memory like a sieve. I hate having to restart it periodically in order to get it all reclaimed. A web browser shouldn't be using nearly 150 MB of ram. That's 15 MB for each of my open tabs!<br />
</td><br />
<td>n/a</td><br />
</tr><br />
<br />
<tr><td><br />
I don't know where this would go, but how about a really easy off-line browsing agent? Here's an example of what I do. Every morning I pull up about a dozen web pages in tabs, as a sort of 'newspaper' I read specific articles that catch my eye, or have an interest, like say the North Korea problem. I then go to the next article. (just like a newspaper.) I'd like to be able to click a 'offline this link' (or something like that), where it downloads just that article, as deep as it needs to go, with all the stuff that goes with it) then save it. I can then take this on my laptop and read it at work, in the car or such if/when I don't have internet connections. The off-line browsers I've used want to download the entire site(s), and are so hard to configure I give up on them.<br />
<br />
Also it should handle login sites too (like bank sites) but it'd be ok, if you have to input the login/password manually.) <br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
I have no idea if this is possible, but if Thunderbird is installed it would be cool to have the option of opening Thunderbird as a tab.<br />
</td><br />
<td>n/a</td><br />
</tr><br />
<br />
<tr><td><br />
Two buttons for favorites that open as many tabs as there are links in a special folder: One for daily checked pages (e.g. news paper, special forum a.s.o) and one for pages you check only sometimes (e.g. homepages of former friends or employers, news of your hometown a.s.o.)<br />
</td><td><br />
n/a<br />
</td></tr><br />
<br />
<tr><td><br />
I think the possibility to setup and use a socket connection for client-server communications would be a great improvement for Firefox to use it in Web2.0 / intranet-webapplications.<br><br />
I know it's already possible, but it requires 'signed/secure javascript' through a plugin to deploy the possibilities, but it would (and should) be a lot easier if a could just setup a javascript object (eg:<br />
<br />
mySocket = new SocketClient("tcp://domain.com/application");<br />
mySocket.onData = processReponse();<br />
mySocket.connect();<br />
<br />
)<br />
<br />
If you look at the flash player for example, it is used a lot in all kinds of applications, not just gaming or chatting, but it's also penetrating the intranet-applications business.<br />
</td><td>n/a</td></tr><br />
<br />
<tr><td><br />
HTTP Sniffer.<br />
<br />
Have a HTTP Sniffer, where you see what exactly is transmitted, which POST / GET parameter, cookies, loading times etc. Something like httpwatch, see link. That's why I have to start IE in regular intverals.<br />
</td><td><br />
http://www.httpwatch.com/<br />
</td></tr><br />
<br />
</table><br />
<br />
<br />
* [http://forums.mozillazine.org/viewforum.php?f=8 Firefox Features - MZForums]<br />
* [http://wiki.mozilla.org/Firefox3/Gecko_Feature_List Gecko 1.9 Feature List]</div>DJ Doenahttps://wiki.mozilla.org/index.php?title=User:DJ_Doena/Tab_Features&diff=36972User:DJ Doena/Tab Features2006-10-16T05:57:46Z<p>DJ Doena: </p>
<hr />
<div>== Multi-Line Tabs ==<br />
<br />
Tabs shouldn't be smaller than a defined width because then the tab headers become unreadable. If this width is to fall short a second row should be opened. Like a multi-line Windows taskbar.<br />
<br />
== "New Tab" Button in Tabbar ==<br />
With the "Tabbrowser Preferences" extension it is possible to have a "new tab" button at the begin of the tab bar. Firefox itself has such a button, too. But one cannot drag it onto the tabbar itself.<br />
<br />
== "Open Link in New Tab" should remain history ==<br />
If I mid-click a link then it opens in a new tab. Unfortunately the history is lost and the opened link is the "first one". The history should be preserved.</div>DJ Doena