| 06:44 | <annevk_> | TabAtkins: for Document there's this note in the source '"Document" isn't properly defining itself, and the force switch isn't working.' |
| 06:44 | <annevk> | TabAtkins: is there a bug on file for that in Bikeshed? |
| 06:44 | <annevk> | TabAtkins: also, I noticed addEventListener also links to the HTML specification... |
| 06:45 | <annevk> | TabAtkins: it seems we should blacklist some terms for HTML |
| 07:01 | <annevk> | TabAtkins: filed https://github.com/tabatkins/bikeshed/issues/403 |
| 08:28 | <Ms2ger> | annevk, your latest DOM commit isn't necessary |
| 08:28 | <Ms2ger> | https://dom.spec.whatwg.org/#concept-element-attributes-get-by-name already lowercases |
| 08:34 | <rcombs> | How do I patch KDE2 under FreeBSD? |
| 08:41 | <Domenic> | Ms2ger: it is necessary; otherwise setAttribute("ALIGN", "left") + getAttribute("align") doesn't work |
| 08:41 | <Ms2ger> | Domenic, no, it isn't |
| 08:42 | <Ms2ger> | Wait |
| 08:42 | <Ms2ger> | Oh, hmm |
| 08:42 | <Ms2ger> | Okay, it's half necessary :) |
| 08:42 | <Domenic> | If it helps, I have an implementation of the 8-hours-ago spec that fails related web-platform-tests :) |
| 08:43 | <Ms2ger> | We'll lowercase twice now, so that kinda sucks |
| 08:44 | <Domenic> | How are case-insensitive maps normally done? I would think you'd need to lowercase on both set and get |
| 08:45 | <Domenic> | I guess you could do case-insensitive comparison on get |
| 08:45 | <Domenic> | not sure if that's implementable any faster |
| 08:50 | <annevk> | Ms2ger: I agree it's not great |
| 08:50 | <annevk> | Ms2ger: but I couldn't see a better abstraction immediately |
| 08:50 | <annevk> | Ms2ger: and I figured it would be better to fix this bug and refactor later |
| 08:50 | <Ms2ger> | Yeah, makes sense |
| 08:52 | <annevk> | Domenic: normally you want a canonical form so you can store atoms internally |
| 08:56 | <annevk> | Anyone have a good logo for the Storage Standard? |
| 08:58 | <Domenic> | boxes ... something windows 95ey... |
| 08:59 | <Domenic> | database cylinders... |
| 08:59 | <Domenic> | database cyclinders are popular https://www.google.de/search?q=storage+icon |
| 09:00 | <annevk> | Heh, or a cloud I guess |
| 09:00 | <Domenic> | gotta save that for the cloud standard |
| 09:00 | <Domenic> | floppy disk icon |
| 09:00 | <annevk> | Fair, I'm game with cyliners, I wonder if zcorpan has some cycles to whip up some SVG |
| 09:01 | <annevk> | Floppy disk would also be great |
| 09:01 | <Domenic> | zcorpan usually is the best at this |
| 09:01 | <Domenic> | i like floppy disk a lot too now |
| 09:02 | annevk | finds http://commons.wikimedia.org/wiki/File:Floppy_icon.svg in the public domain |
| 09:02 | <annevk> | Adopting the original one with less detail in some way might be good, maybe I'll take a stab once I have done some actual work |
| 09:03 | <Domenic> | always a balance with these things between making the pretties and doing real work |
| 09:03 | <Domenic> | i still want to spruce up the mobile stylesheets for the specs and add some kind of floating TOC sidebar for the desktop ones |
| 13:50 | <annevk> | MikeSmith: https://twitter.com/azu_re/status/595212022314217472 Translate gives "Of the of" as translation for the first couple of symbols, is there anything more to it? |
| 13:51 | <wanderview> | Domenic: so I spoke with someone at a node meetup last week who is using streams to pass js objects and is using multiple readers from the same stream |
| 13:51 | <wanderview> | Domenic: this seems somewhat reasonable to me... what do you think? |
| 13:52 | <annevk> | tobie: [[ENCODING]] is also a bit weird, listing what the W3C considers to be the editors |
| 13:52 | <annevk> | tobie: perhaps we should just support duplicate metadata for certain entries? |
| 13:52 | <Domenic> | wanderview: seems like a good case for a tee or two |
| 13:53 | <Domenic> | wanderview: or just a single reader that calls multiple functions |
| 13:53 | <wanderview> | Domenic: the problem with tee is that you now have multiple readers consuming the same object... not the same as multiple readers from the same stream |
| 13:53 | <annevk> | I wish I could tee my tea |
| 13:53 | <Domenic> | wanderview: you mean, alternating? |
| 13:53 | <Domenic> | wanderview: in that case yeah, a single reader alternating between the functions it calls |
| 13:53 | <Domenic> | wanderview: they can just hand out the reader object to multiple people |
| 13:54 | <wanderview> | Domenic: yea... or lock and unlock on each read |
| 13:54 | <Domenic> | meh just handing out the object seems simpler |
| 13:54 | <Domenic> | The object is the capability; if you want to give it out widely, no problem with doing so. |
| 13:54 | <wanderview> | Domenic: use case I can think of is where each reader represents a remote server to do the real work... and you are distributing the incoming load to them |
| 13:55 | <wanderview> | Domenic: or (harder to implement now), somehow attach N Worker threads to read from the same stream |
| 13:55 | <wanderview> | classic queue-with-threadpool model |
| 13:56 | <wanderview> | it would be kind of nice to give devs the ability to build a threadpool in some way |
| 13:56 | <Domenic> | seems totally doable |
| 13:57 | <Domenic> | .read().then(result => dispatchTo(workers[i], result)) |
| 13:58 | <wanderview> | Domenic: thats not the same... the workers should pull when they are done with previous work... what you wrote could cause values to backup behind a worker stuck on a lot of slow work |
| 13:59 | <Domenic> | fair |
| 13:59 | <Domenic> | still not hard |
| 13:59 | <wanderview> | yea, it can be built in a library... just a lot of extra messaging for js to manage |
| 14:00 | <Domenic> | especially easy if workers get to expose writable streams and writable streams get more fine-grained flow control (desiredSize) |
| 14:00 | <Domenic> | .read().then(result => findMinBy(workers, w => w.writable.desiredSize).writable.write(result.value)) // eliding done handling |
| 14:02 | <Domenic> | err findMaxBy |
| 14:34 | <wanderview> | Domenic: yea, that seems like a possible way to fix it as well |
| 14:44 | <annevk> | Is w3c-test.org offline? |
| 15:37 | <annevk> | https://resources.whatwg.org/logo-storage.svg |
| 15:40 | <Domenic> | might need some top and bottom borders, can't tell until i see it in a circle i guess |
| 15:46 | <TabAtkins> | Same. Like the idea, but possible needs borders. |
| 15:53 | <caitp-> | there are probably people working in tech today who have never seen a floppy disk in their life |
| 15:54 | <caitp-> | and yet it's still the universal "save/storage" symbol |
| 15:54 | <TabAtkins> | Yeah, but that's how iconography works. |
| 15:55 | <caitp-> | but we did move away from representing it with a 5 1/4" floppy |
| 15:57 | <TabAtkins> | Yeah, but the 3 1/2" inch was the last real hard disk (zip disks don't count, nobody cared about them) so there was nothing to update to afterwards. |
| 15:57 | <TabAtkins> | And consumer CDs were mostly readonly at first; so they couldn't take over. |
| 15:58 | <TabAtkins> | Plus hard drives were large enough by then that people rarely saved to an external thing anyway. So the icon froze. |
| 15:59 | <caitp-> | could always be a mashup google/amazon/apple/adobe/cloud logo |
| 16:01 | <annevk> | Domenic: hmm I guess I can make a border around it |
| 16:01 | <annevk> | I kind of liked it this way |
| 16:09 | <Domenic> | as i said, could work well once i see it with a circle around it |
| 16:12 | <annevk> | Not all logos have a circle |
| 16:13 | <Domenic> | hmm did not realize to what extent that was true |
| 16:13 | <Domenic> | i guess it would be better here not to |
| 16:13 | <Domenic> | hmm |
| 16:13 | Domenic | notices the quirks mode logo ... amazing... |
| 16:15 | <Domenic> | I got un-lazy and used inspector to edit storage.spec.whatwg.org and show the logo in place (no circle). I think the giant gap at the bottom where it bleeds into the page is too much :-/ |
| 16:19 | <annevk> | hmm yeah |
| 16:27 | <TabAtkins> | annevk: It might be fine with a circle around it! I'm not sure. I just *suspect*, without seeing it in full, that the open space at the top and bottom will look weird. But maybe it's fine. |
| 16:35 | <annevk> | Further patches/bug reports to the storage logo welcome in the resources.whatwg.org repo |
| 21:04 | <wanderview> | jsbell: review ping on this last PR... https://critic.hoppipolla.co.uk/r/4825 |
| 21:07 | <jsbell> | wanderview: oops, forgot to submit... |
| 21:08 | <wanderview> | jsbell: the fetch-with-streams really does not drain the Response on .text()? that seems... really wrong |
| 21:10 | <jsbell> | wanderview: there was a recent change in chromium to align with that by the spec author, so I guess so. I have not absorbed streams or fetch-with-streams enough to argue. But I agree it seems weird. |
| 21:11 | <wanderview> | jsbell: well, I've objected to that proposal... I'll follow-up on that... and last I heard from annevk this was not being merged into fetch yet |
| 21:11 | <wanderview> | jsbell: seems premature to include this in wpt upstream |
| 21:19 | <wanderview> | jsbell: with this behavior it seems it forces the browser to keep the contents of the stream in memory.... |
| 21:23 | <wanderview> | jsbell: thanks... for being obstinate |
| 21:23 | <jsbell> | :) |
| 21:24 | <jsbell> | wanderview: not waiting on anything else from me, correct? |
| 21:24 | <wanderview> | jsbell: correct, thank you very much for reviewing all those! |
| 21:25 | <wanderview> | I wrote a new issue for the bodyUsed thing: https://github.com/yutakahirano/fetch-with-streams/issues/37 |
| 21:25 | <jsbell> | wanderview: np; we'll "downstream" them into Blink soon (I have a minion now...) |
| 21:26 | <jgraham> | wanderview: Oh, so is everything you are waiting for in wpt now merged? |
| 21:27 | <wanderview> | jgraham: I have to address a nit in that last PR |
| 21:27 | <wanderview> | and then I will ask you to merge |
| 21:27 | <jgraham> | Oh, OK |
| 21:27 | jgraham | requests that people use Issue for things that actually have to be fixed |
| 21:28 | <jgraham> | Even nits, if they have to be fixed |
| 21:29 | <wanderview> | jgraham: I wish there was an easy way to run a PR to wpt upstream against the browser |
| 21:29 | <wanderview> | to make sure I don't make a stupid typo |
| 21:30 | <jgraham> | wanderview: Like starting the webserver on your local machine and running the test? Because that's very possible |
| 21:30 | <jgraham> | ./serve in the wpt checkout root, although you probably need to configure your hosts file |
| 21:31 | <wanderview> | jgraham: how do I get the tools dir? |
| 21:31 | <jgraham> | git submodule update --recursive --init |
| 21:31 | <jgraham> | https://github.com/w3c/web-platform-tests/blob/master/README.md#running-the-tests |
| 21:33 | <wanderview> | jgraham: sadly, that doesn't work too well on my headless linux machine |
| 21:33 | <wanderview> | if it only listens on localhost |
| 21:35 | <jgraham> | wanderview: You can actually change that in the config file |
| 21:36 | <jgraham> | Create a config.json with the bits of https://github.com/w3c/web-platform-tests/blob/master/config.default.json that you want to override |
| 21:37 | <wanderview> | I'm just cloning it on my laptop |
| 21:37 | <wanderview> | I have about 3 minutes before I have to leave |
| 21:39 | <wanderview> | jgraham: sorry... it didn't work and I don't have time to investigate more... if you want me to retest before merging I can do it tomorrow |
| 21:44 | <jgraham> | wanderview: Well it still needs to be reviewed anyway |
| 21:45 | <jgraham> | So I guess if jsbell tests and reviews it then I will merge it, but it does seem like tomorrow is more likely |
