Luke Warlow

I'm going to go ahead and close this based on recent discussions in another issue. TLDR you can feature detect if a browser is aware of a certain named command...

Is there more work needed here or can this be closed?

This is a clone of #1247 where I will finish any outstanding work to get this across the line

See also https://github.com/whatwg/dom/pull/1258 which is another integration point with the DOM spec that we need for TT.

I think I've addressed all the comments from #1247. I do want to point out Chrome and WebKit don't (or at least not in a way obvious to me) 100%...

> This change is either incomplete or makes many cosmetic changes that would be best proposed separately as they confuse me quite a bit. Apologies I thought I'd reverted all...

@otherdaniel, @annevk , and @smaug---- regarding the case where the default policy changes assumptions about the existence of an attribute mid-way through what would you prefer the spec say to...

Sorry I mean algorithmically the spec and implementations don't follow the same flow. So it's trickier to reason between the spec and implementation. This might just be my lack of...

> The path of least resistance is prolly matching Chromium. Introducing new paths that throw is always risky. If you are looking for guidance as to how, I'd need quite...

@otherdaniel if you've got time could you read through this to ensure it makes sense to you?