RESOLVED FIXED 32336
Update Chromium Loader to pass through the new ResourceType::TargetType
https://bugs.webkit.org/show_bug.cgi?id=32336
Summary Update Chromium Loader to pass through the new ResourceType::TargetType
Mike Belshe
Reported 2009-12-09 12:02:07 PST
FrameLoaderClientImpl.cpp previously would override the resource type as a generic TargetIsSubresource when the target is not a main or subframe. Update to only modify the type if the resource is a frame; otherwise, leave the setting as is, since the ResourceRequest now initializes and sets the resource type properly.
Attachments
patch (3.59 KB, patch)
2009-12-09 12:17 PST, Mike Belshe
eric: review+
eric: commit-queue-
followup patch to workaround horribly painful and broken chromium/webkit processes. (3.89 KB, patch)
2009-12-09 16:23 PST, Mike Belshe
no flags
Mike Belshe
Comment 1 2009-12-09 12:17:19 PST
WebKit Review Bot
Comment 2 2009-12-09 12:19:26 PST
style-queue ran check-webkit-style on attachment 44554 [details] without any errors.
Eric Seidel (no email)
Comment 3 2009-12-09 13:24:27 PST
Comment on attachment 44554 [details] patch Looks sane. Although you've already filled in the Reviewed by line, so I'm not sure what needs to be done for this patch if anything...
Darin Fisher (:fishd, Google)
Comment 4 2009-12-09 13:29:53 PST
Comment on attachment 44554 [details] patch > Index: WebKit/chromium/public/WebURLRequest.h > - TargetIsSubFrame, > - TargetIsSubResource, > + TargetIsSubframe, > + TargetIsSubresource, > + TargetIsStyleSheet, > + TargetIsScript, > + TargetIsFontResource, > + TargetIsImage, Removal of webkit api is something we generally try to stage. Otherwise, it puts burden on the person performing the webkit update to land a two-sided patch :-( I think I saw you send michaeln a patch for the Chromium side of this, but in the future please preserve the old webkit api, and then remove it in a subsequent patch once Chromium has been updated. Otherwise, r=me too.
Michael Nordman
Comment 5 2009-12-09 15:42:59 PST
> I think I saw you send michaeln a patch for the Chromium side > of this, but in the future please preserve the old webkit api, > and then remove it in a subsequent patch once Chromium has > been updated. Change looks great, having more nuanced info about what is being retrieved is really nice. As mentioned in http://codereview.chromium.org/477008, can we stage these changes in without the need of the two-headed patch dance (you never know when the change that breaks 500 layout tests will just show up).
Mike Belshe
Comment 6 2009-12-09 16:23:47 PST
Created attachment 44579 [details] followup patch to workaround horribly painful and broken chromium/webkit processes.
WebKit Review Bot
Comment 7 2009-12-09 16:26:27 PST
style-queue ran check-webkit-style on attachment 44579 [details] without any errors.
WebKit Commit Bot
Comment 8 2009-12-10 15:33:31 PST
Comment on attachment 44579 [details] followup patch to workaround horribly painful and broken chromium/webkit processes. Clearing flags on attachment: 44579 Committed r51967: <http://trac.webkit.org/changeset/51967>
Eric Seidel (no email)
Comment 9 2009-12-28 23:29:54 PST
I'm confused as to if this should still be open or not?
Eric Seidel (no email)
Comment 10 2009-12-28 23:30:26 PST
I believe this has been landed, so marking closed. Please re-open if I'm wrong.
Note You need to log in before you can comment on or make changes to this bug.