Well, I’ve just reduced a surprising crashing bug in Safari. It turns out if you have an image that’s defined as display: block surrounded by a link (or probably any tag) that displays content with the :after selector (in my tests, I used an image) then Safari crashes if it doesn’t have the images already cached. This means refreshing the page or emptying the cache and going to the page again crashes.
A short snippet of code that demonstrates the crash problem is the following:
Easiest way to see this is through the Snippets editor in the debug menu. And if you change the display to inline instead of block, it won’t crash. And if you change it back to block, it still won’t crash until you empty cache or refresh a page that has this code.
Entries (RSS)