| 00:15 | <zewt> | wish more systems would take the web's lead in eliminating rare edge cases from APIs |
| 00:16 | <zewt> | (re: most of the day spent running down bugs caused by weird, obscure android service behavior) |
| 02:47 | <munsterberg> | leave |
| 08:42 | <annevk> | beverloo: thanks for patching all the things :-) |
| 12:02 | <beverloo> | annevk, np :) |
| 12:56 | <annevk> | JakeA: beverloo: Google still pushing requestAutocomplete()? |
| 12:56 | <annevk> | JakeA: beverloo: just noticed development at Mozilla seems stalled since June/July last year |
| 12:57 | <annevk> | JakeA: beverloo: was really hoping we'd make some progress on payments :-( |
| 14:46 | <wanderview> | annevk: whats a CG vs a WG? |
| 14:47 | <annevk> | wanderview: CG is a community group, WG is a working group; difference is mostly related to how IPR works |
| 14:47 | <wanderview> | annevk: what is IPR? |
| 14:47 | <annevk> | wanderview: and who gets to influence what is in scope and such |
| 14:47 | <annevk> | wanderview: intellectual property rights? I think... |
| 14:47 | <wanderview> | ah, ok |
| 14:48 | <annevk> | wanderview: WG is harder to setup but has strong theoretical protection |
| 14:48 | <wanderview> | annevk: what percentage of w3c discussions takes place with acronyms? |
| 14:48 | <annevk> | none of it has been battle tested I think |
| 14:48 | <annevk> | wanderview: a lot? |
| 14:49 | <wanderview> | that was meant to be a joke :-) |
| 14:55 | <jgraham> | Pretty sure it's 100% ACD |
| 14:56 | <annevk> | Even acronyms are abbreviated as <abbr> |
| 14:58 | <jgraham> | Well yes, at one point, most W3C discussions were themselves actually about <acronym> |
| 16:02 | <JakeA> | annevk: I haven't heard much from rAC lately. I'm not a huge fan of it. But I don't know what our plans are. |
| 16:03 | <annevk> | JakeA: I haven't really seen anything better to do payments |
| 16:03 | <annevk> | JakeA: though admittedly I didn't really like it either and it still doesn't seem like a silver bullet, but I doubt there is one |
| 16:05 | <JakeA> | annevk: yeah. It doesn't offer a whole lot beyond autocomplete |
| 16:18 | <annevk> | JakeA: I think the main thing it offers is some native UI controlled by the browser and a protocol to get that information on a page |
| 16:18 | <annevk> | JakeA: which is sort of the basics of what payments would look like |
| 16:18 | <annevk> | JakeA: but it needs iteration, e.g. generating tokens and not sharing credit card data would be great, though would require browsers to cooperate with banks somehow |
| 17:33 | <annevk> | https://medium.com/backchannel/marissa-mayer-has-completed-step-one-71dc31912855 Hmm, yet another article dissing "HTML 5" for mobile, this time from a Yahoo! perspective |
| 17:44 | <tantek> | annevk: and all this work we did to switch from "HTML 5" to HTML5. sigh. |
| 17:45 | <annevk> | tantek: yeah, I'm not sure what's bothering me more with that bit :-P |
| 18:30 | <wanderview> | JakeA: do you know if Service Worker scripts and related importScripts() end up in the normal http cache in blink? or do you bypass normal http caching in that case? |
| 19:27 | <Krinkle> | Hixie: Heya, regarding link disabled. Wanna pick your brain for a sec. |
| 19:28 | <Krinkle> | The issue we ran into is that adding them dynamically means you run into the problem of not having a callback |
| 19:28 | <Krinkle> | Or was that resolved? |
| 19:29 | <Krinkle> | Which makes orchestration of enabling more than one stylesheet, as well as disabling the previous set, almost impossible. |
| 19:31 | <Domenic> | Hixie: I'm idly curious what made you decide navigator.vendorSub was worth adding? |
| 20:02 | <jsbell> | wanderview: re: SW+importScripts - yes, they read/write from the normal http cache. |
| 20:02 | <jsbell> | (in addition to the dedicated SW script cache) |
| 20:02 | <wanderview> | jsbell: ok... and you are just pinning them in the http cache somehow? |
| 20:02 | <jsbell> | wanderview: no, we end up storing 'em twice |
| 20:02 | <wanderview> | jsbell: awesome... we're going to do the same :-) |
| 20:02 | <jsbell> | wanderview: on the list of things to optimize |
| 20:03 | <wanderview> | jsbell: thanks! |
| 20:03 | <jsbell> | np |
| 20:04 | <wanderview> | jsbell: you plan to optimize with de-dupe with http cache? |
| 20:05 | <gsnedders> | annevk: I remember you making a comment along the lines of the "XML Namespaces is hard enough even Presto manages to get it wrong subtly". I don't remember in what way. Do you? :P |
| 20:38 | <Hixie> | Krinkle: how do you mean, you don't have a callback? |
| 20:38 | <Hixie> | Domenic: did the checkin comment link to the bug fail? |
| 20:38 | <Krinkle> | Hixie: From when the stylesheet has finished loading |
| 20:38 | <Hixie> | TabAtkins: https://www.w3.org/Bugs/Public/show_bug.cgi?id=28080 |
| 20:38 | <Hixie> | Krinkle: can't you use <link onload>? |
| 20:39 | <Krinkle> | Hixie: <link> has onload? O_O |
| 20:39 | <Domenic> | Hixie: never noticed the "bug" column in the tracker until today! |
| 20:40 | <Domenic> | Wow, how are people using navigator.vendorSub if it is always the empty string? It's falsy, even!? |
| 20:40 | <Hixie> | hell if i know man |
| 20:40 | <Hixie> | foolip is the one to ask |
| 20:44 | <Krinkle> | Hixie: Hm.. it seems <link> have an own property of onload. I can't find it in the html spec though. |
| 20:44 | <Hixie> | every element has onload, that doesn't tell you much |
| 20:44 | <Krinkle> | If that works, that is amazing. That's the most mundane feature I've wanted to exist for years suddenly realising its existance. |
| 20:44 | <Hixie> | what you should look for is whether a 'load' event gets fired at the link element |
| 20:44 | <Hixie> | and i'm pretty sure we added that a few years ago |
| 20:45 | <Hixie> | could be wrong... |
| 20:45 | <Krinkle> | The number of hacks around this are crazy. This is the first I heard of a load event for stylesheets. |
| 20:45 | <Krinkle> | It makes perfect sense, but it's evaded me so far. |
| 21:13 | <Ms2ger> | Write some tests :) |
| 21:30 | smaug____ | wonders if there is some comparison how different open source projects do code reviews |
| 21:31 | <jgraham> | smaug____: Write Reviewers at Work |
| 21:38 | <annevk> | gsnedders: perhaps one of https://dump.testsuite.org/2006/xml/ is a problem? |
| 21:55 | <hober> | MikeSmith: hahahah, I sent that tweet. And the reply. :) |
| 21:58 | <tantek> | hober, you tweeting with yourself again? |
| 21:58 | <hober> | tantek: :) |
| 22:47 | <jsbell> | wanderview: sorry, was mtging. We have no explicit plans; de-duping definitely makes sense. No idea what the priority of that will be |
| 23:33 | <MikeSmith> | hober is emacs! |
| 23:33 | <MikeSmith> | emacs has finally taken on full human form, as so many people had predicted it would evolve to |
| 23:34 | <MikeSmith> | it bega when TV Raman created emacs-speak |
| 23:34 | <MikeSmith> | then somebody along the way must have added emacs-walk |
| 23:35 | <tantek> | does emacs-speak support the blade runner photo browsing commands? http://www.criticalcommons.org/Members/ironman28/clips/bladeRunner3DphotoH264.mov/view |
| 23:35 | <MikeSmith> | maybe hober added emacs-walk himselfーhe emacs-bootstrapped himself into humanness |
| 23:36 | <tantek> | can't spell emacs without "mac", figures it'd be someone from Apple |
| 23:38 | <MikeSmith> | tantek: emacs can do that photo browsing thingーit's really just hober in there pulling levers and stuff, like wizard of oz |
| 23:38 | <MikeSmith> | emacs say, Pay no attention to the human behind that curtain! |
| 23:39 | <MikeSmith> | haha https://twitter.com/emacs/status/573265792118071296 |
| 23:39 | <tantek> | no one tell Stallman that emacs is masquerading on a closed source silo |
| 23:39 | <MikeSmith> | I'm a vim user but it looks like I'm at risk of getting assimiliated into the collective |
| 23:40 | <MikeSmith> | tantek: blasphemy |
| 23:40 | <MikeSmith> | prepared to be struck by emacs-lightning |
| 23:46 | <MikeSmith> | in other news I seem to be getting this "Waiting for available socket" thing in Chrome only for www.w3.org URLs |