[Fetch API] Remove Headers.prototype.getAll()

Remove Headers.prototype.getAll()
It's no longer part of the spec 
(https://github.com/whatwg/fetch/commit/42464c)

intent-to-deprecate-and-remove
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

BUG=645492
Review-Url: https://codereview.chromium.org/2591723003
Cr-Commit-Position: refs/heads/master@{#468022}
Committed: https://chromium.googlesource.com/chromium/src/+/73dde766a935605604b2d7cca45033f8dbd9c6fb

[dhna, 2016-12-20 14:02:02]

Description was changed from

==========
[Fetch API] Remove Headers.prototype.getAll()

BUG=645492
==========

to

==========
Remove Headers.prototype.getAll()
It's no longer part of the spec 
(https://github.com/whatwg/fetch/commit/42464c)

BUG=645492
==========

[dhna, 2016-12-20 14:02:02]

corona10@gmail.com changed reviewers:
+ yhirano@chromium.org

[dhna, 2016-12-20 14:02:17]

yhirano@
PTAL

[dhna, 2016-12-20 14:04:42]

corona10@gmail.com changed reviewers:
+ jsbell@chromium.org

[yhirano, 2016-12-20 14:08:02]

On 2016/12/20 14:02:17, dhna wrote:
> yhirano@
> PTAL

This is a public API change and we need an intent-to-deprecate /
intent-to-remove discussion. You may need to prove that not so many people are
using the feature.
See http://www.chromium.org/blink/launching-features (though it's for the launch
process)

[yhirano, 2016-12-20 14:08:38]

On 2016/12/20 14:08:02, yhirano wrote:
> On 2016/12/20 14:02:17, dhna wrote:
> > yhirano@
> > PTAL
> 
> This is a public API change and we need an intent-to-deprecate /
> intent-to-remove discussion. You may need to prove that not so many people are
> using the feature.
> See http://www.chromium.org/blink/launching-features (though it's for the
launch
> process)

We need an intent-to-deprecate / intent-to-remove discussion on
blink-dev@chromium.org, I mean.

[dhna, 2016-12-20 14:46:57]

On 2016/12/20 14:08:38, yhirano wrote:
> On 2016/12/20 14:08:02, yhirano wrote:
> > On 2016/12/20 14:02:17, dhna wrote:
> > > yhirano@
> > > PTAL
> > 
> > This is a public API change and we need an intent-to-deprecate /
> > intent-to-remove discussion. You may need to prove that not so many people
are
> > using the feature.
> > See http://www.chromium.org/blink/launching-features (though it's for the
> launch
> > process)
> 
> We need an intent-to-deprecate / intent-to-remove discussion on
> mailto:blink-dev@chromium.org, I mean.

yhirano@
It means we need some data of usage information from use counter to prove it?

[yhirano, 2016-12-20 15:12:03]

On 2016/12/20 14:46:57, dhna wrote:
> On 2016/12/20 14:08:38, yhirano wrote:
> > On 2016/12/20 14:08:02, yhirano wrote:
> > > On 2016/12/20 14:02:17, dhna wrote:
> > > > yhirano@
> > > > PTAL
> > > 
> > > This is a public API change and we need an intent-to-deprecate /
> > > intent-to-remove discussion. You may need to prove that not so many people
> are
> > > using the feature.
> > > See http://www.chromium.org/blink/launching-features (though it's for the
> > launch
> > > process)
> > 
> > We need an intent-to-deprecate / intent-to-remove discussion on
> > mailto:blink-dev@chromium.org, I mean.
> 
> yhirano@
> It means we need some data of usage information from use counter to prove it?

Likely.

[dhna, 2017-03-31 05:59:16]

