Luke Warlow

Sorry for the delays on this, I wanted to wait till close watcher spec was a bit more settled. Now that the basic machinery is pretty stable I'm going to...

Yeah so a second change will be needed if https://github.com/tc39/ecma262/pull/3294 gets accepted. Though if it's not CSP would have to reconstruct the string itself (if it even has all the...

Idk if it's neccessary given it will be addressed soon (all going well) but this currently has an extra parameter than the actual proposal doc and PR associated with it,...

> If those participating in TC39 think acceptance of https://github.com/tc39/ecma262/pull/3294 is a given I guess I'm willing to trust that, but it seems weird that it's still a draft. I'm...

@domenic and @annevk I've updated the tc39 PR and have https://github.com/tc39/proposal-dynamic-code-brand-checks/pull/17 which just needs merging for the proposal document. Then we have alignment between JS PR, HTML PR, and CSP...

> can fall back to a regular `` if not supported. I guess it depends on the specifics but I feel (just a hunch so could be very wrong) like...

To do anything with the cycle button you'd still need JavaScript (or invokers) so a button as a fallback wouldn't really impact that? I don't think you'd want this to...

> A button might work for a toggle with two states, but not for a cycle with more than two states. I'd be curious what your reasoning is for this?...

One thing to say, which I know might be contentious, while graceful degradation is important there are limits to what is possible and I think we should be careful not...

I'd have to double check but I think I'd need a maximum of 4 states for anything I'd consider a toggle/cycle button. For example take a microphone button you'd have...