| 01:07 | <MikeSmith> | JonathanNeal: I e-mailed the mailing list to invite some feedback but I don't plan on mailing anybody else |
| 01:07 | <MikeSmith> | who do you think we should e-mail> |
| 01:07 | <MikeSmith> | ? |
| 01:07 | <MikeSmith> | ? |
| 01:12 | <JonathanNeal> | I dunno. I tweeted it for some feedback. |
| 01:16 | <dekiss> | rillian, sry now I saw |
| 01:16 | <dekiss> | rillian, who edit html spec? |
| 01:16 | <dekiss> | who is authorized? |
| 01:29 | <MikeSmith> | https://twitter.com/TVRaman/status/342047516025552896 |
| 01:30 | <MikeSmith> | Xforms in the air today I guess |
| 01:30 | <MikeSmith> | even got Raman tweeting |
| 01:30 | <MikeSmith> | I didn't even know he was twitter |
| 01:34 | <dekiss> | MikeSmith, you guys get feedback in emails and here and edit hmtl specification based on the feedback? |
| 01:38 | <MikeSmith> | dekiss: Hixie is the sole editor of the whatwg HTML spec. The W3C publishes a version of the spec also, based mostly only the whatwg spec but with some additions and changes. There are several editors of the W3C HTML spec but probably the most active one is SteveF, who's on this channel often and who focuses on accessibility features. |
| 01:41 | <dekiss> | nice |
| 01:41 | <dekiss> | I will look for him to ask him if accessibility technology devices can interpret dom and javascript |
| 01:43 | <MikeSmith> | dekiss: the answer is that the DOM and the results of JS operations on the DOM do get exposed to accessibility software |
| 01:43 | <MikeSmith> | though in a somewhat different form |
| 01:44 | <dekiss> | MikeSmith, thanks I will download and/or buy some devices to check it myself |
| 01:58 | <JonathanNeal> | Did you guys change the validator to stop allowing <span> from wrapping block content? |
| 01:58 | <MikeSmith> | JonathanNeal: it doesn't allow it now |
| 01:59 | <MikeSmith> | there's been no change |
| 01:59 | <MikeSmith> | that causes an error to be reported |
| 02:35 | <tantek> | JonathanNeal - see, I was pretty sure you couldn't <span><blockquote></blockquote></span> |
| 05:54 | <MikeSmith> | Hixie: are you referencing level 4 of Selectors in HTML because something in the spec specifically requires something in level 4, or rather just because it's the latest? |
| 06:20 | <Hixie_> | MikeSmith: i believe i'm not referencing the editor's draft, actually |
| 06:20 | <Hixie_> | er |
| 06:20 | <Hixie_> | now |
| 06:20 | <Hixie_> | not not |
| 06:21 | <Hixie_> | yeah, i'm just referencing the editor's draft |
| 06:21 | <Hixie_> | (closest they have to a "living standard") |
| 06:32 | <MikeSmith> | Hixie_: ok |
| 06:47 | <Ms2ger> | OH: "Good ideas never die ... XForms..." |
| 07:08 | <jgraham> | Ms2ger: "proves that bad ideas never die, either"? |
| 07:17 | <Ms2ger> | <SimonSapin> http://w3cmemes.tumblr.com/post/34634329920/csswg-resolves-to-use-less-magic |
| 07:17 | <Ms2ger> | <fantasai> dbaron: Could introduce some magic |
| 07:59 | <dbaron> | it's really not *that* magical |
| 08:11 | <jgraham> | tobie: Are you going to rename the ttwf-docs repo? |
| 08:11 | <tobie> | yeah, I absolutely should. |
| 08:12 | <tobie> | also the docs suffix is idiotic |
| 08:12 | <tobie> | as we'll have more in there than just docs |
| 08:12 | <tobie> | including the main page, etc. |
| 08:12 | <tobie> | … the events |
| 08:13 | <tobie> | testtwf-website? |
| 08:14 | <jgraham> | WFM |
| 08:14 | <tobie> | deal |
| 09:11 | <MikeSmith> | tobie: in general I take the "docs" abbreviation to just mean (Web) "documents" and not necessarily documentation |
| 09:11 | <MikeSmith> | e.g., "/www/docs" and such |
| 09:11 | <tobie> | oh, you're old school, man! |
| 09:11 | <MikeSmith> | heh |
| 09:11 | <MikeSmith> | I am that, I guess |
| 09:12 | <MikeSmith> | anyway, -website is definitely clearer |
| 09:16 | <darobin> | bah |
| 09:16 | <darobin> | it should be testtwf-var-www-sites |
| 09:17 | <MikeSmith> | heh |
| 09:18 | <jgraham> | Hmm, we would attract more users if we went all OSX. Library-WebServer-Documents-TestTWF ftw |
| 09:37 | <MikeSmith> | good brainstorming |
| 10:04 | <jgraham> | lol at "let's proceed only on es-discuss. This is […] not a browser issue" |
| 10:05 | <jgraham> | In other news, skepticism remains about how much TC39 really want to work with the rest of the community. |
| 10:07 | <darobin> | ouch |
| 10:07 | <Ms2ger> | :/ |
| 10:35 | <annevk> | I don't know why he insists on trolling all the time |
| 10:35 | <annevk> | it's annoying |
| 10:43 | <Ms2ger> | Habit? |
| 10:44 | <annevk> | You would know |
| 10:50 | <Ms2ger> | Indeed so |
| 10:58 | <hsivonen> | annevk: this text misunderstands the meaning of CORS-same-origin, right: https://dvcs.w3.org/hg/html-media/rev/69dbfb8baca8#l1.18 ? |
| 10:59 | <annevk> | hsivonen: that reads very weird |
| 10:59 | <hsivonen> | annevk: that is, the CORS-same-origin concept covers the case where CORS has been used, so the "or use the crossorigin..." bit is confused |
| 11:00 | <annevk> | hsivonen: yes |
| 11:00 | <annevk> | also, xsl:template o_O |
| 11:10 | <hsivonen> | annevk: my bank exposed an expired certificate in production this morning and my reaction was "also, ISO-8859-15 o_O" |
| 11:11 | <annevk> | need a bigger O |
| 11:11 | <Ms2ger> | I wonder if cobol outputs ISO-8859-15 |
| 11:19 | <hsivonen> | Ms2ger: ISO-8859-1 is way too new for Cobol |
| 11:19 | <hsivonen> | argh |
| 11:19 | <hsivonen> | -15 |
| 13:09 | <annevk> | hsivonen: http://i.imgur.com/4J7Il0m.jpg is beautiful |
| 13:13 | <zcorpan> | annevk: btw philipj suggested maybe Fetch should cover the fetching story that apply to media elements |
| 13:14 | <annevk> | I know there's a sad story for <img> elements. There's one for media elements too? |
| 13:14 | <zcorpan> | what's about <img<? |
| 13:14 | <annevk> | I should write these stories down somewhere so I don't forget about them. |
| 13:15 | <zcorpan> | well media elements support http range requests |
| 13:15 | <annevk> | zcorpan: per Document a URL is only fetched once and then simply retrieved from cache, irrespective of HTTP cache headers on the fetch. |
| 13:15 | <annevk> | I'll be back in 45min, need to ensure I have dry clothes before traveling Friday :) |
| 13:16 | <Ms2ger> | Eh, dry clothes are overrated |
| 13:16 | <zcorpan> | loading an .ogg resource means doing a range request from 0 to infinity, then if the server supports range requests and the ogg resource doesn't have an index, you seek to the end (i.e. abort the first request and do a new request) of the file to find out the duration, then you do a third request from where you left of from the first request |
| 13:17 | <zcorpan> | and there's a different cache for media resources |
| 13:18 | <zcorpan> | we reverse engineered gecko in this area :-) |
| 13:19 | <zcorpan> | also, there are unsubmitted tests in this area :-/ |
| 13:21 | <jgraham> | zcorpan: Yeah, I noticed that the other day when Ms2ger was asking |
| 13:22 | <jgraham> | Making Gecko run tests on their own reverse-engineered behaviour should be reason enough to release them ;) |
| 13:26 | <zcorpan> | the media cache tests are ugly php hacks |
| 13:26 | <zcorpan> | with state management being text files on the server, iirc |
| 13:26 | <jgraham> | Nice |
| 13:27 | <zewt_> | zcorpan: seems really wasteful to send a request expecting to abort it, since the server will probably push out a ton of data that would get discarded |
| 13:27 | <zewt> | surprised it doesn't just leave the first request running, and run a second request at the end in parallel |
| 13:27 | <zcorpan> | zewt: yeah well |
| 13:28 | <zewt> | the server probably can't tell the difference (it might not even be able to detect the abort until after the second request starts anyway), and it'd be a lot more efficient |
| 13:28 | <zcorpan> | yeah i've pondered about that as a way to do it as well |
| 13:28 | <zcorpan> | but it was hard to argue that we should spend time implementing such a tweak when there were lots of more important things to implement |
| 13:29 | <jgraham> | I presume a certain amount of real world experience went into this design |
| 13:29 | <jgraham> | Although I might be wrong ofc |
| 13:29 | <zewt> | i'm wary about making that assumption these days :) |
| 13:30 | <zcorpan> | i don't know if the parallel strategy was considered before things got implemented in gecko and presto |
| 13:31 | <jgraham> | Well it seems kind of obvious |
| 13:31 | <jgraham> | So I favour the explaination that it was considered and rejected over the explaination that no one even thought of it |
| 13:32 | <zcorpan> | i thought of it, but not until after we had implemented the aborting strategy |
| 13:33 | <zcorpan> | maybe the gecko people thought of it too and rejected it because it wouldn't work with some proxies or whatever |
| 13:33 | <zewt> | also means that if the server doesn't support range, you get fewer round-trips (since the main request doesn't have to be a Range and you don't have to redo it if it doesn't work), not that broken servers is a big optimization point |
| 13:33 | <zewt> | (also are) |
| 13:34 | <zewt> | though I guess you want to know that (in the "don't need to read from the end of the file" case) anyway, to know whether to enable seeking |
| 13:34 | <zcorpan> | zewt: if the server doesn't support range, the first request is carried on as if it wasn't a range request |
| 13:38 | <zewt> | though I guess you want to know that (in the "don't need to read from the end of the file" case) anyway, to know whether to enable seeking |
| 13:38 | <zcorpan> | zewt: if the server doesn't support range, the first request is carried on as if it wasn't a range request |
| 13:40 | <zcorpan> | now i don't follow :-) |
| 14:07 | <zewt> | ie10 still doesn't put spaces between console.log parameters? :| |
| 14:09 | <annevk5> | jgraham: I'd favour asking |
| 14:11 | <annevk5> | jgraham: I'd favour asking |
| 14:12 | <zewt> | ie10 still doesn't put spaces between console.log parameters? :| |
| 14:14 | <jgraham> | annevk: Yes, of course, I wouldn't suggest we blindly assume everything must have been done for a good reason. But I also wouldn't go in with the attitude that things that look suboptimal don't have any reasoning behind them. |
| 14:19 | <GPHemsley> | annevk: So... when do we start on that common definitions spec? |
| 14:21 | <annevk> | GPHemsley: do you have spare time? |
| 14:21 | <GPHemsley> | ain't that a loaded question |
| 14:21 | GPHemsley | really wishes he got paid for his spare time |
| 14:21 | <annevk> | heh |
| 14:22 | <Ms2ger> | Too much, clearly ;) |
| 14:22 | <jgraham> | You get paid for it in time |
| 14:23 | <jgraham> | Which is, I have been led to believe, money |
| 14:23 | <GPHemsley> | aha |
| 14:27 | <annevk> | heh |
| 14:31 | <annevk> | GPHemsley: I'm not sure we're quite there yet. Might need some more incremental evolution first. |
| 14:31 | <GPHemsley> | incremental evolution where? because we may start to have divergent definitions |
| 14:33 | <jgraham> | Well talking to each other helps with that :) |
| 14:33 | <GPHemsley> | jgraham: I'm probably more worried about the cases where we don't even realize we're using/defining the same terms. |
| 14:33 | <jgraham> | At some level you always have people not specs |
| 14:34 | <jgraham> | Well if people aren't reading each other's specs, we have a bigger problem |
| 14:36 | <GPHemsley> | Why is that? There are plenty of specs (that annevk writes) that have nothing to do with what I'm doing. |
| 14:37 | <GPHemsley> | Ms2ger: Where in the code will I need to look to fix this? https://bitbucket.org/ms2ger/anolis/issue/8/should-override |
| 14:37 | <annevk> | GPHemsley: I think as a specification editor it's part of your job to be familiar with a large set of specifications. That's the only way you avoid needlessly introducing new concepts and terminology into the world. |
| 14:37 | <jgraham> | GPHemsley: I didn't say that everyone had to read everyone else's specs. But if you are writing a spec and it isn't being read by anyone that is writing/reading any other specs, that's not good |
| 14:37 | <jgraham> | Also, as annevk says, the reverse is true |
| 14:37 | <annevk> | GPHemsley: It'll also help understand where we might need to abstract or share concepts. |
| 14:38 | <Ms2ger> | GPHemsley, either xref.py or xspecxref.py in anolislib/processes |
| 14:39 | <jgraham> | tobie: Any chance of giving me whatever the permissions are on testtwf-website so that I can add hooks? (admin?) |
| 14:40 | <GPHemsley> | annevk: By that logic, then, you should already be familiar with all the stuff I'm doing in mimesniff, right? |
| 14:40 | <GPHemsley> | Ms2ger: Oh, and I heard there were tests I can run? |
| 14:41 | <Ms2ger> | Yeah |
| 14:41 | <annevk> | GPHemsley: I don't think that follows directly from what I said and I haven't checked mimesniff lately |
| 14:42 | <Ms2ger> | GPHemsley, python runtests.py in the top dir |
| 14:42 | <GPHemsley> | Ms2ger: Ah, k, thanks |
| 14:42 | <Ms2ger> | GPHemsley, adding a test for your case when you fix it is appreciated ;) |
| 14:43 | <GPHemsley> | k |
| 14:50 | <GPHemsley> | argh, I forget how hg works |
| 14:56 | <tantek> | GPHemsley - that happens to me all the time. I forget how (insert command line tool here) works. |
| 14:56 | <GPHemsley> | heh |
| 14:56 | <jgraham> | Well hg in particular is bad |
| 14:56 | <GPHemsley> | well this is specifically because I've been spending so much time with git lately |
| 14:57 | <tantek> | So when learning any new one, I end up making "xyz for dummies" wiki pages for each such command line tool, because I can predict fairly accurately that my future self will be a dummy with regards to said xyz command line tool. |
| 14:58 | <tantek> | e.g. for hg, I didn't make this one, but I've contributed to it: http://wiki.csswg.org/tools/hg |
| 14:59 | <tantek> | you may find it of some use, and feel free to add any problems / questions you encounter |
| 15:02 | <Ms2ger> | jgraham, it's much better than git, fortunately |
| 15:06 | <jgraham> | Yes, because applications where the first step in using them is "fiddle about with a configureation file to enable essential features" are so easy to use |
| 15:08 | <Ms2ger> | jgraham, "I forgot how to set it up" is a lot less of a problem than "I forgot how to use it" |
| 15:10 | <jgraham> | I rarely know how to use things that I have to Google to even set up correctly. |
| 15:12 | <tantek> | jgraham - LOL: "fiddle about with a configureation file to enable essential features" are so easy to use |
| 15:13 | <tantek> | yeah, that. |
| 15:16 | <jgraham> | Although it does look like if you have new enough mercurial, you get histedit with only a config option and not a config option + downloading a random script from the internet |
| 15:16 | <jgraham> | So I guess that's progress |
| 15:17 | <GPHemsley> | Ms2ger: Are the tests themselves documented? Because I've got one failing without telling me why or what it's for. |
| 15:17 | <jgraham> | Still would be nice if someone would go back in time and convinve the hg people that cheap, temporary, local branches are an essential feature |
| 15:17 | <jgraham> | Unfortunately, they don't believe in editing history\ |
| 15:18 | <Ms2ger> | GPHemsley, which one fails? They all pass for me |
| 15:18 | <GPHemsley> | toc-basic.src.html |
| 15:18 | <GPHemsley> | apparently x != y |
| 15:18 | <GPHemsley> | but the difference is subtle and hard to see |
| 15:19 | <GPHemsley> | id=baz? vs id=baz |
| 15:19 | <Ms2ger> | Interesting |
| 15:20 | <Ms2ger> | Ignore it for now and/or file a bug, I guess |
| 15:22 | <GPHemsley> | Ms2ger: How is it that you're not seeing it? |
| 15:22 | <GPHemsley> | (Maybe a different version of html5lib?) |
| 15:22 | <Ms2ger> | Yeah, that's the most likely |
| 15:26 | <jgraham> | 0.95 vs 1.0b? |
| 15:27 | <jgraham> | Would be interested in knowing if it's that |
| 15:27 | <Ms2ger> | Doesn't seem to make a difference |
| 15:28 | <GPHemsley> | Ms2ger: Is there a fake xref file I can use? |
| 15:29 | <Ms2ger> | GPHemsley, I don't think so |
| 15:29 | <Ms2ger> | You'll probably need an .options file too |
| 15:32 | <GPHemsley> | Ms2ger: How do I add the xspecxref process? |
| 15:32 | <GPHemsley> | (to the options) |
| 15:32 | Ms2ger | reads some code |
| 15:32 | <GPHemsley> | heh |
| 15:33 | <Ms2ger> | { 'processes': 'xspecxref' } |
| 15:33 | <GPHemsley> | "TypeError: buildReferences() takes at least 3 arguments (2 given)" |
| 15:33 | <Ms2ger> | Hrm |
| 15:34 | <Ms2ger> | Or ['xspecxref'] |
| 15:34 | <Ms2ger> | Yeah, needs to be an array |
| 15:34 | <GPHemsley> | yeah, right, already did that :) |
| 15:34 | <GPHemsley> | the issue may be with not having an xref file |
| 15:35 | <Ms2ger> | You may need to point at it... |
| 15:36 | <Ms2ger> | 'xref': 'data' or whatever you called the dir |
| 15:51 | <GPHemsley> | Ms2ger: https://bitbucket.org/ms2ger/anolis/pull-request/8/fix-8-should-override/diff |
| 15:51 | <Ms2ger> | Thanks, going to look in a bit |
| 16:38 | <jgraham> | odinho: I think I suggested the shutdown. I'm only still there to turn out the lights :) |
| 16:42 | <nimbu> | jgraham: ARE YOU IN OSLO |
| 16:43 | Ms2ger | covers his ears |
| 16:50 | <jgraham> | nimbu: NO. YOU KNOW THAT THE INTERNET LETS YOU TALK TO PEOPLE A LONG WAY AWAY WITHOUT SHOUTING? |
| 16:50 | <jgraham> | THATS WHY IT IS GOOD |
| 16:51 | <jgraham> | So we can probably talk at a normal volume |
| 17:07 | <annevk> | BUT THE TUBES |
| 17:08 | <miketaylr> | have to shout over the noise of splits |
| 17:21 | <rillian> | miketaylr: when you say that, I think you don't appreciate the elegance of minimal spanning trees |
| 17:22 | <miketaylr> | :) |
| 17:22 | Ms2ger | throws a brick at rillian |
| 17:23 | Ms2ger | thinks he's done having classes about MSTs now |
| 17:44 | <JonathanNeal> | hello |
| 17:57 | <GPHemsley> | Feedback welcome: http://wiki.whatwg.org/wiki/Contexts |
| 17:57 | <GPHemsley> | especially from Hixie_ (HTML) and annevk (Fetch) ^^ |
| 17:58 | <GPHemsley> | and any CSS folks who care to weigh in (TabAtkins, SimonSapin, etc.) |
| 17:58 | <annevk> | GPHemsley: for bonus points, plot that against CSP fetch types |
| 17:58 | <annevk> | GPHemsley: CSS has these img-src, media-src, etc. thingies we need to integrate into the rest of the stack somehow |
| 17:59 | <annevk> | not CSS, CSP |
| 17:59 | <annevk> | grmbl |
| 17:59 | <GPHemsley> | ah, k |
| 17:59 | <GPHemsley> | do you have a link handy/ |
| 17:59 | <GPHemsley> | ? |
| 17:59 | <annevk> | https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-1.0-specification.html |
| 17:59 | <annevk> | I think there might be a 1.1 too somewhere |
| 17:59 | <annevk> | it's not very well organized over on w3.org :/ |
| 17:59 | <GPHemsley> | MDN says https://dvcs.w3.org/hg/content-security-policy/raw-file/tip/csp-specification.dev.html |
| 18:00 | <tantek> | annevk, perhaps it could be better organized on w3.org/wiki ;) |
| 18:00 | <annevk> | GPHemsley: nice |
| 18:02 | <GPHemsley> | incidentally, I think there may also need to be an 'embed' or 'plugin' context, but I haven't quite figured that out yet |
| 18:06 | <annevk> | yeah, HTML defines a bunch of that itself |
| 18:06 | <annevk> | getting these things extracted is good work |
| 18:08 | <GPHemsley> | HTML currently only uses "browsing context" by name |
| 18:08 | <GPHemsley> | the rest are currently implicit |
| 18:08 | <GPHemsley> | the rest are currently implicit |
| 18:08 | <GPHemsley> | but I needed to figure them out so that I could have separate sniffing algorithms for each |
| 18:18 | <matjas> | annevk: any idea why i can’t seem to ssh into html5.org anymore? |
| 18:18 | <matjas> | getting “Connection to html5.org closed by remote host. Connection to html5.org closed.” |
| 18:18 | <GPHemsley> | annevk: OK, updated with CSP directives and 'plugin' context type |
| 18:19 | <GPHemsley> | oh, hmm, maybe I should move that column |
| 18:23 | <rillian> | Ms2ger: I'm actually a little surprised no one's tried to fix the MSP thing. It's not like the network doesn't have to run the same daemon on all servers, so it should be easy to extend the protocol on that side to do multiple routing and de-dup |
| 18:24 | <Ms2ger> | ? |
| 18:26 | <GPHemsley> | Updated: http://wiki.whatwg.org/wiki/Contexts |
| 18:26 | <GPHemsley> | (Help removing questions marks appreciated.) |
| 18:29 | <rillian> | Ms2ger: MST, not MSP. It's going to be one of those typo days |
| 18:29 | rillian | considers tea |
| 18:30 | <Ms2ger> | Michigan State Police? |
| 18:30 | <Ms2ger> | Ministerio de Salud P�blica? |
| 18:30 | <GPHemsley> | how are those different? |
| 18:30 | <Ms2ger> | Measurements of Student Progress? |
| 18:30 | <GPHemsley> | ^_^ |
| 18:31 | Ms2ger | wonders if there's any website with reasonable UX in English that covers most European rail |
| 18:35 | <jgraham> | I thought everyone used the german rail website for tat |
| 18:35 | <jgraham> | *that |
| 18:36 | <jgraham> | But I don't know about "reasonable UX" |
| 18:37 | <jgraham> | Although if search is anything to go by, my information might be outdated |
| 18:38 | <Domenic_> | hmm this is getting linked to from a popular-this-week stackoverflow answer; someone (annevk?) might want to update it... https://developer.mozilla.org/en-US/docs/DOM_Levels |
| 18:39 | <rillian> | Ms2ger: Minimal Spanning Tree. I was referring to your comments of an hour past |
| 18:39 | <jgraham> | Domenic_: Which SO? Or don't you know? |
| 18:41 | <Domenic_> | jgraham: I got it in my weekly Programmers newsletter. http://programmers.stackexchange.com/questions/200247/a-few-clarifications-about-the-dom?newsletter=1&nlcode=31316|4c54 |
| 18:42 | <annevk> | Domenic_: heh, that seems quite out of date |
| 18:42 | <Ms2ger> | jgraham, yeah, that does look a lot better than what I ended up with before, thanks |
| 18:42 | <annevk> | matjas: no, email me? |
| 18:42 | <annevk> | matjas: can sort out tomorrow hopefully |
| 18:44 | <jgraham> | Hmm, someone with a SO account might like to provide a better answer |
| 18:45 | <Ms2ger> | (It's Dutch translation doesn't appear to be entirely accurate, but hey, there is one) |
| 19:23 | <Ms2ger> | Heh, CSS Eleven |
| 19:23 | <nimbu> | wat |
| 19:25 | <Ms2ger> | http://my.opera.com/dstorey/blog/css-eleven seems to be a contemporary blog post about them |
| 19:28 | <miketaylr> | is this like html5 superfriends? |
| 19:28 | <Ms2ger> | Heh, CSS Eleven |
| 19:28 | <nimbu> | wat |
| 19:28 | <Ms2ger> | http://my.opera.com/dstorey/blog/css-eleven seems to be a contemporary blog post about them |
| 19:28 | <miketaylr> | is this like html5 superfriends? |
| 19:29 | <Ms2ger> | Mm, forgot about those too |
| 19:29 | <Ms2ger> | I guess those turned out just as useless |
| 19:35 | <tantek> | Ms2ger - nah - html5superfriends had an impact on the spec |
| 19:35 | <tantek> | e.g. <time> improvements very much started from brainstorming among the html5superfriends |
| 19:36 | <tantek> | also, AFAIK CSS Eleven as just an announcement - I don't know of any actual output |
| 19:36 | <tantek> | whereas HTML5 Super Friends published http://www.zeldman.com/superfriends/ |
| 19:36 | <tantek> | and http://www.zeldman.com/superfriends/guide/ |
| 19:36 | <tantek> | and was also one of the inspirations for me to write my book on HTML5. |
| 19:43 | <jgraham> | I'm pretty sure that "guide" was entirely ignored |
| 19:44 | <jgraham> | Except to the extent that you personally championed issues on the mailing lists |
| 19:44 | <jgraham> | Which is not surprising |
| 19:45 | <jgraham> | Making fancy announcements doesn't impress anyone |
| 19:45 | <jgraham> | Doing actual work does |
| 19:58 | <tantek> | jgraham, nah, the guide was well read because it was easy to read by a broad audience. |
| 19:58 | <tantek> | and then we filed follow-up issues to get actual changes made |
| 19:59 | <tantek> | the context of 2009 is also important, when there was a lot of hype+disappointment |
| 19:59 | <tantek> | in "HTML5" |
| 19:59 | <tantek> | so part of the point was to provide a broader recommendation that yes, in general HTML5 is good, and that web designers ought to move forward with it |
| 20:00 | <tantek> | web designers read blogs/twitter more than #whatwg or certainly lists^H^H^H^H^H support forums. |
| 20:16 | <Hixie_> | tantek: the "superfriends" didn't influence the spec, you did |
| 20:16 | <tantek> | Hixie - the superfriends influenced me |
| 20:16 | <tantek> | transitive |
| 20:16 | <tantek> | even if bottlenecked - which you know something about |
| 20:16 | <Hixie_> | in that case the war on iraq influenced the spec :-P |
| 20:17 | <tantek> | http://en.wikipedia.org/wiki/Butterfly_effect :P |
| 20:17 | <Hixie_> | yeah i don't think that's a useful definition for discussion :-) |
| 21:49 | <shepazu> | hober, is this a candidate for W3CMemes? http://schepers.cc/svg/text/simply-wrap-text-in-SVG.png |
| 22:10 | Hixie_ | comes across a comment in the html spec that says "<!-- This algorithm is a monument to bad design. Go legacy! -->" |
| 22:18 | <Hixie_> | well that's interesting |
| 22:18 | <Hixie_> | while firefox supports svg in <embed>, chrome just supports anything. html. images. |
| 22:18 | Hixie_ | brings out IE as a tie-breaker |
| 22:21 | <Hixie_> | great, the version of IE I have won't even load flash |
| 22:21 | <Hixie_> | anyone got IE10? |
| 22:22 | <Hixie_> | control test: does this say "pass"? http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2283 |
| 22:22 | <Hixie_> | image test: what does this do? http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2284 |
| 22:22 | <Hixie_> | html test: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2285 |
| 22:22 | <Hixie_> | svg type test: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2286 |
| 22:23 | <Hixie_> | (ignore the dump button) |
| 22:25 | <Hixie_> | and finally, svg test: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2287 |
| 22:28 | <Hixie_> | and finally finally, if the previous test actually worked: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2288 |
| 23:43 | <GPHemsley> | Hixie_: IE8: |
| 23:43 | <GPHemsley> | 2283 - pass |
| 23:44 | <GPHemsley> | 2284 has a disabled, empty box with a scrollbar |
| 23:44 | <GPHemsley> | 2285 has a tiny little empty square |
| 23:45 | <GPHemsley> | same for 2286 |
| 23:45 | <GPHemsley> | 2287 has a wide empty rectangle |
| 23:46 | <GPHemsley> | 2288 wants to run MSXML plugin |
| 23:46 | <GPHemsley> | so... none of them in any way match the "control", if they were supposed to |
| 23:54 | <Hixie_> | GPHemsley: cool, thanks |