| 08:24 | <justbreath1120> | YO |
| 08:25 | <justbreath1120> | Whats up guys im super dooper new to coding |
| 08:46 | <justbreath1120> | I have a very important and meaningful request |
| 08:47 | <justbreath1120> | please if anyone has time to help me with my assignments please message me . This is my last chance to bring up my GPA and i also web development i just need a little help |
| 11:49 | <canova> | Hey annevk ! While I was looking into the EventTiming API, I came across an issue. There is a spec change proposal there, do you mind taking a look to see if you agree with the proposal? Wanted to get a green light from all of the interop parties before making a change |
| 12:30 | <annevk> | canova: per https://github.com/WebKit/standards-positions/issues/420 it seems we're not satisfied with this API to begin with so unsure how we'd judge minor changes |
| 12:44 | <canova> | annevk: I agree that I was confused about the "first-input" at first too. Some parts of the issue mentioned seem to be resolved, and later yoavweiss's answer seems to cover some other issues. It would be great to get a response there maybe. There is also a larger issue filed for evolving this into first interaction. But I think this is still an improvement compared to the current situation. Previously we were getting |
| 14:18 | <sefeng> | er...isn't it part of the interop2025? |
| 20:50 | <smaug> | Hmm, trying to recall the history of CommandEvent in Gecko, which is separate to XULCommandEvent. And the HTML spec CommandEvent is like a mix of those two. |
| 20:54 | <smaug> | Luckily the existing CommandEvent in Gecko can be just tweaked a bit to be like the HTML concept CommandEvent. |
| 20:55 | <smaug> | In Gecko the existing event is used only in the parent process to handle events like back/forward etc coming from special keys or extra buttons of mouse. |