4
edits
Talk:Firefox3/PRD: Difference between revisions
m
→Tab Reordering/Tearing Animations: new section
(Had problems with the broadband connection and double-submitted) |
m (→Tab Reordering/Tearing Animations: new section) |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 519: | Line 519: | ||
PLENTY OF PEOPLE IN INDIA STILL USING WINDOWS 98 WHY U NOT SUPPORT THAT OS ? PLEASE CONCERN THIS - DIEHARD FAN OF FIREFOX | PLENTY OF PEOPLE IN INDIA STILL USING WINDOWS 98 WHY U NOT SUPPORT THAT OS ? PLEASE CONCERN THIS - DIEHARD FAN OF FIREFOX | ||
=== Windows 98 is an unsupported OS anyway === | |||
Microsoft has already dropped support for Windows 98 anyway. If you don't mind running an outdated, unsupported OS then why would you mind running an older version of Firefox on it? | |||
== Open New Tab Right Next the Parent Tab == | == Open New Tab Right Next the Parent Tab == | ||
| Line 776: | Line 780: | ||
* clear private data for current site | * clear private data for current site | ||
* clear private data for all sites on this window | * clear private data for all sites on this window | ||
== Why isn't the schedule updated? == | |||
The schedule only has info up until Beta 4. Isn't a complete schedule the single most important thing to involve the users in Firefox's development? I think so. | |||
== "Firefox is already running, but not responding" suggestion == | |||
This error message ticks me off to ''no end'' whenever I see it and it gets frustrating to keep seeing it time and time again on Firefox 3.5. | |||
And of course, the moment I open my Task Manager to close the 'not responding' Firefox process, IT EXITS! | |||
As such, I would like to make a request for the "Firefox is already running but not responding" dialog box: '''add a "Force Quit Firefox" button.''' | |||
Seriously. It'd end a lot of headaches. | |||
== Local content (from hard drive) should never be cached. == | |||
What reason is there for local content to ever be cached? In development, often most testing is local. This necessitates extra steps to ensure everything is refreshed every time an edit is made. | |||
== Clearing cache should be complete, every time. == | |||
Some files don't get cleared for a page that is currently open. This problem has plagued Firefox for years. Where it is most noticeable is with Flash apps that load multiple Flash files. The subsequent SWF files are NEVER cleared from the cache unless the user closes the window or navigates away from the page the files are on. This makes for extra steps in clearing in the cache for every edit. As a developer I have to explain this process repeatedly to many clients and colleagues. They are either confused or frustrated by the issue. | |||
== Caching: The Ghost of the Internet == | |||
Any developer knows, caching can be a confusing hinderance of development. I've often wondered how many times I've solved an issue, but was unaware because the page cached and I had already moved on to the next hacky attempt at a solution. As ubiquitous as caching is to the web, clearing of the cache should be simpler and options/controls for the cache could be me robust for every browser. | |||
I can think of several ways to improve caching. It seems like it's always a buried option that is always in a different place in the tools or preferences, and has a different and obscure hot key, for every browser. In Firefox, it's clumped in with a bunch of other "Private data", in IE it involves clicking through and confirmation in several annoying windows. Even the single window Firefox uses for confirmation is an annoyance to me. It makes people feel like they are doing something "techy" which is scary to them, when really there shouldn't be any risk to clearing a cache, and therefore no need for any confirmation. Just DO it! | |||
Seriously. Imagine as a developer, at the 11th hour of many projects, having to diagnose cached items for why your clients are seeing funny stuff, asking them what browser they are using, and going through the process of clearing the cache on the phone. Then imagine this being true for just about anything that goes wrong just because you need to rule that out. | |||
An option to have a "clear cache" button right next to the reload button would be awesome. How about an option to force every reload to clear cached items for the current page. How about a check box that defeats all caching without changing other caching options (in prefs would be cool but right on the browse would be cool too). There could be an indicator on the browser window that shows weather or not there are any cached items on the page. There could be a way to reveal what items are cached right on the page. | |||
I believe caching is important enough to be it's own preference panel. There, you could specify caching options for individual pages or domains, like max/min file size, file types to cache, duration to keep files and max cache size for each page/domain. | |||
Is this crazy? I know it would save me TON time, trouble, and sanity. | |||
== Tab Reordering/Tearing Animations == | |||
It would be nice to have tab animations when the user grabs a tab, and rearranges it on the tabs toolbar. An example of this is in Chrome and Safari, where the tabs move themselves accordingly to where the user holds the grabbed tab at the moment. This makes the reorganization of tabs look more smooth. However, there should be an choice in the options page where the user can allow/disable these animations. | |||
Also, animations should be added for when tabs are torn from the toolbar, and are either used to make a new window, or join another window's tabs. These animations are also found in Chrome and Safari, and add a nice touch to the browsing experience. These animations would make the browsing on Firefox look more smooth and seamless. | |||