MozillaWiki - User contributions [en]

Firefox/Feature Brainstorming:Other or Uncategorized

2007-01-27T05:34:44Z

Carutsu:

{{FeatureBrainstorming}}

== Widgets ==
* In my opinion, that's the only feature lacking in Firefox to create first-quality "mozlets", similar to the Opera's widgets or Safari's dashboard (if not better, since Opera's widget goes nowhere farther than using XShape).

== Editions ==
* Create several Editions for example standard edition, web developer edition, low memory edition, kid's edition, or even google edition
*and maybe even a simple/lite version(extensions and themes are not installable)

== "Open page in another browser" option ==
* Simple, useful, and easy to implement.
** Already exists in the form of Launchy. I don't think that Firefox should, by default, give an option to use another browser. I know Firefox isn't 'anti-IE' or 'anti-Opera', ''but it is'' 'pro-Firefox'. This would be admitting that other browsers are superior to Firefox, and you should use them if things happen, rather than fix it, ask for help, or use Firefox anyway. (on IE-only sites, by using User Agent Switcher)

== Conditional Comments ==
Allow users to add CSS filters for version compatibility that doesn't rely on a CSS rule being implemented. Arguably, this is the unofficial standard for dealing with Internet Explorer bugs and it would be nice to have a simple interface for doing this with any browser (just in case things change later on down the line). The syntax should be about the same, so something like  would be appropriate.

; Comments
That's a very good idea! It could prevent use of CSS hacks in future. Opera could do that too. --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Glow Text ==
Allows text to Glow when the glow HTML command is used, such as in IE7.

== Gradient backgrounds ==
Make a process for implementing gradient backgrounds in a table or web page, such as in IE.

== Page autorefresh ==
Create a new "Automatically page refresh" submenu in page's content menu (and inside "In this frame" submenu). It might contain items like "Stop autorefresh", "5 seconds", "10 seconds", "1 minute", "5 minutes", "Custom...". The page should be automatically refreshed untill "Stop autorefresh" selected or user navigated away from the page. In case of page was loaded by 'POST' command the new item should be "disabled" or user might be asked about "repost data every time".
:There is already a couple of extensions for that.

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

; References
* [http://en.wikipedia.org/wiki/Synesthesia Synesthesia] (wikipedia)
* [https://addons.mozilla.org/firefox/3810/ ChromaTabs] (Google.co.uk happens to be yellowish-orange) --[[User:Greg K Nicholson|Greg K Nicholson]]

; Commentary
: It shouldn't be user picked, but extracted in some ways from the URL domain and optionally changed by a meta tag in the XHTML. This is important to make it a useful feature for both sites and communications (on other computers, the same site will have the same colour). Also it doesn't overload unneeded customization.

== Propietary Anchor mode ==
Many pages don't have anchors so linking to Content that is somewhere on the page can be a pain. Make possible custom anchors like this would make firefox scroll 0pixel to left and 555pixel down:

url#custom(0,555)

This make firefox scroll to the 5th H1 element on the page and highlight it decently:

url#custom(h1/5)

; References
* [http://www.w3.org/TR/xptr-framework/ XPTR framework]

; Commentary
* Pixels are unsafe (depending on fonts, zooming etc.)
* This looks like reinventing the wheel. use xpath instead?
* This implies support for XPointer

== Smooth vs Raw Page Transitions ==
There isn't any *good* point to have the previous page "visible but unusable" until the new page starts rendering, a block a time. This is aesthetically awful and without any useful gain at the UI level.

=== Details & Commentary ===
'''Smooth Page Transition''': when someone clicks on a link, the page will slightly fade out, indicating that it is refreshing until the new page is fully ready, when a smooth (really '''fast''' crossfade <0.5sec, maybe). On the page there should be some form of interaction that could allow to see - and browse, and use - the previous page until the new is fully loaded AND the possibility to switch to the new one, displaying it a block a time.
* If implementing this, Firefox could adhere to some of IE page/site transition definitions from HTTP response or meta http-equiv headers.
** Please no: this is a step back in the past using BAD transitions that were just annoying. This feature, as stated, is conceptually '''DIFFERENT''' and must NOT be assimilated with the IE page transitions.
* The point here is to make the navigation softer and nicer for everyone (cool-factor), not only occasional user, and behaving more like an offline app. The '''"freeze page, load the other one block a time" is obsolete''' and should be improved into a new form of page transition: unobtrusive, aesthetically pleasant and without drawbacks (on slow connection, seeing the page loading a block a time is useful, don't avoid it if needed).
* To be clear: this is COMPLETELY different from the "page transitions" concept seen before on some browsers as site behaviour. This should be an integrated feature, well balanced and ''without annoying drawbacks''. Also, this should be default but disabled.
* The interaction could be:
** On a full-page location refresh (i.e. non javascript) the current page should be lightly dimmed until the new page is ready.
** When the new page is ready, a fast crossfade should display it.
** If the page loads slowly, clicking on Forward (a button not really used since now) will show the page loading a block a time, like now.
** If the user clicks on the dimmed "old" page, it could interact with it until the new page is ready (and faded in). Any click event of course blocks the page load (and the Forward button will turn disabled).

; References
* [http://wiki.mozilla.org/User_talk:Folletto#Smooth_Page_Transitions Smooth Page Transitions]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=zombie Bug zombie] is relevant (--[[User:Greg K Nicholson|Greg K Nicholson]])

== Mouse gestures ==
Allow the user to use mouse gestures (like right click followed by left click for 'back' etc)...

; References
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]
* [https://addons.mozilla.org/search.php?q=Rocker&app=firefox Plugins providing this functionality]

== Link navigation using arrow keys ==
* Using shift+arrowKey, the selection "hovers" to the nearest link in that direction
* With this feature remote controls can be configured to navigate pages
* Same as Opera feature

== Remote Control ==
Support for Red/Green/Yellow/Blue remote control buttons
* The ability to configure keyboard shortcuts to select HTML elements that have the accesskey attribute in the format: accesskey="{red}" | accesskey="{green}" | accesskey="{yellow}" | accesskey="{blue}"
* e.g. configure Alt-F1 to select the element with accesskey="{red}", Alt-F2 selects element with accesskey="{green}" etc
* With this feature the RGYB buttons of remote controls can be configured to select links
* This would make Firefox compatible with the Netgem iPlayer facility

== Scripting ==
* 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.
** Support for regular expressions so that pages with broken URLs can be fixed, HTML can be converted to another format, etc.

; References
* [http://greasemonkey.mozdev.org/ Greasemonkey]

== Patching display ==
Let the user configure the display of their page and 'patch' them.

For exemple, change some image, text disposition or even the whole design of the page using regular expression. (Maybe witch a WYGIWYS editor-like to be more user friendly ?)

(I used a while ago an adblock proxy who do that, but it's really slow, whith something directly coded in firefox, this will be great ! No more forum witch crap animated smilets if we can change them on client side)

I think about a way that users can themselfs modify a whole page, and submit their 'patchs' to a centralized server.

When an other user navigate on the page, he can use a button on the navigation page to switch between the different patches submitted by other people and vote for them.

So for one site, we will probably had a lot of version : Ad-free, Alternative design
(Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

== JavaScript Performance ==
JavaScript engine is too slow. When a script on page is become unresponsive - Firefox hangs, until window, proposing to stop that script appears. Enclosing enhancements are good, but functionality and quality are the main thing, we must to follow.

== PDF Reader ==
Make a quick-opening pdf reader, just for text. In other case, run adobe or similar

== Rename tabs ==
It would be useful if end users could rename tabs after opening. Oftentimes, pages with wildly disparate content have similar headings, particularly if browsing forums or newspages or anything where a lot of content comes from a single site. If you could take six tabs all saying "CNN.COM - YOUR SOURCE F..." and change each of them to the subject of the page, it would greatly simplify things.

It really does come up quite often, even if you use separate windows instead of tabs, that the data listed in the browser summary field is basically useless due to excessively long page titles. This does sound like a good feature.

== Incorporate Wizz RSS ==
To incorporate the Wizz RSS. It becomes it native of the program.

== Web services integration ==
Automatically create a web services test form by inspecting a URL to a WSDL file. For comparison, ASP.NET can do this by browsing to a web services URL like foo.asmx?wsdl

== Web mail integration ==
Following Firefox 2 support for online web feed readers, it could be extended to web mail services like Yahoo! Mail, Hotmail and Gmail at least. Users should be able to select one or more web mail providers and set a default or just keep the default stand alone email client. The idea is not to develop a complete email client but to provide minimum integration:
* New mail notification through an alert a la "Downloads complete"
* mailto: handling
* File/Send link... overlay
* More providers can be added with preferences for compose URL and new mail XPath

== Email pseudo-url ==
Presently the mailto: pseudo url simply opens up a mail client. In the old Netscape/Mozilla days, the mail client was part of the package, so it wasn't necessarily such an issue.
Perhaps Firefox could incorporate a lite smpt component which could actually send off data, perhaps as part of a form's action.

== Explorer files integrated ==
Firefox 3.0 should integrate a file explorer of your system, while having the same characteristics as a web page: Tabs, mouse gestures, bookmarks. etc.

== Explorer integration (Windows) ==
In Windows allow file system browsing (ie C:\windows), perhaps by calling on MSHTML APIs.
* Preferably using default file manager -open Koqueror in the current tab when a local directory path is entered

In Windows, allow Firefox to change global settings for preferred browser; not only changing preferred browser for files-types, but also to change what browser applications start when they want to access a webpage.

== Link Activation ==
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.
* Add option to pre-process Javascript (and Flash?) links - enable MMB/CTRL-click to open these in new tab, by tracking the target before obeying the command
* Improved functionality when opening embedded Windows Media Player video files.
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.
* 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.
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.
*Any link will open in a new tab if dragged in any direction rather than being clicked.
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back.
*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.
*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
*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.
* 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.
* An integrated prefetching mechanism (use free bandwith to load in background all the static pages linked from the page) - similar to Fasterfox plugin.
* After i click Shift + click of link i open a link in other window. Now Gecko focuses a loaded window after loading but it's very bad! I suggest to do not focus loaded windows after a loading page through "Shit + click of link". It puts off from browsing :(
* Same as the one above when reading email with several links: Every click on a link brings FF to focus. Better would be keeping FF in background so that one can read the whole mail undisturbed.
* Make an option that Ctrl+Alt+Click, or some other combination, that will open a "preview" of the like page in a "bubble" or some other form of preview.

; References
* [https://addons.mozilla.org/firefox/1269/ Fasterfox plugin]

== Link Context Menu ==
* Add a command to open selected text in a new tab/window.
* 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.
; References
* https://addons.mozilla.org/firefox/1472/

== Additional Mouse Interactivity ==
* Grabbing whitespace within the document act as grabbing the icon in the address bar. ie: it becomes the link. To avoid issues with selecting text make it a right click+drag as the trigger. This would make bookmarking easier, as well as open options for duplicating tabs without duplicating the history of the tab.
* Dragging links to whitespace opens the link in new tab or window. - SuperDragAndGo extention provides this.
* Highlighting text causes it to be treated as a link in all of it's functionality. If it is a valid, unformatted URL, go to that page. If it is text treat it as an "I'm feeling lucky Google search". Apply a max length of 256 characters to prevent shift+a+click overloading.
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object
* Opera has a nifty feature with it's Mouse Gestures when you visit an Apache Directory Index or a Gallery site, and a few other sites. When you are on the index, you can just "go forward" in an imaginary history and it will start with the first link. Continuing going forward, will result in the second link, third link, etc... And when you've seen them all - you're back at the Index page.

== Javascript Links ==
* 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.
; References
* See {{bug|55696}}

== Tab Refresh ==
* Allow to refresh Tabs automatically by a counter
** When a change is made to the page on a reload, the tab should change visually

== Independent tabs ==
* The main browser interface should be on a thread that MUST never stop responding (and have a bigger priority). Each tab, should have it's own thread used to fill it's content. If a web page from inside one tab stops responding (or takes too much to load - such as big pdf files or sites that use java - but not resticted to those) the tab should be coloured in a different way (and maybe some text: the web page is not responding). The user MUST be able to either stop , go back, or close the tab, even if the content is not responding. It's VERY anoying now if I open lots of tabs, and the last stops responding, I must close the browser. (true the session restoration is a good step, but it's only a workaround, not the real solution to the problem).

== Quick Top of page/Bottom of page ==
* 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.
* Duplicates Ctrl-Home / Ctrl-End functionality. Would an extra icon to do this be useful?

== Uploading Files ==
Auto-zip multiple files in upload dialog
* Implement multiple file selections in the upload dialog that automatically generates a archive (.zip) for easy transmissions of many files.
* After selecting multiple files a dialog shall appear that asks for the file name of the archive (to be transmitted, auto-naming already included) and confirms the archive type (.zip/.tar.gz/whatsoever)

== Support drag and drop files from OS into a text box / text area ==
* Dragging a file icon from an OS file browser window should drop the name of the file in the target text box. Main use would be for uploading files, but it can be convenient for any other case when a file name and path must be used. It would be a must-have for web-based Document Management Systems, like [http://www.egroupware.org eGroupWare's] DMS.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=50660 bug 50660] and [https://bugzilla.mozilla.org/show_bug.cgi?id=347178 bug 347178]
* [http://slashdot.org/comments.pl?sid=200759&cid=16438433 A comment on Slashdot that gives a nice example of the problem]
* [http://e-vertise.com/dragtext/feature.html What DragText does] in OS/2.

== Dynamic Font Support ==
Support dynamic font such as prf, eot or svg. Considering the huge advancements made in with SVG in the Firefox browser, I really can't see any excuse for NOT including this technology.

From a designer's point of view it makes just about the '''most''' amount of sense - with IE4 onwards supporting font embedding, gifting this technology to FF would just about cover 99% of browsers - the possibilities from a typography point of view are fantastic.
; References
* [http://www.laakshmi.com/aarre/wp/archives/36 this blog]

;Comments

No. Firefox should support dynamic FON, TTF and OTF fonts. --[[User:Alenonimo|Alenonimo]] 15:43, 27 October 2006 (PDT)

== Syntax Highlightning ==
* Devloper aware syntax highlightning
** No language includes these words &nbsp;, <th> and such. The spellchecker should know about symbols used by developers, bloggers and wikiwriters and not to highlight them as a syntax error at least.

== Linux compatibility ==
* Render embedded buttons with native GTK2 widgets
* 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!)
* 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.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].
* 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].

== Mac OS X compatibility ==
* Support Command-Option-F to select search toolbar (standard for Mac applications).
* Render embedded buttons with native Aqua widget
* Dragging favicon to bookmark bar: Expand bookmark folders for bookmark placement when hovering -- FF 1.X+ under other OS's have been able to do this.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=299185 bug #299185]
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=136524 bug #136524]

== Long term target ==
On a long term basis Mozilla has come to a cross-road. The current XUL technology can't be used on a PAD/Smart phone nor on an OLPC. Yet there's a need for such a browser/mailer and it's just a matter of time somebody starts such a project. But I'm sure if such a browser/mailer gets built, it will be ported to the ordinary desktops slowly starting to replace Mozilla. And since switching technologies isn't a task done in a few weeks this subject has to be taken care of ASAP.

IMO it's important for Mozilla to start a task force now to think about the long term future. The PDA/Smart phones are already on the market almost exclusively using IE/Outlook and the OLPC and other embedded devices is just on the brink. So the pressure of this task, to prevent Mozilla from lagging behind again, is imminent.

== Evaluating the future of XUL ==
* It's essential to first evaluate XUL in the light of new requirements, especially about new devices ranging from the OLPC to embedded devices.

== Evaluating possible alternatives ==
* Alternatives should be based on the cornerstone "runs anywhere". Possible is IMO only wxWidgets yet others like Java or .Net/Mono should be rated against XUL as well.

== More vs. Less ==
Well it seems like we could divide 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.

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 interested 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.

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.

== "Core Firefox" & "More Firefox" (Packaging options) ==
* 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:
** A Firefox "Core" with just essential features (based upon XULRunner...)
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".
* 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.
; References
* [http://wiki.mozilla.org/User_talk:Folletto#Firefox_Core_.2B_More Firefox Core + More]

; Commentary
: 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.

=== Extension packs ===
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.

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.

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.

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)

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.

I love the idea of official extensions! And I'd definately like the ability to strip down firefox to the core. This method of development and packageing gets my vote!

Perhaps the installer could be a bit more than just Core & More. You could for example have a check box for extra features, and another for web development tools. Each check box could be expanded to get individual extensions like no-script.

And of course the defaults will be well chosen.

The more functionality you add, the more words and submenus have to be created. And both is confusing for beginners and older folks. What is the difference between words, that seem to mean the same thing at first glance ? Do I have to understand "all these new words" like "javascript", "PlugIn" ? Keep in mind, not all of the users are like the Techies who develop !

Firefox already has all the necessary stuff. There must always be an easy way for "lightweight-users" to use firefox without getting confused about words, large submenus or confusing questions.

The more functions, the more words, the more confusion. Please, always offer an easy way for the non-techie user ... !

I agree that a much smaller (memory) footprint is needed (even on desktop systems), and love the extension pack idea. I'd like to also strongly suggest looking at the reason for the memory size with the current feature set - 225 MB with just 3 tabs open just seems like too much.

The subject of More vs. Less is quite interesting. A good starting point might be to ask "what recent features are being used?". In that vein, maybe one of the "pre-release" versions could be "instrumented" to count the features used and (with the permission of the user, of course) report back those. Another way might be to do a web crawl, and see what features are used by various "popular" web sites. As with ANY feature set, one should realize that "growing featureism" is a very slippery slope. I suspect that many web users would be content with the features of an older browser (say back to 1999) to do their work. Remember that each added "feature" involves code, and with any new code comes both bugs and vulnerabilities. The user community wants neither.

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!).

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.

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!

(removed further repetitive commentary here)

== Customizable extension sets ==
The ability for each user to create, save, install, and manage "feature (extension) sets".

== Rich Internet Application Support ==
There is an opportunity here to lead the way in supporting the growing number of DHTML- and Ajax-heavy applications and to provide the browser support needed to eliminate some of the drawbacks of these apps. In all cases a security model will be necessary, probably including some automated safeguards and some user confirmations.

=== Preloaded javascript libraries ===
* with AJAX large javascript libraries (e.g. "dojo.js") have to be downloaded which need a lot of time. It would be nice if such libraries could be downloaded local in the background and taken from this local store instead of downloaded from the web when referenced by a page. This would speed up any AJAX page considerably. Which libraries are handled this way may be configured in the "offline" settings.

=== Local filesystem access ===
* Allow pages to request access to the local filesystem or some subset thereof (for example, a user's home directory, desktop, or docs folder) for reading and/or writing.<br />
<b>Hear hear!</b> This would enable productivity applications on the web far beyond what we can do today. Mozilla has an opportunity to create a standard API for local storage.

=== Access to global UI elements (menubar, taskbar, panels...) ===
* Allow a page to request access to major OS-level global UI elements like a first-class application. Such elements include the Mac menubar, Windows taskbar, GNOME/KDE panels, Mac Dock, etc. Some are more important than others; for example, being able to write menus to the global menubar is far more important on the Mac platform than Dock access. However, Dock access on the Mac is probably more important than taskbar access on Windows because Windows will already have an entry for each browser window (though being able to define that window's icon would be nice so users can distinguish between "regular" browser windows and in-browser apps).

=== Enhanced clipboard integration ===
* Provide APIs to allow non-text apps to manipulate the system clipboard/pasteboard more.

=== More robust file uploads ===
* Provide single- and multi-select access to standard OS Open dialogs for opening/uploading files. Include an upload manager for asynchronous uploads. Include functionality to resume interrupted uploads. For apps that store data, combine with local filesystem access to allow easy setup of sites that keep local and remote data seamlessly synchronized.

:; Commentary
:: A standardized synchronization protocol would really help on this one. Why does every photo site need to make their own bulk uploader? A sync protocol could send the sha1 of the files in the local directory tree to the server and then let server request upload of the files that it is missing. Even better, make this a two way sync protocol.

== An alternative view of the web browser ==
* Firefox as a new kind of desktop manager.
* Active front end.
; References
* [[User:Anonymous42|Some thoughts]]

== Enabeling new Top-Level-Domains (TLDs) on browser basis ==
* Top-Level-Domains for regions, cities and others
* Top-Level-Domains with IDN characters

The ICANN process for getting approval for a new TLD is quite slow and very stressful for TLD applicant. Making new and by ICANN not yet approved TLDs available could help to foster the development of the DNS. Firefox could easily enable lots of new TLDs and thereby give regional, cultural, linguistic or ethnic communities the opportunity to present themselves by an own identifier. Not to split up the Internet there can be only domains at those TLDs available for which the community indicates to apply at ICANN for an official approval of their TLD.

; References
* [[User:Dotzone|New Top-Level-Domains]]

== Annotations ==
I think it would be really great if there would be enhanced possibilities of graphical marks. It's tough to explain. I think of an complicated scientific text. If I print such a text. I highlight some words, cross other chapters out, add some notes. That's the big advantage of printing a page. If I could mark within a browser wouldn't have to print the page. I could work on screen.

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

== Offline browsing ==
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.

== Thunderbird in a tab ==
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.
== All Mozilla applications in a tab ? ==
Why not opening FileZilla, ChatZilla, etc... in a tab : it's kind of firefox suite ... but the programs are installed separately to avoid one heavy program and get several light ones. Firefox could become an interface for any Mozilla program installed by opening it in a tab.

== Bookmark behaviour ==
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.)

; Comments

Firefox should Import/Export with more formats. XBEL, xFolk, OPML or even create a new one. Support for tags would be cool too. --[[User:Alenonimo|Alenonimo]] 15:48, 27 October 2006 (PDT)

== Socket connection ==
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>
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, like so:

mySocket = new SocketClient("tcp://domain.com/application");
mySocket.onData = processReponse();
mySocket.connect();

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.

== HTTP Sniffer ==
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.
; References
* http://www.httpwatch.com/
* http://tamperdata.mozdev.org/
; Commentary
: Should this functionality really be in the browser itself, when there are things like [http://www.parosproxy.org/index.shtml Paros Web Proxy]?
: Sometimes we are required to use a different proxy (e.g. in corporate networks). Besides, when using HTTPS and gzip compression of pages, the external sniffer will not show the contents of the page. It would be better to sniff by means of the browser itself (both for outgoing requests and for incoming pages, when they are about to be encoded or have already been decoded, respectively, ''by browser''), and to be able to manage these requests in the browser and/or extensions (allow, deny, save, redirect etc.).

== Security ==
* I see many attacks upcoming, which manipulate the DOM-tree inside the browser, altering transactions in banking-systems a.s.o.
* What i wish for Firefox is, to have ONLY signed extensions!
* I want a default block of all extensions to manipulate SSL-protected sites.
This security-feature will be a boost for the usage of Firefox, because all banks will promote FF.

== Flexible table element selection and copy ==
For example, select and copy a column (or columns) from a html table
* Press Ctrl/Cmd when selecting

== User dictionaries ==
I have an existing "user.dic" dictionary, and a couple of specialist dictionaries ("avifauna.dic", "lepidoptera.dic"). They are used by several of my apps, including my e-mail client (Turnpike) and various MS Office apps. I should be able to direct FF to use the former as its dictionary to which new words are added, and to check against all of them when spell-checking.

Also, when the word I'm spell checking is at the bottom of the window, then the suggested replacements should be at the bottom of the context menu.

== Various ==
* Move all MPL code to GPL

== Better Support for Web Apps ==
See my [[User_talk:FunTomas|article]] on that topic.

==Memory management==
Try to minimize the memory usage of Firefox. May be we can have one feature (one button click), which enables the browser to run with minimum feature and there by reducing the memory usage.

As an additional memory usage related feature a (on/off switchable) display of memory usage in each browsertab would be interesting (not only for developers). It may be colorcoded as well to see instantaniously, which tab causes the memory usage spike. Telling me for instance to close the tab with the still running buggy JS on that not so well coded Web2.0-page I left open in the background...

==Save web pages in pdf or odt format==
Allow save html pages in pdf or odt format.

==Spell-check support for multiple languages==
I'm doing a doctorate in a French university, on databases, and I'm Romanian. This means that I mail/post/write things in French, English and Romanian all the time, sometimes even in the same text box. I'd like a way to tell FF what languages I'm likely to use so that it can use those dictionaries at the same time. If it's really smart, it should also detect what language each sentence/paragraph/text-box is after a few words and restrict the dictionary automatically to that language. And, perhaps, it should use a different underline color for words that are not in the "current language" dictionary but are in another "in use" dictionary, for cases of [http://en.wikipedia.org/wiki/Code-switching code-switching] (it happens very often when discussing computer-related things in another language than English).

==Restart==
Restart the firefox browser, but restore the session. So that you can get extensions working without losing all your tabs etc.

; Comments

That's implemented already. Just change the Home Page settings to load your previous session. --[[User:Alenonimo|Alenonimo]] 15:49, 27 October 2006 (PDT)

==Built-in Flash Support==
Forget about SVG and Canvas, build an open source Flash implementation into the browser and get rid of the plugin. You could start from gnash http://www.gnu.org/software/gnash/ Use the MIT license and give the source code to Microsoft, they might even help write it.

==PopUp Blocker==
The popup blocker need not have the "Options" button at the end. Instead, clicking anywhere on the popup blocker, we should be able to bring the pop-up blocker options menu (ala IE). Also, add the "Temporarily allow pop-up for this page" option to the main options menu.

==CPU usage when minimized==
Stop flash animations and other CPU power stealers when Firefox window is not selected or is minimized, and for no selected tabs.

==New User Agent string layout==
The actual User Agent strings are confusing and should be deprecated. Firefox 3 could use an User Agent strings simmilar to Opera. Ex:

Firefox/3.0 (Windows NT 5.0; U; pt-BR)

Or yet:

Gecko/1.9 (Windows XP; pt-BR) Firefox 3.0

--[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

==Process Isolation for each Web Site==
With web browsers becoming the de facto application launchers in desktops and several web applications (e.g. gmail) being used continuously, it is very important that an ill-behaved web site is not able to crash the entire web environment. At most, it should crash itself, without affecting the other web sites showing on other windows/tabs or requiring firefox to restart.
[[User:Mrcgran|Mrcgran]] 19:34, 27 October 2006 (PDT)

==Independent sessions per tab/window==
Currently, any web browser I am aware of shares sessions across all instances of the browser (windows/tabs). It would be nice to separate a window or tab and create a new session within it. This would allow you to have, say, two different GMail accounts logged-in at the same time without needing to have two different web browsers.

==Won't comeback button==
In order to minimize the "leak" of memory that the "quick back" and "quick forward" features use we should have an button "I won't come back" this will close the tab and unload everything it had in the memory so that if you close every tab the memory usage will drop back the their 30-40MB that are used on start. Also we should allow the user to define this as his/her normal closing button (so if you close the tab and have that option checked will unload automatically the memory).

==Easier tildes, ñ and Cyrillic characters==
I usually use the ZombieKeys for that, however in some text areas I can't use it, and it seems that the creator of that extension will no longer update it, so, we should have it "by default" (sadly ala IE7). This could be an extra extension (also might be an extension for Cyrillic characters) because I agree with the core/more Firefox movement.

==Page split==
Add ability to split Web pages display.
Web pages may be splited horizontally as spreadsheets does. This feature should include two panels display, each one with its own scrollbar on the right and ability to display result of a link clicked on one panel on the other panel as long as link refers to the same page.
This may be very useful for long pages with multiples internal links and especially for pages containing a table of content on the top (as this one :-) ). This way we could keep TOC on the top panel and navigate through content on the bottom panel.

==Export/Import config to/from XML==
Add ability to export selected config elements (arrived at by running a search within the about:config page) to a file in XML format. The file should have some version info in the header. Each record should optionally contain an extra field for a URL that will point to description of the config element. It should be possible to import the XML back after editing.

==Easy Mechanism/API for changing/adding client-side scripting language dynamically==
Javascript is the default scripting language in Firefox, but javascript is not the best language to use in every problem domain, due to its nature or to legacy code.

Therefore, Firefox should add an easy (standard/documented with examples) mechanism/API to allow developers to plug in new scripting languages (such as python, haskell, lua, ruby etc) with full access to standardized DOM/CSS, and to users to download them (in the form of some add-on/plugin) and switch them on on-the-fly without resetting the browser.

With the continuous trend in executing client-side web applications, this would be a boost to using Firefox as an OS-agnostic desktop application provider environment. The scripting language name should be as easy to choose as putting the name inside the [script language="[name]"] tag attribute. It should be possible to use several scripting languages on the same web page.

Microsoft Internet Explorer already implements something on these lines with their ScriptHost API, that allows any script engine to be hosted in Internet Explorer (there's even a HaskellScript language that uses this API on top of IScript, a COM interface). Why not implement some similar IScript interface on top of XPCOM?
[[User:Mrcgran|Mrcgran]] 23:42, 4 November 2006 (PST)

==Support for the MNG format==
The MNG format would be an alternative to (and intended to replace) the old GIF format, which is used really often (eg: boards' smileys, animated buttons, etc ...). It's lack of Alpha channel support is really annoying when you start to create animations not to be used on only one colored background.

The MNG format, which is based on the PNG format, has many features that the popular GIF format does not. MNG supports alpha channel and animation, object or sprite-based approach to animation, nested loops for complex animations, better compression than the GIF format, integration of both PNG and JPEG-based ("JNG") images, support for transparent JPEG images, but it's not yet a standard in current web browsers. This format needs to be helped in becoming one, but if there was only Microsoft who could do sommething by intergrating the format in IE, we could wait for a long time. Thus, I think Firefox should follow Konkeror in the integration of this format to accelerate the "standardization" of MNG and the "elimination" of GIF, to help the World Wide Web in becoming more user friendly. Not supporting new and better media/technology for viewing and experiencing the web prevents its progression and stagnates it's growth.

; References
* http://www.libpng.org/pub/mng/
* http://en.wikipedia.org/wiki/MNG
* http://en.wikipedia.org/wiki/Gif

:I'm afraid those were supported by the browser, but were deprecated because it's low support by the Web.
:I don't think that it will be supported cause According to [http://mozilla.wikia.com/wiki/APNG_vs_MNG Unofficial Mozilla wiki] Mozilla decided to use APNG over MNG even though APNG violates section 5.2 of the PNG specifications. this was discussed at [https://bugzilla.mozilla.org/show_bug.cgi?id=257197 BUG 257197]
::Nevertheless i think that if Firefox adopts it the popularity of MNG will grow. We should support it, firefox then would be the most standardized browser, like Konqueror, and right now it's impossible to insert a decent animation (gif sucks at the so used degrades) (as a side note very good that Firefox support alpha channels in jpg unfortunately i can't use them!, over here (Mexico) IE is in the 99.999% of the machines).

==Save page independently==
Option to save page into all-in-one html. Images can be included with data URL-s, javascript and css can be included to page naturally. Flash, java and others are more complicated, but in first step these can be ignored...

<link src="my.css" ...> will be <style>...content of my.css...</style> and <script src="my.js" ... /> will be <script>...content of my.js...</script>. Images will have src="data,..."

==Spatial navigation==
Please, support by default spatial navigation.
References:
* http://www.mozilla.org/access/keyboard/snav/
* http://www.opera.com/support/tutorials/nomouse/#nav

==Favourite web pages performance==
I would like to have a macro to open my favourite coffee morning web pages in a special way. Now, if i command to open simultaneously 30 web pages that i use to visit i have obviously many performance problems. What i propose is to have 2 or 4 web pages loaded (a visible window of 4 web pages) that i can cycle like a powerpoint presentation by all over my 30 web pages as i close one. In this way a have only 4 slices open but i can continue with my non seen web pages. In this way it would be good if i could go forward and backward in the macro list.

Like slices in Powerpoint

==Clipping extra information==
This is a function that can also improve the performance. Firefox could check for some frequently visited web pages extra information from the user. The extra information could be "mark from here as read" "I like this paragraph" and so on. This context information is very useful since the web browser can use this to avoid load information repeated. It would be nice if the browser could understand the information and filter the same news or easily the same words in the news and remove it from the loading task. Other information like "I like this paragraph" could be shared by the community or simple with the web page that we read. There is a extension clipping or something like this that try this concept but in a private way.

Extra information button about the web page

==Mouse cursor variation==
* Visual feedback in the form of different mouse cursor appearances informs the user whether a link will open in the current tab/window or in a new tab/window. Just as an example, when a cursor hovers over a new window link, the cursor becomes a "hand" and a mini plus sign attached to it, sort of like the green plus sign you see when you option-click drag a Finder file in OS X.

==Page Info==
* "Page Info" dialog should have links on Links tab clickable, saveable, bookmarkable, etc, like any other links. Media in the same dialogue at Media tab should be clickable etc. Probably it would be reasonable to attach a usual right-click context menu.

==Toolbar icons in customise' view==
*The ability to sort icons in the "toolbar " / "customise" view, alpahbetically, or "newest first", would be beneficial. [[User:Pigsonthewing|Pigsonthewing]] 11:07, 4 January 2007 (PST)

==MAC version: Please be Cocoa ==
*I don't know how feasible this is, but if Firefox were native Cocoa on the Mac, we could take advantage of cool things the Mac has to offer like: SERVICES
I don't know how many times I reflexively go to Services to save a snippet or something and forget that Firefox isn't Cocoa.

=="Smart" scrolling ("Pg Dn" and "Pg Up" i mean) ==
Whit the growing popularity of the blogs reading a bunch of articles might be hard, what if Firefox might recognize where is the next header and if i press, lets say Control+Pg Dn it jumps to the next header, that way i can cycle through the headers of my the blog or the news.

Firefox/Feature Brainstorming:Other or Uncategorized

2007-01-27T05:27:35Z

Carutsu: /* Support for the MNG format */

Firefox/Feature Brainstorming:Other or Uncategorized

2006-11-06T22:36:44Z

Carutsu: /* Support for the MNG format */

{{FeatureBrainstorming}}

== Widgets ==
* In my opinion, that's the only feature lacking in Firefox to create first-quality "mozlets", similar to the Opera's widgets or Safari's dashboard (if not better, since Opera's widget goes nowhere farther than using XShape).

== Editions ==
* Create several Editions for example standard edition, web developer edition, low memory edition, kid's edition, or even google edition

== "Open page in another browser" option ==
* Simple, useful, and easy to implement.

== Conditional Comments ==
Allow users to add CSS filters for version compatibility that doesn't rely on a CSS rule being implemented. Arguably, this is the unofficial standard for dealing with Internet Explorer bugs and it would be nice to have a simple interface for doing this with any browser (just in case things change later on down the line). The syntax should be about the same, so something like  would be appropriate.

; Comments
That's a very good idea! It could prevent use of CSS hacks in future. Opera could do that too. --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Glow Text ==
Allows text to Glow when the glow HTML command is used, such as in IE7.

== Page autorefresh ==
Create a new "Automatically page refresh" submenu in page's content menu (and inside "In this frame" submenu). It might contain items like "Stop autorefresh", "5 seconds", "10 seconds", "1 minute", "5 minutes", "Custom...". The page should be automatically refreshed untill "Stop autorefresh" selected or user navigated away from the page. In case of page was loaded by 'POST' command the new item should be "disabled" or user might be asked about "repost data every time".
:There is already a couple of extensions for that.

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

; References
* [http://en.wikipedia.org/wiki/Synesthesia Synesthesia] (wikipedia)

; Commentary
: It shouldn't be user picked, but extracted in some ways from the URL domain and optionally changed by a meta tag in the XHTML. This is important to make it a useful feature for both sites and communications (on other computers, the same site will have the same colour). Also it doesn't overload unneeded customization.

== Propietary Anchor mode ==
Many pages don't have anchors so linking to Content that is somewhere on the page can be a pain. Make possible custom anchors like this would make firefox scroll 0pixel to left and 555pixel down:

url#custom(0,555)

This make firefox scroll to the 5th H1 element on the page and highlight it decently:

url#custom(h1/5)

; References
* [http://www.w3.org/TR/xptr-framework/ XPTR framework]

; Commentary
* Pixels are unsafe (depending on fonts, zooming etc.)
* This looks like reinventing the wheel. use xpath instead?
* This implies support for XPointer

== Smooth vs Raw Page Transitions ==
There isn't any *good* point to have the previous page "visible but unusable" until the new page starts rendering, a block a time. This is aesthetically awful and without any useful gain at the UI level.

=== Details & Commentary ===
'''Smooth Page Transition''': when someone clicks on a link, the page will slightly fade out, indicating that it is refreshing until the new page is fully ready, when a smooth (really '''fast''' crossfade <0.5sec, maybe). On the page there should be some form of interaction that could allow to see - and browse, and use - the previous page until the new is fully loaded AND the possibility to switch to the new one, displaying it a block a time.
* If implementing this, Firefox could adhere to some of IE page/site transition definitions from HTTP response or meta http-equiv headers.
** Please no: this is a step back in the past using BAD transitions that were just annoying. This feature, as stated, is conceptually '''DIFFERENT''' and must NOT be assimilated with the IE page transitions.
* The point here is to make the navigation softer and nicer for everyone (cool-factor), not only occasional user, and behaving more like an offline app. The '''"freeze page, load the other one block a time" is obsolete''' and should be improved into a new form of page transition: unobtrusive, aesthetically pleasant and without drawbacks (on slow connection, seeing the page loading a block a time is useful, don't avoid it if needed).
* To be clear: this is COMPLETELY different from the "page transitions" concept seen before on some browsers as site behaviour. This should be an integrated feature, well balanced and ''without annoying drawbacks''. Also, this should be default but disabled.
* The interaction could be:
** On a full-page location refresh (i.e. non javascript) the current page should be lightly dimmed until the new page is ready.
** When the new page is ready, a fast crossfade should display it.
** If the page loads slowly, clicking on Forward (a button not really used since now) will show the page loading a block a time, like now.
** If the user clicks on the dimmed "old" page, it could interact with it until the new page is ready (and faded in). Any click event of course blocks the page load (and the Forward button will turn disabled).

; References
* [http://wiki.mozilla.org/User_talk:Folletto#Smooth_Page_Transitions Smooth Page Transitions]

== Mouse gestures ==
Allow the user to use mouse gestures (like right click followed by left click for 'back' etc)...

; References
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]
* [https://addons.mozilla.org/search.php?q=Rocker&app=firefox Plugins providing this functionality]

== Link navigation using arrow keys ==
* Using shift+arrowKey, the selection "hovers" to the nearest link in that direction
* With this feature remote controls can be configured to navigate pages
* Same as Opera feature

== Remote Control ==
Support for Red/Green/Yellow/Blue remote control buttons
* The ability to configure keyboard shortcuts to select HTML elements that have the accesskey attribute in the format: accesskey="{red}" | accesskey="{green}" | accesskey="{yellow}" | accesskey="{blue}"
* e.g. configure Alt-F1 to select the element with accesskey="{red}", Alt-F2 selects element with accesskey="{green}" etc
* With this feature the RGYB buttons of remote controls can be configured to select links
* This would make Firefox compatible with the Netgem iPlayer facility

== Scripting ==
* 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.
** Support for regular expressions so that pages with broken URLs can be fixed, HTML can be converted to another format, etc.

; References
* [http://greasemonkey.mozdev.org/ Greasemonkey]

== Patching display ==
Let the user configure the display of their page and 'patch' them.

For exemple, change some image, text disposition or even the whole design of the page using regular expression. (Maybe witch a WYGIWYS editor-like to be more user friendly ?)

(I used a while ago an adblock proxy who do that, but it's really slow, whith something directly coded in firefox, this will be great ! No more forum witch crap animated smilets if we can change them on client side)

I think about a way that users can themselfs modify a whole page, and submit their 'patchs' to a centralized server.

When an other user navigate on the page, he can use a button on the navigation page to switch between the different patches submitted by other people and vote for them.

So for one site, we will probably had a lot of version : Ad-free, Alternative design
(Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

== JavaScript Performance ==
JavaScript engine is too slow. When a script on page is become unresponsive - Firefox hangs, until window, proposing to stop that script appears. Enclosing enhancements are good, but functionality and quality are the main thing, we must to follow.

== PDF Reader ==
Make a quick-opening pdf reader, just for text. In other case, run adobe or similar

== Rename tabs ==
It would be useful if end users could rename tabs after opening. Oftentimes, pages with wildly disparate content have similar headings, particularly if browsing forums or newspages or anything where a lot of content comes from a single site. If you could take six tabs all saying "CNN.COM - YOUR SOURCE F..." and change each of them to the subject of the page, it would greatly simplify things.

It really does come up quite often, even if you use separate windows instead of tabs, that the data listed in the browser summary field is basically useless due to excessively long page titles. This does sound like a good feature.

''Note:'' (Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

''Note:'' Done and done.

== Incorporate Wizz RSS ==
To incorporate the Wizz RSS. It becomes it native of the program.

== ActiveX ==
* Implement full ActiveX support
** including optional support via WINE under Linux

;Comments
No way! --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Web services integration ==
Automatically create a web services test form by inspecting a URL to a WSDL file. For comparison, ASP.NET can do this by browsing to a web services URL like foo.asmx?wsdl

== Web mail integration ==
Following Firefox 2 support for online web feed readers, it could be extended to web mail services like Yahoo! Mail, Hotmail and Gmail at least. Users should be able to select one or more web mail providers and set a default or just keep the default stand alone email client. The idea is not to develop a complete email client but to provide minimum integration:
* New mail notification through an alert a la "Downloads complete"
* mailto: handling
* File/Send link... overlay
* More providers can be added with preferences for compose URL and new mail XPath

== Email pseudo-url ==
Presently the mailto: pseudo url simply opens up a mail client. In the old Netscape/Mozilla days, the mail client was part of the package, so it wasn't necessarily such an issue.
Perhaps Firefox could incorporate a lite smpt component which could actually send off data, perhaps as part of a form's action.

== Explorer files integrated ==
Firefox 3.0 should integrate a file explorer of your system, while having the same characteristics as a web page: Tabs, mouse gestures, bookmarks. etc.

== Explorer integration (Windows) ==
In Windows allow file system browsing (ie C:\windows), perhaps by calling on MSHTML APIs.
* Preferably using default file manager -open Koqueror in the current tab when a local directory path is entered

In Windows, allow Firefox to change global settings for preferred browser; not only changing preferred browser for files-types, but also to change what browser applications start when they want to access a webpage.

== Link Activation ==
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.
* Add option to pre-process Javascript (and Flash?) links - enable MMB/CTRL-click to open these in new tab, by tracking the target before obeying the command
* Improved functionality when opening embedded Windows Media Player video files.
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.
* 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.
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.
*Any link will open in a new tab if dragged in any direction rather than being clicked.
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back.
*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.
*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
*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.
* 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.
* An integrated prefetching mechanism (use free bandwith to load in background all the static pages linked from the page) - similar to Fasterfox plugin.
* After i click Shift + click of link i open a link in other window. Now Gecko focuses a loaded window after loading but it's very bad! I suggest to do not focus loaded windows after a loading page through "Shit + click of link". It puts off from browsing :(
* Same as the one above when reading email with several links: Every click on a link brings FF to focus. Better would be keeping FF in background so that one can read the whole mail undisturbed.
* Make an option that Ctrl+Alt+Click, or some other combination, that will open a "preview" of the like page in a "bubble" or some other form of preview.

; References
* [https://addons.mozilla.org/firefox/1269/ Fasterfox plugin]

== Link Context Menu ==
* Add a command to open selected text in a new tab/window.
* 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.
; References
* https://addons.mozilla.org/firefox/1472/

== Additional Mouse Interactivity ==
* Whitespace grabs within the document act as grabbing the icon in the address bar.
* Dragging links to whitespace opens the link in new tab or window
* Highlighting text causes it to be treated as a link in all of it's functionality, including the I'm feeling lucky Google search. If the highlighted text is a valid URL but not formated link (clickable) then open in new tab.
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object
* Opera has a nifty feature with it's Mouse Gestures when you visit an Apache Directory Index or a Gallery site, and a few other sites. When you are on the index, you can just "go forward" in an imaginary history and it will start with the first link. Continuing going forward, will result in the second link, third link, etc... And when you've seen them all - you're back at the Index page.

== Javascript Links ==
* 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.
; References
* See {{bug|55696}}

== Tab Refresh ==
* Allow to refresh Tabs automatically by a counter
** When a change is made to the page on a reload, the tab should change visually

== Independent tabs ==
* The main browser interface should be on a thread that MUST never stop responding (and have a bigger priority). Each tab, should have it's own thread used to fill it's content. If a web page from inside one tab stops responding (or takes too much to load - such as big pdf files or sites that use java - but not resticted to those) the tab should be coloured in a different way (and maybe some text: the web page is not responding). The user MUST be able to either stop , go back, or close the tab, even if the content is not responding. It's VERY anoying now if I open lots of tabs, and the last stops responding, I must close the browser. (true the session restoration is a good step, but it's only a workaround, not the real solution to the problem).

== Quick Top of page/Bottom of page ==
* 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.
* Duplicates Ctrl-Home / Ctrl-End functionality. Would an extra icon to do this be useful?

== Uploading Files ==
Auto-zip multiple files in upload dialog
* Implement multiple file selections in the upload dialog that automatically generates a archive (.zip) for easy transmissions of many files.
* After selecting multiple files a dialog shall appear that asks for the file name of the archive (to be transmitted, auto-naming already included) and confirms the archive type (.zip/.tar.gz/whatsoever)

== Support drag and drop files from OS into a text box / text area ==
* Dragging a file icon from an OS file browser window should drop the name of the file in the target text box. Main use would be for uploading files, but it can be convenient for any other case when a file name and path must be used. It would be a must-have for web-based Document Management Systems, like [http://www.egroupware.org eGroupWare's] DMS.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=50660 bug 50660] and [https://bugzilla.mozilla.org/show_bug.cgi?id=347178 bug 347178]
* [http://slashdot.org/comments.pl?sid=200759&cid=16438433 A comment on Slashdot that gives a nice example of the problem]
* [http://e-vertise.com/dragtext/feature.html What DragText does] in OS/2.

== Dynamic Font Support ==
Support dynamic font such as prf, eot or svg. Considering the huge advancements made in with SVG in the Firefox browser, I really can't see any excuse for NOT including this technology.

From a designer's point of view it makes just about the '''most''' amount of sense - with IE4 onwards supporting font embedding, gifting this technology to FF would just about cover 99% of browsers - the possibilities from a typography point of view are fantastic.
; References
* [http://www.laakshmi.com/aarre/wp/archives/36 this blog]

;Comments

No. Firefox should support dynamic FON, TTF and OTF fonts. --[[User:Alenonimo|Alenonimo]] 15:43, 27 October 2006 (PDT)

== Syntax Highlightning ==
* Devloper aware syntax highlightning
** No language includes these words &nbsp;, <th> and such. The spellchecker should know about symbols used by developers, bloggers and wikiwriters and not to highlight them as a syntax error at least.

== Linux compatibility ==
* Render embedded buttons with native GTK2 widgets
* 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!)
* 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.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].
* 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].

== Mac OS X compatibility ==
* Support Command-Option-F to select search toolbar (standard for Mac applications).
* Render embedded buttons with native Aqua widget
* Dragging favicon to bookmark bar: Expand bookmark folders for bookmark placement when hovering -- FF 1.X+ under other OS's have been able to do this.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=299185 bug #299185]
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=136524 bug #136524]

== Long term target ==
On a long term basis Mozilla has come to a cross-road. The current XUL technology can't be used on a PAD/Smart phone nor on an OLPC. Yet there's a need for such a browser/mailer and it's just a matter of time somebody starts such a project. But I'm sure if such a browser/mailer gets built, it will be ported to the ordinary desktops slowly starting to replace Mozilla. And since switching technologies isn't a task done in a few weeks this subject has to be taken care of ASAP.

IMO it's important for Mozilla to start a task force now to think about the long term future. The PDA/Smart phones are already on the market almost exclusively using IE/Outlook and the OLPC and other embedded devices is just on the brink. So the pressure of this task, to prevent Mozilla from lagging behind again, is imminent.

== Evaluating the future of XUL ==
* It's essential to first evaluate XUL in the light of new requirements, especially about new devices ranging from the OLPC to embedded devices.

== Evaluating possible alternatives ==
* Alternatives should be based on the cornerstone "runs anywhere". Possible is IMO only wxWidgets yet others like Java or .Net/Mono should be rated against XUL as well.

== More vs. Less ==
Well it seems like we could divide 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.

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 interested 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.

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.

== "Core Firefox" & "More Firefox" (Packaging options) ==
* 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:
** A Firefox "Core" with just essential features (based upon XULRunner...)
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".
* 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.
; References
* [http://wiki.mozilla.org/User_talk:Folletto#Firefox_Core_.2B_More Firefox Core + More]

; Commentary
: 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.

=== Extension packs ===
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.

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.

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.

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)

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.

I love the idea of official extensions! And I'd definately like the ability to strip down firefox to the core. This method of development and packageing gets my vote!

Perhaps the installer could be a bit more than just Core & More. You could for example have a check box for extra features, and another for web development tools. Each check box could be expanded to get individual extensions like no-script.

And of course the defaults will be well chosen.

The more functionality you add, the more words and submenus have to be created. And both is confusing for beginners and older folks. What is the difference between words, that seem to mean the same thing at first glance ? Do I have to understand "all these new words" like "javascript", "PlugIn" ? Keep in mind, not all of the users are like the Techies who develop !

Firefox already has all the necessary stuff. There must always be an easy way for "lightweight-users" to use firefox without getting confused about words, large submenus or confusing questions.

The more functions, the more words, the more confusion. Please, always offer an easy way for the non-techie user ... !

I agree that a much smaller (memory) footprint is needed (even on desktop systems), and love the extension pack idea. I'd like to also strongly suggest looking at the reason for the memory size with the current feature set - 225 MB with just 3 tabs open just seems like too much.

The subject of More vs. Less is quite interesting. A good starting point might be to ask "what recent features are being used?". In that vein, maybe one of the "pre-release" versions could be "instrumented" to count the features used and (with the permission of the user, of course) report back those. Another way might be to do a web crawl, and see what features are used by various "popular" web sites. As with ANY feature set, one should realize that "growing featureism" is a very slippery slope. I suspect that many web users would be content with the features of an older browser (say back to 1999) to do their work. Remember that each added "feature" involves code, and with any new code comes both bugs and vulnerabilities. The user community wants neither.

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!).

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.

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!

(removed further repetitive commentary here)

== Customizable extension sets ==
The ability for each user to create, save, install, and manage "feature (extension) sets".

== Rich Internet Application Support ==
There is an opportunity here to lead the way in supporting the growing number of DHTML- and Ajax-heavy applications and to provide the browser support needed to eliminate some of the drawbacks of these apps. In all cases a security model will be necessary, probably including some automated safeguards and some user confirmations.

=== Preloaded javascript libraries ===
* with AJAX large javascript libraries (e.g. "dojo.js") have to be downloaded which need a lot of time. It would be nice if such libraries could be downloaded local in the background and taken from this local store instead of downloaded from the web when referenced by a page. This would speed up any AJAX page considerably. Which libraries are handled this way may be configured in the "offline" settings.

=== Local filesystem access ===
* Allow pages to request access to the local filesystem or some subset thereof (for example, a user's home directory, desktop, or docs folder) for reading and/or writing.<br />
<b>Hear hear!</b> This would enable productivity applications on the web far beyond what we can do today. Mozilla has an opportunity to create a standard API for local storage.

=== Access to global UI elements (menubar, taskbar, panels...) ===
* Allow a page to request access to major OS-level global UI elements like a first-class application. Such elements include the Mac menubar, Windows taskbar, GNOME/KDE panels, Mac Dock, etc. Some are more important than others; for example, being able to write menus to the global menubar is far more important on the Mac platform than Dock access. However, Dock access on the Mac is probably more important than taskbar access on Windows because Windows will already have an entry for each browser window (though being able to define that window's icon would be nice so users can distinguish between "regular" browser windows and in-browser apps).

=== Enhanced clipboard integration ===
* Provide APIs to allow non-text apps to manipulate the system clipboard/pasteboard more.

=== More robust file uploads ===
* Provide single- and multi-select access to standard OS Open dialogs for opening/uploading files. Include an upload manager for asynchronous uploads. Include functionality to resume interrupted uploads. For apps that store data, combine with local filesystem access to allow easy setup of sites that keep local and remote data seamlessly synchronized.

:; Commentary
:: A standardized synchronization protocol would really help on this one. Why does every photo site need to make their own bulk uploader? A sync protocol could send the sha1 of the files in the local directory tree to the server and then let server request upload of the files that it is missing. Even better, make this a two way sync protocol.

== An alternative view of the web browser ==
* Firefox as a new kind of desktop manager.
* Active front end.
; References
* [[User:Anonymous42|Some thoughts]]

== Enabeling new Top-Level-Domains (TLDs) on browser basis ==
* Top-Level-Domains for regions, cities and others
* Top-Level-Domains with IDN characters

The ICANN process for getting approval for a new TLD is quite slow and very stressful for TLD applicant. Making new and by ICANN not yet approved TLDs available could help to foster the development of the DNS. Firefox could easily enable lots of new TLDs and thereby give regional, cultural, linguistic or ethnic communities the opportunity to present themselves by an own identifier. Not to split up the Internet there can be only domains at those TLDs available for which the community indicates to apply at ICANN for an official approval of their TLD.

; References
* [[User:Dotzone|New Top-Level-Domains]]

== Annotations ==
I think it would be really great if there would be enhanced possibilities of graphical marks. It's tough to explain. I think of an complicated scientific text. If I print such a text. I highlight some words, cross other chapters out, add some notes. That's the big advantage of printing a page. If I could mark within a browser wouldn't have to print the page. I could work on screen.

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

== Offline browsing ==
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.

== Thunderbird in a tab ==
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.
== All Mozilla applications in a tab ? ==
Why not opening FileZilla, ChatZilla, etc... in a tab : it's kind of firefox suite ... but the programs are installed separately to avoid one heavy program and get several light ones. Firefox could become an interface for any Mozilla program installed by opening it in a tab.

== Bookmark behaviour ==
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.)

; Comments

Firefox should Import/Export with more formats. XBEL, xFolk, OPML or even create a new one. Support for tags would be cool too. --[[User:Alenonimo|Alenonimo]] 15:48, 27 October 2006 (PDT)

== Socket connection ==
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>
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, like so:

mySocket = new SocketClient("tcp://domain.com/application");
mySocket.onData = processReponse();
mySocket.connect();

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.

== HTTP Sniffer ==
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.
; References
* http://www.httpwatch.com/
* http://tamperdata.mozdev.org/
; Commentary
: Should this functionality really be in the browser itself, when there are things like [http://www.parosproxy.org/index.shtml Paros Web Proxy]?
: Sometimes we are required to use a different proxy (e.g. in corporate networks). Besides, when using HTTPS and gzip compression of pages, the external sniffer will not show the contents of the page. It would be better to sniff by means of the browser itself (both for outgoing requests and for incoming pages, when they are about to be encoded or have already been decoded, respectively, ''by browser''), and to be able to manage these requests in the browser and/or extensions (allow, deny, save, redirect etc.).

== Security ==
* I see many attacks upcoming, which manipulate the DOM-tree inside the browser, altering transactions in banking-systems a.s.o.
* What i wish for Firefox is, to have ONLY signed extensions!
* I want a default block of all extensions to manipulate SSL-protected sites.
This security-feature will be a boost for the usage of Firefox, because all banks will promote FF.

== Flexible table element selection and copy ==
For example, select and copy a column (or columns) from a html table
* Press Ctrl/Cmd when selecting

== User dictionaries ==
I have an existing "user.dic" dictionary, and a couple of specialist dictionaries ("avifauna.dic", "lepidoptera.dic"). They are used by several of my apps, including my e-mail client (Turnpike) and various MS Office apps. I should be able to direct FF to use the former as its dictionary to which new words are added, and to check against all of them when spell-checking.

Also, when the word I'm spell checking is at the bottom of the window, then the suggested replacements should be at the bottom of the context menu.

== Various ==
* Move all MPL code to GPL

== Better Support for Web Apps ==
See my [[User_talk:FunTomas|article]] on that topic.

==Memory management==
Try to minimize the memory usage of Firefox. May be we can have one feature (one button click), which enables the browser to run with minimum feature and there by reducing the memory usage.

==Save web pages in pdf or odt format==
Allow save html pages in pdf or odt format.

==Spell-check support for multiple languages==
I'm doing a doctorate in a French university, on databases, and I'm Romanian. This means that I mail/post/write things in French, English and Romanian all the time, sometimes even in the same text box. I'd like a way to tell FF what languages I'm likely to use so that it can use those dictionaries at the same time. If it's really smart, it should also detect what language each sentence/paragraph/text-box is after a few words and restrict the dictionary automatically to that language. And, perhaps, it should use a different underline color for words that are not in the "current language" dictionary but are in another "in use" dictionary, for cases of [http://en.wikipedia.org/wiki/Code-switching code-switching] (it happens very often when discussing computer-related things in another language than English).

==Restart==
Restart the firefox browser, but restore the session. So that you can get extensions working without losing all your tabs etc.

; Comments

That's implemented already. Just change the Home Page settings to load your previous session. --[[User:Alenonimo|Alenonimo]] 15:49, 27 October 2006 (PDT)

==Built-in Flash Support==
Forget about SVG and Canvas, build an open source Flash implementation into the browser and get rid of the plugin. You could start from gnash http://www.gnu.org/software/gnash/ Use the MIT license and give the source code to Microsoft, they might even help write it.

==PopUp Blocker==
The popup blocker need not have the "Options" button at the end. Instead, clicking anywhere on the popup blocker, we should be able to bring the pop-up blocker options menu (ala IE). Also, add the "Temporarily allow pop-up for this page" option to the main options menu.

==CPU usage when minimized==
Stop flash animations and other CPU power stealers when Firefox window is not selected or is minimized, and for no selected tabs.

==New User Agent string layout==
The actual User Agent strings are confusing and should be deprecated. Firefox 3 could use an User Agent strings simmilar to Opera. Ex:

Firefox/3.0 (Windows NT 5.0; U; pt-BR)

Or yet:

Gecko/1.9 (Windows XP; pt-BR) Firefox 3.0

--[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

==Process Isolation for each Web Site==
With web browsers becoming the de facto application launchers in desktops and several web applications (e.g. gmail) being used continuously, it is very important that an ill-behaved web site is not able to crash the entire web environment. At most, it should crash itself, without affecting the other web sites showing on other windows/tabs or requiring firefox to restart.
[[User:Mrcgran|Mrcgran]] 19:34, 27 October 2006 (PDT)

==Independent sessions per tab/window==
Currently, any web browser I am aware of shares sessions across all instances of the browser (windows/tabs). It would be nice to separate a window or tab and create a new session within it. This would allow you to have, say, two different GMail accounts logged-in at the same time without needing to have two different web browsers.

==Won't comeback button==
In order to minimize the "leak" of memory that the "quick back" and "quick forward" features use we should have an button "I won't come back" this will close the tab and unload everything it had in the memory so that if you close every tab the memory usage will drop back the their 30-40MB that are used on start. Also we should allow the user to define this as his/her normal closing button (so if you close the tab and have that option checked will unload automatically the memory).

==Easier tildes, ñ and Cyrillic characters==
I usually use the ZombieKeys for that, however in some text areas I can't use it, and it seems that the creator of that extension will no longer update it, so, we should have it "by default" (sadly ala IE7). This could be an extra extension (also might be an extension for Cyrillic characters) because I agree with the core/more Firefox movement.

==Page split==
Add ability to split Web pages display.
Web pages may be splited horizontally as spreadsheets does. This feature should include two panels display, each one with its own scrollbar on the right and ability to display result of a link clicked on one panel on the other panel as long as link refers to the same page.
This may be very useful for long pages with multiples internal links and especially for pages containing a table of content on the top (as this one :-) ). This way we could keep TOC on the top panel and navigate through content on the bottom panel.

==Export/Import config to/from XML==
Add ability to export selected config elements (arrived at by running a search within the about:config page) to a file in XML format. The file should have some version info in the header. Each record should optionally contain an extra field for a URL that will point to description of the config element. It should be possible to import the XML back after editing.

==Easy Mechanism/API for changing/adding client-side scripting language dynamically==
Javascript is the default scripting language in Firefox, but javascript is not the best language to use in every problem domain, due to its nature or to legacy code.

Therefore, Firefox should add an easy (standard/documented with examples) mechanism/API to allow developers to plug in new scripting languages (such as python, haskell, lua, ruby etc) with full access to standardized DOM/CSS, and to users to download them (in the form of some add-on/plugin) and switch them on on-the-fly without resetting the browser.

With the continuous trend in executing client-side web applications, this would be a boost to using Firefox as an OS-agnostic desktop application provider environment. The scripting language name should be as easy to choose as putting the name inside the [script language="[name]"] tag attribute. It should be possible to use several scripting languages on the same web page.

Microsoft Internet Explorer already implements something on these lines with their ScriptHost API, that allows any script engine to be hosted in Internet Explorer (there's even a HaskellScript language that uses this API on top of IScript, a COM interface). Why not implement some similar IScript interface on top of XPCOM?
[[User:Mrcgran|Mrcgran]] 23:42, 4 November 2006 (PST)

==Support for the MNG format==
The MNG format would be an alternative to the old GIF format, which is used really often (eg: boards' smileys, animated buttons, etc ...). It's lack of Alpha channel support is really annoying when you start to create animations not to be used on only one colored background.

The MNG format, which is based on the PNG format, supports alpha channel and animation, but it's not yet a standard. This format needs to be helped in becoming one, but if there was only Microsoft who could do sommething by intergrating the format in IE, we could wait for a long time. Thus, I think Firefox should follow Konkeror in the integration of this format to accelerate the "standardization" of MNG and the "elimination" of GIF, to help the World Wide Web in becoming more user friendly.

; References
* http://en.wikipedia.org/wiki/MNG
* http://en.wikipedia.org/wiki/Gif

:I'm afraid those were supported by the browser, but were deprecated because it's low support by the Web.

==Save page independently==
Option to save page into all-in-one html. Images can be included with data URL-s, javascript and css can be included to page naturally. Flash, java and others are more complicated, but in first step these can be ignored...

<link src="my.css" ...> will be <style>...content of my.css...</style> and <script src="my.js" ... /> will be <script>...content of my.js...</script>. Images will have src="data,..."

Firefox/Feature Brainstorming:Other or Uncategorized

2006-11-06T22:30:40Z

Carutsu: /* Support for the MNG format */

{{FeatureBrainstorming}}

== Widgets ==
* In my opinion, that's the only feature lacking in Firefox to create first-quality "mozlets", similar to the Opera's widgets or Safari's dashboard (if not better, since Opera's widget goes nowhere farther than using XShape).

== Editions ==
* Create several Editions for example standard edition, web developer edition, low memory edition, kid's edition, or even google edition

== "Open page in another browser" option ==
* Simple, useful, and easy to implement.

== Conditional Comments ==
Allow users to add CSS filters for version compatibility that doesn't rely on a CSS rule being implemented. Arguably, this is the unofficial standard for dealing with Internet Explorer bugs and it would be nice to have a simple interface for doing this with any browser (just in case things change later on down the line). The syntax should be about the same, so something like  would be appropriate.

; Comments
That's a very good idea! It could prevent use of CSS hacks in future. Opera could do that too. --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Glow Text ==
Allows text to Glow when the glow HTML command is used, such as in IE7.

== Page autorefresh ==
Create a new "Automatically page refresh" submenu in page's content menu (and inside "In this frame" submenu). It might contain items like "Stop autorefresh", "5 seconds", "10 seconds", "1 minute", "5 minutes", "Custom...". The page should be automatically refreshed untill "Stop autorefresh" selected or user navigated away from the page. In case of page was loaded by 'POST' command the new item should be "disabled" or user might be asked about "repost data every time".
:There is already a couple of extensions for that.

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

; References
* [http://en.wikipedia.org/wiki/Synesthesia Synesthesia] (wikipedia)

; Commentary
: It shouldn't be user picked, but extracted in some ways from the URL domain and optionally changed by a meta tag in the XHTML. This is important to make it a useful feature for both sites and communications (on other computers, the same site will have the same colour). Also it doesn't overload unneeded customization.

== Propietary Anchor mode ==
Many pages don't have anchors so linking to Content that is somewhere on the page can be a pain. Make possible custom anchors like this would make firefox scroll 0pixel to left and 555pixel down:

url#custom(0,555)

This make firefox scroll to the 5th H1 element on the page and highlight it decently:

url#custom(h1/5)

; References
* [http://www.w3.org/TR/xptr-framework/ XPTR framework]

; Commentary
* Pixels are unsafe (depending on fonts, zooming etc.)
* This looks like reinventing the wheel. use xpath instead?
* This implies support for XPointer

== Smooth vs Raw Page Transitions ==
There isn't any *good* point to have the previous page "visible but unusable" until the new page starts rendering, a block a time. This is aesthetically awful and without any useful gain at the UI level.

=== Details & Commentary ===
'''Smooth Page Transition''': when someone clicks on a link, the page will slightly fade out, indicating that it is refreshing until the new page is fully ready, when a smooth (really '''fast''' crossfade <0.5sec, maybe). On the page there should be some form of interaction that could allow to see - and browse, and use - the previous page until the new is fully loaded AND the possibility to switch to the new one, displaying it a block a time.
* If implementing this, Firefox could adhere to some of IE page/site transition definitions from HTTP response or meta http-equiv headers.
** Please no: this is a step back in the past using BAD transitions that were just annoying. This feature, as stated, is conceptually '''DIFFERENT''' and must NOT be assimilated with the IE page transitions.
* The point here is to make the navigation softer and nicer for everyone (cool-factor), not only occasional user, and behaving more like an offline app. The '''"freeze page, load the other one block a time" is obsolete''' and should be improved into a new form of page transition: unobtrusive, aesthetically pleasant and without drawbacks (on slow connection, seeing the page loading a block a time is useful, don't avoid it if needed).
* To be clear: this is COMPLETELY different from the "page transitions" concept seen before on some browsers as site behaviour. This should be an integrated feature, well balanced and ''without annoying drawbacks''. Also, this should be default but disabled.
* The interaction could be:
** On a full-page location refresh (i.e. non javascript) the current page should be lightly dimmed until the new page is ready.
** When the new page is ready, a fast crossfade should display it.
** If the page loads slowly, clicking on Forward (a button not really used since now) will show the page loading a block a time, like now.
** If the user clicks on the dimmed "old" page, it could interact with it until the new page is ready (and faded in). Any click event of course blocks the page load (and the Forward button will turn disabled).

; References
* [http://wiki.mozilla.org/User_talk:Folletto#Smooth_Page_Transitions Smooth Page Transitions]

== Mouse gestures ==
Allow the user to use mouse gestures (like right click followed by left click for 'back' etc)...

; References
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]
* [https://addons.mozilla.org/search.php?q=Rocker&app=firefox Plugins providing this functionality]

== Link navigation using arrow keys ==
* Using shift+arrowKey, the selection "hovers" to the nearest link in that direction
* With this feature remote controls can be configured to navigate pages
* Same as Opera feature

== Remote Control ==
Support for Red/Green/Yellow/Blue remote control buttons
* The ability to configure keyboard shortcuts to select HTML elements that have the accesskey attribute in the format: accesskey="{red}" | accesskey="{green}" | accesskey="{yellow}" | accesskey="{blue}"
* e.g. configure Alt-F1 to select the element with accesskey="{red}", Alt-F2 selects element with accesskey="{green}" etc
* With this feature the RGYB buttons of remote controls can be configured to select links
* This would make Firefox compatible with the Netgem iPlayer facility

== Scripting ==
* 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.
** Support for regular expressions so that pages with broken URLs can be fixed, HTML can be converted to another format, etc.

; References
* [http://greasemonkey.mozdev.org/ Greasemonkey]

== Patching display ==
Let the user configure the display of their page and 'patch' them.

For exemple, change some image, text disposition or even the whole design of the page using regular expression. (Maybe witch a WYGIWYS editor-like to be more user friendly ?)

(I used a while ago an adblock proxy who do that, but it's really slow, whith something directly coded in firefox, this will be great ! No more forum witch crap animated smilets if we can change them on client side)

I think about a way that users can themselfs modify a whole page, and submit their 'patchs' to a centralized server.

When an other user navigate on the page, he can use a button on the navigation page to switch between the different patches submitted by other people and vote for them.

So for one site, we will probably had a lot of version : Ad-free, Alternative design
(Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

== JavaScript Performance ==
JavaScript engine is too slow. When a script on page is become unresponsive - Firefox hangs, until window, proposing to stop that script appears. Enclosing enhancements are good, but functionality and quality are the main thing, we must to follow.

== PDF Reader ==
Make a quick-opening pdf reader, just for text. In other case, run adobe or similar

== Rename tabs ==
It would be useful if end users could rename tabs after opening. Oftentimes, pages with wildly disparate content have similar headings, particularly if browsing forums or newspages or anything where a lot of content comes from a single site. If you could take six tabs all saying "CNN.COM - YOUR SOURCE F..." and change each of them to the subject of the page, it would greatly simplify things.

It really does come up quite often, even if you use separate windows instead of tabs, that the data listed in the browser summary field is basically useless due to excessively long page titles. This does sound like a good feature.

''Note:'' (Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

''Note:'' Done and done.

== Incorporate Wizz RSS ==
To incorporate the Wizz RSS. It becomes it native of the program.

== ActiveX ==
* Implement full ActiveX support
** including optional support via WINE under Linux

;Comments
No way! --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Web services integration ==
Automatically create a web services test form by inspecting a URL to a WSDL file. For comparison, ASP.NET can do this by browsing to a web services URL like foo.asmx?wsdl

== Web mail integration ==
Following Firefox 2 support for online web feed readers, it could be extended to web mail services like Yahoo! Mail, Hotmail and Gmail at least. Users should be able to select one or more web mail providers and set a default or just keep the default stand alone email client. The idea is not to develop a complete email client but to provide minimum integration:
* New mail notification through an alert a la "Downloads complete"
* mailto: handling
* File/Send link... overlay
* More providers can be added with preferences for compose URL and new mail XPath

== Email pseudo-url ==
Presently the mailto: pseudo url simply opens up a mail client. In the old Netscape/Mozilla days, the mail client was part of the package, so it wasn't necessarily such an issue.
Perhaps Firefox could incorporate a lite smpt component which could actually send off data, perhaps as part of a form's action.

== Explorer files integrated ==
Firefox 3.0 should integrate a file explorer of your system, while having the same characteristics as a web page: Tabs, mouse gestures, bookmarks. etc.

== Explorer integration (Windows) ==
In Windows allow file system browsing (ie C:\windows), perhaps by calling on MSHTML APIs.
* Preferably using default file manager -open Koqueror in the current tab when a local directory path is entered

In Windows, allow Firefox to change global settings for preferred browser; not only changing preferred browser for files-types, but also to change what browser applications start when they want to access a webpage.

== Link Activation ==
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.
* Add option to pre-process Javascript (and Flash?) links - enable MMB/CTRL-click to open these in new tab, by tracking the target before obeying the command
* Improved functionality when opening embedded Windows Media Player video files.
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.
* 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.
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.
*Any link will open in a new tab if dragged in any direction rather than being clicked.
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back.
*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.
*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
*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.
* 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.
* An integrated prefetching mechanism (use free bandwith to load in background all the static pages linked from the page) - similar to Fasterfox plugin.
* After i click Shift + click of link i open a link in other window. Now Gecko focuses a loaded window after loading but it's very bad! I suggest to do not focus loaded windows after a loading page through "Shit + click of link". It puts off from browsing :(
* Same as the one above when reading email with several links: Every click on a link brings FF to focus. Better would be keeping FF in background so that one can read the whole mail undisturbed.
* Make an option that Ctrl+Alt+Click, or some other combination, that will open a "preview" of the like page in a "bubble" or some other form of preview.

; References
* [https://addons.mozilla.org/firefox/1269/ Fasterfox plugin]

== Link Context Menu ==
* Add a command to open selected text in a new tab/window.
* 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.
; References
* https://addons.mozilla.org/firefox/1472/

== Additional Mouse Interactivity ==
* Whitespace grabs within the document act as grabbing the icon in the address bar.
* Dragging links to whitespace opens the link in new tab or window
* Highlighting text causes it to be treated as a link in all of it's functionality, including the I'm feeling lucky Google search. If the highlighted text is a valid URL but not formated link (clickable) then open in new tab.
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object
* Opera has a nifty feature with it's Mouse Gestures when you visit an Apache Directory Index or a Gallery site, and a few other sites. When you are on the index, you can just "go forward" in an imaginary history and it will start with the first link. Continuing going forward, will result in the second link, third link, etc... And when you've seen them all - you're back at the Index page.

== Javascript Links ==
* 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.
; References
* See {{bug|55696}}

== Tab Refresh ==
* Allow to refresh Tabs automatically by a counter
** When a change is made to the page on a reload, the tab should change visually

== Independent tabs ==
* The main browser interface should be on a thread that MUST never stop responding (and have a bigger priority). Each tab, should have it's own thread used to fill it's content. If a web page from inside one tab stops responding (or takes too much to load - such as big pdf files or sites that use java - but not resticted to those) the tab should be coloured in a different way (and maybe some text: the web page is not responding). The user MUST be able to either stop , go back, or close the tab, even if the content is not responding. It's VERY anoying now if I open lots of tabs, and the last stops responding, I must close the browser. (true the session restoration is a good step, but it's only a workaround, not the real solution to the problem).

== Quick Top of page/Bottom of page ==
* 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.
* Duplicates Ctrl-Home / Ctrl-End functionality. Would an extra icon to do this be useful?

== Uploading Files ==
Auto-zip multiple files in upload dialog
* Implement multiple file selections in the upload dialog that automatically generates a archive (.zip) for easy transmissions of many files.
* After selecting multiple files a dialog shall appear that asks for the file name of the archive (to be transmitted, auto-naming already included) and confirms the archive type (.zip/.tar.gz/whatsoever)

== Support drag and drop files from OS into a text box / text area ==
* Dragging a file icon from an OS file browser window should drop the name of the file in the target text box. Main use would be for uploading files, but it can be convenient for any other case when a file name and path must be used. It would be a must-have for web-based Document Management Systems, like [http://www.egroupware.org eGroupWare's] DMS.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=50660 bug 50660] and [https://bugzilla.mozilla.org/show_bug.cgi?id=347178 bug 347178]
* [http://slashdot.org/comments.pl?sid=200759&cid=16438433 A comment on Slashdot that gives a nice example of the problem]
* [http://e-vertise.com/dragtext/feature.html What DragText does] in OS/2.

== Dynamic Font Support ==
Support dynamic font such as prf, eot or svg. Considering the huge advancements made in with SVG in the Firefox browser, I really can't see any excuse for NOT including this technology.

From a designer's point of view it makes just about the '''most''' amount of sense - with IE4 onwards supporting font embedding, gifting this technology to FF would just about cover 99% of browsers - the possibilities from a typography point of view are fantastic.
; References
* [http://www.laakshmi.com/aarre/wp/archives/36 this blog]

;Comments

No. Firefox should support dynamic FON, TTF and OTF fonts. --[[User:Alenonimo|Alenonimo]] 15:43, 27 October 2006 (PDT)

== Syntax Highlightning ==
* Devloper aware syntax highlightning
** No language includes these words &nbsp;, <th> and such. The spellchecker should know about symbols used by developers, bloggers and wikiwriters and not to highlight them as a syntax error at least.

== Linux compatibility ==
* Render embedded buttons with native GTK2 widgets
* 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!)
* 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.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].
* 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].

== Mac OS X compatibility ==
* Support Command-Option-F to select search toolbar (standard for Mac applications).
* Render embedded buttons with native Aqua widget
* Dragging favicon to bookmark bar: Expand bookmark folders for bookmark placement when hovering -- FF 1.X+ under other OS's have been able to do this.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=299185 bug #299185]
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=136524 bug #136524]

== Long term target ==
On a long term basis Mozilla has come to a cross-road. The current XUL technology can't be used on a PAD/Smart phone nor on an OLPC. Yet there's a need for such a browser/mailer and it's just a matter of time somebody starts such a project. But I'm sure if such a browser/mailer gets built, it will be ported to the ordinary desktops slowly starting to replace Mozilla. And since switching technologies isn't a task done in a few weeks this subject has to be taken care of ASAP.

IMO it's important for Mozilla to start a task force now to think about the long term future. The PDA/Smart phones are already on the market almost exclusively using IE/Outlook and the OLPC and other embedded devices is just on the brink. So the pressure of this task, to prevent Mozilla from lagging behind again, is imminent.

== Evaluating the future of XUL ==
* It's essential to first evaluate XUL in the light of new requirements, especially about new devices ranging from the OLPC to embedded devices.

== Evaluating possible alternatives ==
* Alternatives should be based on the cornerstone "runs anywhere". Possible is IMO only wxWidgets yet others like Java or .Net/Mono should be rated against XUL as well.

== More vs. Less ==
Well it seems like we could divide 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.

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 interested 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.

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.

== "Core Firefox" & "More Firefox" (Packaging options) ==
* 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:
** A Firefox "Core" with just essential features (based upon XULRunner...)
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".
* 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.
; References
* [http://wiki.mozilla.org/User_talk:Folletto#Firefox_Core_.2B_More Firefox Core + More]

; Commentary
: 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.

=== Extension packs ===
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.

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.

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.

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)

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.

I love the idea of official extensions! And I'd definately like the ability to strip down firefox to the core. This method of development and packageing gets my vote!

Perhaps the installer could be a bit more than just Core & More. You could for example have a check box for extra features, and another for web development tools. Each check box could be expanded to get individual extensions like no-script.

And of course the defaults will be well chosen.

The more functionality you add, the more words and submenus have to be created. And both is confusing for beginners and older folks. What is the difference between words, that seem to mean the same thing at first glance ? Do I have to understand "all these new words" like "javascript", "PlugIn" ? Keep in mind, not all of the users are like the Techies who develop !

Firefox already has all the necessary stuff. There must always be an easy way for "lightweight-users" to use firefox without getting confused about words, large submenus or confusing questions.

The more functions, the more words, the more confusion. Please, always offer an easy way for the non-techie user ... !

I agree that a much smaller (memory) footprint is needed (even on desktop systems), and love the extension pack idea. I'd like to also strongly suggest looking at the reason for the memory size with the current feature set - 225 MB with just 3 tabs open just seems like too much.

The subject of More vs. Less is quite interesting. A good starting point might be to ask "what recent features are being used?". In that vein, maybe one of the "pre-release" versions could be "instrumented" to count the features used and (with the permission of the user, of course) report back those. Another way might be to do a web crawl, and see what features are used by various "popular" web sites. As with ANY feature set, one should realize that "growing featureism" is a very slippery slope. I suspect that many web users would be content with the features of an older browser (say back to 1999) to do their work. Remember that each added "feature" involves code, and with any new code comes both bugs and vulnerabilities. The user community wants neither.

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!).

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.

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!

(removed further repetitive commentary here)

== Customizable extension sets ==
The ability for each user to create, save, install, and manage "feature (extension) sets".

== Rich Internet Application Support ==
There is an opportunity here to lead the way in supporting the growing number of DHTML- and Ajax-heavy applications and to provide the browser support needed to eliminate some of the drawbacks of these apps. In all cases a security model will be necessary, probably including some automated safeguards and some user confirmations.

=== Preloaded javascript libraries ===
* with AJAX large javascript libraries (e.g. "dojo.js") have to be downloaded which need a lot of time. It would be nice if such libraries could be downloaded local in the background and taken from this local store instead of downloaded from the web when referenced by a page. This would speed up any AJAX page considerably. Which libraries are handled this way may be configured in the "offline" settings.

=== Local filesystem access ===
* Allow pages to request access to the local filesystem or some subset thereof (for example, a user's home directory, desktop, or docs folder) for reading and/or writing.<br />
<b>Hear hear!</b> This would enable productivity applications on the web far beyond what we can do today. Mozilla has an opportunity to create a standard API for local storage.

=== Access to global UI elements (menubar, taskbar, panels...) ===
* Allow a page to request access to major OS-level global UI elements like a first-class application. Such elements include the Mac menubar, Windows taskbar, GNOME/KDE panels, Mac Dock, etc. Some are more important than others; for example, being able to write menus to the global menubar is far more important on the Mac platform than Dock access. However, Dock access on the Mac is probably more important than taskbar access on Windows because Windows will already have an entry for each browser window (though being able to define that window's icon would be nice so users can distinguish between "regular" browser windows and in-browser apps).

=== Enhanced clipboard integration ===
* Provide APIs to allow non-text apps to manipulate the system clipboard/pasteboard more.

=== More robust file uploads ===
* Provide single- and multi-select access to standard OS Open dialogs for opening/uploading files. Include an upload manager for asynchronous uploads. Include functionality to resume interrupted uploads. For apps that store data, combine with local filesystem access to allow easy setup of sites that keep local and remote data seamlessly synchronized.

:; Commentary
:: A standardized synchronization protocol would really help on this one. Why does every photo site need to make their own bulk uploader? A sync protocol could send the sha1 of the files in the local directory tree to the server and then let server request upload of the files that it is missing. Even better, make this a two way sync protocol.

== An alternative view of the web browser ==
* Firefox as a new kind of desktop manager.
* Active front end.
; References
* [[User:Anonymous42|Some thoughts]]

== Enabeling new Top-Level-Domains (TLDs) on browser basis ==
* Top-Level-Domains for regions, cities and others
* Top-Level-Domains with IDN characters

The ICANN process for getting approval for a new TLD is quite slow and very stressful for TLD applicant. Making new and by ICANN not yet approved TLDs available could help to foster the development of the DNS. Firefox could easily enable lots of new TLDs and thereby give regional, cultural, linguistic or ethnic communities the opportunity to present themselves by an own identifier. Not to split up the Internet there can be only domains at those TLDs available for which the community indicates to apply at ICANN for an official approval of their TLD.

; References
* [[User:Dotzone|New Top-Level-Domains]]

== Annotations ==
I think it would be really great if there would be enhanced possibilities of graphical marks. It's tough to explain. I think of an complicated scientific text. If I print such a text. I highlight some words, cross other chapters out, add some notes. That's the big advantage of printing a page. If I could mark within a browser wouldn't have to print the page. I could work on screen.

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

== Offline browsing ==
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.

== Thunderbird in a tab ==
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.
== All Mozilla applications in a tab ? ==
Why not opening FileZilla, ChatZilla, etc... in a tab : it's kind of firefox suite ... but the programs are installed separately to avoid one heavy program and get several light ones. Firefox could become an interface for any Mozilla program installed by opening it in a tab.

== Bookmark behaviour ==
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.)

; Comments

Firefox should Import/Export with more formats. XBEL, xFolk, OPML or even create a new one. Support for tags would be cool too. --[[User:Alenonimo|Alenonimo]] 15:48, 27 October 2006 (PDT)

== Socket connection ==
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>
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, like so:

mySocket = new SocketClient("tcp://domain.com/application");
mySocket.onData = processReponse();
mySocket.connect();

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.

== HTTP Sniffer ==
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.
; References
* http://www.httpwatch.com/
* http://tamperdata.mozdev.org/
; Commentary
: Should this functionality really be in the browser itself, when there are things like [http://www.parosproxy.org/index.shtml Paros Web Proxy]?
: Sometimes we are required to use a different proxy (e.g. in corporate networks). Besides, when using HTTPS and gzip compression of pages, the external sniffer will not show the contents of the page. It would be better to sniff by means of the browser itself (both for outgoing requests and for incoming pages, when they are about to be encoded or have already been decoded, respectively, ''by browser''), and to be able to manage these requests in the browser and/or extensions (allow, deny, save, redirect etc.).

== Security ==
* I see many attacks upcoming, which manipulate the DOM-tree inside the browser, altering transactions in banking-systems a.s.o.
* What i wish for Firefox is, to have ONLY signed extensions!
* I want a default block of all extensions to manipulate SSL-protected sites.
This security-feature will be a boost for the usage of Firefox, because all banks will promote FF.

== Flexible table element selection and copy ==
For example, select and copy a column (or columns) from a html table
* Press Ctrl/Cmd when selecting

== User dictionaries ==
I have an existing "user.dic" dictionary, and a couple of specialist dictionaries ("avifauna.dic", "lepidoptera.dic"). They are used by several of my apps, including my e-mail client (Turnpike) and various MS Office apps. I should be able to direct FF to use the former as its dictionary to which new words are added, and to check against all of them when spell-checking.

Also, when the word I'm spell checking is at the bottom of the window, then the suggested replacements should be at the bottom of the context menu.

== Various ==
* Move all MPL code to GPL

== Better Support for Web Apps ==
See my [[User_talk:FunTomas|article]] on that topic.

==Memory management==
Try to minimize the memory usage of Firefox. May be we can have one feature (one button click), which enables the browser to run with minimum feature and there by reducing the memory usage.

==Save web pages in pdf or odt format==
Allow save html pages in pdf or odt format.

==Spell-check support for multiple languages==
I'm doing a doctorate in a French university, on databases, and I'm Romanian. This means that I mail/post/write things in French, English and Romanian all the time, sometimes even in the same text box. I'd like a way to tell FF what languages I'm likely to use so that it can use those dictionaries at the same time. If it's really smart, it should also detect what language each sentence/paragraph/text-box is after a few words and restrict the dictionary automatically to that language. And, perhaps, it should use a different underline color for words that are not in the "current language" dictionary but are in another "in use" dictionary, for cases of [http://en.wikipedia.org/wiki/Code-switching code-switching] (it happens very often when discussing computer-related things in another language than English).

==Restart==
Restart the firefox browser, but restore the session. So that you can get extensions working without losing all your tabs etc.

; Comments

That's implemented already. Just change the Home Page settings to load your previous session. --[[User:Alenonimo|Alenonimo]] 15:49, 27 October 2006 (PDT)

==Built-in Flash Support==
Forget about SVG and Canvas, build an open source Flash implementation into the browser and get rid of the plugin. You could start from gnash http://www.gnu.org/software/gnash/ Use the MIT license and give the source code to Microsoft, they might even help write it.

==PopUp Blocker==
The popup blocker need not have the "Options" button at the end. Instead, clicking anywhere on the popup blocker, we should be able to bring the pop-up blocker options menu (ala IE). Also, add the "Temporarily allow pop-up for this page" option to the main options menu.

==CPU usage when minimized==
Stop flash animations and other CPU power stealers when Firefox window is not selected or is minimized, and for no selected tabs.

==New User Agent string layout==
The actual User Agent strings are confusing and should be deprecated. Firefox 3 could use an User Agent strings simmilar to Opera. Ex:

Firefox/3.0 (Windows NT 5.0; U; pt-BR)

Or yet:

Gecko/1.9 (Windows XP; pt-BR) Firefox 3.0

--[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

==Process Isolation for each Web Site==
With web browsers becoming the de facto application launchers in desktops and several web applications (e.g. gmail) being used continuously, it is very important that an ill-behaved web site is not able to crash the entire web environment. At most, it should crash itself, without affecting the other web sites showing on other windows/tabs or requiring firefox to restart.
[[User:Mrcgran|Mrcgran]] 19:34, 27 October 2006 (PDT)

==Independent sessions per tab/window==
Currently, any web browser I am aware of shares sessions across all instances of the browser (windows/tabs). It would be nice to separate a window or tab and create a new session within it. This would allow you to have, say, two different GMail accounts logged-in at the same time without needing to have two different web browsers.

==Won't comeback button==
In order to minimize the "leak" of memory that the "quick back" and "quick forward" features use we should have an button "I won't come back" this will close the tab and unload everything it had in the memory so that if you close every tab the memory usage will drop back the their 30-40MB that are used on start. Also we should allow the user to define this as his/her normal closing button (so if you close the tab and have that option checked will unload automatically the memory).

==Easier tildes, ñ and Cyrillic characters==
I usually use the ZombieKeys for that, however in some text areas I can't use it, and it seems that the creator of that extension will no longer update it, so, we should have it "by default" (sadly ala IE7). This could be an extra extension (also might be an extension for Cyrillic characters) because I agree with the core/more Firefox movement.

==Page split==
Add ability to split Web pages display.
Web pages may be splited horizontally as spreadsheets does. This feature should include two panels display, each one with its own scrollbar on the right and ability to display result of a link clicked on one panel on the other panel as long as link refers to the same page.
This may be very useful for long pages with multiples internal links and especially for pages containing a table of content on the top (as this one :-) ). This way we could keep TOC on the top panel and navigate through content on the bottom panel.

==Export/Import config to/from XML==
Add ability to export selected config elements (arrived at by running a search within the about:config page) to a file in XML format. The file should have some version info in the header. Each record should optionally contain an extra field for a URL that will point to description of the config element. It should be possible to import the XML back after editing.

==Easy Mechanism/API for changing/adding client-side scripting language dynamically==
Javascript is the default scripting language in Firefox, but javascript is not the best language to use in every problem domain, due to its nature or to legacy code.

Therefore, Firefox should add an easy (standard/documented with examples) mechanism/API to allow developers to plug in new scripting languages (such as python, haskell, lua, ruby etc) with full access to standardized DOM/CSS, and to users to download them (in the form of some add-on/plugin) and switch them on on-the-fly without resetting the browser.

With the continuous trend in executing client-side web applications, this would be a boost to using Firefox as an OS-agnostic desktop application provider environment. The scripting language name should be as easy to choose as putting the name inside the [script language="[name]"] tag attribute. It should be possible to use several scripting languages on the same web page.

Microsoft Internet Explorer already implements something on these lines with their ScriptHost API, that allows any script engine to be hosted in Internet Explorer (there's even a HaskellScript language that uses this API on top of IScript, a COM interface). Why not implement some similar IScript interface on top of XPCOM?
[[User:Mrcgran|Mrcgran]] 23:42, 4 November 2006 (PST)

==Support for the MNG format==
The MNG format would be an alternative to the old GIF format, which is used really often (eg: boards' smileys, animated buttons, etc ...). It's lack of Alpha channel support is really annoying when you start to create animations not to be used on only one colored background.

The MNG format, which is based on the PNG format, supports alpha channel and animation, but it's not yet a standard. This format needs to be helped in becoming one, but if there was only Microsoft who could do sommething by intergrating the format in IE, we could wait for a long time. Thus, I think Firefox should follow Konkeror in the integration of this format to accelerate the "standardization" of MNG and the "elimination" of GIF, to help the World Wide Web in becoming more user friendly.

; References
* http://en.wikipedia.org/wiki/MNG
* http://en.wikipedia.org/wiki/Gif

I'm afraid those were supported by the browser, but were deprecated because it's low support by the Web.

==Save page independently==
Option to save page into all-in-one html. Images can be included with data URL-s, javascript and css can be included to page naturally. Flash, java and others are more complicated, but in first step these can be ignored...

<link src="my.css" ...> will be <style>...content of my.css...</style> and <script src="my.js" ... /> will be <script>...content of my.js...</script>. Images will have src="data,..."

Talk:Firefox/Feature Brainstorming

2006-11-05T06:20:52Z

Carutsu: When?

== Strong support for an intelligent page-scroll! ==

Under "Text readability improvements", topic 2 (in the article of this Feature Brainstorming page) there is described a feature, I have missed for decades in all HTML-displaying software, including Firefox...

You all do know this:
Reading a page over more than one screen leads to a last one, which contains any text-tail, not filling the screen completely. But here, whenever you page-down to this last screen, the end of the text is placed at the bottom of the screen, and therefore at the top there is more or less of text, displayed again. From there, you've lost the last line!
From there, you always have to scan for this line, first...

This behavior is different from any other scrolling, and it's a drag in an ergonomical sense for the reader.
I've never understood, why users didn't critize this, why programers didn't change this!

So, this feature in the way proposed seems to me overdue, really: "the previously visible area should be delimited by a frame/line for a certain period of time, after which the frame disappears or fades out, so it's easier to find the last read line."
Or, similarily: simply show the last line of the previous screen at the top (for recognition, like an editor does), followed by the rest - and show an empty part beneath.

My suspicion is, that in the stone age, somebody had decided "Never screens with empty places at the bottom! Does no look good!", and from there on, all were imitating this - till nowadays.
Imagine this crazy solution with a printed book:
at the end of every chapter, the last page starts repeating text from the page before... maybe, pretty much lines (on average clearly half a page!), just to end with a last line, always exactly at the bottom place!

voodooyou

== Downloading ==

I recently downloaded Firefox 2.0 and tried to download something. The "Open file with... isn't there and I have to save it first. I would like that option back.

i want to agree with that. you sould know it's passible to reactivate this feture by editing a config file, there are instractions on mozillazine fourms

== Open ==

In IE it was wery good function: when you click on exe file you can open it witchout saving! IE sucks but it's have this! Why Firefox haven't got is?

== Reintroduction of a Necessary feature ==

''I don't know where to put this so I hope its ok that I put it here!''
<ol>
<li>why can't you use Alt-Enter to access the properties of a bookmark? </li>

<li>I really like Firefox but I find that it is missing one key feature for me to transition from Mozilla 1.7.12 to Firefox 1.5.0.4, that is the lack of the same Mozilla "Bookmark This <u>G</u>roup of Tabs" feature in Firefox.

Now I know that Firefox has a "Bookmark All Tabs..." option but unlike Mozilla it creates a folder just like any other and has an option to "open in tabs" at the bottom of the folder. I can see why they did this and it would be nice to be able to enter a bookmark group to access only one tab... Yet it is something that is really rarely needed and could be done by hovering over the tab group for a short while.

Now this might seam like a minor gripe considering all the other positives Firefox has over Mozilla, Yet I am truly addicted to the bookmark group in Mozilla and there are a few main reasons behind this:
*it looks different than the other folders and is easy to distinguish
*one simple click on the bookmark group to open it
*The "Bookmark This <u>G</u>roup of Tabs" defaults to show you the file tree (for lack of a better term) giving you a quicker way to save the bookmark group.

Now I have been unable to find any extention that would allow me to use the same Mozilla bookmark group functions inside of Firefox. Is it possable that this could be included? Pretty please! </li>
</ol>
I REALLY would LOVE a solution to this Please help.... Thanks! -- [[User:UKPhoenix79|UKPhoenix79]] 00:32, 3 November 2006 (PST)

== When? ==

I know that the release of Firefox 2.0 has just happened but I can't wait to see the new advantages of Firefox 3.0 so when can we expect it? And by the way When and how will you tell us what features made the cut down? [[User:Carutsu|Carutsu]] 22:20, 4 November 2006 (PST)

Firefox/Feature Brainstorming:Addressbar

2006-11-05T06:05:52Z

Carutsu: /* Another nice feature in IE */

{{FeatureBrainstorming}}

== Showing non-latin characters in address bar ==
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
[http://uk.wikipedia.org/wiki/%D0%92%D1%96%D0%BA%D1%96%D0%BF%D0%B5%D0%B4%D1%96%D1%8F this one] (see the title not the status bar).

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):
http://uk.wikipedia.org/wiki/Вікіпедія
�

== Auto-paging ==
* 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.

== Searching from Location bar ==
* 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.
OR
* Merge functionality of location bar and search bar: When typing in the URL, show both autocomplete and google suggestions (preferrably google suggestions first. Explanation: this helps a lot newbie users; also a lot of users tend to use the drop-down button to go to previously visited urls instead of using the autocomplete feature). Something like this (well not just like that, i just hidden the location bar and moved the search bar in place): http://tinyurl.com/yl24y3

* Bring back the simple, down-arrow functionality of the Mozilla suite address bar, where the user can type in words for a search and down arrow to send that term to the search-engine preference.

== Autocomplete ==
* middle of word
* local filenames
* user's bookmarks
* using history frequency for relevance
* 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
* using addresses for which a password is known, or are otherwise marked as 'trusted' (marked as allow script, allow cookie, allow xpi install, etc)
* all of above make autocomplete still useful after clearing private data or migrating from IE
* Make autocomplete function more like a shell's tab completion in that it matches the longest common substring. See [https://bugzilla.mozilla.org/show_bug.cgi?id=109758 Bug #109758]
; References
* Similar to AppRocket on Windows and Quicksilver for OS X
* [[User talk:bur#Autocomplete_URL|remarks from bur]]
* [https://addons.mozilla.org/firefox/2300/ Autocomplete Manager] extension provides some of this

== Autocorrection ==
* Allow to correct automatically badly entered top level domains (ex: .xom instead of .com or .comù instead of .com) ;
* Allow to correct automatically badly entered sub domains (ex: xxx. instead of www. or wwww. instead of www.) ;
* Allow to correct automatically recurrent typed adresses (ex: www.goiogle.com instead of www.google.com, www.imedia.biz instead of www.imedias.biz or www.youtube.net instead of www.youtube.com) by looking in the favorites and history ;
* Allow to transcode addresses entered incorrectly in different keyboard layout (e.g. Cyrillic цццюьщяшддфющкп to www.mozilla.org) ;

This could be implemented as a smart algorithm. Whenever the user types an invalid adress, Firefox remembers this and if the address typed in right after this is correct (by correctly pointing to a site) a match is created. If the difference is not too large between the wrongly typed one, and the correct one, this get's saved as a correction and will automatically execute.

Alternatively, string metrics can be used to find matches of already typed (and correct) URLs, and automatically redirect the user. Perhaps this is a cleaner solution.

Usually when an incorrect address is typed, the user knows almost immediately. Ingore pages that are only displayed for less than 5 seconds.

== Provide basic site navigation from address bar ==
When I use news aggregation sites like slashdot and digg that provide deep
links to stories on other sites, I invariably find myself wanting to look
at the home page or perhaps even parent of the current URL.

It would be a very useful feature to provide hotkeys that manipulate the
URL in the addressbar. At least 2 operations spring to mind:
* get server URL
* get parent URL
; References
* See [https://addons.mozilla.org/firefox/2933 Link Widgets]
** ...works best with ''Status Buttons 1.0'', basic site navigation buttons could be placed on the '''status line''' this way, so it's no longer «just taking away screen space» as the above fellow said.

== Contextual menu ==
* Contextual menu on each address including "Open", "Open in a new tab" ...
* An option to remove an address from the list. (contextual menu on address ?)
* Also in the contextual menu, add "Delete address".
*On right click, adding also a "paste & go" item

; References
* Like in Opera browser
** Note: Middle click already does this if you turn it on (and it's on by default on Linux)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=216667 bug 216667]

== Location Bar should sort based on order visited ==
All major browser order the entries of the location bar based on last visited. Example: if I type "yahoo.com", then "google.com", the order is:
* google.com
* yahoo.com

If I then type "yahoo.com" again, the order is:
* yahoo.com
* google.com

The order also changes if I open the location bar and select an entry with the mouse.

Sorting this way worked in early releases of Firefox 0.9.X. There is a bug filed in bugzilla for which the fixing is postphoned from one release to the other. Please make sure that it is included in Firefox 2.5, 3.0 or whatever it is.
; References
* [https://bugzilla.mozilla.org/show_bug.cgi?id=258107 bug 258107]

== Keybindings ==
* 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.
* 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.
; References
* [https://bugzilla.mozilla.org/show_bug.cgi?id=237027 bug 237027]

== Allow AJAX/frames-based sites to change location URL ==

A problem with Frames-based and DHTML / AJAX sites is that the page contents
displayed can change but the location URL remains static, which impacts on the
user's ability to bookmark page contents.

For security reasons (e.g. to prevent phishing) it is not possible from
Javascript code to change the location URL displayed in the browser (except
perhaps to add/change a "#" value, which is of limited use).

I propose that it should be possible to change the URL in other LIMITED ways,
e.g.:

To any other URL with the *same* domain
AND/OR
To change the querystring

This could of course be configurable in the browser's Options, but one or both
should be enabled by default, to allow web developers to make use of this
feature to improve the user experience for most Firefox users.

Changing the "#" value, such as at [http://wikimapia.org/#y=44558001&x=38081274&z=15&l=1&m=a&v=2 Wikimapia] is only of partial use and has limitations.

== General Location bar improvements ==
* 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.
* Multi-line paste of URLs: When pasting a multi-line URL - such as when one copies a large URL from a text-only shell-based e-mail program - Firefox should automatically strip line breaks and elide what is pasted as a single line URL.

== SVG File as Favicon ==

Allow website admins/designers to use Scalable Vector Graphics files as Favicons. This allows the use of visually appealing favicons with transparency. This is also ideal for displays with high resolutions, allowing the display of larger icons on such displays without website admins/designers having to modify the icon files.

Right-click option to export favicon.

Javascript manipulation of favicon.

== Highlight the domain name ==

Make the domain name within the URL bold or otherwise highlighted to reduce the spoofing risks of complex URLs.

== Show more security info ==

Show more security info for secure sites in the URL bar, such as the name of the company to which the cert was issued.

== Nice feature in IE ==

A feature absent from FireFox: When you click a link in IE, the page starts loading the page. Sometimes you have connection problems (etc.) so the page remains blank. In the interest of time, you can click "Stop" (to stop downloading the page), and when you do that, IE displays the the page's URL in the address bar, even if the page failed to load. This is absent from FireFox and you have to guess which link you clicked that isn't opening now.

== Another nice feature in IE ==
<strike>I haven't figured out what is the hotkey of the address bar</strike>, could you make it to be F4, just like IE, it would be easier to change the address. Or may be F2 because it's the hotkey used in several applications to change the name or text of anything. Or even you could allow the user to change every hotkey the way he/she wants it, Firefox its very popular for its customization, this would help even more.
:Edit:Err, sorry I found it F6, however the change or customization still stands for it.

Firefox/Feature Brainstorming:Addressbar

2006-11-05T05:58:00Z

Carutsu:

{{FeatureBrainstorming}}

== Showing non-latin characters in address bar ==
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
[http://uk.wikipedia.org/wiki/%D0%92%D1%96%D0%BA%D1%96%D0%BF%D0%B5%D0%B4%D1%96%D1%8F this one] (see the title not the status bar).

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):
http://uk.wikipedia.org/wiki/Вікіпедія
�

== Auto-paging ==
* 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.

== Searching from Location bar ==
* 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.
OR
* Merge functionality of location bar and search bar: When typing in the URL, show both autocomplete and google suggestions (preferrably google suggestions first. Explanation: this helps a lot newbie users; also a lot of users tend to use the drop-down button to go to previously visited urls instead of using the autocomplete feature). Something like this (well not just like that, i just hidden the location bar and moved the search bar in place): http://tinyurl.com/yl24y3

* Bring back the simple, down-arrow functionality of the Mozilla suite address bar, where the user can type in words for a search and down arrow to send that term to the search-engine preference.

== Autocomplete ==
* middle of word
* local filenames
* user's bookmarks
* using history frequency for relevance
* 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
* using addresses for which a password is known, or are otherwise marked as 'trusted' (marked as allow script, allow cookie, allow xpi install, etc)
* all of above make autocomplete still useful after clearing private data or migrating from IE
* Make autocomplete function more like a shell's tab completion in that it matches the longest common substring. See [https://bugzilla.mozilla.org/show_bug.cgi?id=109758 Bug #109758]
; References
* Similar to AppRocket on Windows and Quicksilver for OS X
* [[User talk:bur#Autocomplete_URL|remarks from bur]]
* [https://addons.mozilla.org/firefox/2300/ Autocomplete Manager] extension provides some of this

== Autocorrection ==
* Allow to correct automatically badly entered top level domains (ex: .xom instead of .com or .comù instead of .com) ;
* Allow to correct automatically badly entered sub domains (ex: xxx. instead of www. or wwww. instead of www.) ;
* Allow to correct automatically recurrent typed adresses (ex: www.goiogle.com instead of www.google.com, www.imedia.biz instead of www.imedias.biz or www.youtube.net instead of www.youtube.com) by looking in the favorites and history ;
* Allow to transcode addresses entered incorrectly in different keyboard layout (e.g. Cyrillic цццюьщяшддфющкп to www.mozilla.org) ;

This could be implemented as a smart algorithm. Whenever the user types an invalid adress, Firefox remembers this and if the address typed in right after this is correct (by correctly pointing to a site) a match is created. If the difference is not too large between the wrongly typed one, and the correct one, this get's saved as a correction and will automatically execute.

Alternatively, string metrics can be used to find matches of already typed (and correct) URLs, and automatically redirect the user. Perhaps this is a cleaner solution.

Usually when an incorrect address is typed, the user knows almost immediately. Ingore pages that are only displayed for less than 5 seconds.

== Provide basic site navigation from address bar ==
When I use news aggregation sites like slashdot and digg that provide deep
links to stories on other sites, I invariably find myself wanting to look
at the home page or perhaps even parent of the current URL.

It would be a very useful feature to provide hotkeys that manipulate the
URL in the addressbar. At least 2 operations spring to mind:
* get server URL
* get parent URL
; References
* See [https://addons.mozilla.org/firefox/2933 Link Widgets]
** ...works best with ''Status Buttons 1.0'', basic site navigation buttons could be placed on the '''status line''' this way, so it's no longer «just taking away screen space» as the above fellow said.

== Contextual menu ==
* Contextual menu on each address including "Open", "Open in a new tab" ...
* An option to remove an address from the list. (contextual menu on address ?)
* Also in the contextual menu, add "Delete address".
*On right click, adding also a "paste & go" item

; References
* Like in Opera browser
** Note: Middle click already does this if you turn it on (and it's on by default on Linux)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=216667 bug 216667]

== Location Bar should sort based on order visited ==
All major browser order the entries of the location bar based on last visited. Example: if I type "yahoo.com", then "google.com", the order is:
* google.com
* yahoo.com

If I then type "yahoo.com" again, the order is:
* yahoo.com
* google.com

The order also changes if I open the location bar and select an entry with the mouse.

Sorting this way worked in early releases of Firefox 0.9.X. There is a bug filed in bugzilla for which the fixing is postphoned from one release to the other. Please make sure that it is included in Firefox 2.5, 3.0 or whatever it is.
; References
* [https://bugzilla.mozilla.org/show_bug.cgi?id=258107 bug 258107]

== Keybindings ==
* 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.
* 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.
; References
* [https://bugzilla.mozilla.org/show_bug.cgi?id=237027 bug 237027]

== Allow AJAX/frames-based sites to change location URL ==

A problem with Frames-based and DHTML / AJAX sites is that the page contents
displayed can change but the location URL remains static, which impacts on the
user's ability to bookmark page contents.

For security reasons (e.g. to prevent phishing) it is not possible from
Javascript code to change the location URL displayed in the browser (except
perhaps to add/change a "#" value, which is of limited use).

I propose that it should be possible to change the URL in other LIMITED ways,
e.g.:

To any other URL with the *same* domain
AND/OR
To change the querystring

This could of course be configurable in the browser's Options, but one or both
should be enabled by default, to allow web developers to make use of this
feature to improve the user experience for most Firefox users.

Changing the "#" value, such as at [http://wikimapia.org/#y=44558001&x=38081274&z=15&l=1&m=a&v=2 Wikimapia] is only of partial use and has limitations.

== General Location bar improvements ==
* 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.
* Multi-line paste of URLs: When pasting a multi-line URL - such as when one copies a large URL from a text-only shell-based e-mail program - Firefox should automatically strip line breaks and elide what is pasted as a single line URL.

== SVG File as Favicon ==

Allow website admins/designers to use Scalable Vector Graphics files as Favicons. This allows the use of visually appealing favicons with transparency. This is also ideal for displays with high resolutions, allowing the display of larger icons on such displays without website admins/designers having to modify the icon files.

Right-click option to export favicon.

Javascript manipulation of favicon.

== Highlight the domain name ==

Make the domain name within the URL bold or otherwise highlighted to reduce the spoofing risks of complex URLs.

== Show more security info ==

Show more security info for secure sites in the URL bar, such as the name of the company to which the cert was issued.

== Nice feature in IE ==

A feature absent from FireFox: When you click a link in IE, the page starts loading the page. Sometimes you have connection problems (etc.) so the page remains blank. In the interest of time, you can click "Stop" (to stop downloading the page), and when you do that, IE displays the the page's URL in the address bar, even if the page failed to load. This is absent from FireFox and you have to guess which link you clicked that isn't opening now.

== Another nice feature in IE ==
I haven't figured out what is the hotkey of the address bar, could you make it to be F4, just like IE, it would be easier to change the address. Or may be F2 because it's the hotkey used in several applications to change the name or text of anything. Or even you could allow the user to change every hotkey the way he/she wants it, Firefox its very popular for its customization, this would help even more.

Firefox/Feature Brainstorming:Form handling and text areas

2006-11-05T05:21:32Z

Carutsu: /* WYSIWYG Text Area */

{{FeatureBrainstorming}}

== External editing of text boxes ==
* Allow an external editor (vim, emacs, textpad, etc) to edit text in form text boxes
* Currently supported by plug-ins, but only on some platforms; should be available everywhere
* 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.
* Include ability to save/restore the text box contents.
* Provide a key binding and also bind to right-click/Edit in text areas.
; References
* [https://bugzilla.mozilla.org/show_bug.cgi?id=103767 bug 103767]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=13474 bug 13474]

== Search and replace for editable areas ==
* Search and replace for textareas and editable iframes

== Full featured editing of text areas==
Much writing nowadays is done in text areas: wikis, blogs, forums, webmail. Text areas need full featured editing support:
* Unlimited undo/redo.
* Regular expression search and replace.
* <strike>Spell checking.</strike> Thanks!
* Improve spell checking by switching from MySpell to the far-superior HunSpell (this is a direct descendant of MySpell and is the spell checking system now used by new versions of Open Office). There's a list of all the improvements in [https://bugzilla.mozilla.org/show_bug.cgi?id=319778 bug 319778]. This may also allow us to ship some dictionaries other than En-US in our localized builds (e.g. Hungarian).
* Grammar checking functionality similar to Spell checking (Grammar mistakes is just as prolific an bad spelling)
* Configurable shortcuts and macros.
* Allow easy saving of text area contents on the local machine.
* Automatic safety saves, so that the contents of a text area are never lost.
* Allow resizing of text areas, and splitting into two views.

;See also: [http://ifindkarma.typepad.com/relax/2005/01/life_in_a_texta.html Life in a TEXTAREA] by Adam Rifkin

== WYSIWYG Text Area ==
Enhanced the TEXTAREA tag to provide a WYSIWYG editor that generates HTML code. How many different Javascript, ActiveX, Applet and AJAX solutions exist for this problem? How many of them <u>actually work</u>? None. Let's fix this problem once and do it right. Imagine:

<TEXTAREA NAME="foo" TYPE="wysiwyg">

The user would see a text box with WYSIWYG editing controls. When the form submits, the field would contain HTML code for the user's content. Other browsers would ignore the new flag and display a standard TEXTAREA.

<u>EVERYONE</u> needs this, including this Wiki.
:However we would be breaking the standards, wouldn't we? And i think we shouldn't be trying to do W3C's job.

== Editable dropdowns ==
* Enhanced SELECT tag to allow the user to type new values into the dropdown or accept one of the provided options. Examples in abound in real applications but in a form, the only solution is to provide an input box and a comment like "select a value or enter a new one".
* Enhance the SELECT more by allowing HTML in an OPTION. Will allow for images, bold/italic text and much more in an option. (Restriction necessary as e.g. a SELECT in an OPTION doesn't make sense).

Firefox/Feature Brainstorming:Other or Uncategorized

2006-11-04T07:17:43Z

Carutsu: /* Page autorefresh */

{{FeatureBrainstorming}}

== Widgets ==
* In my opinion, that's the only feature lacking in Firefox to create first-quality "mozlets", similar to the Opera's widgets or Safari's dashboard (if not better, since Opera's widget goes nowhere farther than using XShape).

== Editions ==
* Create several Editions for example standard edition, web developer edition, low memory edition, kid's edition, or even google edition

== "Open page in another browser" option ==
* Simple, useful, and easy to implement.

== Conditional Comments ==
Allow users to add CSS filters for version compatibility that doesn't rely on a CSS rule being implemented. Arguably, this is the unofficial standard for dealing with Internet Explorer bugs and it would be nice to have a simple interface for doing this with any browser (just in case things change later on down the line). The syntax should be about the same, so something like  would be appropriate.

; Comments
That's a very good idea! It could prevent use of CSS hacks in future. Opera could do that too. --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Glow Text ==
Allows text to Glow when the glow HTML command is used, such as in IE7.

== Page autorefresh ==
Create a new "Automatically page refresh" submenu in page's content menu (and inside "In this frame" submenu). It might contain items like "Stop autorefresh", "5 seconds", "10 seconds", "1 minute", "5 minutes", "Custom...". The page should be automatically refreshed untill "Stop autorefresh" selected or user navigated away from the page. In case of page was loaded by 'POST' command the new item should be "disabled" or user might be asked about "repost data every time".
:There is already a couple of extensions for that.

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

; References
* [http://en.wikipedia.org/wiki/Synesthesia Synesthesia] (wikipedia)

; Commentary
: It shouldn't be user picked, but extracted in some ways from the URL domain and optionally changed by a meta tag in the XHTML. This is important to make it a useful feature for both sites and communications (on other computers, the same site will have the same colour). Also it doesn't overload unneeded customization.

== Propietary Anchor mode ==
Many pages don't have anchors so linking to Content that is somewhere on the page can be a pain. Make possible custom anchors like this would make firefox scroll 0pixel to left and 555pixel down:

url#custom(0,555)

This make firefox scroll to the 5th H1 element on the page and highlight it decently:

url#custom(h1/5)

; References
* [http://www.w3.org/TR/xptr-framework/ XPTR framework]

; Commentary
* Pixels are unsafe (depending on fonts, zooming etc.)
* This looks like reinventing the wheel. use xpath instead?
* This implies support for XPointer

== Smooth vs Raw Page Transitions ==
There isn't any *good* point to have the previous page "visible but unusable" until the new page starts rendering, a block a time. This is aesthetically awful and without any useful gain at the UI level.

=== Details & Commentary ===
'''Smooth Page Transition''': when someone clicks on a link, the page will slightly fade out, indicating that it is refreshing until the new page is fully ready, when a smooth (really '''fast''' crossfade <0.5sec, maybe). On the page there should be some form of interaction that could allow to see - and browse, and use - the previous page until the new is fully loaded AND the possibility to switch to the new one, displaying it a block a time.
* If implementing this, Firefox could adhere to some of IE page/site transition definitions from HTTP response or meta http-equiv headers.
** Please no: this is a step back in the past using BAD transitions that were just annoying. This feature, as stated, is conceptually '''DIFFERENT''' and must NOT be assimilated with the IE page transitions.
* The point here is to make the navigation softer and nicer for everyone (cool-factor), not only occasional user, and behaving more like an offline app. The '''"freeze page, load the other one block a time" is obsolete''' and should be improved into a new form of page transition: unobtrusive, aesthetically pleasant and without drawbacks (on slow connection, seeing the page loading a block a time is useful, don't avoid it if needed).
* To be clear: this is COMPLETELY different from the "page transitions" concept seen before on some browsers as site behaviour. This should be an integrated feature, well balanced and ''without annoying drawbacks''. Also, this should be default but disabled.
* The interaction could be:
** On a full-page location refresh (i.e. non javascript) the current page should be lightly dimmed until the new page is ready.
** When the new page is ready, a fast crossfade should display it.
** If the page loads slowly, clicking on Forward (a button not really used since now) will show the page loading a block a time, like now.
** If the user clicks on the dimmed "old" page, it could interact with it until the new page is ready (and faded in). Any click event of course blocks the page load (and the Forward button will turn disabled).

; References
* [http://wiki.mozilla.org/User_talk:Folletto#Smooth_Page_Transitions Smooth Page Transitions]

== Mouse gestures ==
Allow the user to use mouse gestures (like right click followed by left click for 'back' etc)...

; References
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]
* [https://addons.mozilla.org/search.php?q=Rocker&app=firefox Plugins providing this functionality]

== Link navigation using arrow keys ==
* Using shift+arrowKey, the selection "hovers" to the nearest link in that direction
* With this feature remote controls can be configured to navigate pages
* Same as Opera feature

== Remote Control ==
Support for Red/Green/Yellow/Blue remote control buttons
* The ability to configure keyboard shortcuts to select HTML elements that have the accesskey attribute in the format: accesskey="{red}" | accesskey="{green}" | accesskey="{yellow}" | accesskey="{blue}"
* e.g. configure Alt-F1 to select the element with accesskey="{red}", Alt-F2 selects element with accesskey="{green}" etc
* With this feature the RGYB buttons of remote controls can be configured to select links
* This would make Firefox compatible with the Netgem iPlayer facility

== Scripting ==
* 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.
** Support for regular expressions so that pages with broken URLs can be fixed, HTML can be converted to another format, etc.

; References
* [http://greasemonkey.mozdev.org/ Greasemonkey]

== Patching display ==
Let the user configure the display of their page and 'patch' them.

For exemple, change some image, text disposition or even the whole design of the page using regular expression. (Maybe witch a WYGIWYS editor-like to be more user friendly ?)

(I used a while ago an adblock proxy who do that, but it's really slow, whith something directly coded in firefox, this will be great ! No more forum witch crap animated smilets if we can change them on client side)

I think about a way that users can themselfs modify a whole page, and submit their 'patchs' to a centralized server.

When an other user navigate on the page, he can use a button on the navigation page to switch between the different patches submitted by other people and vote for them.

So for one site, we will probably had a lot of version : Ad-free, Alternative design
(Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

== JavaScript Performance ==
JavaScript engine is too slow. When a script on page is become unresponsive - Firefox hangs, until window, proposing to stop that script appears. Enclosing enhancements are good, but functionality and quality are the main thing, we must to follow.

== PDF Reader ==
Make a quick-opening pdf reader, just for text. In other case, run adobe or similar

== Rename tabs ==
It would be useful if end users could rename tabs after opening. Oftentimes, pages with wildly disparate content have similar headings, particularly if browsing forums or newspages or anything where a lot of content comes from a single site. If you could take six tabs all saying "CNN.COM - YOUR SOURCE F..." and change each of them to the subject of the page, it would greatly simplify things.

It really does come up quite often, even if you use separate windows instead of tabs, that the data listed in the browser summary field is basically useless due to excessively long page titles. This does sound like a good feature.

''Note:'' (Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

''Note:'' Done and done.

== Incorporate Wizz RSS ==
To incorporate the Wizz RSS. It becomes it native of the program.

== ActiveX ==
* Implement full ActiveX support
** including optional support via WINE under Linux

;Comments
No way! --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Web services integration ==
Automatically create a web services test form by inspecting a URL to a WSDL file. For comparison, ASP.NET can do this by browsing to a web services URL like foo.asmx?wsdl

== Web mail integration ==
Following Firefox 2 support for online web feed readers, it could be extended to web mail services like Yahoo! Mail, Hotmail and Gmail at least. Users should be able to select one or more web mail providers and set a default or just keep the default stand alone email client. The idea is not to develop a complete email client but to provide minimum integration:
* New mail notification through an alert a la "Downloads complete"
* mailto: handling
* File/Send link... overlay
* More providers can be added with preferences for compose URL and new mail XPath

== Email pseudo-url ==
Presently the mailto: pseudo url simply opens up a mail client. In the old Netscape/Mozilla days, the mail client was part of the package, so it wasn't necessarily such an issue.
Perhaps Firefox could incorporate a lite smpt component which could actually send off data, perhaps as part of a form's action.

== Explorer files integrated ==
Firefox 3.0 should integrate a file explorer of your system, while having the same characteristics as a web page: Tabs, mouse gestures, bookmarks. etc.

== Explorer integration (Windows) ==
In Windows allow file system browsing (ie C:\windows), perhaps by calling on MSHTML APIs.
* Preferably using default file manager -open Koqueror in the current tab when a local directory path is entered

In Windows, allow Firefox to change global settings for preferred browser; not only changing preferred browser for files-types, but also to change what browser applications start when they want to access a webpage.

== Link Activation ==
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.
* Add option to pre-process Javascript (and Flash?) links - enable MMB/CTRL-click to open these in new tab, by tracking the target before obeying the command
* Improved functionality when opening embedded Windows Media Player video files.
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.
* 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.
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.
*Any link will open in a new tab if dragged in any direction rather than being clicked.
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back.
*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.
*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
*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.
* 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.
* An integrated prefetching mechanism (use free bandwith to load in background all the static pages linked from the page) - similar to Fasterfox plugin.
* After i click Shift + click of link i open a link in other window. Now Gecko focuses a loaded window after loading but it's very bad! I suggest to do not focus loaded windows after a loading page through "Shit + click of link". It puts off from browsing :(
* Same as the one above when reading email with several links: Every click on a link brings FF to focus. Better would be keeping FF in background so that one can read the whole mail undisturbed.
* Make an option that Ctrl+Alt+Click, or some other combination, that will open a "preview" of the like page in a "bubble" or some other form of preview.

; References
* [https://addons.mozilla.org/firefox/1269/ Fasterfox plugin]

== Link Context Menu ==
* Add a command to open selected text in a new tab/window.
* 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.
; References
* https://addons.mozilla.org/firefox/1472/

== Additional Mouse Interactivity ==
* Whitespace grabs within the document act as grabbing the icon in the address bar.
* Dragging links to whitespace opens the link in new tab or window
* Highlighting text causes it to be treated as a link in all of it's functionality, including the I'm feeling lucky Google search. If the highlighted text is a valid URL but not formated link (clickable) then open in new tab.
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object
* Opera has a nifty feature with it's Mouse Gestures when you visit an Apache Directory Index or a Gallery site, and a few other sites. When you are on the index, you can just "go forward" in an imaginary history and it will start with the first link. Continuing going forward, will result in the second link, third link, etc... And when you've seen them all - you're back at the Index page.

== Javascript Links ==
* 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.
; References
* See {{bug|55696}}

== Tab Refresh ==
* Allow to refresh Tabs automatically by a counter
** When a change is made to the page on a reload, the tab should change visually

== Independent tabs ==
* The main browser interface should be on a thread that MUST never stop responding (and have a bigger priority). Each tab, should have it's own thread used to fill it's content. If a web page from inside one tab stops responding (or takes too much to load - such as big pdf files or sites that use java - but not resticted to those) the tab should be coloured in a different way (and maybe some text: the web page is not responding). The user MUST be able to either stop , go back, or close the tab, even if the content is not responding. It's VERY anoying now if I open lots of tabs, and the last stops responding, I must close the browser. (true the session restoration is a good step, but it's only a workaround, not the real solution to the problem).

== Quick Top of page/Bottom of page ==
* 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.
* Duplicates Ctrl-Home / Ctrl-End functionality. Would an extra icon to do this be useful?

== Uploading Files ==
Auto-zip multiple files in upload dialog
* Implement multiple file selections in the upload dialog that automatically generates a archive (.zip) for easy transmissions of many files.
* After selecting multiple files a dialog shall appear that asks for the file name of the archive (to be transmitted, auto-naming already included) and confirms the archive type (.zip/.tar.gz/whatsoever)

== Support drag and drop files from OS into a text box / text area ==
* Dragging a file icon from an OS file browser window should drop the name of the file in the target text box. Main use would be for uploading files, but it can be convenient for any other case when a file name and path must be used. It would be a must-have for web-based Document Management Systems, like [http://www.egroupware.org eGroupWare's] DMS.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=50660 bug 50660] and [https://bugzilla.mozilla.org/show_bug.cgi?id=347178 bug 347178]
* [http://slashdot.org/comments.pl?sid=200759&cid=16438433 A comment on Slashdot that gives a nice example of the problem]
* [http://e-vertise.com/dragtext/feature.html What DragText does] in OS/2.

== Dynamic Font Support ==
Support dynamic font such as prf, eot or svg. Considering the huge advancements made in with SVG in the Firefox browser, I really can't see any excuse for NOT including this technology.

From a designer's point of view it makes just about the '''most''' amount of sense - with IE4 onwards supporting font embedding, gifting this technology to FF would just about cover 99% of browsers - the possibilities from a typography point of view are fantastic.
; References
* [http://www.laakshmi.com/aarre/wp/archives/36 this blog]

;Comments

No. Firefox should support dynamic FON, TTF and OTF fonts. --[[User:Alenonimo|Alenonimo]] 15:43, 27 October 2006 (PDT)

== Syntax Highlightning ==
* Devloper aware syntax highlightning
** No language includes these words &nbsp;, <th> and such. The spellchecker should know about symbols used by developers, bloggers and wikiwriters and not to highlight them as a syntax error at least.

== Linux compatibility ==
* Render embedded buttons with native GTK2 widgets
* 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!)
* 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.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].
* 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].

== Mac OS X compatibility ==
* Support Command-Option-F to select search toolbar (standard for Mac applications).
* Render embedded buttons with native Aqua widget
* Dragging favicon to bookmark bar: Expand bookmark folders for bookmark placement when hovering -- FF 1.X+ under other OS's have been able to do this.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=299185 bug #299185]
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=136524 bug #136524]

== Long term target ==
On a long term basis Mozilla has come to a cross-road. The current XUL technology can't be used on a PAD/Smart phone nor on an OLPC. Yet there's a need for such a browser/mailer and it's just a matter of time somebody starts such a project. But I'm sure if such a browser/mailer gets built, it will be ported to the ordinary desktops slowly starting to replace Mozilla. And since switching technologies isn't a task done in a few weeks this subject has to be taken care of ASAP.

IMO it's important for Mozilla to start a task force now to think about the long term future. The PDA/Smart phones are already on the market almost exclusively using IE/Outlook and the OLPC and other embedded devices is just on the brink. So the pressure of this task, to prevent Mozilla from lagging behind again, is imminent.

== Evaluating the future of XUL ==
* It's essential to first evaluate XUL in the light of new requirements, especially about new devices ranging from the OLPC to embedded devices.

== Evaluating possible alternatives ==
* Alternatives should be based on the cornerstone "runs anywhere". Possible is IMO only wxWidgets yet others like Java or .Net/Mono should be rated against XUL as well.

== More vs. Less ==
Well it seems like we could divide 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.

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 interested 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.

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.

== "Core Firefox" & "More Firefox" (Packaging options) ==
* 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:
** A Firefox "Core" with just essential features (based upon XULRunner...)
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".
* 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.
; References
* [http://wiki.mozilla.org/User_talk:Folletto#Firefox_Core_.2B_More Firefox Core + More]

; Commentary
: 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.

=== Extension packs ===
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.

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.

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.

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)

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.

I love the idea of official extensions! And I'd definately like the ability to strip down firefox to the core. This method of development and packageing gets my vote!

Perhaps the installer could be a bit more than just Core & More. You could for example have a check box for extra features, and another for web development tools. Each check box could be expanded to get individual extensions like no-script.

And of course the defaults will be well chosen.

The more functionality you add, the more words and submenus have to be created. And both is confusing for beginners and older folks. What is the difference between words, that seem to mean the same thing at first glance ? Do I have to understand "all these new words" like "javascript", "PlugIn" ? Keep in mind, not all of the users are like the Techies who develop !

Firefox already has all the necessary stuff. There must always be an easy way for "lightweight-users" to use firefox without getting confused about words, large submenus or confusing questions.

The more functions, the more words, the more confusion. Please, always offer an easy way for the non-techie user ... !

I agree that a much smaller (memory) footprint is needed (even on desktop systems), and love the extension pack idea. I'd like to also strongly suggest looking at the reason for the memory size with the current feature set - 225 MB with just 3 tabs open just seems like too much.

The subject of More vs. Less is quite interesting. A good starting point might be to ask "what recent features are being used?". In that vein, maybe one of the "pre-release" versions could be "instrumented" to count the features used and (with the permission of the user, of course) report back those. Another way might be to do a web crawl, and see what features are used by various "popular" web sites. As with ANY feature set, one should realize that "growing featureism" is a very slippery slope. I suspect that many web users would be content with the features of an older browser (say back to 1999) to do their work. Remember that each added "feature" involves code, and with any new code comes both bugs and vulnerabilities. The user community wants neither.

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!).

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.

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!

(removed further repetitive commentary here)

== Customizable extension sets ==
The ability for each user to create, save, install, and manage "feature (extension) sets".

== Rich Internet Application Support ==
There is an opportunity here to lead the way in supporting the growing number of DHTML- and Ajax-heavy applications and to provide the browser support needed to eliminate some of the drawbacks of these apps. In all cases a security model will be necessary, probably including some automated safeguards and some user confirmations.

=== Preloaded javascript libraries ===
* with AJAX large javascript libraries (e.g. "dojo.js") have to be downloaded which need a lot of time. It would be nice if such libraries could be downloaded local in the background and taken from this local store instead of downloaded from the web when referenced by a page. This would speed up any AJAX page considerably. Which libraries are handled this way may be configured in the "offline" settings.

=== Local filesystem access ===
* Allow pages to request access to the local filesystem or some subset thereof (for example, a user's home directory, desktop, or docs folder) for reading and/or writing.<br />
<b>Hear hear!</b> This would enable productivity applications on the web far beyond what we can do today. Mozilla has an opportunity to create a standard API for local storage.

=== Access to global UI elements (menubar, taskbar, panels...) ===
* Allow a page to request access to major OS-level global UI elements like a first-class application. Such elements include the Mac menubar, Windows taskbar, GNOME/KDE panels, Mac Dock, etc. Some are more important than others; for example, being able to write menus to the global menubar is far more important on the Mac platform than Dock access. However, Dock access on the Mac is probably more important than taskbar access on Windows because Windows will already have an entry for each browser window (though being able to define that window's icon would be nice so users can distinguish between "regular" browser windows and in-browser apps).

=== Enhanced clipboard integration ===
* Provide APIs to allow non-text apps to manipulate the system clipboard/pasteboard more.

=== More robust file uploads ===
* Provide single- and multi-select access to standard OS Open dialogs for opening/uploading files. Include an upload manager for asynchronous uploads. Include functionality to resume interrupted uploads. For apps that store data, combine with local filesystem access to allow easy setup of sites that keep local and remote data seamlessly synchronized.

:; Commentary
:: A standardized synchronization protocol would really help on this one. Why does every photo site need to make their own bulk uploader? A sync protocol could send the sha1 of the files in the local directory tree to the server and then let server request upload of the files that it is missing. Even better, make this a two way sync protocol.

== An alternative view of the web browser ==
* Firefox as a new kind of desktop manager.
* Active front end.
; References
* [[User:Anonymous42|Some thoughts]]

== Enabeling new Top-Level-Domains (TLDs) on browser basis ==
* Top-Level-Domains for regions, cities and others
* Top-Level-Domains with IDN characters

The ICANN process for getting approval for a new TLD is quite slow and very stressful for TLD applicant. Making new and by ICANN not yet approved TLDs available could help to foster the development of the DNS. Firefox could easily enable lots of new TLDs and thereby give regional, cultural, linguistic or ethnic communities the opportunity to present themselves by an own identifier. Not to split up the Internet there can be only domains at those TLDs available for which the community indicates to apply at ICANN for an official approval of their TLD.

; References
* [[User:Dotzone|New Top-Level-Domains]]

== Annotations ==
I think it would be really great if there would be enhanced possibilities of graphical marks. It's tough to explain. I think of an complicated scientific text. If I print such a text. I highlight some words, cross other chapters out, add some notes. That's the big advantage of printing a page. If I could mark within a browser wouldn't have to print the page. I could work on screen.

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

== Offline browsing ==
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.

== Thunderbird in a tab ==
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.
== All Mozilla applications in a tab ? ==
Why not opening FileZilla, ChatZilla, etc... in a tab : it's kind of firefox suite ... but the programs are installed separately to avoid one heavy program and get several light ones. Firefox could become an interface for any Mozilla program installed by opening it in a tab.

== Bookmark behaviour ==
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.)

; Comments

Firefox should Import/Export with more formats. XBEL, xFolk, OPML or even create a new one. Support for tags would be cool too. --[[User:Alenonimo|Alenonimo]] 15:48, 27 October 2006 (PDT)

== Socket connection ==
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>
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, like so:

mySocket = new SocketClient("tcp://domain.com/application");
mySocket.onData = processReponse();
mySocket.connect();

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.

== HTTP Sniffer ==
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.
; References
* http://www.httpwatch.com/
* http://tamperdata.mozdev.org/
; Commentary
: Should this functionality really be in the browser itself, when there are things like [http://www.parosproxy.org/index.shtml Paros Web Proxy]?
: Sometimes we are required to use a different proxy (e.g. in corporate networks). Besides, when using HTTPS and gzip compression of pages, the external sniffer will not show the contents of the page. It would be better to sniff by means of the browser itself (both for outgoing requests and for incoming pages, when they are about to be encoded or have already been decoded, respectively, ''by browser''), and to be able to manage these requests in the browser and/or extensions (allow, deny, save, redirect etc.).

== Security ==
* I see many attacks upcoming, which manipulate the DOM-tree inside the browser, altering transactions in banking-systems a.s.o.
* What i wish for Firefox is, to have ONLY signed extensions!
* I want a default block of all extensions to manipulate SSL-protected sites.
This security-feature will be a boost for the usage of Firefox, because all banks will promote FF.

== Flexible table element selection and copy ==
For example, select and copy a column (or columns) from a html table
* Press Ctrl/Cmd when selecting

== User dictionaries ==
I have an existing "user.dic" dictionary, and a couple of specialist dictionaries ("avifauna.dic", "lepidoptera.dic"). They are used by several of my apps, including my e-mail client (Turnpike) and various MS Office apps. I should be able to direct FF to use the former as its dictionary to which new words are added, and to check against all of them when spell-checking.

Also, when the word I'm spell checking is at the bottom of the window, then the suggested replacements should be at the bottom of the context menu.

== Various ==
* Move all MPL code to GPL

== Better Support for Web Apps ==
See my [[User_talk:FunTomas|article]] on that topic.

==Memory management==
Try to minimize the memory usage of Firefox. May be we can have one feature (one button click), which enables the browser to run with minimum feature and there by reducing the memory usage.

==Save web pages in pdf or odt format==
Allow save html pages in pdf or odt format.

==Spell-check support for multiple languages==
I'm doing a doctorate in a French university, on databases, and I'm Romanian. This means that I mail/post/write things in French, English and Romanian all the time, sometimes even in the same text box. I'd like a way to tell FF what languages I'm likely to use so that it can use those dictionaries at the same time. If it's really smart, it should also detect what language each sentence/paragraph/text-box is after a few words and restrict the dictionary automatically to that language. And, perhaps, it should use a different underline color for words that are not in the "current language" dictionary but are in another "in use" dictionary, for cases of [http://en.wikipedia.org/wiki/Code-switching code-switching] (it happens very often when discussing computer-related things in another language than English).

==Restart==
Restart the firefox browser, but restore the session. So that you can get extensions working without losing all your tabs etc.

; Comments

That's implemented already. Just change the Home Page settings to load your previous session. --[[User:Alenonimo|Alenonimo]] 15:49, 27 October 2006 (PDT)

==Built-in Flash Support==
Forget about SVG and Canvas, build an open source Flash implementation into the browser and get rid of the plugin. You could start from gnash http://www.gnu.org/software/gnash/ Use the MIT license and give the source code to Microsoft, they might even help write it.

==PopUp Blocker==
The popup blocker need not have the "Options" button at the end. Instead, clicking anywhere on the popup blocker, we should be able to bring the pop-up blocker options menu (ala IE). Also, add the "Temporarily allow pop-up for this page" option to the main options menu.

==CPU usage when minimized==
Stop flash animations and other CPU power stealers when Firefox window is not selected or is minimized, and for no selected tabs.

==New User Agent string layout==
The actual User Agent strings are confusing and should be deprecated. Firefox 3 could use an User Agent strings simmilar to Opera. Ex:

Firefox/3.0 (Windows NT 5.0; U; pt-BR)

Or yet:

Gecko/1.9 (Windows XP; pt-BR) Firefox 3.0

--[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

==Process Isolation for each Web Site==
With web browsers becoming the de facto application launchers in desktops and several web applications (e.g. gmail) being used continuously, it is very important that an ill-behaved web site is not able to crash the entire web environment. At most, it should crash itself, without affecting the other web sites showing on other windows/tabs or requiring firefox to restart.
[[User:Mrcgran|Mrcgran]] 19:34, 27 October 2006 (PDT)

==Independent sessions per tab/window==
Currently, any web browser I am aware of shares sessions across all instances of the browser (windows/tabs). It would be nice to separate a window or tab and create a new session within it. This would allow you to have, say, two different GMail accounts logged-in at the same time without needing to have two different web browsers.

==Won't comeback button==
In order to minimize the "leak" of memory that the "quick back" and "quick forward" features use we should have an button "I won't come back" this will close the tab and unload everything it had in the memory so that if you close every tab the memory usage will drop back the their 30-40MB that are used on start. Also we should allow the user to define this as his/her normal closing button (so if you close the tab and have that option checked will unload automatically the memory).

==Easier tildes, ñ and Cyrillic characters==
I usually use the ZombieKeys for that, however in some text areas I can't use it, and it seems that the creator of that extension will no longer update it, so, we should have it "by default" (sadly ala IE7). This could be an extra extension (also might be an extension for Cyrillic characters) because I agree with the core/more Firefox movement.

Firefox/Feature Brainstorming:Other or Uncategorized

2006-11-04T07:15:19Z

Carutsu:

{{FeatureBrainstorming}}

== Widgets ==
* In my opinion, that's the only feature lacking in Firefox to create first-quality "mozlets", similar to the Opera's widgets or Safari's dashboard (if not better, since Opera's widget goes nowhere farther than using XShape).

== Editions ==
* Create several Editions for example standard edition, web developer edition, low memory edition, kid's edition, or even google edition

== "Open page in another browser" option ==
* Simple, useful, and easy to implement.

== Conditional Comments ==
Allow users to add CSS filters for version compatibility that doesn't rely on a CSS rule being implemented. Arguably, this is the unofficial standard for dealing with Internet Explorer bugs and it would be nice to have a simple interface for doing this with any browser (just in case things change later on down the line). The syntax should be about the same, so something like  would be appropriate.

; Comments
That's a very good idea! It could prevent use of CSS hacks in future. Opera could do that too. --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Glow Text ==
Allows text to Glow when the glow HTML command is used, such as in IE7.

== Page autorefresh ==
Create a new "Automatically page refresh" submenu in page's content menu (and inside "In this frame" submenu). It might contain items like "Stop autorefresh", "5 seconds", "10 seconds", "1 minute", "5 minutes", "Custom...". The page should be automatically refreshed untill "Stop autorefresh" selected or user navigated away from the page. In case of page was loaded by 'POST' command the new item should be "disabled" or user might be asked about "repost data every time".

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

; References
* [http://en.wikipedia.org/wiki/Synesthesia Synesthesia] (wikipedia)

; Commentary
: It shouldn't be user picked, but extracted in some ways from the URL domain and optionally changed by a meta tag in the XHTML. This is important to make it a useful feature for both sites and communications (on other computers, the same site will have the same colour). Also it doesn't overload unneeded customization.

== Propietary Anchor mode ==
Many pages don't have anchors so linking to Content that is somewhere on the page can be a pain. Make possible custom anchors like this would make firefox scroll 0pixel to left and 555pixel down:

url#custom(0,555)

This make firefox scroll to the 5th H1 element on the page and highlight it decently:

url#custom(h1/5)

; References
* [http://www.w3.org/TR/xptr-framework/ XPTR framework]

; Commentary
* Pixels are unsafe (depending on fonts, zooming etc.)
* This looks like reinventing the wheel. use xpath instead?
* This implies support for XPointer

== Smooth vs Raw Page Transitions ==
There isn't any *good* point to have the previous page "visible but unusable" until the new page starts rendering, a block a time. This is aesthetically awful and without any useful gain at the UI level.

=== Details & Commentary ===
'''Smooth Page Transition''': when someone clicks on a link, the page will slightly fade out, indicating that it is refreshing until the new page is fully ready, when a smooth (really '''fast''' crossfade <0.5sec, maybe). On the page there should be some form of interaction that could allow to see - and browse, and use - the previous page until the new is fully loaded AND the possibility to switch to the new one, displaying it a block a time.
* If implementing this, Firefox could adhere to some of IE page/site transition definitions from HTTP response or meta http-equiv headers.
** Please no: this is a step back in the past using BAD transitions that were just annoying. This feature, as stated, is conceptually '''DIFFERENT''' and must NOT be assimilated with the IE page transitions.
* The point here is to make the navigation softer and nicer for everyone (cool-factor), not only occasional user, and behaving more like an offline app. The '''"freeze page, load the other one block a time" is obsolete''' and should be improved into a new form of page transition: unobtrusive, aesthetically pleasant and without drawbacks (on slow connection, seeing the page loading a block a time is useful, don't avoid it if needed).
* To be clear: this is COMPLETELY different from the "page transitions" concept seen before on some browsers as site behaviour. This should be an integrated feature, well balanced and ''without annoying drawbacks''. Also, this should be default but disabled.
* The interaction could be:
** On a full-page location refresh (i.e. non javascript) the current page should be lightly dimmed until the new page is ready.
** When the new page is ready, a fast crossfade should display it.
** If the page loads slowly, clicking on Forward (a button not really used since now) will show the page loading a block a time, like now.
** If the user clicks on the dimmed "old" page, it could interact with it until the new page is ready (and faded in). Any click event of course blocks the page load (and the Forward button will turn disabled).

; References
* [http://wiki.mozilla.org/User_talk:Folletto#Smooth_Page_Transitions Smooth Page Transitions]

== Mouse gestures ==
Allow the user to use mouse gestures (like right click followed by left click for 'back' etc)...

; References
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]
* [https://addons.mozilla.org/search.php?q=Rocker&app=firefox Plugins providing this functionality]

== Link navigation using arrow keys ==
* Using shift+arrowKey, the selection "hovers" to the nearest link in that direction
* With this feature remote controls can be configured to navigate pages
* Same as Opera feature

== Remote Control ==
Support for Red/Green/Yellow/Blue remote control buttons
* The ability to configure keyboard shortcuts to select HTML elements that have the accesskey attribute in the format: accesskey="{red}" | accesskey="{green}" | accesskey="{yellow}" | accesskey="{blue}"
* e.g. configure Alt-F1 to select the element with accesskey="{red}", Alt-F2 selects element with accesskey="{green}" etc
* With this feature the RGYB buttons of remote controls can be configured to select links
* This would make Firefox compatible with the Netgem iPlayer facility

== Scripting ==
* 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.
** Support for regular expressions so that pages with broken URLs can be fixed, HTML can be converted to another format, etc.

; References
* [http://greasemonkey.mozdev.org/ Greasemonkey]

== Patching display ==
Let the user configure the display of their page and 'patch' them.

For exemple, change some image, text disposition or even the whole design of the page using regular expression. (Maybe witch a WYGIWYS editor-like to be more user friendly ?)

(I used a while ago an adblock proxy who do that, but it's really slow, whith something directly coded in firefox, this will be great ! No more forum witch crap animated smilets if we can change them on client side)

I think about a way that users can themselfs modify a whole page, and submit their 'patchs' to a centralized server.

When an other user navigate on the page, he can use a button on the navigation page to switch between the different patches submitted by other people and vote for them.

So for one site, we will probably had a lot of version : Ad-free, Alternative design
(Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

== JavaScript Performance ==
JavaScript engine is too slow. When a script on page is become unresponsive - Firefox hangs, until window, proposing to stop that script appears. Enclosing enhancements are good, but functionality and quality are the main thing, we must to follow.

== PDF Reader ==
Make a quick-opening pdf reader, just for text. In other case, run adobe or similar

== Rename tabs ==
It would be useful if end users could rename tabs after opening. Oftentimes, pages with wildly disparate content have similar headings, particularly if browsing forums or newspages or anything where a lot of content comes from a single site. If you could take six tabs all saying "CNN.COM - YOUR SOURCE F..." and change each of them to the subject of the page, it would greatly simplify things.

It really does come up quite often, even if you use separate windows instead of tabs, that the data listed in the browser summary field is basically useless due to excessively long page titles. This does sound like a good feature.

''Note:'' (Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

''Note:'' Done and done.

== Incorporate Wizz RSS ==
To incorporate the Wizz RSS. It becomes it native of the program.

== ActiveX ==
* Implement full ActiveX support
** including optional support via WINE under Linux

;Comments
No way! --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Web services integration ==
Automatically create a web services test form by inspecting a URL to a WSDL file. For comparison, ASP.NET can do this by browsing to a web services URL like foo.asmx?wsdl

== Web mail integration ==
Following Firefox 2 support for online web feed readers, it could be extended to web mail services like Yahoo! Mail, Hotmail and Gmail at least. Users should be able to select one or more web mail providers and set a default or just keep the default stand alone email client. The idea is not to develop a complete email client but to provide minimum integration:
* New mail notification through an alert a la "Downloads complete"
* mailto: handling
* File/Send link... overlay
* More providers can be added with preferences for compose URL and new mail XPath

== Email pseudo-url ==
Presently the mailto: pseudo url simply opens up a mail client. In the old Netscape/Mozilla days, the mail client was part of the package, so it wasn't necessarily such an issue.
Perhaps Firefox could incorporate a lite smpt component which could actually send off data, perhaps as part of a form's action.

== Explorer files integrated ==
Firefox 3.0 should integrate a file explorer of your system, while having the same characteristics as a web page: Tabs, mouse gestures, bookmarks. etc.

== Explorer integration (Windows) ==
In Windows allow file system browsing (ie C:\windows), perhaps by calling on MSHTML APIs.
* Preferably using default file manager -open Koqueror in the current tab when a local directory path is entered

In Windows, allow Firefox to change global settings for preferred browser; not only changing preferred browser for files-types, but also to change what browser applications start when they want to access a webpage.

== Link Activation ==
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.
* Add option to pre-process Javascript (and Flash?) links - enable MMB/CTRL-click to open these in new tab, by tracking the target before obeying the command
* Improved functionality when opening embedded Windows Media Player video files.
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.
* 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.
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.
*Any link will open in a new tab if dragged in any direction rather than being clicked.
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back.
*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.
*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
*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.
* 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.
* An integrated prefetching mechanism (use free bandwith to load in background all the static pages linked from the page) - similar to Fasterfox plugin.
* After i click Shift + click of link i open a link in other window. Now Gecko focuses a loaded window after loading but it's very bad! I suggest to do not focus loaded windows after a loading page through "Shit + click of link". It puts off from browsing :(
* Same as the one above when reading email with several links: Every click on a link brings FF to focus. Better would be keeping FF in background so that one can read the whole mail undisturbed.
* Make an option that Ctrl+Alt+Click, or some other combination, that will open a "preview" of the like page in a "bubble" or some other form of preview.

; References
* [https://addons.mozilla.org/firefox/1269/ Fasterfox plugin]

== Link Context Menu ==
* Add a command to open selected text in a new tab/window.
* 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.
; References
* https://addons.mozilla.org/firefox/1472/

== Additional Mouse Interactivity ==
* Whitespace grabs within the document act as grabbing the icon in the address bar.
* Dragging links to whitespace opens the link in new tab or window
* Highlighting text causes it to be treated as a link in all of it's functionality, including the I'm feeling lucky Google search. If the highlighted text is a valid URL but not formated link (clickable) then open in new tab.
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object
* Opera has a nifty feature with it's Mouse Gestures when you visit an Apache Directory Index or a Gallery site, and a few other sites. When you are on the index, you can just "go forward" in an imaginary history and it will start with the first link. Continuing going forward, will result in the second link, third link, etc... And when you've seen them all - you're back at the Index page.

== Javascript Links ==
* 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.
; References
* See {{bug|55696}}

== Tab Refresh ==
* Allow to refresh Tabs automatically by a counter
** When a change is made to the page on a reload, the tab should change visually

== Independent tabs ==
* The main browser interface should be on a thread that MUST never stop responding (and have a bigger priority). Each tab, should have it's own thread used to fill it's content. If a web page from inside one tab stops responding (or takes too much to load - such as big pdf files or sites that use java - but not resticted to those) the tab should be coloured in a different way (and maybe some text: the web page is not responding). The user MUST be able to either stop , go back, or close the tab, even if the content is not responding. It's VERY anoying now if I open lots of tabs, and the last stops responding, I must close the browser. (true the session restoration is a good step, but it's only a workaround, not the real solution to the problem).

== Quick Top of page/Bottom of page ==
* 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.
* Duplicates Ctrl-Home / Ctrl-End functionality. Would an extra icon to do this be useful?

== Uploading Files ==
Auto-zip multiple files in upload dialog
* Implement multiple file selections in the upload dialog that automatically generates a archive (.zip) for easy transmissions of many files.
* After selecting multiple files a dialog shall appear that asks for the file name of the archive (to be transmitted, auto-naming already included) and confirms the archive type (.zip/.tar.gz/whatsoever)

== Support drag and drop files from OS into a text box / text area ==
* Dragging a file icon from an OS file browser window should drop the name of the file in the target text box. Main use would be for uploading files, but it can be convenient for any other case when a file name and path must be used. It would be a must-have for web-based Document Management Systems, like [http://www.egroupware.org eGroupWare's] DMS.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=50660 bug 50660] and [https://bugzilla.mozilla.org/show_bug.cgi?id=347178 bug 347178]
* [http://slashdot.org/comments.pl?sid=200759&cid=16438433 A comment on Slashdot that gives a nice example of the problem]
* [http://e-vertise.com/dragtext/feature.html What DragText does] in OS/2.

== Dynamic Font Support ==
Support dynamic font such as prf, eot or svg. Considering the huge advancements made in with SVG in the Firefox browser, I really can't see any excuse for NOT including this technology.

From a designer's point of view it makes just about the '''most''' amount of sense - with IE4 onwards supporting font embedding, gifting this technology to FF would just about cover 99% of browsers - the possibilities from a typography point of view are fantastic.
; References
* [http://www.laakshmi.com/aarre/wp/archives/36 this blog]

;Comments

No. Firefox should support dynamic FON, TTF and OTF fonts. --[[User:Alenonimo|Alenonimo]] 15:43, 27 October 2006 (PDT)

== Syntax Highlightning ==
* Devloper aware syntax highlightning
** No language includes these words &nbsp;, <th> and such. The spellchecker should know about symbols used by developers, bloggers and wikiwriters and not to highlight them as a syntax error at least.

== Linux compatibility ==
* Render embedded buttons with native GTK2 widgets
* 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!)
* 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.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].
* 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].

== Mac OS X compatibility ==
* Support Command-Option-F to select search toolbar (standard for Mac applications).
* Render embedded buttons with native Aqua widget
* Dragging favicon to bookmark bar: Expand bookmark folders for bookmark placement when hovering -- FF 1.X+ under other OS's have been able to do this.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=299185 bug #299185]
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=136524 bug #136524]

== Long term target ==
On a long term basis Mozilla has come to a cross-road. The current XUL technology can't be used on a PAD/Smart phone nor on an OLPC. Yet there's a need for such a browser/mailer and it's just a matter of time somebody starts such a project. But I'm sure if such a browser/mailer gets built, it will be ported to the ordinary desktops slowly starting to replace Mozilla. And since switching technologies isn't a task done in a few weeks this subject has to be taken care of ASAP.

IMO it's important for Mozilla to start a task force now to think about the long term future. The PDA/Smart phones are already on the market almost exclusively using IE/Outlook and the OLPC and other embedded devices is just on the brink. So the pressure of this task, to prevent Mozilla from lagging behind again, is imminent.

== Evaluating the future of XUL ==
* It's essential to first evaluate XUL in the light of new requirements, especially about new devices ranging from the OLPC to embedded devices.

== Evaluating possible alternatives ==
* Alternatives should be based on the cornerstone "runs anywhere". Possible is IMO only wxWidgets yet others like Java or .Net/Mono should be rated against XUL as well.

== More vs. Less ==
Well it seems like we could divide 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.

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 interested 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.

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.

== "Core Firefox" & "More Firefox" (Packaging options) ==
* 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:
** A Firefox "Core" with just essential features (based upon XULRunner...)
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".
* 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.
; References
* [http://wiki.mozilla.org/User_talk:Folletto#Firefox_Core_.2B_More Firefox Core + More]

; Commentary
: 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.

=== Extension packs ===
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.

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.

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.

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)

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.

I love the idea of official extensions! And I'd definately like the ability to strip down firefox to the core. This method of development and packageing gets my vote!

Perhaps the installer could be a bit more than just Core & More. You could for example have a check box for extra features, and another for web development tools. Each check box could be expanded to get individual extensions like no-script.

And of course the defaults will be well chosen.

The more functionality you add, the more words and submenus have to be created. And both is confusing for beginners and older folks. What is the difference between words, that seem to mean the same thing at first glance ? Do I have to understand "all these new words" like "javascript", "PlugIn" ? Keep in mind, not all of the users are like the Techies who develop !

Firefox already has all the necessary stuff. There must always be an easy way for "lightweight-users" to use firefox without getting confused about words, large submenus or confusing questions.

The more functions, the more words, the more confusion. Please, always offer an easy way for the non-techie user ... !

I agree that a much smaller (memory) footprint is needed (even on desktop systems), and love the extension pack idea. I'd like to also strongly suggest looking at the reason for the memory size with the current feature set - 225 MB with just 3 tabs open just seems like too much.

The subject of More vs. Less is quite interesting. A good starting point might be to ask "what recent features are being used?". In that vein, maybe one of the "pre-release" versions could be "instrumented" to count the features used and (with the permission of the user, of course) report back those. Another way might be to do a web crawl, and see what features are used by various "popular" web sites. As with ANY feature set, one should realize that "growing featureism" is a very slippery slope. I suspect that many web users would be content with the features of an older browser (say back to 1999) to do their work. Remember that each added "feature" involves code, and with any new code comes both bugs and vulnerabilities. The user community wants neither.

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!).

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.

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!

(removed further repetitive commentary here)

== Customizable extension sets ==
The ability for each user to create, save, install, and manage "feature (extension) sets".

== Rich Internet Application Support ==
There is an opportunity here to lead the way in supporting the growing number of DHTML- and Ajax-heavy applications and to provide the browser support needed to eliminate some of the drawbacks of these apps. In all cases a security model will be necessary, probably including some automated safeguards and some user confirmations.

=== Preloaded javascript libraries ===
* with AJAX large javascript libraries (e.g. "dojo.js") have to be downloaded which need a lot of time. It would be nice if such libraries could be downloaded local in the background and taken from this local store instead of downloaded from the web when referenced by a page. This would speed up any AJAX page considerably. Which libraries are handled this way may be configured in the "offline" settings.

=== Local filesystem access ===
* Allow pages to request access to the local filesystem or some subset thereof (for example, a user's home directory, desktop, or docs folder) for reading and/or writing.<br />
<b>Hear hear!</b> This would enable productivity applications on the web far beyond what we can do today. Mozilla has an opportunity to create a standard API for local storage.

=== Access to global UI elements (menubar, taskbar, panels...) ===
* Allow a page to request access to major OS-level global UI elements like a first-class application. Such elements include the Mac menubar, Windows taskbar, GNOME/KDE panels, Mac Dock, etc. Some are more important than others; for example, being able to write menus to the global menubar is far more important on the Mac platform than Dock access. However, Dock access on the Mac is probably more important than taskbar access on Windows because Windows will already have an entry for each browser window (though being able to define that window's icon would be nice so users can distinguish between "regular" browser windows and in-browser apps).

=== Enhanced clipboard integration ===
* Provide APIs to allow non-text apps to manipulate the system clipboard/pasteboard more.

=== More robust file uploads ===
* Provide single- and multi-select access to standard OS Open dialogs for opening/uploading files. Include an upload manager for asynchronous uploads. Include functionality to resume interrupted uploads. For apps that store data, combine with local filesystem access to allow easy setup of sites that keep local and remote data seamlessly synchronized.

:; Commentary
:: A standardized synchronization protocol would really help on this one. Why does every photo site need to make their own bulk uploader? A sync protocol could send the sha1 of the files in the local directory tree to the server and then let server request upload of the files that it is missing. Even better, make this a two way sync protocol.

== An alternative view of the web browser ==
* Firefox as a new kind of desktop manager.
* Active front end.
; References
* [[User:Anonymous42|Some thoughts]]

== Enabeling new Top-Level-Domains (TLDs) on browser basis ==
* Top-Level-Domains for regions, cities and others
* Top-Level-Domains with IDN characters

The ICANN process for getting approval for a new TLD is quite slow and very stressful for TLD applicant. Making new and by ICANN not yet approved TLDs available could help to foster the development of the DNS. Firefox could easily enable lots of new TLDs and thereby give regional, cultural, linguistic or ethnic communities the opportunity to present themselves by an own identifier. Not to split up the Internet there can be only domains at those TLDs available for which the community indicates to apply at ICANN for an official approval of their TLD.

; References
* [[User:Dotzone|New Top-Level-Domains]]

== Annotations ==
I think it would be really great if there would be enhanced possibilities of graphical marks. It's tough to explain. I think of an complicated scientific text. If I print such a text. I highlight some words, cross other chapters out, add some notes. That's the big advantage of printing a page. If I could mark within a browser wouldn't have to print the page. I could work on screen.

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

== Offline browsing ==
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.

== Thunderbird in a tab ==
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.
== All Mozilla applications in a tab ? ==
Why not opening FileZilla, ChatZilla, etc... in a tab : it's kind of firefox suite ... but the programs are installed separately to avoid one heavy program and get several light ones. Firefox could become an interface for any Mozilla program installed by opening it in a tab.

== Bookmark behaviour ==
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.)

; Comments

Firefox should Import/Export with more formats. XBEL, xFolk, OPML or even create a new one. Support for tags would be cool too. --[[User:Alenonimo|Alenonimo]] 15:48, 27 October 2006 (PDT)

== Socket connection ==
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>
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, like so:

mySocket = new SocketClient("tcp://domain.com/application");
mySocket.onData = processReponse();
mySocket.connect();

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.

== HTTP Sniffer ==
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.
; References
* http://www.httpwatch.com/
* http://tamperdata.mozdev.org/
; Commentary
: Should this functionality really be in the browser itself, when there are things like [http://www.parosproxy.org/index.shtml Paros Web Proxy]?
: Sometimes we are required to use a different proxy (e.g. in corporate networks). Besides, when using HTTPS and gzip compression of pages, the external sniffer will not show the contents of the page. It would be better to sniff by means of the browser itself (both for outgoing requests and for incoming pages, when they are about to be encoded or have already been decoded, respectively, ''by browser''), and to be able to manage these requests in the browser and/or extensions (allow, deny, save, redirect etc.).

== Security ==
* I see many attacks upcoming, which manipulate the DOM-tree inside the browser, altering transactions in banking-systems a.s.o.
* What i wish for Firefox is, to have ONLY signed extensions!
* I want a default block of all extensions to manipulate SSL-protected sites.
This security-feature will be a boost for the usage of Firefox, because all banks will promote FF.

== Flexible table element selection and copy ==
For example, select and copy a column (or columns) from a html table
* Press Ctrl/Cmd when selecting

== User dictionaries ==
I have an existing "user.dic" dictionary, and a couple of specialist dictionaries ("avifauna.dic", "lepidoptera.dic"). They are used by several of my apps, including my e-mail client (Turnpike) and various MS Office apps. I should be able to direct FF to use the former as its dictionary to which new words are added, and to check against all of them when spell-checking.

Also, when the word I'm spell checking is at the bottom of the window, then the suggested replacements should be at the bottom of the context menu.

== Various ==
* Move all MPL code to GPL

== Better Support for Web Apps ==
See my [[User_talk:FunTomas|article]] on that topic.

==Memory management==
Try to minimize the memory usage of Firefox. May be we can have one feature (one button click), which enables the browser to run with minimum feature and there by reducing the memory usage.

==Save web pages in pdf or odt format==
Allow save html pages in pdf or odt format.

==Spell-check support for multiple languages==
I'm doing a doctorate in a French university, on databases, and I'm Romanian. This means that I mail/post/write things in French, English and Romanian all the time, sometimes even in the same text box. I'd like a way to tell FF what languages I'm likely to use so that it can use those dictionaries at the same time. If it's really smart, it should also detect what language each sentence/paragraph/text-box is after a few words and restrict the dictionary automatically to that language. And, perhaps, it should use a different underline color for words that are not in the "current language" dictionary but are in another "in use" dictionary, for cases of [http://en.wikipedia.org/wiki/Code-switching code-switching] (it happens very often when discussing computer-related things in another language than English).

==Restart==
Restart the firefox browser, but restore the session. So that you can get extensions working without losing all your tabs etc.

; Comments

That's implemented already. Just change the Home Page settings to load your previous session. --[[User:Alenonimo|Alenonimo]] 15:49, 27 October 2006 (PDT)

==Built-in Flash Support==
Forget about SVG and Canvas, build an open source Flash implementation into the browser and get rid of the plugin. You could start from gnash http://www.gnu.org/software/gnash/ Use the MIT license and give the source code to Microsoft, they might even help write it.

==PopUp Blocker==
The popup blocker need not have the "Options" button at the end. Instead, clicking anywhere on the popup blocker, we should be able to bring the pop-up blocker options menu (ala IE). Also, add the "Temporarily allow pop-up for this page" option to the main options menu.

==CPU usage when minimized==
Stop flash animations and other CPU power stealers when Firefox window is not selected or is minimized, and for no selected tabs.

==New User Agent string layout==
The actual User Agent strings are confusing and should be deprecated. Firefox 3 could use an User Agent strings simmilar to Opera. Ex:

Firefox/3.0 (Windows NT 5.0; U; pt-BR)

Or yet:

Gecko/1.9 (Windows XP; pt-BR) Firefox 3.0

--[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

==Process Isolation for each Web Site==
With web browsers becoming the de facto application launchers in desktops and several web applications (e.g. gmail) being used continuously, it is very important that an ill-behaved web site is not able to crash the entire web environment. At most, it should crash itself, without affecting the other web sites showing on other windows/tabs or requiring firefox to restart.
[[User:Mrcgran|Mrcgran]] 19:34, 27 October 2006 (PDT)

==Independent sessions per tab/window==
Currently, any web browser I am aware of shares sessions across all instances of the browser (windows/tabs). It would be nice to separate a window or tab and create a new session within it. This would allow you to have, say, two different GMail accounts logged-in at the same time without needing to have two different web browsers.

==Won't comeback button==
In order to minimize the "leak" of memory that the "quick back" and "quick forward" features use we should have an button "I won't come back" this will close the tab and unload everything it had in the memory so that if you close every tab the memory usage will drop back the their 30-40MB that are used on start. Also we should allow the user to define this as his/her normal closing button (so if you close the tab and have that option checked will unload automatically the memory).

==Easier tildes, ñ and Cyrillic characters==
I usually use the ZombieKeys for that, however in some text areas I can't use it, and it seems that the creator of that extension will no longer update it, so, we should have it "by default" (sadly ala IE7). This could be an extra extension (also might be an extension for Cyrillic characters) because I agree with the core/more Firefox movement.

Firefox/Feature Brainstorming:Other or Uncategorized

2006-11-04T06:32:33Z

Carutsu: Won't come back button

{{FeatureBrainstorming}}

== Widgets ==
* In my opinion, that's the only feature lacking in Firefox to create first-quality "mozlets", similar to the Opera's widgets or Safari's dashboard (if not better, since Opera's widget goes nowhere farther than using XShape).

== Editions ==
* Create several Editions for example standard edition, web developer edition, low memory edition, kid's edition, or even google edition

== "Open page in another browser" option ==
* Simple, useful, and easy to implement.

== Conditional Comments ==
Allow users to add CSS filters for version compatibility that doesn't rely on a CSS rule being implemented. Arguably, this is the unofficial standard for dealing with Internet Explorer bugs and it would be nice to have a simple interface for doing this with any browser (just in case things change later on down the line). The syntax should be about the same, so something like  would be appropriate.

; Comments
That's a very good idea! It could prevent use of CSS hacks in future. Opera could do that too. --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Glow Text ==
Allows text to Glow when the glow HTML command is used, such as in IE7.

== Page autorefresh ==
Create a new "Automatically page refresh" submenu in page's content menu (and inside "In this frame" submenu). It might contain items like "Stop autorefresh", "5 seconds", "10 seconds", "1 minute", "5 minutes", "Custom...". The page should be automatically refreshed untill "Stop autorefresh" selected or user navigated away from the page. In case of page was loaded by 'POST' command the new item should be "disabled" or user might be asked about "repost data every time".

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

; References
* [http://en.wikipedia.org/wiki/Synesthesia Synesthesia] (wikipedia)

; Commentary
: It shouldn't be user picked, but extracted in some ways from the URL domain and optionally changed by a meta tag in the XHTML. This is important to make it a useful feature for both sites and communications (on other computers, the same site will have the same colour). Also it doesn't overload unneeded customization.

== Propietary Anchor mode ==
Many pages don't have anchors so linking to Content that is somewhere on the page can be a pain. Make possible custom anchors like this would make firefox scroll 0pixel to left and 555pixel down:

url#custom(0,555)

This make firefox scroll to the 5th H1 element on the page and highlight it decently:

url#custom(h1/5)

; References
* [http://www.w3.org/TR/xptr-framework/ XPTR framework]

; Commentary
* Pixels are unsafe (depending on fonts, zooming etc.)
* This looks like reinventing the wheel. use xpath instead?
* This implies support for XPointer

== Smooth vs Raw Page Transitions ==
There isn't any *good* point to have the previous page "visible but unusable" until the new page starts rendering, a block a time. This is aesthetically awful and without any useful gain at the UI level.

=== Details & Commentary ===
'''Smooth Page Transition''': when someone clicks on a link, the page will slightly fade out, indicating that it is refreshing until the new page is fully ready, when a smooth (really '''fast''' crossfade <0.5sec, maybe). On the page there should be some form of interaction that could allow to see - and browse, and use - the previous page until the new is fully loaded AND the possibility to switch to the new one, displaying it a block a time.
* If implementing this, Firefox could adhere to some of IE page/site transition definitions from HTTP response or meta http-equiv headers.
** Please no: this is a step back in the past using BAD transitions that were just annoying. This feature, as stated, is conceptually '''DIFFERENT''' and must NOT be assimilated with the IE page transitions.
* The point here is to make the navigation softer and nicer for everyone (cool-factor), not only occasional user, and behaving more like an offline app. The '''"freeze page, load the other one block a time" is obsolete''' and should be improved into a new form of page transition: unobtrusive, aesthetically pleasant and without drawbacks (on slow connection, seeing the page loading a block a time is useful, don't avoid it if needed).
* To be clear: this is COMPLETELY different from the "page transitions" concept seen before on some browsers as site behaviour. This should be an integrated feature, well balanced and ''without annoying drawbacks''. Also, this should be default but disabled.
* The interaction could be:
** On a full-page location refresh (i.e. non javascript) the current page should be lightly dimmed until the new page is ready.
** When the new page is ready, a fast crossfade should display it.
** If the page loads slowly, clicking on Forward (a button not really used since now) will show the page loading a block a time, like now.
** If the user clicks on the dimmed "old" page, it could interact with it until the new page is ready (and faded in). Any click event of course blocks the page load (and the Forward button will turn disabled).

; References
* [http://wiki.mozilla.org/User_talk:Folletto#Smooth_Page_Transitions Smooth Page Transitions]

== Mouse gestures ==
Allow the user to use mouse gestures (like right click followed by left click for 'back' etc)...

; References
* [http://www.opera.com/products/desktop/mouse/index.dml Opera Mouse Gestures]
* [https://addons.mozilla.org/search.php?q=Rocker&app=firefox Plugins providing this functionality]

== Link navigation using arrow keys ==
* Using shift+arrowKey, the selection "hovers" to the nearest link in that direction
* With this feature remote controls can be configured to navigate pages
* Same as Opera feature

== Remote Control ==
Support for Red/Green/Yellow/Blue remote control buttons
* The ability to configure keyboard shortcuts to select HTML elements that have the accesskey attribute in the format: accesskey="{red}" | accesskey="{green}" | accesskey="{yellow}" | accesskey="{blue}"
* e.g. configure Alt-F1 to select the element with accesskey="{red}", Alt-F2 selects element with accesskey="{green}" etc
* With this feature the RGYB buttons of remote controls can be configured to select links
* This would make Firefox compatible with the Netgem iPlayer facility

== Scripting ==
* 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.
** Support for regular expressions so that pages with broken URLs can be fixed, HTML can be converted to another format, etc.

; References
* [http://greasemonkey.mozdev.org/ Greasemonkey]

== Patching display ==
Let the user configure the display of their page and 'patch' them.

For exemple, change some image, text disposition or even the whole design of the page using regular expression. (Maybe witch a WYGIWYS editor-like to be more user friendly ?)

(I used a while ago an adblock proxy who do that, but it's really slow, whith something directly coded in firefox, this will be great ! No more forum witch crap animated smilets if we can change them on client side)

I think about a way that users can themselfs modify a whole page, and submit their 'patchs' to a centralized server.

When an other user navigate on the page, he can use a button on the navigation page to switch between the different patches submitted by other people and vote for them.

So for one site, we will probably had a lot of version : Ad-free, Alternative design
(Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

== JavaScript Performance ==
JavaScript engine is too slow. When a script on page is become unresponsive - Firefox hangs, until window, proposing to stop that script appears. Enclosing enhancements are good, but functionality and quality are the main thing, we must to follow.

== PDF Reader ==
Make a quick-opening pdf reader, just for text. In other case, run adobe or similar

== Rename tabs ==
It would be useful if end users could rename tabs after opening. Oftentimes, pages with wildly disparate content have similar headings, particularly if browsing forums or newspages or anything where a lot of content comes from a single site. If you could take six tabs all saying "CNN.COM - YOUR SOURCE F..." and change each of them to the subject of the page, it would greatly simplify things.

It really does come up quite often, even if you use separate windows instead of tabs, that the data listed in the browser summary field is basically useless due to excessively long page titles. This does sound like a good feature.

''Note:'' (Sorry for my bad english, if you can reformulate my proposition more clearly, don't hesitate)

''Note:'' Done and done.

== Incorporate Wizz RSS ==
To incorporate the Wizz RSS. It becomes it native of the program.

== ActiveX ==
* Implement full ActiveX support
** including optional support via WINE under Linux

;Comments
No way! --[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

== Web services integration ==
Automatically create a web services test form by inspecting a URL to a WSDL file. For comparison, ASP.NET can do this by browsing to a web services URL like foo.asmx?wsdl

== Web mail integration ==
Following Firefox 2 support for online web feed readers, it could be extended to web mail services like Yahoo! Mail, Hotmail and Gmail at least. Users should be able to select one or more web mail providers and set a default or just keep the default stand alone email client. The idea is not to develop a complete email client but to provide minimum integration:
* New mail notification through an alert a la "Downloads complete"
* mailto: handling
* File/Send link... overlay
* More providers can be added with preferences for compose URL and new mail XPath

== Email pseudo-url ==
Presently the mailto: pseudo url simply opens up a mail client. In the old Netscape/Mozilla days, the mail client was part of the package, so it wasn't necessarily such an issue.
Perhaps Firefox could incorporate a lite smpt component which could actually send off data, perhaps as part of a form's action.

== Explorer files integrated ==
Firefox 3.0 should integrate a file explorer of your system, while having the same characteristics as a web page: Tabs, mouse gestures, bookmarks. etc.

== Explorer integration (Windows) ==
In Windows allow file system browsing (ie C:\windows), perhaps by calling on MSHTML APIs.
* Preferably using default file manager -open Koqueror in the current tab when a local directory path is entered

In Windows, allow Firefox to change global settings for preferred browser; not only changing preferred browser for files-types, but also to change what browser applications start when they want to access a webpage.

== Link Activation ==
* Allow popup windows (ones that don't currently work in tabs) to appear in tabs.
* Add option to pre-process Javascript (and Flash?) links - enable MMB/CTRL-click to open these in new tab, by tracking the target before obeying the command
* Improved functionality when opening embedded Windows Media Player video files.
* When hovering over a link, show its target in status bar (e.g. "Open http://example.com/ in a new tab") as in Safari.
* Allow the user to draw a box on the webpage that launches all links within the box bounds, as new tabs
* User key for this could be MMB, Drag or a modifier key with LMB, Drag.
* if a large number of links are selected, a confirmation box could ask weather this was the users intention.
* 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.
*Text highlighted that starts with http:// can be opened in a new tab by dragging the selected text upward.
*Any link will open in a new tab if dragged in any direction rather than being clicked.
*Boss key, hot key combo that minimizes and removes from task bar, same combination brings it back.
*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.
*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
*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.
* 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.
* An integrated prefetching mechanism (use free bandwith to load in background all the static pages linked from the page) - similar to Fasterfox plugin.
* After i click Shift + click of link i open a link in other window. Now Gecko focuses a loaded window after loading but it's very bad! I suggest to do not focus loaded windows after a loading page through "Shit + click of link". It puts off from browsing :(
* Same as the one above when reading email with several links: Every click on a link brings FF to focus. Better would be keeping FF in background so that one can read the whole mail undisturbed.
* Make an option that Ctrl+Alt+Click, or some other combination, that will open a "preview" of the like page in a "bubble" or some other form of preview.

; References
* [https://addons.mozilla.org/firefox/1269/ Fasterfox plugin]

== Link Context Menu ==
* Add a command to open selected text in a new tab/window.
* 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.
; References
* https://addons.mozilla.org/firefox/1472/

== Additional Mouse Interactivity ==
* Whitespace grabs within the document act as grabbing the icon in the address bar.
* Dragging links to whitespace opens the link in new tab or window
* Highlighting text causes it to be treated as a link in all of it's functionality, including the I'm feeling lucky Google search. If the highlighted text is a valid URL but not formated link (clickable) then open in new tab.
* Shift-click, alt-click or whatever on any graphical object (animated gif, flash etc.) hides the object
* Opera has a nifty feature with it's Mouse Gestures when you visit an Apache Directory Index or a Gallery site, and a few other sites. When you are on the index, you can just "go forward" in an imaginary history and it will start with the first link. Continuing going forward, will result in the second link, third link, etc... And when you've seen them all - you're back at the Index page.

== Javascript Links ==
* 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.
; References
* See {{bug|55696}}

== Tab Refresh ==
* Allow to refresh Tabs automatically by a counter
** When a change is made to the page on a reload, the tab should change visually

== Independent tabs ==
* The main browser interface should be on a thread that MUST never stop responding (and have a bigger priority). Each tab, should have it's own thread used to fill it's content. If a web page from inside one tab stops responding (or takes too much to load - such as big pdf files or sites that use java - but not resticted to those) the tab should be coloured in a different way (and maybe some text: the web page is not responding). The user MUST be able to either stop , go back, or close the tab, even if the content is not responding. It's VERY anoying now if I open lots of tabs, and the last stops responding, I must close the browser. (true the session restoration is a good step, but it's only a workaround, not the real solution to the problem).

== Quick Top of page/Bottom of page ==
* 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.
* Duplicates Ctrl-Home / Ctrl-End functionality. Would an extra icon to do this be useful?

== Uploading Files ==
Auto-zip multiple files in upload dialog
* Implement multiple file selections in the upload dialog that automatically generates a archive (.zip) for easy transmissions of many files.
* After selecting multiple files a dialog shall appear that asks for the file name of the archive (to be transmitted, auto-naming already included) and confirms the archive type (.zip/.tar.gz/whatsoever)

== Support drag and drop files from OS into a text box / text area ==
* Dragging a file icon from an OS file browser window should drop the name of the file in the target text box. Main use would be for uploading files, but it can be convenient for any other case when a file name and path must be used. It would be a must-have for web-based Document Management Systems, like [http://www.egroupware.org eGroupWare's] DMS.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=50660 bug 50660] and [https://bugzilla.mozilla.org/show_bug.cgi?id=347178 bug 347178]
* [http://slashdot.org/comments.pl?sid=200759&cid=16438433 A comment on Slashdot that gives a nice example of the problem]
* [http://e-vertise.com/dragtext/feature.html What DragText does] in OS/2.

== Dynamic Font Support ==
Support dynamic font such as prf, eot or svg. Considering the huge advancements made in with SVG in the Firefox browser, I really can't see any excuse for NOT including this technology.

From a designer's point of view it makes just about the '''most''' amount of sense - with IE4 onwards supporting font embedding, gifting this technology to FF would just about cover 99% of browsers - the possibilities from a typography point of view are fantastic.
; References
* [http://www.laakshmi.com/aarre/wp/archives/36 this blog]

;Comments

No. Firefox should support dynamic FON, TTF and OTF fonts. --[[User:Alenonimo|Alenonimo]] 15:43, 27 October 2006 (PDT)

== Syntax Highlightning ==
* Devloper aware syntax highlightning
** No language includes these words &nbsp;, <th> and such. The spellchecker should know about symbols used by developers, bloggers and wikiwriters and not to highlight them as a syntax error at least.

== Linux compatibility ==
* Render embedded buttons with native GTK2 widgets
* 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!)
* 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.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=232553 bug #232553].
* 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].

== Mac OS X compatibility ==
* Support Command-Option-F to select search toolbar (standard for Mac applications).
* Render embedded buttons with native Aqua widget
* Dragging favicon to bookmark bar: Expand bookmark folders for bookmark placement when hovering -- FF 1.X+ under other OS's have been able to do this.
; References
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=299185 bug #299185]
* See [https://bugzilla.mozilla.org/show_bug.cgi?id=136524 bug #136524]

== Long term target ==
On a long term basis Mozilla has come to a cross-road. The current XUL technology can't be used on a PAD/Smart phone nor on an OLPC. Yet there's a need for such a browser/mailer and it's just a matter of time somebody starts such a project. But I'm sure if such a browser/mailer gets built, it will be ported to the ordinary desktops slowly starting to replace Mozilla. And since switching technologies isn't a task done in a few weeks this subject has to be taken care of ASAP.

IMO it's important for Mozilla to start a task force now to think about the long term future. The PDA/Smart phones are already on the market almost exclusively using IE/Outlook and the OLPC and other embedded devices is just on the brink. So the pressure of this task, to prevent Mozilla from lagging behind again, is imminent.

== Evaluating the future of XUL ==
* It's essential to first evaluate XUL in the light of new requirements, especially about new devices ranging from the OLPC to embedded devices.

== Evaluating possible alternatives ==
* Alternatives should be based on the cornerstone "runs anywhere". Possible is IMO only wxWidgets yet others like Java or .Net/Mono should be rated against XUL as well.

== More vs. Less ==
Well it seems like we could divide 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.

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 interested 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.

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.

== "Core Firefox" & "More Firefox" (Packaging options) ==
* 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:
** A Firefox "Core" with just essential features (based upon XULRunner...)
** A Firefox "More" with many features, released WITH Firefox as Extensions, by the Mozilla Firefox development team, and updated in sync with Firefox "Core".
* 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.
; References
* [http://wiki.mozilla.org/User_talk:Folletto#Firefox_Core_.2B_More Firefox Core + More]

; Commentary
: 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.

=== Extension packs ===
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.

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.

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.

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)

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.

I love the idea of official extensions! And I'd definately like the ability to strip down firefox to the core. This method of development and packageing gets my vote!

Perhaps the installer could be a bit more than just Core & More. You could for example have a check box for extra features, and another for web development tools. Each check box could be expanded to get individual extensions like no-script.

And of course the defaults will be well chosen.

The more functionality you add, the more words and submenus have to be created. And both is confusing for beginners and older folks. What is the difference between words, that seem to mean the same thing at first glance ? Do I have to understand "all these new words" like "javascript", "PlugIn" ? Keep in mind, not all of the users are like the Techies who develop !

Firefox already has all the necessary stuff. There must always be an easy way for "lightweight-users" to use firefox without getting confused about words, large submenus or confusing questions.

The more functions, the more words, the more confusion. Please, always offer an easy way for the non-techie user ... !

I agree that a much smaller (memory) footprint is needed (even on desktop systems), and love the extension pack idea. I'd like to also strongly suggest looking at the reason for the memory size with the current feature set - 225 MB with just 3 tabs open just seems like too much.

The subject of More vs. Less is quite interesting. A good starting point might be to ask "what recent features are being used?". In that vein, maybe one of the "pre-release" versions could be "instrumented" to count the features used and (with the permission of the user, of course) report back those. Another way might be to do a web crawl, and see what features are used by various "popular" web sites. As with ANY feature set, one should realize that "growing featureism" is a very slippery slope. I suspect that many web users would be content with the features of an older browser (say back to 1999) to do their work. Remember that each added "feature" involves code, and with any new code comes both bugs and vulnerabilities. The user community wants neither.

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!).

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.

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!

(removed further repetitive commentary here)

== Customizable extension sets ==
The ability for each user to create, save, install, and manage "feature (extension) sets".

== Rich Internet Application Support ==
There is an opportunity here to lead the way in supporting the growing number of DHTML- and Ajax-heavy applications and to provide the browser support needed to eliminate some of the drawbacks of these apps. In all cases a security model will be necessary, probably including some automated safeguards and some user confirmations.

=== Preloaded javascript libraries ===
* with AJAX large javascript libraries (e.g. "dojo.js") have to be downloaded which need a lot of time. It would be nice if such libraries could be downloaded local in the background and taken from this local store instead of downloaded from the web when referenced by a page. This would speed up any AJAX page considerably. Which libraries are handled this way may be configured in the "offline" settings.

=== Local filesystem access ===
* Allow pages to request access to the local filesystem or some subset thereof (for example, a user's home directory, desktop, or docs folder) for reading and/or writing.<br />
<b>Hear hear!</b> This would enable productivity applications on the web far beyond what we can do today. Mozilla has an opportunity to create a standard API for local storage.

=== Access to global UI elements (menubar, taskbar, panels...) ===
* Allow a page to request access to major OS-level global UI elements like a first-class application. Such elements include the Mac menubar, Windows taskbar, GNOME/KDE panels, Mac Dock, etc. Some are more important than others; for example, being able to write menus to the global menubar is far more important on the Mac platform than Dock access. However, Dock access on the Mac is probably more important than taskbar access on Windows because Windows will already have an entry for each browser window (though being able to define that window's icon would be nice so users can distinguish between "regular" browser windows and in-browser apps).

=== Enhanced clipboard integration ===
* Provide APIs to allow non-text apps to manipulate the system clipboard/pasteboard more.

=== More robust file uploads ===
* Provide single- and multi-select access to standard OS Open dialogs for opening/uploading files. Include an upload manager for asynchronous uploads. Include functionality to resume interrupted uploads. For apps that store data, combine with local filesystem access to allow easy setup of sites that keep local and remote data seamlessly synchronized.

:; Commentary
:: A standardized synchronization protocol would really help on this one. Why does every photo site need to make their own bulk uploader? A sync protocol could send the sha1 of the files in the local directory tree to the server and then let server request upload of the files that it is missing. Even better, make this a two way sync protocol.

== An alternative view of the web browser ==
* Firefox as a new kind of desktop manager.
* Active front end.
; References
* [[User:Anonymous42|Some thoughts]]

== Enabeling new Top-Level-Domains (TLDs) on browser basis ==
* Top-Level-Domains for regions, cities and others
* Top-Level-Domains with IDN characters

The ICANN process for getting approval for a new TLD is quite slow and very stressful for TLD applicant. Making new and by ICANN not yet approved TLDs available could help to foster the development of the DNS. Firefox could easily enable lots of new TLDs and thereby give regional, cultural, linguistic or ethnic communities the opportunity to present themselves by an own identifier. Not to split up the Internet there can be only domains at those TLDs available for which the community indicates to apply at ICANN for an official approval of their TLD.

; References
* [[User:Dotzone|New Top-Level-Domains]]

== Annotations ==
I think it would be really great if there would be enhanced possibilities of graphical marks. It's tough to explain. I think of an complicated scientific text. If I print such a text. I highlight some words, cross other chapters out, add some notes. That's the big advantage of printing a page. If I could mark within a browser wouldn't have to print the page. I could work on screen.

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

== Offline browsing ==
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.

== Thunderbird in a tab ==
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.
== All Mozilla applications in a tab ? ==
Why not opening FileZilla, ChatZilla, etc... in a tab : it's kind of firefox suite ... but the programs are installed separately to avoid one heavy program and get several light ones. Firefox could become an interface for any Mozilla program installed by opening it in a tab.

== Bookmark behaviour ==
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.)

; Comments

Firefox should Import/Export with more formats. XBEL, xFolk, OPML or even create a new one. Support for tags would be cool too. --[[User:Alenonimo|Alenonimo]] 15:48, 27 October 2006 (PDT)

== Socket connection ==
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>
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, like so:

mySocket = new SocketClient("tcp://domain.com/application");
mySocket.onData = processReponse();
mySocket.connect();

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.

== HTTP Sniffer ==
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.
; References
* http://www.httpwatch.com/
* http://tamperdata.mozdev.org/
; Commentary
: Should this functionality really be in the browser itself, when there are things like [http://www.parosproxy.org/index.shtml Paros Web Proxy]?
: Sometimes we are required to use a different proxy (e.g. in corporate networks). Besides, when using HTTPS and gzip compression of pages, the external sniffer will not show the contents of the page. It would be better to sniff by means of the browser itself (both for outgoing requests and for incoming pages, when they are about to be encoded or have already been decoded, respectively, ''by browser''), and to be able to manage these requests in the browser and/or extensions (allow, deny, save, redirect etc.).

== Security ==
* I see many attacks upcoming, which manipulate the DOM-tree inside the browser, altering transactions in banking-systems a.s.o.
* What i wish for Firefox is, to have ONLY signed extensions!
* I want a default block of all extensions to manipulate SSL-protected sites.
This security-feature will be a boost for the usage of Firefox, because all banks will promote FF.

== Flexible table element selection and copy ==
For example, select and copy a column (or columns) from a html table
* Press Ctrl/Cmd when selecting

== User dictionaries ==
I have an existing "user.dic" dictionary, and a couple of specialist dictionaries ("avifauna.dic", "lepidoptera.dic"). They are used by several of my apps, including my e-mail client (Turnpike) and various MS Office apps. I should be able to direct FF to use the former as its dictionary to which new words are added, and to check against all of them when spell-checking.

Also, when the word I'm spell checking is at the bottom of the window, then the suggested replacements should be at the bottom of the context menu.

== Various ==
* Move all MPL code to GPL

== Better Support for Web Apps ==
See my [[User_talk:FunTomas|article]] on that topic.

==Memory management==
Try to minimize the memory usage of Firefox. May be we can have one feature (one button click), which enables the browser to run with minimum feature and there by reducing the memory usage.

==Save web pages in pdf or odt format==
Allow save html pages in pdf or odt format.

==Spell-check support for multiple languages==
I'm doing a doctorate in a French university, on databases, and I'm Romanian. This means that I mail/post/write things in French, English and Romanian all the time, sometimes even in the same text box. I'd like a way to tell FF what languages I'm likely to use so that it can use those dictionaries at the same time. If it's really smart, it should also detect what language each sentence/paragraph/text-box is after a few words and restrict the dictionary automatically to that language. And, perhaps, it should use a different underline color for words that are not in the "current language" dictionary but are in another "in use" dictionary, for cases of [http://en.wikipedia.org/wiki/Code-switching code-switching] (it happens very often when discussing computer-related things in another language than English).

==Restart==
Restart the firefox browser, but restore the session. So that you can get extensions working without losing all your tabs etc.

; Comments

That's implemented already. Just change the Home Page settings to load your previous session. --[[User:Alenonimo|Alenonimo]] 15:49, 27 October 2006 (PDT)

==Built-in Flash Support==
Forget about SVG and Canvas, build an open source Flash implementation into the browser and get rid of the plugin. You could start from gnash http://www.gnu.org/software/gnash/ Use the MIT license and give the source code to Microsoft, they might even help write it.

==PopUp Blocker==
The popup blocker need not have the "Options" button at the end. Instead, clicking anywhere on the popup blocker, we should be able to bring the pop-up blocker options menu (ala IE). Also, add the "Temporarily allow pop-up for this page" option to the main options menu.

==CPU usage when minimized==
Stop flash animations and other CPU power stealers when Firefox window is not selected or is minimized, and for no selected tabs.

==New User Agent string layout==
The actual User Agent strings are confusing and should be deprecated. Firefox 3 could use an User Agent strings simmilar to Opera. Ex:

Firefox/3.0 (Windows NT 5.0; U; pt-BR)

Or yet:

Gecko/1.9 (Windows XP; pt-BR) Firefox 3.0

--[[User:Alenonimo|Alenonimo]] 15:41, 27 October 2006 (PDT)

==Process Isolation for each Web Site==
With web browsers becoming the de facto application launchers in desktops and several web applications (e.g. gmail) being used continuously, it is very important that an ill-behaved web site is not able to crash the entire web environment. At most, it should crash itself, without affecting the other web sites showing on other windows/tabs or requiring firefox to restart.
[[User:Mrcgran|Mrcgran]] 19:34, 27 October 2006 (PDT)

==Independent sessions per tab/window==
Currently, any web browser I am aware of shares sessions across all instances of the browser (windows/tabs). It would be nice to separate a window or tab and create a new session within it. This would allow you to have, say, two different GMail accounts logged-in at the same time without needing to have two different web browsers.

==Won't comeback button==
In order to minimize the "leak" of memory that the "quick back" and "quick forward" features use we should have an button "I won't come back" this will close the tab and unload everything it had in the memory so that if you close every tab the memory usage will drop back the their 30-40MB that are used on start. Also we should allow the user to define this as his/her normal closing button (so if you close the tab and have that option checked will unload automatically the memory).

Firefox/Feature Brainstorming:Security

2006-11-02T03:54:30Z

Carutsu:

{{FeatureBrainstorming}}
<table class="fullwidth-table">
<tr><th>Specific features</th>
<th width="30%">References</th></tr>

<tr><td>
; AJAX
* Ability to disable XMLHTTP* javascript calls entirely. AJAX rocks, but it could be a potential security threat (for example, I enter in my credit card number, and then think better of it. But too late! The asynchronous javascript has already sent my details back to some nefarious web site before I clicked "submit").
* Ability to see graphically if asynchronous calls are being made on my behalf (mabye add a flashing icon to the status bar?)
* Ability to selectively allow/disallow certain sites from using AJAX.
</td><td>
n/a
</td></tr>

<tr><td>
; Surf by IP protection
* Two new security options, which should be checked by default...
[ ] Disallow visiting sites by IP address (IP anywhere in the URL)<br>
[ ] Allow local LAN IPs<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.
</td><td>
n/a
</td></tr>

<tr><td>
; Download actions -- don't handle when requested
* Download actions -- add option "don't handle files like this". At the moment if the plugin exists, I can only select which application will open the file, but the file will always be downloaded. It should be possible to disable handling (and therefore also downloading) of some file type.
</td><td>
n/a
</td></tr>

<tr><td>
; Security preferences
* Automated user preference auditing with user notification of potentially problematic preference settings.
</td><td>
n/a
</td></tr>

<tr><td>
; Phishing protection
* Make it easier to report phishing sites
* Implement a phishing filter that learns automatically
** Consider intergration with something like PhishTank [http://phishtank.com]
* Multi-provider support for local list checking (depending upon provider demand)
* new approach: allow certificate whitelisting.
** Organizations could sign certificates not just (as today) in order to confirm the identity but to confirm that a web site belongs to the "good guys". Users could mark the certificate of such an organization as trustworthy. When displaying a site which has been approved that way the browser should mark it somehow (a green address field e.g.). This is just an infrastructure idea. If Firefox supports that people will start to offer whitelists. Whitelisting makes more sense than blacklisting - it's easier and safer. There are rather few web sites which are potential phishing targets so it should work.
</td><td>
certificate whitelisting - in German [http://www.hauke-laging.de/ideen/bsi-zertifikatsplugin/]
</td></tr>

<tr><td>
; Safer Browsing
* Like anti-phishing, but with a list of sites that are known or suspected of being a source of malware (virii, spyware, etc)
</td><td>
See [https://bugzilla.mozilla.org/show_bug.cgi?id=347849 bug 347849]
</td></tr>

<tr><td>
; Script execution
* Integrate script execution whitelisting
* Allow cross-site scripting between whitelisted sites (for mashups)
</td><td>
[http://noscript.net NoScript]

[https://bugzilla.mozilla.org/show_bug.cgi?id=320522 bug 320522]
</td></tr>

<tr><td>
; Pop-ups
* Implement one-click viewing of blocked pop-ups
* Make printing popup windows possible
* Implement a way to block every pop-up window, regardless of the way it was requested.
* Let the user allow temporally show pop-ups for a certain site (like IE). The way it is now, makes a hard to visit a site just once.
</td><td>
- [[User talk:ThomasWaldmann|More on printing pop-ups]]<br />
</td></tr>

<tr><td>
; Restricted Javascript
* Prevent window resizing
* Prevent hiding toolbar/controls
* Prevent capturing mouse events (overriding clicks, and obnoxious mouse-tracking scripts)
* Prevent floaters (or have some way to hide these layers)
* Prevent automatic form submission (or "Did you really want to submit this?")
* Trace window/panel with the history of form submissions and visited URLs, with the option of ask before submit everytime.
* 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 (for instance : http://users.etu.info.unicaen.fr/~pbour/)
* 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.
** Please, PLEASE don't forget Intranet and Web Application usage scenarios when considering the Restricted Javascript proposal. There are countless weblications that depend on one or more of the above. If the Javascript restrictions are not (at least) configurable, and possibly defaulted to 'no restrictions' for local or LAN-accessed files, then those applications will break or mis-function. [[User:Jabbott|Jabbott]] 10:32, 16 October 2006 (PDT)
</td><td>
n/a
</td></tr>

<tr><td>
; Cookies
* Add cookie whitelist funcitonality
* One-click block/allow cookies<sup>1</sup>
* Allow cookies from sites (on request) remain persistant even after the browser has been restarted
* Allow session cookies per window/tab so that multiple logins can be had to services such as gmail/hotmail simultaneously.<sup>2</sup>
* "Supercookies"
* Never accept cookies associated with invisuble images: single, pixel GIFs and so forth
* 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.
* 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.
* 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.
* 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.
* Cookie-Editor
* Support for non-"top-level" domains (e.g. don't allow cookies for .co.uk).

</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=252342 Fix cookie domain checks to not allow .co.uk]<br />
<sup>1</sup> Like "CookieCuller"<br />
<sup>2</sup> Like "CookiePie"<br />
</td></tr>
<tr><td>
; Exploit Mitigation
* 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.
**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.
**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)
</td><td>
For Windows samples see: [[User:SergioJ]]
</td></tr>

<tr><td>
; Extension installation
* One-click to permanently add site to whitelist
* One-click to temporarily add site to whitelist for this session
* Third-party signing and authentication by Mozilla
</td><td>
[[Firefox:1.5_Extension_and_Plugin_Blacklisting|Extension Blacklisting UI Spec]]<br />
</td></tr>

<tr><td>
; Virus/Malware protection
* Intergrate a sandboxing feature automatically. (Like Sandboxie -http://www.sandboxie.com/)
* Integrate virus scanning and malware protection for retrieved content/files
* Integrated support for 3rd party Anti-virus scanners
* Firefox to run in a "Protected mode" like IE7/Vista (see the Sandboxing above)
** See <b>Exploit Mitigation</b> comment above.
</td><td>
n/a
</td></tr>

<tr><td>
; Spoofing
* Employ some shared-secret anti-spoofing techniques<sup>1</sup>
* Prevent content and scripts from being able to spoof or mimic protected chrome
* SSL auth required for send password
** This is an optional, but strongly recommended feature suggested during install
** 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.
** Do not allow adding "*" to FORM.edit field from Javascript (avoid spoof)
** 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>
* Add some indication of which site produced a Javascript dialog, to prevent dialogs appearing to come from another site in a tabbed session.
* 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.
</td><td>
<sup>1</sup> [http://passpet.org PassPet]<br />
<sup>2</sup> [[User_talk:Csoma|details & discussion]]<br />
</td></tr>
<tr><td>
;Visualy showing server access

Show every server access (by a moving icon), including AJAX access (see above) and streaming, for example, not only standard HTTP access.

</td></tr>
<tr><td>
; New technology support
* Extended Validation Certificate support
* Integrated PGP/GPG to sign/encrypt/authenticate text (eg Web Mail)
</td><td>
n/a
</td></tr>

<tr><td>
; HTTP authentication improvements
* Support for logging out of basic or digest HTTP authentication (RFC 2617 style)
* Implement a somewhat secure HTTP shared-secret authentication scheme based on SRP. The RFC2617 schemes are both very vulnerable to phishing.
* Show content of 401-unauthorized pages, and add widgets to login via forms instead of modal dialogs
</td><td>
See [https://bugzilla.mozilla.org/show_bug.cgi?id=355319 bug 355319]
</td></tr>

<tr><td>
; Keychain support for MAC OS X / KDE / Gnome
* Save passwords in the OS-level Keychain on OS X, so that passwords can be shared between Safari / FIrefox / Camino / etc.
* Ability to switch to external password manager like kwallet etc. and to disable firefox standard password manager
</td><td>
n/a
</td></tr>

<tr><td>
; Parental Controls
* Filtering, prevent programs from being downloaded, keep sensitive information from being transmitted, monitoring, logging, etc.
* Should work with third party vendors to implement a set of baseline capabilities (that are somewhat commoditized) while providing awareness for higher value products and services.

</td><td>
n/a
</td></tr>

<tr><td>
; SSL Verification Levels
Certificate authorities offer a variety of different certificates. Some only check if the applicant has an Email (like admin or info) in the domain for which the certificate is requested. Some require the applicant to send in some proof of his/her identity.
* It would be nice to see the level of trust an ssl certicate has.
* Different Icons for different Levels of certificates would make my decision to trust a website easier.
* Certificate-Levels to think of: Domain validated, web of trust, Company identity validated, ...

</td><td>
n/a
</td></tr>

<tr><td>
; Support StartTLS
* Without StartTLS, managing virtual hosts with TLS support is a pain (because it requires many IP addresses, for example). StartTLS support could make TLS use much more common.
</td><td>
http://www.ietf.org/rfc/rfc2817.txt
</td></tr>

<tr><th colspan="2">General tasks</th></tr>
<tr><td>
* Improve user notification of insecure browsing situations
** 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)
* Improve handling of digital certificates
* Improve phishing protection UI
* Improve overall security UI
* Improve pop-up blocking UI and options
* Implement a Security Center like Netscape 8.1
</td><td>
n/a
</td></tr>
<tr><td>
Integrated something like adblock.
</td><td>
n/a
</td></tr>

<tr><td>
* Integrated mini-Firewall
Integrate a plugin tool, which emulates some kind like a Firewall, like the "Foxie" plugin to IE, but of course, more powerful.

* Session manager
A module that allow you, to save your session, restore, modify and lot of more things to do with them !! (Like Opera o MyIE).

By Kaamos
</td><td>

Thunderbird/Feature Brainstorming

2006-11-02T02:40:01Z

Carutsu:

Since there is now a "Feature Brainstorming" page for firefox,
I'd like to start one for Thunderbird as well.

== Virtual folders only. ==

The most important feature that I would like to see in Thunderbird
is an extension of the "virtual mail folders" concept.

I would like to have all my mail physically stored exactly once.

All folders I use should be virtual in the sense that I can
move any mail into any number of folders without the physical
mail getting copied.

When I delete a mail, I would like to have the option to
delete it from that place only (delete the link) or to delete
it completely, i.e. from all folders that reference it (delete
the real mail from its physical storage and thus all links to it).

The technical details only matter for performance reasons,
but from a user's standpoint I do not care whether that one
place is a mail folder file like the ones Thunderbird has now
or a real operating system folder with one file per mail or
something else, as long as I can still access my mail
with operating system tools such as grep.
I guess the whole concept of virtual folders could be implemented
by putting all original mails into individual files in a directory,
create another directory for every virtual folder and then use
(hard or symbolic) links from the directory of all original mails
into the virtual folder directories.

== Auto filing. ==

When a new mail arrives that belongs to a thread which already
resides in exactly one of my virtual folders, I would like
the new mail to go into that virtual folder automatically.

== Synchronizing with PDA/Smart phone ==

So far Mozilla mails and contacts can't be synchronized with a PDA/Smart phone, at least not with a simple plain binary program (ala active sync). This is IMO the worst drawback against Outlook. This should be done in a cross-platform fashion using wxWidgets.

== Customizable notifiers ==

Ala ''Incredimail'' we should let the user change the notifier he/she wants to use when new mail arrives. And also let the community design their owns, so we have a new "Add-on".

Firefox/Feature Brainstorming:Tabs, Sidebar, Windows

2006-11-01T04:32:46Z

Carutsu:

{{FeatureBrainstorming}}

== Split Windows ==
* Possible to open many pages within a single frame. (useful for widescreens, since many pages use a fixed-width column layout)
* Horizontal splitting and maybe vertical.
* 'Close' would remove active frame.
* Toolbar/urlbar changes to reflect active frame.
* Key bindings for all major functions.

== Advanced tab behaviour ==
* Using a single browser window at all times
* Setting behaviour of links (open in background, open in new tab)
*Ability to turn tabbed browsing off, or at least no functional way to open links into tabs unless specified (e.g. right clicking a link and selecting 'open in new tab'). It's a great feature, but some people prefer the previous method.

== Tab appearance ==
* UI for modifying tab width (f.e. splitter between tabs that can be dragged to change the width of all tabs)
* Options to have no title and Icon only with 32x32 icon with a close button located bottom right of the icon

== Tab strip ==
* Allow to move the tabbar to the right or left, with vertical orientation. this is the best useful when count of tabs exceeds 10 items. vertical tabbar allows to easy use up to 30-40 of tabs. for FF2 i was create the extention, that move tabbar to the right (http://forum.mozilla-russia.org/viewtopic.php?pid=138440) and some simplify tabbrowser.
** When left or right are selected (or perhaps all the time), provide the ability to specify a fixed width for tabs/tab-bar.
** 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]
* Allow to move some tabs (and not the whole tabbar) to the right or left or bottom. That would be a great feature to have a minimum ability to organize tabs when using a single window.
* Displaying tabs over multiple rows
* Holding right click then move left and right it's not used to do anything, this moving may has benefit to switch each windows tab. It's useful with users that take so much time for moving mouse to switch manually.

== Tab focus behaviour ==
*Ability to "minimize" a tab, which would be the fastest way to go to the previous active/focused tab. Otherwise you either have to close it or remember where in the tabbar the previous one was placed!

== Tab Opening/Closing ==
* Duplicating tabs
* Tab opening + closing animation
* When warning about closing multiple tabs, currently there are only two buttons: Close Tabs (which closes all the tabs) and Cancel (which closes nothing). Add a button that says Close Current Tab Only, which will only close the tab that was currently open before clicking on Close.
* Improved UI for finding and reopening any one or more closed tabs (including shortcut key) (like the "recycle bin" feature in Opera)
* Having one close-button on the right, BUT IT SHOULD BE ABLE TO BE TURNED OFF IN OPTIONS. This feature is nice, but looks icky to those who use the middle button (wheel mouse) to close tabs. Accidentally closed tabs result in this feature to unwilling users.
* Undo-close caching
* 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.
* Keyboard shortcut to undo close tab (ctrl-z or whatever)
* 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
* Changing the focus when closing a tab
* Creating a new tab when an addr is typed in the Location bar
* If you have A, B, C tabs in order, and you open a new tab from B (this becomes D) and then close it (D), then the active tab will be C instead of B, the last viewed. It would be also useful if a newly opened tab would appear beside the one that opened it.
* Alternatively, if you have tabs A, B, and C, and open B1, B2 from B, then select B2 and close it, sibling B1 should be focused; close B1, no more siblings, so back to parent B.
** Example: Google search result page 1 (T1) -> Open 2 external links (T2, T3) -> go to search result page 2 (T1) -> Open 1 more external link (T4) -> Select it (T4) -> Close to focus T3 -> Close to focus T2.
** In the B1, B2 example (right above), after you close B2, B1 is focused; if now you select C, and close it, then B (not B1) should be focused because of the sibling rule.
** Tabs closed in background is not affected.
* Option to open default page when creating a new tab
* 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)
* "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.
* Select on close behavior
* 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.
* Allow opening new tab when domain name is different from current page
* 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.
* 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)
* 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.
* To save a lot of space, make the favicon on each tab into the "X" on hover.
* Make the current tab not shrink with the others, so is more visible.
* 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).
* 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.
* A button on the right click menu (on web pages) to open all links on this page in new tabs
* A button on the right click menu for back/forward to open the back or forward in a new tab
* 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.
* When middle-clicking / control-clicking to open in a new tab. Both RSS Feeds and bookmarks should open in a tab "behind" the rest, and not take focus like it currently does.
* avoid having twice the same tab by checking before opening a new bookmark or typing an adress in the bar that the website is not already open. Then click a second time when you really want to open it twice. The tab may also "blink" (or any kind of animation) to prevent the fact that the tab was already open
* When opening the "new window" option, the new window should remain with the present page as in Explorer, instead of going back to the home page.
* Open link in new window with middle mouse button. GUI-configurable option.
* Open different windows each as a new browser instance so that a crash in one does not take down all other instances.
* 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)
* 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
* Multiple link selection
** Click and drag to select multiple links on a page
** Right click to open multiple link context menu
*** Open multiple links in new tabs
*** Open multiple links in new windows
*** Open multiple links in tabs in a new window.
* Allow open a window in modal mode. To force the user to not click in the parent window if the modal windows is open.
* The ability to drag a tab to an empty piece of desktop real estate (secondary monitor, fr'ex) and have it spawn as a new Firefox window.
* Allow user to "Undo Close Tab" via right-click even when no tabs are currently open (Currently, you can only access "Undo Close Tab" via right-click if at least 2 tabs are open).
* Allow Closing all tabs on the left or on the right of the current one
Often, we are browsing and opening many links on the right of the current tab. Also at organizing them, we would like to switch of topic. For example, all tabs on the left of the current one are not relevant anymore. To be able to close all tabs on left would be convenient.
*Allow Closing all tabs except the ones which are on the same domain as the current one
That was self-explanatory.
* Capability to mark tabs with color (an extension is already doing that)
* Capability to close tabs with a given color
That functionnality needs to one just above to be already implemented.
* Capability to close all tabs without a given color
That functionnality is acting on the complementary set of the one above.
* Capability to protect a tab from being closed
Because among all the rules to close tabs which are explained above, we can have some exceptions.
* Allow to have booth options to close a tab, either by a button on the tab and the right hand button. And all this customizable through the options dialog, not from "about:config".

== Send tabs to dock/system tray ==
* Allow sending of tabs to system tray (or platform equivalent). This would better facilitate web apps such as google calendar by providing a lifetime outside of typical browsing sessions and help blend the lines with traditional desktop applications.

== Additional browser events ==
* Allow "triggers" to be set 1) before FF attempts to start downloading a page, 2) when the page has been downloaded but not yet rendered, 3) after a page has finished loading. Ideally, the triggers would either be external applications, or maybe even a funky python plugin framework - if this feature is added, _please_ don't make me have o write nasty javascript for my triggers! Thx :-)

== Location bar and unavailable URLs ==
* Allow navigation toolbar to show URL's that are as-yet, not loaded: if you open a link in a new tab, and that web site is down, you end up with an empty tab with no URL shown. If you've got lots of tabs open, it is very useful to know what should be displayed on the empty tab. I suggest that when a URL is attempted to be opened in a new tab, FF displays the URL in the tab, but shows it "grayed out" (but still selectable!)

== Isolated tabs ==
* Add Isolated Tabbed Windows: This is to ensure each tabbed windows does not leak over to another window eg: HTTPS sites. Simplest way to test, Goto your bank's website (make sure you got 2 different accounts usually your wife's account would be good to test if she is with the same bank) log into your account with one tab, log into your second account in another tab, navigate to your second account's summary view, then go back to 1 first tab and do the same. You will notice that both summaries are from the secondary account.

== Attach/Detach Tabs ==
* A right-click option to pop an existing tab out into a new window.
* The ability to drag a tab from one window to another

== Thunderbird/Sunbird Tabs ==
* Thunderbird Tab -- Opens Thunderbird within a tab rather than a separate Thunderbird window
* Sunbird Tab -- Opens Sunbird within a tab rather than a separate Sunbird window

== Tab Groups/Stacks ==
* Tab Grouping by Domain and Tab Grouping by Originating Page (eg. if I open a Page from Tab A then it will be in the same group as Tab A). A group maybe as simple as having a coloured border around the tabs in the same group.
*Alternatively, an option to have tabs open next to the current tab. This solves the problem of having all your links from different tabs open in the same place, and helps with sorting tabs, because all the links from one website are next to each other.
* Tab collections used to organize tabs, think Linux virtual desktops
* Saving tabs
* Customizing tab groups
* Nested tabs (eg. drag tabs into a tab) and multiple rows of tabs (see this mockup: [[media:Nested-tabs.png]]).
* Tab stacks
; References
* [[User:Dria/On Tabs|On Tabs]]

== Session saving/management ==
* Support session savings. Enables the user to save a session where he/she has, say, 18 tabs open, to another time.
* Implement some method to deal with session sets
* Make session restore fast and precise (save and restore DOM, or use FastBack data)
* Add "email all tabs" option in list of right click tab options
; References
* [http://kb.mozillazine.org/SessionSaver SessionSaver - MZKB]
* [https://addons.mozilla.org/firefox/436/ SessionSaver - UMO]
* [http://forums.mozillazine.org/viewtopic.php?t=47184 SessionSaver (rewrite) - MZForum]
* [http://sessionmanager.mozdev.org/ Session Manager Ext]
* [http://tmp.garyr.net/ Tab Mix Plus with Session Managment]

== Tab overflow ==
* Add arrows to the right and left ends of the tab bar when it gets full to unhide/allow to see all tabs
* Allow an option to have more then one tab bar, especially for commonly used tabs.
* Make the tab overflow left and right arrows in Firefox 2.0 to be draggable; that is, instead of moving 1 tab at a time on click, you can also drag it to act like the scrollbar middle box.

== Window-like tab behaviour within Fx window ==
* Allow multiple tabs to open to vertically or horizontally on the same screen.
* Tab docking like window docking in Visual Studio .NET to be able to drag a tab and dock it with its content to one side of the window. This would allow displaying tabs side by side.
* Display multiple tabs in tiled panes (both vertical and horizontal panes, preferably mixed.
* Cascade tabs
* Allow for windowblind treatment of tabs
*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.
* Option to make a window / popup sticky and always-on-top (Would be nice for watching a video in a popup while surfing). this option MUST ONLY be available for the user not for scripts!
* 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,

== Tab switching/expose ==
* Tab exposé
* Option to view tabs in sidebar (with thumbnails)
* Show all open tags in a browser window organized by miniatures like the F12 function of Xgl or the same function of MacOsX Expose.
* Switching tabs with mouse whell (like Konqeror or Epiphany on Linux)
; References
* [http://www.apple.com/macosx/features/expose/ Apple - Mac OS X - Exposé]
* [http://en.wikipedia.org/wiki/Expos%C3%A9_%28Mac_OS_X%29 Exposé on Wikipedia]
* [http://shiira.jp/screenshot/en.php#tabExpose Shiira Web Browser]
* [http://wiki.beryl-project.org/index.php/Plugins/PluginOptions#Scale XGL/Beryl Scale Plugin]
* [http://img47.imageshack.us/my.php?image=beryl2fw0.png Screenshot of Scale Plugin]

== Tab search ==
* Tab search

== Sidebar ==
* Sidebar animation
* Allow the windows from downloads,extensions,bookmarks and history to dock as sidebars. A bit like the extension All-In-One-Sidebar.
* Better handling of multiple searches in different windows (see [https://bugzilla.mozilla.org/show_bug.cgi?id=45082 Bug 45082])
* Ability to be able to change how the sidebar appears on the screen (i.e. Where you want the sidebar to be docked on the right-hand side of the screen, top of the horizontally or even bottom of the screen horizontally) without the need for scripts. Also have a preferences option to set the default appearance would be nice as well.

== Multiple sidebars ==
* Possibility to add another sidebar on the right (useful expecially with widescreen monitors)

== Options ==

* Setting tabs to refresh every X seconds.
* Turning off the close button on every tab.

== Various ==
* select tab from command line mozilla -remote "selecttab(http://www.mozilla.org)"
* Shading of Tabs denoting time since it started (On the scale of white to black, white is more recent than black); corresponding extension: [http://en.design-noir.de/mozilla/aging-tabs/ Aging Tabs]
* Faster tab mouseover feedback, i.e. show in status bar or set tooltip delay to 0
* 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
* 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/
* 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)
* Sort tab according to time opened, title, time idle
* Tabbed source viewer
* dual screened tabs. two tabs showing in the same window pane, almost like frames. with ability to drag and resize viewing area between the two tabs.
* 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.
*Widescreen browsing : split long web pages into two windows side by side. Sync scroll bar in order that scrolling the first one (top of web page) will scroll the second one (rest of the same web page).
*Scroll Bar Re-position-- allow the right side scroll bar to be moved to the left side screen. Or even placed in the middle... having to move the cursor all around from menus to scroll bars etc... to the right side and then to top and botton is a PITA. (It could be placed on a column separator by user for convenience )... I keep panels at the top with menus, so the same could apply to the bottom scroll bar: allow it to be placed at the top just under the menu's or tabs.
*Scroll Bar Status: For very long pages, more info is needed rather than just the shaded scroll: place 1) an equivalent line number 2) an equivalent page number 3) a percentage number of the page: in order to help fine adjustment positioning or a reference point.
*View screenshot of all available tabs. (Similar to Ctrl-Q or respective keys in IE7). Be able to close tabs from here or switch to any of these tabs.
* Text readability improvements: 1)button/keybind to automatically narrow text to a pre-configured width - text extending accross the whole width of the window is cumbersome to read - possibly configurable to multi-column mode; 2)"Visibility imprint" - on quick scroll operations (PgUP, PgDn, mousewheel...) the previously visible area should be delimited by a frame/line for a certain period of time, after which the frame disappears or fades out, so it's easier to find the last read line; and 3)Improved automatic scrolling: finer control for very slow scrolling and freeing up the mouse. Like current autoscrolling, only finer controls (the current slowest is still too fast) and the possibility to detach the mouse, for instance by re-clicking the middle button, upon which the mouse is free to move but the page continues autoscrolling.
* 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.
* "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. (Very nice idead - i think you can make something like this with 5 lines of VB but launching firefox.exe -appmode -url http... would be cool! When the Browser runs in appmode there JS should allowed to modify the window's behavior)
* Auto-fix tabs whose pages containing user-changed data in input or textarea fields (asking confirmation when attempting to close)
* In addition to the current "block all pop-ups except from this site list" option, also have "block pop-ups from this site list"

== References ==
* [http://kb.mozillazine.org/Category:Tabbed_browsing Tabbed Browsing -MZKB]
* [http://wiki.mozilla.org/User:DoubleEM22 Tabs Screenshots]
* [[Link_Targeting|design thoughts for tabs instead of windows]]
* [http://weblogs.mozillazine.org/ben/archives/009210.html Ben Goodger blogs about tabs]
* Whether [[Ctrl_W_not_close_app|Ctrl+W should not close the app]]
* [[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]]
* [http://users.blueprintit.co.uk/~dave/web/firefox/TabSidebar/index.html Tab Sidebar extension homepage]
* [http://guides.macrumors.com/Show_Safari_Form_Results_In_New_Tab Show Safari form results in new tab]
* [http://www.extensionsmirror.nl/index.php?showtopic=2959 Tab Related Ext - TEM]
* [https://addons.mozilla.org/firefox/1122/ Tab Mix Plus - UMO]
* [https://addons.mozilla.org/firefox/1419/ "Open in IE tab" extension]
* [http://userstyles.org/style/show/1136 Active Tab Flex at userstyles.org]
* [http://wiki.mozilla.org./User:Tuomaz Two tabs side-by-side]
* [http://piro.sakura.ne.jp/xul/tabextensions/index.html.en Tabbrowser Extensions]
* [[User:DJ_Doena/Tab_Features|Current problems with tabs and their probable solution]]
* [[User:Dria/On Tabs|On Tabs]]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=55696 bug 55696]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=281192 bug 281192]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=156264 bug 156264]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=102132 bug 102132]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=104566 bug 104566]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=298571 bug 298571]
* [http://www.novell.com/products/desktop/img/preview_screenshots/apps3.png Xgl miniatures function]
* [http://superdragandgo.mozdev.org/ Super DragAndGo Extension allows you to drag links and words in order to surf and search]
* [http://firefox.exxile.net/aios/screenshots.php?PHPSESSID=a4f4bfaacaa8c756b236f44315b3188d Screenshots of All-In-One-Sidebar extension]
* [http://wiki.mozilla.org/User:Wtmitchell/TabsBarSuggestion1 Provide a separate 'X' clickable button to close whatever tab is active]

== Tab recovery after a crash ==
* This would be useful when windows or firefox crash when you are opening ~5+ tabs...
: Already in Firefox 2.0

== Tabs permissions ==
* This would be useful to can set permissions for each tab (enable/disable javascript, images, frames, redirections, extentions, referer, etc...)

== Tab dragging ==
* When you drag a tab from one window to another, close the original tab and copy the history (back, forward, etc.) to the new window

== Unclose tabs ==
* Make the unclose tab a button able to be dragged into the menu bars, si it can be reached much more easily. The way it is now makes that if you have only 1 tab (and you have enabled the option to hide the tab's bar if there's inly 1) you got to open a new tab just for unclose.

Firefox/Feature Brainstorming:Web Standards Support

2006-11-01T04:30:18Z

Carutsu:

{{FeatureBrainstorming}}
<table class="fullwidth-table">
<tr><th>Specific features</th>
<th width="30%">References</th></tr>

<tr><td>
; Make spellchecker standard-friendly
Firefox is known for its compliance to standards - then suddenly it introduces the "spellcheck" attribute. How are we any better, then, than Microsoft and all its superfluous DOM extensions? Please, put the spellcheck attribute in a namespace, get it approved by the W3C, or drop it.
</td><td>
</td></tr>

<tr><td>
; Report site health at runtime
Do not wait till pages are terminally broken before failing users and developpers. Provide unobstrusive run-time feedback on the errors encountered so pages can be proactively fixed
* The [http://users.skynet.be/mgueury/mozilla/ HTML validator] extension shows how such a feedback could be provided without overwhelming the user. Its main value is errors/warnings are detected when they occur, not when someone thinks about looking for them.
* If you wait till people take the time to open the debugger/console and/or run the various offline validators you've already lost.
* You can't blame non-technical people from setting up broken websites or webapps if the PHBs have no easy way to check the contractors actually delivered clean code.
</td><td>
</td></tr>

<tr><td>
; PDF internal Support
</td><td>
</td></tr>

<tr><td>
; iCalendar Support
* Support to visualize iCalendar content
</td><td>
[http://microformats.org/wiki/hcalendar hCalendar Microformat]
</td></tr>

<tr><td>
; X3D Support
* Support to visualize content X3D, it would allow to work in improving the interactivida one of the hand of a great navigator
* (I request excuses by the text I do not speak English and to use the translator of google :) )
* Please somebody that complements the importance of including X3D in firefox.
</td><td>
*[http://www.web3d.org Web3D Consortium]
*[http://en.wikipedia.org/wiki/X3D X3D in Wikipedia]
</td></tr>

<tr><td>
; ACID 2 test
* Do make sure Firefox passes it.
* Keep eye out for ACID 3 test (no date exists yet as far as I am aware, but they have stated their intent to do such a test). If it is released before 1.9 needs to be ultra-stable, try and get it passed beforehand (mostly for PR purposes really).
</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=289480 Bug 289480]
</td></tr>

<tr><td>
; Full SVG 1.1 support
* Add full support (not a non-standard subset of it) of SVG 1.1 or TinySVG 1.2
* Make SVG "scalable" : When viewing a SVG File, it should be possible to zoom in and out
</td><td>
[http://www.w3.org/TR/SVG11/ W3C SVG1.1]
</td></tr>

<tr><td>
; Graph-support
* Add support for Graph-Formats including [http://graphml.graphdrawing.org/ GraphML] and [http://www.infosun.fmi.uni-passau.de/Graphlet/GML/ GML]/[http://www.cs.rpi.edu/~puninj/XGMML/ XGMML] (ie. by converting to SVG)
</td><td>
 
</td></tr>

<tr><td>
; Content-editable
* Add support for content-editable
</td><td>
[http://www.w3.org/TR/SVGMobile12/text.html#text-edit tinysvg w3c]
</td></tr>

<tr><td>
; CSS
* Make "display: inline-block" work correctly
* Make "display: run-in" work (bug raised in 1998!)
* Support for "content" on all elements, not just on the :before and :after (like Opera)
* Implementation of the value "none" for the property "content". ([http://www.w3.org/TR/css3-content/#content w3c-content])
* Complete support for Multiple background images (like WebKit/Safari)
* Basic support for "border-image".
* Support "box-shadow" ([http://www.w3.org/TR/css3-background/#the-box-shadow w3c-box-shadow])
* Support "text-shadow" (like Konqueror/Safari does)
* Support printing-related properties such as page-break-before and page-break-after
* Implement CSS3 column-rule-*
* Implement CSS3 column-break-* (at least column-break-inside:avoid is required to be able to prevent a zone from beeing "cut in the middle" on resizing).
* Implement font-stretch property
* Implement embeded Font (@font-face to TTF, OTF or EOT ), will benefit also to SVG
*
</td><td>
*[https://bugzilla.mozilla.org/show_bug.cgi?id=9458 Bug 9458 (inline-block)]
*[http://blog.empyree.org/?2893-i-request-support-for-run-in-for-gecko Bug 2056 (run-in)]
*[http://www.w3.org/TR/css3-background/#layering multiple-background-images]
*[http://www.w3.org/TR/css3-background/#the-border-image border-image]<br />
*[https://bugzilla.mozilla.org/show_bug.cgi?id=24000 Bug 24000 (page-break)]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=10713 Bug 10713 (text-shadow)]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=271586 Bug 271586 (CSS3 column-rule-*)]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=70132 Bug 70132 (@font-face)]
</td></tr>

<tr><td>
; XForms
* XForms supported and built-in.
</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=326372 Bug 326372]
</td></tr>

<tr><td>
; XHTML 2.0
* Add support for current XHTML 2.0 draft
</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=161463 Bug 161463],<br />
[http://www.w3.org/TR/2006/WD-xhtml2-20060726/ XHTML2 Working Draft]
</td></tr>
<tr><td>
; Java support
* Activate JavaXPCom on FF (already default on XULRunner 1.8.0.4+)
* Ease extensions creation using Java, ie "pluglet like"
</td>
<td>[http://developer.mozilla.org/en/docs/JavaXPCOM JavaXPCOM]</td></tr>

<tr><td>
; XPointer support
</td>
<td></td></tr>

<tr><td>
; IPv6
* IPv6/IPv4 preference. When a site got both, an option should indicate which one is preffered.
</td>
<td>[https://bugzilla.mozilla.org/show_bug.cgi?id=213121 Bug 213121]</td></tr>

<tr><td>
; new DNS like system
* Having a mapping between domain names (evt. as a RegEx) and IP.
The idea is to be able to edit site that don't have a DNS entry, when we develop a new version that is not on the "real" site.

It's like to change this file: C:\WINDOWS\system32\drivers\etc\hosts but included in firefox.

</td><td>
n/a
</td></tr>

<tr><td>
; XHTML ruby annotation
* 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.
</td><td>
[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]
</td></tr>

<tr><td>
; shy
* Add full support for soft hypens.
</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=9101 Bug 9101]
</td></tr>

<tr><td>
; IE Compatibility
* Answer to below suggestion: Integrate IE tab into firefox by default.
* 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.
* 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)
* Support for embedded managed code objects (ie .NET Windows Forms or platform independant MONO assemblies)
* WPF/XBAP Support.
</td><td>
[http://msdn.microsoft.com/windowsvista/reference/default.aspx?pull=/library/en-us/dnlong/html/introducingwpf.asp#introducingwpf_topic14 Introducing Windows Presentation Foundation]
</td></tr>

<tr><td>
; Opera-like XHTML error processing
* When opening an XHTML document with a syntax error, Opera shows a source fragment with lines numbers and both the tag where the error's been found and the tag that is missing its closing part highlighted.
* There is also a "Reparse document as HTML" link.
* (very optional) There is also a link to the format specification.
</td><td>
[http://www.spasche.net/mozilla/ Open in Browser extension]
</td></tr>

<tr><td>
; XSLT 2.0
* W3C Candidate Recommendation 8 June 2006
</td><td>
[http://www.w3.org/TR/xslt20/ XSLT Candidate Recommendation]
</td></tr>

<tr><td>
; XSL-FO 1.0
* W3C Recommendation 15 October 2001
</td><td>
[http://www.w3.org/TR/xsl/ XSL-FO Recommendation]
</td></tr>

<tr><td>
; Full HTML 4.01, and CSS 2.1 compatibility.
* Increase the standard bar in HTML, and CSS standard.
* 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 :)
* What's wrong with aiming for full CSS3 support? This is FF 3.0 we're talking about. Surely CSS 2.1 support is a given, and 3.0 is achievable in the timescale we're talking about.
</td><td>
[http://www.webdevout.net/browser_support.php Browser standard comparison]
</td></tr>

<tr><td>
; iCab-Smiley analogue
* This nice feature will promote standard-compliancy of the web.
</td><td>
[http://en.wikipedia.org/wiki/ICab iCab wikipedia page]
</td></tr>

<tr><td>
;MHT / MHTML Support
* Saveing / Reading of MIME Encapsulation of Aggregate Documents, such as HTML
* We may also wish to support the MAFF format too.
</td><td>RFC 2557

[https://bugzilla.mozilla.org/show_bug.cgi?id=18764 BUG 18764]
[https://bugzilla.mozilla.org/show_bug.cgi?id=40873 BUG 40873]</td></tr>
<tr><td>
;SMIL support
</td><td>
[http://www.w3.org/TR/SMIL20 REC SMIL 2.0]
</td></tr>

<tr><td>
;XInclude Support
* Including XML files or fragments.
</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=201754 Bug 201754]
[https://bugzilla.mozilla.org/show_bug.cgi?id=232378 Bug 232378]
[http://www.w3.org/TR/xinclude/ XInclude 1.0]
</td></tr>

<tr><td>
;align=char support
* Allow text to be aligned by a character or string in a table cell.
* Example - centre numbers around a decimal point, as in a spreadsheet.
* Part of the overall standards compatibility, but I think it deserves highlighting.
* Bug raised in 1999!
</td><td>
[https://bugzilla.mozilla.org/show_bug.cgi?id=2212 Bug 2212]
[https://bugzilla.mozilla.org/attachment.cgi?id=91020 Test Case]
[https://bugzilla.mozilla.org/attachment.cgi?id=108368 Another Test Case]
</td></tr>

<tr><th colspan="2">Library Compatibility</th></tr>
<tr><td>
KDE compatibility
* A Qt based firefox to remove dependencies on GTK.
</td><td>
n/a
</td></tr>

<tr><th colspan="2">General tasks</th></tr>
<tr><td>
* Improve overall standards support
* Provide I18Ned mozilla.com/getfirefox.com website (beeing english only is not user friendly, site should adapt to user's locale).
* Improve support for High DPI screens
* Use scalable graphics (eg. SVG) for FF UI icon and image. Make scalable graphics first class citizen in FF.
</td><td>
n/a
</td></tr>
<tr><td>
;Improve interoperability of XML languages
* HTML and MathML in SVG foreignObject elements
* SMIL to animate web pages
* interface for plugins to handle mixed XML languages. Final goal: FF + plugins should be able to handle a SMIL + XHTML + [http://xml.coverpages.org/xmlMusic.html MusicML] + SVG + ... document
</td><td>
[http://www.members.shaw.ca/dighere/index.xml VML+SMIL+XSLT Demo in IE]
</td></tr>
<td>
Make the property in CSS of direction (ltr) work properly (is it just me or isn't it working?
</td>
</table>

Firefox/Feature Brainstorming:Tabs, Sidebar, Windows

2006-11-01T04:13:44Z

Carutsu: /* Tab Opening/Closing */