On 2016/12/20 15:12:03, yhirano wrote:
> On 2016/12/20 14:46:57, dhna wrote:
> > On 2016/12/20 14:08:38, yhirano wrote:
> > > On 2016/12/20 14:08:02, yhirano wrote:
> > > > On 2016/12/20 14:02:17, dhna wrote:
> > > > > yhirano@
> > > > > PTAL
> > > > 
> > > > This is a public API change and we need an intent-to-deprecate /
> > > > intent-to-remove discussion. You may need to prove that not so many
people
> > are
> > > > using the feature.
> > > > See http://www.chromium.org/blink/launching-features (though it's for
the
> > > launch
> > > > process)
> > > 
> > > We need an intent-to-deprecate / intent-to-remove discussion on
> > > mailto:blink-dev@chromium.org, I mean.
> > 
> > yhirano@
> > It means we need some data of usage information from use counter to prove
it?
> 
> Likely.

yhirano@
PTAL

[yhirano, 2017-03-31 06:56:48]

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

[commit-bot: I haz the power, 2017-03-31 06:57:07]

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

[yhirano, 2017-03-31 06:58:24]

Please add a link to the intent-to-deprecate-and-remove thread in the issue
description.

You need to fix webexposed tests when removing a function from an IDL (I'm
running a dry-run, so you will see failures).

[dhna, 2017-03-31 07:19:32]

Description was changed from

==========
Remove Headers.prototype.getAll()
It's no longer part of the spec 
(https://github.com/whatwg/fetch/commit/42464c)

BUG=645492
==========

to

==========
Remove Headers.prototype.getAll()
It's no longer part of the spec 
(https://github.com/whatwg/fetch/commit/42464c)

intent-to-deprecate-and-remove
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

BUG=645492
==========

[commit-bot: I haz the power, 2017-03-31 08:59:28]

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

[commit-bot: I haz the power, 2017-03-31 08:59:29]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[dhna, 2017-03-31 09:23:47]

On 2017/03/31 06:58:24, yhirano wrote:
> Please add a link to the intent-to-deprecate-and-remove thread in the issue
> description.
> 
> You need to fix webexposed tests when removing a function from an IDL (I'm
> running a dry-run, so you will see failures).

yhirano@

Got it.
I will update
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
and check out why layout test failed.

[yhirano, 2017-04-03 13:49:20]

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

[commit-bot: I haz the power, 2017-04-03 13:49:34]

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, 2017-04-03 16:03:40]

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

[commit-bot: I haz the power, 2017-04-03 16:03:41]

Dry run: Try jobs failed on following builders:
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[dhna, 2017-04-03 18:29:42]

On 2017/03/31 09:23:47, dhna wrote:
> On 2017/03/31 06:58:24, yhirano wrote:
> > Please add a link to the intent-to-deprecate-and-remove thread in the issue
> > description.
> > 
> > You need to fix webexposed tests when removing a function from an IDL (I'm
> > running a dry-run, so you will see failures).
> 
> yhirano@
> 
> Got it.
> I will update
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> and check out why layout test failed.

I fixed test codes to pass it.
PTAL

[dhna, 2017-04-03 18:30:23]

Patchset #4 (id:60001) has been deleted

[yhirano, 2017-04-04 00:17:05]

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

[commit-bot: I haz the power, 2017-04-04 00:17:39]

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, 2017-04-04 01:48:43]

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

[commit-bot: I haz the power, 2017-04-04 01:48:45]

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

[yhirano, 2017-04-04 01:53:23]

On 2017/04/03 18:29:42, dhna wrote:
> On 2017/03/31 09:23:47, dhna wrote:
> > On 2017/03/31 06:58:24, yhirano wrote:
> > > Please add a link to the intent-to-deprecate-and-remove thread in the
issue
> > > description.
> > > 
> > > You need to fix webexposed tests when removing a function from an IDL (I'm
> > > running a dry-run, so you will see failures).
> > 
> > yhirano@
> > 
> > Got it.
> > I will update
> >
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> > and check out why layout test failed.
> 
> I fixed test codes to pass it.
> PTAL

Please fix tests.
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel...

[yhirano, 2017-04-04 04:31:45]

