10:55 | <smaug> | rego: smaug: would appreciate your input on https://github.com/whatwg/html/issues/8545 |
10:55 | <smaug> | I think that needs to be fixed |
14:27 | <annevk> | smaug: I haven't really been able to think of something that would actually address it, but I'm also no longer as persuaded it's a real problem |
14:28 | <smaug> | it is just not super fun to report leak issues to web sites 😉 |
16:17 | <hsivonen> | annevk: Is the reason why Declarative Shadow DOM needs to be opt-in for DOMParser stated somewhere in one place? (I vaguely recall "XSS" but not the specifics.) |
18:24 | <TabAtkins> | Does anyone else have issues with |
19:25 | <TabAtkins> | I keep getting these things on initial load (restarted my computer this morning), I have to assume it's something about whatwg's CDN? |
20:40 | <TabAtkins> | nolanlawson: right, but that means we shouldn't offer them tools that break that encapsulation because they'll realize (maybe later) that destroys the benefits |
22:47 | <Domenic> | I keep getting these things on initial load (restarted my computer this morning), I have to assume it's something about whatwg's CDN? |