2
edits
Talk:Firefox/Projects/3.7 and 4.0 Theme and UI Revamp/Direction and Feedback: Difference between revisions
Jump to navigation
Jump to search
Talk:Firefox/Projects/3.7 and 4.0 Theme and UI Revamp/Direction and Feedback (view source)
Revision as of 07:42, 2 October 2009
, 2 October 2009→Combining Stop/Refresh (and eventually Go)
No edit summary |
|||
| Line 130: | Line 130: | ||
I forsee a scenario where a long and slow page is taking forever to load, so you go to hit Stop so you can read the partially loaded page. However, right then the page finishes loading and you end up hitting Refresh and now you have to wait forever again for the page to load again (i.e., a race condition with the user). Can the Refresh button be disabled for 1-2 seconds after a page finishes loading, to prevent this? | I forsee a scenario where a long and slow page is taking forever to load, so you go to hit Stop so you can read the partially loaded page. However, right then the page finishes loading and you end up hitting Refresh and now you have to wait forever again for the page to load again (i.e., a race condition with the user). Can the Refresh button be disabled for 1-2 seconds after a page finishes loading, to prevent this? | ||
-- | |||
In a country where traffic shaping is common practice, I often encounter occasions where the page just stops loading (it's like the server timed out while the client is still waiting), especially when my bandwidth gets shaped by a large amount. In these cases, I only really wanted to just refresh. Merging the two buttons will mean I need to first stop it, then refresh - It saves one mouse click per "dead" page load. This becomes significant when I have >30 tabs open (ie. most times). | |||
= Bookmark Tab = | = Bookmark Tab = | ||