User:Dmcritchie/Firefox priorities

From MozillaZine Knowledge Base


Firefox Priorities

It seems all too often to me that Firefox is being changed for the worse based on what looks pretty to a graphics designer rather than what is useful for browsing. This is my list of priorities in order of importance that should or should have been implemented in Firefox, many of them ages ago.

Priorities for Developers

  1. Keyword bookmark property, should be seen in all bookmark dialogs for Adding, modifying or deleting bookmarks. Keyword is essentially an alias for a bookmark, there can be only one bookmark for a keyword. This is one of the fundamental features of Firefox. [1] [2] [3]  Additional references mainly to Keyword Bookmarks
  2. Description bookmark property, should also be seen in all bookmark dialogs for Adding, modifying or deleting bookmarks.
  3. Bookmark selections, need ability to export selections of bookmarks and/or bookmark folders. For use by others, for documentation, and to combine and recombine sections of bookmarks.
  4. Distinguish Tabs active/read/unread with styling up to the user. Bug 480813, Bug 487242, TabVisited, Style 24728
  5. Document Outline (table of contents of a page) why is this not builtin to Firefox, it is coded into so many pages such as MozillaZine KB, it would be so useful to all users. I would choose "Headings Map" over "Document Map" extension only because the first includes additional areas in frames.
  6. Tabs opening next to parent tabs should never have been done before item #4 as in Firefox 3.6, but not only was it done, but 3.6 wiped out the ability of extensions and styles to distinguish the same. It also had no clear means to users installing 3.6 as to how to remove the new feature.
  7. Tags should not have been introduced before items #1 is firmly in the bookmark addition properties and item #3 where users can share bookmarks. Instead a developer removed keyword thinking it was the same as a tag, keyword was restored the next day but it still was hidden. Tags on the other hand are very confusing to new users particularly when implemented with an additional drop-down detracting from the ability to add a bookmark into a particular folder or a recently added to folder.
  8. Pinning (docking) dialogs to a Window should be avoided, the worst case is proposal to further mess up bookmark dialog. Pinning the bookmark dialog means that one cannot scroll down the page or visit other tabs to help fill in information while creating or modifying a bookmark. Combine that with a three column webpage, and bookmarks sidebar and you have nothing to work with.

Keywords, Tags and other bookmark properties

There seems to be a lot of confusion among the developers working on Tags as what Keywords are. The main point is that they are not the same. All of the items can be modified by the user.

Title resides in each primary bookmark record and is filled in automatically when bookmarking a page from the webpage TITLE.

URL the address to locate a page (Universal Resource Locator), but they do not have to be an absolute address, they can have JavaScript making them more powerful. If used with keywords they can also make use of substitutions. Firefox includes automatically when bookmarking a page.

Keyword resides in each primary bookmark record and as such can be considered an alias, which is exactly how they are treated in Opera. But Firefox goes far beyond mere aliases by having substitutions available in bookmarks (%s and %S) combined with a keyword one can directly access a single article from a multitude of articles, such as one's own pages, a definition of a specific word. Both of those are simple to create and use. Only when you combine JavaScript do they get more complicated to create, but they are still simple to use. Just do a search anywhere on bookmarklets (or favelets) and any one of them could have a keyword to invoke the bookmarklet directly without going through bookmarks. A user must fill in the Keyword to have it available.

Tags (recently added to Firefox) are additional words added to classify a bookmark, they can be very powerful, but are most likely to be misused. Each tag requires additional bookmark records for each bookmark they are attached to. If you don't have a consistent plan to begin with retagging bookmarks would be very time-consuming especially for a typical set of 7,000 bookmarks. In fact for an individual user tagging bookmarks if pretty much redundant as they could have changed the title to help find a bookmark later. A user must fill in Tags to have them available. Ideally they could be filled in from web pages, but web authors abuse tags (from a keyword list in a webpage) that that it would be impractical as evidenced by some web search engines outright ignoring them.

The primary distinction between keywords and tags is that there can be only one bookmark associated with a keyword, and that for a tag there can be many bookmarks associated with a tag, and many tags associated with a bookmark.

Description is a part of every bookmark record, it is automatically filled in with the "Open Book" extension and with styling so filling in is already in Firefox to fill in from a webpage's own description, but is not automatic. Descriptions could be included in searching with the awesomeBar, and bookmarks, if not also history but they are not.

'resizability' of bookmark dialogs is a part of the "Open Book" extension it works fine there.

What really bugs users the most is that developers make changes to Firefox without any knowledge of the features they break on purpose, even when told beforehand. Here's one summed up in user comment #14 in Bug 404507 – Can't assign bookmark keywords from "Add Bookmark" dialog. Somewhere else was written that keywords are hidden because they can be confused with tags (only by a developer), I don't hear them attempting to suppress tabs because they sound like tags. Or check this one out can't tell the difference between size and shape Bug 524071 – Places UI (3.7): Bookmark contextual dialog should be detachable into a persistent sidebar Or that keywords are not important see my list earlier, or do an add-ons search for: keywords simple, which will produce the maximum 200 hits which I expect are mostly from frustrated users.


Put the customization of Firefox back into Firefox. When I started Firefox, within two clicks of installing Firefox you came upon a page to customize Firefox via userChrome.css and userContent.css that was nice, to the point and not wasteful of machine cycles. The user was a part of the dynamic. One of the best features was a single line change to include keyword in the add bookmark dialog, that ability was removed from Firefox, but that page can be --Customizing Mozilla. After a loss of over one year during betas one can use styling again to add keyword (Style 9029). Now users only see extensions and themes and are directed to many of the worst choices as "Recommended" extensions. Styles offer a user the ability to install as is or to modify them for a more customized look via the "Stylish" extension and many styles on

Real Estate

  1. Keep page layouts simple, don't make us look at three unrelated columns on a page, it's a waste of space.
  2. Keep toolbar heights to a minimum size without distorted icons. The Navigation Toolbar takes almost 3 lines of toolbar space.
  3. Keep the menus, these are the primary route to learn how to use an application, has a hierarchical outline with keyboard shortcuts. They can be modified by users using extensions to add directly into menus with related items as the user sees fit. Lacking decent built-in facilities the "Menu Editor " extension provides exactly what is needed to customize menus.


  1. Remove large banners
  2. Remove large icon
  3. Display the download size next to each "Install" button.
  4. Move the user comments to the end after Developer descriptions and Developer comments.
  5. Collections are going to become a nightmare if that hasn't already happened.

What should be included in Firefox

See User:Dmcritchie#Facilities that should be built-in to Firefox as seen in these Extensions. This would eliminate problems of incompatible extensions as these features are really needed by all users. Unfortunately when such things are adopted into Firefox they never get done correctly, or do only one small part of the extension.