GitLab

custom-elements: Do not distinguish V0 custom elements and V1 custom elements in :unresolved and :defined matching.

This CL changed the behavior of :unresolved selector for V1-defined
custom elements, and the behavior of :defined selector for V0-defined
custom elements.

The following table shows the current behavior:

		:unresolved	:not(:defined)	:defined
Built-in	false		false		true
Not-defined	true		true		false
V0-defined	false		true		false
V1-defined	true		false		true

After this CL, the behavior is:

		:unresolved	:not(:defined)	:defined
Built-in	false		false		true
Not-defined	true		true		false
V0-defined	false		false*		true*
V1-defined	false*		false		true

V0 custom elements specification defined ':unresolved' and V1 custom
elements specification defines ':defined', but we don't need to
distinguish V0-defined elements and V1-defined elements for these
selectors. The current behavior makes it difficult to migrate V0 custom
elements to V1 custom elements gradually.

Bug: 889336
Change-Id: I48ecced042fe78314b42da4ea65baddb720e38fc
Reviewed-on: https://chromium-review.googlesource.com/1248061Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594582}