| 27 Mar 2024 |
 ErichDonGubler | * jgraham: Okay, so, the actual set of values seems to be:
implementing: Anywhere from "is being implemented" to "we believe we have fully implemented this" for an agent; the intent is "yes please let's test this".not-implementing: Agent is not planning on implementing this, please don't test it.backlog: Seems like this isn't actually Firefox-specific, contrary to my understanding above. Basically, it means, "we intend to implement this, but plz don't test it like implementing yet".
☝🏻 Sound fair?
| 16:36:30 |
 jgraham | Yeah, that seem right. | 16:38:50 |
| ErichDonGubler | I can file a PR for updating docs, if you want. 🙂 | 19:08:32 |
| 29 Mar 2024 |
|  Romulo Cintra changed their display name from Romulo Cintra to Romulo Cintra - OoO 2nd April. | 13:41:16 |
| 1 Apr 2024 |
|  Mukilan changed their display name from Mukilan to Mukilan (back 4th). | 06:05:08 |
|  Florian Rivoal changed their display name from Florian Rivoal to florian. | 13:04:01 |
|  mgaudet changed their display name from mgaudet|off-until-April-1 to mgaudet. | 15:12:52 |
| Florian Rivoal changed their display name from florian to Florian Rivoal. | 16:06:39 |
| 2 Apr 2024 |
|  Alan Stearns set a profile picture. | 01:10:33 |
| Romulo Cintra changed their display name from Romulo Cintra - OoO 2nd April to Romulo Cintra. | 07:41:31 |
 Ms2ger | Was looking for my old irc logs about testing, and the first thing I find is: | 12:30:42 |
| Ms2ger | Feb 14 2013 12:58:31 <jgraham> tobie: I object to ordering that makes Process sound more important than actually achieving meaningful interop | 12:30:43 |
 zcorpan | jgraham++ | 13:17:40 |
 Luca Casonato | Hey folks - I have a colleague which is failing to run ./wpt serve in Python 3.12. Downgrading to 3.11 works just fine. It seems that something ssl related in 3.12, which is causing the wss server to fail to start | 13:38:59 |
| Luca Casonato | After instrumenting serve.py a bit, we managed to figure out the error they are hitting is: module 'ssl' has no attribute 'wrap_socket' | 13:39:51 |
| Ms2ger | https://github.com/web-platform-tests/wpt/issues/44427 | 13:49:20 |
| Luca Casonato | Thanks Ms2ger! | 15:07:40 |
| 3 Apr 2024 |
 sideshowbarker | I want to test that a toggle event does not fire at a closed details element when find-in-page locates a match in its summary (rather than in the text content of the second slot of the details element, in which case the toggle event should fire — and I already have tests written for that).
So, what’s the right way to test that an event does not fire? (Other than just letting the test time out)
| 06:21:37 |
| sideshowbarker | I guess I’ll just use step_timeout | 06:39:42 |
| Ms2ger | jgraham: ping https://github.com/web-platform-tests/wpt/pull/45002 | 10:41:43 |
|  Alaska joined the room. | 16:57:54 |
|  jib changed their display name from jib to jib - PTO. | 20:08:12 |
| 4 Apr 2024 |
|  Eric Portis (he/him) joined the room. | 00:21:19 |
| Eric Portis (he/him) | Let's say I started writing some tests to my master instead of a branch. Should I... undo that somehow, or is it ok to create a PR from my master? | 00:22:09 |
 Luke Warlow | Assuming you've committed If you do a soft git reset to the head commit, switch branch, and recommit you should be good to go. Makes it easier to keep your main branch clean to resync it in future. | 00:25:23 |
| Alan Stearns | You may already have these incantations committed to memory, but I find https://ohshitgit.com/ to be very helpful way too often | 00:39:31 |
 annevk | .https is not documented? http://web-platform-tests.org/writing-tests/server-features.html | 08:19:25 |
| jgraham | http://web-platform-tests.org/writing-tests/general-guidelines.html#https | 08:20:33 |
| zcorpan | git branch -m mybranchname | 08:25:48 |
| zcorpan | is what I usually do | 08:26:05 |
