| 00:36 | <MikeSmith> | heycam: if the dev.w3.org URL that's slow or unresponsive is under http://dev.w3.org/csswg/ or http://dev.w3.org/fxtf/ it's being rewritten to http://drafts.csswg.org/ so any problems with it being unresponsive or loading slowly would likley be due to drafts.w3.org instead of dev.w3.org itself |
| 00:37 | <heycam> | MikeSmith, I see. thanks; will ping plinss in the future about that. |
| 00:37 | <MikeSmith> | k |
| 00:38 | <MikeSmith> | that said though, there have been times in the past when crawlers hit dev.w3.org and cause it to become unresponsive but I think these days the rate-limiting setup that the systeam has there should prevent that from happening |
| 00:41 | <heycam> | ok |
| 01:36 | <_2_daychelin> | Hola |
| 01:36 | <botie1> | salut, _2_daychelin |
| 10:12 | <Ms2ger> | MikeSmith, you have an SGML book behind your desk? |
| 10:14 | <zcorpan> | Ms2ger: don't you? |
| 10:15 | Ms2ger | double-checks |
| 10:15 | <Ms2ger> | No |
| 10:15 | <zcorpan> | handy to look up how parameter entities in the external subset work |
| 10:16 | <zcorpan> | or how to tweak the SHORTTAG feature |
| 10:17 | <zcorpan> | ain't that right, MikeSmith? |
| 10:19 | <MikeSmith> | zcorpan: You know me too well |
| 10:20 | MikeSmith | orders an SGML book to send Ms2ger for his bookshelf |
| 10:25 | <Ms2ger> | Oh, I needed a monitor stand :) |
| 10:30 | <jgraham> | How are we all looking behind MikeSmith's desk? Has he decided to supplement his salary by becoming a camboy? |
| 10:34 | <zcorpan> | jgraham: Naoko Smith leaked a picture on the twitters |
| 10:39 | <zcorpan> | promise experts, does http://www.w3.org/2009/dap/track/issues/166 make sense? |
| 10:42 | <Ms2ger> | If so, it should probably be an attribute |
| 11:50 | <annevk> | Ms2ger: it should, but they probably don't want to expose that on navigator as such due to people enumerating the properties of the object |
| 11:50 | <annevk> | Ms2ger: see also getGamepads() |
| 12:14 | <Ms2ger> | Does https://html.spec.whatwg.org/multipage/infrastructure.html#root-element allow the "root element" of a node to not be an element? |
| 12:17 | <annevk> | Ms2ger: seems like it |
| 12:18 | Ms2ger | files a bug |
| 14:03 | <zcorpan> | what is the situation for high-resolution backing store for canvas? i'm having trouble finding relevant things in the spec |
| 14:37 | <annevk> | zcorpan: didn't we give up? |
| 14:39 | <annevk> | zcorpan: https://html5.org/r/8397 and https://www.w3.org/Bugs/Public/show_bug.cgi?id=24301 |
| 14:56 | <zcorpan> | annevk: thx |
| 15:15 | wanderview | enables cloudflare to get https on his github.io blog. |
| 16:16 | <gsnedders> | <b><b><b><b>x</b></b></b></b>y — what's the parent of the y? |
| 16:17 | <Ms2ger> | The pa- Oh wait, AAA |
| 16:23 | <jgraham> | gsnedders: The parent of the outermost <b> |
| 16:28 | <gsnedders> | jgraham: (that's the whole document, so that'd be body) |
| 16:28 | <gsnedders> | (this is all about how Noah's Ark effects it) |
| 16:30 | <jgraham> | *affects |
| 16:30 | <gsnedders> | (I have someone claiming it sohuld end up as the child of the outermost <b>, and I'm pretty sure they're wrong) |
| 16:30 | <jgraham> | Yes, try it in any browser :p |
| 16:30 | <gsnedders> | jgraham: can I take the descriptive view that both words are synonymous nowadays? :P |
| 16:30 | <jgraham> | gsnedders: No |
| 16:30 | <jgraham> | If they were I wouldn't have corrected you :p |
| 16:32 | <Ms2ger> | Why would you aks such a thing? |
| 17:05 | <wanderview> | Domenic: do you use cloudflare flexible ssl or full ssl with your github.io page? |
| 17:05 | <Domenic> | wanderview: flexible SSL |
| 17:05 | <wanderview> | k |
| 17:06 | <wanderview> | seems like full ssl should be possible since subdomain.github.io supports https |
| 17:50 | <JakeA> | annevk: Chrome are going to use https://github.com/slightlyoff/ServiceWorker/issues/609#issuecomment-74714928 as a way to progress with postMessage, let me know if I got it wrong |
| 17:51 | <annevk> | JakeA: "We're in agreement"? |
| 17:51 | <JakeA> | annevk: I thought you said you were happy with that model now? |
| 17:52 | <JakeA> | (I'll change it if not) |
| 17:53 | <annevk> | JakeA: well, I think after I said that I posted that comment with some other considerations |
| 17:53 | <annevk> | JakeA: I'd like to understand why we still think that ServiceWorker and Client having different lifetime models is a good idea |
| 17:58 | <TabAtkins> | zcorpan: Re: battery promise, is the promise solely used to gate the battery access behind an async wall? That is, it'll generally be perma-fulfilled? |
| 17:59 | <zcorpan> | TabAtkins: i don't know, haven't read the spec. this just appeared in my critic inbox |
| 18:00 | <JakeA> | annevk: this is the reason clients are snapshots https://github.com/slightlyoff/ServiceWorker/issues/588#issuecomment-66985639 - if each property is behind a promise, it's going to be unmanageable |
| 18:03 | <JakeA> | annevk: regardless, I'm not sure what dynamic clients buys us in terms of postMessage |
| 18:05 | <annevk> | JakeA: well e.g. === checks |
| 18:06 | <annevk> | JakeA: if you keep getting copies of Client objects, it's somewhat annoying |
| 18:06 | <annevk> | JakeA: and will be impossible to tell two Gmail windows aparts |
| 18:08 | <JakeA> | annevk: I think it's worthwhile looking at that, but this feels separate to where client.postMessage and serviceWorker.postMessage land |
| 18:10 | <annevk> | JakeA: well when live it would mean onmessage could be elsewhere |
| 18:10 | <annevk> | JakeA: as I suggested in that comment |
| 18:13 | <JakeA> | annevk: So function onMessage() {...} clients.forEach(client => client.onmessage = onMessage) would become SW boilerplate? |
| 18:15 | <annevk> | we could make the comment bubble to self.clients |
| 18:15 | <annevk> | s/comment/event/ |
| 18:23 | <JakeA> | annevk: that makes iterating through clients really tough when it comes to selecting one to potentially focus / postMessage. Also, serviceWorkerInstance.postMessage going to self.onmessage fits in well with the dedicated worker model. I realise that it isn't 1:1 like dedicated worker, but I don't think that's an issue when it comes to developers using the |
| 18:23 | <JakeA> | API |
| 18:24 | <annevk> | JakeA: why does it make iteration tough? |
| 18:25 | <JakeA> | annevk: See https://github.com/slightlyoff/ServiceWorker/issues/588#issuecomment-66985639, now imagine each state property was behind a promise |
| 18:27 | <annevk> | JakeA: yeah, if they were actually live I'd imagine we'd update state based on events |
| 18:27 | <annevk> | JakeA: similar to the other side |
| 18:28 | <JakeA> | annevk: would you still have the client getter behind a promise? Means that those objects aren't always there to have to update |
| 18:41 | <annevk> | JakeA: that seems like an optimization the UA could make |
| 19:09 | <Domenic> | annevk: CORS pinning++ |
| 21:29 | <smaug____> | hmm, can <embed> load web pages or only <object> |
| 21:30 | <smaug____> | looks like it can |