On 2017/04/04 01:53:23, yhirano (slow) wrote:
> On 2017/04/03 18:29:42, dhna wrote:
> > On 2017/03/31 09:23:47, dhna wrote:
> > > On 2017/03/31 06:58:24, yhirano wrote:
> > > > Please add a link to the intent-to-deprecate-and-remove thread in the
> issue
> > > > description.
> > > > 
> > > > You need to fix webexposed tests when removing a function from an IDL
(I'm
> > > > running a dry-run, so you will see failures).
> > > 
> > > yhirano@
> > > 
> > > Got it.
> > > I will update
> > >
> >
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> > > and check out why layout test failed.
> > 
> > I fixed test codes to pass it.
> > PTAL
> 
> Please fix tests.
>
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel...

Just in case you don't know, by clicking "layout_test_results" link you get
https://storage.googleapis.com/chromium-layout-test-archives/mac_chromium_rel...
which is super useful.

[dhna, 2017-04-04 04:51:40]

On 2017/04/04 04:31:45, yhirano (slow) wrote:
> On 2017/04/04 01:53:23, yhirano (slow) wrote:
> > On 2017/04/03 18:29:42, dhna wrote:
> > > On 2017/03/31 09:23:47, dhna wrote:
> > > > On 2017/03/31 06:58:24, yhirano wrote:
> > > > > Please add a link to the intent-to-deprecate-and-remove thread in the
> > issue
> > > > > description.
> > > > > 
> > > > > You need to fix webexposed tests when removing a function from an IDL
> (I'm
> > > > > running a dry-run, so you will see failures).
> > > > 
> > > > yhirano@
> > > > 
> > > > Got it.
> > > > I will update
> > > >
> > >
> >
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> > > > and check out why layout test failed.
> > > 
> > > I fixed test codes to pass it.
> > > PTAL
> > 
> > Please fix tests.
> >
>
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel...
> 
> Just in case you don't know, by clicking "layout_test_results" link you get
>
https://storage.googleapis.com/chromium-layout-test-archives/mac_chromium_rel...
> which is super useful.

yhirano@
I didn't know that :)
This is super useful!!
I just tested by my hands before I know this!
Thanks

[dhna, 2017-04-04 05:03:32]

On 2017/04/04 04:51:40, dhna wrote:
> On 2017/04/04 04:31:45, yhirano (slow) wrote:
> > On 2017/04/04 01:53:23, yhirano (slow) wrote:
> > > On 2017/04/03 18:29:42, dhna wrote:
> > > > On 2017/03/31 09:23:47, dhna wrote:
> > > > > On 2017/03/31 06:58:24, yhirano wrote:
> > > > > > Please add a link to the intent-to-deprecate-and-remove thread in
the
> > > issue
> > > > > > description.
> > > > > > 
> > > > > > You need to fix webexposed tests when removing a function from an
IDL
> > (I'm
> > > > > > running a dry-run, so you will see failures).
> > > > > 
> > > > > yhirano@
> > > > > 
> > > > > Got it.
> > > > > I will update
> > > > >
> > > >
> > >
> >
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> > > > > and check out why layout test failed.
> > > > 
> > > > I fixed test codes to pass it.
> > > > PTAL
> > > 
> > > Please fix tests.
> > >
> >
>
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel...
> > 
> > Just in case you don't know, by clicking "layout_test_results" link you get
> >
>
https://storage.googleapis.com/chromium-layout-test-archives/mac_chromium_rel...
> > which is super useful.
> 
> yhirano@
> I didn't know that :)
> This is super useful!!
> I just tested by my hands before I know this!
> Thanks

yhirano@

I checked broken tests are passed locally.

PTAL

[yhirano, 2017-04-04 05:09:25]

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

[commit-bot: I haz the power, 2017-04-04 05:09:40]

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

[dhna, 2017-04-04 05:11:43]

