Chrome bug: it forgets browsing sessions!

I just reported my first Chrome bug but it looks like it’s been known for quite some time, unfortunately.


When Chrome is configured to open the home page on startup it forgets any recently opened tabs if you don’t open those pages before you close the browser again. I’m fairly certain it used to do the right thing before and remember those pages but I’m not sure when that behaviour changed.

Unfortunately Firefox does the same thing. Go to History->Restore Previous Session and it will restore the home page in the same circumstances. I’m almost certain that browser did the right thing in a previous release.

If one were pedantic, the previous session was the single homepage tab and not the dozen tabs I had open before my browser was closed but it’s not what I expect. I’ll close my browser down when I’m doing something intensive but then click on a link in Tweetdeck, laugh at a rage comic and close the browser again before I realise my mistake.

The other thing Chrome has changed is when you have multiple windows open. It only shows the recently closed tabs for one of those windows. Open the home page again and you’ll see the “recently closed” link again where you can open tabs from other windows. You can also press ctrl-shift-t to restore closed windows.

If you hadn’t closed many pages before you shut your browser down you can also use the History page to open previously closed pages selectively. Unfortunately that won’t help if you had pages open for days that you just meant to read when you had time but never found the time. I find myself shoving pages into Read It Later just so I can get back to them at my leisure.

I’ve tried a few Chrome extensions that promised to save my browsing sessions but none worked in the way I’ve described. Does such an extension exist?

Testing Firefox 2.0

I’m trying out Firefox 2.0 and first impressions are good. Fonts looks a little different which is refreshing but I’m having trouble exporting my bookmarks from Flock. It looks like others are having the same problem too. There’s even a FAQ about it.

On the Mac, click-and-hold doesn’t bring up a context menu. I’ll have to figure out why. Must be a key combo. Ah! It’s CTRL-click!

If you’re wondering which is better, IE7 or Firefox 2.0, then check out this “unbiased” review:

In one corner we have Internet Explorer 7. After 18 months of development and a shiny new set of tabs, he’s in top shape and looking better than his predecessor ever did. That is, before he entered the ring with Firefox 2.0. Now he’s just a cripple with fancy RSS reading.

Drowning in the flood

I have noticed a strange thing in the past week or so. Google has referred legitimate looking browser user agents to this blog and In Photos.org and within seconds that browser tries to download all my feed links, and several months of my archives. I have a little flood protection built in and it stops them with a 403 after several of these requests but it’s annoying. It’s some sort of pre-fetching plugin to “speed up” browsing isn’t it? Firefox has a similar thing in the form of the “Fasterfox” extension if memory serves. Ben Metcalfe has a good write up on the evils of pre-fetching. It could kill your database or use all your credits in online stores!

Whatever you’re using, welcome to my kill file.

64.136.27.227 … “GET /index.php?tag=suicide-girls HTTP/1.1” 200 36422 “http://www.google.com/search?q=suicide+girls&hl=en&lr=&start=20&sa=N” “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)”
64.136.27.227 … “GET /wp-content/plugins/widgets/rss.png HTTP/1.1” 200 3341 “https://inphotos.org/index.php?tag=suicide-girls” “Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)”
64.136.27.227 … “GET /feed/atom/ HTTP/1.1” 200 35775 “https://inphotos.org/index.php?tag=suicide-girls” …
64.136.27.227 … “GET /feed/ HTTP/1.1” 200 35449 …
64.136.27.227 … “GET /feed/rss/ HTTP/1.1” 200 4636 …
64.136.27.227 … “GET /wp-content/themes/whiteasmilk/style.css HTTP/1.1” 200 9639 “-” …
64.136.27.227 … “GET /xmlrpc.php HTTP/1.1” 200 42 …
64.136.27.227 … “GET /2006/07/ HTTP/1.1” 200 68150 …
64.136.27.227 … “GET /2006/09/ HTTP/1.1” 200 68150 …
64.136.27.227 … “GET /2006/08/ HTTP/1.1” 200 68150 …
64.136.27.227 … “GET /2006/06/ HTTP/1.1” 200 68150 …