| Summary: | Add back WTFURL to WebKit | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Benjamin Poulain <benjamin> | ||||
| Component: | Web Template Framework | Assignee: | Benjamin Poulain <benjamin> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | abarth | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Benjamin Poulain
2012-01-28 16:29:59 PST
Created attachment 124457 [details]
Patch
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.
(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. 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. 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. Committed r107502: <http://trac.webkit.org/changeset/107502> |