Make Document.charset an alias of characterSet, as per spec

Make Document.charset an alias of characterSet, as per spec

https://dom.spec.whatwg.org/#interface-document

Remove counters DocumentInputEncoding and DocumentCharset, they have
fulfilled their purpose as both have been specified as aliases based on
the data collected:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27435
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27436

BUG=438392
R=dominicc@chromium.org

Committed: https://crrev.com/5a4c2803cbed040ea1afe4d59c316f473607836e
Cr-Commit-Position: refs/heads/master@{#351508}

[philipj_slow, 2015-09-24 09:37:30]

The CQ bit was checked by philipj@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2015-09-24 09:37:52]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1365923002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1365923002/1

[commit-bot: I haz the power, 2015-09-24 11:43:01]

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

[commit-bot: I haz the power, 2015-09-24 11:43:01]

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

[dominicc (has gone to gerrit), 2015-09-28 06:48:09]

On 2015/09/24 at 11:43:01, commit-bot wrote:
> Dry run: Try jobs failed on following builders:
>   win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

One nit inline. Sorry for the slow reply.

[philipj_slow, 2015-09-28 09:08:21]

On 2015/09/28 06:48:09, dominicc wrote:
> On 2015/09/24 at 11:43:01, commit-bot wrote:
> > Dry run: Try jobs failed on following builders:
> >   win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
>
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
> 
> One nit inline. Sorry for the slow reply.

Did you forget to submit your nit, or was it something about the failing bot?

[chromium-reviews, 2015-09-29 00:40:56]

Gah, sorry.

I was wondering why enum 127 was removed, and what's happening with enum
427. (IIRC)
On Sep 28, 2015 6:08 PM, <philipj@opera.com> wrote:

> On 2015/09/28 06:48:09, dominicc wrote:
>
>> On 2015/09/24 at 11:43:01, commit-bot wrote:
>> > Dry run: Try jobs failed on following builders:
>> >   win_chromium_x64_rel_ng on tryserver.chromium.win (JOB_FAILED,
>>
>
>
>
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...
> )
>
> One nit inline. Sorry for the slow reply.
>>
>
> Did you forget to submit your nit, or was it something about the failing
> bot?
>
> https://codereview.chromium.org/1365923002/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[philipj_slow, 2015-09-29 07:29:32]

On 2015/09/29 00:40:56, chromium-reviews wrote:
> Gah, sorry.
> 
> I was wondering why enum 127 was removed, and what's happening with enum
> 427. (IIRC)

I had "Also remove the use counters that have done their job" in the
description, but I've expanded on that to clarify.

As for DocumentSetCharset (427), that has already been removed from
UseCounter.h, the apparent drop in usage is just an artefact of that.

[dominicc (has gone to gerrit), 2015-09-30 05:36:23]

The CQ bit was checked by dominicc@chromium.org

[dominicc (has gone to gerrit), 2015-09-30 05:36:23]

lgtm

[commit-bot: I haz the power, 2015-09-30 05:36:30]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1365923002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1365923002/1

[commit-bot: I haz the power, 2015-09-30 07:24:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-30 07:25:12]

Patchset 1 (id:??) landed as
https://crrev.com/5a4c2803cbed040ea1afe4d59c316f473607836e
Cr-Commit-Position: refs/heads/master@{#351508}