DrunkenBlog had previously posted about what he called the Safari Image of Doom, although he said that this problem isnit exactly the same as the last one. (That offending image isnit included in the post; itis on a separate page.)
“Belay the hysterics,” he wrote, “but do take it seriously. I wouldnit be the least bit offended if you wet yourself after realizing what someone seriously capable could be poking around in if Iim able to blindly stumble into this stuff again and again.”
DrunkenBlog added that this bug, like the previous one, is in Appleis system. “No clue as to the status/resolution,” he wrote.
Reader reaction was mixed, with some upset that the presence of the image in the post, as well as on the front of the blog, was needlessly crashing Web browsers. They suggested that DrunkenBlog should have linked to the image on a separate page, as he did with the previous offending image, thus enabling readers who use Safari in Tiger to still access the post without having to launch a separate browser.
Other visitors, however, felt that any inconvenience was worthwhile if it drew attention to the problem. When an application crashes, users have the ability to file a bug report with Apple, and they believe posting the image in the blog post will result in the company receiving plenty of warnings about the problem.