Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Aphyr, every single browser engine has longstanding bugs; it's just a matter of priorities.

WebKit doesn't have load events for stylesheets either, for example. It has buggy CSS selector matching, on purpose (doing the right thing was deemed too slow). There are multi-year-open bugs in V8 and Chrome, and that whole project hasn't even had an open bug database for more than a few years.

So I'm not sure the development culture is any different. You just haven't had a chance yet to file a bug and get it ignored by the WebKit folks for a few years. It happens all the time....



You're absolutely right; I've been bitten by chrome/webkit bugs as well, some of which remain unpatched. And Chrome's relative youth means the browser code hasn't acquired the same level of cruft--so I can't strongly infer a difference in process.


> [WebKit] has buggy CSS selector matching, on purpose (doing the right thing was deemed too slow)

Can you substantiate this? (both the buggy selector(s) and the reasoning)

I have no role in any of this; I'm merely interested in the bugs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: