Count element name validity per DOM versus HTML parsing.

Count element name validity per DOM versus HTML parsing.

DOM uses the XML "Name" production for tag name validity, whereas
the HTML parser does something different. This creates edge cases
where some elements can only be created by createElement, like
<:foo>, and some can only be created by the HTML parser, like
<foo">.

This adds a use counter to count how often pages use createElement,
etc. with tag names that are valid in one system but not the other
to determine whether it is practical for DOM to use the same rules
as HTML for tag names.

BUG=648179
Review-Url: https://codereview.chromium.org/2838123002
Cr-Commit-Position: refs/heads/master@{#467219}
Committed: https://chromium.googlesource.com/chromium/src/+/cb56b4ff751b3fef6ada2ae547a2c374caca8361

[dominicc (has gone to gerrit), 2017-04-25 07:32:40]

Description was changed from

==========
Count element and attribute name validity in DOM versus HTML parsing.

DOM uses the XML "Name" production for tag and attribute name
validity, whereas the HTML parser does something different. This
creates edge cases where some elements can only be created by
createElement, like <:foo>, and some can only be created by the HTML
parser, like <foo">.

This adds a use counter to count how often pages use createElement,
setAttribute, etc. to with tag names and attribute names that are
valid in one system but not the other to determine whether it is
practical for DOM to use the same rules as HTML for tag and attribute
names.

BUG=648179
==========

to

==========
Count element and attribute name validity in DOM versus HTML parsing.

DOM uses the XML "Name" production for tag and attribute name
validity, whereas the HTML parser does something different. This
creates edge cases where some elements can only be created by
createElement, like <:foo>, and some can only be created by the HTML
parser, like <foo">.

This adds a use counter to count how often pages use createElement,
setAttribute, etc. to with tag names and attribute names that are
valid in one system but not the other to determine whether it is
practical for DOM to use the same rules as HTML for tag and attribute
names.

BUG=648179
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
==========

[dominicc (has gone to gerrit), 2017-04-25 08:45:08]

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

[commit-bot: I haz the power, 2017-04-25 08:45:18]

Dry run: CQ is trying da patch.

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

[dominicc (has gone to gerrit), 2017-04-25 08:49:08]

Description was changed from

==========
Count element and attribute name validity in DOM versus HTML parsing.

DOM uses the XML "Name" production for tag and attribute name
validity, whereas the HTML parser does something different. This
creates edge cases where some elements can only be created by
createElement, like <:foo>, and some can only be created by the HTML
parser, like <foo">.

This adds a use counter to count how often pages use createElement,
setAttribute, etc. to with tag names and attribute names that are
valid in one system but not the other to determine whether it is
practical for DOM to use the same rules as HTML for tag and attribute
names.

BUG=648179
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
==========

to

==========
Count element name validity per DOM versus HTML parsing.

DOM uses the XML "Name" production for tag name validity, whereas
the HTML parser does something different. This creates edge cases
where some elements can only be created by createElement, like
<:foo>, and some can only be created by the HTML parser, like
<foo">.

This adds a use counter to count how often pages use createElement,
etc. with tag names that are valid in one system but not the other
to determine whether it is practical for DOM to use the same rules
as HTML for tag names.

BUG=648179
==========

[dominicc (has gone to gerrit), 2017-04-25 08:49:42]

dominicc@chromium.org changed reviewers:
+ domenic@chromium.org, tkent@chromium.org

[dominicc (has gone to gerrit), 2017-04-25 08:49:43]

PTAL

[tkent, 2017-04-25 09:14:34]

lgtm

[commit-bot: I haz the power, 2017-04-25 10:30:43]

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

[commit-bot: I haz the power, 2017-04-25 10:30:44]

Dry run: This issue passed the CQ dry run.

[dominicc (has gone to gerrit), 2017-04-26 00:26:29]

The CQ bit was checked by dominicc@chromium.org

[commit-bot: I haz the power, 2017-04-26 00:27:19]

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-26 00:38:23]

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

[commit-bot: I haz the power, 2017-04-26 00:38:25]

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...)

[dominicc (has gone to gerrit), 2017-04-26 02:20:22]

dominicc@chromium.org changed reviewers:
+ ericwilligers@chromium.org
- domenic@chromium.org

[dominicc (has gone to gerrit), 2017-04-26 02:20:23]

+erickwilligers for histograms.xml, PTAL

[haraken, 2017-04-26 02:20:52]

On 2017/04/26 02:20:23, dominicc wrote:
> +erickwilligers for histograms.xml, PTAL

LGTM

[Eric Willigers, 2017-04-26 02:47:44]

lgtm

[dominicc (has gone to gerrit), 2017-04-26 03:00:28]

The CQ bit was checked by dominicc@chromium.org

[commit-bot: I haz the power, 2017-04-26 03:00:50]

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-26 03:07:46]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1493175628375430,
"parent_rev": "84d4dfb32ea85d528373295087f10d0766d556b6", "commit_rev":
"cb56b4ff751b3fef6ada2ae547a2c374caca8361"}

[commit-bot: I haz the power, 2017-04-26 03:08:47]

Description was changed from

==========
Count element name validity per DOM versus HTML parsing.

DOM uses the XML "Name" production for tag name validity, whereas
the HTML parser does something different. This creates edge cases
where some elements can only be created by createElement, like
<:foo>, and some can only be created by the HTML parser, like
<foo">.

This adds a use counter to count how often pages use createElement,
etc. with tag names that are valid in one system but not the other
to determine whether it is practical for DOM to use the same rules
as HTML for tag names.

BUG=648179
==========

to

==========
Count element name validity per DOM versus HTML parsing.

DOM uses the XML "Name" production for tag name validity, whereas
the HTML parser does something different. This creates edge cases
where some elements can only be created by createElement, like
<:foo>, and some can only be created by the HTML parser, like
<foo">.

This adds a use counter to count how often pages use createElement,
etc. with tag names that are valid in one system but not the other
to determine whether it is practical for DOM to use the same rules
as HTML for tag names.

BUG=648179

Review-Url: https://codereview.chromium.org/2838123002
Cr-Commit-Position: refs/heads/master@{#467219}
Committed:
https://chromium.googlesource.com/chromium/src/+/cb56b4ff751b3fef6ada2ae547a2...
==========

[commit-bot: I haz the power, 2017-04-26 03:08:49]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/cb56b4ff751b3fef6ada2ae547a2...