> If you find a badly rendered webpage, you can submit it to: > https://bugs.webkit.org/enter_bug.cgi?product=WebKit&component=Layout%20and%20Rendering > - OR - > http://code.google.com/p/chromium/issues/entry
The way you decide is: If it breaks in both browsers, then file the bug at WebKit.org. If it breaks only in Chrome, file it under code.google.com. On Thu, Sep 3, 2009 at 11:54, dhhwai <[email protected]> wrote: > > Google Chrome and Safari are both very good. They both use the > fastest Javascript processors now, Chrome uses V8 and Safari uses > Nitro (formerly SquirrelFish Extreme). > > Also, they both use the extremely fast and efficient WebKit rendering > engine to display webpages, which is very quick and allows very fast > screen display. > > However, since they both use WebKit for rendering, any webpages not > working with Safari will likely not work in Chrome either. Many of > these problems are caused by bad/non-standard HTML coding by webpage > authors or bad browser detection code. Additionally, there could also > be WebKit problems in not rendering a webpage correctly. > > If you find a badly rendered webpage, you can submit it to: > > https://bugs.webkit.org/enter_bug.cgi?product=WebKit&component=Layout%20and%20Rendering > - OR - > http://code.google.com/p/chromium/issues/entry > > On Sep 3, 9:42 am, siddhu chowdary <[email protected]> wrote: > > hi > > so what do you suggest about apple safari? Is it good or bad for > > google chrom? > > Can we try this because some of web sites are not working with out > > safari. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
