OK, Thank you for the reply. I think "The official release is not using the webkit trunk, since it is not stable enough" is a good reason.
I think I will have a look at the Chrome trunk. On Nov 4, 5:35 pm, Darin Fisher <[EMAIL PROTECTED]> wrote: > Yup, we're working on updating Chrome to use a more recent WebKit. Our plan > is to make it possible for Chrome developers to build against tip-of-tree > WebKit, which given the speed of WebKit development, poses several > challenges. > -Darin > > > > On Tue, Nov 4, 2008 at 8:20 AM, Jean-Daniel <[EMAIL PROTECTED]> wrote: > > > Is there a good reason you're not working with the WebKit trunk (or at > > least a recent version). And is there any plan to update it ? > > There is a lots of feature available in WebKit that are not available > > in chrome (HTML 5 localStorage for example, and lots of -webkit- css > > properties). > > > I though WebKit based browser where able to perform a better result > > than 79 on the ACID 3 test (Safari 4, QT and GTK+ based browser > > successfully pass the test). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
