| 07:52 | <annevk> | zcorpan: do browsers have such a hook internally? |
| 07:53 | <zcorpan> | annevk: i don't know |
| 07:54 | <annevk> | zcorpan: perhaps the "adopting steps" should only run if the document actually changes (and otherwise you just get the removal notification) |
| 07:54 | <zcorpan> | annevk: yeah, i was thinking that as well |
| 07:55 | <zcorpan> | annevk: what other things are using "adopting steps"? |
| 07:55 | <annevk> | I guess asking smaug and Dominic might help |
| 07:55 | <annevk> | zcorpan: <template> |
| 07:57 | <zcorpan> | annevk: looks like <template> wouldn't regress with such a change |
| 07:57 | <annevk> | zcorpan: agreed |
| 07:57 | <annevk> | zcorpan: would still like to check with implementations though |
| 07:57 | <zcorpan> | yeah |
| 07:58 | <zcorpan> | i can file a bug on the dom spec |
| 08:02 | <annevk> | ta |
| 08:12 | <ritsyy> | zcorpan: sometimes when i wrap it to 100 characters the lines become very messy, wrapping it to 80 characters would be bad solution to it? |
| 08:12 | <ritsyy> | zcorpan: i think the wrapping looks weird still https://github.com/Ritsyy/html/commit/8105da3c0feab3c4a186e6b3a7ff1bf1e18836ea |
| 08:13 | <zcorpan> | ritsyy: where did those < come from? :-) |
| 08:15 | <ritsyy> | zcorpan: ah, sublime is rude to me see this one also when i wrap it to 100 characters the text goes like this http://pastebin.com/AtPCiq9Z |
| 08:16 | <ritsyy> | zcorpan: i tried to clean them up, but i am not able to figure out why it add these > , i am really sorry i'll change it |
| 08:16 | <zcorpan> | ritsyy: no problem |
| 08:17 | <ritsyy> | zcorpan: thank you |
| 08:17 | <zcorpan> | ritsyy: as for messy lines, i think just wrap to 100 anyway and not worry about it looking "messy" |
| 08:18 | <ritsyy> | zcorpan: okay :) |
| 08:19 | <zcorpan> | ritsyy: maybe sublime's wrap thing thinks < is a quote or comment character or something? maybe it can be turned off somehow |
| 08:19 | <ritsyy> | zcorpan: yes maybe that can be a reason i'll search for it |
| 08:24 | <annevk> | ritsyy: you're on Linux, right? I think you should have gedit... Perhaps that works better? |
| 08:27 | <ritsyy> | annevk: yes i am on linux, okay i am using that now, hope it works right, thanks! |
| 08:42 | <annevk> | zcorpan: Domenic != Dominic |
| 08:43 | <zcorpan> | annevk: heh oops |
| 08:53 | <zcorpan> | Domenic: i get 2 wattsi errors when generating script-type-module branch |
| 09:36 | <annevk> | Domenic: https://github.com/annevk/html-cross-origin-objects/issues/8 |
| 11:27 | <ritsyy> | annevk: is this one mentioning it the flag set correctly http://pastebin.com/73SBRcZT for bug https://github.com/whatwg/html/issues/176 |
| 11:28 | <annevk> | ritsyy: you want to do something like "Set <var>request</var>'s <span>... flag</span>." in a previous step, before <!--FETCH--> |
| 11:30 | <ritsyy> | annevk: okay, just thought if may be this could be correct, i'll add it before the <!--FETCH--> |
| 11:54 | <zcorpan> | https://github.com/issues?utf8=✓&q=is%3Aopen+is%3Aissue+label%3A"good+first+bug"+user%3Awhatwg <- all good first bugs for all whatwg repos |
| 11:57 | <annevk> | nice |
| 11:58 | <daurnimator> | "a HTTP server" or "an HTTP server"? |
| 11:58 | <akanksha_> | Hello zcorpan, I am new to whatwg. Can you suggest how to get started solving bug and setting up for development? |
| 11:58 | <annevk> | daurnimator: an, I think |
| 11:59 | <zcorpan> | akanksha_: welcome! good to have you here :-) |
| 11:59 | <zcorpan> | akanksha_: it depends on which spec you would like to work on. html? |
| 12:00 | <daurnimator> | annevk: so "A HTTP/1.0 connection" is okay? |
| 12:00 | <akanksha_> | Yeah sure! I'd love to work on HTML. |
| 12:00 | <daurnimator> | uh *"An HTTP/1.0 connection" |
| 12:01 | <annevk> | daurnimator: yeah, because of the way you pronounce HTTP/1.0 |
| 12:01 | daurnimator | says "haich tee tee pee" |
| 12:02 | <zcorpan> | akanksha_: great, have a look at https://github.com/whatwg/html#pull-requests and https://github.com/whatwg/html-build#html-build-tools and please ask questions if something is not clear |
| 12:02 | <annevk> | daurnimator: right, and for that "an" makes it sound more natural |
| 12:03 | <daurnimator> | annevk: (for "aiche" it does... not so much for "haich". but I think i'm in the minority here) |
| 12:03 | <annevk> | daurnimator: ah, hmm, you might be |
| 12:03 | <Ms2ger> | "The HTTP..." :) |
| 12:04 | <zcorpan> | "huttup" |
| 12:06 | <zcorpan> | https://www.youtube.com/watch?v=xqpd7WcBmjM |
| 12:27 | <Ms2ger> | whatwig? |
| 12:28 | <akanksha_> | zcorpan, On running build.sh I am getting the following error. I think it might be due to the proxy I am working behind. Can you point me in the right direction to make the change? http://fpaste.org/309752/26016681/ |
| 12:29 | <MikeSmith> | akanksha_: I'm not sure there's any way to fix that on the client side |
| 12:30 | <zcorpan> | akanksha_: MikeSmith: would a VPN help? |
| 12:30 | <MikeSmith> | zcorpan: sure |
| 12:31 | <MikeSmith> | but what would really help is if we just check that generated cldr file and XML file into our github repo and just version it |
| 12:31 | <akanksha_> | ^How would I go about doing that? |
| 12:32 | <MikeSmith> | zcorpan: I think it's pathological that we are making contributors deal with (re)builing those files just to be able to make a PR with a contribution |
| 12:32 | <Ms2ger> | Yeah, that cldr stuff is annoying |
| 12:33 | <MikeSmith> | zcorpan: this gets back to the question you had about downloading in parallel: The way I would prefer to deal with it is, we just quit imposing those downloads on contributors |
| 12:33 | <zcorpan> | MikeSmith: that sounds good |
| 12:34 | <MikeSmith> | OK I will make a PR for it and we'll see if we can get agreement on it |
| 12:34 | <MikeSmith> | akanksha_: there are some VPN services that are free I think |
| 12:35 | <MikeSmith> | gimme a minute to look |
| 12:37 | <MikeSmith> | http://www.vpnbook.com/ maybe |
| 12:37 | <akanksha_> | ^On it! |
| 12:40 | <annevk> | MikeSmith: we should perhaps also stop downloading unicode.xml or whatever the name is automatically |
| 12:40 | <MikeSmith> | annevk: yeah that's what I meant by "XML stuff" |
| 12:40 | <annevk> | MikeSmith: and just keep a local copy checked in, that we update once we have consensus that we actually want to change the specification around entities |
| 12:40 | <MikeSmith> | right |
| 12:41 | <MikeSmith> | agreed |
| 12:41 | <annevk> | especially given the latest thing there where upstream changed but we found out we didn't want to change |
| 12:42 | <MikeSmith> | right |
| 12:42 | <MikeSmith> | plus the fact that upstream doesn't change that often to begin with |
| 12:51 | <akanksha_> | Hey, so I got the build done. While I was trying to setup the vpn account I also decided to look up changes that I could make to let that cldr download command run with proxy settings and turns out by changing svn server config to use my proxy settings I was able to do so. I'd like to get started with some easy bugs to get a feel of the code. I am a student |
| 12:51 | <akanksha_> | so bear with me if I am a little slow. Can you all suggest some easy bug so I can make my initial PR? |
| 12:59 | <zcorpan> | akanksha_: https://github.com/whatwg/html#contribution-opportunities has links to good first bugs. e.g. https://github.com/whatwg/html/issues/502 seems easy |
| 13:27 | <robertkowalski> | :)) |
| 13:28 | <Ms2ger> | > investigated cross-browser behaviour of initial about:blank iframe loads |
| 13:28 | <Ms2ger> | jdm is the new hsivonen |
| 13:37 | <smaug____> | why do we need https://w3c.github.io/preload/? |
| 13:37 | <smaug____> | yoav_, igrigorik ^ |
| 13:38 | <smaug____> | it smells a lot like prefetch + some feature which service workers is supposed to deal with |
| 13:38 | <yoav_> | smaug____: prefetch is for next navigation, preload is for current one |
| 13:39 | <yoav> | main use case is to fetch critical resources with late discovery earlier |
| 13:40 | <yoav> | also enables to decouple download from execution while downloading with the right resource type |
| 13:40 | <smaug____> | yoav: "next navigation" is so vaguely spec'ed that browser can use it , and most probably does use it for "current navigation" |
| 13:41 | <smaug____> | "Add request to preload response cache (TODO). " |
| 13:41 | smaug____ | is not at all sold with the idea having different rel types for effectively same feature |
| 13:43 | <yoav> | smaug____: we started by a more unified model of rel types, but then split it out since it wasn't future friendly |
| 13:45 | <yoav> | the semantics of "prefetch" (next nav hint) and "preload" (mandatory current nav fetch) are significantly different |
| 13:45 | <smaug____> | prefetch is _very_vaguely spec'ed |
| 13:46 | <smaug____> | effectively only thing spec is is "The prefetch relationship is used to declare a resource that might be required by the next navigation, and that the user agent SHOULD fetch, such that the user agent can deliver a faster response once the resource is requested in the future." |
| 13:46 | <smaug____> | that is all |
| 13:46 | <smaug____> | and "next navigation" itself is unclear |
| 13:48 | <smaug____> | is it really the idea that prefetch can't be used at all in single page applications ? |
| 13:49 | smaug____ | wants to see browser tests proving that they don't use prefetch'ed resources in such app |
| 14:18 | <zcorpan> | MikeSmith: what causes this?: |
| 14:19 | <zcorpan> | Possible article problems: |
| 14:19 | <zcorpan> | 17351: <dd>If the element has a <code data-x="attr-hyperlink-href">href</code> attribute: <span>Interactive content</span>.</dd> |
| 14:19 | <annevk> | zcorpan: see the end of the build script |
| 14:19 | <annevk> | zcorpan: should be "an href" |
| 14:19 | <zcorpan> | ah |
| 16:06 | <ritsyy> | https://github.com/whatwg/html/issues/388 this bug is still is showing up in open issues |
| 16:09 | <zcorpan> | Domenic: i know it's WIP :-D but i have to dig in to understand what's going on and maybe come up with something useful like https://github.com/whatwg/html/pull/443#issuecomment-170847782 , but feel free to ignore the wording nits for now |
| 16:10 | <Domenic> | zcorpan: OK :) good point I need to respond to that post |
| 16:12 | <zcorpan> | Domenic: is there an introduction or explainer for JS modules? i could read the JS spec but my brain is starting to block synapses this time of the day |
| 16:13 | <Domenic> | zcorpan: http://jsmodules.io/ is OK for basic syntax. A lot of what this PR is dealing with is the string portion (i.e. in `import * as fs from "fs"`, the "fs"). |
| 16:13 | <Domenic> | jsmodules.io glosses over the string portion |
| 16:14 | <annevk> | ritsyy: can you close it? |
| 16:14 | <annevk> | ritsyy: maybe mention the PR that fixed it in a comment while you do that |
| 16:14 | <zcorpan> | Domenic: thx |
| 16:16 | <ritsyy> | annevk: okay will do that |
| 17:12 | <jochen__> | is there somewhere a spec what the baseURI of a document should be if you open() it? |
| 17:29 | <gsnedders> | jochen__: about:blank, no? |
| 17:29 | <gsnedders> | jochen__: that should be in HTML |
| 17:31 | <jochen__> | i didn't find it |
| 17:31 | <jochen__> | and it appears to be the baseURI of the document that opened the doc |
| 17:33 | <jochen__> | https://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-72161170 is linked from mdn |
| 17:34 | <gsnedders> | "If the document's address is about:blank, and the Document's browsing context has a creator browsing context, then return the document base URL of the creator Document, and abort these steps. |
| 17:34 | <gsnedders> | from HTML |
| 17:35 | <gsnedders> | jochen__: you don't want to look at DOM Level 2 HTML, really |
| 17:35 | <gsnedders> | jochen__: https://dom.spec.whatwg.org is way closer to reality |
| 17:37 | <annevk> | MDN should update its URLs at some point |
| 17:38 | <annevk> | jochen__: https://github.com/whatwg/html/issues/421 has some related discussion |
| 18:37 | <ritsyy> | for this bug https://github.com/whatwg/html/issues/156 , as the byte sequences are fixed for headers, |
| 18:37 | <ritsyy> | i needed a starting pointer of how headers are byte sequences or any other example to explain this |
| 19:25 | <Jasper> | Bizarre question. Google doesn't give a clear answer. What's the state of the art for gzip / deflate in HTTP *requests*? |
| 19:25 | <Jasper> | mod_deflate seems to support Content-Encoding: gzip on requests, but I can't find any client that would ever use it, because of capability negotiation stuff. |
| 19:26 | <Jasper> | Theoretically, clients could use an HTTP OPTIONS request to figure out what the server supports, but I can't find any standard for what header to send back -- both Content-Encoding and Accept-Encoding are in active use. |
| 19:26 | <Jasper> | Did I miss something obvious here? |
| 19:32 | <caitp> | I thought gzipping responses was something servers were just configured to do |
| 19:32 | <caitp> | never heard of a negotiation for that |
| 19:33 | <gsnedders> | Jasper: as far as I know, there's been no real movement in forever on that front. |
| 19:33 | <Jasper> | caitp, requests, not responses. |
| 19:33 | <Jasper> | gzipped responses are negotiated by the client setting Accept-Encoding in the request header |
| 19:35 | <Jasper> | gsnedders, OK, thanks. |
| 19:35 | <Jasper> | We're trying to cut down on upload sizes. We'll probably just gzip the payload ourselves rather than try to use HTTP for it. |
| 19:41 | <IZh> | Hixie: Domenic, annevk: Hi! My PDF generator can't again generate the document because of https://html.spec.whatwg.org/images/wolf.jpg and https://html.spec.whatwg.org/images/kettlebell.jpg images having MIME type text/html which is a bit wrong. |
| 19:42 | <Domenic> | IZh: oh, thanks, will fix!! |
| 22:35 | <gsnedders> | SimonSapin: do you have any interest in maintaining (python-)webencodings any more? |
| 22:35 | <gsnedders> | SimonSapin: I assume not? :) |
| 22:48 | <yoav> | Domenic: friendly ping on https://github.com/whatwg/dom/pull/144 :) |
