4 ms·
To a rendering engine, this isn't any simpler or more complex than any other page. The reason we see this bug is probably that something in the page takes a cod
by bajsejohannes 16y ago
To a rendering engine, this isn't any simpler or more complex than any other page. The reason we see this bug is probably that something in the page takes a code path that is taken very seldom, and thus has not been discovered before.
I'm not saying it's ok to have this bug, just that it doesn't really make sense to come up with a small testcase and say "How can you break something so simple?".
I reported a bug, by the way.
- cmikec 16y agoAgreed. Most pages don't dynamically create framesets in window.onhashchange. Nevertheless, it clearly should work in Opera and they need to fix it. I typically don't test in Opera but I was curious about this one so I fired it up. Seems like the initial page load doesn't work, but if you change the hash (or the settings, same thing), it actually will render properly after that. At some point, if I feel like it, I will write an ugly workaround just for Opera based on this principle. So far 1.81% of visitors from HN are using Opera, FWIW.