|Summary:||Add back WTFURL to WebKit|
|Product:||WebKit||Reporter:||Benjamin Poulain <benjamin>|
|Component:||Web Template Framework||Assignee:||Benjamin Poulain <benjamin>|
|Version:||528+ (Nightly build)|
Comment 2 Adam Barth 2012-01-28 16:55:52 PST
Comment on attachment 124457 [details] Patch There's still an ongoing thread on webkit-dev about this work, but I think it's fine to proceed as long as you're aware of the issues being discussed there.
Comment 3 Benjamin Poulain 2012-01-28 17:40:07 PST
(In reply to comment #2) > (From update of attachment 124457 [details]) > There's still an ongoing thread on webkit-dev about this work, but I think it's fine to proceed as long as you're aware of the issues being discussed there. Yep, I'll wait until there is some clear path forward before landing this.
Comment 4 Benjamin Poulain 2012-02-11 19:24:50 PST
Are you OK if I land this? I think we have an idea of where to go from here: -no dependency on anything else in WTF -at some point WTFURL will have to be compiled as a static library for Chromium Next I think I am gonna export the headers for WebCore and make an empty skeleton of KURL based on ParsedURL + a WTFString for invalid URL.
Comment 5 Adam Barth 2012-02-11 19:30:59 PST
That sounds like a good plan. I'm not sure we have 100% buy-in from all the stakeholders, but if you're ok proceeding knowing that risk is out there, I'm happy to review your patches.