| 07:33 | <domfarolino> | annevk: If you could take a look at https://github.com/whatwg/html/pull/6249 that would be great! |
| 07:35 | <annevk> | domfarolino: will do |
| 07:37 | <annevk> | domfarolino: I just realized that the first paragraph that's added is between two paragraphs about the document's URL |
| 07:37 | <annevk> | domfarolino: so you either want to put it after the warning or a paragraph earlier |
| 07:38 | <domfarolino> | annevk: hah, whoops. I'll take a look now |
| 07:39 | <domfarolino> | annevk: Done |
| 07:41 | <annevk> | domfarolino: thanks, I guess we can prefix this with Editorial, right? |
| 07:41 | <annevk> | I'll merge it once the build bot gets back to us |
| 07:42 | <domfarolino> | annevk: yeah I think that's right |
| 07:42 | <domfarolino> | done |
| 07:44 | <annevk> | Oh, no need to change the title in the future |
| 07:45 | <annevk> | I thought you meant the bot was done, but it seems even GitHub Actions isn't that fast |
| 07:47 | <annevk> | Well' it's all done now, it was pretty fast |
| 07:47 | <domfarolino> | Ah, haha. Indeed, thanks! |
| 07:47 | <domfarolino> | I'm glad that's properly defined now |
| 07:52 | <annevk> | Yeah, it's great improvement that adds a lot of clarity |
| 07:53 | <annevk> | It's so surprising that old API specs hand-waved all private state and you had to infer it somehow |
| 08:03 | <domfarolino> | Ugh, I know :/ |
| 08:46 | <annevk> | lol Domenic that PR from you against Secure Contexts was the majority of the open issues |
| 15:38 | <Domenic> | Nice |
| 15:39 | <Domenic> | Hmm https://github.com/whatwg/html/pull/6282 ended up much shorter than I expected given all the surrounding discussion |
| 15:42 | <andreubotella> | Domenic: that PR deals with escapes and it's intended to replace https://github.com/whatwg/html/pull/3276 |
| 15:43 | <andreubotella> | I'm still waiting for feedback from some of the folks at whatwg/forms before I open the one dealing with newline normalization |
| 15:43 | <Domenic> | Ah I see |
| 15:43 | <andreubotella> | https://github.com/whatwg/html/issues/6247 |
| 15:44 | <annevk> | I think in the end we should define the full format, but I'm all for small incremental steps as that makes reviewing a lot easier |
| 15:45 | <andreubotella> | indeed |
| 15:46 | <andreubotella> | in the WPT tests I've written and modified, all browsers act the same other than the few bugs related to escapes or newlines |
| 15:46 | <andreubotella> | but I'll take a look at hixie's test suite after I'm done with this |
| 15:47 | <andreubotella> | the test suite at https://github.com/masinter/multipart-form-data/tree/master/test-cases, rather |
| 16:39 | <annevk> | Domenic: what do you think about creating historical tests for <object><param name=src+friends> and filing a bug against Chrome and Safari each? The spec never supported it and it seems like it should matter even less today |
| 17:57 | <Domenic> | annevk: in the absence of anyone on the Chrome side stepping up to take ownership of this stuff (I sent out a message yesterday but no responses), that seems reasonable. Maybe eventually when the bug gets triaged there will be some pushback and desire to add it to the spec, I dunno. |
| 18:05 | <annevk> | Domenic: yeah, I mean, that's also fine, it's not like something we couldn't add to Fx, I just rather not |
| 18:06 | <Domenic> | Yeah, I'd definitely prefer it in the abstract if we could just make <param> totally do nothing, I just am not personally willing to sign up for the work of adding use counters/doing outreach to any pages we find/potentially dealing with angry enterprise customers when the change makes it to stable. I hope someone is though :) |
| 18:12 | <annevk> | Domenic: did you see https://github.com/whatwg/html/pull/6281 btw? |
| 18:13 | <Domenic> | annevk: yep, it generally looks good, I wanted to do a pass to make sure there wasn't more to delete. I'll do that now. |
| 18:13 | <annevk> | no rush, I'll be out until tomorrow most likely |
| 18:13 | <annevk> | was just wondering since you checked the more recent PR |