Welcome to WebmasterWorld Guest from 54.196.75.226

Forum Moderators: open

Message Too Old, No Replies

Chrome and Standards Compliance

... or, rather, lack thereof

     
6:01 pm on Nov 10, 2011 (gmt 0)

Senior Member

WebmasterWorld Senior Member drdoc is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Mar 15, 2002
posts:6807
votes: 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.

I will admit that the CSS capabilities of Chrome have improved as of late, although it still has some nagging issues that pop up from time to time. But the JavaScript engine is quite a disappointment.

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?
9:25 pm on Nov 10, 2011 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member fotiman is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 17, 2005
posts: 4987
votes: 12


?
I love Chrome, don't have problems with it on any site. Very early versions had some problems, but they were quickly remedied. And the JavaScript engine is rock solid, fastest out there!

firstChild is a property, not a method, so that should be document.body.firstChild rather than document.body.firstChild()

I've never seen that give me an element of the head section. Best guess would be invalid HTML causing the browser to think the head element is closed?
11:15 pm on Nov 10, 2011 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member lucy24 is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Apr 9, 2011
posts:13060
votes: 302


Cold-blooded answer: They're the new MSIE aren't they? We don't have to follow no steenking standards.
11:53 pm on Nov 10, 2011 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member fotiman is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Oct 17, 2005
posts: 4987
votes: 12


What are you talking about?! Chrome passes the Acid 3 test with 100% and is one of the most standards compliant browsers available today.
12:07 am on Nov 19, 2011 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member jab_creations is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:Aug 26, 2004
posts: 3150
votes: 12


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!

- John