This isn't a problem with Chrome. This is a problem with the web developer for that site. If a site is Safari compatible, the Chrome will handle it as well as Safari will (mainly because Chrome is built on WebKit, which powers Safari). However, if a page bugs in Safari, it'll bug in Chrome.
I'm betting that this problem is because they ignored Safari as a browser and focused on Internet Explorer and Firefox. On Sep 11, 3:23 pm, MABalt <[EMAIL PROTECTED]> wrote: > Getting some weird text overlap on AviationWeek.com > > http://www.aviationweek.com/aw/generic/story_generic.jsp?channel=om&i... > > for example. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
