| 00:01 | <TabAtkins> | Domenic: Any progress on document.ready promise? |
| 00:37 | <Domenic> | TabAtkins: open an issue on html so we don't forget? Should be easy now that we can edit the spec, just need to line up a few implementers. |
| 01:38 | <MikeSmith> | gsnedders: yeah there seems to be a bug in html5lib that's causing it to ignore namespaceHTMLElements=False |
| 01:41 | <MikeSmith> | gsnedders: tossing a sys.stderr.write("namespaceHTMLElements is %s \n" % str(namespaceHTMLElements)) into the HTMLParser constructor I see: |
| 01:41 | <MikeSmith> | namespaceHTMLElements is True |
| 01:41 | <MikeSmith> | namespaceHTMLElements is False |
| 01:45 | <MikeSmith> | and if I change the signature of the constructor to have namespaceHTMLElements=False instead of True, then it does work as expected (that is, html element goes into void namespace, and I finally get un-namespaced output when I serialize) |
| 02:05 | <gsnedders> | MikeSmith: huh? |
| 02:05 | <gsnedders> | MikeSmith: minimal TC with just html5lib and no lxml, plz? |
| 03:00 | <MikeSmith> | gsnedders: Hai |
| 03:07 | <annevk> | Domenic: I updated the ruby parser commit and updated the commit message too |
| 03:19 | <annevk> | Heh, whatwg/html is already more popular than whatwg/fetch |
| 03:19 | <annevk> | whatwg/streams is still miles ahead though |
| 03:52 | <gsnedders> | hmm, there's no way to use idlharness.js to check document.all, because of the typeof checks |
| 04:41 | <MikeSmith> | gsnedders: you sure? |
| 04:41 | <MikeSmith> | ah document.all |
| 04:45 | annevk | wonders how familiar jgraham is with Fetch and how well he remembers his navigate adventures |
| 04:49 | <annevk> | MikeSmith: I'm a bit hesitant to update my local https://github.com/whatwg/html-build copy as it's unclear from the README.md how to preserve my local whatwg/html copy |
| 04:49 | <annevk> | MikeSmith: shall I file an issue? |
| 04:51 | <MikeSmith> | yeah |
| 04:51 | <MikeSmith> | it's not going to overwrite your existing repo though |
| 04:52 | <MikeSmith> | the only time it tries to clone the repo is if it doesn't find any existing one |
| 04:52 | <annevk> | MikeSmith: does it look for ../html? |
| 04:52 | <MikeSmith> | yeah |
| 04:52 | <MikeSmith> | only that |
| 04:52 | <annevk> | okay, so I guess I'm good then |
| 04:52 | <MikeSmith> | yes I think so |
| 04:53 | <annevk> | ah, I do need to clean up old files somehow |
| 04:54 | <MikeSmith> | also fwiw if it makes a clone it only ever clones it into a subdirectory of the directory the build.sh script is in; that is, into your html-build dir |
| 04:55 | <annevk> | Hmm, I wonder why git reset --hard doesn't remove all the local files that are now supposed to be elsewhere |
| 04:56 | <annevk> | Isn't that the way to get rid of all kinds of uncommitted resources and such? |
| 04:57 | <annevk> | Ah, git clean -fd |
| 04:57 | <annevk> | "OK, looked in the /Users/annevk/GH/html directory and found HTML source there..." |
| 04:58 | <annevk> | Going well so far |
| 04:58 | <annevk> | MikeSmith: <3 those messages |
| 04:59 | <MikeSmith> | heh |
| 04:59 | <MikeSmith> | a little human touch there |
| 04:59 | <annevk> | It still works :-) |
| 04:59 | <MikeSmith> | annevk: git clean -fdx is what I usually do, fwiw |
| 04:59 | <MikeSmith> | heh |
| 05:00 | <MikeSmith> | good ✌️ |
| 05:00 | <annevk> | Hopefully I no longer I have the problem of html-build/source and html/source getting confused |
| 05:00 | <annevk> | MikeSmith: did you see 🖖? |
| 05:00 | <MikeSmith> | you will not have that problem |
| 05:00 | <MikeSmith> | oh man |
| 05:00 | <MikeSmith> | wow |
| 05:00 | <MikeSmith> | no, dinnet now |
| 05:01 | <MikeSmith> | hober gotta love tha one |
| 05:01 | <annevk> | Got it from hober |
| 05:01 | <MikeSmith> | hahah |
| 05:01 | <annevk> | (obv) |
| 05:01 | <MikeSmith> | yeah |
| 05:01 | <MikeSmith> | I miss hober |
| 05:01 | <MikeSmith> | haven't talked with him for quite a while |
| 05:01 | <terinjokes> | MikeSmith: i started to get into the habit of `git clean -fdx` after publishing packages to npm for 6 months with my .idea folder included |
| 05:02 | <MikeSmith> | terinjokes: yeah if you're going to clean, you should, you know, clean |
| 05:18 | <annevk> | MikeSmith: the commit contains "TODO Move the following comment to the README.md file after we review." |
| 05:35 | <MikeSmith> | ah yeah |
| 05:35 | <MikeSmith> | will do that |
| 05:35 | <MikeSmith> | thanks for catching that |
| 05:46 | <MikeSmith> | annevk: fwiw I would prefer that we follow a policy that nobody ever push their own PRs to master unreviewed, ever |
| 05:46 | <MikeSmith> | no matter how small |
| 05:46 | <MikeSmith> | both for the build script and the source |
| 05:47 | <annevk> | MikeSmith: you mean no changes ever? |
| 05:47 | <annevk> | MikeSmith: maybe that is the best for this specification |
| 05:47 | <MikeSmith> | I think that is ideal |
| 05:47 | <MikeSmith> | yeah for the spec at least for sure |
| 05:48 | <MikeSmith> | everybody make mistakes sometimes |
| 05:48 | <MikeSmith> | always better to have a 2nd pair of eyes |
| 05:48 | <MikeSmith> | sanity check, etc |
| 05:48 | <MikeSmith> | anyway, https://github.com/whatwg/html-build/pull/22 |
| 05:49 | <annevk> | Yeah makes sense, given that most writing PRs haven't written the text doesn't help either |
| 05:49 | <annevk> | MikeSmith: so yeah, I saw that, r+, but I guess I should merge it? |
| 06:01 | <MikeSmith> | yes please |
| 06:38 | <SteveF_> | annevk: domenic: as pre hixies feedback on ARIA section update, have removed the whole section and updated PR |
| 06:39 | <MikeSmith> | hey SteveF_ |
| 06:39 | <SteveF_> | hi |
| 06:39 | <MikeSmith> | I reckon Domenic and Hixie are away but annevk is here |
| 06:40 | <SteveF_> | OK |
| 06:44 | <annevk> | SteveF_: I guess it might still be good to <ref> the various ARIA specifications |
| 06:44 | <annevk> | SteveF_: or perhaps group them all under the [ARIA] banner? |
| 06:46 | <SteveF_> | annevk: I think it is worthwhile pointing implementers to the other specs, but seems like hixie didn't |
| 06:47 | <SteveF_> | annevk: " under the [ARIA] banner" where? also not all are ARIA specs notably HTML acc API spec |
| 06:49 | <annevk> | SteveF_: well, "This is redundant with the referenced specs." would no longer be true if we didn't reference anything, would it? |
| 06:49 | <SteveF_> | annevk: I could add the section back with the references |
| 06:49 | <SteveF_> | refernces only that is |
| 06:49 | <annevk> | SteveF_: I meant that the text keeps it <ref spec=ARIA> and that the references section includes the various specifications under that banner, similar to what is done for HTTP |
| 06:53 | <annevk> | SteveF_: and apologies for making this take so long, I was obviously not experienced enough to review that |
| 06:54 | <annevk> | SteveF_: still a bit early days trying to maintain HTML |
| 06:55 | <SteveF_> | annevk: no problem |
| 07:01 | <SteveF_> | annevk: have pushed update to ARIA section PR that just has very brief references to the 2 relevant specs |
| 07:02 | <SteveF_> | annevk: will wait to see how that goes down |
| 07:04 | <annevk> | SteveF_: did you intentionally leave the list of roles and list of aria-* attributes in source? |
| 07:05 | <SteveF_> | annevk: form the other section? I haven't looked at that bit yet thats as it was |
| 07:05 | <SteveF_> | annevk: not added or edited by me |
| 07:06 | <MikeSmith> | yeah I think we need to keep those |
| 07:06 | <MikeSmith> | I don't think there is a conflict in keeping them |
| 07:06 | <MikeSmith> | that section is not defining any requirements around them |
| 07:07 | <MikeSmith> | it's basically just stating that they exist and are a part of the language |
| 07:07 | <annevk> | It also has "The terms strong native semantics is used as defined in the ARIA specification. The term default implicit ARIA semantics has the same meaning as the term implicit WAI-ARIA semantics as used in the ARIA specification." which wouldn't really be relevant anymore |
| 07:07 | <MikeSmith> | hmm yeah |
| 07:07 | <SteveF_> | what i said previoulsy is I would do a PR at some point to update the links there as they currently point to ARIA 1.0 |
| 07:08 | <SteveF_> | annevk: so should i remove "The terms strong native semantics is used as defined in the ARIA specification. The term default implicit ARIA semantics has the same meaning as the term implicit WAI-ARIA semantics as used in the ARIA specification."? |
| 07:09 | <annevk> | I'm not a 100% sure, but it seems like it |
| 07:10 | <SteveF_> | OK |
| 07:11 | <annevk> | I would prefer it if we reworked all of ARIA in a single commit in the end |
| 07:11 | <MikeSmith> | yes please |
| 07:11 | <MikeSmith> | squash |
| 07:11 | <annevk> | I can take care of squashing your work, but if you have any other changes planned please make them here I think |
| 07:11 | <annevk> | And then hopefully we can get Hixie to review when he wakes up and make this happen |
| 07:14 | <MikeSmith> | Edge team just changed srcdoc to "under review" |
| 07:14 | <MikeSmith> | https://dev.modern.ie/platform/status/iframesrcdocattribute/ |
| 07:14 | <MikeSmith> | it was previously "no status" |
| 07:15 | <annevk> | srcdoc is one of the things that makes navigate complicated |
| 07:16 | <annevk> | I didn't realize this until today or so, but "navigate"'s input is "a new resource" |
| 07:16 | <annevk> | And that means much more than a URL |
| 07:23 | <SteveF_> | annevk: pushed update with that text removed and links to aria attributes updated to point to latest spec |
| 07:23 | <SteveF_> | annevk: so that should be it |
| 07:26 | <MikeSmith> | annevk: yeah that "navigate" stuff needs some attention |
| 07:27 | <annevk> | SteveF_: ta |
| 07:27 | <annevk> | SteveF_: almost 1% of line savings |
| 07:28 | <SteveF_> | annevk: is that good? |
| 07:29 | <annevk> | SteveF_: I think so, although it's somewhat sad to have a core part of HTML defined elsewhere |
| 07:33 | <SteveF_> | annevk: at least its defined somewhere :-) |
| 07:50 | <zcorpan> | Ms2ger: r? https://critic.hoppipolla.co.uk/r/5785 |
| 08:06 | <nox> | Ms2ger: Of what? |
| 08:06 | <Ms2ger> | https://critic.hoppipolla.co.uk/r/5785 |
| 08:14 | <annevk> | It seems to me that navigating back to an about:srcdoc document is not as well-defined as it should be |
| 08:15 | <annevk> | Or maybe I missed something and those cannot end up in session history anyway? |
| 08:15 | <annevk> | I didn't actually check that... |
| 08:16 | <nox> | Ms2ger: Oh, the tests fail because they are wrong? |
| 08:16 | <Ms2ger> | I dunno |
| 08:17 | <Ms2ger> | That's why I'm delegating :) |
| 08:18 | <nox> | The spec does reject most things in a frameset. |
| 08:18 | <annevk> | nox: see https://www.w3.org/Bugs/Public/show_bug.cgi?id=29041 for context |
| 08:26 | <nox> | Ms2ger: LGTM |
| 08:54 | <jgraham> | annevk: I remember a little about navigation, but know very little about fetch |
| 08:57 | <annevk> | jgraham: I guess have to start from scratch then |
| 08:57 | <jgraham> | annevk: Wat are you trying to do? |
| 08:58 | <annevk> | jgraham: integrate the two |
| 08:58 | <Ms2ger> | Sounds like we should ship you plenty of hard liquor, then |
| 08:59 | <jgraham> | iirc the parts of navigation that actually fetch documents are super-handwavy at the moment |
| 08:59 | <jgraham> | "do some magic until you have some bytes" |
| 09:07 | <annevk> | Ms2ger: that might just make it worse :-) |
| 09:08 | <annevk> | Ms2ger: good tea is welcome though |
| 09:17 | <jgraham> | Speaking of tea… |
| 10:14 | <nox> | zcorpan: No problem. |
| 10:56 | Ms2ger | noticed http://blogs.opera.com/news/2015/09/opera-interns-share-their-stories/ had no Core interns |
| 11:13 | <MikeSmith> | annevk: http://stackoverflow.com/questions/32500073/request-header-field-access-control-allow-headers-is-not-allowed-by-itself-in-pr |
| 11:18 | <jgraham> | Ms2ger: That appears to be a subset of all the interns though |
| 11:21 | <MikeSmith> | about python troubleshooting, how do you all normally troubleshoot code where it's using multiple libs and trying to figure out where a problem might be? |
| 11:22 | <MikeSmith> | gdb? |
| 11:22 | <MikeSmith> | and/or is there some way to just dump a stack trace? |
| 11:23 | <jgraham> | MikeSmith: What kind of problem? |
| 11:23 | <jgraham> | YOu can get a stacktrace from within python using the traceback module |
| 11:24 | <MikeSmith> | k |
| 11:24 | <jgraham> | pdb is also reasonable if you aren't running with multiple threads and things |
| 11:24 | <MikeSmith> | ah yeah |
| 11:24 | <jgraham> | If you have something super-complicated using gdb makes sense |
| 11:24 | <MikeSmith> | I recall use that before |
| 11:24 | <MikeSmith> | it's not super-complicated |
| 11:24 | <MikeSmith> | echo "<p>" | python -c "from sys import stdin; from lxml.html import html5parser as h5, tostring; print tostring(h5.parse(stdin, h5.HTMLParser(namespaceHTMLElements=False)))" |
| 11:24 | <jgraham> | e.g. I use gdb when I'm trying to figure out deadlocks |
| 11:24 | <MikeSmith> | <html:html xmlns:html="http://www.w3.org/1999/xhtml"><html:head></html:head><html:body><html:p>; |
| 11:24 | <MikeSmith> | </html:p></html:body></html:html> |
| 11:25 | <MikeSmith> | yeah this problem is not complex |
| 11:30 | <Ms2ger> | It involves an HTML parser, it is complex :) |
| 11:35 | <MikeSmith> | heh |
| 11:56 | <MikeSmith> | ok I reckon I have it figured out |
| 11:58 | <MikeSmith> | well, a guess at least |
| 12:11 | <annevk> | MikeSmith: tried to answer |
| 12:12 | <MikeSmith> | cool |
| 12:57 | <MikeSmith> | the Push API has landed in Gecko? |
| 12:57 | <MikeSmith> | https://bugzilla.mozilla.org/show_bug.cgi?id=1038811 |
| 12:57 | <MikeSmith> | resolved=fix |
| 12:57 | <MikeSmith> | wondering when it will ship |
| 13:23 | <gsnedders> | Ms2ger: well of course it didn't, Core hasn't existed for years! |
| 13:24 | <Ms2ger> | Can I bug you for reviews already? |
| 13:38 | <Ms2ger> | jgraham, annevk, you mentioned tea? https://historyofloveblog.wordpress.com/2013/10/10/can-drinking-tea-turn-you-into-a-whore/ |
| 13:41 | <annevk> | Ms2ger: I guess the rest of the world picked up on our channel topic at some point |
| 13:51 | <wanderview> | annevk: you around? |
| 13:51 | <annevk> | wanderview: c |
| 13:52 | <wanderview> | annevk: regarding this: https://github.com/whatwg/html/issues/95#issuecomment-138653119 |
| 13:52 | <wanderview> | annevk: as far as I can tell, the spec says to return the Response provided to respondWith() as the result of the fetch algorithm |
| 13:53 | <wanderview> | which suggests if the Response has a different url from the original Request, then that will be visible to script |
| 13:53 | <wanderview> | annevk: sorry if there is somewhere that says to override the Response.url with the original Request.url.... I can't find it |
| 13:53 | <annevk> | wanderview: step 15 of https://fetch.spec.whatwg.org/#main-fetch |
| 13:54 | <wanderview> | ah |
| 13:54 | <wanderview> | annevk: I see... and this works because 30x redirects are appending to the *request* url list, not the response list |
| 13:56 | <annevk> | wanderview: they can't append to the response list |
| 13:56 | <annevk> | wanderview: they are a response |
| 13:57 | <wanderview> | annevk: yea, I just think necko is modeled differently |
| 13:57 | <annevk> | ah, shucks |
| 13:59 | <wanderview> | annevk: the good news is my original concept of what SW+fetch was supposed to is correct... I just misread the spec when trying to prove it to ehsan |
| 14:03 | <annevk> | wanderview: have to bring your A game to ehsan |
| 14:03 | annevk | finds out that more headers are subject to Referer than just Referer! |
| 14:04 | <annevk> | Well, subject to the referrer policy... |
| 14:07 | <wanderview> | annevk: I'm going to CC you on this email if thats ok |
| 14:07 | <annevk> | wanderview: sure |
| 14:10 | <wanderview> | annevk: have you thought about how you will spec the opaque tainting? |
| 14:10 | <wanderview> | the opaque tainting for images written to canvas |
| 14:16 | <annevk> | wanderview: I haven't settled on something definitive yet I think, at the moment I'm just trying to convert the existing language and adding some new concepts along the way to help with that |
| 14:16 | <annevk> | wanderview: I hope that once I'm through I can figure out something that's a bit more coherent |
| 14:17 | <annevk> | wanderview: but in general it's as we discussed I think; basic/cors/default is "safe", other types are unsafe |
| 14:18 | <wanderview> | annevk: yea, I was more wondering how it would be tracked... just a boolean flag... or an origin that is compared |
| 14:19 | <annevk> | wanderview: ah I think I discussed that with bz and Hixie at some point and we decided boolean was fine |
| 14:20 | <annevk> | wanderview: that once you're secure it's okay, even if you then end up leaking it with your public suffix friends |
| 14:25 | <wanderview> | annevk: yea... I think we felt we needed the final URL fully propagated before we had some of the recent spec changes implemented... if you look at my email it seems we are safe and a boolean should work |
| 14:25 | <wanderview> | I think |
| 14:25 | <wanderview> | annevk: ehsan may disagree |
| 14:28 | <annevk> | wanderview: yeah the security really doesn't depend on URLs |
| 14:28 | <annevk> | wanderview: it's just tainting |
| 14:28 | <annevk> | wanderview: and once you're tainted you can't untaint |
| 16:02 | <Domenic> | jkdflsajdf git troubles |
| 16:02 | <Domenic> | fffrig annevk can you re-push that commit i killed it accidentally |
| 16:03 | <annevk> | Domenic: c6d4dda..8d1c8af ruby -> ruby |
| 16:03 | <annevk> | (aka done) |
| 16:04 | <annevk> | (also rebased) |
| 16:04 | <Domenic> | ok cool. github wasn't smart enough to re-associate with the pr oh well |
| 16:05 | <annevk> | Domenic: hmm weird, always works for me these days |
| 16:05 | <annevk> | Domenic: hmm you didn't push? |
| 16:05 | <Domenic> | annevk: I was experimenting with my local script and effed things up and force-pushed to the ruby branch with zero commits. which auto-closed the PR. when you re-added a commit it wasn't smart enough to re-open the PR. |
| 16:06 | <annevk> | Domenic: oh |
| 16:06 | <annevk> | perhaps edit the commit message then to say Close #101: ...? |
| 16:07 | Ms2ger | tends to put (fixes #nnn) at the ned |
| 16:07 | <Ms2ger> | end |
| 16:08 | <Domenic> | Oh I think I know the problem |
| 16:09 | <Domenic> | I was using my new checkout from the build script |
| 16:09 | <Domenic> | Which doesn't have the full history |
| 16:09 | <Domenic> | which makes git confused about remote branches that are based on top of previous commits |
| 16:09 | <annevk> | I gotta go for a bit |
| 16:09 | <Domenic> | (like ruby used to be) |
| 16:09 | <Domenic> | OK, it'll be merged with no problems by the time you get back, promise |
| 16:28 | <annevk> | Domenic: so the problem with not associating either through GitHub's purple thingie or an explicit "Close #n:" is that someone browsing the commit logs has no way to find the rationale |
| 16:28 | <Domenic> | annevk: oh, I see :( |
| 16:28 | <Domenic> | I was like ... but 101 is already accidentally closed... |
| 16:28 | <annevk> | Domenic: so I think we should maybe make that part of the policy, that you either have a clean merge or edit the commit message |
| 16:29 | <Domenic> | annevk: OK. I find it a bit weird for PRs to close themselves but your reasoning is more compelling. |
| 16:29 | <Domenic> | What some projects do is standardize on fields like PR URL: ... |
| 16:29 | <Domenic> | e.g. browse the commits at https://github.com/nodejs/node/commits/master |
| 16:46 | <annevk> | That seems fine too |
| 16:47 | <Domenic> | Is the ARIA PR still waiting on something? |
| 16:49 | <annevk> | Domenic: Hixie |
| 16:49 | <Domenic> | It looks like the ASCII fish example is still missing |
| 16:49 | <annevk> | Domenic: that seems to be in the referenced draft... |
| 16:50 | <Domenic> | I guess we shouldn't duplicate it |
| 16:50 | <annevk> | Domenic: Steve added it back in, but dropped it after Hixie's comments |
| 16:50 | <Domenic> | OK |
| 16:58 | annevk | added the kitchen sink to the header of https://twitter.com/htmlstandard |
| 17:07 | <annevk> | I'll merge ARIA |
| 17:14 | <annevk> | Getting some errors from the build script... |
| 17:28 | <annevk> | The errors were from the W3C Bugzilla cross-referencing btw |
| 17:28 | <annevk> | Closing the bugs seems to have helped... |
| 17:30 | <Domenic> | heh |
| 17:30 | <Domenic> | yeah I noticed MikeSmith removing some URLs from bugs presumably for similar reasons |
| 17:30 | <Domenic> | I need to fix https://github.com/whatwg/html-build/issues/21 |
| 18:24 | <Domenic> | beverloo: long shot but do you have a SVG of http://peter.sh/experiments/asynchronous-and-deferred-javascript-execution-explained/ |
| 18:37 | <hober> | MikeSmith: awwwwh, I miss you too Mike. |
| 19:10 | <wanderview> | annevk: Domenic: have we figured out how to handle variable length uploads with fetch streams integration? mcmanus tells me that will not work for http1 since it needs an accurate content-length on the upload |
| 19:11 | <Domenic> | wanderview: content-encoding chunked, right? |
| 19:11 | <Domenic> | wanderview: I thought all streaming uploads would be CE: chunked |
| 19:11 | <wanderview> | Domenic: http1.1 supports chunked, but http1 does not... and we cannot tell if the server supports 1.1 until after we send the request |
| 19:12 | <Domenic> | wanderview: i guess fetch stream uploads don't work with http 1.0 then |
| 19:12 | <wanderview> | Domenic: we're not tackling this in the spec yet, right? |
| 19:12 | <Domenic> | wanderview: no, no uploads yet. Q4 is yhirano_'s plan |
| 19:13 | <wanderview> | Domenic: well, FYI about this issue then... I ran into it a bit prematurely because I was trying to lay some groundwork in infrastructure while fixing another bug |
| 19:13 | <Domenic> | yeah, good to know :-S |
| 19:14 | <wanderview> | Domenic: is there an issue or somewhere I should note this? |
| 19:15 | <Domenic> | wanderview: fetch-with-streams has a whole label for upload, yeah, would be good. |
| 19:15 | <wanderview> | ok, thanks |
| 19:35 | <wanderview> | https://github.com/yutakahirano/fetch-with-streams/issues/57 |
| 19:48 | <MikeSmith> | TabAtkins: fyi http://stackoverflow.com/questions/32493442/html-whitespace-spaces-before-and-after-br |
| 19:50 | <MikeSmith> | Domenic: yeah, I removed the URLs from those bugs because with the source on the ARIA branch, the presence of them was an error, so rightly the merge of the branch shouldn't happen until those errors were fixed |
| 19:50 | <MikeSmith> | this is another thing we need to document |
| 19:51 | <MikeSmith> | the timing of when to remove the URLs is a gray era I guess. But basically, they shouldn't be removed until there's agreement to merge the branch |
| 19:53 | <MikeSmith> | also I think someone reviewing the branch needs to take also responsibility for actually closing the bugs (or moving their components), if it turns out that after the changes, the bug is no longer relevant or has been resolved by the changes on the branch |
| 19:54 | <annevk> | wanderview: I guess it would just fail for HTTP/1.0 then |
| 19:54 | <annevk> | wanderview: is that problematic? |
| 19:54 | <wanderview> | annevk: if the js script expects to do an infinite upload stream... what will happen? |
| 19:55 | <wanderview> | get an error code immediately when it sees the chunked setting? |
| 19:55 | <wanderview> | when the server sees |
| 19:55 | <wanderview> | or does the server wait for the entire body to finish before sending an error code? |
| 19:55 | <wanderview> | I expect there are server bugs here |
| 20:00 | <annevk> | wanderview: I have no idea |
| 20:00 | <annevk> | wanderview: servers are rather broken, typically |
| 20:00 | <wanderview> | annevk: yea, just saying we should test some servers and see what they do |
| 20:00 | <wanderview> | before creating a footgun to easily OOM the browser |
| 20:00 | <wanderview> | because servers do something different than we expect |
| 20:01 | <wanderview> | annevk: in fairness, browsers are rather broken typically too |
| 20:05 | <MikeSmith> | annevk: the https://twitter.com/htmlstandard image is perfect🖖 |
| 20:20 | <caitp> | hah |
| 20:22 | <Domenic> | someone test http://jsbin.com/xelixaqaru/edit?html,output in Safari for me? what type of error is in your console? |
| 20:22 | <MikeSmith> | Domenic: looking now |
| 20:23 | <MikeSmith> | 7TypeError |
| 20:23 | <Domenic> | perfect |
| 20:24 | <MikeSmith> | Domenic: btw I think adopting a PR URL: convention would be good |
| 20:24 | <MikeSmith> | with the nit that it could just as well but PR: |
| 20:24 | <MikeSmith> | (without the URL part) |
| 20:25 | <MikeSmith> | because it's always going to be a URL |
| 20:25 | <MikeSmith> | *could just as well be just "PR:" |
| 20:26 | <Domenic> | Heh yes |
| 20:40 | <Domenic> | MikeSmith: regarding https://github.com/whatwg/html-build/issues/21#issuecomment-139366175, should we just treat any output from wattsi as an error, and return the error text instead of the zip file? |
| 20:40 | <TabAtkins> | MikeSmith: Thanks for the heads up on that SO thread. I've sent email to the list about it. ^_^ |
| 20:45 | <MikeSmith> | TabAtkins: cool |
| 20:45 | <MikeSmith> | TabAtkins: I really wish you were the one editing that spec |
| 20:45 | <MikeSmith> | but you can't do everything, I guess |
| 20:56 | <TabAtkins> | Unfortunately. |
| 22:22 | <MikeSmith> | TabAtkins: the CSS WG should put a clear disclaimer on those other specs |
| 22:23 | <TabAtkins> | What other specs? |
| 22:23 | <MikeSmith> | Warning: This spec was NOT written by Tab Atkins |
| 22:23 | <MikeSmith> | I mean |
| 22:23 | <MikeSmith> | I'm only half-joking |
| 22:25 | <MikeSmith> | because seriously if I go to look at a CSS WG spec and don't see that you have been one of the people working on it, I am not always super-confident about the rigor/precision/etc of what I may find inside |
| 23:24 | <gsnedders> | y'know, having booked tickets and hotels for TPAC, I probably ought, like, join a W3C WG. |
| 23:24 | <TabAtkins> | <3 |
| 23:24 | <gsnedders> | Given I'm currently on, um, none. |
| 23:26 | <tantek> | gsnedders, aren't you a member of the WHATWG CG? |
| 23:26 | <tantek> | perhaps find an IG or two to join as well. |
| 23:30 | <Domenic> | Yay the canvas PR is here. I love new features. |
| 23:31 | <gsnedders> | tantek: I should rejoin the CSS WG too, given I'm probably gonna start kicking around there again too |
| 23:31 | <gsnedders> | tantek: given the whole habit of giving ex-members IE status |
| 23:32 | <tantek> | doesn't hurt to ask the chairs |
| 23:34 | <gsnedders> | MikeSmith: can you prod someone so my invited expert application gets accepted? AFAICT nobody gets notified given I already had one on file from when I was an invited expert before? |
| 23:42 | <ccardona-work> | Where is the TPAC this year? |
| 23:43 | <ccardona-work> | Japan? |
| 23:47 | <gsnedders> | ccardona-work: yeah, in Sapporo |
| 23:47 | <ccardona-work> | that sounds exciting. |
| 23:47 | <ccardona-work> | i realize now how fortunate I was that it happened in San Jose a few years back and I was able to go. |