| 00:00 | <mattur> | shepazu: the #ffs was short for: gosh, this is a slightly exasperating; the W3C /should/ be eating its own dogfood |
| 00:01 | <Hixie> | (and always has before!) |
| 08:28 | <annevk> | morning |
| 08:43 | <zcorpan> | Hixie: why "+ <li>All <a href=#xml-mime-type title="XML MIME type">XML MIME types</a></li>" ? |
| 08:46 | <zcorpan> | Hixie: the idea of supporting all unknown mime types ending with +xml has failed. web compat requires non-support. |
| 08:53 | <Ms2ger> | <Hixie> you guys give perl a bad name :-P |
| 08:53 | <Ms2ger> | Because it didn't have one yet? |
| 08:55 | <jgraham> | Please evreyone stop saying that. Every time I read it to the tune of Bon Jovi. That's practically illegal under the Geneva convention. |
| 08:56 | <annevk> | zcorpan, for XHR too? |
| 08:58 | <zcorpan> | annevk: for navigation. dunno about xhr, doesn't xhr assume xml if you use an unknown type (even if it doesn't end in +xml)? |
| 09:00 | <annevk> | no for missing or malformed content-type only |
| 09:16 | <zcorpan> | annevk: in opera i get an XMLDocument for text/foo |
| 09:24 | <annevk> | Opera is buggy |
| 09:24 | <annevk> | actually causes us issues |
| 09:25 | <zcorpan> | do other browsers do the +xml thing for xhr? |
| 09:25 | <annevk> | WebKit does at least |
| 09:25 | <zcorpan> | ok |
| 09:25 | <annevk> | WebKit is pretty compliant |
| 09:26 | <zcorpan> | ok, then +xml hasn't completely failed :) |
| 09:27 | <zcorpan> | but it's not clear to me why we should ban registration of unknown +xml types |
| 09:28 | <zcorpan> | hmm i guess i should file a bug on navigation |
| 09:42 | <zcorpan> | turns out google earth was the major +xml abuser |
| 09:42 | <AryehGregor> | Hixie, I don't have a Mac, no. |
| 09:43 | <annevk> | blocking all XML types btw blocks application/atom+xml |
| 09:43 | <annevk> | which I think web pages might legitimately handle |
| 09:43 | <AryehGregor> | (also, I'll be in Toronto for the next two days, so if anyone wants to contact me, e-mail is a better bet than IRC) |
| 09:43 | <zcorpan> | annevk: yeah |
| 09:44 | <annevk> | the web+ scheme convention is interesting |
| 09:44 | <annevk> | I wonder how the IETF will react |
| 09:44 | <annevk> | prolly late |
| 09:44 | <zcorpan> | annevk: although the last bullet point bans atom also |
| 09:45 | <annevk> | I wonder if that is for application/pdf and the like |
| 09:51 | <zcorpan> | <http://www.w3.org/mid/E1QvsLJ-0007QA-SV⊙jwo>; - this is why we should always err on the side of REOPEN instead of WONTFIX+TrackerIssue when somebody does REOPEN+TrackerIssue |
| 09:55 | <annevk> | I think the problem was that Murata added TRackerIssue but the i18n WG did not know about it |
| 10:08 | <zcorpan> | heh, the spec uses application/vnd.google-earth.kml+xml as an example use case for registerContentHandler but then bans XML types |
| 10:11 | <annevk> | whoa |
| 10:11 | <annevk> | blog.whatwg.org is slow |
| 10:13 | <annevk> | http://blog.whatwg.org/weekly-undomanager |
| 10:14 | <annevk> | I'm away the next 6 or 7 days so if someone else wants to write it next week go ahead |
| 10:22 | <zcorpan> | http://www.w3.org/2010/html-xml/snapshot/report.html seems to say "parsing HTML with an XML parser is problematic and parsing XML with an HTML parser is problematic. the best solution is to parse XML with an XML parser and HTML with an HTML parser." |
| 10:24 | <Ms2ger> | Tell the TAG |
| 10:25 | <annevk> | zcorpan, pretty much |
| 10:26 | <jgraham> | Hey, it's taken 10 ears to get past the "parsing HTML with an XML parser is problematic so everyone should produce XML always" stage |
| 10:26 | <jgraham> | *years |
| 10:26 | <jgraham> | The number of ears sacrified is unknown |
| 10:29 | <zcorpan> | 2.5 How can XML be made more forgiving of errors? is interesting |
| 10:29 | <zcorpan> | wonder if xml core will agree to specify lenient xml parsing |
| 10:30 | <annevk> | I put that in |
| 10:30 | <annevk> | sort of |
| 10:30 | <zcorpan> | or if somebody else will successfully do it over xml core's objections |
| 10:30 | <annevk> | I would finish my specification if one browser vendor would seriously consider implementing it |
| 12:04 | <Kellen`> | is the author of validator.nu here by any chance? |
| 12:06 | <Ms2ger> | He's on holiday until early next week, IIRC |
| 12:07 | <Kellen`> | okay thanks! is he usually in this channel? |
| 12:07 | <jgraham> | yep |
| 12:07 | <Kellen`> | awesome, I'll check back then |
| 12:10 | <zcorpan> | MikeSmith also fixes stuff in v.nu |
| 16:11 | <scor> | foolip: is the live microdata service down? http://foolip.org/microdatajs/live/ |
| 16:12 | <foolip> | scor, no, looks fine to me |
| 16:12 | <foolip> | is it b0rked in some way? |
| 16:12 | <foolip> | I pushed some changes a few days ago |
| 16:12 | <scor> | "wating for foolip.org" |
| 16:12 | <scor> | same goes for http://foolip.org/ |
| 16:13 | <foolip> | both are fine here |
| 16:13 | <foolip> | sounds like a network problem |
| 16:13 | <scor> | could it be my network then? |
| 16:13 | <scor> | it used to work from here in the past. let me check |
| 16:13 | <foolip> | perhaps I was blacklisted :) |
| 16:15 | <scor> | my network at work is very picky. sorry to have bugged you foolip, I'll check with my sysadmins… |
| 16:16 | <karlcow> | cute http://gsgwebs.com/help/browser_compatibility.html |
| 16:16 | <karlcow> | This page lists the discrepancies in HTML tag support between Netscape Navigator and Internet Explorer. |
| 16:18 | <karlcow> | had forgotten about dynsrc and lowsrc on images http://msdn.microsoft.com/en-us/library/ms533742(v=vs.85).aspx |
| 16:35 | <dglazkov> | good morning, Whatwg! |
| 16:36 | <Ms2ger> | Morning |
| 16:36 | <dglazkov> | wait what? are you visiting? :) |
| 16:50 | <dglazkov> | wiki.whatwg.org is down |
| 16:51 | <dglazkov> | Hixie, AryehGregor: ^^^ |
| 17:09 | <karlcow> | http://www.mnot.net/blog/2011/08/24/distributed_hungarian_notation_doesnt_work |
| 18:00 | <shepazu> | in case anyone here uses Thunderbird, and finds themselves needing to share a link to a specific email, I've made an add-on http://schepers.cc/archived-link |
| 18:02 | <Ms2ger> | I guess that's easier than ctrl-u and copy it from the header |
| 18:52 | <jarek> | Hi! |
| 18:52 | <jarek> | does any browser support or is planning to support native rendering of menu element? |
| 18:52 | <jarek> | http://www.w3.org/TR/html5/interactive-elements.html#the-menu-element |
| 18:52 | <smaug____> | jarek: latest FF builds have support for context menu |
| 18:53 | <jarek> | <smaug____> yeah, I have just stumbled upon this news |
| 18:54 | <smaug____> | jarek: note, the child elements should be <menuitem> elements, not <command> elements |
| 18:54 | <jarek> | <smaug____> but I wonder whether all menus are going to be rendered this way |
| 18:55 | <jarek> | is it possible to trigger contextmenu with left mouse button? |
| 18:55 | <smaug____> | depends on OS, I guess |
| 19:02 | <dglazkov> | annevk: Dimitri “good morning” Glazkov :D |
| 19:05 | <smaug____> | jarek_: in which way should the menus be rendered? |
| 19:08 | <jarek_> | <smaug____> I mean something like this: http://twitpic.com/68ztwa/full |
| 19:09 | <smaug____> | jarek_: isn't that how it is rendered now? |
| 19:09 | <jarek_> | <smaug____> I need HTML5 menus that would look exactly as those from native apps |
| 19:09 | <smaug____> | (I don't have a mac) |
| 19:09 | <jarek_> | <smaug____> I have just checked menu and contextmenu element on Chrome, both are completely unstyled by default |
| 19:10 | <smaug____> | contextmenu element? |
| 19:10 | <smaug____> | and I have no idea what Chrome does |
| 19:11 | <smaug____> | I thought it doesn't support <menu type="context"> yet |
| 19:11 | <jarek_> | oopps, it should be <menu type="context"> |
| 19:11 | <dglazkov> | jarek_: no implementation in WebKit as far as I know, so probably not in Chrome |