“Do you want to remember this password?”) in favour of non-modal messages in the notification bar (see Alex Faaborg’s post about this from last year). One of great things about Firefox 3 is that it eliminated a lot of the modal dialog boxes (e.g. First, it uses modal dialog boxes, which are generally a bad idea. The Problemīut the interface for session restore has always bugged me a bit. (And in my field study I’ve learned that lots of other people do this too.) If your browser crashes, or the Firefox process sustains collateral damage in a kill(1)ing spree, it’s a relief not to lose all the tabs your were saving. I often use tabs like lightweight bookmarks, leaving tabs open to a page that I am planning to come back to. You know, when you start Firefox, and it asks you if you’d like to restore your windows and tabs from last time? That’s session restore. One thing that’s been on my mind lately is the session restore feature. Since I’m doing a field study on how people use tabs in Firefox, you can imagine that I spend a lot of time thinking some of the smallest details of the Firefox user experience. Firefox should always restore with as much of the saved state as possible, except in the private browsing case, then none of the previous state should be restored at all.Sketchbook: Firefox session restore December 5, 2008 I think you get the idea, so get creative. Check that your previous sites are available in the Awesome bar as part of your browsing history. in the middle of a transaction (like searching for a plane ticket) while filling out a form on a public site while filling out a form and logged in to a site while browsing about in private browsing mode (should return in normal mode, and should not ever see the session restore dialog.) with a bunch of windows + bunches of tabs open, ensure that only the ones you pick get restored. with a bunch of tabs open, ensure they all get restored Now that you're all savvy on how to crash the browser, let's look at things to test: You can browse through our currently open crash bugs and see if any of the test cases there still crash 3.5 beta 99 (and please leave a note if they do).You can use the Task Manager in Windows to "End Process" the firefox.exe process.On OS X, you can use Activity Monitor to do a "Force Quit" on the browser.kill -9 -> give it the number for the Firefox instance you want to kill.ps -A |grep firefox -> displays a list of process ID numbers that correspond to the running instance of Firefox.You can also open up a terminal window in Linux and mac and run the following commands:.Use Ted's nifty Crash Me Now! Extension.If we crash twice then we know that something is amiss, and maybe one of the open sites is causing the crash so the dialog displays as your first tab. The thinking here is that after the first crash, you just want to bring everything back the way it was. One more note about the way it works - you only see the nifty dialog if you crash twice. To choose to not restore a page or a window, clear the checkmark on the left side of the window. The page will load in the first tab after a crash and it looks like: Previously, we just restored everything all at once, but if one of those pages was the one causing the crash, then this would create a crash every time you restarted your browser. The new session restore page allows you to choose which pages and windows to restore after a crash.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |