Jut to be clear, we are happy that you used chromium to create your proof-of-concept. I hope you take the comments above as constructive critic.
The order W3C -> webkit is not set on stone. You can also approach webkit first, or find out who is the lead on CSS for webkit and talk directly to that person. On Jul 17, 8:27 am, Adam Barth <aba...@chromium.org> wrote: > The next step for your specification is to go to the W3C. > > CSS expressions have be a huge pain point for Internet Explorer, both > in terms of security and in terms of performance. We'll want to be > extremely careful before implementing a similar feature. > > Finally, features at this layer should go into WebKit directly, not > into Chromium. Once your spec has been approved by W3C, you should > take your feature request to webkit.org. > > Adam > > > > On Fri, Jul 17, 2009 at 5:27 AM, darrel karisch<dkari...@gmail.com> wrote: > > > security is an issue no matter where javascript is executed. > > it is addressed here... > > >http://groups.google.com/group/chromium-dev/browse_thread/thread/1186... > > > I'm using this execution in a "parallel universe" technique in my > > implementation. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
