| 10:37 | <MikeSmith> | anybody have problems reaching https://www.w3.org/ or https://validator.w3.org/nu/ |
| 10:37 | <MikeSmith> | specifically, with Chrome do you get ERR_HTTP2_PROTOCOL_ERROR |
| 10:44 | <Ms2ger> | wfm |
| 10:48 | <MikeSmith> | Ms2ger: thanks |
| 10:54 | <annevk> | Writing side-effect-free dictionary member detection scripts is a lot of fun |
| 10:55 | <annevk> | That's not to say we shouldn't have something better, but until we find that I thing I'll enjoy writing these |
| 14:55 | <annevk> | zcorpan: so apparently <object> does resizing for SVG and also executes script |
| 14:55 | <annevk> | zcorpan: it's not clear this is good and there are bugs, but... |
| 14:56 | <zcorpan> | annevk: what's the context here? |
| 14:58 | <annevk> | zcorpan: https://twitter.com/annevk/status/1187722568322682881 |
| 14:58 | <annevk> | (and some spelunking into embed/object to decide whether they navigate or not) |
| 15:01 | <zcorpan> | annevk: ah right. Yes, the resizing to the SVG's intrinsic size is why I said it's different from iframe auto-size for HTML |
| 18:42 | <jyasskin> | annevk: What's the best way to get advice on a problem I think implies a new URL scheme? An issue on the URL spec? Direct emails to you? Something else? |
| 20:31 | <annevk> | jyasskin: uri⊙wo might offer some advice; I have your email in my todos |
| 20:33 | <jyasskin> | annevk: Thanks! The actual review isn't super-urgent; I just wanted to make sure I didn't leave anyone out. |
| 20:38 | <annevk> | jyasskin: Fetch and HTML issues might be appropriate if it impacts fetching or navigation |
| 20:40 | <jyasskin> | The problem is around how we handle storage in unsigned packages, where I think we need the origin to be based on both the package URL and the claimed subresource origin within the package. Package handling and storage will definitely involve Fetch and HTML changes, so you'll get issues there too. |