| 03:31 | <karlcow> | MikeSmith: I guess it is not Anne's version https://dvcs.w3.org/hg/url/raw-file/tip/Overview.html |
| 03:31 | <karlcow> | ah found http://url.spec.whatwg.org/ |
| 05:00 | <Hixie> | what should 1.2a3.4a5.6 be treated like? |
| 05:00 | <Hixie> | 1,2,3,4,5,6 and some strings? 1.2,3.4,5.6 and some strings? 1.2,3,4,5,6 and some strings? |
| 07:07 | <MikeSmith> | Hixie: I guess 1.2,3.4,5.6 would seem like the most intuitive |
| 07:07 | <MikeSmith> | unsurprising |
| 09:22 | <jgraham> | Argh. Where is zcorpan when you need him? |
| 09:24 | <jgraham> | gsnedders: yt? |
| 09:37 | <annevk5> | smaug____: so we have moz-blob which is incremental... |
| 09:45 | <smaug____> | yes |
| 09:45 | <smaug____> | which is why it is very different to the new proposal |
| 09:51 | <annevk> | I don't follow |
| 09:52 | <annevk> | smaug____: how is it different? |
| 09:53 | <smaug____> | oh, wait, you say incremental as latter Blobs containing all the data |
| 09:53 | <smaug____> | from the beginning |
| 09:53 | <annevk> | all I meant was available during LOADING |
| 09:54 | <smaug____> | sorry, I was thinking about the chunked thing |
| 09:54 | smaug____ | checks who added moz-blob |
| 09:54 | <smaug____> | sounds like sicking-ish thing |
| 09:54 | <annevk> | yes |
| 10:01 | <smaug____> | I guess I need to change my mind |
| 10:02 | <smaug____> | the .iso usecase is quite valid one |
| 10:05 | <annevk> | smaug____: so we do the semantics we discussed yesterday? |
| 10:05 | <smaug____> | yeah |
| 10:05 | <smaug____> | but then, if we get incremental blobs and typedarrays, shouldn't we have partial data to |
| 10:05 | <smaug____> | I mean chunked data |
| 10:06 | <smaug____> | what was the original bug report |
| 10:06 | <smaug____> | w3c bug report |
| 10:06 | <smaug____> | is it about incremental or chunked |
| 10:06 | <annevk> | https://www.w3.org/Bugs/Public/show_bug.cgi?id=21111 is for blob/arraybuffer during LOADING |
| 10:07 | <annevk> | The discussion about chunked resulted in the addition of stream |
| 10:07 | <annevk> | That discussion was mailing-list only |
| 10:07 | <smaug____> | so |
| 10:07 | <smaug____> | with incremental we're getting close to a stream like anyway |
| 10:08 | <annevk> | I'll ask why Stream is no good. |
| 10:10 | <smaug____> | because it is not implemented ? |
| 10:10 | <smaug____> | but really, incremental and chunked are so close to each others |
| 10:10 | <smaug____> | scripts can use incremental as chunked |
| 10:11 | <smaug____> | but memory usage would be just higher that way |
| 10:11 | <smaug____> | in some cases |
| 10:12 | <annevk> | smaug____: neither is blob during LOADING in WebKit... |
| 10:12 | <annevk> | smaug____: or in Gecko for the keyword "blob" |
| 10:12 | <annevk> | smaug____: and the Streams API is about incremental the way it is currently set up |
| 10:13 | <smaug____> | how is Stream better? |
| 10:13 | <smaug____> | (other than better name) |
| 10:13 | <annevk> | It's an object that incrementally expands and does not have a fixed .size |
| 10:14 | <smaug____> | eh |
| 10:14 | <annevk> | Arguably Blob should have been designed that way... |
| 10:14 | smaug____ | re-reads the spec |
| 10:15 | <annevk> | I wonder how Streams API got published including StreamBuilder :-( |
| 10:15 | <smaug____> | I meant s/Stream/Stream API/ |
| 10:15 | <smaug____> | so yes, are we talking about Stream interface or API |
| 10:16 | <annevk> | Stream is defined in the Streams API |
| 10:16 | <smaug____> | since I asked about API, but I guess you're talking about the interface |
| 10:16 | <annevk> | There's not much more to the spec... |
| 10:18 | <smaug____> | so, you'd get Stream from XHR , and then read it separate ? |
| 10:19 | <smaug____> | separately |
| 10:19 | <smaug____> | and not care about XHR |
| 10:19 | <annevk> | That's the same with Blob |
| 10:21 | <annevk> | I'm not entirely sure StreamReader has the correct design though :-( |
| 10:23 | <Ms2ger`> | Sounds like a good web API, then |
| 10:23 | <smaug____> | does it allow incremental and chunked... |
| 10:23 | <smaug____> | I don't quite see that |
| 10:24 | <annevk> | I think only incremental |
| 10:28 | <smaug____> | well, then adding something similar to moz-blob to XHR wouldn't make sense |
| 10:29 | <smaug____> | I would expect an API called Stream to deal with chunked data |
| 10:30 | <annevk> | Could we design it to handle both? |
| 10:31 | <smaug____> | well, what if there are two StreamReaders. First one reading chunked data, and then another reading incremental |
| 10:31 | <smaug____> | the latter would like to get all the data since the beginning |
| 10:32 | <smaug____> | but I'd like to be able to discard the already read data |
| 10:32 | <smaug____> | (that is a reason for moz-chunked-* in XHR) |
| 10:32 | <annevk> | I understand |
| 10:33 | <smaug____> | back in few minutes |
| 10:34 | <annevk> | smaug____: one question, does moz-blob create a new Blob object each time you access it? |
| 10:35 | <annevk> | I'll draft an email to public-webapps to sort this out |
| 10:49 | <annevk> | Oh smaug just left. How rude. Well I figured it out via testing anyway |
| 10:51 | <smaug____> | annevk: looks like moz-blob does not create a new object each time |
| 10:51 | <smaug____> | only if there is some new data |
| 10:51 | <annevk> | ah good to know |
| 10:51 | <smaug____> | and sorry being so rude :) |
| 10:52 | <smaug____> | so, will we need Stream and IncrementalStream. Though the latter sounds odd. It is more like IncrementalBlob |
| 10:56 | <annevk> | smaug____: oh, I reached the opposite conclusion :-) |
| 10:56 | <annevk> | smaug____: see public-webapps |
| 10:58 | <smaug____> | it wasn't really my conclusion :) |
| 10:58 | <annevk> | smaug____: given that an incremental Blob can be done via masquerade, all the additional API complexity of Stream does not seem worth it |
| 10:58 | <smaug____> | helsinki.fi, could you be a bit faster today |
| 10:58 | <smaug____> | ah |
| 10:59 | <annevk> | Hmm strange. Feras Moussa is listed as Invited Expert. Is he no longer at Microsoft? |
| 11:00 | <smaug____> | as of now, I'd like to have incremental and chunked in XHR |
| 11:00 | <smaug____> | but need to get more comments |
| 11:01 | <smaug____> | since I thought Stream was about chunked data |
| 11:01 | <smaug____> | but the spec doesn't say that |
| 11:01 | <smaug____> | or I can't find it |
| 11:01 | <smaug____> | s/Stream/StreamReader/ |
| 11:02 | <MikeSmith> | annevk: Feras is no longer at Microsoft. But he intends to continue editing the Streams spec |
| 11:02 | <annevk> | smaug____: the API does not look like it's chunked, although maxSize does suggest that I suppose... |
| 11:02 | <annevk> | MikeSmith: I see |
| 11:12 | <gsnedders> | jgraham: Here now |
| 11:12 | <jgraham> | gsnedders: I was looking for Opera's postMessage tests |
| 11:12 | <jgraham> | But I found them |
| 11:13 | <jgraham> | They all need conversion though :( |
| 11:13 | <gsnedders> | Okay. I don't where to look anyway. :) |
| 11:14 | <jgraham> | It seems we are going to do that farcical thing where we ask Microsoft "are your tests good enough to take this spec forward?" And they say "yes of course they are, after all we pass them all". |
| 11:14 | <jgraham> | For messaging as well as web sockets |
| 11:14 | <gsnedders> | What about zcorpan's web sockets tests? |
| 11:15 | <jgraham> | gsnedders: They are still partially unconverted to testharness format |
| 11:16 | <jgraham> | I guess this is what I need to spend my evenings doing |
| 11:17 | <jgraham> | Rather than working on critic |
| 11:44 | <marcosc> | The JSON spec says that JSON text shall be Unicode (i.e., UTF-8 to 32). Chrome fails to parse UTF-16, big endian, no BOM. OTOH, FireFox refuse to parse any UTF-16, except UTF-16-LE with no BOM. Have not tested UTF-32. |
| 11:44 | <annevk> | marcosc: parse where? |
| 11:44 | <marcosc> | annevk: JSON.parse() |
| 11:45 | <annevk> | marcosc: that takes a JavaScript string |
| 11:45 | <marcosc> | ah |
| 11:45 | <annevk> | XMLHttpRequest only supports JSON encoded as utf-8 |
| 11:46 | <marcosc> | annevk: I'm pulling in the JSON text through XHR |
| 11:46 | <annevk> | marcosc: it's already decoded at that point depending your server configuration and the specifics of how you're using XMLHttpRequest... |
| 12:01 | <marcosc> | annevk: in the XHR, when open() is called, what's the reason for dropping the <fragment> component from the URL? |
| 12:01 | <annevk> | marcosc: that's how HTTP works |
| 12:02 | <annevk> | marcosc: sounds like you're not reading http://xhr.spec.whatwg.org/ though which is much better |
| 12:02 | <annevk> | marcosc: and defers for that particular thing to Fetch |
| 12:02 | <marcosc> | ah! I'm not |
| 12:02 | <annevk> | (which I'm trying to work out now...) |
| 12:03 | <marcosc> | In the manifest spec, I really just want to say: behave as if performing an XHR open() request with URL set to bla, and method set to GET. |
| 12:04 | <marcosc> | Otherwise, I'm going to end up cloning a bunch of stuff from the XHR spec |
| 12:04 | <marcosc> | which sucks |
| 12:04 | <annevk> | marcosc: oh no, you want to use fetch |
| 12:04 | <marcosc> | fetch from HTML? |
| 12:04 | <annevk> | marcosc: yes |
| 12:04 | <marcosc> | ok |
| 12:05 | <annevk> | marcosc: until I've written Fetch and then everyone can use that |
| 12:05 | <annevk> | it will be glorious |
| 12:05 | <marcosc> | I can imagine! :) |
| 12:06 | <marcosc> | ok, so http://www.whatwg.org/specs/web-apps/current-work/#fetch is currently incomplete then. |
| 12:08 | marcosc | lunch |
| 12:16 | <annevk> | marcosc: nah it's complete, just not detailed (imo) |
| 12:16 | <annevk> | I wish Hixie was around |
| 12:34 | <odinho> | And not with a nice URL and its own easy hookpoint :] |
| 13:14 | <SteveF_> | marcosc: johnny kannis was probably before your time ;-) |
| 13:14 | <marcosc> | SteveF_: yep :) |
| 13:14 | <marcosc> | but I don't mind :) |
| 13:15 | <SteveF_> | marcosc: was following odd trains of thought and music while suffering from stomach cramps hitme were a great sydney pub rock band btw |
| 13:15 | <SteveF_> | hitmen |
| 13:16 | <SteveF_> | marcosc: wasn't meaning to make a wog connection... |
| 13:16 | <marcosc> | heh, now you have :) |
| 13:18 | marcosc | throws SteveF_ a rope out of the hole. Funky tunes: http://www.youtube.com/watch?v=TnjuGYU-gCA |
| 13:19 | SteveF_ | ;-) |
| 13:19 | marcosc | gets all in the mood for some bad 80's rock |
| 13:20 | SteveF_ | seeing them drinking longnecks in that vid really took me back |
| 13:23 | <marcosc> | me too, I was 12 again :) |
| 13:23 | SteveF_ | remember seeing the angels as an underager out in the western sydney beerbarns http://www.youtube.com/watch?v=RiOQzWTz3cM |
| 13:25 | <SteveF_> | marcosc: where did you live in oz? |
| 13:25 | <marcosc> | Brisbane |
| 13:26 | <SteveF_> | say no more |
| 13:29 | SteveF_ | I'm a bankstown boy myself |
| 13:31 | <jgraham> | Are we supposed to hum that to the tune of uptown girl? |
| 13:31 | <annevk> | Please record if you do |
| 13:34 | <annevk> | aaah |
| 13:34 | <smaug____> | does anyone actually use microdata thing |
| 13:34 | <annevk> | smaug____: you'd have to elaborate on thing |
| 13:34 | <annevk> | smaug____: but e.g. http://schema.org/ backed by the search engines recommends using it to people |
| 13:35 | <smaug____> | "recommends" does mean anyone actually uses it |
| 13:35 | <smaug____> | er |
| 13:35 | <smaug____> | doesn't |
| 13:35 | SteveF_ | context of 'bansktown boys boys don't cry' statement made by the honourable Paul Keating PM http://www.thepunch.com.au/articles/an-ode-to-paul-keating/ |
| 13:36 | <annevk> | smaug____: if nobody is using it I wish they'd stop discussing it |
| 13:36 | <SteveF_> | his observation of marcosc's buddy John Howard "What we have got is a dead carcass, swinging in the breeze, but nobody will cut it down to replace him. " |
| 13:37 | <marcosc> | Oh lolz, slightlyoff! The comments here are hilarious: https://github.com/slightlyoff/async-local-storage/blob/master/src/async-local-storage.js |
| 13:38 | <jgraham> | They might be funny |
| 13:39 | <jgraham> | But they are not all on-base |
| 13:39 | <jgraham> | I have no idea why .length implied "ordered" for example |
| 13:39 | <marcosc> | oh, they are spot on |
| 13:39 | <marcosc> | Just a little out of character for the oh ever so eloquent slightlyoff |
| 13:40 | <jgraham> | (certainly in python it doesn't) |
| 13:40 | <jgraham> | (where len(set([1,2,1])) == 2, just like you would expect) |
| 13:41 | <jgraham> | (and you can't index a set by number there either) |
| 13:41 | <jgraham> | (or indeed a dict, which *also* has a __len__) |
| 13:46 | <jgraham> | Also, navigator?? |
| 14:05 | <marcosc> | jgraham: yeah, navigator is that's a strange place to put that |
| 16:13 | <slightlyoff> | marcosc: dude, LS + IDB is enough to make anyone swear like a sailor |
| 16:38 | <annevk> | jgraham: I suggested navigator I think, where would you put it? |
| 16:43 | <marcosc> | slightlyoff: amen to that :) |
| 16:43 | <slightlyoff> | marcosc: i honestly don't understand transactions in IDB |
| 16:43 | <slightlyoff> | and I think I made a serious attempt to understand them |
| 16:43 | <slightlyoff> | I'm currently digging through chromium code to grok why FF and Chrome differ in timing/end-of-turn behavior |
| 16:43 | <zewt> | jgraham: yeah, "length", "count" and "size" mean exactly the same thing, and it's nonsensical to not use the same term for all data structures |
| 16:43 | <marcosc> | I haven't even gotten that far. I lost the plot and started swearing long even before getting the object store going |
| 16:43 | <slightlyoff> | not true |
| 16:44 | <slightlyoff> | zewt: length is a 1-dimensional measure |
| 16:44 | <slightlyoff> | it implies ordering |
| 16:44 | <zewt> | length does not imply ordering |
| 16:44 | <marcosc> | slightlyoff: I'm currently playing around with Q to get a better understanding of promises, so I can contribute a bit |
| 16:44 | <slightlyoff> | I will leave basic number theory as an exercise to the reader. |
| 16:44 | tantek | gets the popcorn and grabs a seat. |
| 16:45 | <zewt> | ... |
| 16:45 | <slightlyoff> | tantek: sorry man, have go to do real work...no time for this = ) |
| 16:45 | <zewt> | we're talking about "length" as a property of a data set, which has nothing to do with the length of a vector or a line in space |
| 16:45 | <tantek> | slightlyoff :) |
| 16:45 | <Ms2ger> | Clearly it should be "norm" |
| 16:45 | <slightlyoff> | tantek: but you know...if you think zewt isn't *just* a troll, I invite you to try |
| 16:45 | <jgraham> | "cardinality" |
| 16:46 | <jgraham> | slightlyoff: zewt isn't a troll |
| 16:46 | <zewt> | i don't care if it's "length" or "size" or "count" or "elephants", all i care is that it be the same term for all of arrays, maps, sets |
| 16:46 | <jgraham> | But you two rub each other up the wrong way something chronic |
| 16:46 | <karlcow> | love to hate |
| 16:46 | <tantek> | jgraham, you have to pay extra for that in SF. |
| 16:48 | <zewt> | (and since .length is what's already used by JS strings, it wins by default) |
| 16:48 | karlcow | is now diving into https://en.wikipedia.org/wiki/Countable_set |
| 16:49 | <annevk> | Map uses size |
| 16:49 | <zewt> | then map made a dumb mistake |
| 16:50 | <annevk> | zewt: it's not settled yet, you could argue it on es-discuss |
| 16:51 | <karlcow> | in my mind, `length` has a unit after it. When `count` does not have. |
| 16:51 | <jgraham> | karlcow: Then lenght is equally wrong for strings and arrays :) |
| 16:52 | <jgraham> | *length |
| 16:52 | <karlcow> | that said programming languages used mostly len() |
| 16:52 | <zewt> | karlcow: it sounds like you're thinking of "length" as a physical unit--that's simply a different concept of length |
| 16:52 | <annevk> | DOMTokenList uses .length |
| 16:52 | <karlcow> | zewt: Pardon my physics ;) that's my academic background. |
| 16:52 | <annevk> | but the tokens are ordered there iirc |
| 16:53 | karlcow | creates .howmany |
| 16:55 | <jgraham> | annevk: It would be super surprising if you had a Set and a SortedSet and they didn't implement the same API |
| 16:55 | <Ms2ger> | Sounds like something Java would do |
| 16:55 | <annevk> | jgraham: are you going to do something about it? |
| 16:56 | <zewt> | heh, also one of the sillier things C++'s STL does: it only exposes a method for something if it can be computed efficiently |
| 16:56 | <zewt> | so (iirc) you have .size on strings, but not linked lists; to get that you have to use a count method |
| 16:56 | <zewt> | which is the worst sort of academic API design |
| 16:57 | <jgraham> | annevk: By "do something" you mean "join es-discuss and argue about naming"? |
| 16:57 | <karlcow> | hmmm http://twitter.com/FakeOpvard/ |
| 16:57 | <annevk> | jgraham: yes |
| 16:58 | <annevk> | Also, Blob.size |
| 16:58 | <annevk> | ProgressEvent.total |
| 16:58 | <annevk> | We're all over the map already. |
| 16:59 | <karlcow> | sweet, all the million ways of counting |
| 17:01 | <jgraham> | annevk: I'm going with "I probably have more valuable things to do than argue with slightlyoff that he is making the platform harder to learn for no good reason" |
| 17:04 | <tantek> | count: more a verb (method) than a noun (property) "Let me count the ways…". length: physical 1-dimensional measure thus implying it depends on the thing you're measuring and how you're measuring it. size: could be arbitrary, but for some reason I associate strongly with "number of bytes this thing takes up in memory". |
| 17:04 | <annevk> | jgraham: pretty sure he doesn't follow es-discuss closely |
| 17:04 | <jgraham> | (I would argue that non-native speakers wouldn't get the slight semantic difference between "length" and "size", but since I am a native speaker and I have no idea where the idea that "length" implies "ordered" comes from, I don't think I even need that argument) |
| 17:05 | <jgraham> | (I can only imagine it comes from exposure to some other programming language (Java?) that makes that distinction) |
| 17:06 | <jgraham> | tantek: That "some reason" is presumably sizeof(t) |
| 17:06 | <zewt> | it smells like something taught by a well-intentioned college professor, then internalized and never properly questioned |
| 17:07 | <tantek> | we leave all the proper questioning to #whatwg naturally |
| 17:07 | <tantek> | jgraham - yes, that sounds right. from years of C(++) programming. |
| 17:08 | <zewt> | i have more years of C and C++ than any other language and I've never even heard of that distinction |
| 17:17 | <annevk> | Hixie: so, how is potential CORS fetch with "No CORS" different from fetch? |
| 17:18 | <karlcow> | jgraham: for size, I imagine volume, in my head. Maybe because of the French "taille". |
| 17:18 | <karlcow> | oh we didn't touch yet to quantity :p |
| 17:22 | <karlcow> | .vastness, .immensity, .magnitude if at least the naming could be more poetic |
| 17:24 | <dglazkov> | good morning, Whatwg! |
| 17:24 | <annevk> | karlcow: we don't want to make it worse |
| 17:24 | <annevk> | dglazkov: good afternoon |
| 17:25 | <annevk> | dglazkov: you used to hit tea time :p |
| 17:25 | <karlcow> | annevk: heh. But that would be more fun. :) |
| 17:25 | <annevk> | karlcow: only the perverse kind of fun, but I can see how that makes sense to you |
| 17:26 | <karlcow> | at least that would give "left to interpretation" a meaning. |
| 17:39 | <Hixie> | annevk: regular fetch doesn't label the thing as cross-origin |
| 17:53 | <annevk> | Hixie: sure, but is that a feature in some way? |
| 17:56 | <Hixie> | annevk: how do you mean? |
| 17:56 | <Hixie> | it's a feature for the spec, in that it needs to know for every <img> whether it's cors-same-origin or not |
| 17:56 | <annevk> | Hixie: is it a feature of "fetch" that you don't know the label? |
| 17:57 | <annevk> | Hixie: cause otherwise we could make it one algorithm |
| 17:58 | <annevk> | (might go offline for a minute or so, will read the minutes) |
| 17:58 | <annevk> | logs* |
| 18:01 | <odinho> | lol, minutes. |
| 18:01 | <odinho> | Too much W3C for you Anne. |
| 18:01 | <odinho> | Or formalized meetings I guess. |
| 18:07 | <Hixie> | annevk: well i don't really care how you implement it, so long as the API doesn't change :-) |
| 18:07 | <Hixie> | annevk: the key is that when calling this algorithm, i don't know what the mode is |
| 18:07 | <Hixie> | annevk: i just "Do a potentially CORS-enabled fetch of the resulting absolute URL, with the mode being the state of the element's crossorigin content attribute, the origin being the origin of the script element's Document, and the default origin behaviour set to taint" or similar |
| 18:08 | <Hixie> | annevk: and then that returns a resource that is "either CORS-same-origin or CORS-cross-origin" |
| 18:08 | <Hixie> | annevk: i think it would be confusing to have the regular fetch algorithm returning CORS states |
| 18:08 | <Hixie> | annevk: since every caller would ignore it |
| 18:09 | <annevk> | but I think at some point every caller will turn into a potential CORS-caller |
| 18:10 | <annevk> | but yeah, not knowing the CORS-mode makes sense, and we should have "No CORS" |
| 18:10 | <annevk> | I was just wondering whether there's a material difference between the two which I didn't see |
| 18:17 | <annevk> | Hixie: also see email about Anonymous mode |
| 18:19 | <annevk> | odinho: actually surprisingly few these days, WHATWG ftw |
| 18:19 | <Hixie> | how do you set Origin: to a unique origin? |
| 18:20 | <Hixie> | and does Referer: really gets set to about:blank? |
| 18:20 | <annevk> | Hixie: Origin: null |
| 18:20 | <annevk> | Hixie: I think that makes Referer omitted |
| 18:21 | <Hixie> | so wait, why isn't CORS just doing all this automatically when one sets the flag? |
| 18:28 | <zewt> | hmm, something that seems like it should be easy but i'm drawing a blank |
| 18:29 | <zewt> | i have some CSS drawing a thing (gradient background, rounded corners), used in one UI; i need to export that rendering (with alpha) to a PNG for use in a non-HTML element with similar styles |
| 18:30 | <annevk> | Hixie: XHR has both anonymous and without credentials |
| 18:30 | <annevk> | Hixie: anonymous is an extremer variant |
| 18:31 | <zewt> | bleh, guess it's easier to recreate it in photoshop than to figure out a way to do this |
| 18:31 | <Hixie> | annevk: confoosing |
| 18:31 | <Hixie> | annevk: why so many? |
| 18:31 | <annevk> | sorry, if I would design this now it'd be way different |
| 18:31 | <Hixie> | hehe |
| 18:31 | <Hixie> | i know that feeling |
| 18:31 | <Hixie> | bbiab |
| 18:32 | <annevk> | initially we just had withCredentials |
| 18:32 | <annevk> | and then people wanted a mode without Origin or Referer |
| 18:32 | <annevk> | without any identifying information |
| 18:32 | <annevk> | and they got enough backing from silly implementors |
| 18:32 | <odinho> | Silly! |
| 18:34 | Ms2ger | never designs anything for that reason |
| 18:34 | <annevk> | Ms2ger: was Text.serializeXXX not you? |
| 18:35 | <Ms2ger> | Never got implemented, did it? ;) |
| 18:36 | <annevk> | Ms2ger: "never designs" is clearly false though |
| 18:43 | <TabAtkins> | zewt: That's what screenshots are for. |
| 18:54 | <zewt> | no alpha |
| 18:54 | <TabAtkins> | Ah, that's true. Darn. |
| 18:54 | <TabAtkins> | No way, then, since you can't draw DOM into <canvas> yet. |
| 20:40 | <JonathanNeal> | hello |
| 21:00 | <rillian> | howdy |
| 21:02 | <JonathanNeal> | So, how does <template> get around not having any logic, say for if statements or loops? |
| 21:04 | <TabAtkins> | JonathanNeal: It has loops. I think we have a way to avoid generating things, as well, which is basically an if. |
| 21:04 | <TabAtkins> | (Don't know if that's in the current revision of the spec.) |
| 21:08 | <JonathanNeal> | Is there a draft of the spec that you think might address these things? |
| 21:13 | <jamesr> | anyone have a good readymade rant about linking to /TR/ ? |
| 21:13 | <jamesr> | JonathanNeal, https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html |
| 21:13 | <Hixie> | jamesr: "it's out of date" |
| 21:14 | <jamesr> | JonathanNeal, that's pretty heavy on technical detail and light on explanations it seems |
| 21:15 | <JonathanNeal> | Yea, I'm trying to extrapolate an example. |
| 21:16 | <JonathanNeal> | > Just after the step labeled "Loop" in the algorithm to reset the insertion mode appropriately, add the following step: If node is a template element, then switch the insertion mode to the current template insertion mode and abort these steps. Modify the step which begins "If node is a head element..." to be … |
| 21:48 | <JonathanNeal> | https://twitter.com/jon_neal/status/306521507784445952 |
| 21:49 | <JonathanNeal> | IE10 is out for Windows 7. |
| 22:07 | <ronaldmansveld> | Does any of you happen to have experience with the w3c community groups? |
| 22:08 | <ronaldmansveld> | As in: has any of you been part of one? |
| 22:13 | <jgraham> | Yes |
| 22:16 | <ronaldmansveld> | jgraham, what I take from it, these groups create reports that may or may not be used by the w3c to use as the foundation for a working draft, right? So it's like the very first stage of creating specs |
| 22:17 | <TabAtkins> | ronaldmansveld: Basically, yes. They're not WGs, so can't produce specs themselves, but it gives a nice gathering-place for interested parties to hash out early ideas into something presentable. |
| 22:18 | <ronaldmansveld> | jgraham, and secondly, how do these groups work, cause for what I can see some have been created, have contributors, but seem to be doing nothing for like a year |
| 22:18 | <ronaldmansveld> | TabAtkins, thanks :) That was basically my idea of what they would be doing |
| 22:37 | <jgraham> | ronaldmansveld: Well it's not really clear that they work :) |
| 22:37 | <jgraham> | Creating a group is easy |
| 22:38 | <jgraham> | Creating a critical mass of interested, and relevant, parties actually working on a problem in a meaningful way is hard |
| 22:38 | <jgraham> | e.g. if you want to suggest something new for browsers you really want browser vendors on board |
| 22:39 | <jgraham> | So you are much better off using WHATWG since they are already there |
| 22:39 | <ronaldmansveld> | hmm, i see |
| 22:39 | <ronaldmansveld> | cause in this case there's one group I'm interested in working with, since it touches what I deal with on a daily base |
| 22:40 | <ronaldmansveld> | but it seems like nothing happened since they started almost a year ago |
| 22:40 | <jgraham> | Which group? |
| 22:41 | <ronaldmansveld> | multilingual web site |
| 22:41 | <ronaldmansveld> | http://www.w3.org/community/mws/ |
| 22:46 | <jgraham> | Well the good news is that's nothing browser related |
| 22:46 | <jgraham> | So I guess just try sending mail to the group list and see if you can get some momentum going? |
| 22:47 | <ronaldmansveld> | I'll wait for my application to come through, and then I will, thanks :) |
| 22:47 | <ronaldmansveld> | (and even though the start-up document does mention browser-related changes, I disagree with that, but that's something to discuss with the group) |
| 23:23 | <JonathanNeal> | All web developers should rejoice! https://twitter.com/jon_neal/status/306544841641308160 Automatic updates in IE10 are enabled by default on first run http://i.imgur.com/j5jFjUa.png |
| 23:46 | <TabAtkins> | \o/ |
