| 00:46 | <TimothyGu> | Domenic: I've been working with japhet to try to clarify some Blink-internal terminologies around active/fully active documents. In Blink, there seems to be a distinction between documents that have never become active versus documents that used to be active but no longer. Do you happen to know if HTML has a similar distinction? |
| 00:51 | <Domenic> | TimothyGu: Very interesting. I'm not aware of anything. Closest I can think of is similar things around user activation, and special checks for initial about:blank. |
| 00:57 | <MikeSmith> | very nice to have https://wiki.mozilla.org/Standards |
| 00:58 | <MikeSmith> | not just for Mozilla-internal reasons but also for non-Mozilla folk to know who is handling what |
| 03:00 | <MikeSmith> | https://stackoverflow.com/questions/62034488/what-part-of-htmlimageelement-prototype-needs-to-be-overridden-to-control-how-i |
| 06:19 | <annevk> | How do people stand on outright deleting spammy issues? |
| 06:19 | <annevk> | I plan to continue reporting them, but I wonder if deleting them might reduce the amount of spam for people using GitHub's notifications view to track things |
| 06:20 | <annevk> | (rather than email, where you'll be out-of-luck) |
| 06:20 | <alystair> | what would be classified as a spammy issue |
| 06:30 | <jgraham> | a |
| 06:48 | <alystair> | thanks for the guidance annevk I'll review the faq and w3c guidelines tomorrow. As a web dev it was a bit hard wrapping my head around all the governing bodies... started at TC39 and now my adventure continues |
| 06:52 | <annevk> | alystair: https://github.com/whatwg/html/issues/5557 is an example |
| 06:52 | <annevk> | alystair: there are quite a few indeed, happy to help navigate |
| 06:57 | <alystair> | thanks - was also nervous the issue I posted was one of them, gnight |
| 06:59 | <annevk> | alystair: not at all |
| 07:16 | <MikeSmith> | in W3C repos, I just delete the ones that are clearly spam/junk |
| 08:02 | <annevk> | omg https://github.com/w3c/csswg-drafts/issues/5115 |
| 08:02 | <annevk> | it's happening, maybe? |
| 09:13 | <noamr> | I could use some help with html-build on mac... it keeps trying to go to the wattsi build server thingy and receiving an HTTP2 error |
| 09:14 | <noamr> | anyone here familiar with this? thanks :) |
| 09:20 | <annevk> | noamr: I think that's due to macOS curl being out-of-date or some such |
| 09:21 | annevk | files https://github.com/whatwg/html-build/issues/230 |
| 09:23 | <MikeSmith> | annevk: is that just a problem for curl on macOS? |
| 09:25 | <MikeSmith> | and if so is there some other command-line client which is known to have working HTTP/2 support and that we could use in the documentation instead? |
| 09:25 | <MikeSmith> | I guess wget doesn’t do HTTP/2 |
| 09:26 | <MikeSmith> | but maybe a command-line python one-liner? |
| 09:26 | <MikeSmith> | or node even |
| 09:26 | <jgraham> | I don't think that Python has a http2 client in the stdlib |
| 09:26 | <MikeSmith> | ah OK |
| 09:26 | <annevk> | MikeSmith: Python's requests module would work |
| 09:27 | <annevk> | MikeSmith: and now we require Python 3 you have to install some stuff anyway |
| 09:27 | <annevk> | MikeSmith: so that seems reasonable to me, we use it elsewhere on WHATWG |
| 09:27 | <MikeSmith> | yeah well requests itself isn’t part of the standard distro, even in Python 3, is it? |
| 09:27 | <annevk> | MikeSmith: correct |
| 09:27 | <MikeSmith> | OK |
| 09:28 | <MikeSmith> | well I guess it’s not an either-or; we could say, “if curl doesn’t work, try this, and this” |
| 09:28 | <MikeSmith> | but really for macOS I think the simplest thing would be to tell users, “brew install curl”, right? |
| 09:29 | <MikeSmith> | or even full “/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"; |
| 09:29 | <MikeSmith> | oofs |
| 09:29 | <MikeSmith> | or even full “/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"; && brew install curl” |
| 11:18 | <MikeSmith> | https://stackoverflow.com/questions/62041644/csp-sandbox-from-a-serviceworker |
| 11:28 | <MikeSmith> | https://gregoryszorc.com/blog/2020/01/13/mercurial%27s-journey-to-and-reflections-on-python-3/ is a great read |
| 11:28 | <MikeSmith> | > The effort required to port to Python 3 was staggering. ... As a project maintainer, it's natural to ask what we could have accomplished if we weren't forced to carry out this sideshow. |
| 16:34 | <Domenic> | Anyone with a Mac and Python 3 able to tell me whether `pip3` is in your path? |
| 16:43 | <Mek> | it is for me |
| 16:48 | <annevk> | Domenic: here too |
| 16:48 | <Domenic> | Good to hear :) |
| 16:48 | <annevk> | I hope that they never do Python 4 |
| 23:28 | <MikeSmith> | https://stackoverflow.com/questions/62050273/how-to-know-when-a-fetch-ends-without-locking-the-body-stream seems like a pretty good question |
| 23:50 | <Domenic> | I agree with the comment saying "An alternative would be to just pass a callback function to..." In general it should be the responsibility of the thing consuming the stream to let the caller know when they're done consuming the stream. |