| 00:00 | <annevk> | thanks othermaciej |
| 00:17 | <annevk> | http://blog.whatwg.org/weekly-end-of-last-call |
| 00:17 | <annevk> | also gave myself a week off :) |
| 01:04 | annevk | hopes abarth's URL spec will end up in HTML one day |
| 01:06 | <abarth> | annevk: yeah, me too :) |
| 01:06 | <abarth> | i have all the info, i just need to find a couple hours to do it |
| 01:21 | <annevk> | if Mozilla throws a NS_ERROR_INVALID_POINTER, is that an indication of a problem? |
| 01:23 | <jamesr> | there seems to be a porblem |
| 01:25 | <annevk> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3Ex%3Cscript%3Etry%7Bdocument.body.replaceChild%28null%2Cdocument.createElement%28%22x%22%29%29%7Dcatch%28e%29%7Bw%28e%29%7D%3C%2Fscript%3E |
| 01:42 | <annevk> | AryehGregor, you should maybe make some wiki with W3C Process issues |
| 01:42 | <Hixie> | damowmow.com/playground/ideas-for-the-w3c might help if you do that ;-) |
| 01:42 | <annevk> | AryehGregor, I mean, would you please make one :) |
| 01:42 | <annevk> | Hixie, did you look at chairs⊙wo? o_O |
| 01:43 | <Hixie> | what post? |
| 01:43 | <Hixie> | i don't read the secret lists anymore |
| 01:44 | <annevk> | maybe a good idea |
| 01:45 | <annevk> | but e.g. http://lists.w3.org/Archives/Member/chairs/2011JulSep/0053.html (W3C Member-only) |
| 01:45 | <annevk> | not that it makes much sense |
| 01:46 | <hober> | annevk: good times |
| 01:46 | <Hixie> | ah, well, daniel and i often disagree about process things :-) |
| 01:46 | <Hixie> | (i'm assuming he disagrees with me, i didn't do more than skim it) |
| 01:46 | <wolfman2000> | evening. *checks topic* hmm...remind me to do that more often. |
| 01:47 | <wolfman2000> | how goes progress here? |
| 01:47 | <annevk> | wolfman2000, there's http://blog.whatwg.org/ |
| 01:48 | <annevk> | wolfman2000, and http://html5.org/tools/web-apps-tracker |
| 01:48 | <annevk> | both should give some indication of progress |
| 01:48 | <wolfman2000> | don't recall the blog the last time I was here. |
| 01:48 | <annevk> | wolfman2000, we even have http://twitter.com/WHATWG |
| 01:48 | <wolfman2000> | ...should have known |
| 01:49 | <wolfman2000> | everyone is going to twitter |
| 01:49 | <wolfman2000> | next thing I know, you guys will say you have a Google+ account |
| 01:49 | <annevk> | Google+ does not allow accounts for groups yet |
| 01:49 | <wolfman2000> | don't know if that's good or bad |
| 01:49 | <Hixie> | i did sign up for the company profile thing for whatwg |
| 01:49 | <Hixie> | doubt we'll get in on teh beta though :-) |
| 01:49 | <annevk> | ah cool |
| 01:50 | <wolfman2000> | well, that covers one of my purposes here. |
| 01:51 | <wolfman2000> | The other purpose will depend on whether a particular user is active...and even then, I'd have to take that conversation to PM or a different channel |
| 01:51 | <annevk> | alright |
| 01:52 | <wolfman2000> | so hopefully it won't be a problem if I idle in here until he is around |
| 01:52 | <wolfman2000> | also, now following you guys on twitter to make things easier |
| 01:52 | <annevk> | there's no rules here |
| 01:54 | <wolfman2000> | strange thing, but I can adapt. |
| 02:23 | <Hixie> | annevk5: it's interesting how the responses kinda miss the point |
| 02:23 | <Hixie> | e.g. chaals talks about how the process i describe would make the editor "all powerful" |
| 02:23 | <Hixie> | but it would actually make the editor as powerless as the whole w3c is now |
| 02:29 | <benschwarz> | Hixie! |
| 02:58 | <erlehmann> | Hixie, could you suggest readings on community gouvernment that influenced you? |
| 03:17 | <Hixie> | benschwarz! |
| 03:17 | <Hixie> | erlehmann: community gouvernment? |
| 03:17 | <Hixie> | erlehmann: oh you mean like how to run a community? |
| 03:18 | <Hixie> | erlehmann: http://video.google.com/videoplay?docid=-4216011961522818645 or http://www.youtube.com/watch?v=-F-3E8pyjFo |
| 03:18 | <Hixie> | erlehmann: and similar talks |
| 03:18 | <Hixie> | in the first of those i think you can see the back of my head in the audience at one point :-) |
| 03:18 | <erlehmann> | Hixie, whatever you call it. i am interested for example, why you prefer descriptive over normative standards and stuff. |
| 03:19 | <Hixie> | oh, that's not really about community building |
| 03:19 | <Hixie> | hm |
| 03:19 | <erlehmann> | also, how to respond to volunteers without driving them off. i think the whatwg did a pretty good job with that. |
| 03:19 | <Hixie> | what makes you think i prefer descriptive standards over normative standards? |
| 03:19 | <Hixie> | how to respond to volunteers is exactly what those videos are about, so that answers that one |
| 03:20 | <erlehmann> | your comments on codecs in particular, like “speccing that so-and-so won't change apple's stance on it“ |
| 03:20 | <Hixie> | (in fact just watch all the videos that you find in a search for [brian fitzpatrick and ben collins sussman]) |
| 03:21 | <erlehmann> | ima gonna do that some time this week. thank you. |
| 03:22 | <erlehmann> | oh, and context: i maintain the dev branch of a minecraft clone. first project having significant contributions from people i do not personally know. |
| 03:22 | <Hixie> | erlehmann: "speccing that so-and-so won't change apple's stance on it" doesn't mean i prefer descriptive over normative standards |
| 03:22 | <Hixie> | erlehmann: it's just that you can't have normative standards if you don't have any power over the people who use them |
| 03:22 | <erlehmann> | oh. thanks for clearing that up, then. |
| 03:22 | <Hixie> | erlehmann: so descriptive standards are the only option on the webd |
| 03:22 | <Hixie> | web |
| 03:23 | <Hixie> | personally i'd much rather we had normative standards, then i could just spec what i wanted and not listen to any feedback, my life would be way easier :-P |
| 03:23 | <zewt> | text/hixie |
| 03:26 | <erlehmann> | there was a german joke made about that: „in relation to the browser makers, we are all petitioners“ – only that the german word for someone petitioning “bittsteller” can also be mis-construed as “someone who places bits” |
| 03:29 | <erlehmann> | a web dev said that at the end of a panel discussion in april. pretty good ad-hoc humor, in my opinion :) |
| 04:07 | <wolfman2000> | zewt: are you around? |
| 08:10 | <hsivonen> | I feel so baited to reply to http://www.jenitennison.com/blog/node/160#comment-11185 even though I know I should be reviewing and writing code today |
| 08:12 | <erlehmann> | >threads on google+ |
| 08:12 | <erlehmann> | >deleted a sizable amount of my friends' accounts |
| 08:12 | <erlehmann> | do not want ;_; |
| 08:14 | <Hixie> | what on earth does it mean to be called a "Jacobin"? My ancient political history apparently fails me |
| 08:14 | <Hixie> | erlehmann: why did they delete accounts? did your friends escalate? |
| 08:15 | <jacobolus> | Hixie: they were a political club in revolutionary france |
| 08:15 | <Hixie> | hsivonen: it baffles me how people think standards have any power |
| 08:15 | <Hixie> | jacobolus: that much i gathered from wikipedia |
| 08:15 | <jacobolus> | Hixie: calling someone a Jacobin roughly implies someone who cares mainly about ideological purity |
| 08:16 | <erlehmann> | Hixie, they used their nick names. i have gone back to a normal feedreader since then. |
| 08:16 | <jacobolus> | hah. just looked at wikipedia, which apparently uses the same phrase as description :) |
| 08:17 | <Hixie> | erlehmann: you mean they violated the terms of service and then the terms of service were applied? i'm not saying i agree with the policy, but it seems silly to complain about a site doing what it said it would do. |
| 08:17 | <Hixie> | erlehmann: anyway, they can just put in the more common names they're actually known by and the accounts will be restored |
| 08:17 | <Hixie> | jacobolus: but what does it mean to be called a jacobian? is that good or bad? |
| 08:17 | <Hixie> | jacobolus: oh, sorry, missed your answer |
| 08:17 | <jacobolus> | it's certainly derogatory |
| 08:18 | <erlehmann> | sometimes the common name is just „plomlompom“ or something equally weird. |
| 08:18 | <hsivonen> | did the Gmail ToS prohibit pseudonyms, too? |
| 08:18 | <jacobolus> | it means you'll toss out allies who don't live up to an impossible extremist standard |
| 08:18 | <Hixie> | hsivonen: no (and still doesn't, to my knowledge) |
| 08:18 | <hsivonen> | the scariest part of G+ ToS getting applied is people getting their Gmail account closed, too |
| 08:19 | <hsivonen> | dunno if that's happened over pseudonyms, but, reportedly, it has happened over age requirement |
| 08:19 | <Hixie> | erlehmann: if someone really is called that then it should be easy to demonstrate it. but i can understand people doubting that someone is called that in person. |
| 08:20 | <erlehmann> | Hixie, i think you are absolutely right with the tos. i think they should move out of the google namespace. |
| 08:20 | <hsivonen> | maybe the age requirement is in the Gmail ToS, too, but it's terrible to close a non-American kid's email account without asking the parents when the U.S. law would allow parental consent and the kid isn't in the U.S. anyway |
| 08:20 | <Hixie> | hsivonen: as i understand it from media reports (i have no inside knowledge) there is one case where someone who was already violating the ToS (<13) had their account suspended pending parental approval after they tried to join G+ (which is closed to <18 anyway) and corrected their birthday. |
| 08:20 | <jacobolus> | Hixie: "The Jacobins assumed more and more power during the spring of 1793, with the support of the Parisian mob, which overawed the Convention, culminating in a coup at the end of May. They were to hold power until the summer of 1794, and they repeatedly purged the Convention of those they held disloyal to the Republic, ending with a widespread program of execution, the Reign of Terror in their last months. Robesp |
| 08:20 | <jacobolus> | ierre, generally the spokesman for the successful faction, had great esteem for his reputation as "the sea-green incorruptible", and set up the slogan of the Republic of Virtue, until the Jacobins' last purge, 9 Thermidor, July 27, 1794, Robespierre attempted suicide and only succeeded in shattering his lower jaw. He was executed the next day on Thermidor 10, July 28, 1794.[7]" |
| 08:20 | <Hixie> | hsivonen: but we already have a system in place that lets the parents unsuspend the account in that case, so i dunno why it made the news |
| 08:21 | <jacobolus> | there's wikipedia again |
| 08:21 | <erlehmann> | unfortunately, without g+ providing feeds and publish APIs, that is problematic. oh well. |
| 08:21 | <erlehmann> | walled gardens again. |
| 08:21 | <Hixie> | jacobolus: wow, glad he is reconsidering! |
| 08:21 | <hsivonen> | Hixie: oh. I guess it wasn't at all clear to the parents that there was such a system |
| 08:21 | <erlehmann> | my sister read that article. she's ten. uses google mail. though not for anything important, by her own account. |
| 08:21 | <erlehmann> | she's scared now. i showed her IMAP and will help her migrate. |
| 08:22 | <Hixie> | hsivonen: either that or they were trying to get attention. I've seen several cases where that's happened. |
| 08:22 | <hsivonen> | I've become more scared of having a foreign BigCo manage my identity when I've lately been trying to unlock an old Apple ID of mine |
| 08:23 | <erlehmann> | the funniest case in germany is a woman whone last name can be literally translated as „unknown“. of course social networks kill her accounts. |
| 08:23 | Hixie | is a big proponent of open federated standards for this kind of thing |
| 08:23 | <Hixie> | any one vendor being in control of anything is a dangerous situation, however benevolent the vendor. |
| 08:24 | <erlehmann> | indeed. i don't understand why my friends did that stuff. but then i consider g+ a big imageboard. though lacking features. |
| 08:24 | <hsivonen> | so far, iforgot.apple.com doesn't work for my old Apple ID, phone support directed me to iTunes email support and iTunes email support person is having scripted conversations with me and their scripts don't seem to cover dealing with decade-old Apple IDs that have never been used in the iTunes store |
| 08:24 | <erlehmann> | and by „did that stuff“, i mean „use it instead of using their own servers“. |
| 08:24 | <erlehmann> | oh itunes. the internet explorer 6 of the media players you are. |
| 08:26 | <hsivonen> | Are all new Apple IDs required to be email addresses? Is it even possible to register @-less Apple IDs anymore? |
| 08:26 | <erlehmann> | regarding google+: i can only hope that people realized they should not whine when stuff breaks. unless they pay for it. |
| 08:26 | <hsivonen> | where the @-part is implied to be @mac.com for iChat purposes |
| 08:26 | <hsivonen> | the Apple ID page still talks about iChat |
| 08:27 | <erlehmann> | it still looks like a PR problem from here. maybe only in germany. |
| 08:27 | <erlehmann> | or maybe only with early adopters from hacker culture. |
| 08:27 | <hsivonen> | if I register an Apple ID with @whatever and whatever doesn't have the XMPP DNS stuff, how would it work in iChat? |
| 08:35 | <hsivonen> | It's so frustrating to go back and forth with a support person who is following a script instead of paying good attention to what I say. |
| 08:36 | <erlehmann> | the only good support i ever had via phone was a short talk that amounted to „just remove the yellow disk on the underside with a screw driver and clean it“ |
| 08:36 | <hsivonen> | If Apple has a policy against letting me revive my old Apple ID, I'd prefer them to tell me instead of spewing scripted answers to me |
| 08:37 | <hsivonen> | erlehmann: oh, Apple's phone support was clued but the phone guy wasn't empowered to poke at the Apple ID database |
| 08:37 | <erlehmann> | oha! |
| 08:37 | <hsivonen> | erlehmann: he pointed me to iTunes Store support and it went downhill from there |
| 08:38 | <erlehmann> | why do you need to revive it anyway? can't you just create a new one? or is stuff tied to it? |
| 08:39 | <erlehmann> | like .mac trial or something? (i am guessing here) |
| 08:39 | <hsivonen> | erlehmann: in case the ID is now or in the future exposed in some communication service (as it used to be exposed in iChat), I want to be known as "hsivonen" as in other services |
| 08:39 | <hsivonen> | if it won't be exposed anywhere public, I guess then I shouldn't care |
| 08:39 | <erlehmann> | oh well. |
| 08:39 | <erlehmann> | namespace issues again ;) |
| 08:42 | <hsivonen> | I supposed it's rational for them to by default assume that I'm clueless, but it's still so very annoying |
| 08:42 | <hsivonen> | *suppose |
| 08:45 | <erlehmann> | funny. one of my acquaintances was not deleted, though he has used his IRL nickname and added „dings“ (like the idiom „foo“) |
| 08:46 | <erlehmann> | i wonder if there is something done manually, he is somewhat popular. |
| 08:46 | <erlehmann> | oh well. |
| 08:57 | <hsivonen> | looks like Darth Vader got kicked out of G+, too |
| 10:07 | <hsivonen> | why does Chrome decode this as UTF-8? http://m.gsmweb.cz/ |
| 10:08 | <hsivonen> | is Chrome applying on-by-default heuristics to detect UTF-8 when there's no declaration? |
| 10:08 | <hsivonen> | or is Chrome willfully violating HTML5 and honoring the XML decl? |
| 10:09 | <espadrine`> | What is the reason behind requiring btoa input to be below U+00FF? Is it technical, or historical? |
| 10:19 | <Philip`> | espadrine`: What would you expect it do for >= U+0100? |
| 10:21 | <Philip`> | (Base-64 is an algorithm that's defined over 8-bit values so it's unclear what should happen to larger values) |
| 10:22 | <Philip`> | (and you can't just do an implicit UTF-8 encode because then btoa and atob couldn't be exact inverses any more) |
| 11:45 | <hsivonen> | hmm. looks like Chrome is better at detecting Polish ISO-8859-2 text as ISO-8859-2 than Firefox, IE and Opera |
| 11:47 | <hsivonen> | whoa. Poland and Germany both have high Firefox usage but the usage by Firefox version is *very* different |
| 11:47 | <hsivonen> | oops. no matter. I was looking at the wrong numbers |
| 11:48 | <espadrine`> | Philip`: ah, ok (I was thinking indeed about a utf-8 encode) |
| 12:53 | <karlcow> | ePub previewer http://dl.dropbox.com/u/160781/apps/mac/Murasaki/index.html |
| 13:02 | <jgraham> | karlcow: Seems like one should just implement an ePub reader in HTML since they are basically HTML documents |
| 13:04 | <jgraham> | Alternative theory: it seems like ePub should just be plain HTML with a few specific conventions |
| 13:04 | <karlcow> | It's what is done already by most epubreaders I think. Not sure I understand what you mean :) |
| 13:05 | <hsivonen> | I'm feeling an 386 urge to reply to http://www.jenitennison.com/blog/node/160#comment-11185 again. I need to learn to look away. |
| 13:05 | <jgraham> | karlcow: Well I mean clearly that uses WebKit for the rendering. But I mean you may as well make the rest of the UI HTML too. Especially for a "preview" reader |
| 13:06 | <jgraham> | Although I understand that some people will value the OSX integration |
| 13:07 | Philip` | likes the non-word "unanimosity" |
| 13:07 | <jgraham> | hsivonen: You could reply briefly with only the most important points |
| 13:07 | <karlcow> | jgraham: yup I found it by looking for an ePub Spotlight importer to just be able to full text search on the files I have. |
| 13:09 | <karlcow> | hsivonen: if you want to make constructive points to some things which seem general enough, do not leave a comment, but create a FAQ on your web site and point to it. |
| 13:09 | <karlcow> | The FAQ will have the benefits to be able to grow across time and subsequent blog posts |
| 13:14 | Ms2ger | wonders what http://www.w3.org/wiki/DOM/domcore is about |
| 13:15 | <hsivonen> | karlcow: maybe I should do that, but having a page that catalogs incorrect allegations and misunderstandings about me, the stuff I'm working on and stuff I don't want to work on would be a rather odd thing to have on my site |
| 13:15 | <Philip`> | http://www.legislation.gov.uk/%0C - yay XML |
| 13:16 | <hsivonen> | Philip` strikes again |
| 13:21 | <Philip`> | Hmm, their inline sitestat script code seems to not execute, because it's <script><!-- ... --></script> but served as XML so the comment gets ignored |
| 13:23 | <Philip`> | (which is lucky since http://www.legislation.gov.uk/"+alert(document.cookie)+"; would be an XSS hole if it did execute) |
| 13:24 | <Philip`> | (Oddly it does seem to prevent "--" being injected into the script code, but nothing else) |
| 13:25 | Philip` | guesses that's the consequence of using an XML templating system that thinks the page name is actually meant to be inserted into a legitimate comment |
| 13:26 | <Philip`> | (which is presumably introducing the vulnerability for any users without an XHTML-supporting browser) |
| 13:29 | <Philip`> | (Sticking an HTML5 serialiser on the output wouldn't help since that'll serialise the comment node inside the script element as <script><!-- ... and result in it becoming executable too) |
| 13:30 | Philip` | would like it if parsing tree-structured data wasn't so very complex :-( |
| 13:31 | <Philip`> | s/parsing/serialising and parsing/ |
| 14:29 | <gsnedders> | "inserted into a document" means if you follow parentNode you'll reach the Document node, right? |
| 14:33 | <Ms2ger> | That's "in a document" in DOM Core/HTML |
| 14:34 | <gsnedders> | Right, and inserted into is when it enters that state? |
| 14:34 | <gsnedders> | Yay I can understand specs. :3 |
| 14:36 | <Philip`> | Something is in a document once it's been inserted into a document? Who would've guessed! |
| 14:36 | jgraham | wonders what he wanted to say to Ms2ger |
| 14:38 | <jgraham> | Oh yes |
| 14:38 | Philip` | wonders what the Plain English Campaign would think about the specs |
| 14:38 | <jgraham> | Ms2ger: Do you have a link to the testharness.js/Mochitest integration bug? |
| 14:39 | <Ms2ger> | https://bugzilla.mozilla.org/show_bug.cgi?id=647323 |
| 14:39 | <jgraham> | Takk |
| 14:40 | Ms2ger | should figure out at what line length annevk wraps |
| 14:45 | <annevk> | uh? |
| 14:49 | jgraham | wonders which text editor annevk uses |
| 14:50 | Philip` | ponders what font annevk picked |
| 14:50 | Ms2ger | ponders Philip` |
| 14:51 | <annevk> | oh I get it now |
| 14:51 | <annevk> | 76 |
| 14:51 | <annevk> | TextWrangler, Monaco-12 |
| 14:52 | <Philip`> | An excellent choice |
| 14:52 | <jgraham> | Now you should blog about how that exact setup is the key to writing good specs |
| 14:53 | <Ms2ger> | Pff, 80, gedit, Monospace-10 beats that :) |
| 14:54 | <annevk> | gedit is nice |
| 14:55 | jgraham | was at least right in thinking annevk isn't an emacs/vi type |
| 14:56 | <Ms2ger> | Don't tell Hixie |
| 15:04 | <gsnedders> | Philip`: Well, question of whether inserted means in the tree or has ownerDocument. |
| 15:13 | <foolip> | does anyone know how to leave a W3C WG? http://www.w3.org/2004/01/pp-impl/42786/join exists but /leave does not |
| 15:15 | jgraham | tries to avoid humming hotel california |
| 15:16 | <Philip`> | foolip: Wait a year until you get automatically unsubscribed? |
| 15:16 | Philip` | wonders if that only applies to the HTML WG |
| 15:16 | <annevk> | foolip, you should talk to Charles |
| 15:18 | <annevk> | foolip, the /join form goes via Charles too |
| 15:18 | <foolip> | annevk, k |
| 15:43 | <Ms2ger> | "User agents may wish to offer the user more control over the provided media." |
| 15:43 | Ms2ger | wonders if that's an RFC2119 MAY |
| 15:51 | <Ms2ger> | <AryehGregor> git commands have seldom been faulted for having an insufficient number of options. |
| 15:51 | <Ms2ger> | Hah |
| 15:51 | <david_carlisle> | annevk: thanks for closing that bug |
| 15:53 | <annevk> | your welcome |
| 15:57 | <annevk> | btw |
| 15:57 | <annevk> | I learned my lesson |
| 15:58 | <annevk> | one Microsoft employee in the water, 500 dollar potential Apple hardware damages |
| 16:14 | <Ms2ger> | annevk, step 2 at http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-ensure-samedoc was for sync mutation events, not sure if it was a good idea |
| 16:15 | <annevk> | oh because adoptNode removes |
| 16:15 | <gsnedders> | Window.prototype.toString doesn't exist per WebIDL, right? |
| 16:16 | <annevk> | I think the idea is that the mutation event fire after all mutations happened |
| 16:16 | <annevk> | so an implicit call to adoptNode would not fire one |
| 16:16 | <annevk> | prolly need to split out the adoptNode algorithm to handle that scenario |
| 16:16 | <annevk> | better |
| 16:20 | <Ms2ger> | gsnedders, why would it? |
| 16:22 | <annevk> | btw |
| 16:22 | <gsnedders> | Ms2ger: Because Jeff Walden implied it did :) |
| 16:22 | <annevk> | the shadow DOM stuff apparently introduces a new Node type |
| 16:22 | <Ms2ger> | Boo, Waldo |
| 16:26 | <dglazkov> | good morning, Whatwg |
| 16:26 | <dglazkov> | annevk: yes! |
| 16:53 | <annevk> | so what is the plan dglazkov? |
| 16:53 | <annevk> | is Ian going to edit the specification? |
| 16:53 | <annevk> | or you? |
| 16:55 | <dglazkov> | It's going to be me and Dominic Cooney, for starters. |
| 16:55 | <dglazkov> | "for starters" is here, btw: http://dglazkov.github.com/component-model/ |
| 16:56 | <dglazkov> | the only section that's more or less spec'd is events: http://dglazkov.github.com/component-model/events.html |
| 16:56 | <dglazkov> | I essentially took Hixie's events section from XBL2 and wrote it down in algorithms. |
| 16:57 | <dglazkov> | unfortunately, I need to work on something different this quarter (WebKit hygiene related stuff) |
| 16:58 | <dglazkov> | so I am 20%-ing on the use cases/spec work at the moment |
| 16:59 | <dglazkov> | but I'll be back with the vengeance in October!! :) |
| 17:00 | <dglazkov> | annevk: does this make any sense? :) |
| 17:01 | <Ms2ger> | The web? None |
| 17:01 | <dglazkov> | Ms2ger: all we have to do is slightly adjust the definition of "sense" |
| 17:02 | <Ms2ger> | Apply a binding to the word, if you will |
| 17:02 | <dglazkov> | Ms2ger: you know me, I would much rather sub-class it |
| 17:02 | <dglazkov> | class WebSense : Sense |
| 17:02 | <Ms2ger> | { |
| 17:03 | <Ms2ger> | // Reimplement everything |
| 17:03 | <dglazkov> | / override all methods |
| 17:03 | <dglazkov> | :) |
| 17:04 | annevk | reads |
| 17:05 | Ms2ger | cleans up annevk's typos |
| 17:05 | <annevk> | sounds good dglazkov |
| 17:05 | <annevk> | you should probably announce that spec on WebApps |
| 17:06 | <dglazkov> | annevk: yes. |
| 17:13 | <annevk> | Ms2ger, I had the idea of not <dfn>'ing historical constants |
| 17:14 | <annevk> | Ms2ger, Web IDL already requires everything there is to need to know about them |
| 17:14 | <annevk> | Ms2ger, and they do not need to be referenced |
| 17:14 | <Ms2ger> | That works |
| 17:15 | gsnedders | would like Anolis to automatically semantically mark-up IDL blocks |
| 17:16 | <gsnedders> | (and make it possible to xref them, etc.) |
| 17:16 | <Ms2ger> | You mean, turn it into ReSpec? :) |
| 17:18 | <gsnedders> | ReSpec didn't exist when I started talking about implementing that :) |
| 17:18 | <Ms2ger> | Also, patches welcome |
| 17:19 | <annevk> | semantically how? |
| 17:20 | <annevk> | haven't changed exceptions because of the outstanding bug |
| 17:21 | <gsnedders> | annevk: basically making it possible to just type a pre/code block of WebIDL with no elements within it |
| 17:22 | <gsnedders> | annevk: And getting the same output as today |
| 17:22 | <annevk> | yeah that would be kind of cool |
| 17:23 | <Ms2ger> | Someone (who isn't me) should write a python WebIDL parser |
| 17:24 | <gsnedders> | Ms2ger: This was what I concluded. :) |
| 17:24 | <Ms2ger> | So, is the DOM Tree a tree? |
| 17:24 | Ms2ger | enjoys www-dom |
| 17:26 | annevk | replied with a link to wikipedia |
| 17:27 | <dglazkov> | oh good lord |
| 17:27 | dglazkov | feels bad for the poor guy |
| 17:27 | <Ms2ger> | gal* |
| 17:27 | <dglazkov> | pesone |
| 17:28 | <dglazkov> | ^^ person that is |
| 17:28 | <annevk> | Ms2ger, can http://dev.w3.org/2009/webidl-checker/webidl-check be reused in some way |
| 17:29 | <Ms2ger> | Wait, that's python? |
| 17:29 | Ms2ger | is confused |
| 17:29 | <annevk> | combined with XSLT |
| 17:29 | <dglazkov> | PYTHON IS AWESOME |
| 17:30 | <annevk> | oh it looks more like a nice hack |
| 17:30 | <annevk> | heycam, is there some Python parser for Web IDL that you know of? |
| 17:31 | <heycam> | annevk, not that I know of |
| 17:31 | <annevk> | also hi |
| 17:31 | <heycam> | hi :) |
| 17:31 | <heycam> | you might like to look at that es-operating-system project? to see what parser they're using |
| 17:32 | <zewt> | well that's lovely |
| 17:32 | <zewt> | "wait 30 seconds to download" sites that stop the countdown if you change tabs |
| 17:33 | <zewt> | three cheers for degenerate scripting abuses |
| 17:35 | <annevk> | http://code.google.com/p/es-operating-system/source/browse/#svn%2Ftrunk%2Fesidl |
| 17:39 | <zewt> | heh www-dom |
| 17:39 | <zewt> | should have suggested that a tree refers to the roots |
| 17:41 | <zewt> | i'd have assumed it was a troll if it wasn't from a named domain |
| 17:44 | <Philip`> | DOM Tree doesn't make any sense because it doesn't photosynthesise |
| 17:53 | <Hixie> | so i'm thinking <dialog> should also have a <form> feature: <form method=dialog> which causes form submission to just look for the nearest ancestor dialog and set its return value accordingly |
| 17:53 | <Hixie> | so you could do: <dialog> <form method=dialog> <button type=submit value=1>Ok</button> <button type=submit value=0>Cancel</button> </form> </dialog> |
| 17:54 | <Hixie> | and then: dialog.showModal(); dialog.onclose = function () { if (dialog.returnValue == '1') { ... } }; |
| 17:54 | <dglazkov> | Hixie: <dialog> sounds pretty cool |
| 17:54 | <annevk> | for some reason I read <details> and got confused |
| 17:54 | <Hixie> | (instead of having to hook each button up to the <dialog>, etc) |
| 17:54 | <Hixie> | this also gets you form validation for free |
| 17:54 | <Hixie> | so you can use <input required>, etc |
| 17:54 | <Hixie> | and it all magically works |
| 17:55 | <dglazkov> | so returnValue is what? |
| 17:55 | <Hixie> | the value of the button the user used to submit the form |
| 17:55 | <dglazkov> | what if I have a dialog to ask for a new label name? |
| 17:56 | <Hixie> | you can get the value from the form by just grabbing the form control and picking the input element and getting its value |
| 17:56 | <Hixie> | dialog.getElementsByTagName('form')[0].newLabelName.value |
| 17:57 | <Hixie> | (with <input name=newLabelName>) |
| 17:57 | <annevk> | will these dialogs be written in markup though? |
| 17:57 | <Hixie> | haven't really done the research yet but i'm guessing yes |
| 17:57 | <zewt> | is there a reason to do this in a surrounding dialog element, instead of just using events on the form? |
| 17:57 | <Hixie> | (still need to see if it's what people want by studying how it's done today) |
| 17:58 | <Hixie> | zewt: how would that look? |
| 17:58 | <annevk> | zewt, you need a container that will be the dialog |
| 17:58 | <zewt> | akin to onsubmit, i imagine |
| 17:59 | <Hixie> | how would you write the example above? |
| 18:00 | <zewt> | something like form.method = "none"; /* submitting triggers events but doesn't submit to the server */ form.onaftersubmit = function(e) { form.returnValue ... } |
| 18:01 | <Philip`> | Should OK/Cancel buttons get automatically hooked up to keys like Enter/Escape and other UI like 'X' buttons, rather than just being arbitrary submit buttons? |
| 18:01 | <Hixie> | zewt: how do you get the dialog to show up in this model? |
| 18:02 | <Hixie> | Philip`: ok/cancel are an antipattern in dialog design, i don't think we should be encouraging their use. I was just lazy in my example. |
| 18:02 | <zewt> | i don't know anything about <dialog>, i'm looking at it from the javascript-form perspective |
| 18:02 | <Hixie> | zewt: ah well if all you want is a form, you can already do that using action="javascript:..." |
| 18:02 | <zewt> | where it seems like you sort-of want f.onsubmit = function(e) { e.preventDefault(); }, but you don't want to actually stop the submission entirely--still go through validation and so on, just don't send it to the server |
| 18:02 | <TabAtkins_> | Not for much longer, if at all anymore. |
| 18:02 | <zewt> | ew |
| 18:02 | <Philip`> | Hixie: Keyboard shortcuts and default choices seem important regardless of what the buttons are labelled with |
| 18:03 | <Hixie> | Philip`: ah if you mean should it be possible to mark a button as the default button, that's already on the list of features for a future version |
| 18:04 | <zewt> | can you do form.action = function in JS? code in a javascript: url is evil |
| 18:05 | <nlogax> | not afaik. but why not add an event listener? |
| 18:05 | <zewt> | listener on what? |
| 18:05 | <Hixie> | zewt: why is it evil? |
| 18:06 | <zewt> | how is it not evil? heh |
| 18:06 | <Hixie> | what's the difference between onclick="foo()" and action="javascript:foo()" ?? |
| 18:06 | <Ms2ger> | That the latter is evil :) |
| 18:07 | <zewt> | i can say x.click = function() in JS; x.action = "foo()" in JS is nasty |
| 18:07 | <zewt> | onclick |
| 18:07 | <Hixie> | oh well if you're talking about scripted stuff sure |
| 18:07 | <Hixie> | i assumed you were talking about markup |
| 18:07 | <nlogax> | zewt: submit listener on the form |
| 18:07 | <zewt> | whether prefixed with javascript: or not (that just makes it worse) |
| 18:08 | <Philip`> | Scripts in attribute strings are effectively executed using eval, and eval is inherently evil |
| 18:08 | <zewt> | nlogax: being able to trigger validation without performing a server submit |
| 18:08 | <nlogax> | zewt: you can prevent the default action |
| 18:09 | <nlogax> | form.addEventListener("submit", function(e) { e.preventDefault(); do some stuff; }, false) |
| 18:10 | <zewt> | i assumed that would prevent form validation as well (havn't used form validation yet) |
| 18:11 | <nlogax> | i think an invalid form is not possible to submit anyway.. but only used it once and forgot |
| 18:11 | <nlogax> | >_> |
| 18:11 | nlogax | reads |
| 18:11 | <zewt> | too tired at the moment to think much harder about it |
| 18:11 | <zewt> | two hours of sleep is fun |
| 18:20 | <erlehmann> | i am of sleepy as well. |
| 18:28 | <annevk> | I wonder how we should organize the Nodes section |
| 18:28 | <annevk> | the current order makes little sense |
| 18:28 | <annevk> | maybe they should be in nodeType order |
| 18:29 | <annevk> | with the exception of comment |
| 18:29 | <annevk> | that should just come after Text and not ProcessingInstruction |
| 18:30 | <Ms2ger> | Tree order? Doc/PI/doctype/Element/CharData/Text/Comment/DocFrag |
| 18:31 | <annevk> | that seems kind of nice actually, again with Comment out of order |
| 18:32 | <Ms2ger> | I just want (CharData/Text/Comment) together |
| 18:36 | <annevk> | yeah |
| 19:32 | <AryehGregor> | So it looks like one of the two bugs I filed in IE Connect was silently fixed at some point. |
| 19:32 | <AryehGregor> | Encouraging. Maybe I'll file some more. |
| 19:33 | <zewt> | was it reflexively WONTFIX'd anyway |
| 19:33 | <zewt> | heh |
| 19:34 | <annevk> | god I wish Mozilla obsoleted Attr already |
| 19:35 | <annevk> | and other browsers too of course |
| 19:35 | <annevk> | but I mainly want to clean up the DOM spec :p |
| 19:35 | <Ms2ger> | We warn already! |
| 19:36 | <AryehGregor> | zewt, no, both of my bugs got quick form responses saying: Thank you for your feedback. |
| 19:36 | <AryehGregor> | We were able to reproduce the issue and are investigating it. |
| 19:36 | <AryehGregor> | Best regards, |
| 19:36 | <AryehGregor> | The Internet Explorer Team |
| 19:36 | <AryehGregor> | Which is actually impressive by itself. |
| 19:36 | <karlcow> | each time a Website is using it, make Firefox sends an email to the spec editor ;) |
| 19:37 | <zewt> | i'd say "buy a lottery ticket" if randomness worked that way |
| 19:37 | <Ms2ger> | karlcow, to the website author ;) |
| 19:37 | <AryehGregor> | Also, they kept them open after shipping IE9. One is still open, the other is fixed, and I confirmed that the fixed one is actually fixed in 10PP2. |
| 19:37 | <annevk> | D/DF/PI/DT/E/T/C is the new order |
| 19:37 | <AryehGregor> | So actually my only complaint is that I don't seem to get e-mail for status updates, and there's no explanation of when the fixed one was fixed. |
| 19:38 | <Ms2ger> | Weird place for DF |
| 19:38 | <annevk> | I also abstracted out the adopting stuff Ms2ger |
| 19:38 | <annevk> | it's close to Document |
| 19:38 | <karlcow> | Ms2ger, I really wish we had a simple way of having a feedback loop for people in charge of websites. It is hard to impossible to find the right persons, web agencies, departments. |
| 19:39 | <Ms2ger> | Same here |
| 19:39 | <zewt> | if only there was always actually someone in charge of websites :| |
| 19:39 | <Ms2ger> | annevk, great |
| 19:39 | <annevk> | i think the new adopt stuff is quite good yes :) |
| 19:40 | <annevk> | now I just need to solve xxxhierarchy |
| 19:40 | <annevk> | and see how the mutating algorithms overlap |
| 19:40 | <annevk> | so there's only a few places to patch eventually for mutation events |
| 19:41 | <wolfman2000> | afternoon |
| 19:42 | <Ms2ger> | Night |
| 19:42 | <annevk> | almost midday |
| 19:45 | <karlcow> | http://www.niso.org/topics/ccm/e-book_annotation/ |
| 19:45 | <karlcow> | Books in Browsers Meeting |
| 19:45 | <karlcow> | October 26, 2011 |
| 19:46 | <Ms2ger> | How is the hit-testing going? |
| 19:46 | <Ms2ger> | (Pushed) |
| 19:46 | <annevk> | tantek is finding out it is hard :) |
| 19:48 | <Ms2ger> | He's managing to make others write spec text, though |
| 19:49 | <annevk> | maybe he can make you do more than fix typos :p |
| 19:50 | <Ms2ger> | Noooo |
| 19:51 | <annevk> | tantek, btw, will you remove the pseudo-elements from CSS3 UI? |
| 19:52 | <tantek> | annevk: lol - what I was finding out is just how many *more* unprefixed CSS properties have been implemented. |
| 19:52 | <tantek> | (which may affect hit-testing yes) |
| 19:53 | <tantek> | regarding the pseudo-elements in CSS3-UI, I've already placed them all "at risk" |
| 19:56 | <Ms2ger> | <ChrisL> can we please drop the 'levels' stuff |
| 19:56 | <Ms2ger> | Hear, hear |
| 20:01 | <tantek> | and will be keeping ::value and ::choices per implementer interest/intent (Mozilla) - but at this point looking at dropping the ::repeat-* pseudo-elements. |
| 20:01 | <zewt> | gar |
| 20:02 | <zewt> | next thing browsers need: modal save-as prompts |
| 20:02 | <zewt> | which is ... hard :| |
| 20:03 | <wolfman2000> | Maybe look at jquery to see how they did their modal stuff? |
| 20:06 | <hober> | zewt & wolfman2000: please contribute what you find to http://wiki.whatwg.org/wiki/Dialogs |
| 20:06 | <annevk> | tantek, hmm, if they are going to be used for shadow DOM like stuff it might be better to wait for that |
| 20:08 | <tantek> | annevk - my understanding is that ::value and ::choices are simple enough that it will fairly easy to map them to shadow DOM like stuff when that is defined. |
| 20:08 | <tantek> | and if there is only one implementation of the pseudo-elements then they won't exit CR |
| 20:08 | <tantek> | so I'm ok with seeing if browser implement them or not and keeping/dropping accordingly. |
| 20:08 | <tantek> | *browserS |
| 20:10 | <annevk> | I think for shadow DOM though instead of having a bunch of pre-defined pseudo-elements we want something else |
| 20:10 | <annevk> | ::shadow(ident) |
| 20:10 | <annevk> | and in your shadow tree you have <div pseudo=test> which can then be matched from the outside using ::shadow(test) |
| 20:11 | <annevk> | dglazkov might know more |
| 20:11 | <annevk> | because otherwise you need to keep updating the selectors grammar and in general it would not be very extensible |
| 20:17 | <dglazkov> | annevk: I tried to convince dhyatt to do something like ::shadow(ident), but he insisted that we just use pseudo-elements. |
| 20:17 | <dglazkov> | annevk: and allow builders of shadow DOM to define them with "pseudo" attribute. |
| 20:18 | <annevk> | but that does not work |
| 20:18 | <annevk> | ::foobar { } is dropped from a style sheet |
| 20:19 | <annevk> | unrecognized pseudo-elements do not make it past parsing |
| 20:19 | <dglazkov> | annevk: not in WebKit |
| 20:19 | <annevk> | that's a CSS compliance issue then |
| 20:20 | <dglazkov> | annevk: right http://lists.w3.org/Archives/Public/www-style/2011Apr/0769.html |
| 20:20 | <dglazkov> | WebKit. we're awesome. |
| 20:21 | <annevk> | well that extension makes sense |
| 20:21 | <annevk> | but that is not about not dropping unrecognized pseudo-elements on the floor |
| 20:22 | <dglazkov> | how would you know if a pseudo-element is unrecognized? |
| 20:22 | <annevk> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cstyle%3E%3A%3Atesttest%2Cbody{background%3Ared}%3C%2Fstyle%3E |
| 20:23 | <annevk> | only red in webkit |
| 20:23 | <annevk> | violating forwards compatible parsing rules |
| 20:24 | <wolfman2000> | hober: I may have misunderstood your request. I'm looking at the slashdot example on the dialog wiki page, and that looks like jquery to me. |
| 20:24 | <annevk> | WebKit. we've awesomely undocumented extensions and do not push for them in standards bodies |
| 20:24 | <annevk> | ;) |
| 20:24 | <dglazkov> | ;) |
| 20:25 | <dglazkov> | maybe TabAtkins should do it |
| 20:25 | <dglazkov> | he's smart |
| 20:26 | <Ms2ger> | CSS3WEBKIT? |
| 20:29 | <tantek> | annevk - longer term it seems the ::shadow(ident) approach makes more sense. which is why I'm fairly conservative with adding new pseudo-elements. ::value and ::choices have specific uses / use-cases and implementer interest which is why I'm even considering them. |
| 20:37 | <gsnedders> | B2G — an entirely memory unsafe OS, on a limited memory platform? |
| 20:41 | <Ms2ger> | Limited memory and Gecko in one sentence? |
| 20:43 | <zewt> | "gecko causes me to have limited memory" |
| 20:45 | <gsnedders> | Ms2ger: Well, isn't that the implication of B2G? Or going down the Maemo/N900 route of needing swap space on microSD or the like? |
| 20:46 | <Ms2ger> | Dunno, I'm happy to have skipped that thread |
| 20:47 | <zewt> | swap on sd? sounds like a good way to have to replace an sdcard every couple months, heh |
| 21:06 | <AryehGregor> | How do you get raw HTML hosted at github, like es5.github.com? Does it require $$$? |
| 21:21 | <karlcow> | AryehGregor: http://pages.github.com/ if you like solutions which are not free, tied to a corporate for hosting ;) |
| 21:22 | <AryehGregor> | Yeah, so it's not free. Figures. |
| 21:31 | <Philip`> | Do any modern browsers not have document.images? |
| 21:32 | <Ms2ger> | Gecko does, that much my source tells me |
| 21:34 | <Philip`> | Hmm, looks like IE4+, NN3+, O3+ |
| 21:34 | <Philip`> | per http://blooberry.com/indexdot/html/topics/uastring-navobj.htm |
| 21:39 | <AryehGregor> | Okay, I'd say my editing spec is ready for implementer review. |
| 21:39 | AryehGregor | writes up posts |
| 22:23 | <AryehGregor> | http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-July/032630.html |
| 22:27 | <jamesr> | AryehGregor: tl;dr |
| 22:27 | <AryehGregor> | jamesr, :( |
| 22:27 | <jamesr> | AryehGregor: :D |
| 22:27 | <Hixie> | man, harsh |
| 22:29 | <jamesr> | is the intent that this spec be detailed enough to clean-room from the spec and be compatible with the web? |
| 22:29 | <AryehGregor> | jamesr, yes. |
| 22:29 | <jamesr> | i'm wondering if anyone would try to do an html5-parser style rewrite+ditch |
| 22:29 | <AryehGregor> | I'm pretty sure that's the only feasible strategy here. |
| 22:29 | <AryehGregor> | I don't know if it's quite ready for that, though. |
| 22:29 | <jamesr> | for interop, yeah |
| 22:30 | <AryehGregor> | It still has some known issues, and I'm sure there are loads of problems I didn't think of at all. |
| 22:30 | <karlcow> | sometimes I wonder if specs should not just been small index card. linked together |
| 22:31 | <AryehGregor> | One problem with this is that interop is so bad right now that sites that rely on execCommand all use massive browser sniffing. |
| 22:31 | <AryehGregor> | So any convergence will have to break sites in at least one browser, probably. |
| 22:31 | <AryehGregor> | But that's not avoidable. |
| 22:31 | <jamesr> | also a certain amount of content is inherently engine-specific |
| 22:31 | <AryehGregor> | Yes, we all know WebKit has that problem. |
| 22:31 | <AryehGregor> | Well, and IE, but they just gave up and started keeping around the old engines, so it's not an issue for them. |
| 22:31 | <jamesr> | it's a significant issue in WebKit, but probably true to some degree for everyone |
| 22:32 | <jamesr> | i guess apple could keep another version of WebKit.framework around for Mail.app :/ |
| 22:32 | <AryehGregor> | The algorithms should be compatible enough in most cases, because usually sites aren't going to depend on the exact DOM produced. |
| 22:32 | <AryehGregor> | Or so one hopes. |
| 22:33 | <AryehGregor> | Unlike with the HTML parser. |
| 22:33 | <AryehGregor> | But there will definitely be some migration pain here. |
| 22:33 | <AryehGregor> | Still, no way around it. |
| 22:35 | <zewt> | well, you *could* avoid backwards-compatibility, in principle, by speccing a new function ("newExecCommand"), everyone implements that, then declare execComment to be inherently browser-specific for backwards-compat only, as if it was a prefixed vendor extension |
| 22:35 | <zewt> | not very pretty, of course |
| 22:35 | <jamesr> | if you're going to do that, might as well go ahead and design something that makes more sense |
| 22:35 | <AryehGregor> | WebKit can do that if they want to preserve compat with WebKit-specific content, but it's not reasonable for the web in general. |
| 22:36 | <AryehGregor> | We need to define something for execCommand() that's basically web-compatible. |
| 22:36 | <zewt> | jamesr: well, that way means that the new API gives a pretty simple migration for existing code |
| 22:36 | <jamesr> | that's basically saying "let's design a new editing API", which is different from standardizing execCommand() |
| 22:36 | <zewt> | whereas a new sparkly API may not |
| 22:36 | <AryehGregor> | jamesr, well, a redesign from scratch risks introducing unforeseen design flaws, and it would be harder for authors to port their sites. |
| 22:36 | <AryehGregor> | But yeah, this isn't an option, we're standardizing what's out there. |
| 22:36 | <zewt> | also a much bigger investment implementation- and design-side |
| 22:36 | <AryehGregor> | Most users probably won't break. |
| 22:36 | <jamesr> | fingers crossed! |
| 22:36 | <AryehGregor> | I mean, most sites that use it. |
| 22:37 | <zewt> | breaking users sounds like a fascinating side-effect |
| 22:37 | <zewt> | *crunch* |
| 22:37 | <AryehGregor> | If they do, we'll figure out what to do at the time. I'm happy to change the spec to be more compatible if people identify specific sites that break. |
| 22:55 | <AryehGregor> | Hixie, was the WebSockets protocol ever part of the HTML5 draft at the W3C, before it moved to the IETF? |
| 22:56 | <annevk> | http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%3Cscript%3Evar%20df%20%3D%20document.createDocumentFragment()%3B%20df.appendChild(document.createElement(%22x%22))%3Bdocument.replaceChild(df%2Cdocument.documentElement)%3C%2Fscript%3E only works in Firefox |
| 22:56 | <annevk> | hmm |
| 22:57 | <franksalim> | AryehGregor: a predecessor protocol was as part of TCPConnection |
| 22:57 | <annevk> | guess expanding DocumentFragment nodes for insertion and append operations isn't really well supported |
| 22:58 | <AryehGregor> | Opera 11.50 is weird. |
| 22:58 | <Hixie> | AryehGregor: no idea off-hand |
| 22:59 | <AryehGregor> | It replaces the element successfully, but it sticks in an empty <head> and <body>. |
| 22:59 | <AryehGregor> | Hixie, k. |
| 23:00 | <annevk> | AryehGregor, http://www.w3.org/TR/2009/WD-html5-20090212/comms.html#network |
| 23:01 | <AryehGregor> | annevk, thanks. |
| 23:02 | <annevk> | I guess I will go with what Firefox did |
| 23:03 | <annevk> | DocumentFragment, bah |
| 23:03 | <zewt> | heh DRM talk on the list--yeah right |
| 23:05 | <franksalim> | AryehGregor: I just realized you said "at the W3C." please disregard my last message |
| 23:19 | <Hixie> | ok i just replied to the oldest e-mail in my folders, from 2007 |
| 23:20 | <TabAtkins_> | Hah, awesome. |
| 23:20 | <Hixie> | there's some 2008 e-mail about contenteditable that i'll look at eventually but right now it's not included in my counts because aryeh's working on editing |
| 23:25 | <Hixie> | is anyone working on speccing the fullscreen api? |
| 23:32 | <AryehGregor> | Is there a Bugzilla I could use for the editing API stuff? If I start getting nontrivial amounts of feedback, it would be a lot more convenient than e-mail. |
| 23:32 | <annevk> | Hixie, I planned on doing it |
| 23:33 | <annevk> | but then didn't |
| 23:33 | <Hixie> | AryehGregor: prod mikesmith to get you a component in the bugzilla |
| 23:33 | <Hixie> | annevk: ah, awesome |
| 23:33 | <annevk> | heycam was next in line |
| 23:33 | <annevk> | well not awesome |
| 23:33 | <Hixie> | oh |
| 23:33 | <annevk> | so far nothing happened :) |
| 23:33 | <AryehGregor> | Nobody will mind that the spec isn't at the W3C? |
| 23:33 | <Hixie> | i see |
| 23:33 | <Hixie> | AryehGregor: not if you don't make a fuss about it |
| 23:33 | <Hixie> | :-) |
| 23:33 | <AryehGregor> | The problem is if someone else later does after I started relying on it. |
| 23:33 | <annevk> | has not happened so far |
| 23:34 | <annevk> | e.g. with DOM Range |
| 23:34 | <Hixie> | AryehGregor: the W3C has kindly agreed to allow us to use the bugzilla for non-w3c specs |
| 23:34 | <AryehGregor> | Oh, okay then. |
| 23:34 | <AryehGregor> | I didn't realize DOM Range had a component. |
| 23:36 | <Hixie> | annevk: i'm trying to work out where to send all this feedback |
| 23:37 | <annevk> | attach it to a bug report? |
| 23:37 | <Hixie> | there's like 50 e-mails |
| 23:37 | <annevk> | and assign when it's clear there's an editor or something |
| 23:37 | <annevk> | email it to www-archive? |
| 23:37 | <annevk> | and add it to Specifications TODO |
| 23:37 | <annevk> | on the wiki |
| 23:38 | <Hixie> | i'll just move it to a bucket that doesn't count against my numbers i guess |
| 23:38 | <Hixie> | and add a note on the wiki |
| 23:38 | <annevk> | or you know, just spec it :) |
| 23:38 | <Hixie> | not gonna happen |
| 23:38 | <Hixie> | :-P |
| 23:39 | <Hixie> | annevk: hey do you want my range and traversal buckets? |
| 23:41 | <annevk> | traversal yes |
| 23:41 | <annevk> | range not yet (maybe AryehGregor wants that for now) |
| 23:41 | <annevk> | traversal is now in DOM Core |
| 23:42 | <annevk> | and I suspect Range will one day be too |
| 23:42 | <AryehGregor> | I could take the Range buckets, but I don't know how I'd actually respond to them in the format you're sending me. |
| 23:42 | <annevk> | you just reply to the individuals |
| 23:42 | <AryehGregor> | So just lots and lots and lots of copy-paste? |
| 23:43 | <annevk> | hixie could resend each of them |
| 23:43 | <annevk> | i suppose |
| 23:43 | <heycam> | annevk, cpearce is implementing it for us, maybe he would like to do speccing work too? :) |
| 23:44 | <cpearce> | hmmm? I working on what? |
| 23:44 | <heycam> | full screen |
| 23:44 | <cpearce> | ah yes... |
| 23:44 | <cpearce> | I've basically implemented https://wiki.mozilla.org/index.php?title=Gecko:FullScreenAPI |
| 23:44 | <Hixie> | AryehGregor: i can also just bounce all the mails to you as separate e-mails |
| 23:44 | <cpearce> | without all the security checks yet ;) |
| 23:45 | <AryehGregor> | Hixie, well, if you want me to spend time systematically responding to all the editing and range stuff, I don't mind. |
| 23:45 | <Hixie> | annevk: looks like hte only thing i have about traversal is about what happens if a filter moves its iterator or treewalker |
| 23:45 | <AryehGregor> | Probably would be easier for me if you forwarded them all to me in some format where I could reply all to get the individual plus the list. |
| 23:46 | <Hixie> | annevk: you defined that? |
| 23:46 | <Hixie> | AryehGregor: i'm more interested in making sure the points are addressed than that they get replies at this point |
| 23:46 | <Hixie> | AryehGregor: i can send the replies later when i do the review work |
| 23:47 | <Hixie> | AryehGregor: as i mentioned in /msg, it would help me learn the spec :-) |
| 23:47 | <AryehGregor> | k. |
| 23:47 | <AryehGregor> | (got to go now) |
| 23:47 | <Hixie> | later |
| 23:48 | <annevk> | Hixie, yes |
| 23:48 | <annevk> | Hixie, it throws |
| 23:48 | <Hixie> | hah, i chave a CSS 2.1 bucket with over 100 e-mails in it |
| 23:48 | <Hixie> | annevk: ok, i'll delete this mail then |
| 23:49 | <Hixie> | how about dom events, do you want a multipart/digest of those? |
| 23:49 | <Hixie> | got some mail from 2004 in this bucket |
| 23:49 | <Hixie> | and a whatwg mail from 2005 |
| 23:50 | <annevk> | Hixie, I guess |
| 23:50 | <annevk> | Hixie, kind of depends if they are about the core part or UI events |
| 23:51 | <Hixie> | didn't check |
| 23:51 | <Hixie> | sent you a pile of feedback |
| 23:51 | <Hixie> | see comment in the e-mail |
| 23:51 | <Hixie> | i have a folder here named "cssom--anne-says-eta-2015", wonder what that's about |
| 23:52 | <annevk> | suspect new features or something |
| 23:53 | <Hixie> | TabAtkins_: do you recall if you've gone through all that feedback i sent you about css lists? (i have a bucket here that says i should delete it once you're confident you've dealt with it) |
| 23:53 | Hixie | deletes two e-mails from hyatt dated 2003 about the flexbox model |
| 23:54 | <Hixie> | ok seriously, i'm deleting this css 2.1 feedback. i hope it all got dealt with. |
| 23:54 | <annevk> | should maybe email to elika |
| 23:55 | <Hixie> | it's all ancient stuff |
| 23:56 | <annevk> | k |
| 23:56 | <Hixie> | oh heck, a websqldb folder |
| 23:56 | Hixie | deletes |
| 23:57 | <Hixie> | ok that's some good cleanup |