| 07:42 | <annevk> | TabAtkins: if you have any idea what might be the cause of https://github.com/w3c/spec-generator/issues/765 I'd appreciate it. I guess ideally we just have one build path, but then we'd need to feed PR Preview the results of our build output somehow. Which maybe we could do, but it'd be work I'd rather avoid. |
| 09:30 | <keithamus> | https://github.com/whatwg/html/pull/12373 runs specfmt source and commits it, as trying to run specfmt causes noisy diffs making it less disirable to use. Feel free to close if we don't think this is important. |
| 09:42 | <annevk> | That's a lot smaller than what I would have expected. Did you spot check it for accuracy? |
| 09:43 | <keithamus> | I did. Couldn't see anything untoward. |
| 09:44 | <annevk> | It seems determined to keep <dt>s on a single line. |
| 09:44 | <annevk> | Not sure that's actually our style. |
| 09:45 | <annevk> | The other changes look good though. Dominic Farolino ^^ |
| 11:30 | <Noam Rosenthal> | Details aside, I think this is a good idea. git is capable of following beyond a single change so clobbering history with this is not a huge problem |
| 12:33 | <annevk> | Yeah, it seems fine but I'd like some more eyes on the <dt> changes. Definitely if you follow back blame you'll find many Hixie commits that changed wrapping across the entire specification. They're slightly annoying, but also easily skipped. |
| 16:12 | <zcorpan> | Need --full-spec to get it to process all lines. |
| 16:33 | <annevk> | keithamus: not sure when you stop working but if you or a colleague could fixup and land https://github.com/web-platform-tests/wpt/pull/58713 in the next 24h that'd be great; I'll pre-approve |
| 16:34 | <keithamus> | done. |
| 16:35 | <keithamus> | thanks for landing https://github.com/whatwg/html/pull/12267! |
| 17:07 | <TabAtkins> | annevk: looking into it |