Back in the day, when table-based layouts needed content with certain dimensions to ensure widths and heights in all browsers, I used to rely on an image with src set to about:blank, instead of the silly 1x1 transparent pixel spacer.gif technique.
Later on, when I stumbled upon a CSS problem in IE6 where elements wouldn't show up unless they had a background, about:blank was back to save the day.
It's really like /usr/bin/yes or /dev/null of the web in a way. I really wanted to read more 'folklore' about it's meaning, rather than an article about the perils of it's implementation. Now I'll have to start another Googling odyssey [CMD+T -> about:blank].
Hope they manage to nail it. We're pretty used to slight delays (hiding elements until they're ready), so an asynchronous callback seems like the way to go, if it solves things for the FF developers.
Trippy page load btw, looked like some HTML art example from the nineties at first..
Later on, when I stumbled upon a CSS problem in IE6 where elements wouldn't show up unless they had a background, about:blank was back to save the day.
It's really like /usr/bin/yes or /dev/null of the web in a way. I really wanted to read more 'folklore' about it's meaning, rather than an article about the perils of it's implementation. Now I'll have to start another Googling odyssey [CMD+T -> about:blank].
Hope they manage to nail it. We're pretty used to slight delays (hiding elements until they're ready), so an asynchronous callback seems like the way to go, if it solves things for the FF developers.
Trippy page load btw, looked like some HTML art example from the nineties at first..