Chrome 143 / Firefox 149 allow more characters in DOM APIs

[hamishwillee]

FF149 adds support for additional characters to be allowed in attribute and element names in https://bugzilla.mozilla.org/show_bug.cgi?id=1773312.

Previously you could only use the chars allowed in XML names - now the rules are less restrictive to allow the same chars as the HTML parser.

Spec update: whatwg/html#7991

Chrome states support in 143:

• https://developer.chrome.com/blog/chrome-143-beta#allow_more_characters_in_javascript_dom_apis
• https://chromestatus.com/feature/6278918763708416

Webkit added support in https://bugs.webkit.org/show_bug.cgi?id=241419 but I don't think this made it to Safari yet.

Related docs work can be tracked in mdn/content#43218

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[caugner]

Are we intentionally omitting namespaces and attribute names? (Also applies to the other ones.)

Suggested change

	"description": "Emoji and more Unicode in element names (valid names match HTML parser)",
	"description": "Emoji and more Unicode in namespace, element, and attribute names (valid names match HTML parser)",

[hamishwillee]

@caugner No we are not - definitely an omission. I applied the following slight variation as search-replace.

Emoji and more Unicode in element and attribute names and namespace prefix (valid names match HTML parser)

The namespace we're talking about here is the namespace prefix to an element and attribute name: it isn't a thing on its own which this proposal might imply.