| 04:40 | <kilua17> | anyone there?? |
| 09:16 | <Taggnostr> | is there a CSS3 validator? |
| 09:18 | <Taggnostr> | now I found it in the option before the validation, but it would be better to provide a way to change the version in the result page, or try CSS3 validation when CSS2 validation fails (if that makes sense) |
| 09:19 | <Taggnostr> | (is a valid CSS2 page always valid CSS3 too?) |
| 10:06 | <estellevw> | Taggnostr: Louis wrote a piece on it: http://www.impressivewebs.com/css3-validation/ |
| 10:06 | <estellevw> | basically, use the validator with these steps: Change the “Profile” to “CSS Level 3″ |
| 10:06 | <estellevw> | Change the “Warnings” to “No warnings” or “Most important” |
| 10:06 | <estellevw> | Change the “Vendor extensions” to “Warnings” |
| 10:07 | <estellevw> | http://jigsaw.w3.org/css-validator/#validate_by_uri+with_options |
| 10:08 | <Taggnostr> | vendor extensions is another thing that sometimes annoys me, but in this specific instance I saw 8 errors and when I went to check they were about :last-child |
| 10:09 | <Taggnostr> | couldn't the validator use CSS3 by default? I usually get directly to the validation page without going through the page you linked |
| 10:12 | <Taggnostr> | estellevw, thanks for the link though, I think I might just tweak the tools I'm using to use css3 by default in the meanwhile |
| 10:40 | <Ms2ger> | "you may have questions regarding recent W3C |
| 10:40 | <Ms2ger> | developments, including |
| 10:40 | <Ms2ger> | XHTML 1.0 |
| 10:40 | <Ms2ger> | http://www.w3.org/TR/xhtml1"; |
| 10:43 | <estellevw> | the date on that is 2002 |
| 10:55 | <Ms2ger> | Anne, could you redeploy web-apps-tracker to fix the bug numbers? |
| 11:04 | <annevk> | Ms2ger: can you also make sure it always outputs https URLs? |
| 11:06 | <annevk> | Ms2ger: I can do it too I suppose |
| 11:16 | <annevk> | I can, but apparently cannot commit it back from the server ... |
| 11:16 | <annevk> | maybe once foolip is around he can sort that out |
| 11:18 | Ms2ger | looks |
| 11:19 | <annevk> | html5.org is updated |
| 11:19 | <annevk> | I also have this in my copy: |
| 11:19 | <annevk> | + elif line.startswith("Affected topics:"): |
| 11:19 | <annevk> | + pass |
| 11:20 | <annevk> | as well as |
| 11:20 | <annevk> | - bug = "<a href=\"http://www.w3.org/Bugs/Public/show_bug.cgi?id="; + revChanges["bug"] + "\">" + revChanges["bug"] + "</a>" |
| 11:20 | <annevk> | + bug = "<a href=\"https://www.w3.org/Bugs/Public/show_bug.cgi?id="; + revChanges["bug"] + "\">" + revChanges["bug"] + "</a>" |
| 11:20 | <annevk> | but no way to commit it :/ |
| 11:23 | <Ms2ger> | Committed both of those |
| 11:28 | <annevk> | cheers |
| 11:30 | <annevk> | hmm feedback on File API draft resulted in discussion on method parameters without topic change... |
| 11:30 | annevk | reviews readAsTExt |
| 11:42 | <annevk> | I forgot to quote the last part of Arun's email: "Feel free to respond to public-webapps" |
| 11:49 | <annevk> | how did StreamBuilder even end up getting introduced? |
| 11:49 | <annevk> | seems like it was introduced post the BlobBuilder fiasco |
| 11:57 | <Ms2ger> | Microsoft? |
| 11:57 | <annevk> | Ms2ger: for http://html5.org/specs/dom-parsing.html the URL should be about:blank, which is the initial value |
| 11:58 | <annevk> | Ms2ger: it should not be null in particular |
| 11:58 | <Ms2ger> | It was null in Chrome/Opera, I believe |
| 11:58 | <annevk> | yeah, but we want to align with Gecko |
| 11:58 | <annevk> | so it's always a valid URL |
| 11:58 | <mhausenblas> | hey annevk, got a sec? |
| 11:59 | <annevk> | mhausenblas: I saw your query yesterday, what are unanswered questions? sounds like they should go to a mailing list |
| 11:59 | <Ms2ger> | Well, Gecko had the URL of the page |
| 12:00 | <annevk> | ugh |
| 12:00 | <mhausenblas> | more like deployment issues and sorta 'is this gonna happen? stable?' - I always point them in your direction, annevk :P |
| 12:00 | <Ms2ger> | Fun, isn't it? :) |
| 12:01 | <annevk> | mhausenblas: I see |
| 12:01 | <annevk> | Ms2ger: I think we can still get them all to align on the about:blank thingie... |
| 12:01 | <mhausenblas> | I try to gather and address the stuff at enable-cors.org anyways, but I was thinking more of a sort of statement, like 'yes, it's safe to use it. it's stable, etc.' |
| 12:02 | <Ms2ger> | That works for me too |
| 12:02 | <mhausenblas> | anyways, looks like you're busy - lemme know if you wanna do something about it, annevk, yes? |
| 12:02 | <Ms2ger> | File a bug, please? I need to go now. |
| 12:02 | <annevk> | Ms2ger: k, btw, when you create an error document is content type still the original content type? |
| 12:02 | <annevk> | mhausenblas: what do you want to do about it? |
| 12:03 | <annevk> | mhausenblas: isn't stackoverflow there to help people out? |
| 12:03 | <mhausenblas> | hmmm, good question - dunno, maybe a screen cast |
| 12:03 | <Ms2ger> | Yes |
| 12:03 | <mhausenblas> | yeah, sure |
| 12:03 | <mhausenblas> | I think more along the advocacy line |
| 12:04 | <annevk> | mhausenblas: we can try a screencast for sure |
| 12:04 | <annevk> | been a while since I did something like that |
| 12:04 | <mhausenblas> | of course, providing the solutions is also a goal of enable-cors.org but advocacy is still important |
| 12:05 | <mhausenblas> | right. now, we could do it sort of interview style - I can prep some questions and the via G+ hangout, as you, etc |
| 12:06 | <mhausenblas> | I didn't really think hard about it, but something to reassure people that CORS is the right thing to do, and it's easy and safe to use, etc |
| 12:06 | <mhausenblas> | s/and the via G+ hangout, as you, etc/and then via G+ hangout, ask you, etc |
| 12:07 | <annevk> | sure okay |
| 12:07 | <mhausenblas> | OMG, still a bit hangover-ish from yesterdays Scotch night, sry |
| 12:07 | <annevk> | haha |
| 12:07 | <mhausenblas> | don't laugh so loud, my brain hurts :P |
| 12:07 | <mhausenblas> | right, so I might pop you some questions via mail and then we take it from there, annevk, yes? |
| 12:08 | <mhausenblas> | to annevk AT opera DOT com - or? |
| 12:09 | <annevk> | sure |
| 12:09 | <annevk> | and yes, that email works |
| 12:09 | <mhausenblas> | cool. cya & have a nice one ... |
| 12:12 | <annevk> | you too man, I recommend fruit and maybe a beer ;) |
| 12:12 | <mhausenblas> | fruit++ - beer, dunno, wife looks suspicious and kids somehow demand a sober dad on Sunday ;) |
| 12:25 | <hsivonen> | sigh. the wikipedia page on xhr is out of date but the policies are against me fixing it. https://en.wikipedia.org/wiki/Talk:XMLHttpRequest#Neither_limited_to_XML_nor_HTTP |
| 12:26 | <wilhelm_> | Write something on the discussion page. |
| 12:26 | <annevk> | prolly the wrong channel for lobbying for such changes :) |
| 12:26 | <annevk> | that's what he did |
| 12:28 | <wilhelm_> | I can't read, apparently. |
| 12:32 | <bga> | inkscape so slow :( |
| 13:01 | <mhausenblas> | hsivonen re editing https://en.wikipedia.org/wiki/XMLHttpRequest - I think you have some very valid points there |
| 13:02 | mhausenblas | folding in the edits now |
| 13:03 | mhausenblas | forgot how painful Wikipedia editing got ;) |
| 13:05 | <annevk> | oh yes |
| 13:05 | <annevk> | inbox <400 |
| 13:05 | <annevk> | I wonder if I was at less than 300 before I left... |
| 13:06 | <mhausenblas> | :) |
| 13:16 | <mhausenblas> | ok, hsivonen - pls have a look at https://en.wikipedia.org/wiki/XMLHttpRequest and lemme know if the edits are fine ... |
| 13:23 | <mhausenblas> | and now for something completely different. to the tunes of 'especially for you', annevk - https://plus.google.com/u/0/102497386507936526460/posts/gYquiyQ7xXj |
| 13:23 | <annevk> | lol |
| 13:23 | <annevk> | how do I attribute you on twitter for that? |
| 13:23 | <annevk> | ah |
| 13:24 | <mhausenblas> | no worries, just provide link to G+ post, should work |
| 13:25 | <mhausenblas> | tx, bro ;) |
| 13:58 | <annevk> | Philip`: can you maybe weigh in on https://bugzilla.mozilla.org/show_bug.cgi?id=470523 ? encoding support for iso-2022-cn |
| 13:59 | <annevk> | Philip`: see my comment (7) |
| 14:03 | <Philip`> | annevk: http://code.google.com/p/chromium/issues/detail?id=21354 seems to be the reasoning for Chrome's implementation |
| 14:04 | <Philip`> | annevk: I'm not sure what kind of weighing in would be useful |
| 14:08 | <annevk> | thanks |
| 14:08 | <annevk> | I'll just add a pointer to that discussion |
| 14:10 | <zewt_> | bugzilla needs to stop with the useless "comment collision" silliness |
| 14:11 | <annevk> | seems better to just have a simplistic decoder and encoder to me |
| 14:11 | <smaug____> | zewt: file a bug |
| 14:12 | <smaug____> | zewt: though, I'm pretty sure there is a bug file filed already |
| 14:12 | <annevk> | I don't like that people file ACTIONS on me to fix a spec bug |
| 14:12 | <annevk> | e.g. https://www.w3.org/2011/webappsec/track/actions/46 |
| 14:12 | <annevk> | no way to add a comment |
| 14:12 | <annevk> | meh |
| 14:17 | <smaug____> | timeless could just fix some bugs https://bugzilla.mozilla.org/show_bug.cgi?id=303738 |
| 14:59 | <zewt> | annevk: might be |
| 15:04 | <nueva> | is there any easy way in Python's html5lib to not convert HTML entities from input stream into unicode characters? |
| 15:05 | <nueva> | i want just sanitize input stream but leave HTML entities as-is |
| 15:06 | <Philip`> | nueva: Would it be acceptable if it converted Unicode characters back into entities when re-serializing the stream? |
| 15:06 | <nueva> | yes |
| 15:07 | <gsnedders> | You can just use encoding="ascii" and then it'll encode everything that's not ASCII |
| 15:13 | <nueva> | ok it works, thanks. but my input stream is in utf-8 and i want it to stay as-is and not in form of HTML entities for every character. is there any another way? |
| 16:08 | <annevk> | working in the weekend is nice |
| 16:08 | <annevk> | the only email you get is your own |
| 16:08 | <annevk> | inbox <350 |
| 19:56 | <charlvn> | http://tools.ietf.org/html/draft-pbryan-http-json-resource-01 |
| 20:03 | <mhausenblas> | tx charlvn for spotting the ID |
| 20:04 | <mhausenblas> | great, now we have three contenders in this space |
| 20:04 | <mhausenblas> | OData/JSON, Object Network and this one |
| 20:07 | <charlvn> | this one seems to be purely for JSON+REST, i think the scope of the others might be a little more specific? |
| 20:09 | <mhausenblas> | charlvn, oh, let's not go down the REST route ;) |
| 20:10 | <mhausenblas> | OData is APP with a JSON serialisation and ON is too new to tell, really |
| 20:10 | <mhausenblas> | but good to see competition in this area, really |
| 20:10 | <charlvn> | sorry, HTTP :) |
| 20:10 | <charlvn> | but yeah |
| 20:11 | <mhausenblas> | OData, though backed by MS and what seems to be a big community is too hefty for my taste |
| 20:11 | <mhausenblas> | he he |
| 20:11 | <mhausenblas> | 'A Convention for HTTP Access to JSON Resources' sounds also humble enough to me ;) |
| 20:12 | <mhausenblas> | charlvn, do you know the Editor ( Paul C. Bryan)? |
| 20:13 | <charlvn> | nope can't say i do |
| 20:13 | <mhausenblas> | righto |
| 20:13 | <mhausenblas> | seems there is a bit of a CouchDB influence there (see ack section) |
| 20:16 | <mhausenblas> | time for a blog post about this topic. TTYL, charlvn and tx again for great spotting! |
| 20:17 | <charlvn> | np :) |
| 20:21 | mhausenblas | will credit you, of course, charlvn - any preferred handle? twitter? |
| 20:23 | <mhausenblas> | BTW, hsivonen, seems the Wikipedia policy hasn't figured my today's edits (yet) ... https://en.wikipedia.org/w/index.php?title=XMLHttpRequest&action=history |
| 20:23 | <mhausenblas> | s/policy/police |
| 20:26 | <charlvn> | mhausenblas: nah not at all, my full name is "Charl van Niekerk" |
| 20:26 | <mhausenblas> | k |
| 20:27 | mhausenblas | will paste the URL of blog post here later on in case you wanna follow-up on it ;) |
| 21:20 | <mhausenblas> | charlvn, see http://webofdata.wordpress.com/2012/02/05/json-http-data-links/ |
| 21:20 | <charlvn> | cool, thanks! |
| 21:26 | <mhausenblas> | yw |