| 08:02 | <annevk> | So we have GitHub Actions for WHATWG, but they're also still in beta... |
| 09:07 | <smaug____> | Ms2ger: thanks for pinging about that dump() call |
| 09:07 | <smaug____> | I suck |
| 09:08 | <Ms2ger> | I blame the lint for not catching it |
| 09:09 | <smaug____> | wpt lint is a bit silly |
| 09:09 | <smaug____> | complaining about some web API usage |
| 09:09 | <smaug____> | like setTimeout |
| 09:10 | <annevk> | smaug____: there's a reason for t.step_timeout though |
| 09:11 | <annevk> | smaug____: two even, I think; making sure exceptions from the timeout call are attributed to the test and allowing for longer timeouts on slow architectures |
| 09:11 | <smaug____> | lint doesn't suggest using t.step_timeout, but the global setTimeout |
| 09:11 | <smaug____> | I always prefer using the stuff we ship for testing |
| 09:11 | <smaug____> | not some wrappers on the stuff |
| 09:12 | <smaug____> | (mochitest also complains about anything else but setTimeout(,0) ) |
| 10:09 | <hsivonen> | Has anyone tested <textarea wrap=hard> for interop? The spec says "using a UA-defined algorithm". |
| 11:56 | <annevk> | hsivonen: I suspect the last time some testing got done is when Hixie added it |
| 14:00 | <annevk> | hsivonen: did you see https://en.m.wikipedia.org/wiki/HTML5? |
| 14:00 | <annevk> | hsivonen: I just noticed that the W3C reintroduced the space while they were forking |