Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding [Legacy​ASCII​Case​Insentive​Enum] for element​.insertAdjacent* APIs #968

Closed
ExE-Boss opened this issue Mar 19, 2021 · 1 comment

Comments

@ExE-Boss
Copy link
Contributor

ExE-Boss commented Mar 19, 2021

The element.insertAdjacentElement, element.insertAdjacentText and element.insertAdjacentHTML APIs take a where/position argument of DOMString that is ASCII lowercased and treated as if it were converted to the following enum:

enum InsertPosition {
	"beforebegin",
	"afterbegin",

	"beforeend",
	"afterend"
};

Except that instead of throwing a TypeError or a RangeError #489, a "SyntaxErrorDOMException is thrown instead.

See also:

@annevk
Copy link
Member

annevk commented Mar 21, 2021

I think there should be more precedent before we standardize upon a pattern in IDL. Unless there's a reason handling it prose is difficult, but that does not appear to be the case here?

@ExE-Boss ExE-Boss changed the title Consider adding [LegacyASCIICaseInsentiveEnum] for element.insertAdjacent* APIs Consider adding [LegacyASCIICaseInsentiveEnum] for element.insertAdjacent* APIs Mar 24, 2021
@domenic domenic closed this as completed Sep 14, 2022
@ExE-Boss ExE-Boss changed the title Consider adding [LegacyASCIICaseInsentiveEnum] for element.insertAdjacent* APIs Consider adding [Legacy​ASCII​Case​Insentive​Enum] for element​.insertAdjacent* APIs Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants