@domenic besides the brevity of the current name I don't see how the current proposal helps. > I kind of prefer the brevity and clarity of the existing method, and how it matches existing platform conventions (e.g. supports() on DOMTokenList or supports() on CSS). As @plinss pointed out, this is precisely the confusing part with the current proposal because `HTMLScriptElement.supports()` is not intended to provide the generic capability `CSS.supports()` does. The fact that people recognize the API name will only add to the confusion as they realize that the only thing they can check for is `type`. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/674#issuecomment-920228073
Received on Wednesday, 15 September 2021 17:38:53 UTC