On 2017/04/04 05:03:32, dhna wrote:
> On 2017/04/04 04:51:40, dhna wrote:
> > On 2017/04/04 04:31:45, yhirano (slow) wrote:
> > > On 2017/04/04 01:53:23, yhirano (slow) wrote:
> > > > On 2017/04/03 18:29:42, dhna wrote:
> > > > > On 2017/03/31 09:23:47, dhna wrote:
> > > > > > On 2017/03/31 06:58:24, yhirano wrote:
> > > > > > > Please add a link to the intent-to-deprecate-and-remove thread in
> the
> > > > issue
> > > > > > > description.
> > > > > > > 
> > > > > > > You need to fix webexposed tests when removing a function from an
> IDL
> > > (I'm
> > > > > > > running a dry-run, so you will see failures).
> > > > > > 
> > > > > > yhirano@
> > > > > > 
> > > > > > Got it.
> > > > > > I will update
> > > > > >
> > > > >
> > > >
> > >
> >
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> > > > > > and check out why layout test failed.
> > > > > 
> > > > > I fixed test codes to pass it.
> > > > > PTAL
> > > > 
> > > > Please fix tests.
> > > >
> > >
> >
>
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel...
> > > 
> > > Just in case you don't know, by clicking "layout_test_results" link you
get
> > >
> >
>
https://storage.googleapis.com/chromium-layout-test-archives/mac_chromium_rel...
> > > which is super useful.
> > 
> > yhirano@
> > I didn't know that :)
> > This is super useful!!
> > I just tested by my hands before I know this!
> > Thanks
> 
> yhirano@
> 
> I checked broken tests are passed locally.
> 
> PTAL

FYI, Use-counter still remains.
https://codereview.chromium.org/2593673002/
Should we remove later or with this CL?

[commit-bot: I haz the power, 2017-04-04 06:42:02]

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

[commit-bot: I haz the power, 2017-04-04 06:42:03]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[dhna, 2017-04-04 08:17:16]

On 2017/04/04 05:11:43, dhna wrote:
> On 2017/04/04 05:03:32, dhna wrote:
> > On 2017/04/04 04:51:40, dhna wrote:
> > > On 2017/04/04 04:31:45, yhirano (slow) wrote:
> > > > On 2017/04/04 01:53:23, yhirano (slow) wrote:
> > > > > On 2017/04/03 18:29:42, dhna wrote:
> > > > > > On 2017/03/31 09:23:47, dhna wrote:
> > > > > > > On 2017/03/31 06:58:24, yhirano wrote:
> > > > > > > > Please add a link to the intent-to-deprecate-and-remove thread
in
> > the
> > > > > issue
> > > > > > > > description.
> > > > > > > > 
> > > > > > > > You need to fix webexposed tests when removing a function from
an
> > IDL
> > > > (I'm
> > > > > > > > running a dry-run, so you will see failures).
> > > > > > > 
> > > > > > > yhirano@
> > > > > > > 
> > > > > > > Got it.
> > > > > > > I will update
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
> > > > > > > and check out why layout test failed.
> > > > > > 
> > > > > > I fixed test codes to pass it.
> > > > > > PTAL
> > > > > 
> > > > > Please fix tests.
> > > > >
> > > >
> > >
> >
>
https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel...
> > > > 
> > > > Just in case you don't know, by clicking "layout_test_results" link you
> get
> > > >
> > >
> >
>
https://storage.googleapis.com/chromium-layout-test-archives/mac_chromium_rel...
> > > > which is super useful.
> > > 
> > > yhirano@
> > > I didn't know that :)
> > > This is super useful!!
> > > I just tested by my hands before I know this!
> > > Thanks
> > 
> > yhirano@
> > 
> > I checked broken tests are passed locally.
> > 
> > PTAL
> 
> FYI, Use-counter still remains.
> https://codereview.chromium.org/2593673002/
> Should we remove later or with this CL?

Done. Updated. It looks like last broken test.(and I wish..)

[yhirano, 2017-04-05 03:10:22]

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

[commit-bot: I haz the power, 2017-04-05 03:10:38]

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, 2017-04-05 05:22:38]

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

[commit-bot: I haz the power, 2017-04-05 05:22:39]

Dry run: This issue passed the CQ dry run.

[yhirano, 2017-04-05 05:26:36]

lgtm

Thank you for working on this issue!

[dhna, 2017-04-05 06:53:54]

The CQ bit was checked by corona10@gmail.com

[commit-bot: I haz the power, 2017-04-05 06:54:11]

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, 2017-04-05 07:01:10]

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

[commit-bot: I haz the power, 2017-04-05 07:01:11]

Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[dhna, 2017-04-05 07:52:43]

corona10@gmail.com changed reviewers:
+ tkent@chromium.org

[dhna, 2017-04-05 07:53:01]

On 2017/04/05 07:01:11, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

tkent@
I need your review. PTAL

[tkent, 2017-04-05 07:57:47]

> intent-to-deprecate-and-remove
> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

Your intent was for deprecate-and-remove.  This CL looks to remove the feature
without deprecation.

[yhirano, 2017-04-05 08:07:07]

On 2017/04/05 07:57:47, tkent wrote:
> > intent-to-deprecate-and-remove
> > https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0
> 
> Your intent was for deprecate-and-remove.  This CL looks to remove the feature
> without deprecation.

Sorry, that's my fault. I didn't understand the deprecation process...

[dhna, 2017-04-05 09:09:11]

On 2017/04/05 08:07:07, yhirano wrote:
> On 2017/04/05 07:57:47, tkent wrote:
> > > intent-to-deprecate-and-remove
> > >
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0
> > 
> > Your intent was for deprecate-and-remove.  This CL looks to remove the
feature
> > without deprecation.
> 
> Sorry, that's my fault. I didn't understand the deprecation process...

tkent@
Thanks for the review.
I am new to work in this process also.

If you are okay, Can I get some tips how to show a deprecated message on API?
(Relevant code will be good to me!)

[tkent, 2017-04-05 10:06:06]

On 2017/04/05 at 09:09:11, corona10 wrote:
> If you are okay, Can I get some tips how to show a deprecated message on API?
> (Relevant code will be good to me!)

Required C++ change is just to update Deprecation::deprecationMessage().  You
need to update some -expected.txt for tests using the feature.

[dhna, 2017-04-05 17:53:46]

On 2017/04/05 10:06:06, tkent wrote:
> On 2017/04/05 at 09:09:11, corona10 wrote:
> > If you are okay, Can I get some tips how to show a deprecated message on
API?
> > (Relevant code will be good to me!)
> 
> Required C++ change is just to update Deprecation::deprecationMessage().  You
> need to update some -expected.txt for tests using the feature.

Thanks for letting me know the way.
I found the code to add a deprecated message on the function you mentioned.
It looks like not a hard job.
But first of the all, What I need to do is adding this deprecated features on
the ChromeStatus.
However, as I known, I don't have permission to create this feature on the
ChromeStatus.
Because I don't have chromium.org account.

[tkent, 2017-04-05 22:44:45]

> But first of the all, What I need to do is adding this deprecated features on
the ChromeStatus.
> However, as I known, I don't have permission to create this feature on the
ChromeStatus.
> Because I don't have chromium.org account.

Please follow 'Request "edit" access' link at the bottom of chromestatus.com.

[dhna, 2017-04-06 01:00:08]

On 2017/04/05 22:44:45, tkent wrote:
> > But first of the all, What I need to do is adding this deprecated features
on
> the ChromeStatus.
> > However, as I known, I don't have permission to create this feature on the
> ChromeStatus.
> > Because I don't have http://chromium.org account.
> 
> Please follow 'Request "edit" access' link at the bottom of
http://chromestatus.com.

tkent@
Thanks, I submit the form.
Now I am waiting for their reviews.
Thank you for your help!

[dhna, 2017-04-11 13:03:11]

On 2017/04/06 01:00:08, dhna wrote:
> On 2017/04/05 22:44:45, tkent wrote:
> > > But first of the all, What I need to do is adding this deprecated features
> on
> > the ChromeStatus.
> > > However, as I known, I don't have permission to create this feature on the
> > ChromeStatus.
> > > Because I don't have http://chromium.org account.
> > 
> > Please follow 'Request "edit" access' link at the bottom of
> http://chromestatus.com.
> 
> tkent@
> Thanks, I submit the form.
> Now I am waiting for their reviews.
> Thank you for your help!

tkent@
I got a request permission from Chrome Status right now.
Also, I am now trying to add a feature on Chrome Status. 
One question is:
I agree that the deprecated period is necessary for the removal of most APIs.
But in this case, the usage rate is 0.0, I think we can remove it directly
without a deprecated period. Also, I think that the deprecated period can rather
increase the API usage rate.
WDYT?
https://www.chromestatus.com/metrics/feature/timeline/popularity/1724

[tkent, 2017-04-12 13:41:16]

On 2017/04/11 at 13:03:11, corona10 wrote:
> I agree that the deprecated period is necessary for the removal of most APIs.
But in this case, the usage rate is 0.0, I think we can remove it directly
without a deprecated period. Also, I think that the deprecated period can rather
increase the API usage rate.
> WDYT?
> https://www.chromestatus.com/metrics/feature/timeline/popularity/1724

As I wrote, the approved intent for this feature was "deprecate and remove", not
"remove".
If you'd like to change your intention, you need to say it in the intent thread,
and need to get approval again.

[dhna, 2017-04-12 15:30:10]

On 2017/04/12 13:41:16, tkent wrote:
> On 2017/04/11 at 13:03:11, corona10 wrote:
> > I agree that the deprecated period is necessary for the removal of most
APIs.
> But in this case, the usage rate is 0.0, I think we can remove it directly
> without a deprecated period. Also, I think that the deprecated period can
rather
> increase the API usage rate.
> > WDYT?
> > https://www.chromestatus.com/metrics/feature/timeline/popularity/1724
> 
> As I wrote, the approved intent for this feature was "deprecate and remove",
not
> "remove".
> If you'd like to change your intention, you need to say it in the intent
thread,
> and need to get approval again.

yhirano@ tkent@

I request to change my intention.
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

[dhna, 2017-04-13 15:08:25]

On 2017/04/12 15:30:10, dhna wrote:
> On 2017/04/12 13:41:16, tkent wrote:
> > On 2017/04/11 at 13:03:11, corona10 wrote:
> > > I agree that the deprecated period is necessary for the removal of most
> APIs.
> > But in this case, the usage rate is 0.0, I think we can remove it directly
> > without a deprecated period. Also, I think that the deprecated period can
> rather
> > increase the API usage rate.
> > > WDYT?
> > > https://www.chromestatus.com/metrics/feature/timeline/popularity/1724
> > 
> > As I wrote, the approved intent for this feature was "deprecate and remove",
> not
> > "remove".
> > If you'd like to change your intention, you need to say it in the intent
> thread,
> > and need to get approval again.
> 
> yhirano@ tkent@
> 
> I request to change my intention.
> https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

tkent@ yhirano@ 

I requested to change the intention to 'Remove' from 'Deprecate and remove'.
And I got approved from the thread.

Also, I added this feature on the Chrome Status.
https://www.chromestatus.com/feature/5656023951998976

I think that we can proceed this CL to remove this API.

[tkent, 2017-04-14 03:17:11]

lgtm

[dhna, 2017-04-14 03:19:06]

The CQ bit was checked by corona10@gmail.com

[commit-bot: I haz the power, 2017-04-14 03:19:18]

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, 2017-04-14 03:22:27]

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

[commit-bot: I haz the power, 2017-04-14 03:22:28]

Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[dhna, 2017-04-14 09:37:30]

The CQ bit was checked by corona10@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-14 09:37:39]

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, 2017-04-14 11:09:11]

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

[commit-bot: I haz the power, 2017-04-14 11:09:12]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[dhna, 2017-04-14 11:19:35]

The CQ bit was checked by corona10@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-14 11:19:42]

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

[dhna, 2017-04-14 12:15:10]

The CQ bit was checked by corona10@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-14 12:15:20]

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

[dhna, 2017-04-14 13:05:15]

The CQ bit was checked by corona10@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-14 13:05:24]

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

[dhna, 2017-04-14 13:10:52]

The CQ bit was unchecked by corona10@gmail.com

[dhna, 2017-04-14 13:17:05]

The CQ bit was checked by corona10@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-14 13:17:13]

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

[dhna, 2017-04-14 14:14:21]

corona10@gmail.com changed reviewers:
+ timvolodine@chromium.org

[dhna, 2017-04-14 14:15:22]

On 2017/04/14 03:22:28, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
>
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
>   linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

timvolodine@
I request your review for this file. 
'android_webview/tools/system_webview_shell/test/data/webexposed/global-interface-listing-expected.txt'

[commit-bot: I haz the power, 2017-04-14 15:05:01]

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

[commit-bot: I haz the power, 2017-04-14 15:05:02]

Dry run: This issue passed the CQ dry run.

[dhna, 2017-04-18 12:20:46]

corona10@gmail.com changed reviewers:
+ darin@chromium.org

[dhna, 2017-04-28 02:28:05]

On 2017/04/14 14:15:22, dhna wrote:
> On 2017/04/14 03:22:28, commit-bot: I haz the power wrote:
> > Try jobs failed on following builders:
> >   cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
> >
>
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
> >   linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
> >
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
> 
> timvolodine@
> I request your review for this file. 
>
'android_webview/tools/system_webview_shell/test/data/webexposed/global-interface-listing-expected.txt'

timvolodine@
PTAL

[timvolodine, 2017-04-28 13:46:28]

On 2017/04/28 02:28:05, dhna wrote:
> On 2017/04/14 14:15:22, dhna wrote:
> > On 2017/04/14 03:22:28, commit-bot: I haz the power wrote:
> > > Try jobs failed on following builders:
> > >   cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
> > >
> >
>
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)
> > >   linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
> > >
> >
>
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
> > 
> > timvolodine@
> > I request your review for this file. 
> >
>
'android_webview/tools/system_webview_shell/test/data/webexposed/global-interface-listing-expected.txt'
> 
> timvolodine@
> PTAL

lgtm, thanks!

[dhna, 2017-04-28 13:48:45]

The CQ bit was checked by corona10@gmail.com

[dhna, 2017-04-28 13:48:45]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
yhirano@chromium.org
Link to the patchset: https://codereview.chromium.org/2591723003/#ps240001
(title: "Fix tests")

[commit-bot: I haz the power, 2017-04-28 13:49:23]

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, 2017-04-28 13:52:49]

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

[commit-bot: I haz the power, 2017-04-28 13:52:51]

Try jobs failed on following builders:
  chromeos_amd64-generic_chromium_compile_only_ng on
master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[dhna, 2017-04-28 14:44:19]

The CQ bit was checked by corona10@gmail.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-28 14:44:50]

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, 2017-04-28 16:19:04]

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

[commit-bot: I haz the power, 2017-04-28 16:19:06]

Dry run: This issue passed the CQ dry run.

[dhna, 2017-04-28 16:21:14]

The CQ bit was checked by corona10@gmail.com

[dhna, 2017-04-28 16:21:14]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org,
yhirano@chromium.org, timvolodine@chromium.org
Link to the patchset: https://codereview.chromium.org/2591723003/#ps280001
(title: "Update get.")

[commit-bot: I haz the power, 2017-04-28 16:21:45]

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, 2017-04-28 16:27:35]

CQ is committing da patch.

Bot data: {"patchset_id": 280001, "attempt_start_ts": 1493396474066120,
"parent_rev": "fa845ac545a12d519ab5cb7d7ba5d9fd57ae2a0c", "commit_rev":
"73dde766a935605604b2d7cca45033f8dbd9c6fb"}

[commit-bot: I haz the power, 2017-04-28 16:27:51]

Description was changed from

==========
Remove Headers.prototype.getAll()
It's no longer part of the spec 
(https://github.com/whatwg/fetch/commit/42464c)

intent-to-deprecate-and-remove
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

BUG=645492
==========

to

==========
Remove Headers.prototype.getAll()
It's no longer part of the spec 
(https://github.com/whatwg/fetch/commit/42464c)

intent-to-deprecate-and-remove
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/x3YXciXQWM0

BUG=645492

Review-Url: https://codereview.chromium.org/2591723003
Cr-Commit-Position: refs/heads/master@{#468022}
Committed:
https://chromium.googlesource.com/chromium/src/+/73dde766a935605604b2d7cca450...
==========

[commit-bot: I haz the power, 2017-04-28 16:27:53]

Committed patchset #14 (id:280001) as
https://chromium.googlesource.com/chromium/src/+/73dde766a935605604b2d7cca450...