The only glitches I've seen so far (aside from only being available for Windows) is its handling of PNG translucencies. And its form autocompletion is applied rather haphazardly.Luckily, it's based upon the WebKit renderer (same as used by Apple's Safari and the Omni Group's OmniWeb, as well as Adobe AIR) so at least it's not a completely new renderer for us web devo types to have to worry about. But it is another browser that we'll need to test on.
LOL... sorry for geeking out.PNG is a graphics format like JPEG. It's an advanced format that, unlike JPEG, can handle translucency -- the fancier sites that you see around that use drop-shadows and the like are taking advantage of this format.The rest was just bitching about having one more browser to test web applications on...
I have a mac. So no...
So BB will you report a bug to Google dev for the PNG issue?
Quote from: J Digory on September 04, 2008, 10:14:34 PMI have a mac. So no...That is it's biggest drawback.Quote from: FR8TRAIN on September 04, 2008, 10:28:15 PMSo BB will you report a bug to Google dev for the PNG issue?Already have. They already know all about me from other bug reporting.
I've been playing with it for the last couple of hours and while it is fast, so is Firefox without any plugins. This brings me to some "flaws" that I have found.1) Because it is so new, there isn't any of the plugins that are required for many video sites on the web, such as ABC.com and Fox.com. These will only come if there's enough people using the browser.2) Chrome doesn't always render proper CSS and XHTML appropriately. 3) Importing bookmarks and such from Firefox is broken.4) Oh, and typing Google.com in the address bar closes the browser...wtf?5) I don't like that when I open a new browser that it shows all the pages I viewed last session.