| 03:06 | <Hixie> | Lachy: kilts look great dude, what are you talking about |
| 04:35 | <annodomini> | What happened to the database specification that (I seem to recall) was a part of HTML5? |
| 04:35 | <annodomini> | The only reference I can find is openDatabase in http://www.whatwg.org/specs/web-apps/current-work/#the-window-object |
| 04:37 | <doublec> | annodomini, this? http://dev.w3.org/html5/webstorage/ |
| 04:37 | <annodomini> | doublec: Yeah, that's it. |
| 04:38 | <annodomini> | I didn't realize it had been split out. |
| 04:38 | <doublec> | there's a post in the whatwg list about some of the things that have been split out |
| 04:42 | <annodomini> | Yeah, I see that now. It didn't mention "database" or "sql", so I didn't find it when I searched for those. |
| 05:06 | <annodomini> | Has there been any discussion of adding a mechanism (with appropriate security features) for reading and writing files from the user's filesystem? |
| 05:14 | <takkaria> | there has been briefly, but it's generally pretty quickly dismissed |
| 05:14 | <takkaria> | why would you want to? |
| 05:20 | <annodomini> | To implement an html editor directly in html, so that it could be portably used across browsers. |
| 05:22 | <MikeSmith> | annodomini: http://dev.w3.org/2006/webapi/fileio/fileIO.htm |
| 05:25 | <annodomini> | MikeSmith: Looks like the kind of thing I'm thinking of. What's the status of this? Has it been discussed seriously? Implemented anywhere? |
| 05:27 | <MikeSmith> | annodomini: it is just a proposal -- an individual editor's draft that doesn't have an official status at the W3C |
| 05:27 | <MikeSmith> | Opera proposal |
| 05:27 | <MikeSmith> | Opera may already actually implement something like it in Opera Mobile |
| 05:28 | <MikeSmith> | as far as discussion, there was some limited discussion, but Apple and Mozilla don't seem interested in implementing it |
| 05:28 | <MikeSmith> | annodomini: that guy to ask about it is virtuelv |
| 05:28 | <MikeSmith> | when he wakes up |
| 05:29 | <MikeSmith> | he wrote it |
| 05:29 | <MikeSmith> | he's in Oslo |
| 05:29 | <annodomini> | MikeSmith: Thanks. I've found this thread that I'm reading through: http://lists.w3.org/Archives/Public/public-webapi/2008May/0065.html |
| 05:38 | <annodomini> | Yeah, looks like the security issues are pretty thorny (as expected), and this proposal doesn't do a good job of dealing with them. |
| 06:53 | virtuelv | reads backlog |
| 06:53 | <virtuelv> | file io in itself is not a risk |
| 06:54 | <virtuelv> | it is the binding between your system and the interfaces |
| 06:55 | <virtuelv> | (and no, "my" proposal didn't try to deal with it in the web context, given that I at first never intended it for the web) |
| 08:28 | <MikeSmith> | virtuelv: fwiw, might help if the draft actually made it clear that it's not intended for the web |
| 08:28 | <MikeSmith> | nice |
| 08:29 | <MikeSmith> | oops |
| 08:29 | <MikeSmith> | virtuelv: since the abstract starts out with "This document describes an interface for an abstract File I/O interface where web applications can interact with a file system..." |
| 09:23 | <annevk3> | Hixie, "half a driver's" -> "have a driver's" |
| 09:29 | <Hixie> | oops thanks |
| 09:34 | <Lachy> | Hixie, what's in an earthquake kit, and why would anyone steal it? (re http://twitter.com/Hixie/status/1371054800 ) |
| 09:36 | <Lachy> | Hixie, also, how did you manage to get tircd up and running? I tried that about a week or two ago, but without success. My IRC client just wouldn't connect to localhost |
| 09:39 | <Philip`> | It's an earthquake *prevention* kit, according to http://ln.hixie.ch/ |
| 09:39 | <Philip`> | I really can't imagine how that would work |
| 09:40 | <Philip`> | Maybe it contains an awful lot of duct tape, so you can stick the continental plates together and stop them wobbling against each other? |
| 09:41 | jgraham | wonders how an adoption agecy algorithm helps when your car has been broken into |
| 09:42 | <annevk3> | Philip`, how would any kind of tape help when they're pushing against each other? |
| 09:45 | <Lachy> | annevk3, obviously the tape would only help in the cases where they're pulling away from each other |
| 09:45 | <Philip`> | annevk3: There's no problem with the pushing because that's a nice stable non-quakey state - the problem is when they start sliding |
| 09:46 | <Lachy> | Philip`, no, when they're pushing together hard enough, they start to push upwards and make mountains |
| 10:07 | <jgraham> | Hixie: More to the point, surely if everyone involved fainted whilst climbing you could have a more serious accident than you suggest? After all the belayer is the only thing preventing the rope from running free so if the climber were to fall whilst the belayer was not holding the dead rope, you could fall the height climbed. |
| 10:09 | <Philip`> | What if you were climbing and then a dragon suddenly flew in and ate you? |
| 10:09 | <Philip`> | (That seems similarly likely to everyone fainting simultaneously) |
| 10:10 | <jgraham> | They might be characters in a Jane Austen novel who were libable to all swoon if they saw a particuarly rich, unattached, gentleman |
| 10:11 | <Philip`> | Do characters in Jane Austen novels often go rock climbing? |
| 10:11 | <gsnedders> | Sadly not |
| 10:12 | <Philip`> | That's a shame |
| 10:13 | <jgraham> | (it seems more plausible that your belayer would faint and that, in a panic, you would loose your grip on the rock) |
| 10:36 | Philip` | imagines the discussion of broken IRIs in Atom would be more useful if people had test results of how feed readers parse URL-ish strings, or data about how many feeds have invalid IRIs |
| 10:37 | <annevk3> | I'm not sure |
| 10:38 | <jgraham> | Philip`: There is a well defined data-gathering mechanism for HTML 5 which is to say, people ay things that should be qualified with data and then you provide the data |
| 10:38 | <annevk3> | My main point is that I don't want two URL functions in a browser doing essentially the same thing and it's pretty clear that we need one for HTML that does it like HTML5 |
| 10:39 | <annevk3> | I also wouldn't really want two URL functions in a feed reader and since feed readers ought to handle HTML... |
| 10:40 | <Philip`> | Web browsers already have a zillion functions (many for doing similar things in slightly different ways), so two functions for parsing URLs wouldn't hurt much |
| 10:41 | <annevk3> | Every one of those that can be avoided hurts in developer and QA time. Security analysis cost, etc. |
| 10:42 | <annevk3> | I'ts one of the reasons we're still trying to eliminate quirks if feasible. (Either by standardizing on them or removing them.) |
| 10:42 | <Philip`> | It hurts but not a huge amount, and it has to be balanced against the cost of changing every other spec and software product that uses URIs in non-HTML contexts |
| 10:42 | jgraham | grumbles about standards bodies that publish their standards in non-standard formats |
| 11:03 | <Lachy> | Hixie, it the status section of the web storage spec, it says to send mail to public-webapps-comments and links to the non-existent archives. It should be public-webapps |
| 11:04 | <annevk3> | Philip`, and that in turn has to be balanced against bugs in those software products and specs and how much of those bugs would be fixed by changing libraries and URL specs |
| 11:04 | <jgraham> | Is Julian's argument that allowing whitespace in URIs is bad because authors that choose to use it may experience poor syntax highlighting? Because that seems like it could be easily fixed by choosing not to use it |
| 11:04 | Lachy | wonders who Hish is and why he has to have a name messes with my IRC's autocomplete for "Hi<tab>" |
| 11:05 | <annevk3> | Highlighting and autolinking fails all over the place anyway due to most code not properly taking care of punctation (and even then it could be wrong if a URL actually did end with say a dot or comma) |
| 11:07 | Philip` | notes that you already have to handle spaces in URIs in order to write an HTTP client that can retrieve web pages, regardless of anything to do with HTML |
| 11:07 | <annevk3> | Philip`, why is that? |
| 11:11 | <Philip`> | annevk3: Because people put spaces in Location headers |
| 11:11 | <Philip`> | e.g. http://www.usafa.af.mil/ returns 302 with "Location: index.cfm?catname=AFA Homepage" |
| 11:12 | <annevk3> | cheers |
| 11:12 | <Philip`> | (That broke that page in my dmoz downloader since HttpClient throws an exception on invalid URIs) |
| 11:15 | <Philip`> | http://www.flightsimulator.nl/ gives "Location: RunScript.asp?Article_type=General%20News&p=ASP\Pg0.asp" where the \ is apparently illegal |
| 11:16 | <Philip`> | and there's other with "|" and "[" and "]" |
| 11:16 | <Philip`> | *others |
| 11:17 | <Philip`> | Oops, not true, the "[" and "]" weren't in redirects, they were just in dmoz's list |
| 11:19 | <Philip`> | (which I suppose is a separate issue - anything parsing dmoz's RDF dump of site listings needs to deal with invalid URIs too) |
| 12:46 | <annevk3> | I wonder whether http://lists.w3.org/Archives/Public/www-style/2005Mar/0102 and co still apply. Stuff Hixie wrote back then on normalization code no longer really applies I think. Every browser as code for that now. |
| 12:53 | <annevk3> | Ah, the problem is with step 1. |
| 12:56 | <annevk3> | Step 1 in RFC 3987 that is. |
| 12:56 | <annevk3> | HTML5 deals with that by not following RFC 3987 at all there. |
| 12:57 | <annevk3> | I doubt any software deals with that properly. |
| 12:57 | jgraham | wonders wwhat Joshue's point is |
| 12:57 | <annevk3> | http://lists.w3.org/Archives/Public/www-style/2005May/0024.html has more details by the way. |
| 12:59 | <annevk3> | jgraham, I think part of his point is that ARIA makes things more complex for disabled people by allowing a link to be marked up as button. |
| 13:00 | <jgraham> | annevk3: That seemed to be the case to me as well |
| 13:01 | <jgraham> | Isn't this exactly what was predicted would happen? |
| 13:01 | <annevk3> | Yes it was, but since HTML5 did not happen at the W3C nobody believed in it... |
| 13:01 | <annevk3> | And everyone else thought IE would never be updated so we'd forever need a hack for IE6 rather than hoping everyone would implement 'appearance' and such one day. |
| 13:03 | <annevk3> | I sometimes have the cynical thought that these people are paid to consult on these bolt-on accessibility things and therefore would never ever denounce them. |
| 13:07 | <jgraham> | I would never ever think anything like that. Never. |
| 13:07 | <jgraham> | In related newsm I still believe that sarcasm can work on the internet, despite available evidence |
| 13:08 | <annevk3> | jgraham, we just need implied start and end tags that work reliably across all readers so they can use custom style sheets to hide it if desired |
| 13:21 | <hsivonen> | validator.nu goes down for a kernel update reboot. html5.validator.nu stays up. |
| 13:23 | <hsivonen> | how do I tell via dump() if two scripts run in the context of the same global scope object without relying on variables set by me? |
| 13:23 | <hsivonen> | is there anything a script can read that is a different hash in different global scopes but the same hash is the same scope? |
| 13:25 | <Lachy> | hsivonen, do you mean in JavaScript, or some other language? |
| 13:26 | <hsivonen> | Lachy: browser-hosted JS |
| 13:26 | <hsivonen> | or Gecko-hosted JS even |
| 13:28 | <annevk3> | wrong channel? |
| 13:28 | <hsivonen> | perhaps |
| 13:28 | <annevk3> | though admittedly a lot of Gecko people are in this channel nowadays :) |
| 13:29 | <Philip`> | Sounds like a bad sci-fi movie plot - Invasion of the Gecko People! |
| 13:40 | <hsivonen> | html5.validator.nu goes down for kernel update (and may be insanely slow to come back up). validator.nu is up. |
| 14:27 | <hsivonen> | I wonder how MS intends to maintain their mode switching blacklist using telemetry when sites that are on the blacklist don't get the compat view button in the release version of IE8 |
| 14:44 | <annevk3> | Now while the HTML5 URL handling is quirky in one respect handling href="björn" the same regardless of how the document was originally encoded makes a whole lot of sense to me. |
| 14:48 | <MikeSmith> | hsivonen: I got a patch ready for http://html5.org/tools/web-apps-tracker?from=2889&to=2890 "Rename attributes for form submission to avoid clashes with existing usage." |
| 14:49 | <MikeSmith> | action -> formaction on input and button elements |
| 14:49 | <MikeSmith> | etc. |
| 14:49 | <hsivonen> | MikeSmith: great! |
| 14:49 | <hsivonen> | MikeSmith: I'll redeploy V.nu after you've checked in. |
| 14:49 | <MikeSmith> | OK |
| 14:50 | <MikeSmith> | I'll check it in now |
| 14:50 | <MikeSmith> | I already smoke-tested it against my local v.nu install and seems I didn't miss anything |
| 14:55 | <hsivonen> | ok. I think I have IE8 mode switching figured out |
| 15:00 | zcorpan | informs the xml core wg about web addresses |
| 15:00 | <annevk3> | zcorpan, I hope you're enjoying this |
| 15:01 | <zcorpan> | i've tried to ignore it mostly |
| 15:02 | <zcorpan> | although i realized that the xml core wg have spent the last couple of months (at least) discussing in telecons that they should update all xml specs in existence to reference LEIRI |
| 15:02 | <annevk3> | If CSS uses HTML5 URL handling everything should be fine there. |
| 15:03 | <annevk3> | Though CSS might be fine if it enforced UTF-8ness for the query bit |
| 15:03 | <annevk3> | Just like XMLHttpRequest |
| 15:06 | <zcorpan> | i wonder why some people argue along the lines of "why change a published spec?" instead of "why have both parseURL(url, encoding) and parseLEIRI(url) when having just he former will do fine" |
| 15:06 | <svl> | Hixie: huh, I tried part of that trick once (trying to open the gate going into a garage, as the one at the exit lane was broken), but it wouldn't give a ticket (nor open, which was the vexing part) without the weight of a car on the sensor before the gate. |
| 15:07 | <annevk3> | zcorpan, maybe we should form a club |
| 15:11 | <jgraham> | We could have some sort of principle that says implementors are more important than spec authors |
| 15:12 | <zcorpan> | hmm the boolean attribute discussion reminds me of aria |
| 15:12 | <zcorpan> | i think aria allows values like "undefined" and "false" |
| 15:13 | <annevk3> | fun |
| 15:13 | <zcorpan> | consistency++ |
| 15:13 | <hsivonen> | mpilgrim: I think I've now completed the IE8 flow chart except I haven't been able to verify the position of the MS-maintained blacklist: http://hsivonen.iki.fi/ie8-mode.pdf |
| 15:14 | <hsivonen> | I think the most interesting bit is the Almost Standard Doctype? box on lower right |
| 15:15 | <hsivonen> | that is, *quirky* doctype plus X-UA-Compatible: IE=8 means IE8 *standards* mode |
| 15:15 | <annevk3> | <meta> overrides HTTP? sweet |
| 15:15 | <hsivonen> | annevk3: yeah |
| 15:15 | <hsivonen> | annevk3: See Ruby's Postulate :-) |
| 15:15 | <zcorpan> | hsivonen: i filed a bug about the combination quirky doctype and ie8 meta :( |
| 15:16 | <annevk3> | you and you're references I need to Google each time :p |
| 15:16 | <annevk3> | but yeah, that sounds about right |
| 15:16 | <jgraham> | hsivonen: Highlighting the shortest path to standards mode (any maybe other modes) would be good |
| 15:16 | <annevk3> | we actually encountered such a bug the other day with a site declaring euc_kr in HTTP and Opera and Safari being the only browsers that recognize it as euc-kr and therefore ignoring the more correct <meta> |
| 15:17 | <Philip`> | hsivonen: Have you looked at IE=EmulateIE8? |
| 15:17 | <annevk3> | (Opera and Safari are correct per Unicode, for those who care) |
| 15:17 | <hsivonen> | Philip`: I haven't |
| 15:17 | <Philip`> | It seems logical that that'd be equivalent to not giving any X-UA-Compatible, therefore it must be the case that it does something weird and crazy |
| 15:18 | <annevk3> | ouch, s/you're/your/ |
| 15:18 | <jgraham> | The whole HTTP thing is a victory for theoretical utility over practical reality |
| 15:18 | <hsivonen> | aargh. I forgot IE=IE7 |
| 15:18 | <jgraham> | Maybe CS should have a required psycology component |
| 15:18 | <jgraham> | Or at least a required HCI class |
| 15:19 | <annevk3> | I wonder how much failure of HTTP is due to the perceived need of content negotiation |
| 15:19 | <zcorpan> | hsivonen: aren't there two IE7 modes? one using the old engine and one using the new engine? |
| 15:19 | <annevk3> | I'm pretty sure that's what got us stuff like Content-Type |
| 15:19 | <Philip`> | zcorpan: I thought the old one was just what you got if you didn't install IE8 |
| 15:19 | <annevk3> | before that we had magic bytes, such as <plaintext> |
| 15:20 | <jgraham> | annevk3: Well there is also the use cases like being able to send feeds as text/plain for debugging, for example |
| 15:20 | <jgraham> | which HTTP is designed to allow |
| 15:20 | <zcorpan> | Philip`: i thought ie8 had two ie7 modes |
| 15:20 | <annevk3> | jgraham, just move Content-Type to the content and call it <plaintext> |
| 15:20 | <zcorpan> | "IE7" and "EmulateIE7" |
| 15:21 | <jgraham> | annevk3: Doesn't really work if your ontent doesn't support it |
| 15:21 | <jgraham> | *content |
| 15:21 | <Philip`> | zcorpan: I remember reading that IE7 makes it render in IE7-bug-mode always, whereas EmulateIE7 makes it render in IE5-bug-mode if there's a quirky doctype else in IE7-bug-mode |
| 15:21 | <annevk3> | Anyway, "too late now" This will be my meme of the day. |
| 15:21 | <hsivonen> | zcorpan: as far as I can tell, IE=7 means IE7 standards and IE=EmulateIE7 means perform doctype sniffing like IE7 and decide quirks or IE7 standards |
| 15:21 | <Philip`> | (and the Emulate versions are preferred so that pages will be more compatible with other browsers) |
| 15:22 | <zcorpan> | hsivonen: ok |
| 15:22 | <Philip`> | (but people started promoting and using the feature before the Emulate options were added, so people use a random mixture of the two) |
| 15:23 | <annevk3> | It would be nice to have a Web-based version of that flowchart |
| 15:23 | <hsivonen> | annevk3: OmniGraffle's SVG export costs extra and sucked last I checked |
| 15:24 | <hsivonen> | annevk3: I intend to write this as <dl> some day |
| 15:24 | <annevk3> | I agree that SVG versions of flowcharts are never really great. |
| 15:24 | <hsivonen> | Philip`: there's no EmulateIE8 |
| 15:25 | <Philip`> | hsivonen: There is in "strings -el mshtml.dll" |
| 15:27 | <hsivonen> | Philip`: I'm not sure if that's legal in my country. :-( |
| 15:27 | <annevk3> | So the insane algorithm leads to a total of 4 rendering modes? Ouch! |
| 15:27 | <annevk3> | hsivonen, you can however legally reverse engineer the value no? |
| 15:27 | jgraham | is not sure if anything is legal. Which seems like a problem somehow |
| 15:28 | <hsivonen> | I believe I'm on solid ground doing blackbox poking. |
| 15:29 | hsivonen | starts revising /doctype/ |
| 15:30 | <zcorpan> | http://lists.w3.org/Archives/Public/public-xml-core-wg/2009Mar/0012.html |
| 15:31 | <annevk3> | zcorpan, well yes, but that's not a point against not making all things consistent, right? |
| 15:39 | <hsivonen> | I guess the HTML5 doctype is out of the bag, so I might as well recommend it. |
| 15:40 | <hsivonen> | this marks the first change to my doctype advice since late 2000. |
| 15:51 | <annevk3> | Given http://www.intertwingly.net/slides/2004/devcon/ it surprises me Sam is now advocating some kind of QNames solution in HTML |
| 15:53 | <annevk3> | http://www.intertwingly.net/slides/2004/devcon/96.html |
| 15:55 | <annevk3> | http://www.intertwingly.net/slides/2004/devcon/107.html "You won't find reality in in any specification" true, though at least we have progressed somewhat into writing specs that could become reality some day |
| 15:55 | <annevk3> | Re-reading that presentation still makes me laugh. It's a good pointer for people who say things are simple. |
| 15:59 | <Philip`> | hsivonen: I'm not sure it is here but I know there's stuff in the copyright law about allowing reverse engineering for interoperability so I just kind of assume it's probably okay and nobody's going to care |
| 16:23 | <hsivonen> | MikeSmith: something went wrong with V.nu redeployment. I'll investigate in the morning. |
| 16:34 | <hsivonen> | I've updated http://hsivonen.iki.fi/doctype/ ; reviews welcome |
| 16:34 | <hsivonen> | the position I'm taking with X-UA-Compatible is that I don't recommend IE=8 |
| 16:37 | <Philip`> | hsivonen: "inadequete" |
| 16:37 | <hsivonen> | Philip`: thanks. that typo has been there for years... |
| 16:41 | <Philip`> | You should use publishing tools that report a fatal error if there are unresolved spell-checker failures |
| 16:42 | <Lachy> | hsivonen, my position on X-UA-Compatible is that you should use IE=Edge, unless you need compatibility with an older version of IE other than the latest. So IE=7 is ok if IE7 mode is needed for your site. But I agree that IE=8 should be avoided, at least until IE9 comes out |
| 16:43 | <annevk3> | my position is that you should not use it |
| 16:43 | <Lachy> | annevk3, if you need to use it, like when you're stuck on a blacklisted domain |
| 16:44 | <annevk3> | then I'd create a US company and sue MS |
| 16:44 | <hsivonen> | Lachy: if your site works in IE7 mode but not in IE8 mode, your site is broken and needs to be fixed |
| 16:44 | annevk3 | blinks |
| 16:44 | <Lachy> | hsivonen, sure. But the whole point of X-UA-Compatible is that it gives you time to make that transition to more standards compliant code |
| 16:45 | <hsivonen> | Lachy: oh well. editing |
| 16:45 | <annevk3> | hsivonen, a TOC would help |
| 16:46 | <Philip`> | annevk3: Rather than suing them, you could just get your domain administrator to follow the steps to get removed from the list |
| 16:46 | <annevk3> | that's not nearly dramatic enough |
| 16:47 | <Philip`> | More likely to succeed, though |
| 16:47 | <hsivonen> | Lachy: fixed, thanks |
| 16:49 | <annevk3> | Philip`, for some value of succeed |
| 16:49 | <hsivonen> | Do they use the Public Suffix List for stuff like .co.uk? |
| 16:50 | <hsivonen> | I've been trying to get iki.fi on the Public Suffix List, but the people in charge at IKI are IETF-oriented. |
| 16:51 | <Philip`> | hsivonen: They use some kind of list (IETldCache) that contains stuff like police.uk, nhs.uk, kent.sch.uk, though it doesn't have uk or co.uk |
| 16:52 | <Philip`> | hsivonen: http://philip.html5.org/data/ie8-tlds.txt |
| 16:53 | <hsivonen> | Philip`: thanks |
| 16:53 | <annevk3> | that doesn't look nearly complete enough |
| 16:54 | <Philip`> | hsivonen: (That's stored in the same binary format as the compatibility domain list) |
| 16:54 | <annevk3> | why is +ACE-nu.nl listed twice and what does it mean? |
| 16:54 | <Philip`> | Don't ask me :-) |
| 16:55 | <gsnedders> | Philip`: why is +ACE-nu.nl listed twice and what does it mean? |
| 16:55 | <Philip`> | This is just the complete list of strings from C:\Users\Whoever\AppData\Roaming\Microsoft\Windows\IETldCache\index.dat |
| 17:17 | <annevk3> | wow http://thedailywtf.com/Articles/Where-the-Wild-Web-Things-Are.aspx |
| 17:18 | <annevk3> | -- http://twitter.com/collinjackson/status/1376236042 |
| 17:22 | <Philip`> | Looks like all the literal "<"s and ">s" got mangled into "<" and ">" in that blog post |
| 17:22 | <Philip`> | which makes it unnecessarily confusing |
| 17:23 | <gavin> | needs more XSLT |
| 17:25 | <Hixie> | Lachy: an earthquake emergency kit is like a regular emergency kit (has food rations, a first aid kit, a mechanical radio, etc), but for people in earthquake zones |
| 17:25 | <Hixie> | Philip`: an earthquake prevention kit is an earthquake emergency kit, but it prevents earthquakes because naturally you'd only experience a serious earthquake when unprepared |
| 17:26 | <Hixie> | jgraham: while climbing if the belayer faints the grigri will lock and the rope will stop moving. |
| 17:29 | <Lachy> | Hixie, does an earthquake prevent kit also prevent other geological disasters? |
| 17:30 | <jcranmer> | Lachy: it should protect from volcanoes as well |
| 17:30 | <Lachy> | I'm just wondering if there's a correlation between your prevention kit being stolen and the volcano erruption that wasn't prevented in Alaska today. |
| 17:31 | <Hixie> | svl: interesting, the guy's car was in fact on the sensor, maybe you're right |
| 17:31 | <jcranmer> | things like tornadoes, floods, and hurricanes need completely different prevention mechanisms |
| 17:32 | <Hixie> | Lachy: i have no idea. i would imagine it wouldn't prevent any disasters except those that it would actually help me with, so i guess it's a coincidence |
| 17:44 | <Hixie> | http://www.reddit.com/r/web_design/comments/86ogf/multiple_web_technologies_on_one_page/ |
| 17:51 | <Philip`> | "that site is craptastic example of how NOT to make an html 5 site" - clearly all new web technologies are part of HTML 5 |
| 17:52 | <Hixie> | yeah we need to figure out some new branding mechanism |
| 17:52 | <Hixie> | i'm torn between "web 3.0" and "web 5.0" |
| 17:53 | <Hixie> | i'm thinking maybe we should just define "web 3.0" as a subset of the new stuff and have three levels from web 3.0 to web 5.0 |
| 17:53 | <Hixie> | where web 5.0 is all our new techs |
| 17:54 | <Philip`> | Why not pave the cowpaths and call everything HTML 5? |
| 17:58 | <gavin> | I think you should pave all foreseeable future cowpaths |
| 17:59 | <Philip`> | Turn all the cow fields into giant parking lots |
| 18:06 | <annevk3> | Hixie, imo Web X does not make much sense if it does not also include HTTP, CSS, etc. |
| 18:07 | <Philip`> | "Web X" suffers from the negative opinions that exist towards Web 2.0 |
| 18:07 | <annevk3> | Hixie, I do not really have better suggestions though |
| 18:07 | <Hixie> | annevk3: it would include HTTP, CSS, etc |
| 18:08 | <Hixie> | in particular it would include the new CSS animation stuff at some level |
| 18:08 | <Hixie> | Philip`: calling things HTML5 leads to people being confused when they look at the spec called HTML5 |
| 18:08 | <annevk3> | In that case I suppose it makes sense to redefine "Web X" to refer to its technologies rather than type of usage |
| 18:17 | <annevk3> | Hixie, is the IETF meeting going on now as well? |
| 18:17 | <Hixie> | i think so, yes |
| 18:17 | <Hixie> | i'm not going to that |
| 18:17 | <Hixie> | i'm going to some informal thing on wednesday with sam, lisa, dan, and others |
| 18:18 | <annevk3> | ah ok |
| 18:18 | <annevk3> | DanC mentioned WebSockets in http://lists.w3.org/Archives/Public/www-tag/2009Mar/0140.html so I assumed you'd be there. Clearly this doesn't work that way :) |
| 18:19 | <Hixie> | speaking of the ietf |
| 18:19 | <Hixie> | did you know |
| 18:19 | <Hixie> | that since meetings aren't supposed to be productive |
| 18:19 | <Hixie> | they actually prevent you from publishing anything while their meetings are going on? |
| 18:19 | <Hixie> | the official version of the websockets spec is falling behind because the ietf won't let me update it |
| 18:21 | <annevk3> | for websockets a WHATWG version would be nice I think, btw |
| 18:21 | <annevk3> | especially since text/plain is annoying to read |
| 18:21 | <Hixie> | holy crap! they turned off the blocking! woo, it just updated |
| 18:21 | <Hixie> | yeah i think i might do that |
| 18:22 | <Hixie> | gonna wait a bit to see what happens though |
| 18:22 | <Hixie> | i was thinking of just making an uber WHATWG spec with all the files that are in this source document in one place |
| 18:22 | <Hixie> | no, wait, it didn't update |
| 18:22 | <Philip`> | Maybe they block updates to make sure everyone at the meeting has time to read the same document so they can agree on what they're talking about, rather than some people reading this morning's version and some people reading last week's version and all getting confused |
| 18:22 | <Hixie> | wtf |
| 18:22 | <Hixie> | man the ietf is annoying |
| 18:23 | <annevk3> | http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol is from Feb 25 |
| 18:23 | <Hixie> | Philip`: maybe, but then the solution is to give up on meetings, not block progress even from those who aren't there |
| 18:23 | <Hixie> | i got an e-mail saying draft-hixie-thewebsocketprotocol-05 is published |
| 18:23 | <Hixie> | but it doesn't seem to be |
| 18:24 | <annevk3> | 05? hmm, that vies me 03 |
| 18:24 | <annevk3> | s/view/gives/ |
| 18:24 | <Hixie> | yeah |
| 19:26 | <Hixie> | wow |
| 19:26 | <Hixie> | tgbyhn deleted his entire reddit account |
| 19:27 | <Hixie> | it is telling i think that people who want to complain about html5 often only do so anonymously |
| 19:27 | <Hixie> | and refuse to back up their points when they are pressed |
| 19:29 | <annevk3> | pointer to reddit thread? |
| 19:30 | <virtuelv> | annevk3: when someone deletes their account, their posts vanish |
| 19:30 | <virtuelv> | (sort of, you used to be able to recover them by appending /.rss to the url in question |
| 19:33 | <Hixie> | annevk3: http://www.reddit.com/r/technology/comments/85acf/microsoft_is_ignoring_web_standards_and_should/c08agbv |
| 19:33 | <Hixie> | in the future i'll always quote their messages in mine, i guess :-) |
| 19:38 | <annevk3> | http://www.reddit.com/user/tgbyhn still exists |
| 19:39 | <svl> | http://www.google.com/search?q=cache:http://www.reddit.com/r/technology/comments/85acf/microsoft_is_ignoring_web_standards_and_should/ has (most of) the deleted comments |
| 20:04 | <jgraham> | Hixie: I had forgotton about the existence of grigris because I have only used one about once and most people I have spoken to consider them more dangerous than a normal belay device |
| 20:05 | <jgraham> | The reason being that it is very hard to control most grigris when the climber is coming down |
| 21:15 | <Hixie> | jgraham: doesn't seem that hard to me, but ok |
| 21:25 | <annevk3> | I wonder what is supposed to be wrong with the desire to interoperate even in case of error. |
| 21:27 | <Hixie> | it's not pretty? |
| 21:28 | <annevk3> | Granted, reality often sucks. |
| 21:28 | <Hixie> | sometimes i kinda just want to be like "web standards development is not a game, if you're not willing to make hard choices that compromise spec purity when doing so is needed to make users have a better experience, get out of the water and get back into the wading pool" |
| 21:29 | <Hixie> | i'm so tired of having to argue with people who still seem to think the web is a research project |
| 21:46 | <mpilgrim> | hsivonen: on the new http://hsivonen.iki.fi/doctype/ i think the phrase "(e.g. mit.edu!)" needs some external citation -- i read the irc backscroll so i know the reference, but other people wouldn't |
| 21:51 | <olliej> | sicking: so one issue with the async lock for local storage (that i don't believe has been addressed) is what happens to closures that capture the localstorage reference |
| 21:52 | <sicking> | olliej, i did in fact comment on that |
| 21:53 | <sicking> | olliej, if the object passed to the callback is accessed after the callback has ended we need that to fail |
| 21:53 | <sicking> | olliej, and define how it fails |
| 21:53 | <sicking> | olliej, and define what happens if you access that object inside another callback (should the object get reenabled again, or should a new one be created on each callback) |
| 21:54 | <sicking> | olliej, the important part is accessing the storage after the callback is failing. The rest is less important IMHO, but needs to be defined |
| 21:55 | <olliej> | sicking: that's what i was thinking -- sorry i must have missed that email |
| 21:55 | <Hixie> | btw if anyone is keeping track of examples of microsoft knowingly hurting web standards, note the way this e-mail was never actually followed up on, despite the promise therein: http://lists.w3.org/Archives/Public/public-html-comments/2008Jun/0020.html |
| 21:55 | <sicking> | olliej, it was a long email :) |
| 21:55 | <olliej> | sicking: heh |
| 22:02 | <mpilgrim> | hsivonen: another +1 for adding a table of contents, and perhaps auto-generating nested section numbers like html5 spec does |
| 22:08 | <mpilgrim> | someone needs to make philip's ie8 blacklist into a web service |
| 22:09 | <mpilgrim> | validator.nu could hook into it to tell you what rendering mode IE8 would use for your site |
| 22:16 | <roc> | Hixie: shouldn't someone follow up on that now? |
| 22:16 | <sicking> | Hixie, did they add API to support explicit locking and unlocking? |
| 22:17 | <annevk3> | they don't have that |
| 22:17 | <annevk3> | they have an event that is dispatched when stuff is written to disk |
| 22:17 | <annevk3> | and have some remainingStorage attribute |
| 22:17 | <annevk3> | that was in the latest beta/rc, things might have changed in final |
| 22:17 | <roc> | I thought they had a commit() method |
| 22:18 | <roc> | ISTR they removed remainingStorage |
| 22:18 | <annevk3> | they used to have that, yes |
| 22:18 | <annevk3> | ISTR? |
| 22:18 | <roc> | they took commit() out? |
| 22:18 | <roc> | I Seem To Recall |
| 22:18 | <annevk3> | to my knowledge the latest RC did have remainingStorage and did not have commit() |
| 22:20 | <annevk3> | http://msdn.microsoft.com/en-us/library/cc197062(VS.85).aspx "confirms" that |
| 22:20 | <roc> | oh |
| 22:20 | <roc> | remainingSpace is no longer enumerable, but I guess it's still there |
| 22:20 | <roc> | After shipping the RC build we listened to feedback on our HTML 5 DOM storage implementation. We acted on this feedback by making two changes to IE8’s DOM storage implementation so that we match the HTML 5 spec. The first change is that we now return null and not undefined for keys that don’t exist in DOM storage. The second change is that we removed the length and remainingSpace properties when iterating DOM storage using a for..in statement. |
| 22:21 | <annevk3> | there was a lot more feedback, including how to make their XML backend non-well-formed |
| 22:22 | <annevk3> | what Hixie pointed out above, and how storagecommit was not defined anywhere |
| 22:26 | <Philip`> | mpilgrim: I imagine the main difficulty is you'd have to run the service on a Windows machine with IE8 and automatic updates |
| 22:26 | <Philip`> | (and I only have Linux boxes) |
| 22:27 | <Philip`> | Maybe it'd be a pretty trivial service since you just embed Trident in your service and read res://iecompat.dll/iecompatdata.xml |
| 22:27 | <Philip`> | (unless that's IE-only) |
| 22:31 | <gsnedders> | http://www.ietf.org/internet-drafts/draft-sneddon-atom-export-00.txt |
| 22:37 | <annevk3> | I thought you were doing useful work on HTTP parsing? :p |
| 22:38 | <gsnedders> | Oh, I was. This is just closer to being able to be published :P |
| 22:58 | <Hixie> | roc: their begin() and commit() methods are not for threading |
| 22:59 | <annevk3> | (they don't have them anymore) |
| 22:59 | <Hixie> | oh they dropped those? |
| 22:59 | <Hixie> | interesting |
| 23:00 | <annevk3> | I think begin() is implicit and commit() is prolly run at some timeout at which point they dispatch the storagecommit event. |
| 23:00 | <Hixie> | begin() is definitely not implicit |
| 23:00 | <Hixie> | they have no implicit locking |
| 23:00 | <Hixie> | that's one of the problems |
| 23:01 | <annevk3> | Well, they must have something now... |
| 23:01 | <Hixie> | why? |
| 23:02 | <Hixie> | if you run the following two scripts in two different windows in IE8: |
| 23:02 | <Hixie> | localStorage.foo = 0; while (true) localStorage.foo = parseInt(localStorage.foo) + 1; |
| 23:02 | <Hixie> | var x = 0; while (localStorage.foo == localStorage.foo) x += 1; x |
| 23:02 | <Hixie> | the second will return. |
| 23:03 | <Hixie> | so they have no implicit cross-frame locking as far as i can tell |
| 23:04 | <annevk3> | sorry, nm |
| 23:04 | <roc> | we don't want to follow IE8 down this road |
| 23:04 | <annevk3> | I'm tired from breaking my head over URLs |
| 23:05 | <annevk3> | and I've no real opinion on this anyway other than that I think it'd be a annoying if we changed localStorage again |
| 23:06 | <Hixie> | well IE8 doesn't implement the spec |
| 23:09 | <annevk3> | Hixie, by that argument we can break <canvas> |
| 23:09 | <annevk3> | Hixie, afaict IE8 has a usuable impl |
| 23:09 | <Hixie> | oh i wasn't making an argument |
| 23:10 | <Hixie> | just an observation |
| 23:10 | <annevk3> | they do not allow all possible key/value strings, they have a custom DOM attribute and event, the solution works poorly for multiple top-level browsing contexts, but other than that it pretty much just works as described |
| 23:12 | <Hixie> | i don't think most authors will notice, sadly |
| 23:13 | <annevk3> | the multiple top-level browsing contexts part? |
| 23:13 | <Hixie> | any of those issues |
| 23:15 | <annevk3> | I'm sort of surprised neither Microsoft nor Google brought up the issues with localStorage and multiple processes |
| 23:15 | <annevk3> | (when it was re-designed) |
| 23:16 | <Hixie> | google is who did bring up the issue :-) |
| 23:16 | <Hixie> | though originally with workers |
| 23:16 | <Hixie> | it's not a HUGE problem with top-level browsing contexts |
| 23:16 | <Hixie> | just a bit of additional latency |
| 23:17 | <gsnedders> | Hixie: You just use pico from pine? |
| 23:17 | <Hixie> | hm? |
| 23:17 | <gsnedders> | Hixie: As a message editor? |
| 23:17 | <gsnedders> | (really random question) |
| 23:17 | <Hixie> | i just use pine |
| 23:17 | <Hixie> | occasionally escaping to emacs if things get complicated |
| 23:18 | <gsnedders> | pine opens up another program, by default pico, to write messages |
| 23:18 | <Hixie> | ok |
| 23:18 | <Hixie> | it says "PINE" at the top of my editor window |
| 23:18 | <annevk3> | Hixie, ah yeah, the spec mentions that already |
| 23:19 | <Philip`> | About http://www.w3.org/mid/op.uq9oyuqd64w2qv⊙aooc : perhaps it would be useful to say what happens if you a.setAttribute('href', 'http://www.example.com/zero\u0000here/';) since that seems more like what the question intended |
| 23:20 | <annevk3> | didn't I answer that too? |
| 23:21 | <annevk3> | anyway, thinking about it some more I'm not sure that'd work either, though setting window.location might |
| 23:21 | <Philip`> | Oh, right, I didn't notice that sentence |
| 23:24 | <Hixie> | woo, http://tools.ietf.org/html/draft-hixie-thewebsocketprotocol now redirects to -05 |
| 23:24 | <Hixie> | i wonder why that suddenly works again |
| 23:24 | <Hixie> | maybe my whining to them actually had an effect |
| 23:35 | <Philip`> | Dotnetdotcom.org says they're in the process of putting their data on http://aws.amazon.com/publicdatasets/ , which should be good since you could process the data on EC2 without downloading anything |
| 23:36 | <Philip`> | (where "their data" is a 9 million page sample from a 7 billion page crawl) |
| 23:40 | gsnedders | wonders whether uninstalling specific things is the right way to reduce clutter on this computer, with the amount of clutter, instead of uninstalling all and starting again |
| 23:46 | <mpilgrim> | Philip` of course i was thinking of running the service on an app hosting provider like appengine and just updating it once a day from an auto-updating windows machine |
| 23:47 | <mpilgrim> | but i don't have an always-on windows machine, so i can't do it |
| 23:51 | <annevk3> | are there any cool people still running Windows anyways? |
| 23:56 | <Hixie> | i wonder if the http people have complained to the ietf tools people about the submission tool using a GET request for posting confirmation |