| 01:43 | <annevk> | +1 to HTML |
| 01:44 | <annevk> | I had a note for my blogpost anyway on how we already call it that |
| 01:44 | <annevk> | if we actually call it that it might make more sense :) |
| 01:51 | <Hixie> | hehe |
| 01:51 | <Hixie> | (reminder for those not reading backlog: i'm planning on doing s/HTML5/HTML/ on the http://whatwg.org/html spec tomorrow unless someone raises an issue on this.) |
| 01:51 | <Hixie> | (someone other than TabAtkins) |
| 02:13 | <annevk> | wait what |
| 02:13 | <annevk> | WAI-ARIA became CR?! |
| 02:13 | <annevk> | I would love to see the disposition of comments |
| 02:13 | <annevk> | sounds like SVG all over again |
| 02:17 | annevk | -> sleep |
| 02:19 | <paul_irish> | Hixie: I thought the 5 was being retained to help people searching for the spec. |
| 02:20 | <Hixie> | it was being retained to help with advocacy |
| 02:21 | <Hixie> | but now that the w3c has basically jumped onto the bandwagon of using "html5" as the new "ajax", it's not clear that anyone searching for "html5" is looking for the spec |
| 02:21 | <Hixie> | and anyway, "html5" on google doesn't get you the whatwg spec on the first page |
| 02:21 | <erlehmann> | Next up: The W3C ursurps the term “HTML” … oh wait. |
| 02:25 | <paul_irish> | Hixie: i see. Will http://developers.whatwg.org be able to retain "html5" ? |
| 02:25 | <Hixie> | that's up to ben |
| 02:25 | <paul_irish> | okay. i just pinged him. sounds good. |
| 03:24 | <hober> | Hixie: valentine's day |
| 03:24 | <hober> | Hixie: but yeah, I enjoyed the non-response |
| 03:28 | <hober> | also, +1 to s/5// |
| 03:30 | <othermaciej> | <small>i like the 5</small> |
| 03:33 | <MikeSmith> | http://es5.github.com/ |
| 03:33 | <MikeSmith> | (moved from sideshowbarker.github.com/es5-spec/) |
| 03:34 | <MikeSmith> | I added markers that link to the MDC JavaScript Reference and MDC JavaScript Guide |
| 03:35 | <MikeSmith> | also added ones that link to Dmitry Soshnikov's article series |
| 04:31 | <karlcow> | es5.github.com just crashed my browser |
| 04:31 | gsnedders | wonders about changing the tree-walker API again to use a dict of (namespace, localName) tuple to value instead of the current list of dicts… |
| 04:48 | <Hixie> | othermaciej: correct me if i'm wrong, but it's more the versioning you like, right? not the 5 per se. We've already dropped the versioning. |
| 05:05 | <MikeSmith> | karlcow: I noticed some serious performance issues with viewing it Opera |
| 05:06 | <MikeSmith> | almost certainly due to me probably doing something really dumb in the JS code that generates the annotations |
| 05:07 | <MikeSmith> | but not crashes |
| 05:07 | <MikeSmith> | on my machine, I mean |
| 05:08 | <MikeSmith> | mostly just seems to talk a really long time to load -- scrolling slows/locks for a long time |
| 05:09 | <MikeSmith> | but then it seems to finish doing whatever and I can scroll fine and all after that |
| 05:11 | <gsnedders> | Reflowing during script execution when it adds the annotations? |
| 05:11 | <MikeSmith> | suppose so |
| 05:13 | <MikeSmith> | it's a big document a gazillion of those annotation markers |
| 05:29 | <cutepy> | hi i have a project to create an online document viewer. I plan to convert pdf documents to html for showing the documents. |
| 05:29 | <cutepy> | does anyone have any idea of how to program this |
| 06:32 | <Hixie> | (note for those not reading backlog: i'm planning on doing s/HTML5/HTML/ on the http://whatwg.org/html spec tomorrow unless someone raises an issue on this.) |
| 06:58 | <othermaciej> | Hixie: nah, I like HTML5 as a buzzword |
| 06:58 | <othermaciej> | Hixie: but I also don't care a huge amount what the draft says |
| 07:55 | <Hixie> | othermaciej: well as a buzz word it means far more than what the spec means, according to w3c |
| 07:55 | <Hixie> | othermaciej: so the buzzword is not a useful label for the spec :-) |
| 08:01 | <Hixie> | if anyone cares about prefixes in rdfa, here's my CP: http://wiki.whatwg.org/wiki/Change_Proposal_for_ISSUE-120 |
| 08:02 | <Hixie> | i'll submit it tomorrow so if anyone has any feedback on it, either edit the CP directly or let me know here |
| 08:36 | <zcorpan> | wow is http://www.w3.org/TR/2011/CR-wai-aria-20110118/appendices#xhtml_dtd confused or what |
| 08:39 | <annevk> | http://antimatter15.com/wp/2011/01/the-ambiguity-of-open-and-vp8-vs-h-264/ is a pretty good article |
| 08:41 | <annevk> | they spell HTML5 with a space |
| 08:42 | <annevk> | and link to an ancient draft directly rather than via the references section? |
| 08:42 | <paul_irish> | gross. |
| 08:42 | <paul_irish> | also annevk, not that it should matter but antimatter is actually 15 years old. |
| 08:42 | <annevk> | smart kid then |
| 08:45 | <erlehmann> | the working draft podcast really nailed it with their stylesheet :D http://workingdraft.de/10/ |
| 08:47 | <annevk> | haha |
| 08:49 | <annevk> | waiting for someone to create the interrobang version now |
| 08:53 | <erlehmann> | annevk, only question is: which color? let me see … |
| 08:54 | <annevk> | html5.org uses pink |
| 08:54 | <annevk> | WHATWG uses "WHATWG green" |
| 08:54 | <annevk> | http://workingdraft.de/ uses purple |
| 08:54 | <annevk> | lime? |
| 09:11 | <annevk> | "sergeant semantics" -- hsivonen makes up the best new terms :) |
| 09:15 | <erlehmann> | annevk, green and purple difference is approx. 60° on the color wheel. the new color thus would be some kind of orange. |
| 09:17 | <annevk> | if picking colors was a science, geeks would have prettier blogs |
| 09:17 | <zcorpan> | picking colors is art |
| 09:17 | <annevk> | trolling is a art too |
| 09:17 | <erlehmann> | if X was a science, geeks would have prettier Y (related to X) |
| 09:17 | <erlehmann> | corollar: nothing is sciency! |
| 09:17 | <zcorpan> | that's why art picked your blog's colors |
| 09:18 | <erlehmann> | annevk, AN art. |
| 09:18 | <annevk> | troled |
| 09:18 | <erlehmann> | coolface :B |
| 09:18 | <erlehmann> | :D |
| 09:19 | <erlehmann> | btw, anyone already selling spandex suits with the W3C HTML5 logo on the front? |
| 09:27 | <annevk> | I think brucel should do a sketch in such a suit |
| 09:27 | <annevk> | he clearly lost all creditability he had as developer advocate with the nudity and silly YouTube sketches :p |
| 09:28 | <erlehmann> | btw, whom of you is doing CSSquirrel? i like it, sometimes :3 |
| 09:29 | <annevk> | I don't think he hangs out here |
| 09:44 | <zcorpan> | hsivonen: s/to for/to go for/ ? |
| 09:45 | <hsivonen> | https://twitter.com/#!/SemanticSarge/status/27657521934106625 |
| 09:45 | <hsivonen> | zcorpan: thanks |
| 09:52 | <zcorpan> | "I've seen SVG and CSS3 versions of the logo - who's got a WOFF one?" http://epeus.blogspot.com/2011/01/how-w3c-invented-logo.html - would be funny with a font where "HTML5" etc were replaced by the logo glyph |
| 09:53 | <hsivonen> | zcorpan: there should be a ligature for the string HTML5 |
| 09:54 | <zcorpan> | yeah |
| 09:55 | hsivonen | likes Eric Meyer's characterization: "Soviet-era Transformers logo" |
| 10:15 | <hsivonen> | Is my feed broken or is Venus broken when I have relative URLs in my Atom feed and Venus resolves them relative to my feed as opposed to resolving them relative to the entry's URL? |
| 10:21 | <roc> | There should be a Unicode character for HTML5 |
| 10:23 | <zcorpan> | just use U+F8FF |
| 10:24 | <Lachy> | ? |
| 10:24 | <zcorpan> | yah |
| 10:24 | <jgraham> | Seems to be in the PUA? |
| 10:25 | <zcorpan> | yah |
| 10:25 | <Lachy> | it is. It's the Apple logo on Macs |
| 10:25 | <jgraham> | Oh, I see |
| 10:25 | <jgraham> | Looks quite different here :) |
| 10:25 | <Lachy> | yeah, I expected as much |
| 10:25 | <jgraham> | Like: |
| 10:25 | <jgraham> | - |
| 10:25 | <jgraham> | Erm |
| 10:25 | <jgraham> | nevermind |
| 10:26 | <zcorpan> | it's great because when some people write "HTML5", other people will read "Apple" |
| 10:26 | <zcorpan> | and vice versa |
| 10:27 | <jgraham> | You have a sick sense of humor |
| 10:27 | <zcorpan> | thanks |
| 10:27 | <jgraham> | I can't work out if Apple would love it or hate it :) |
| 10:29 | <Lachy> | zcorpan, according to wikipedia, it's also the Windows logo in Wingdings 1 |
| 10:52 | <annevk> | whoa whoa whoa |
| 10:52 | <annevk> | can create a wireless network with Android |
| 10:52 | <annevk> | circumventing the whole tethering nonsense |
| 10:53 | <annevk> | Android win |
| 10:55 | <erlehmann> | annevk, don't do it. it eats the battery faster than you can charge it. |
| 10:55 | <matijsb> | hook it up to the laptop? |
| 10:55 | <erlehmann> | better tether with USB. btw, OS X cannot into USB tethering. BUT WHY? |
| 10:56 | <annevk> | Android tethering is disabled as well |
| 10:56 | <erlehmann> | wat. |
| 10:56 | <annevk> | T-Mobile... |
| 10:56 | <rimantas> | erlehmann, what do you mean? I can tetter usb, bluetooth and wifi (have iOS 4.3 beta on my phone) |
| 10:56 | <annevk> | but creating a wireless network works |
| 10:57 | <rimantas> | not on AT&T though, and not even in US… |
| 10:57 | <annevk> | on Android? |
| 10:57 | asmodai | rages against unwanted java consoles in firefox' addons. |
| 10:57 | <matijsb> | rimantas: you have to be registered dev to get hold of betas though, right? |
| 10:57 | <rimantas> | matijsb, correct |
| 10:57 | <matijsb> | drat |
| 10:57 | <erlehmann> | rimantas, when I hook up my HTC dream to my debian box, network-manager can connect. my friend, who has a macbook, could not find any signs of automagic connection setup over USB. |
| 10:58 | <matijsb> | would quite possible the only way to get 4.3-like tethering before the clueless operators block it again |
| 10:58 | <erlehmann> | annevk, T-Mobile is shit everywhere. In Germany, they even want to charge for instant messaging and voip. |
| 10:59 | <erlehmann> | when i switched to my current carrier, O2, the salesperson actually got me with the “we won't fuck around with your traffic” part. every other carrier does, |
| 10:59 | <erlehmann> | T-mobile even dynamically re-compresses javascript, breaking the admin interface of an imageboard (that shall not be named) for me. |
| 11:00 | <erlehmann> | when i called support to tell them to stop this dickery, the told me i should sent some specific header. i raged, then switched. |
| 11:01 | <annevk> | there's not a whole lot of choice |
| 11:01 | <annevk> | I guess vodaphone would be an alternative... |
| 11:02 | <matijsb> | it's the only viable one in the Netherlands |
| 11:03 | <erlehmann> | nope. they block voip AFAIK. |
| 11:03 | <erlehmann> | kinda ironic, since they used several high profile bloggers to promote their services, testimonial-style. |
| 11:04 | <matijsb> | all these guys should be doing right now is work their asses off to build the best possible mobile network |
| 11:04 | <erlehmann> | “thus i stand for this — with my tainted name.” |
| 11:04 | <annevk> | if i had a lot of money to burn, I would try competing with them |
| 11:05 | <erlehmann> | matijsb, i suspect that wanting to challenge the status quo is an uncommon disposition. |
| 11:06 | <matijsb> | woudn't you much rather just buy a small country if you had that kind of money at your disposal? :) |
| 11:06 | <matijsb> | erlehmann: heh :) |
| 11:06 | <erlehmann> | annevk, the chaos communication congress had its own GSM network. maybe some free mesh network can emerge, like the german “freifunk” project (when i moved in here, i found empty linksys router packaging in the cupboard). |
| 11:07 | <erlehmann> | at least on the city-level that is feasible. outside, not so. |
| 11:07 | <annevk> | i would buy a big island with all the additional money i'd make |
| 11:08 | <matijsb> | isn't that what Fon does erlehmann? |
| 11:09 | <erlehmann> | matijsb, no. fon is a proprietary piggybacking on that idea, locking down their hardware and creating a walled garden. |
| 11:09 | <matijsb> | Oh! |
| 11:11 | <erlehmann> | matijsb, also: freifunk is actually doing mesh-networking. fon is not. |
| 11:12 | <erlehmann> | there is a reason for it, unique to germany. after reunification, people dug trenches for optical networks. but after they found out how one can use copper lines for DSL, no one used the fiber. |
| 11:12 | <erlehmann> | thus there were (and probably still are) areas where you could not get fast internet. mesh-networking with linux-based routers to the rescue! |
| 11:32 | <Philip`> | "I thought I had e-mailed about this a few days ago, but it turns out I had sent my e-mail to publish-html⊙wo instead of public-html⊙wo!" |
| 11:32 | <Philip`> | http://www.w3.org/TR/html5/ was published a few days ago |
| 11:33 | <Philip`> | Is this a secret mailing list that triggers spec publication? |
| 11:34 | <hsivonen> | Philip`: huh. Did Hixie just leak the existence of the secret publication cabal? |
| 11:36 | <annevk> | fwiw, Team/publish-html Member/publish-html all 404 |
| 11:36 | <annevk> | thinking it was just a typo |
| 11:39 | <hsivonen> | annevk: I was joking |
| 11:40 | <annevk> | I was curious myself :) |
| 11:41 | <annevk> | a mistake like that is unlikely to happen in my mail client, but I think Hixie uses some ancient thing |
| 11:43 | <annevk> | I sometimes wish we had #secretthreehouse to rant about crazy Member-only emails |
| 11:43 | <annevk> | or questionable things, like why a certain WG is missing here http://www.w3.org/mid/20110119004051.GG7500⊙srn |
| 11:44 | <annevk> | oh hey |
| 11:44 | <annevk> | that's public :) |
| 11:44 | annevk | got it via the chairs cc |
| 11:46 | <annevk> | "Assuming this bug report is in English, it is invalid." hahaha |
| 11:48 | <jgraham> | Hixie uses (al)pine iirc |
| 11:56 | <hsivonen> | annevk: well, HTML5 doesn't reference the Role Attribute 1.0 spec |
| 11:57 | <hsivonen> | annevk: I wish the SVG WG didn't reference it, either, in their specs |
| 11:57 | <annevk> | HTML5 does mention the role="" attribute |
| 11:58 | <hsivonen> | annevk: what HTML5 mentions isn't the role attribute from the Role Attribute 1.0 spec. These aren't the droids you are looking for. |
| 11:58 | <erlehmann> | vrs |
| 11:59 | <vrs> | erlehmann |
| 12:36 | <annevk> | TabAtkins, https://bitbucket.org/annevk/simpleserver |
| 12:53 | <FastJack> | heh, like that html5 logo. looks a bit like the master control program from tron (the original one) |
| 13:00 | <zcorpan> | Philip`: feel like greping for pages with <textarea> in <button>? |
| 13:03 | karlcow | is reading hsivonen about the badge |
| 13:03 | <annevk> | that Python server works surprisingly well |
| 13:04 | <karlcow> | good point about the military semantics :/ It is spreading everywhere it seems. |
| 13:04 | <karlcow> | There was also recently "The Army of awesome" or something like that |
| 13:19 | <Philip`> | zcorpan: I looked for files (not just lines) matching (?i)<button([^<]|<(?!/button))*<textarea which I think should do that |
| 13:19 | <Philip`> | and didn't find any |
| 13:20 | <Philip`> | (There's lots if I use e.g img instead of textarea) |
| 13:22 | <MikeSmith> | hsivonen: http://bugzilla.validator.nu/show_bug.cgi?id=812 |
| 13:23 | <MikeSmith> | would be easy enough to make that change, just wondering if in fact that'd be the right way to address the problem |
| 13:23 | <charlvn> | "oh nonon onono non onono nonono nono nononono nonon onono nononononononononononononononononono" ?! :) what the heck? |
| 13:24 | <MikeSmith> | hsivonen: also would need to make that change in part of the IRI checker that deals with javascript: URLs |
| 13:24 | <MikeSmith> | I guess |
| 13:24 | <MikeSmith> | hsivonen: I think that one is supposed to match FunctionBody too, iirc |
| 13:25 | <gsnedders> | "return" should be a valid ExpressionStatement that falls into FunctionBody. |
| 13:26 | <zcorpan> | Philip`: ok. thanks |
| 13:31 | <MikeSmith> | hmm, neither http://tools.ietf.org/html/rfc4329 nor http://tools.ietf.org/html/draft-hoehrmann-javascript-scheme-03 specifies this |
| 13:31 | <hsivonen> | MikeSmith: I have no idea what Rhino is doing there, but I suppose the suggested fix makes sense if Rhino can't be configured with more granularity |
| 13:31 | <MikeSmith> | hsivonen: OK |
| 13:32 | <MikeSmith> | I will check and see if it can be |
| 13:32 | <MikeSmith> | but I am pretty sure it can't |
| 13:32 | <MikeSmith> | didn't find anything last time I poked around in their docs |
| 13:33 | <MikeSmith> | hsivonen: what about for javascript: URIs? |
| 13:33 | <MikeSmith> | should not we be doing the same there too? |
| 13:34 | <MikeSmith> | did you ever find anything that actually specifies exactly what the contents of those must conform to? |
| 13:34 | <MikeSmith> | I vaguely remember seeing something but can't remember where |
| 13:34 | <hsivonen> | MikeSmith: nothing fully realistic |
| 13:34 | <MikeSmith> | ok |
| 14:09 | <annevk> | hsivonen, I'm a bit slow still, but who defines the values for the role="" attribute then? |
| 14:09 | <annevk> | hsivonen, ooh, those are defined in WAI-ARIA? |
| 14:09 | <annevk> | hsivonen, if that is the case I do indeed wonder why we even need a separate draft |
| 14:10 | <annevk> | hsivonen, bit of shame still role="" was not renamed to aria-role="" |
| 14:10 | <hsivonen> | annevk: HTML5 seems to think ARIA defines and ARIA seems to think HTML5 defines it |
| 14:10 | <hsivonen> | annevk: there's a bit of a definitional gap there |
| 14:10 | <hsivonen> | annevk: but HTML5 tries to say that it specs into existence exactly the kind of thing ARIA wants |
| 14:12 | <matjas> | hsivonen, re: http://hsivonen.iki.fi/sergeant-semantics/ — have you seen the HTML5 ★ Boilerplate logo? :) |
| 14:12 | <hsivonen> | annevk: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914#c7 |
| 14:12 | <hsivonen> | matjas: not sure |
| 14:13 | <matjas> | hsivonen: http://html5boilerplate.com/apple-touch-icon.png etc |
| 14:13 | <hsivonen> | matjas: no, I hadn't noticed that, no |
| 14:14 | <hsivonen> | FAIL: the boilerplate uses X-UA-Compatible *after* conditional comments |
| 14:15 | <matjas> | hsivonen: the sergeant insignia is also used by police in some countries: http://images.morris.com/images/juneau/mdControlled/cms/2008/04/08/266367930.jpg |
| 14:15 | hsivonen | wonders if anyone has actually tested if the IE=Edge bit on the boilerplate site ever takes effect |
| 14:16 | <hsivonen> | very interesting. it actually takes effect in IE9 |
| 14:18 | <hsivonen> | I wonder if IE=Edge is allowed to have the UI effect of hiding the compat mode button even after it's too late to actually switch the mode |
| 14:19 | <hsivonen> | in the general case, X-UA-Compatible doesn't work after a script or after a conditional comment |
| 14:20 | <matjas> | hsivonen: Interesting! I filed a bug here: https://github.com/paulirish/html5-boilerplate/issues/issue/285 Perhaps paulirish can tell us more. |
| 14:21 | <hsivonen> | interesting, it also has a UI effect in IE8 |
| 14:22 | <hsivonen> | I'd love to know if the boilerplate triggers Edge if served from a blacklisted domain |
| 14:22 | <annevk> | maybe they just scan the first 512 bytes? |
| 14:22 | <annevk> | oh right, by default you get IE=edge anyway |
| 14:22 | <annevk> | but spreading that meta element is bad imo |
| 14:22 | <annevk> | so much cruft |
| 14:23 | <annevk> | just when we managed to kill most of the silly DOCTYPE |
| 14:23 | <annevk> | Microsoft goes to add something... |
| 14:23 | <matjas> | don’t even mention the IE9/Win7 jumplist menu madness |
| 14:26 | <annevk> | I wonder why some people refer to Ian as "html5 editor" |
| 14:26 | <annevk> | Too afraid to mention his name? |
| 14:27 | <annevk> | Reminds me of that book with muggles and wizards |
| 14:27 | <jgraham> | annevk: To dehumanize him? |
| 14:28 | <annevk> | It's rather pathetic really |
| 14:30 | <karlcow> | annevk: the person saying html5 editor is from where? |
| 14:31 | <karlcow> | name/role are handled differently depending on culture |
| 14:32 | <matjas> | Microsoft FrontPage 2011 == HTML5 editor |
| 14:33 | <annevk> | karlcow, the one that is persistent about is Steve Faulkner |
| 14:33 | <annevk> | I think he's from the UK |
| 14:35 | <karlcow> | so that would not work in this case I guess ;) |
| 14:35 | <annevk> | about it* |
| 14:44 | <remysharp> | annevk: do you have a second to answer a question about SSE (re: your comment on the html5doctor article) |
| 14:45 | <annevk> | yes |
| 14:45 | <annevk> | Hixie, do you have some source code that generated http://www.hixie.ch/tests/adhoc/html/parsing/encoding/ ? |
| 14:45 | <remysharp> | you said that the server was sending 200ok and closing |
| 14:45 | <remysharp> | that's right |
| 14:46 | <remysharp> | should it not be sending 200? |
| 14:46 | <remysharp> | I've been re-reading the spec and I'm obviously going wrong if you're saying it's good in Opera 11 |
| 14:48 | <annevk> | remysharp, sending 200 is fine, if you want the browser to reestablish the connection |
| 14:48 | <annevk> | remysharp, if you want to keep sending events, you should not close the connection |
| 14:49 | <annevk> | remysharp, that is the problem |
| 14:49 | <remysharp> | annevk: so this is (a snippet) of what I've got so now: https://gist.github.com/786260 |
| 14:49 | <annevk> | remysharp, if the server keeps the connection open, there is no need for the client to reestablish the connection |
| 14:49 | <remysharp> | so I should ditch the response.end() part |
| 14:50 | <remysharp> | annevk: okay, I'll tweak the server now - remove the close, and I guess just stick a timer in there that keeps sending content |
| 14:50 | <remysharp> | annevk: if it's working, I'll add an update to clarify what I ballsed up. |
| 14:50 | <annevk> | remysharp, you need some kind of asynchronous architecture on the server if you really want to make use of this |
| 14:50 | <annevk> | remysharp, much like with WebSocket |
| 14:50 | <remysharp> | annevk: node should do |
| 14:50 | <annevk> | remysharp, it probably does, yes |
| 14:50 | <remysharp> | :) |
| 14:51 | <hsivonen> | where do all these bug reports with markup come from? |
| 14:54 | <remysharp> | annevk: hmm - didn't seem to work: http://node.remysharp.com:8001/sse-client.html |
| 14:54 | <remysharp> | annevk: it's still opening new connections even though the server isn't closing |
| 14:55 | <matjas> | gotta love his new avatar — http://twitter.com/diveintomark |
| 14:55 | <annevk> | are you sure res.end() is not implicit |
| 14:55 | <annevk> | I mean, if you just removed that |
| 14:55 | <remysharp> | annevk: yeah, actually - I just removed res.end() - but when I curl it from the command line it seems to close |
| 14:55 | <remysharp> | annevk: going to check a little deeper |
| 14:56 | <annevk> | I suspect you need a different kind of setup |
| 14:56 | <annevk> | remysharp, http://www.html5rocks.com/tutorials/eventsource/basics/ |
| 14:57 | <annevk> | remysharp, sorry |
| 14:57 | <annevk> | remysharp, their server implementation is no better |
| 14:57 | <annevk> | I wonder if anyone actually took a real crack at this yet :) |
| 14:57 | <remysharp> | annevk: yeah, I checked over that today, it's practically the same as what I had |
| 14:58 | <remysharp> | annevk: /thats/ why I figured it was borked |
| 14:58 | <remysharp> | :) |
| 14:59 | <annevk> | Seems like paul_irish should hunt someone down at the Googleplex :) |
| 15:00 | <annevk> | there is a real one btw in Java |
| 15:00 | <annevk> | http://my.opera.com/WebApplications/blog/2007/05/03/scalable-server-sent-events |
| 15:00 | <annevk> | but it is for an older version of server-sent events, but it comes down to the same |
| 15:03 | <jgraham> | Seems like it should be quite easy to write a server for, if you write a proper server rather than some PHP hack |
| 15:04 | <remysharp> | yet no one has done it - except for the old example annevk just pointed out |
| 15:05 | <annevk> | I suspect it is quite easy to hack one on top of https://bitbucket.org/annevk/simpleserver |
| 15:05 | Philip` | guesses it should be straightforward in e.g. Twisted in Python |
| 15:06 | <Philip`> | (since that already provides async HTTP stuff) |
| 15:07 | <remysharp> | you'd think it should be simple in node, just remove the res.end() - but it seems to be closing automatically :-\ |
| 15:08 | <annevk> | http://nodejs.org/api.html |
| 15:08 | <annevk> | "Sending a 'Connection: keep-alive' will notify Node that the connection to the server should be persisted until the next request." |
| 15:08 | <Rik`> | remysharp: the gist you're showing misses some code |
| 15:09 | <remysharp> | it's missing most of the code - here's the full listing: |
| 15:09 | <remysharp> | http://node.remysharp.com:8001/custom-echo.js |
| 15:09 | <remysharp> | it's now staying open - seems that I was going through some %$£%$££ proxy and it was caching my responses. |
| 15:09 | <remysharp> | brillant. |
| 15:10 | <annevk> | sweet |
| 15:11 | <annevk> | may I recommend writing a separate article? |
| 15:12 | <remysharp> | dedicated to sse? |
| 15:13 | <annevk> | yeah |
| 15:13 | <remysharp> | why's that - do you mean for a more detailed article, or to correct the fuck up I left in the wake of my article? |
| 15:14 | <remysharp> | of course I want to set people straight either way :) |
| 15:14 | <annevk> | it seems tricky and interesting enough on its own |
| 15:14 | <annevk> | mostly |
| 15:15 | <remysharp> | yeah, the plan is to eventually have dedicated articles on all of those technologies |
| 15:15 | <miketaylr> | a dedicated article would be great |
| 15:15 | <remysharp> | The priority for me is to correct the article and get people re-reading the corrections |
| 15:19 | <remysharp> | problem I've got now, is the opera opens the connection, but isn't receiving message events... |
| 15:20 | <Philip`> | Do you need to flush the response within the server? |
| 15:20 | <remysharp> | no, it's going through |
| 15:20 | <remysharp> | here's the server: curl http://node.remysharp.com:8001/sse/ |
| 15:21 | <remysharp> | sends two lines: "data: connected: 12\nid: 2\n\n" |
| 15:22 | <Philip`> | I see no newlines after the id |
| 15:22 | <Philip`> | id: 18data: connected: 6 |
| 15:22 | <remysharp> | this is the server code that's live: http://node.remysharp.com:8001/custom-echo.js |
| 15:23 | <remysharp> | it shouldn't fix it, but I'm switing '\n\n' to "\n\n" |
| 15:24 | <remysharp> | okay, fixed it |
| 15:24 | <Philip`> | Works now |
| 15:24 | <remysharp> | I'm a plum - forgot to restart after I added \n\n |
| 15:24 | <Philip`> | Ah :-) |
| 15:25 | <remysharp> | screw me sideways. that was too much time on such a simple fix |
| 15:25 | <remysharp> | okay, with that fix - Opera working perfect, no re-requesting |
| 15:25 | <remysharp> | Chrome too |
| 15:25 | Philip` | finds Wireshark handy for debugging this kind of thing, incidentally, since it shows the raw traffic and the packet boundaries and who closed the connection etc |
| 15:26 | <remysharp> | Philip`: yeah, I /used/ to use it years ago - you're reminded me I shouldn't have stopped! |
| 15:29 | <remysharp> | what's nice about SSE is they reconnect nicely :) |
| 15:32 | Philip` | hates the name SSE, since it always makes him think of SIMD instruction sets |
| 15:33 | <remysharp> | EventSource? |
| 15:33 | <remysharp> | SexySeverEvents |
| 15:34 | <remysharp> | +EventSauce = mess |
| 15:34 | remysharp | that me done I think. |
| 15:34 | <Philip`> | Maybe server sent event will be extended to SSE2, then SSE3, then Microsoft will invent SSSE3 and SSE4 while Mozilla invents SSE5 and it'll all be an incompatible mess |
| 15:34 | <Philip`> | s/event/events/ |
| 15:43 | <hsivonen> | OK. the Internets has done its duty and produced a picture of brucel with the W3C HTML5 logo on his superhero suit: https://twitter.com/#!/SuperHTML5Bruce |
| 16:01 | <annevk> | hah |
| 16:35 | <annevk> | you get an XML document as input, process it incrementally and do some transformation, and write it away at the same time, all while using minimal memory even when processing gigabytes of data |
| 16:36 | <annevk> | however, there's no guarantee the input is well-formed |
| 16:36 | <jgraham> | annevk: ? |
| 16:37 | <annevk> | is this an argument/use case for something like XML5 or am I missing something? |
| 16:37 | <annevk> | presumably the processor could detect the error and pass it on, but output is already being written, potentially being another XML document |
| 16:38 | <annevk> | it seems with traditional XML you would always need to do a double pass over the input resource |
| 16:38 | <annevk> | first to check whether it is correct, then to pass on events to the transformation and output layer |
| 16:38 | <jgraham> | It depends on whether you are a revisionist XMLer or not |
| 16:39 | <jgraham> | If you are, it is fine to stop processing where you find the error and just say "now there is an error" |
| 16:39 | <jgraham> | Maybe if you are not, even |
| 16:45 | <annevk> | jgraham, how would you say that though? |
| 16:45 | <annevk> | jgraham, consider XML -> XML |
| 16:46 | <annevk> | jgraham, <test>very long text node with at the end an invalid byte</test> |
| 16:46 | <annevk> | jgraham, the transformation step applied is renaming <test> to <p> |
| 16:46 | <annevk> | this scenario is not theoretical, people at typLAB are doing something similar to this |
| 16:47 | <annevk> | independent from me they came to the conclusion they needed some kind of lenient XML parser |
| 16:47 | <annevk> | when I found out I did point out XML5 |
| 16:49 | <Philip`> | When I did something that streamingly generated XML and might encounter errors, I made it emit U+0018 CANCEL into the XML output to signal the errors |
| 16:49 | <Philip`> | since "cancel" sounded like a good word |
| 16:49 | <Philip`> | and since it'd made any streaming consumer abort too |
| 16:50 | <Philip`> | s/made/make/ |
| 16:52 | <jgraham> | annevk: If you are a revisionist, the handling after you hit the error is explicitly undefined, so it is fine to recover up to where you encounter the byte and close out all open elements or whatever |
| 16:53 | <jgraham> | I mean, I agree this is not enough, but apparently it has taken people years to cotton on to how damaging the XML position of "we know the one true error recovery strategy (and it is hard failure)" is |
| 16:54 | <Philip`> | If you were streamingly outputting HTML and encountered a fatal error, you wouldn't be able to signal it at all, which sounds worse |
| 16:55 | <jgraham> | Philip`: Why not? You could have some out-of band method of signaling |
| 16:56 | <Philip`> | If you have out-of-band signalling then you could use that for XML too and there's no problem |
| 16:57 | <jgraham> | Hmm, maybe I don't understand |
| 16:57 | <jgraham> | You encounter something in HTML you consider a fatal error |
| 16:58 | <jgraham> | You can just stop, and send an error code |
| 16:59 | zcorpan | thinks Philip` meant XML->HTML with some error in the XML |
| 16:59 | <jgraham> | With XML you encounter a non-fatal error (that causes wellformedness problems) |
| 16:59 | <jgraham> | You can't do anything without violating the spec |
| 17:00 | <jgraham> | Or reparsing the whole document as non-XML |
| 17:00 | <Philip`> | I assumed annevk's original point about XML->XML conversion was that there was no way to report fatal errors (because it's streaming and there's no out-of-band notifications) and so a lenient XML parser was required so that you never get fatal errors and don't need to worry about reporting them, or something |
| 17:02 | <Philip`> | But I don't see why you need to avoid fatal parse errors, because you can just abort and emit ill-formed output so the error is passed on to the consumer |
| 17:03 | <Philip`> | and you can get fatal errors in plenty of other ways (e.g. running out of memory) so you need some way to signal errors anyway |
| 17:04 | <Philip`> | so I don't see why lenient XML parsers are relevant |
| 17:04 | <annevk> | if the consumer is the end user that seems like a bad situation |
| 17:04 | <Philip`> | zcorpan: (I meant HTML->XML using hsivonen's non-buffered SAX mode which aborts on non-streamable parse errors) |
| 17:06 | <Philip`> | zcorpan: (unless you meant the other thing I meant) |
| 17:06 | Philip` | is getting confused |
| 17:07 | <annevk> | yay |
| 17:08 | <annevk> | my thread confused Philip` |
| 17:08 | <annevk> | mission accomplished |
| 17:10 | <annevk> | oh right |
| 17:11 | <annevk> | so last night krijnh proposed <h1>Hello <small>Hello 101 Study</small></h1> |
| 17:11 | <annevk> | as alternative to having a new element |
| 17:12 | <annevk> | jgraham, I think I like that even better than what you proposed |
| 17:13 | <jgraham> | I like it less fwiw |
| 17:13 | <jgraham> | Someone else suggested it at the same time |
| 17:14 | <jgraham> | It doesn't mean the same as <small> in other contexts |
| 17:14 | <jgraham> | If we believe in this semantics lark there is no point in making it unnecesssarily hard |
| 17:15 | <Hixie> | annevk: yes i have code that generated that source, ping me in a couple of hours and i can get it to you |
| 17:16 | <Hixie> | in case anyone missed my earlier question, i'm looking for feedback on http://wiki.whatwg.org/wiki/Change_Proposal_for_ISSUE-120 before i submit it today (no-namespaces-in-RDFa CP) |
| 17:16 | <annevk> | Hixie, if you could reply to the email (offlist if you want) that'd be easiest probably |
| 17:16 | <annevk> | I might be taking a pre-night nap |
| 17:16 | <Hixie> | also, in case anyone missed it yesterday, i'm planning on renaming the WHATWG HTML spec from "HTML5 (...)" to just "HTML" in a few hours unless anyone has a reason not to |
| 17:16 | <Hixie> | annevk: wfm |
| 17:16 | <annevk> | ta |
| 17:17 | <zcorpan> | Hixie: just do it already :P |
| 17:17 | <annevk> | jgraham, it is more backwards compatible |
| 17:17 | <Hixie> | zcorpan: :-) |
| 17:17 | <Hixie> | zcorpan: last time it caused all kinds of bitching, so i want to make sure the more active members of our community are on board first this time :-) |
| 17:17 | <annevk> | if you do it now, I can put it on the Internet |
| 17:17 | <annevk> | I mean twitter |
| 17:18 | <jgraham> | annevk: Not really |
| 17:18 | <zcorpan> | Hixie: are you asking on other places than #whatwg? |
| 17:18 | <annevk> | jgraham, styling? |
| 17:18 | <Hixie> | zcorpan: not any significant places, no |
| 17:18 | <Hixie> | zcorpan: feel free to |
| 17:18 | <annevk> | should we ask on twitter? |
| 17:18 | <dglazkov> | I think I need a logo too |
| 17:19 | <jgraham> | annevk: The styling will need to be adjusted by the author anyway |
| 17:19 | <Hixie> | hsivonen: your input on http://wiki.whatwg.org/wiki/Change_Proposal_for_ISSUE-120 in particular would be most welcome |
| 17:19 | <annevk> | jgraham, all you need with small is display block |
| 17:19 | <jgraham> | Right, and probably setting the size that you actually want |
| 17:19 | <Hixie> | i gotta disappear for a few hours, bbiab. let me know if you ask anywhere else and get an answer. :-) |
| 17:19 | <zcorpan> | Hixie: the only obvious place for me would be my twitter but i don't have so many followers |
| 17:20 | <jgraham> | So it is going to be the same as <subhead> in most cases |
| 17:20 | <Hixie> | zcorpan: feel free to convince anne that the whatwg twitter account would be appropriate :-) |
| 17:20 | <Hixie> | bbl |
| 17:21 | <annevk> | "We are going to rename the HTML5 specification to HTML in a few hours to avoid confusion with the marketing term. Problem, interwebs?" |
| 17:21 | <annevk> | s/marketing term/HTML5 buzzword/ |
| 17:21 | <annevk> | zcorpan, wdyt? |
| 17:21 | zcorpan | would go for "Anyone object?" |
| 17:22 | <annevk> | aah, no troll jokes? |
| 17:22 | <Ms2ger> | "Negative Effects: Simplifies RDFa, potentially letting more people use it." |
| 17:22 | <Ms2ger> | Now that's not a nice thing to say |
| 17:23 | <annevk> | also funny |
| 17:24 | <jgraham> | Yeah, but looks childish |
| 17:25 | <annevk> | new try |
| 17:25 | <annevk> | "http://whatwg.org/html is getting renamed from HTML5 to HTML in a few hours to avoid confusion with the HTML5 buzzword. Okay? #html5" |
| 17:26 | <zcorpan> | wfm |
| 17:27 | <annevk> | http://twitter.com/WHATWG/status/27780227706912768 |
| 17:27 | <matjas> | how has it come to this |
| 17:27 | <miketaylr> | hmm i'm leaving dhtml5.com as is for nostalgia then |
| 17:28 | <TabAtkins> | matjas: It's been just "HTML" ever since we abandoned versioning. This is just a convenient time to make the change official. |
| 17:28 | <jacobolus> | Hixie: in your "other technologies" list, I've definitely seen namespace bugs in SVG renderers |
| 17:28 | <annevk> | apparently getting html.org requires USD 20k :/ |
| 17:28 | <annevk> | html5.org ftw |
| 17:29 | <matjas> | TabAtkins: I know. It’s just that I’m still sobbing about the whole HTML5 logo + marketing mess |
| 17:29 | <miketaylr> | i wonder how much the logo cost, let's pawn it for html.org |
| 17:29 | <Philip`> | Hixie: Incompatibility with legacy RDFa-in-text/html documents sounds like it should be considered a negative effect |
| 17:30 | <matjas> | TabAtkins: I mean, the logo is basically a huge 5, which goes against the design principle of forward compatibility |
| 17:30 | <TabAtkins> | matjas: Hahaha |
| 17:30 | matjas | weeps |
| 17:30 | <Ms2ger> | matjas++ |
| 17:31 | <zcorpan> | annevk: you don't have USD 20k to spare? |
| 17:32 | <annevk> | whether or not I do, it seems a bit much for getting rid of a character in a domain |
| 17:32 | <MikeSmith> | confusion is fun |
| 17:32 | <jgraham> | annevk: Maybe if this change goes through it will be a good investment |
| 17:33 | <Workshiva> | We should just wait for the new TLD system and register .html |
| 17:33 | <zcorpan> | we've been over this before! |
| 17:33 | <annevk> | convince the Mali government to allow registration at the top-level |
| 17:33 | Philip` | will take http://index.html, and make it the default page for the whole internet |
| 17:35 | <zcorpan> | http://krijnhoetmer.nl/irc-logs/whatwg/20110107#l-655 |
| 17:36 | <annevk> | no wonder I can recite all of this without looking things up :) |
| 17:36 | <annevk> | some people on twitter are confused at least |
| 17:37 | <MikeSmith> | annevk: nothing new about people on twitter being confused |
| 17:39 | jgraham | sees the headline "World panics as people on twitter fail to become befuddeled!" |
| 17:39 | <MikeSmith> | "Let a hundred flowers of confusion further blossom" is what Chairman Mao once said |
| 17:40 | <MikeSmith> | then there's that cliche expression, "Starve a cold, feed confusion" |
| 17:40 | <MikeSmith> | etc. |
| 17:41 | <MikeSmith> | and it is no coincidence that "Confucian" is pronounced the same as "confusion" |
| 17:46 | <MikeSmith> | "needs more logo" |
| 17:47 | <jgraham> | MikeSmith: You are suggesting we use a cow bell for the HTML logo? |
| 17:50 | <jacobolus> | or just this picture? http://en.wikipedia.org/wiki/File:Confucius_Tang_Dynasty.jpg |
| 17:50 | <MikeSmith> | jgraham: I can't hear you … I think you need to say that again with more logo |
| 17:50 | <MikeSmith> | in other words, you need to HTML5 that more |
| 17:51 | <MikeSmith> | give it more HTML5 |
| 17:52 | <annevk> | I also added http://twitter.com/WHATWG/status/27786442344243200 so I don't have to track twitter replies |
| 17:58 | <zcorpan> | Hi random people from twitter! |
| 18:01 | <jgraham> | zcorpan: They are a highly biased sample of twitter users, hardly random at all |
| 18:01 | <TabAtkins> | jgraham: He never said "uniformly random from the population of all twitter users". |
| 18:02 | <jgraham> | TabAtkins: No, but the unqualified word "random" is highly misleading |
| 18:02 | <TabAtkins> | Only if you're being pedantic, and if so, then you weren't being pedantic enough. |
| 18:02 | <TabAtkins> | Go all the way or go home. |
| 18:02 | Ms2ger | goes home |
| 18:03 | <jgraham> | Feel free to take the pedant and run with it |
| 18:09 | <annevk> | strongest reaction on twitter thus far is from Matt May |
| 18:09 | <annevk> | "Oh, ffs. Way to finish capturing the spec. RT @WHATWG: http://whatwg.org/html is getting renamed from HTML5 to HTML...to avoid confusion." |
| 18:10 | <annevk> | "No, @WHATWG, it's not "okay" to expropriate the name HTML from W3C. Not that it'll stop you." |
| 18:10 | <annevk> | I have no idea what he means, I hope he joins IRC |
| 18:10 | <matjas> | As a rebellion against the W3C and its HTML5 [sic] logo, I hereby propose the WHATWG shall henceforth use the name HTML instead of HTML5 when talking about the markup language, and resort to using the HTML[5] Gang Sign for visual recognition and marketing purposes. http://html5homi.es/ |
| 18:11 | <jgraham> | Sounds like he isn't happy with us using any term that W3C uses (presumably including HTML5) |
| 18:11 | <TabAtkins> | How is using "HTML" more "expropriation" than using "HTML5"? (I don't know what "expropriate" means, but I don't see how it could possibly be different between the two.) |
| 18:11 | <TabAtkins> | Also, you shouldn't alter a retweet like that. |
| 18:12 | <TabAtkins> | I HAVE OPINIONS ON HOW YOU ARE USING THE TWITTERS. |
| 18:12 | <annevk> | he's not here TabAtkins :) |
| 18:12 | <TabAtkins> | It's a generalized "you". |
| 18:12 | <annevk> | but he might read the logs I suppose, apparently they're popular |
| 18:12 | <matjas> | /s/you/one/ happy now annevk? :P |
| 18:13 | <TabAtkins> | I should remember to use "one" more. My favoritest teacher ever used it constantly. |
| 18:13 | <jgraham> | Well you can tell at least some a11y people read the logs from the distribution of yellow |
| 18:13 | <Ms2ger> | "One should do his homework, Tab!"? |
| 18:13 | <jgraham> | matjas: That would make it ungrammatical, no? |
| 18:13 | <annevk> | matjas, you mean s/YOU ARE/ONE IS/? |
| 18:14 | <annevk> | damnit jgraham |
| 18:14 | <jgraham> | ONE SHOULD, surely |
| 18:14 | <TabAtkins> | Ms2ger: That was, indeed, a constant refrain. |
| 18:14 | <MikeSmith> | krijnh should add a "highlight all lines" button |
| 18:14 | <jgraham> | ONE SHOULD USE |
| 18:14 | <matjas> | I heard bad grammar is allowed in HTML5, so meh |
| 18:14 | <MikeSmith> | anything is allowed in HTML5 |
| 18:14 | <TabAtkins> | matjas: Yeah, the parsing algo will fix it up for you. |
| 18:14 | <zcorpan> | nothing wrong with one are if you do the gang sign |
| 18:14 | <Ms2ger> | Only inside badgrammar elements |
| 18:15 | <matjas> | Ms2ger: according to my sources it should work inside <sarcasm /> as well |
| 18:15 | <TabAtkins> | All possible bytestrings can be interpreted as en-html. |
| 18:15 | <jgraham> | AFAIK there is no conformance requirement that the test of a document must conform to the grammar indicated by the lang attribute |
| 18:15 | <Ms2ger> | File a bug |
| 18:15 | <jgraham> | I am worried that now I have thought of this Hixie will add one |
| 18:15 | <jgraham> | :p |
| 18:15 | TabAtkins | is sorely tempted to file a bug. |
| 18:15 | TabAtkins | and then escalate it to an issue. |
| 18:16 | <zcorpan> | Authors must not be stupid. |
| 18:16 | <jgraham> | TabAtkins: Dammit |
| 18:16 | <annevk> | That would make a lot of my HTML invalid. I object! |
| 18:16 | <TabAtkins> | I OBJECT FURTHER. |
| 18:16 | jgraham | is sure there are quite legitimate use cases for non-grammatical constructs |
| 18:16 | <jgraham> | such as the discussion of grammar |
| 18:16 | <TabAtkins> | That's what <sic> is for. |
| 18:17 | <jgraham> | <sic> a) doesn't exist and b) wouldn't make sense in the contexts I am thinking of |
| 18:17 | <annevk> | But if you do "Trolling is <sic>a</sic> art." people would know you are trolling |
| 18:17 | <TabAtkins> | Alternately, any text node containing the substring "[sic]" can ignore the rule. |
| 18:17 | <jgraham> | But literal quotes are another use case |
| 18:17 | <annevk> | So you would have to exclude <sic>, but that produces invalid code |
| 18:17 | <jgraham> | I can't believe I am wasting away my life thinking about this |
| 18:17 | <Philip`> | We'd need to add "precise normative specification of English grammar" to the Companion Specifications page |
| 18:17 | <TabAtkins> | Hahaha. Trolling is indeed a art. |
| 18:18 | <jgraham> | Philip`: I18n would never let that past |
| 18:18 | <TabAtkins> | s/Trolling/Nerd sniping/ |
| 18:18 | <jgraham> | We would need one for each possible valid lang value |
| 18:18 | <TabAtkins> | Finally a use for computational linguists. |
| 18:18 | <Ms2ger> | Well, there's one for en-US-x-hixie |
| 18:18 | <jgraham> | Although |
| 18:18 | <jgraham> | Do we have that for <script>? |
| 18:19 | <Workshiva> | The problem with using "one" is that it gets you trapped in the third-person pronoun tarpit |
| 18:19 | <TabAtkins> | There is no tarpit. "they" is a great third-person singular pronoun. Shakespeare used it. |
| 18:19 | <jgraham> | Ms2ger: That is way underspecified |
| 18:19 | <zcorpan> | Workshiva: use "I" instead |
| 18:19 | <Workshiva> | zcorpan: "I should do your homework" sounds like a bad way to phrase it |
| 18:19 | <TabAtkins> | Anything Shakespeare did is, by definition, valid English. |
| 18:20 | <Workshiva> | TabAtkins: Anything Shakespeare did is by definition obsolete and outdated! |
| 18:20 | <zcorpan> | Workshiva: i don't see anythign wrong with it! |
| 18:20 | <jgraham> | Anything anyone understands is, by definiton, valid english |
| 18:20 | <Philip`> | Shakespeare made up words, so does that mean making up words is valid English? |
| 18:20 | <jgraham> | Descriptiveism ftw |
| 18:20 | <TabAtkins> | Workshiva: I don't think you understand. Shakespeare *created* English. Before him we were all talking fake-german. |
| 18:20 | <jgraham> | Philip`: Yes |
| 18:20 | <jgraham> | (creating words happens all the time) |
| 18:20 | <TabAtkins> | It took him a while to teach English to enough people for them to be able to understand his plays. |
| 18:21 | <Workshiva> | He didn't invent English, he invented Ye Olde Aenglishe |
| 18:21 | <jgraham> | (creating new grammatical forms is, I guess, harder) |
| 18:21 | <Workshiva> | I don't think there's any "u mad?" in Shakespeare |
| 18:21 | <TabAtkins> | Nah, that's easy too. My wife and her mother regularly leave out "to be" from their sentences, like "The cat needs fed." |
| 18:21 | <jgraham> | TabAtkins: I doubt you created taht |
| 18:21 | <Philip`> | The best thing about Shakespeare is that he wrote all those margin notes to explain what he meant in modern English |
| 18:22 | <TabAtkins> | No, but someone did, and it's not standard English. |
| 18:22 | <TabAtkins> | Philip`: He was really forward-looking, yeah. |
| 18:22 | <jgraham> | TabAtkins: But it is English |
| 18:22 | <TabAtkins> | jgraham: Sure, *now*. Because it was invented. |
| 18:22 | <jgraham> | In the sense that it is accepted by native speakers |
| 18:22 | <jgraham> | Well yeas, so was anything |
| 18:23 | <jgraham> | But new words must be more common than new grammatical forms |
| 18:23 | <zcorpan> | yeas? jgraham spelling for yes? |
| 18:23 | <TabAtkins> | Sure, I'd say it's more common. |
| 18:23 | <jgraham> | zcorpan: 21st century keyboard friendly alternative form, yeas |
| 18:23 | zcorpan | likes yeas |
| 18:24 | Ms2ger | likes peas |
| 18:24 | <mattmay> | annevk: you rang? |
| 18:24 | <zcorpan> | Ms2ger: black eyed ones? |
| 18:24 | <TabAtkins> | Hmm. If we define <device> to be something that creates a stream from hardware, and this stream can then be used in other elements that expect a URL... |
| 18:24 | <jgraham> | zcorpan: ugh |
| 18:25 | <TabAtkins> | Then we should get scriptable access to webcams through <video> with the stream, and evented data from HID devices by connecting EventSource to a stream. |
| 18:26 | MikeSmith | highlights "The best thing about Shakespeare is that he wrote all those margin notes to explain what he meant in modern English" |
| 18:27 | <Philip`> | TabAtkins: How would that work when you need to add webcam-specific API (like controlling the contrast or enabling face-tracking or whatever)? Just stick them on HTMLVideoElement? |
| 18:27 | <TabAtkins> | Maybe? |
| 18:27 | <TabAtkins> | I admit, attaching it to <video> is the weirdest case. How does play/pause interact? |
| 18:27 | MikeSmith | also highlights the line where he said, "* MikeSmith highlights "The best thing about Shakespeare is that he wrote all those margin notes to explain what he meant in modern English" |
| 18:27 | <TabAtkins> | But attaching it to <img> seems cool. |
| 18:28 | <TabAtkins> | Handing mic access directly to an audio buffer (per Chris Rogers' spec) would similarly be better than handing it to <audio>. |
| 18:29 | <TabAtkins> | I guess we can define a video buffer as well. |
| 18:29 | <TabAtkins> | Though, things like controlling the contrast seem like they'd be best handled by the UA, no? |
| 18:30 | <karlcow> | http://html5.uncontrol.com/ |
| 18:30 | <Philip`> | It'd probably be similar to <video> UI, where the UA provides default controls but you can write your own scripted ones if you want |
| 18:30 | <TabAtkins> | Good point. |
| 18:30 | <karlcow> | http://people.opera.com/danield/html5/html5logo/ |
| 18:31 | <ben_c> | What would be the issues of play / pause stopping / starting the webcam input stream? |
| 18:32 | <TabAtkins> | Well, is it sensical that the webcam only starts "recording" when you hit play on the <video>? |
| 18:32 | <TabAtkins> | The answer might be "yes", I dunno. |
| 18:32 | <Philip`> | Why would you want to connect a web page to your local webcam anyway? |
| 18:32 | <Philip`> | Seems much more useful to connect to somebody else's webcam |
| 18:32 | <TabAtkins> | That's useful as well. |
| 18:33 | <ben_c> | ah, so in that case the UI would need to change to record / stop, see your point |
| 18:33 | <Philip`> | If you want to look at yourself, just get a glossy monitor |
| 18:33 | <TabAtkins> | Philip`: I think things like Playstation Eye and Kinect prove that it's useful to get live images of yourself into a program. |
| 18:34 | <webr3> | is there any specification of what URI normalization should or should not be implemented by somebody implementing the HTML spec, seems browsers (like chrome) do some normalization but I can't see any requirement for this to happen, or text saying it shouldn't happen |
| 18:34 | <ben_c> | Philip`: You get to have cool business cards - http://www.youtube.com/watch?v=5qoucBw60jM |
| 18:37 | <zcorpan> | webr3: i think abarth is working on a url spec |
| 18:37 | <zcorpan> | webr3: previous work is 'web addresses in html5' or what it's called |
| 18:38 | <TabAtkins> | Heh, I think that, with the new CSS3 Speech additions, I coudl Autotune a webpage. |
| 18:39 | <paul_irish> | TabAtkins: we have a goal on the wall to do that. :) |
| 18:39 | <TabAtkins> | YES. |
| 18:42 | <Hixie> | thanks to the various comments on the CP, I've updated it as suggested. http://wiki.whatwg.org/wiki/Change_Proposal_for_ISSUE-120 |
| 18:48 | <mattmay> | Hixie: how would you prefer an issue be raised on a change that hasn't been made? Pretty sure that's not usually how these things happen. |
| 18:49 | <Hixie> | how do you mean? |
| 18:49 | <Hixie> | annevk: dude how do i log in to the blog :-P |
| 18:50 | <mattmay> | This is about s/HTML5/HTML/g |
| 18:50 | <Hixie> | ah, we're just talking about that here |
| 18:50 | <Hixie> | so if you have a question about it, just raise it here :-) |
| 18:51 | <mattmay> | Okay, well... first of all, I think HTML is a term with a little bit of history to it. |
| 18:51 | Ms2ger | approves of HTML |
| 18:52 | <Hixie> | yeah, the spec has a section talking abotu the history of HTML |
| 18:53 | <mattmay> | And while I know HTML5 is already problematic what with the W3C/WHATWG schism and all, I think removing the 5 leads to an even bigger namespace collision. |
| 18:53 | <Hixie> | namespace collision? |
| 18:53 | <Hixie> | not sure what you mean |
| 18:54 | <mattmay> | Specifically, HTML is the most generic term for web markup available. |
| 18:55 | <Hixie> | not as generic as "web markup" |
| 18:56 | <Hixie> | but even if it was, that doesn't seem like a problem... i mean, "HTML" is what the spec defines, right? |
| 18:56 | <alcuadrado> | Hi everyone, I have just seen a tweet from the whatwg account saying something about "name change". Are you planning to change the name to HTML, to the WG, or what? :s |
| 18:56 | <mattmay> | I'm pretty sure I've never had anyone ask me to help them with their "web markup". |
| 18:56 | <Hixie> | alcuadrado: the plan is to rename http://whatwg.org/html to "HTML" rather than "HTML5 (including next generation additions still in development)" |
| 18:57 | <mattmay> | Then why create a term of art around your work, only to abandon it when it's used by the holder of the HTML trademark? |
| 18:58 | <alcuadrado> | I one read in the WHATWG blog that after this spec you are planning to move to a more or less rolling release approach, I am right? If that's true, I think it'd be ok to name it just html. But well, I'm just a curious web dev :P |
| 18:58 | <alcuadrado> | once* |
| 18:58 | <Ms2ger> | There is no HTML trademark |
| 18:59 | <Hixie> | alcuadrado: yep, already doing that in fact, changing the name is the last step |
| 18:59 | <karlcow> | Ms2ger: there is in fact - http://www.w3.org/Consortium/Legal/2002/trademarks-20021231.html |
| 19:00 | <PlayerNaN> | I guess every browser will need to conform to the html5 specifications for naughty markup when rendering old html documents anyways, I'm for everything that cleans up old documents as well. Have I understood this right? |
| 19:00 | <karlcow> | just to correct the fact |
| 19:00 | <annevk> | Hixie, blog.whatwg.org/wp-admin/ |
| 19:00 | <Hixie> | mattmay: not sure what you mean. We never called the WHATWG spec "HTML5" until the W3C did; the spec was called "Web Applications 1.0" (and still is -- http://whatwg.org/C). We're just talking about the spec that's a subset of the WHATWG work that is a suerpset of the W3C HTML5 work |
| 19:00 | <Hixie> | annevk: thanks |
| 19:00 | <mattmay> | Karlcow: beat me to it. Stupid Android keyboard. |
| 19:00 | <annevk> | hey, great you joined mattmay! |
| 19:01 | annevk | was having dinner |
| 19:02 | <alcuadrado> | so great news Hixie :) and thanks you all for your work guys. see ya |
| 19:02 | <gsnedders> | PlayerNaN: Browsers implement a single mode, regardless of version, pretty much. There's minor differences between quirks/no-quirks, but that's it. Almost all that affects is at a CSS level. |
| 19:02 | <Hixie> | PlayerNaN: yeah, sounds like it |
| 19:04 | <mattmay> | Yeah, I get that. But that also uses the most general term available. You're using the term which is the abstract representation of the web's core language to define one spec. |
| 19:04 | <mattmay> | Which seems short-sighted. |
| 19:04 | <gsnedders> | mattmay: I guess the point is the spec is meant to be continually evolving, much like the impls |
| 19:04 | <Hixie> | HTML isn't the abstract representation of the web's core language, it IS the web's core language |
| 19:04 | <mattmay> | annevk: Yeah, and from a tablet, no less. |
| 19:05 | <PlayerNaN> | I see no problem in just changing the name to html. One spec ftw! |
| 19:05 | <mattmay> | @PlayerNaN: that's the problem. There isn't "one spec". |
| 19:06 | <karlcow> | maybe I found a name for this unversioned Web kitchen sink - WIG = Web Implementation Guide |
| 19:06 | <annevk> | mattmay, shouldn't the core spec be called HTML? |
| 19:06 | <Ms2ger> | mattmay, of course there is |
| 19:06 | <Hixie> | the spec isn't one version of the spec, the whole point of the WHATWG spec is that it is the continuously-maintained spec of the HTML language |
| 19:06 | <mattmay> | karlcow: WIG? You've put a name to my secret shame. |
| 19:09 | <karlcow> | I had to wig him for not implementing properly his web site. |
| 19:09 | <karlcow> | let's put a wig on our HTTP head |
| 19:09 | <karlcow> | we could all wig out too. |
| 19:13 | <mattmay> | Ya know, marketing may annoy you, but it does get people paying attention. |
| 19:16 | <Hixie> | people seem to be paying attention :-) |
| 19:17 | <mattmay> | Do you think you'll benefit from people saying they're using "HTML"? |
| 19:17 | <Hixie> | i don't care about benefitting personally |
| 19:17 | <Hixie> | the goal here is to improve the web |
| 19:18 | <mattmay> | Google it. First page is outdated crap, the kind of practices you hate. They're stale, and they won't go away anytime soon. |
| 19:18 | <Hixie> | so? |
| 19:18 | <Hixie> | why would you google "html"? |
| 19:19 | <mattmay> | At least with HTML5, marketing aside, you have a fresh start. Actually seems to be working. |
| 19:19 | <Ms2ger> | There's no fresh start |
| 19:19 | <Hixie> | "HTML5" according to the W3C means all kinds of stuff including CSS, so it hardly seems like either a fresh start, nor to be working. |
| 19:19 | <mattmay> | Don't ask me. You're the one with the data. But I bet it's searched more than HTML5. |
| 19:20 | <Hixie> | well if it's searched more, all the more reason to use the term :-) |
| 19:20 | <mattmay> | I disagree with that, too. But they need to fix their messaging. You don't need to change yours. |
| 19:21 | <Hixie> | we're not changing messaging |
| 19:21 | <Hixie> | we're just clarifying what the spec defines |
| 19:21 | <mattmay> | It's not what people search to find the spec. That's my point. |
| 19:21 | <Hixie> | i thought you said you had no data on that |
| 19:21 | <ben_c> | I think some people are scared off by HTML5 thinking it's something special so they just go and learn 'standard html', so hopefully the name change will help that |
| 19:21 | <mattmay> | HTML is a more general term than the spec. |
| 19:21 | <Hixie> | HTML5 is a more general term than the spec. |
| 19:22 | <Hixie> | at least HTML is more accurate :-) |
| 19:22 | <hsivonen> | Hixie: chances are that droppin "5" will be toxic like the 2022 thing |
| 19:22 | <mattmay> | Even more accurate is "WHATWG HTML" |
| 19:22 | <hsivonen> | Hixie: I think it's better to keep the title of the WHATWG spec |
| 19:22 | <gsnedders> | Language is inherently transient, and everything will change meaning over time. |
| 19:23 | <gsnedders> | But my general thoughts are much what hsivonen just said |
| 19:25 | <othermaciej> | it's probably true that s/HTML5/HTML/ is more likely to create bad PR than good PR, if anyone even notices |
| 19:26 | <roc> | wow, metservice.co.nz is using canvas for graphs now |
| 19:26 | <Hixie> | so far the response from the twitter question has been almost uniformly positive, to the level of getting people coming here to say so. |
| 19:26 | <jamesr_> | they just made the 5 icon and everything |
| 19:26 | <espadrine> | Is this switch intended for the non-spec community? |
| 19:27 | <karlcow> | I do not think it is a good idea to call it html as well. fwiw |
| 19:27 | <mattmay> | Well, except me. |
| 19:29 | karlcow | wonders if the French grammar is making it obscure: "It is a bad idea to rename it HTML" (what I meant) |
| 19:29 | <Hixie> | hsivonen: well there's always a risk, but i don't see how... could you elaborate on how it could be toxic? |
| 19:30 | <othermaciej> | I think the most likely outcome is not much notice taken of the move beyond insiders |
| 19:30 | <Hixie> | indeed |
| 19:30 | <Hixie> | espadrine: we're working on a (well, ben is working on a) developers.whatwg.org version of the spec which will likely remain "HTML5" for the time being, it's up to him |
| 19:30 | <othermaciej> | probably small chance of someone spinning it into a linkbait shitstorm |
| 19:32 | <espadrine> | Hixie: then this change won't affect many people. |
| 19:32 | <espadrine> | God, http://developers.whatwg.org/ looks nice! |
| 19:33 | <Hixie> | espadrine: we're working on a (well, ben is working on a) developers.whatwg.org version of the spec which will likely remain "HTML5" for the time being, it's up to him |
| 19:34 | <Hixie> | oops |
| 19:34 | <Hixie> | didn't mean to say that twice :-) |
| 19:34 | <Hixie> | espadrine: yeah, ben's got a good eye for design :-) |
| 19:35 | <mattmay> | So how would a dev express that they're using the most modern technology? "You guys! We support HTML!" "Oh, great. My nephew did that like 10 years ago." |
| 19:36 | <TabAtkins> | "HTML and CSS and shit" |
| 19:36 | <Hixie> | wtf, i'm getting hits for http://whatwg.org/specs/web-apps/current-work/multipage/hfavicon.ico and http://whatwg.org/specs/web-apps/current-work/multipage/tfavicon.ico and so on for all characters in the set [dhtml5] |
| 19:36 | <Rik`> | what about calling it "HTML Level 5" ? |
| 19:36 | <espadrine> | If you want to impress, do use HTML5. Otherwise, you're talking about the spec! ^^ |
| 19:36 | <TabAtkins> | "you know, all that cool technology stuff they're doing today" |
| 19:36 | <TabAtkins> | "i dunno" |
| 19:36 | <Ms2ger> | Rik`, the point is that there's no levels |
| 19:37 | <Hixie> | Rik`: as Ms2ger says, the point is that there's just one continuously maintained spec with no versions, levels, etc. |
| 19:37 | <Hixie> | mattmay: "HTML5" started 7 years ago, so that's hardly any better. |
| 19:37 | <Ms2ger> | WA1 started then ;) |
| 19:37 | <Rik`> | just trying to mimic CSS |
| 19:37 | <Hixie> | WA1 still exists :-) |
| 19:38 | <mattmay> | It's about 14 years better. ;) |
| 19:38 | <Ms2ger> | Well, mimicking CSS specs is hardly something I'd recommend |
| 19:38 | <Ms2ger> | (Hi Tab!) |
| 19:41 | <mattmay> | HTML Infinity! |
| 19:41 | <karlcow> | HTML∞ in this case |
| 19:42 | <mattmay> | Yeah, couldn't see that on my virtual kbd. :) |
| 19:43 | <Rik`> | Hixie: how can it be one continuously maintained spec ? |
| 19:43 | <mattmay> | That'd be hell to search for. |
| 19:43 | <Rik`> | isn't it supposed to be done by 2022 ? |
| 19:43 | <Ms2ger> | No |
| 19:43 | <Ms2ger> | The W3C will publish a snapshot of 2010's HTML by then |
| 19:44 | <bfrohs> | I can definitely get behind changing the name of the spec to HTML. It would not only make sense to us veterans, but also help beginners realize there is only one HTML spec that should be followed. |
| 19:44 | <espadrine> | Ecmascript people do quite the same. They name their current compilation of handsome features Harmony, and they will name it ES6 when people are fed up with ES5. |
| 19:45 | <mattmay> | bfrohs: except... there's not... |
| 19:45 | <karlcow> | http://musiclub.web.cern.ch/MusiClub/bands/cernettes/firstband.html |
| 19:45 | <karlcow> | "How was I to know that I was passing an historical milestone, as the one above was the first picture ever to be clicked on in a web browser!" |
| 19:45 | <mattmay> | And imagine the crap you'd find if you started to look for an HTML tutorial on a search engine. Not to mention a bookstore. |
| 19:48 | <hsivonen> | Hixie: HTML5 has brand value that you are about to abandon |
| 19:51 | <espadrine> | hsivonen: The way I see it, HTML5 already didn't mean "the current HTML spec" in the journalistic world. |
| 19:54 | <mattmay> | espadrine: Imagine trying to get those same journalists excited about "HTML". They'll say, "HTML? Meh. That's not new." |
| 19:55 | <mattmay> | Can't wait to hear about the first person who asks us if Dreamweaver supports HTML. |
| 19:56 | <espadrine> | mattmay: When we'll need journalists to get excited, we will say: "we are designing HTML6". That should impress them. |
| 19:56 | <espadrine> | (Wow, 6 is bigger than 5! It must be better then!) |
| 19:57 | <bfrohs> | mattmay: HTML5 has come to define 'the latest web technologies', not HTML itself. The term will still remain in use in media [and when we're pitching to others ;)] |
| 19:57 | <Philip`> | HTML6 is too similar to HTML5 to become a new buzzword |
| 19:57 | <mattmay> | And five seconds later, marketers will steal that, too. |
| 19:58 | <Philip`> | People like totally fresh buzzwords (DHTML, XHTML, AJAX, Web 2.0, HTML5, etc) |
| 19:58 | <bfrohs> | Philip`: HTML∞ for the next version then ;) |
| 19:58 | <Philip`> | and predicting the next one seems hard |
| 19:59 | <espadrine> | bfrohs: yes, but how would we name the next iteration then? How would we impress people after HTML Infinity? |
| 20:00 | <Ms2ger> | Aleph-one |
| 20:00 | <bfrohs> | espadrine: Someone will come up with something else that's catchy -- they always do (like Philip` just mentioned) |
| 20:00 | <espadrine> | Ms2ger: That's actually bold! |
| 20:01 | <TabAtkins> | Can anyone who knows japanese tell me if this is a spammy account or not? |
| 20:01 | <TabAtkins> | http://twitter.com/#!/insidetaka30 |
| 20:02 | <karlcow> | I wonder if the question comes now to is there any chances that Hixie accepts to not rename HTML5 as HTML. If the answer is yes then there is value in the discussion, if it is a "no, my own decision" then no point argueing with made decisions |
| 20:03 | <espadrine> | karlcow: we may argue about how to handle side-effects, I guess. |
| 20:04 | <bfrohs> | karlcow: Even if Hixie has his mind made up atm, arguments that have yet to be presented may change his mind -- He's handled everything else quite well so far; I doubt this would be an exception to that :) |
| 20:05 | <karlcow> | I beg to have a different opinion (which doesn't matter) :) |
| 20:10 | <MikeSmith> | TabAtkins: not spam |
| 20:11 | <TabAtkins> | MikeSmith: Thanks. I keep my follower list clean, and I just can't tell sometimes with the japanese followers. |
| 20:14 | <MikeSmith> | TabAtkins: yeah, I do a lot of blocking too |
| 20:14 | <MikeSmith> | but that one looks like somebody who probably has genuine interest in your tweets |
| 20:15 | <MikeSmith> | though you never can tell |
| 20:16 | <MikeSmith> | the spammy ones getting hard to detect |
| 20:17 | <TabAtkins> | That's all I need. |
| 20:24 | <Hixie> | hsivonen: yeah, that was the reason to keep the name before, but i'm not sure it really matters anymore given recent developments |
| 20:25 | <Hixie> | Rik`: we abandoned the timeline a while back. The stuff that went to LC in 2009 will probably be all stably implemented in 2022, but we've moved on to new stuff too since then as well. The spec will never be "done" unless it's also "abandoned". |
| 20:27 | <annevk> | I don't really see the big deal either. |
| 20:28 | <annevk> | "html spec" will probably give one of the versions of HTML back in due course... |
| 20:28 | <annevk> | And if you want to talk about it you probably want to talk about a specific feature. And if it's just the general idea you could use HTML5, which are both happening already. |
| 20:28 | <Hixie> | "html spec" on google returns html4, then the editor's draft of w3c html5 |
| 20:29 | <Hixie> | and a bit below that the whatwg specs page |
| 20:29 | <Hixie> | (and in between... html 3.2) |
| 20:29 | <annevk> | that seems good enough |
| 20:30 | <annevk> | and on w3.org we've yet to claim w3.org/TR/html/ |
| 20:30 | <annevk> | which surely should point to it |
| 20:31 | <Ms2ger> | That should point to the XHTML2 note, certainly! |
| 20:32 | <Hixie> | wtf, why am i getting so many hits for things like specs/web-apps/current-work/multipage/lfavicon.ico |
| 20:34 | <annevk> | Hixie, maybe because of http://dhtml5.com/ |
| 20:34 | <Hixie> | ooh, maybe |
| 20:34 | Hixie | checks logs |
| 20:34 | <Ms2ger> | <link rel="icon" href="http://dhtml5.com/5favicon.ico">; |
| 20:35 | <annevk> | but also see the base URL |
| 20:35 | <annevk> | that combined with bogus software |
| 20:35 | <Hixie> | yup, that's it |
| 20:36 | <Hixie> | firefix and chrome |
| 20:36 | <Ms2ger> | Oh, good it isn't Firefox ;) |
| 20:36 | <annevk> | miketaylr, ^^ |
| 20:36 | <miketaylr> | aye, fixed that |
| 20:36 | <miketaylr> | :/ sry |
| 20:36 | <annevk> | it's not really your fault I think |
| 20:36 | <miketaylr> | <base> got me. |
| 20:37 | <Hixie> | and opera |
| 20:37 | <Hixie> | i don't understand what the browsers are doing |
| 20:37 | <Ms2ger> | Check the spec? ;) |
| 20:37 | <miketaylr> | someone put dhtml5.com on hacker news so it got a zillion hits |
| 20:38 | <Hixie> | i see nothing here that should result in these hits |
| 20:38 | <annevk> | miketaylr, what did you change? |
| 20:38 | <annevk> | if you changed anything |
| 20:39 | <Ms2ger> | File a bug, Hixie will figure it out |
| 20:39 | <Ms2ger> | Oh wait |
| 20:39 | <miketaylr> | the favicon was a relative URI before, i changed it to be absolute (had forgotten about <base> for the links) |
| 20:39 | <miketaylr> | so i think it was me |
| 20:39 | <annevk> | aah, and it also changes? |
| 20:39 | <miketaylr> | it used too :P |
| 20:40 | <annevk> | then it makes sense :) |
| 20:40 | <Hixie> | what was the relative url before? |
| 20:40 | <Hixie> | aaah |
| 20:40 | <Hixie> | ok |
| 20:40 | <Hixie> | that all makes sense |
| 20:40 | <Hixie> | thanks |
| 20:40 | <annevk> | we should maybe have something in the spec about favicons... |
| 20:40 | <Hixie> | we do, don't we? |
| 20:40 | <miketaylr> | it was just /dfavicon.ico, etc. then some silly script to loop through [dhtml5]favicon.ico, etc. |
| 20:40 | <annevk> | like if there's no rel=icon you may attempt to fetch /favicon.ico |
| 20:41 | <Hixie> | can't that be a cssom issue? :-) |
| 20:41 | <annevk> | you define page loading :) |
| 20:41 | <annevk> | and icons are content |
| 20:41 | <Ms2ger> | DOM Core ;) |
| 20:42 | <annevk> | fffffffuuuuu |
| 20:43 | <Hixie> | hey if you want this in DOM Core, i ain't stopping you |
| 20:43 | <Hixie> | http://www.w3.org/Bugs/Public/show_bug.cgi?id=11815 |
| 20:43 | <Hixie> | someone cc julian on that bug, i'm sure he'll want to escalate it |
| 20:44 | <Hixie> | so what should i blog when i do this name change |
| 20:45 | <Hixie> | specifically, what should the title be |
| 20:45 | <Ms2ger> | "This really doesn't change anything, but hey" |
| 20:45 | <annevk> | I think you should explain "Living Standard" and that we moved on from "Last Call" if you are going to break the news |
| 20:45 | <annevk> | I'm not sure we have done that clearly so far |
| 20:46 | <bfrohs> | "One Acronym to Rule Them All"? :) |
| 20:46 | <annevk> | i.e. explain that we changed the process and that as a result we also changed the name |
| 20:46 | <Hixie> | k |
| 20:46 | <Hixie> | i like how in http://lists.w3.org/Archives/Public/public-html/2011Jan/0239.html the summary is lnger than the rationale and details put together |
| 20:47 | <Ms2ger> | I like how I ignore that list :) |
| 20:47 | <karlcow> | living standard is an interesting turn of language. |
| 20:47 | <annevk> | I have no idea for a good title though :) |
| 20:47 | <beowulf> | so, is the purpose of the renaming to give over the marketing term HTML5 to be purely marketing? |
| 20:48 | <Hixie> | the purpose of renaming is primarily accuracy |
| 20:48 | <annevk> | no, it's because there are no versions of HTML |
| 20:48 | <annevk> | there's one document for all of them |
| 20:48 | <annevk> | or for it, really :) |
| 20:49 | <beowulf> | yeah, but the term HTML5 won't go way as a result, so it'll come to mean something else, no? |
| 20:49 | <karlcow> | annevk: living specification would be more right than living standard |
| 20:49 | <Hixie> | we did it last year but adactio suggested he could still get some mileage out of the term "html5" in advocacy, but with the w3c making the term essentially meaningless now, he agrees that "html" is a better word to describe the html spec. |
| 20:49 | <beowulf> | i'm all for it, though |
| 20:49 | <annevk> | karlcow, people call it a web standard |
| 20:50 | <annevk> | karlcow, it's a different kind of standard, but "living" should indicate that |
| 20:50 | <Hixie> | ok i'm submitting http://wiki.whatwg.org/wiki/Change_Proposal_for_ISSUE-120 (i got rid of the childish stuff) |
| 20:51 | <karlcow> | living standards sound bio-hazard :) there is nothing permanent. |
| 20:51 | <annevk> | beowulf, depending on whether the HTML WG renames the draft it might end up meaning various things |
| 20:51 | <annevk> | beowulf, well, and given a timeline it means various things too |
| 20:51 | <annevk> | beowulf, e.g. there used to be a substantive difference between HTML5 and HTML 5 |
| 20:51 | <karlcow> | living spec is better IMHO. :) |
| 20:51 | <Hixie> | yeah i never understood that |
| 20:52 | <Hixie> | the crazy lengths people have gone to to try to come up with rationales for the space or lack thereof is pretty crazy |
| 20:52 | beowulf | nods |
| 20:52 | <karlcow> | HTML­5 |
| 20:53 | <Ms2ger> | ‌ |
| 20:53 | <Workshiva> | Use a vertical tab |
| 20:53 | <Workshiva> | Then people can disagree about whether there's a space or not |
| 20:53 | <Hixie> | or a form feed |
| 20:53 | <beowulf> | HTML 5 |
| 20:54 | <Hixie> | see with no "5" all these problems go away too! |
| 20:54 | <Workshiva> | HT ML |
| 20:54 | <Hixie> | except... will people think we've renamed it to "HTML "? |
| 20:54 | Workshiva | starts a new H.T.M.L. faction |
| 20:54 | <Hixie> | oh no, people will argue about whether it's "HTML" or "HTML "... |
| 20:54 | <karlcow> | which length for space? |
| 20:54 | Philip` | hates being unable to decide whether to say "HTML 5" or "HTML5", and an arbitrary unnecessary substantive difference is a good way to allow decisiveness without rejecting either of the terms |
| 20:55 | <Hixie> | not sure what "arbitrary unnecessary substantive difference" refers to |
| 20:55 | <Hixie> | oh, i get it |
| 20:55 | <Hixie> | nevermind |
| 20:55 | <Philip`> | Like the language vs syntax difference |
| 20:55 | <Workshiva> | What is the alphabet of HTML? Discuss |
| 20:56 | <karlcow> | unicode 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 200A 200B are all kind of spaces |
| 20:57 | <beowulf> | ah, 2001. a fine space. |
| 20:57 | <Workshiva> | 200C was omitted because we won't need to count that high |
| 20:57 | <karlcow> | zero width non-joiner for 200C |
| 20:59 | <Ms2ger> | The question is, which spaces are semantic? |
| 21:00 | <annevk> | difficult problems -- not so much discussion; simple problems -- lots of discussion |
| 21:03 | <annevk> | I missed this somehow |
| 21:03 | <annevk> | Mark Pilgrim removed the space again on diveintohtml5.org |
| 21:03 | <annevk> | It did not matter to search engines after all? |
| 21:04 | <karlcow> | space quest |
| 21:20 | <jacobolus> | I went by the bookstore a few days ago, and noticed that the dead tree version of Mark Pilgrim’s book is missing the cute pictures. :( |
| 21:21 | <jacobolus> | I propose instead of HTML5, maybe add some typographical flourishes instead. Maybe ❧HTML❧ |
| 21:22 | <jacobolus> | or HTML➽ |
| 21:22 | <jacobolus> | (everyone needs a HEAVY WEDGE-TAILED RIGHTWARDS ARROW now and then) |
| 21:22 | <annevk> | I suggest we use the Unicode sign for beer then |
| 21:23 | <Hixie> | annevk: i wrote a blog post, can you take a look and add whatever you think makes sense and post it? :-) |
| 21:23 | annevk | looks |
| 21:23 | <Hixie> | the name change is live |
| 21:24 | <espadrine> | Hixie: good! By the way, where is the blog post? |
| 21:25 | <Hixie> | annevk's reviewing it |
| 21:25 | <Hixie> | it'll be on blog.whatwg.org |
| 21:25 | <Hixie> | http://www.whatwg.org/specs/web-apps/current-work/ - i changed the <h1> font size... too big? :-) |
| 21:26 | <TabAtkins> | No? |
| 21:26 | <jacobolus> | looks good |
| 21:26 | <annevk> | looks good |
| 21:26 | annevk | hits publish |
| 21:28 | <jacobolus> | Hixie: if you want to get especially fancy (and make it slightly more readable) you could add about 1-2 pixels of letter-spacing |
| 21:28 | <annevk> | twitter is updated as well, plugin appears to be working |
| 21:28 | <jacobolus> | bold all-caps works best in my experience w/ a tiny bit of extra space |
| 21:29 | <karlcow> | http://www.google.com/search?q=%22Living+Standard%22 … |
| 21:30 | <karlcow> | now we got the hate of Monocle, The Economist, Financial Times, etc. |
| 21:30 | <Hixie> | jacobolus: is it better now? |
| 21:30 | <Hixie> | how about the date, is it better like on http://www.whatwg.org/specs/web-apps/current-work/multipage/ or on http://www.whatwg.org/specs/web-apps/current-work/ ? |
| 21:30 | <annevk> | at least my social circle knows what it means :p |
| 21:30 | <Hixie> | (ignore the missing whitespace on the first one, that's a bug) |
| 21:31 | <karlcow> | annevk: ;) |
| 21:31 | <jacobolus> | Hixie: ooh, I like it :) |
| 21:31 | <beowulf> | general style guidelines are that a little letter spacing on all caps is good form |
| 21:32 | <Hixie> | i think it might be better on the h2 line after all |
| 21:33 | <espadrine> | Hixie: I like it too! Although I'd like HTML serif. |
| 21:33 | <espadrine> | (the heading only) |
| 21:33 | <jacobolus> | espadrine: why? the whole rest of the spec uses the same typeface throughout |
| 21:33 | <Hixie> | serifs are the style at http://developers.whatwg.org/ |
| 21:34 | <espadrine> | I've tested it, it looks nice... |
| 21:34 | <Hixie> | i think we're going to stick to sans-serif on the normative spec to keep it distinct |
| 21:34 | <jacobolus> | Hixie: by the way, developers.whatwg looks great, but the monospace text in it renders a bit smaller than the rest |
| 21:34 | <Hixie> | file an issue and ben will fix it -- there's a link at the top iirc |
| 21:35 | <jacobolus> | not seeing the link |
| 21:35 | <Hixie> | at the bottom of the front page |
| 21:35 | <jacobolus> | oh, at the bottom :) |
| 21:35 | <Hixie> | search for "issues" |
| 21:35 | <jacobolus> | yep, see it |
| 21:35 | <Hixie> | yeah sorry he moved it :-) |
| 21:35 | <annevk> | Hixie, is there a way you can not ping the tweet bot when you are not changing "source"? if it's hard never mind btw |
| 21:35 | <annevk> | i.e. only ping when you change source |
| 21:36 | <Hixie> | hmm |
| 21:36 | <annevk> | you get empty result sets otherwise |
| 21:36 | <Hixie> | oh i guess you still got a rev huh |
| 21:36 | <annevk> | right |
| 21:36 | <Hixie> | because i changed the index |
| 21:36 | <Hixie> | hmm |
| 21:36 | <Hixie> | yeah, hold on one sec just finishing this date thing then i'll look at it |
| 21:37 | <espadrine> | Oh, and we forgot the logo! |
| 21:37 | <espadrine> | (never mind the joke) |
| 21:39 | <TabAtkins> | I like the "Living Standard - [date]" form. |
| 21:39 | <Hixie> | TabAtkins: reload, what do you think of it now? |
| 21:39 | <jacobolus> | Hixie: https://github.com/benschwarz/developers.whatwg.org/issues/issue/17 |
| 21:39 | <Hixie> | oops i broke the style |
| 21:39 | <TabAtkins> | Yeah, that's fine too. |
| 21:40 | <TabAtkins> | Actually, a little more space between the first paragraph and the list of versions would be good. |
| 21:40 | <Hixie> | yeah that was what i broke |
| 21:40 | <Hixie> | fixed |
| 21:40 | <TabAtkins> | Oh, I liked the first paragraph butting up against the headings. |
| 21:40 | <jacobolus> | benschwarz: otherwise, congrats, developers.whatwg.org looks great |
| 21:40 | <annevk> | lgtm |
| 21:41 | <Hixie> | TabAtkins: let me deal with anne's tweet thing then i'll take a look |
| 21:41 | <Hixie> | actually, let me get lunch first. then tweet. then spacing. |
| 21:41 | <Hixie> | bbiab |
| 21:41 | <beowulf> | i like it how it is now |
| 21:41 | <espadrine> | I don't fully know how it is designed, but the copyright goes from 2004 to 2010. Should it be 2011? |
| 21:43 | <jacobolus> | benschwarz: hmm, actually, one other thing: I'm not convinced about the gray italicized sections. The gray on white is a bit low contrast |
| 21:43 | <adactio> | I've gotta say, I'd rather the document were called "HTML (including next generation additions still in development)" ...less of a jump from the previous "HTML5 (including next generation additions still in development)" |
| 21:43 | <jacobolus> | I always thought the parenthesized bit in the title was cheesy, FWIW |
| 21:44 | <TabAtkins> | Me too. |
| 21:44 | <Workshiva> | HTML (including HTML additions currently in development) |
| 21:46 | <annevk> | espadrine, yes |
| 21:46 | <annevk> | Hixie, espadrine points out the copyright line is out of date |
| 21:47 | <annevk> | Hixie, still 2010 |
| 21:47 | <jacobolus> | hmm, okay, another issue: code samples in developers.whatwg.org don't keep their indentation |
| 21:48 | <jacobolus> | for example compare http://developers.whatwg.org/urls.html#domstringmap-0 to http://developers.whatwg.org/urls.html#domstringmap-0 |
| 21:51 | <jacobolus> | https://github.com/benschwarz/developers.whatwg.org/issues/#issue/18 |
| 21:54 | <jacobolus> | Hixie: oh, btw, don't include the extra letter-spacing in the h1 at http://whatwg.org/C |
| 21:55 | <jacobolus> | letter-spaced lowercase is ugly |
| 21:56 | <jacobolus> | especially since many browsers don't do any proper kerning, so We had too much space already |
| 21:57 | <espadrine> | Good news, Bespin dropped the use of canvas! |
| 21:58 | <othermaciej> | whoah |
| 21:58 | <annevk> | Curious: were they lobbied by the accessibility community or the semantic markup community? |
| 22:00 | <miketaylr> | they just merged with that other cloud ide thing today, right? |
| 22:00 | <espadrine> | miketaylr: pretty much! ^^ |
| 22:00 | <miketaylr> | ah yes, https://mozillalabs.com/skywriter/2011/01/18/mozilla-skywriter-has-been-merged-into-ace/ |
| 22:03 | <espadrine> | That's odd, I can't paste stuff in it. |
| 22:03 | <espadrine> | bah. |
| 22:03 | <jamesr_> | cool |
| 22:04 | <annevk> | http://ajaxorg.github.com/ace/editor-build.html has demo |
| 22:04 | <annevk> | it is somewhat broken, but I have to say I have been waiting for something like this |
| 22:04 | <espadrine> | Yep, pasting doesn't work. |
| 22:05 | <annevk> | shift-9 does not work for me, which is quite severe limitation |
| 22:06 | <Philip`> | annevk: Here's one you can copy-and-paste: ( |
| 22:06 | <espadrine> | wow, pasting is actually done through shift-9 + ctrl-V! |
| 22:06 | Philip` | tends to use the copy-and-paste strategy whenever he needs a # on an Apple machine |
| 22:06 | <annevk> | :) |
| 22:08 | <benschwarz> | Ok. Here for real now. |
| 22:10 | <benschwarz> | jacobolus: Thanks for logging the issues |
| 22:17 | <jacobolus> | np |
| 22:18 | <jacobolus> | Hixie: actually, I think you might want to leave the size of the H1 at http://whatwg.org/C a bit smaller too |
| 22:19 | <jacobolus> | (that is, beyond just leaving default letter-spacing) |
| 22:19 | <jacobolus> | benschwarz: should I add an issue for "make gray text a bit darker" too? |
| 22:19 | <annevk> | jacobolus, but other than that it is perfect? :) |
| 22:19 | <benschwarz> | jacobolus: those code and example things are on my list today already |
| 22:20 | <benschwarz> | I made the example style, without realising how overused it is in the spec ;) |
| 22:20 | <jacobolus> | annevk: well it's a living document, so it's always going to be perfect, right? |
| 22:22 | <annevk> | prolly a little less than the degree to which humans are perfect |
| 22:23 | <annevk> | tracking WHATWG on twitter at this point is getting kind of hairy |
| 22:23 | <annevk> | too much results |
| 22:26 | <frenzz> | http://blog.whatwg.org/html-is-the-new-html5 what actually that means ? |
| 22:27 | <jacobolus> | espadrine: I like your HTML5^H. That's cute |
| 22:27 | <annevk> | frenzz, Hixie tried to explain it in the blog post |
| 22:29 | <annevk> | frenzz, simply put, the way we develop standards changed; rather than issuing a new version every couple of years we release a new version every day, sometimes multiple times a day |
| 22:29 | <benschwarz> | Hixie: Holla! |
| 22:33 | <jacobolus> | annevk: I like a tweet from an hour ago, “Version numbers? Where we're going, we don't need version numbers.” |
| 22:36 | <annevk> | This is one of the reasons I mention when people ask why the WHATWG still exists. (Aside from the large community.) Because we are much smaller it is a lot easier to break new ground. |
| 22:38 | <annevk> | For a lot of reasons this would be nigh-on impossible at the W3C or IETF. Though I should say that the W3C these days has editor's draft which are a big step up. And steps are taken to make it more clear TR/ editions are snapshots. |
| 22:40 | <Hixie> | back |
| 22:40 | <annevk> | Hixie, might need to allocate more RAM or something, it seems we have been Grubered |
| 22:40 | <Hixie> | let me deal with anne's tweet thing and then i'll look at other stuff |
| 22:40 | <Hixie> | ok let me deal with ram first THEN the tweet thing THEN the styles |
| 22:42 | <Hixie> | ok i've reduced the number of apache instances that can run at once, that should prevent it from DOSing itself |
| 22:43 | <Hixie> | now the tweet thing |
| 22:43 | <ben_c> | Does the blog have a caching plugin or anything running on it? |
| 22:44 | <annevk> | it had, but that was broken |
| 22:44 | <annevk> | I didn't get around to trying something new |
| 22:45 | <ben_c> | which one were you using? I've got WP Super Cache on my site and it works ridiculously well |
| 22:45 | <Hixie> | ok tweet thing is done, shouldn't send you things unless .../source changes |
| 22:45 | <ben_c> | although that also broke and I had to dig around fixing it |
| 22:45 | <Hixie> | who was talking about letter-spacing |
| 22:46 | <Hixie> | jacobolus: should http://www.whatwg.org/specs/web-apps/current-work/webvtt.html be uppercase? |
| 22:46 | <heycam> | Hixie, your data uri kitchen seems to be working kind of slow at the moment |
| 22:46 | <Hixie> | heycam: yeah apparently whatwg.org blog is popularer than we thought |
| 22:46 | <heycam> | ah :) |
| 22:47 | <Hixie> | jacobolus: s/uppercase/have letter spacing/ |
| 22:47 | <Hixie> | heycam: should still be working at least |
| 22:47 | <jacobolus> | Hixie: just in general, if you have all caps it looks better with a tiny bit of letter-spacing, and if you have not-all-caps, it looks better without |
| 22:47 | <heycam> | timed out for me just then |
| 22:47 | <Hixie> | heycam: huh |
| 22:49 | <Hixie> | the machine has ram free and cpu idle, it should be ok |
| 22:49 | <Hixie> | i mean, it's busy, but not overloaded |
| 22:49 | <Hixie> | try now? |
| 22:50 | <Hixie> | jacobolus: k, so, no letter-spacing on the WebVTT one? |
| 22:51 | <jacobolus> | Hixie: here's bringhurst: "2.1.6 Letterspace all strings of capitals and small caps, and all long strings of digits // 2.1.7 Don't letterspace the lower case without a reason" |
| 22:51 | <heycam> | Hixie, worked that time. (took maybe 20 seconds tho.) |
| 22:51 | <jacobolus> | half-capitalized half-uncapitalized words look ugly no matter what you do to them; I wouldn't add extra space though |
| 22:52 | <Hixie> | heycam: yeah, there's a lot of traffic. |
| 22:52 | <Hixie> | jacobolus: k |
| 22:53 | <Hixie> | i can also just make it smallcaps |
| 22:53 | <annevk> | I will look into caching plugins tomorrow for when we make the next announcement o_O |
| 22:53 | <annevk> | I did not quite anticipate this |
| 22:53 | <Hixie> | hehe |
| 22:53 | <jacobolus> | (also note, I'm not really an expert typographer by any stretch of the imagination) |
| 22:54 | <benschwarz> | jacobolus: capital lines should always be letterspaced |
| 22:54 | Hixie | restarts the server with a few more simultaneous connections allowed |
| 22:54 | <benschwarz> | but they should be avoided where possible |
| 22:55 | <jacobolus> | benschwarz: yeah, but what about the word WebVVT |
| 22:55 | <jacobolus> | er, WebVTT |
| 22:55 | <benschwarz> | jacobolus: is it a title? |
| 22:55 | <Hixie> | how about http://www.whatwg.org/specs/web-apps/current-work/webvtt.html ? |
| 22:55 | <Hixie> | (now smallcaps) |
| 22:55 | <jacobolus> | benschwarz: ↑ |
| 22:56 | <Hixie> | http://www.whatwg.org/specs/web-apps/current-work/complete/ is small caps too now |
| 22:56 | <benschwarz> | sever is getting too smashed, I think |
| 22:57 | <Hixie> | yeah it's a bit slow to load these giant specs |
| 22:57 | <Hixie> | gotta say, though, the server is handling this way better than last time we got a lot of traffic |
| 22:57 | <Hixie> | and given that it's basically free... can't complain |
| 22:58 | <Hixie> | is it me or is the h2 on http://www.whatwg.org/specs/web-apps/current-work/multipage/ a different font or something than the h2 on http://www.whatwg.org/specs/web-apps/current-work/complete/ ??? |
| 22:58 | <Hixie> | it's the same style sheet... |
| 22:58 | <Hixie> | different top margin, too |
| 22:58 | <Hixie> | wtf |
| 22:58 | <jacobolus> | Hixie: those are loading slow enough that I can't tell you if they're different :) |
| 22:59 | <TabAtkins> | It's just you. |
| 22:59 | <TabAtkins> | I don't see different top margins either. Clear your cache? |
| 23:00 | <benschwarz> | jacobolus: hmm, I'd keep it regular case. The kerning on the We is way off though |
| 23:00 | <jacobolus> | Hixie: I'm not a big fan of the mix of big and small caps there |
| 23:01 | <jacobolus> | benschwarz, Hixie: maybe add the "render this with kerning" CSS for h1s and h2s? |
| 23:01 | <jacobolus> | then the We won't get so much space |
| 23:01 | <benschwarz> | jacobolus: yeah, thats what I stuck into my inspector :) |
| 23:02 | <jacobolus> | what's the special css for that? |
| 23:02 | <benschwarz> | https://skitch.com/benschwarz/rkg4x/webvtt |
| 23:02 | <jacobolus> | I think firefox does kerning properly regardless these days, no? |
| 23:02 | <benschwarz> | jacobolus: it always has |
| 23:02 | <jacobolus> | well, always since FF3 or something |
| 23:02 | <roc> | yeah, since FF3 |
| 23:03 | <jacobolus> | and safari takes the explicit css flag? |
| 23:03 | <Hixie> | what's the magic css to make the browsers slower again? |
| 23:03 | <benschwarz> | jacobolus: yes |
| 23:03 | <TabAtkins> | use ~ combinators? |
| 23:03 | <roc> | text-rendering:optimizeLegibility |
| 23:03 | <Hixie> | thanks |
| 23:03 | <roc> | actually I'm wrong |
| 23:03 | <benschwarz> | Hixie: see the skitch :) |
| 23:03 | <Hixie> | yeah i saw it after asking :-) |
| 23:03 | <roc> | In FF3 we did not do kerning on Windows and X below certain font sizes (20px) |
| 23:04 | <TabAtkins> | Add a "* ~ * * ~ * * ~ * {}" block to your document. |
| 23:04 | <benschwarz> | FF3 came out forever ago, seemingly |
| 23:04 | <roc> | in FF4 we do kerning always |
| 23:04 | <TabAtkins> | Additional benefit - you look like a 13-year old on myspace. |
| 23:04 | <roc> | assuming the font's got it, etc etc |
| 23:04 | <Hixie> | jgraham: pimpmyspec is giving me 500s... maybe because it can't get the source file from whatwg? |
| 23:05 | <jgraham> | Hixie: That would have that effect |
| 23:05 | <Hixie> | k |
| 23:05 | <Hixie> | can you increase the timeout or something? that might solve the problem with when it's the w3c site, too |
| 23:06 | <frenzz> | http://media.tumblr.com/tumblr_leujsqUBpU1qdswit.jpg |
| 23:06 | <Hixie> | (which is usually the problem when there's a 500 fromm pms) |
| 23:07 | <bga_> | frenzz lynx is turtle |
| 23:07 | <bga_> | or owl |
| 23:07 | <jacobolus> | Hixie: anyway, feel free to refer any questions about the typography of headings to benschwarz; the main thing is just letterspacing on "HTML", dunno about "WebTTV" (maybe the TTV part, if you want to add a span), and no extra letterspacing on "Web Applications" |
| 23:08 | <jgraham> | Hixie: Maybe but I really should sleep now and I am not quite sure how to do it |
| 23:08 | <Hixie> | jgraham: k |
| 23:08 | <Hixie> | jgraham: nn |
| 23:08 | <jgraham> | gn :) |
| 23:08 | <benschwarz> | if multi-page is living standard |
| 23:08 | <benschwarz> | I wonder what developers. should be |
| 23:08 | <Hixie> | jacobolus: well they're all small-caps now so they can all have litter-spacing :-) |
| 23:09 | <heycam> | litter-spacing is where the space between two characters is set to the width of a piece of kitty litter |
| 23:09 | <Hixie> | benschwarz: is "Edition for Web Developers" no good? |
| 23:09 | <heycam> | that, or how much space to put between your kittens |
| 23:09 | <benschwarz> | Hixie: well, now you've upped the ante :D |
| 23:09 | <Hixie> | benschwarz: heh |
| 23:09 | <Hixie> | benschwarz: it's said "living standard" for a while now |
| 23:10 | <heycam> | "living standard" makes me think of "living will" |
| 23:10 | <Hixie> | i guess we should get a new right-hand-side banner |
| 23:10 | <benschwarz> | there is something so bad about this |
| 23:10 | <benschwarz> | http://html5.uncontrol.com/ |
| 23:10 | <Hixie> | or drop it altogether |
| 23:10 | <heycam> | I promise to turn life support to HTML5 off if it becomes a vegetable |
| 23:10 | <benschwarz> | Hixie: drop it ;) |
| 23:11 | <Hixie> | er, left-hand-side banner |
| 23:12 | <benschwarz> | or there are many things bad about that, I should say |
| 23:12 | <Hixie> | i love how "optimiseLegibility" is written as camelcase in CSS |
| 23:12 | <Hixie> | it's a bit like spelling "spelling" as "spellng" |
| 23:13 | <roc> | yeah they stuffed that up |
| 23:13 | <Hixie> | still getting hits to /specs/web-apps/current-work/multipage/mfavicon.ico btw |
| 23:14 | <roc> | we should add optimize-legibility etc as synonyms |
| 23:14 | <Hixie> | eh, aliases just mean more bugs with no new features |
| 23:14 | <Hixie> | i'd just move on |
| 23:14 | <Hixie> | i just think it's funny |
| 23:14 | <othermaciej> | benschwarz: omg, HTML5 is the Master Control Program! |
| 23:15 | <jacobolus> | jgraham: if you're really having trouble you could try horse tranquilizers |
| 23:15 | <Hixie> | oh my lord, without the thing on the left the spec feels so naked! |
| 23:15 | <Hixie> | that's gonna take some getting used to |
| 23:16 | <TabAtkins> | I know! |
| 23:16 | <TabAtkins> | Just add a green stripe. |
| 23:16 | <Hixie> | i think it's kinda nice |
| 23:16 | <Hixie> | looks clean |
| 23:16 | <TabAtkins> | Perhaps with "This is the song that never ends...". |
| 23:22 | <benschwarz> | Hixie: yours better not look better than mine :) |
| 23:22 | <Hixie> | hahaha |
| 23:22 | <Hixie> | no worry of that, believe me |
| 23:22 | <Hixie> | well except for the dom trees unless you've fixed those ;-) |
| 23:22 | <benschwarz> | Hixie: once developers. is ready, we can look at other editions |
| 23:22 | <benschwarz> | Hixie: no, I've been consulting :) |
| 23:23 | <Hixie> | blog comments seem positive so far |
| 23:23 | <benschwarz> | but today I have ab+c time. some whatwg is on my mind |
| 23:23 | <benschwarz> | Hixie: blog comments? on the rename |
| 23:24 | <annevk> | twitter too |
| 23:24 | <Hixie> | yeah |
| 23:24 | <Hixie> | annevk: cool |
| 23:25 | <Hixie> | does wordpress just randomly make up icons for users who don't have them? |
| 23:25 | <annevk> | the twitters also like our tagline |
| 23:25 | <annevk> | Hixie, yeah, before we had some ugly icon so I changed it to make it unique for each of them |
| 23:25 | <annevk> | it's a setting |
| 23:26 | <Hixie> | fun |
| 23:26 | <Hixie> | wow, from the twitters it looks like this change might even cause people to stop focusing on 2022 ;-) |
| 23:27 | <Hixie> | lol, svn.whatwg.org just timed out on me while trying to commit |
| 23:27 | <Hixie> | that could make life fun |
| 23:27 | <annevk> | it only makes sense, now we are always ready |
| 23:27 | <annevk> | and always not |
| 23:27 | <Hixie> | it's amusing how much an announcement can change |
| 23:27 | <Hixie> | i mean, we really didn't change anything today |
| 23:28 | <Hixie> | other than make it impossible for me to edit the sec :-P |
| 23:28 | <Hixie> | spec |
| 23:28 | <annevk> | heh |
| 23:28 | <benschwarz> | Hixie: time to sit back and count our money |
| 23:29 | <annevk> | I think it means we should share our philosophy more |
| 23:29 | <Hixie> | annevk: ok you shouldn't be getting notified anymore if "source" doesn't change. It'll still send you a notification occasionally, e.g. later today when I have to do a forced-submit to make sure everything got updated properly |
| 23:29 | <Hixie> | but not in general |
| 23:29 | <Hixie> | and forced submits will always be editoriol |
| 23:29 | <annevk> | cool |
| 23:29 | <Hixie> | editorial |
| 23:29 | <annevk> | editorial is tweeted too now on request |
| 23:29 | <Hixie> | wtf, we're STILL getting those favicon hits |
| 23:29 | <Hixie> | really! |
| 23:29 | <Hixie> | wow |
| 23:30 | <Hixie> | twitter users are masochists |
| 23:30 | <benschwarz> | whats the favicon story? |
| 23:30 | <annevk> | what we just announced was an editorial change |
| 23:30 | <annevk> | people love the trivia |
| 23:30 | <Hixie> | i guess |
| 23:30 | <Hixie> | benschwarz: dhtml5.org had some bug that was causing whatwg.org to get hits for favicons in weird places |
| 23:30 | <Hixie> | it was fixed but i'm still getting hits |
| 23:30 | <annevk> | the hardcore algorithms are not conversation material |
| 23:31 | <Hixie> | annevk: you might want to just filter out the commits with message "typo" and "xref" then |
| 23:31 | <Hixie> | i wonder if someone has it open with an old copy of the page or something |
| 23:31 | <annevk> | Hixie, yeah, that might make sense |
| 23:32 | <jacobolus> | Hixie: I'll leave it to you, but I've never been a fan of small caps mixed with big caps, especially since browsers use the same glyphs for each, but with different scaling, so that the small caps end up looking really wimpy. |
| 23:32 | <Hixie> | annevk: multiple IPs though |
| 23:32 | <Hixie> | jacobolus: i'm gonna leave it for a while, see if it grows on me or not. I'll probably end up changing it back though. |
| 23:33 | <jacobolus> | I like the big HTML though :) |
| 23:33 | <Hixie> | yeah that's gonna stay |
| 23:33 | <benschwarz> | jacobolus: ps. I think your comments are really very poignant re: developers. |
| 23:33 | <Hixie> | i have a class on that h1 so that i can make it stay even if i change the default back :-) |
| 23:33 | <jacobolus> | benschwarz: hrm? |
| 23:33 | <benschwarz> | if you're interested in forking, working out how on earth to build it |
| 23:34 | <benschwarz> | I'd be interested in seeing patches ;) |
| 23:34 | <Hixie> | looks like it's three people who have dhtml5.org open |
| 23:34 | <Hixie> | on an old page |
| 23:34 | <jacobolus> | benschwarz: not quite sure what you're referring to? |
| 23:34 | <benschwarz> | jacobolus: the developer spec |
| 23:34 | <jacobolus> | did I say something about it? other than nice job, it's pretty? |
| 23:34 | <annevk> | Hixie, I meant the filtering of messages that just say "typo" or "xref" |
| 23:35 | <benschwarz> | jacobolus: are you not jrus? |
| 23:35 | <jacobolus> | benschwarz: or the "nice job, it's pretty" was poignant? |
| 23:35 | <annevk> | so the older copy of dhtml5.org changed the favicon on the fly? |
| 23:35 | <annevk> | hilarious |
| 23:35 | <jacobolus> | benschwarz: ah, that's me. okay, gotcha now |
| 23:35 | <jacobolus> | you're welcome |
| 23:35 | <adactio> | Just for the record, I think the "Living Standard" strapline is kind of cheesy. I'd much rather a plain old "HTML." |
| 23:36 | <benschwarz> | my my, its adactio |
| 23:36 | <Hixie> | annevk: ah |
| 23:36 | <jacobolus> | benschwarz: I try my best to be poignant whenever possible |
| 23:37 | <annevk> | adactio, so basically not bother with labeling the document? |
| 23:37 | <Hixie> | adactio: well we need the date, and the date on its own looks silly. having it say "standard" also puts an end to endless discussions about whether it's a draft and whether you can refer to it, etc. |
| 23:37 | <adactio> | annevk: Label it with "HTML" |
| 23:37 | <Hixie> | i like how google hasn't indexed the new title yet so if you do a "latest" search for "html" it says the top link is the spec but has the old title :-) |
| 23:38 | <jacobolus> | benschwarz: if you want to shrink a completely-separate-from-the-text code sample, that's probably fine |
| 23:38 | <annevk> | Hixie, it still says "Working Draft" on the side btw |
| 23:38 | <adactio> | Hixie: I don't think the date on its own looks silly. |
| 23:38 | <jacobolus> | benschwarz: it's just the in-line ones that are distractingly small |
| 23:38 | <benschwarz> | Hixie: fyi. I removed the date entirely from developers.whatwg.org… |
| 23:38 | <annevk> | Hixie, I think we could nuke the sidebar and maybe reduce the margin somewhat? |
| 23:38 | <TabAtkins> | Do the date on its own! |
| 23:38 | <annevk> | Hixie, the graphical sidebar that is |
| 23:39 | <annevk> | TabAtkins, adactio, I think Hixie has a point in that people will ask about it, but I suppose we could have a FAQ entry |
| 23:39 | <annevk> | there is no real reason to have that label |
| 23:40 | <annevk> | the only reason we have it is because other standard organizations use such labels |
| 23:40 | <adactio> | annevk: Yes, I think it's a job for the FAQ rather than the spec. |
| 23:40 | <benschwarz> | Hixie: the date is probably too high up the typographic hierarchy… |
| 23:41 | <Hixie> | benschwarz: on developers.whatwg.org the date isn't so critical |
| 23:41 | <Hixie> | annevk: the sidebar has been gone for about 20 minutes now |
| 23:41 | <Hixie> | i'm not taking off the "living standard" label right now, since we _just_ blogged that we were adding it, but we can revisit that in a few weeks, certainly |
| 23:41 | <annevk> | o_O |
| 23:42 | <Hixie> | you have to hard-refresh to get style sheet updates |
| 23:42 | <adactio> | Hixie: Okay. An interim measure it is, then. |
| 23:42 | <annevk> | everyone happy, great |
| 23:43 | <benschwarz> | adactio: Hi! We haven't met, yet… |
| 23:43 | <adactio> | benschwarz: Hello. Pleased to meet you. |
| 23:43 | <Hixie> | annevk: do we have any analytics on blog.whatwg.org? |
| 23:43 | <Hixie> | annevk: i'm curious to find out what our top referrers are |
| 23:44 | <annevk> | I think mpilgrim has details on that |
| 23:44 | <annevk> | he set up Google Analytics when he wrote blog entries and it has not been removed from the source code |
| 23:45 | <Hixie> | k |
| 23:45 | <Hixie> | mpilgrim: yt? |
| 23:45 | <annevk> | http://news.ycombinator.com/item?id=2121356 is probably one of them by the way |
| 23:45 | <benschwarz> | adactio: I'm from ab-c.com.au, we're new :0) |
| 23:45 | <benschwarz> | annevk: hacker news is only good for a few hundred hits |
| 23:46 | <adactio> | benschwarz: you did the CSS for the author spec, right? Nice work. |
| 23:46 | <benschwarz> | adactio: Yeah, I've been trying to move along on developers.whatwg.org too, Christmas break was too short though |
| 23:58 | <annevk> | adactio, thanks btw for pushing the envelope! |
| 23:59 | <annevk> | and to everyone else who cares about little details that make this great |
| 23:59 | <adactio> | annevk: no problemo. I don't contribute much, but I'm happy when I can. |
