doc.write blocking intervention warning header

In cases where doc.write blocking intervention could have applied had it
not been a faster connection or a reload, send a warning level
intervention header in the GET request:
Intervention: <https://www.chromestatus.com/feature/5718547946799104>; ;
level="warning"
BUG=649082
Committed: https://crrev.com/6be2bff3df41039c4d3e92680b8ebb72f17a45ae
Cr-Commit-Position: refs/heads/master@{#423257}

[shivanisha, 2016-10-03 12:56:32]

The CQ bit was checked by shivanisha@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-03 12:56:37]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-03 12:58:46]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-03 12:58:47]

Dry run: Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  ios-simulator on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  win_clang on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/...)

[shivanisha, 2016-10-03 15:32:38]

The CQ bit was checked by shivanisha@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-03 15:32:54]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-03 15:44:05]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-03 15:44:06]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[shivanisha, 2016-10-03 17:07:44]

The CQ bit was checked by shivanisha@chromium.org to run a CQ dry run

[shivanisha, 2016-10-03 17:07:59]

Patchset #2 (id:20001) has been deleted

[commit-bot: I haz the power, 2016-10-03 17:08:07]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[shivanisha, 2016-10-03 17:11:31]

shivanisha@chromium.org changed reviewers:
+ japhet@chromium.org

[shivanisha, 2016-10-03 17:11:58]

PTAL, Thanks!

[commit-bot: I haz the power, 2016-10-03 18:17:44]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-03 18:17:45]

Dry run: This issue passed the CQ dry run.

[Nate Chapin, 2016-10-04 20:33:42]

https://codereview.chromium.org/2389753002/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/fetch/FetchContext.h (right):

https://codereview.chromium.org/2389753002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/fetch/FetchContext.h:79: std::pair<AtomicString,
AtomicString>&) const;
Let's just take a non-const ResourceRequest& here and add a comment noting why
it's non-const. This pair<> feels like overkill.

[shivanisha, 2016-10-05 16:48:04]

The CQ bit was checked by shivanisha@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-05 16:48:31]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[shivanisha, 2016-10-05 17:11:55]

https://codereview.chromium.org/2389753002/diff/40001/third_party/WebKit/Sour...
File third_party/WebKit/Source/core/fetch/FetchContext.h (right):

https://codereview.chromium.org/2389753002/diff/40001/third_party/WebKit/Sour...
third_party/WebKit/Source/core/fetch/FetchContext.h:79: std::pair<AtomicString,
AtomicString>&) const;
On 2016/10/04 at 20:33:42, Nate Chapin wrote:
> Let's just take a non-const ResourceRequest& here and add a comment noting why
it's non-const. This pair<> feels like overkill.

Sounds good. done.

[Nate Chapin, 2016-10-05 18:00:33]

lgtm

[commit-bot: I haz the power, 2016-10-05 19:27:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-05 19:27:47]

Dry run: Exceeded global retry quota

[shivanisha, 2016-10-05 19:39:26]

The CQ bit was checked by shivanisha@chromium.org

[commit-bot: I haz the power, 2016-10-05 19:39:53]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-05 19:47:26]

Committed patchset #3 (id:60001)

[commit-bot: I haz the power, 2016-10-05 19:51:03]

Description was changed from

==========
In cases where doc.write blocking intervention could have applied had it
not been a faster connection or a reload, send a warning level
intervention header in the GET request:
Intervention: <https://www.chromestatus.com/feature/5718547946799104> ;
level="warning"
BUG=649082
==========

to

==========
In cases where doc.write blocking intervention could have applied had it
not been a faster connection or a reload, send a warning level
intervention header in the GET request:
Intervention: <https://www.chromestatus.com/feature/5718547946799104> ;
level="warning"
BUG=649082

Committed: https://crrev.com/6be2bff3df41039c4d3e92680b8ebb72f17a45ae
Cr-Commit-Position: refs/heads/master@{#423257}
==========

[commit-bot: I haz the power, 2016-10-05 19:51:04]

Patchset 3 (id:??) landed as
https://crrev.com/6be2bff3df41039c4d3e92680b8ebb72f17a45ae
Cr-Commit-Position: refs/heads/master@{#423257}