Philip Jägenstedt

Some stats on /var/www on the whatwg.org server (named "marquee") to inform how what we could/should do for version control: - A total of ~116k files totaling ~40GB uncompressed and...

In https://github.blog/2021-04-22-github-actions-update-helping-maintainers-combat-bad-actors/ it sounds like approval is only required for first-time contributors, once. Isn't that the case?

If there isn't already an API for this approval, there probably will be soon. Given that, whatbot could approve any PR it does a contribution check for which comes out...

It seems best to only create reports when it the error was because of a policy violation. Doing that in https://html.spec.whatwg.org/multipage/iframe-embed-object.html#allowed-to-use makes sense to me too.

@clelland how will you implement this? Will the checking and the reporting be entirely separate, will there be a flag to the check that says whether to report, or something...

Sounds like a reasonable structure, yeah. @clelland, in this case, would the reporting be implicit or explicit? Seems to me given the structure that making it implicit in the check...

Per "element is a shadow host and the result of retargeting its node document’s fullscreen element against element is element" in https://fullscreen.spec.whatwg.org/#:fullscreen-pseudo-class both the video element and the my-web-component element...

OK, that's not too surprising. It's probably not too difficult to match the spec here, but it might require an extra flag on all elements. Haven't tried to implement it...

@beaufortfrancois that would follow https://github.com/WICG/picture-in-picture/pull/126, right? There's also retargeting in https://fullscreen.spec.whatwg.org/#dom-document-fullscreenelement, what should happen to that?

Fullscreen inside of `` used to work in Chromium. But here it's `frame.requestFullscreen()` so not exactly the situation. Disallowing this would be straightforward and fine I think, unlikely to be...