| 00:25 | <paul_irish> | what's the use of having DOMContentLoaded bubble? http://html5.org/tools/web-apps-tracker?from=5239&to=5240 |
| 00:25 | <TabAtkins> | It's what browsers do right now. |
| 00:26 | <paul_irish> | but it has nowhere to bubble to.. ? |
| 00:26 | <TabAtkins> | Document to Window. |
| 00:28 | <paul_irish> | indeed. I had been under the misunderstanding that no event bubbled from doc to window |
| 00:28 | <paul_irish> | and was wrongggg. |
| 00:29 | TabAtkins | likes looking like he's smart and well-informed when really he just reads his email obsessively. |
| 01:17 | <Hixie> | TabAtkins: i feel the same way about learning things by reading wikipedia :-P |
| 01:18 | <Hixie> | "just in time learning" |
| 01:23 | <TabAtkins> | Yay gay people can marry again in my state! |
| 01:24 | <Hixie> | for a brief period between the district court overturning the ammendment and the supreme court reverting the decision |
| 01:24 | <TabAtkins> | Yeah, so get in all your marriages quick-like. |
| 01:44 | <roc> | Hixie: I actually quite enjoy air travel ... US domestic is awful, but international long distance is better |
| 01:44 | <roc> | at least around here it is |
| 03:14 | <Hixie> | roc: yeah outside the US is orders of magnitude better |
| 03:14 | <Hixie> | roc: the US airlines just seem to have forgotten to compete |
| 05:13 | <karlcow> | http://www.pigsgourdsandwikis.com/2010/08/what-nixonland-means-for-epub.html |
| 06:14 | <MikeSmith> | is using window.location.hash more widely supported than document.location.hash? |
| 06:14 | <MikeSmith> | or are they pretty much the same and it doesn't matter which I use? |
| 06:15 | <MikeSmith> | and was either of them actually specified somewhere prior to HTML5? |
| 06:15 | <MikeSmith> | ah |
| 06:15 | <MikeSmith> | Window object spec |
| 06:20 | <Hixie> | they're the same (literally the same object) |
| 06:20 | <Hixie> | HTML5 was the first to specify them as far as I know |
| 06:20 | <Hixie> | (the Window object briefly had some stuff take from HTML) |
| 06:31 | <MikeSmith> | Hixie: OK, thanks |
| 08:12 | <Cesarino> | Hi all? |
| 08:14 | <Cesarino> | Nederlands hier? |
| 08:20 | <annevk5> | soms |
| 08:20 | <Cesarino> | hoe zet je in html5 video als background? |
| 08:20 | <annevk5> | gewoon dingen eroverheen zetten? |
| 08:21 | <Cesarino> | ja |
| 08:21 | <Cesarino> | dingen er overheen zetten |
| 08:21 | <annevk5> | wel is van CSS gehoord? |
| 08:21 | <annevk5> | ;) |
| 08:21 | <Cesarino> | ja |
| 08:22 | <annevk5> | wat is het probleem dan? |
| 08:22 | <Cesarino> | ah, heb nog niet geprobeerd, dus gewoon, video als background zetten? |
| 08:22 | <Cesarino> | video tag niet gebruiken? |
| 08:22 | <annevk5> | ah nee |
| 08:22 | <annevk5> | je hebt wel <video> nodig |
| 08:22 | <annevk5> | maar je kan er gewoon dingen overheen positioneren op meerdere manieren |
| 08:23 | <Cesarino> | ah |
| 08:23 | <Cesarino> | en container overheen positioneren? |
| 08:23 | <annevk5> | bijvoorbeeld |
| 08:24 | <Cesarino> | zal eerst eens testen :-/ |
| 08:24 | <Cesarino> | ok, thx |
| 08:44 | <MikeSmith> | http://twitter.com/myakura/status/20370867502 |
| 08:44 | <MikeSmith> | "looks like WebKit's got a HTML5 treebuilder: http://trac.webkit.org/changeset/64712"; |
| 08:44 | <MikeSmith> | "Enable HTML5 tree builder" |
| 08:49 | <MikeSmith> | Peter`: seems the HTML5 tree builder is now enabled in WebKit trunk |
| 08:52 | <Peter`> | MikeSmith: http://twitter.com/beverloo/status/20367118193 ;-) |
| 08:52 | <Peter`> | Thank you though! |
| 08:53 | <MikeSmith> | ah man, you're always way ahead of me :) |
| 08:53 | <Peter`> | I wrote an extension for Chrome which notifies me of chromium/webkit commits, that helps a lot :) Plus I tend to cc myself to bugs |
| 08:54 | <Peter`> | WebKit's still building here, going to "try out" the builder myself |
| 09:32 | <Philip`> | "Wave has not seen the user adoption we would have liked. We [Google] don’t plan to continue developing Wave as a standalone product" - hmm, that didn't last long |
| 09:35 | <jgraham> | Yeah |
| 09:35 | <jgraham> | It suffered a bit from second system syndrome |
| 09:36 | <jgraham> | and a lot from having the suckiest UI imaginable |
| 09:52 | <Workshiva> | And from not supporting Opera, obviously |
| 10:26 | <annevk5> | not quite sure yet, but hybi discussion might be about distributed extensibility! |
| 10:26 | <annevk5> | quelle surprise |
| 10:28 | <jgraham> | I don't even understand how that would work |
| 10:28 | <jgraham> | Unless they are talking about a) non-browser clients |
| 10:29 | <jgraham> | or b) extensions made by browsers |
| 10:29 | <jgraham> | a) is totally uninteresting |
| 10:30 | <annevk5> | to us yes |
| 10:30 | <annevk5> | not to them supposedly |
| 10:30 | <jgraham> | If you _only_ care about non-browser clients, why do you care about websockets |
| 10:31 | <jgraham> | It makes no sense |
| 10:31 | <Philip`> | Should have named it WebBrowserSockets to avoid ambiguity |
| 10:31 | <jgraham> | It makes sense to care about browser + non-browser clients |
| 10:31 | <annevk5> | jgraham, that has been hixie's argument too |
| 10:31 | <Philip`> | WebBrowserJavaScriptSockets, even |
| 10:31 | <jgraham> | But I don't see why you make a service that actually didn't work in browsers |
| 10:32 | <annevk5> | jgraham, apparently if browsers start doing something network infrastructure will let it through too; they hope to make use of that or something |
| 10:32 | <jgraham> | (well I guess it would maybe work) |
| 10:32 | <annevk5> | at least, I suppose that is the reason otherwise they could just make their own protocol |
| 10:32 | <micheil> | websockets currently work as both client and server in node.js :d |
| 10:35 | <micheil> | although, admittedly I think how the websocket client is being used within node is kinda wrong though |
| 15:47 | <annevk5> | lol at autofocus thread |
| 15:47 | <annevk5> | not sure why i even got involved |
| 15:47 | <annevk5> | xhr test suite meanwhile is progressing nicely |
| 15:47 | <annevk5> | mostly trimming at the moment |
| 16:01 | <Cesarino> | how do you set a video background with html5? |
| 16:04 | <annevk5> | http://stackoverflow.com/ |
| 17:26 | <erlehmann> | gsnedders, can it be that the php html5lib does not handle comments as of yet? |
| 17:29 | <gsnedders> | erlehmann: Um, it should |
| 17:29 | <gsnedders> | Or do you mean within script? |
| 17:29 | <gsnedders> | That it doesn't |
| 17:29 | <gsnedders> | (I've already implemented all of those states once in the Python version, I don't want to do that again…) |
| 17:29 | <erlehmann> | within <style>. i use the '>' CSS selector |
| 17:29 | <erlehmann> | which breaks if it gets converted to '>' |
| 17:30 | <erlehmann> | or is that a browser issue? |
| 17:30 | <erlehmann> | any idea how i could handle that? |
| 17:32 | <gsnedders> | You mean <style>foo > bar {}</style> |
| 17:32 | <gsnedders> | Or…? |
| 17:33 | <erlehmann> | yes, indeed. |
| 17:33 | <erlehmann> | and i thought i could work around that by commenting it out. was i wrong? |
| 17:34 | <erlehmann> | (well, obviously, i was. but how wrong exactly?) |
| 17:34 | <gsnedders> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3Efoo%20%26gt;%20bar%20{}%3C/style%3E is identical everywhere |
| 17:37 | TabAtkins | wishes that rel=noreferrer worked on more things than just <a>. |
| 17:38 | TabAtkins | has figured out how to avoid sending a referrer with an <img> by using an iframe pointing to a data: url containing an iframe pointing to the image. |
| 17:38 | <TabAtkins> | But that's dumb. |
| 17:39 | <gsnedders> | That's insane |
| 17:39 | <TabAtkins> | I know! |
| 17:40 | <TabAtkins> | I don't even quite understand why it works - surely the inner iframe would send a unique origin as its referrer? |
| 17:40 | <TabAtkins> | But I haven't actually tested it to see what value gets sent. |
| 17:40 | <TabAtkins> | (Well, I highly suspect that no value is sent, since it works for the purpose of avoiding referrer-based hotlinking avoidance.) |
| 17:42 | <TabAtkins> | Once again, one of Leif's messages starts out dumb but understandable, and then makes a right-turn into incomprehensible. |
| 17:42 | <TabAtkins> | Namespacing the <script> element oasf;lgna;dlfj |
| 17:42 | <erlehmann> | lolwut |
| 17:43 | <TabAtkins> | The issue 41 thread. |
| 17:46 | <othermaciej> | does the proposal that he was talking about say anything about namespacing the script element? |
| 17:46 | <TabAtkins> | No, it doesn't. |
| 17:46 | <TabAtkins> | That would be the "right-turn into incomprehensible" part. |
| 18:13 | <jarib> | not sure if this is the right place to ask, but i have a question about webidl |
| 18:13 | <jarib> | a while back i wrote a ruby webidl parser based on http://dev.w3.org/2006/webapi/WebIDL/#idl-grammar |
| 18:13 | <jarib> | since then, it seems like the array type T[] has been introduced without it being reflected in the grammar |
| 18:14 | <jarib> | at least i can't spot it |
| 18:16 | <jarib> | this seems to be the commit http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.xml.diff?r1=1.197&r2=1.198&f=h |
| 18:17 | <jarib> | if someone can confirm that i'm not just blind, that'd be helpful :) |
| 18:18 | <erlehmann> | gsnedders, forget everything i said. since even XML processors apparently work fine with unencoded >, I opted for a simple string replacement to make everything fit. :) |
| 18:38 | <TabAtkins> | Arghsdlfkj margin-collapse is so complicated. >_< |
| 18:38 | <TabAtkins> | I thought I'd successfully interned all the rules and distilled them into some simple intuitions. But then dbaron had to go and throw me a new testcase that's all kinds of crazy. |
| 18:49 | <dbaron> | TabAtkins, I'm starting to think the way the spec describes things makes them more confusing than needed (and also makes it easy to write ambiguous wording in the spec itself, since saying "margins A and B do not collapse" is ambiguous if there's a possibility of any other margins between them) |
| 18:49 | <TabAtkins> | dbaron: I'm rereading your response to the issue 158 thread, where you were concerned that my simplification of the second bullet point was a normative change. |
| 18:50 | <TabAtkins> | I can't tell where in the spec any mention is directly made of margins of the children of a self-adjoining element not being included. |
| 18:51 | <TabAtkins> | (I'm nearly done with my writeup of a resolution to 158 and 178, consisting almost entirely of non-normative notes and informative diagrams.) |
| 18:51 | <TabAtkins> | (I just want to establish exactly what change, if any, I'm making with the simplification to the second bullet point.) |
| 18:52 | <TabAtkins> | Were you referring to the fact that the current second bullet point only makes mention of the block's top margin, not any child margins that may be collapsing with the top margin? |
| 18:53 | <Hixie> | TabAtkins: <div><span></span></div> if the span has 'clear:both' and there's a float before it? (i may be wrong about that) |
| 18:54 | <TabAtkins> | You mean like <float></float><div><span clear></span></div>? |
| 18:54 | <Hixie> | something like that |
| 18:54 | <gsnedders> | Oh shit. Civ V comes out two weeks after I start uni. |
| 18:54 | <Hixie> | the span can end up with clearance even though the div would otherwise be self-adjoining? |
| 18:55 | <Hixie> | i don't know if that's what you mean, this is just a drive-by comment |
| 18:55 | <TabAtkins> | gsnedders: Hahaha! |
| 18:56 | <TabAtkins> | Hixie: Hrm. Implementations appear to not care about that. The child produces clearance, but then the parent and subsequent siblings of the parent don't pay attention to it. |
| 18:56 | <TabAtkins> | In other words: goddammit. |
| 18:58 | <Hixie> | i really would just advise you to not bother changing any of this text and just rely on the existing test suites |
| 18:58 | <TabAtkins> | Well, at the very least I need to change the term "these margins" to something that actually makes sense. |
| 18:59 | <TabAtkins> | (In the sentence "The amount necessary to make the sum of the following equal to the distance to which these margins collapsed when the hypothetical position was calculated:".) |
| 18:59 | <Hixie> | you are not seriously going to make me open the spec and try to page back in all my margin collapsing knowledge. :-P |
| 19:00 | <Hixie> | where is that sentence |
| 19:00 | <TabAtkins> | I seriously am. It's your fault in the first place for using a pronoun to refer to some vague set of margins discussed in a pargraph preceding the list itself. |
| 19:00 | <Hixie> | i don't see it in 8.3.1 |
| 19:00 | <TabAtkins> | 9.5.2, second bullet point. |
| 19:00 | <TabAtkins> | I mean, second numbered step. |
| 19:00 | <gsnedders> | TabAtkins: Oh well, I probably won't have any computer capable of playing it at uni anyway. I guess I'm saved. :P |
| 19:00 | <TabAtkins> | gsnedders: From what I hear, it runs on computers able to run Civ 4 just fine. |
| 19:00 | <Hixie> | it's refering to "the top margin of the element has been collapsed with previous adjacent margins (including the top margin of the parent block). |
| 19:00 | <Hixie> | " |
| 19:01 | <Hixie> | nothing vague about it |
| 19:01 | <TabAtkins> | Okay, I'll clarify that reference. |
| 19:01 | <TabAtkins> | Now, "previous adjacent margins" there actually means just "adjoining margins, per the rules in 8.5.2", right? |
| 19:02 | <TabAtkins> | Because margins of children of a self-adjoining clearing element are included in clearance computation. |
| 19:02 | <Hixie> | it means the ones before the current one |
| 19:02 | <Hixie> | as opposed to any margins after the current one |
| 19:02 | <TabAtkins> | Yes, but "before" and "after" are both ambiguous when you're dealing with separate levels. And if "before" doesn't include children, it appears to be wrong per implementations. |
| 19:03 | <TabAtkins> | s/before/previous/ |
| 19:03 | <Hixie> | implementations don't get this stuff right |
| 19:03 | <Hixie> | ignore the implementations |
| 19:03 | <gsnedders> | TabAtkins: Don't tell me that. |
| 19:03 | <TabAtkins> | Dude, Hixie, as far as I can tell implementations *agree*. That's wondrous in the first place. |
| 19:04 | <Hixie> | if you're planning on changing the normative meaning of this to match implementations, you're on your own, i'm outta here. I've gone through that pain before! |
| 19:04 | <Hixie> | it's not worth it! |
| 19:04 | Hixie | runs away |
| 19:04 | <TabAtkins> | Haha. |
| 19:04 | <TabAtkins> | gsnedders: Sorry. We'll go down in flames together. |
| 19:04 | <gsnedders> | In Flames? Good idea. |
| 19:05 | <jarib> | any suggestions for what would be the best place to ask my webidl question? |
| 19:05 | gsnedders | puts on Lunar Strain |
| 19:09 | <dbaron> | TabAtkins, FWIW, I think the spec *might* be easier to explain if it were described in a form like http://etherpad.mozilla.com:9000/MarginCollapsingSpecRewrite ... though I'm not sure if that big a change in how it's described is worth it |
| 19:10 | <Hixie> | if we're going to rewrite it that much, we should just bite the bullet and convert the text to RFC2119-style at the same time |
| 19:11 | <dbaron> | yeah |
| 19:11 | <Hixie> | that way at least when we get around to rewriting all of CSS in that style, we'll already have the margin collapsing done! |
| 19:11 | <dbaron> | If we were, I would... but I was just prototyping |
| 19:11 | <Hixie> | personally i'm still firmly in the "leave it alone" camp |
| 19:11 | <dbaron> | That said, almost all of the text I wrote is in the form of definitions, so it really just needs a single MUST at the end ;-) |
| 19:11 | <TabAtkins> | Agreed. I'll just make the smallest changes possible for now, and put MUSTifying this section (along with the rest of CSS) on my "medium future project" pile. |
| 19:11 | <Hixie> | dbaron: yeah |
| 19:12 | <dbaron> | One problem with the current spec is that defining things directly in terms of a definition that we have to keep transitive means that we can mess up the transitivity of "collapses with" |
| 19:12 | <jgraham> | jarib: There are no good places for WebIDL questions, but here is no worse than any other |
| 19:12 | <dbaron> | (which there's at least one broken occurrence of in the current spec, and Tab was close to introducing a second) |
| 19:13 | <dbaron> | There are two obvious ways to mess it up: (1) define A collapses with B, B collapses with C, and A does not collapse with C or (2) define A does not collapse with C without saying which of A and C, if any, the margins between them collapse with |
| 19:20 | <jarib> | jgraham: heh, ok |
| 19:21 | <jarib> | not sure how common it is that things like that get out of sync |
| 19:22 | <jarib> | perhaps i'll just write the author directly |
| 19:22 | <TabAtkins> | Hixie , dbaron: I can't remember what case triggers the second step. I know it's relevant when the position of the float is dependent on some margins collapsing, but the clearance uncollapses them and makes the float move upwards. |
| 20:28 | <AryehGregor> | Have any mobile browser teams considered auto-collapsing <nav>/<header>/<footer>/etc.? |
| 20:28 | <AryehGregor> | It seems natural to save space, and might encourage more correct author usage. |
| 20:29 | <Peter-> | <header> usually contains the title of an <article>, that'd result in half-visible pages |
| 20:29 | <Peter-> | they're not only used on the document-level |
| 20:29 | <AryehGregor> | Yeah, I thought of that, they'd have to specially slurp out <h*> and display that even if the container is collapsed. |
| 20:30 | <AryehGregor> | Still sounds like an interesting idea in theory. |
| 20:30 | <AryehGregor> | Since boilerplate is a pain to scroll past on a small screen. |
| 20:30 | <AryehGregor> | Although nowadays, the high-end cell phones have resolutions not much less than full-size monitors, so . . . |
| 20:30 | <AryehGregor> | At least if "the high-end cell phones" is interpreted to mean "the iPhone 4". |
| 20:31 | <AryehGregor> | I get annoyed by the .3F every time I see this URL: http://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F |
| 20:32 | <AryehGregor> | I wrote a feature to make id's include anything except whitespace, but it broke some browsers, so I didn't enable it by default. :( |
| 20:36 | AryehGregor | tests again |
| 20:38 | <erschlafmann> | I am using HTML5 with RDFa. Where is your god now? http://gsoc2010.dieweltistgarnichtso.net/?p=63 |
| 20:38 | <erschlafmann> | Also, who would be the right person to advise me on that? I suppose it isn't Hixie. |
| 20:38 | <TabAtkins> | You should be generating RDFa5. |
| 20:40 | <erschlafmann> | And use Wordpress5? |
| 20:40 | <TabAtkins> | rdfa5 actually exists, though! |
| 20:40 | <TabAtkins> | http://www.xanthir.com/etc/rdfa5.html |
| 20:42 | <erschlafmann> | Wasn't that some kind of practical joke? |
| 20:42 | <TabAtkins> | Only half! |
| 20:42 | <erschlafmann> | Hue hue hue. |
| 20:43 | <TabAtkins> | It's "ha ha but serious". |
| 20:43 | <erschlafmann> | I guess my intermingling of standards will be fine. After all, the markup can be parsed by existing CC tools. |
| 20:45 | <erschlafmann> | But, alas, their licenses are still at version 3! They can't keep up. |
| 20:52 | <AryehGregor> | Blast it. I can't get IE support for redirects to my exotic section anchors. |
| 20:53 | <AryehGregor> | It's the Unicode that's the problem. Hmm. |
| 20:54 | <AryehGregor> | So, any ideas on getting IE to accept redirects to a URL with an anchor that contains Unicode? |
| 20:55 | <AryehGregor> | Direct links work. |
| 20:55 | <AryehGregor> | But it seems to misinterpret the character set of the Redirect header. |
| 20:55 | <AryehGregor> | Which is fair enough, I guess. |
| 20:55 | <AryehGregor> | urlencode()ing the fragment causes IE6 to fail completely. |
| 20:56 | <AryehGregor> | (even for ASCII punctuation, which it's otherwise okay with) |
| 20:57 | <AryehGregor> | Maybe I could stick to ugly anchors for redirects. |
| 20:58 | <Workshiva> | Maybe you could drop support for IE6 :P |
| 20:58 | <AryehGregor> | I wish. |
| 20:58 | AryehGregor | hasn't tested all other browsers yet anyway |
| 20:58 | <AryehGregor> | My notes say Opera 10.10 fails but Opera 10.50 works. On the other hand, my notes also say that IE6 works. |
| 20:58 | <AryehGregor> | So . . . |
| 20:59 | <Workshiva> | It's not that unrealistic, more and more places are dropping IE6 |
| 20:59 | AryehGregor | bets some of the code has changed in the interim |
| 21:09 | <jgraham> | Sigh |
| 21:09 | <jgraham> | I have clearly not explained myself very well on hybi |
| 21:11 | <jgraham> | Oh well, I don't have time to participate more now |
| 21:11 | <jgraham> | Probably just as well |
| 21:12 | <annevk5> | i'm getting sleepy |
| 21:13 | <annevk5> | i have fixed a bunch more XHR tests and noted some of the stuff that was missing |
| 21:13 | <annevk5> | one issue with doing everything on this fancy local server is that nobody can see what is happening :/ |
| 21:15 | <annevk5> | quite surprising how many clarifications made to the specification have not made it into implementations, even though they were requesting it :/ |
| 21:15 | <annevk5> | guess this will mean some more changes later on |
| 21:27 | AryehGregor | will abolish the .3F forever: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/70526 |
| 21:28 | AryehGregor | just needs to wait till trunk is a bit more stable to upgrade the WHATWG wiki. |
| 21:28 | <Hixie> | can someone else explain to roberto about how we look at how people are using technologies to see how to extend technologies? |
| 21:28 | <Hixie> | my various attempts don't seem to have conveyed the message properly. |
| 21:29 | <annevk5> | maybe tomorrow |
| 21:29 | <Workshiva> | AryehGregor: How ironic, my IRC client didn't parse your URL properly |
| 21:29 | <AryehGregor> | Workshiva, which URL? |
| 21:29 | <Workshiva> | The special:code one |
| 21:29 | <AryehGregor> | Why, the colon? |
| 21:29 | <Workshiva> | Yeah |
| 21:29 | <AryehGregor> | Colons are totally legitimate in the path part. |
| 21:30 | <AryehGregor> | RFC says so. |
| 21:30 | <Workshiva> | RFC also says that + is legit in email |
| 21:30 | <annevk5> | this hybi stuff is about 50% of my email I think |
| 21:30 | <TabAtkins> | Fix your IRC client - mine works fine on that link. |
| 21:30 | <annevk5> | prolly because nobody cares about HTML5 anymore ;p |
| 21:30 | <AryehGregor> | Anyone who refuses to implement the RFC on e-mail for sanity's sake is completely justified, though. |
| 21:31 | <Workshiva> | You don't have to implement the specifics, just don't reject non-crazy valid addresses |
| 21:31 | <AryehGregor> | MediaWiki just checks for the presence of "@". |
| 21:31 | <Workshiva> | I bet it can all be traced back to some twit who didn't want to allow + because it confused his regexp |
| 21:32 | <AryehGregor> | No, just some twit saying "meh, what characters have I seen in e-mails before? Let me just whitelist those." |
| 21:40 | <gsnedders> | What about quoted-string and comments!? |
| 22:42 | <Hixie> | What is that internet meme called wherein text is obfuscated using diacritics? |
| 22:44 | <boogyman> | Project Muse? |
| 22:45 | <Hixie> | http://en.wikipedia.org/wiki/Project_MUSE is definitely not what i meant |
| 22:47 | <hdhoang> | Zalgo? |
| 22:49 | <Hixie> | zalgo!!! |
| 22:49 | <Hixie> | thank you! |
| 23:39 | <Hixie> | where is the change controller for a URI scheme listed? |
| 23:40 | <Hixie> | http://www.iana.org/assignments/uri-schemes.html doesn't seem to list it |
| 23:40 | TabAtkins | is super-curious what spec Hixie is working on where Zalgo is relevant. |
| 23:41 | <Hixie> | TabAtkins: who said it was relevant? |
| 23:41 | <TabAtkins> | Well, you claim it'll get enshrined in a spec, at least. |
| 23:42 | <Hixie> | that's a whole different matter |
| 23:43 | <gsnedders> | That's what you say now… |