RESOLVED FIXED 62643
Web Inspector: "data" URLs not detected in CSS url(...) values properly
https://bugs.webkit.org/show_bug.cgi?id=62643
Summary Web Inspector: "data" URLs not detected in CSS url(...) values properly
Alexander Pavlov (apavlov)
Reported 2011-06-14 09:11:21 PDT
The actual URLs that are linked to from the url(...) value are relative to the CSS base URL rather than absolute "data" URLs. Upstreaming http://code.google.com/p/chromium/issues/detail?id=82982
Attachments
[PATCH] Suggested fix (9.46 KB, patch)
2011-06-14 10:15 PDT, Alexander Pavlov (apavlov)
pfeldman: review-
[PATCH] Comments addressed, a simplified approach applied (4.88 KB, patch)
2011-06-14 10:41 PDT, Alexander Pavlov (apavlov)
yurys: review+
Patch (5.13 KB, patch)
2011-06-15 06:28 PDT, Jonh Wendell
pfeldman: review-
Alexander Pavlov (apavlov)
Comment 1 2011-06-14 10:15:29 PDT
Created attachment 97133 [details] [PATCH] Suggested fix
Pavel Feldman
Comment 2 2011-06-14 10:22:00 PDT
Comment on attachment 97133 [details] [PATCH] Suggested fix View in context: https://bugs.webkit.org/attachment.cgi?id=97133&action=review > Source/WebCore/inspector/front-end/AuditRules.js:665 > + if (!parsedURL || !parsedURL.isDataURL) { This check seems wrong. Now all parsed non-data urls fall under this branch. > Source/WebCore/inspector/front-end/CookieItemsView.js:243 > + if (!url || url.isDataURL || !this.cookieDomainMatchesResourceDomain(cookie.domain, url.host)) Will this work as is? > Source/WebCore/inspector/front-end/inspector.js:1320 > + if (parsedHref && (parsedHref.scheme || parsedHref.isDataURL)) No need to change this.
Alexander Pavlov (apavlov)
Comment 3 2011-06-14 10:41:29 PDT
Created attachment 97137 [details] [PATCH] Comments addressed, a simplified approach applied
Alexander Pavlov (apavlov)
Comment 4 2011-06-15 05:10:39 PDT
Jonh Wendell
Comment 5 2011-06-15 06:28:37 PDT
Pavel Feldman
Comment 6 2011-06-15 07:17:33 PDT
Comment on attachment 97284 [details] Patch This patch has already landed.
Jonh Wendell
Comment 7 2011-06-15 07:22:37 PDT
(In reply to comment #6) > (From update of attachment 97284 [details]) > This patch has already landed. Sorry, it was my mistake while learning how to use Tools/Scripts/webkit-patch
Note You need to log in before you can comment on or make changes to this bug.