Msg#: 4385623 posted 6:01 pm on Nov 10, 2011 (gmt 0)
I am curious -- what do you guys think about Chrome's current state of web standard compliance? Personally, I hate that browser! It has caused me enough headaches to bring back painful memories of the IE4 vs NN4 days.
Lack of support I could deal with, but incorrect implementation I have no patience for.
For example, accessing document.body.firstChild() gives me the first element of the <head> section more often than not.
Will we see a truly stable and on-par release of Chrome soon?
Msg#: 4385623 posted 12:07 am on Nov 19, 2011 (gmt 0)
WebKit doesn't have as many bugs as Gecko does (I develop with Firefox by default and very closely mirror with Opera with Chrome and Safari a modestly distant third and IE last as always). There's a nasty bug which if you change the title of a link element's style sheet everything breaks style wise. The WebKit nightly builds haven't worked the last few times I've checked over the course of about a week so I haven't been able to see if the bugfix they have (apparently) been working on has landed and corrects the issue or not. I haven't hit a myriad of issues with Chrome and Safari though when I do they tend to be rather harsh. I also would like it if the Chrome team ported over the cursor hot point fix. Safari 5.1 doesn't have that bug though Chrome 15 does!