Firefox/Feature Brainstorming:Default Browser UI

« Firefox/Feature Brainstorming

Specific features	References
Customizable Main Menu Allow the main menu (File, Edit ...) to be customized and/or retracted in order to be able to free much more space for sites' display without using full screen mode.	n/a
Absolute UI customization Allow to place any action control (eg. File->Exit, all extension buttons, ...) to any place on the browser ui (eg. status bar, preferences window, url suggestion popup, or even into bookmars, ...). Allow to remove as meny as posible unused features from the browser (this can speed up the browser startup, if someone figures out, how to don't load code of removed features). It's too ambitious idea... try figure out, what's possible to implement	n/a
Absolute hotkeyability and toolbarability Any command that can be accessed from a menu or a button should be hotkeyable (including changing the standard hotkey), and can be put onto the toolbar as a button. Users should be able to save and load custom hotkey and toolbar layouts (including "for one session" mode, when they are at the public PC)	n/a
Back and Forward buttons Include right click options on back/forward buttons to open the previous/next page in a new window or tab. It would need to preserve the browse history in new window/tab. Use a second set of Back and Forward buttons to navigate local directories "Smart" Back button in case the page was loaded by "POST" command. It is possible to store the page "as is" in the cache and when requested about "repost data" show that page if selected "no". In most cases the page is needed only because of links on it Along with Back and Forward, an "Up" button could be added for going to "./..", as it is sometimes useful even on the Web. KDE's browser has already had this for some time.	Middle click on back / forward already does this, but History is not preserved. Related to: bug 18808 bug 189313 bug 246719 a detailed proposal here
Three-level Undo and Redo instead of Back and Forward Since AJAX has become very popular, often we do many action on the same page, even if its contents totally changes. Site developers sometimes implement program handling of Back and Forward buttons, which takes page history navigation out of the user's control, and this is not natural and not convenient. Instead, there can be three levels of Undo/Redo actions: low level for each script or user action which changes the actual document DOM structure (also useful for debugging); middle level for traditional Back/Forward (socument location cnanges); and high level for browser-wide actions like opening and closing pages, switching tabs etc. User should be able to turn off tracking of each separate level, to save memory and speed up performance, as well as to customize their history deepness (how many recent actions can be tracked).
More toolbar buttons Include more toolbar buttons (proxy checkbox, Save Page, Print Preview, Full Screen, Downloads, Images, etc) in the customize toolbar dialog.
As per bug 63295 (almost 6 years old), menus should auto-scroll if you hover above/below them. Toolbar enhancements Allow user to move toolbars	n/a
Combine reload and stop buttons With rare exceptions, the Average User does not need access to both the reload and stop buttons at the same time. Combining them so they occupy the same space and "toggle," à la Safari, will free up real estate on the UI and reduce visual complexity. ...at the cost of continuously reload pages on locks/slowness/etc. Shiira already avoided this solution. If this will be done, MUST be enabled/disabled with a setting in the Preferences.	Apple - OS X - Safari
Simple Interface Many people like the simplicity of IE7 - that's the way it should be. More people would use Firefox if it were simplified. Take out the stuff that's not needed... Do not integrate ANYTHING that should be an extension. Instead of integrating, provide more good APIs (XPCOM components + JS wrappers) for the extensions.	Note that all successful endeavors are simple (ie. Google, Windows, IE) Note that Firefox won't remain even as simple as it is now, if all the suggested features are going to be implemented! It won't be, but it SHOULD be at all costs - as I said, that's what most of the world likes, simplicity. Not everyone knows how to install an extension - we should start off small... Concepts of Firefox "Core" and "More".
Text link recognition Double click on a text link (like: www.somesite.com/here.html or http://www.somesite.com/here.html) recognizes it and opens it like a regular link, a very simple feature.
Improved visual navigation Alternatively scrollbar enhancements could help (refer to the second link for more details). Not sure if it's easy to implement though.	Enhanced scrollbar details (Russian, but pictures talk for themselves)
Alternate UI modes Togglable kiosk mode More efficient layout for widescreen laptops Minimal UI mode Show and hide navigation/bookmark/menu bar via a right-click menu everywhere Add an option to the View menu to hide all the top toolbars and the tab bar when the mouse is not over the window header or, when in fullscreen mode, not at the top of the window. Add an option to hide the toolbars and show them at the mouse position (so you don't even have to go all the way up at the top of the screen) by using a mouse + keyboard combination. Add an option to hide the menubar (optional) full screen (or "resize to fit all content" ...a la Mac OS X) mode without toolbars, icons, navigation bar, etc	- details & discussion
Choice of UI rendering mode choice between displaying page when fully rendered (mozilla way) or display as it renders (Firefox way).	Check Smooth Page Transitions suggestion
Rationalize and reorganize browser and context menus Remove some menu items Move other menu items	Reasoning and Arguments
Context Menu Show an open url in new tab or open url option in the context menu when the user right-clicks on a plaintext url (text that is recognizably a url, but has no <a> tags). Show encoding option in the context menu, with easy access to favorite or frequently used encodings (e.g. for Ukrainian users: Windows-1251, KOI8-R, KOI8-U, UTF-8), without need to choose them from the list of dozens of unused items. (Encoding should be made on the fly, without any HTTP or cache requests.)
Display keyboard shortcuts when hovering over objects When hovering over an object in the navigation toolbar the respective keyboard shortcut should be displayed as a tool tip. It could considerably improve the usage of keyboard shortcuts for new Firefox users that are not used to work with keyboard shortcuts (like old people). This should be a default-on feature with the option to turn off in Options -> Advanced -> General -> Accessibility
Reconsider the idea of Home Page Home Page and Home button have been with us since forever. However, I have a strong feeling they are no longer relevant and no one uses them as they did in the old times of "web portals". I propose to create a task-oriented "start" pane - basically a question of "what do you want to do". It should have: urlbar: "I want to go to that page". history: "I want to go to the page I've been to recently" web search: "I want to search" a button that restores session from just-closed window: "I want to continue" bookmarks and feeds, or otherwise Places I consider Thunderbird's start pane to be a good example of what I'm talking about.
OS X widgets Use OS X's provided widget set, especially for textarea, button, radio, checkbox and select elements. Native widgets feature spell check among other niceties. This would go a long way towards making Firefox feel more like a "real" OS X application. The current UI does not follow many of the common idioms on the Mac which causes confusion when switching between it and other Apple apps. This could greatly impact adoption on OS X, particularly among less savvy users who don't understand why it's different. Still, those should be kept customizable via CSS: only the defaults (unstyled) should be system-widgets.	Apple Mac OS X Safari Browser Apple Human Interface Guidelines Hacking Aqua Widgets into Firefox
Use Default GTK+ widgets As with OS X, Firefox on GTK+ OSs uses the same blocky widgets in webforms (to the point that a list box in a webform behaves differently than a listbox in the system.)
Page Zoom Instead of only increasing and decreasing the current page's font size, allow for the entire page to be zoomed in/out, like Opera. Make the zoom keys customizable. Also, like Opera, make sure that all elements zoom, such as Flash.	bug 4821
Preventing Flash, other plugins and scripts from overriding the context menu While Flash displays its own context menu, it is inconvenient and looks inconsistent, preventing access to what user would actually like to do with the page or its part (often users do not recognize where is GIF and where is Flash). The same is happening when a script changes the context menu. User should have the ability to display browser context menu wherever on the page they right click, and to save the object they clicked.	bug 4821
Better autocomplete in form fields Autocomplete list should be editable (like cookie-list) or erasable otherwise it will contain a lot of trash after some time and it is also a mild security risk because sometimes people demonstrate their actions and it is not nice previous entries pop-up; perhaps some toggle can help to disable/enable the feature Also, Emacs-style autocomplete ("dynamic expansion") of words will increase input speed dramatically in input and textarea fields It could go even further by having abbrev-list in a meta rel fashion (the same fashion as favicon is specifyed or other related documents) If implemented, this proposal can boost productivity for web-application users with technically simple (and known from many text-processors/editors) UI add-on	Emacs Dynamic Abbrevs Discussion
Avoid caching sensitive data for autocomplete Use heuristics to try and avoid caching sensitive data for autocompletion. For example, if something looks like a credit card number or social security number, don't cache it. It's very disconcerting to start typing in your social security number on your bank's Web site, and realize your browser already knows it...
Editing HTML of opened page Be able to edit the HTML source of a web page that is open and then save the changed version to the local hard disc. Currently "View > Page Source" does not allow editing for a web based page. Make this editable and then give the ability to save the entire page with images etc, using the modified source to the local hard disc.	bug 172817 bug 269326
Color of visited links depending on time of last visit Color of visited links should range from VLINK to LINK according to time passed. I'd like that the color of visited links could range from the the color defined for visited links to the color of _un_visited links in proportion to the time passed since last visit. This feature was present in early Mosaic, but I haven't seen it again in any browser.	Bug 211531
Different font sizes for each page I'd like to have the option of choosing a custom font size for a page; the browser should be able of remember the last size in future visits to the same page.	n/a
General tasks
Revisit default tab strip Re-evaluate toolbar buttons Re-evaluate status bar Re-evaluate menus and context menus Ensure shortcut consistency Remove Truncation of Title and Alt Tags Intelligently handly text-cursor movement requests so that the cursor isn't moved while the user is typing. Handle Adobe Flash (and others) like IE 7, requiring a left-click before the plugin begins intercepting keyboard shortcuts.	User_talk:Jokeyrhyme User:Auk/Firefox_menus