Temporarily remove didReceiveDataForMainResource() implementation

Temporarily remove didReceiveDataForMainResource() implementation

The method signature of
blink::WebApplicationCacheHost::didReceiveDataForMainResource() is going to be
changed. Not to break build, need to remove the implementation of the
interface in Chromium.

Blink side CL is here: https://codereview.chromium.org/618583002/

R=mkwst,jam
BUG=418885
Committed: https://crrev.com/715a73be0dfef058b5d131189cb0a205ce2fb027
Cr-Commit-Position: refs/heads/master@{#297780}

[tyoshino (SeeGerritForStatus), 2014-10-01 03:43:13]

tyoshino@chromium.org changed reviewers:
+ jam@chromium.org

[tyoshino (SeeGerritForStatus), 2014-10-01 03:47:21]

Hi jam. Please take a look.

"overload" annotation checker prevents me from duplicating the methods while
Blink side change is landing (the checker requires both annotated, but the
compiler refuses one that doesn't actually override (not defined in Blink API)).
I'd like to avoid renaming the methods temporarily. Fortunately, the methods are
no-op for now. Please let me just comment out them temporarily while Blink side
change is landing.

[Mike West, 2014-10-01 08:53:14]

mkwst@chromium.org changed reviewers:
+ mkwst@chromium.org

[Mike West, 2014-10-01 08:53:15]

Rather than commenting them out, please just delete the code. You can always
revert later.

[tyoshino (SeeGerritForStatus), 2014-10-01 08:58:37]

On 2014/10/01 08:53:15, Mike West wrote:
> Rather than commenting them out, please just delete the code. You can always
> revert later.

Done!

[Mike West, 2014-10-01 09:06:57]

mkwst@chromium.org changed reviewers:
+ jochen@chromium.org

[Mike West, 2014-10-01 09:06:58]

LGTM, but you'll need a content/ OWNER to stamp the change.

Perhaps Jochen has a spare cycle or two to take a look at this purely negative
change.

[Mike West, 2014-10-01 09:07:53]

(Also, would you mind updating the change description to explain what you're
doing here? "Correct data size argument type in resource loading path to
unsigned" doesn't seem accurate.)

[jam, 2014-10-01 22:09:22]

lgtm

[tyoshino (SeeGerritForStatus), 2014-10-02 03:22:24]

On 2014/10/01 09:07:53, Mike West wrote:
> (Also, would you mind updating the change description to explain what you're
> doing here? "Correct data size argument type in resource loading path to
> unsigned" doesn't seem accurate.)

Done

[tyoshino (SeeGerritForStatus), 2014-10-02 03:22:38]

The CQ bit was checked by tyoshino@chromium.org

[commit-bot: I haz the power, 2014-10-02 03:23:46]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/615823002/50001

[tyoshino (SeeGerritForStatus), 2014-10-02 03:43:32]

The CQ bit was unchecked by tyoshino@chromium.org

[tyoshino (SeeGerritForStatus), 2014-10-02 03:43:46]

The CQ bit was checked by tyoshino@chromium.org

[commit-bot: I haz the power, 2014-10-02 03:44:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/615823002/50001

[commit-bot: I haz the power, 2014-10-02 04:16:18]

Committed patchset #4 (id:50001) as 25d1763c243b16bb86258c287910f8cbfd18b4d8

[commit-bot: I haz the power, 2014-10-02 04:16:55]

Patchset 4 (id:??) landed as
https://crrev.com/715a73be0dfef058b5d131189cb0a205ce2fb027
Cr-Commit-Position: refs/heads/master@{#297780}