Official announcement by Google of tomorrow's Chrome launch

While it is based on WebKit (same as Safari), it has an all-new JavaScript engine (V8). Since Google's own WYSIWYG editors need the same internal support as TinyMCE, it *should* be a fairly smooth transition - perhaps even more standardization of how embeddable apps work.

With MSIE being assaulted on now (at least) three fronts, they may just get in line. I suspect that *this* is part of the reason IE8 official release is being delayed... Micro$oft has a stake in their new browser being flawless (at least as flawless as a Micro$oft product can be...)

If it comes out tonight, I will be testing v 2.11(?) before I upgrade to the current TinyMCE...

The "Browser Wars" redux - this time it should be *really* interesting...

Even if I like Google having yet another browser to test and verify apps and sites on is a pain. But if it uses WebKit we might just need to test things on Safari and still expect it to work on Googles new browser.

Hi Afraithe,

Not if you take into account that all they need to achieve is lowering IE's market share. All they want is 1) "a better web" (more standards compliance I guess) and - of course! - 2) more money.

If you think about how Google earn money you will admit that fully standards-compliant browsers are a fundamental requirement for their services (be it Gmail, or their online office stuff) - and their ads-based income.

IE still is a huge hindrance in that respect. And if the open source aspect provides benefits for both Firefox and Google Chrome (like the new V8 JavaScript VM) then the two browsers might equally improve over time.

So... instead of "killing" Firefox they add their market share to the one which Firefox already has bolstering both in the process in order to lower IE's market share. And this sounds everything but weird to me.

The new V8 engine sounds very promising, JS could definitely need a speed boost and since it's browser independent FF could switch to that one also.

IE 8 is not what I and many others hoped for, it has some more standards compatibility things but not much that would ease up the development of TinyMCE like applications. It still lacks the proper DOM Range object, W3C event handles and a bunch of other things. So I would not cry if IE would loose it's leading share right now since it will even with the release of IE 8 be behind all the other ones.

But I have to say the IE team have done a superb job with their implementation of contentEditable it works way better than all the other browsers. Or at least the things that do work isn't buggy. FF has all sorts of selection issues and it's a real pain to deal with.

The problem is that only "nerds" or techy ppl are going to run the Google browser, thus taking market share from Mozilla/Firefox instead of MS/IE.

Just tested TinyMCE on Google Crome and it works pretty good or at least as good as on Safari. But I was hoping for more on the JS performance it's actually slower than Safari when I run the performance tests of some common tasks in TinyMCE. But hey it's a first release so I guess they might have lots of debugging and logging on in the test version.

Since Mozilla are Google's pussies, that could as well be payment not to do anything or even add some security bugs on purpose.
Ok, above scenario likely won't happen for a next few years, but meanwhile, they grabbed some AppleWebKit and Firefox source code,
and will do so in future - take over code checked to be quite bug less, contributed by some freebies.
They also want to punish MS for trying to take over Yahoo, so Firefox gets a payment, and also pushing out Knol, because Wikipedia came out with their open source search.wikia.com

I really love the new browser war. Where JS performance is the thing they are battling over. The new WebKit nightly is blazing fast, faster that Chrome in our tests. But who knows, the Chrome team will probably beat that soon with their new version.