Quote:
Originally Posted by NastyBlast
Chrome is jacked up. It can't even do tables properly so you're probably going to end up in the good old multisite deployments that are browser specific. So it's not a problem with your coding it's a problem with chrome and you have to make the decision on how important it is for you to support chrome. I tossed it I don't care because I figure most people are using Firefox and if it doesn't work in chrome they will use Firefox
|
Uh, I'm pretty sure Chrome is one of the most compliant browsers out there and it does
everything I've tried properly (except, of course, for some CSS3/HTML5 things that aren't even a standard yet). I think you're the problem, not Chrome. That said, there could be problems with Chrome's rendering that I don't know about, but they would most likely also affect Safari and all other webkit-based browsers as well. I've used Chrome for probably over two years now and during all that time developed dozens of websites and never had a problem that was Chrome's fault.
edit: oh and if the site renders poorly in Chrome I would probably get out of there pretty quick, unless it's something I absolutely need. I would just pass it off as an incompetent developer, leave, and not think much more about it.