3
edits
Firefox/Feature Brainstorming: Difference between revisions
→Downloads
("Multiple Configuration states" and "Tabbed Toolbars" are entirely inappropriate for a "simple" product; We do prefs locking, it's a docs issue; We have "View Image" and search in textboxes) |
Seb.sprenger (talk | contribs) |
||
| Line 203: | Line 203: | ||
* An alternate solution for the above problem: pressing the "del" button (instead of Ctrl+Shift+Del which is not really intuitive) in a form control history dropdown control could remove that entry off the history. | * An alternate solution for the above problem: pressing the "del" button (instead of Ctrl+Shift+Del which is not really intuitive) in a form control history dropdown control could remove that entry off the history. | ||
* Another concern: saving of credit card information. When on a secure site, I can go to the credit card field, start typing in my card number, expiration date, etc and it will be in the autocomplete. Same thing with my SSN, address, phone number, etc. I would appreciate an option to disable the saving of form information on https (secure) pages. Another approach would be to include an option (not mandatory), to pop up a dialog.. something like: "This appears to be a credit card (SSN, etc) number, do you want it to be saved?" | * Another concern: saving of credit card information. When on a secure site, I can go to the credit card field, start typing in my card number, expiration date, etc and it will be in the autocomplete. Same thing with my SSN, address, phone number, etc. I would appreciate an option to disable the saving of form information on https (secure) pages. Another approach would be to include an option (not mandatory), to pop up a dialog.. something like: "This appears to be a credit card (SSN, etc) number, do you want it to be saved?" | ||
</td><td> | |||
n/a | |||
</td></tr> | |||
Allow a time set feature to open a set of specific tabs at a desired time of day. | |||
<tr><td> | |||
; Multiple Configuration states | |||
* Many customizations provide a lot of features, but also a lot of clutter. Rather than manually adjusting toolbars to fit your current activity, it would be much more efficient to store multiple customized states that can be easily selected from, by name. There are multiple state categories, such as toolbar layout, bookmarks, skins, etc. A saved configuration state could be defined to include only a subset of states. | |||
* This information could be saved to/retrieved from a central server with a username/password (without any prior account creation hassle), so we could have the same environment on every Firefox installation. | |||
</td><td> | |||
n/a | |||
</td></tr> | |||
<tr><td> | |||
; "Tabbed" Toolbars | |||
* Multiple toolbars could be stacked and "tabbed" similar to tabbed pages, which is a popular feature. Rather than tabs, the selection could be similar to a pull-down menu, where each entry is a toolbar. Instead of selecting a toolbar, one could also click the pulldown button, then click one button on any of the transiently displayed toolbars. | |||
</td><td> | |||
n/a | |||
</td></tr> | |||
<tr><td> | |||
; Preference Locking | |||
* Make it easier to lock preferences. For example make it possible to make pref.js and bookmarks.html write protected. As of now Firefox creates lots of copies if you make those files not writeable. | |||
</td><td> | </td><td> | ||
n/a | n/a | ||
| Line 267: | Line 290: | ||
<tr><td> | <tr><td> | ||
Allow user to add file types in addition to being able to change how Firefox "manages" them. | Allow user to add file types in addition to being able to change how Firefox "manages" them. | ||
Allow Firefox to search inside text typed in textboxes (available in IE). | |||
Allow image placeholders to appear before the image starts being displayed (available in IE). | Allow image placeholders to appear before the image starts being displayed (available in IE). | ||
[Last three entries by [[User:CarlRogerson|CarlRogerson]] 23:52, 14 October 2006 (PDT)] | Allow "View Image" to display the image right where it is (available in IE). [Last three entries by [[User:CarlRogerson|CarlRogerson]] 23:52, 14 October 2006 (PDT)] | ||
</td><td> | </td><td> | ||
* FF 2.0 supports searching in textareas. | * FF 2.0 supports searching in textareas. | ||
| Line 3,047: | Line 3,072: | ||
----- | ----- | ||
I agree that a much smaller | I agree that a much smaller 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. | ||
My suggestions for top priorities - before ANY new feature(s) (just my $ .02, for what it's worth): | My suggestions for top priorities - before ANY new feature(s) (just my $ .02, for what it's worth): | ||