October 5th, 2007
I have been trying to convert the IE6 Virtual PC image to a parallels image. Very unsuccessfully.
The conversation wants to require an official XP disk to make it bootable… which kinda destroys the point.
Even if you do give it the files it wants, it still dies with an ntldr error.
Today I discovered one of the weaknesses of badges, gadgets, and embeds. Users who are behind restrictive web filters may never correctly see a web page that contains an “include” from a blocked site.
On my XP machines at work, the Facebook Badge does not time out in a graceful manner. This has been the source of my thinking that my blog has not been working incorrectly. Today I installed firebug and yslow for firefox and noticed the following…
The site was stuck on waiting for the facebook badge — eternally. This is likely because of the websense restrictive filtering policy of the hospital. If I try to directly visit facebook, that never resolves either. I receive an eternal “Waiting for…” message in the tray in both IE6 and firefox.
Eventually, IE6 just quits waiting for the badge and never renders the rest of the page. After a minute or two, firefox gives up and does render the page; however, it is such a long delay most people would give up ship and move to another page.
How many users are we missing because we are using these embedded objects?
The huge spikes in internet traffic during the work portion of the week suggests that a large majority of internet traffic is from people at work. People at work often have some type of internet filter between them and the rest of the world. It makes sense to me, then, that these hot new embeddable objects may be making many web pages inaccessible to many users.
If a browser fails to load an image, it fails gracefully. If a browser fails to load a gadget, the rendering of your entire page may choke.