| 00:00 | <hober> | I guess I'll write an email |
| 00:01 | TabAtkins | really wishes he had figured out this <base> business a long time ago, before he started running into difficulties with content moving between paths. |
| 00:03 | <Hixie> | TabAtkins: if you find yourself needing <div>, then you're not doing markup before style. :-P |
| 00:03 | <TabAtkins> | Hixie: The issue is needing to adjust markup *after* styling fails due to limitations in CSS. |
| 00:03 | <Hixie> | ah |
| 00:03 | <TabAtkins> | When Template Layout is reliably present I'll be happy. ^_^ |
| 00:04 | <TabAtkins> | Yeah, so given an initial design where I have a <nav> and two <aside>s, is it okay to just <div>-wrap them to make them display properly, or do I *need* to <aside>-wrap them instead, and peel off the <aside>s wrapping the individual blocks. |
| 00:05 | <hober> | sent (re pubdate="") |
| 00:05 | <Hixie> | TabAtkins: if you're adding elements purely for styling purposes, you should use <div> |
| 00:05 | <Hixie> | that's what <div> is for |
| 00:06 | <TabAtkins> | Yeah, I know, just making sure that, even though there's an element *for* sidebars, it's still cool to collect things into a sidebar without it. |
| 00:06 | <TabAtkins> | I have tiny niggling inconsistencies in my brain that I'm ironing out right now. |
| 00:07 | <hober> | well, you should always use the element with the closest semantic to your need |
| 00:07 | <ttepasse> | The <main>-proposal got shot down, isn't it? |
| 00:07 | <tantek> | but not *over* semantic |
| 00:07 | <TabAtkins> | At least for now, yeah, ttepasse. |
| 00:07 | <hober> | tantek: indeed |
| 00:08 | <TabAtkins> | hober: I think tantek captured the point behind my questions. ^_^ |
| 00:08 | <tantek> | TabAtkins - I don't like <main> either, but could have settled for <shead>, <sbody>, <sfoot> |
| 00:08 | <TabAtkins> | ttepasse: main content is anything that's not <header>/<footer>/<nav>/<aside> |
| 00:08 | <tantek> | TabAtkins - I *guarantee* that most web devs will just end up creating a <div class="content"> or something similar to go between <header> and <footer> |
| 00:09 | <tantek> | it such a well established markup pattern |
| 00:09 | <ttepasse> | ?anything that's not <header>, etc.? is not easily adressable by JS oder CSS. |
| 00:09 | <TabAtkins> | I do it about 50/50 depending on whether I have styling ned for it. |
| 00:09 | <tantek> | in fact, I doubt you would find many class="header" and class="footer" on a page without an intervening class="content" or class="main" etc. (s/class/id as apropos) |
| 00:10 | <TabAtkins> | ttepasse: Yeah, I know. But it's sensical to ATs, frex. |
| 00:10 | <tantek> | good point ttepasse |
| 00:10 | <ttepasse> | ATs, frex? |
| 00:10 | krijn | joins the discussion |
| 00:10 | <TabAtkins> | AT = accessibility, um, I forget what the T is for. Frex = for example. |
| 00:10 | <krijn> | What's it about? |
| 00:10 | <tantek> | accessibility tools perhaps |
| 00:10 | <TabAtkins> | krijn: Pancakes or waffles: which is better? |
| 00:10 | <krijn> | Pancakes! |
| 00:11 | <TabAtkins> | Good, you and I will flank the infidels. |
| 00:11 | <krijn> | I agree a <main> or <content> thingy would be handy |
| 00:11 | <TabAtkins> | Hahahahahaha Myakura. |
| 00:11 | <krijn> | Now see what you've done :) |
| 00:11 | <tantek> | TabAtkins - is that some sort of subconscious circle vs square preference? or perhaps flat (pancake) vs cellular (waffle) |
| 00:12 | <TabAtkins> | I use a <div .main/.middle/.content/.block> for the non-foo stuff whenever I need it for a CSS or JS hook, yeah. |
| 00:12 | <krijn> | Me too |
| 00:12 | <TabAtkins> | It's about a genital vs oral preference. Freud was all over this. |
| 00:12 | tantek | prefers waffles because they are better structured to contain maple syrup in the cells. |
| 00:12 | <krijn> | Waffles remind me of tables |
| 00:12 | <hober> | yes, because the whole purpose of them is to deliver maple syrup (non-sarcastic) |
| 00:13 | <krijn> | And tables are evil, it seems |
| 00:13 | <tantek> | krijn HTML tables are simply misunderstood ;) |
| 00:13 | <krijn> | No, they are evil |
| 00:13 | <hober> | krijn: fortunately, maple syrup is tabular data |
| 00:13 | <krijn> | According to authors at least :) |
| 00:13 | <hober> | so marking it up in a waffle is approprate |
| 00:13 | <krijn> | So, concluding, we need a <waffle> tag |
| 00:14 | <TabAtkins> | I support this proposal. |
| 00:14 | <krijn> | Can we overrule Hixie without discussion already? |
| 00:14 | <krijn> | Or are we still not there yet? |
| 00:14 | TabAtkins | delivers his breakfast over the wire. |
| 00:14 | <TabAtkins> | Let's vote. |
| 00:14 | <TabAtkins> | Aye for <waffle>, nay for <hixie>. |
| 00:14 | <krijn> | Aye |
| 00:14 | <krijn> | For the record, beer and aye saying don't match |
| 00:15 | <TabAtkins> | A <hixie> element ridicules your use of presentational markup. It's like <audio> but demeaning. |
| 00:15 | <beowulf> | someone say waffles? |
| 00:16 | <TabAtkins> | Yes, how do waffles relate to the struggle to evangelize semantic markup, and the difficulties contained in keeping your fingers from getting sticky when using <td>s. |
| 00:18 | Hixie | checks the air ducts for contaminants |
| 00:18 | <ttepasse> | I hope <hixie> has a textual fallback. |
| 00:18 | <krijn> | Oh look, contaminants! |
| 00:18 | <krijn> | :) |
| 00:20 | <krijn> | Btw, the biggest liquor store in the Netherlands now uses HTML5 for their website \o/ |
| 00:21 | <TabAtkins> | Woo! \o/ |
| 00:21 | <krijn> | In case anybody was waiting for that information |
| 00:21 | <krijn> | Thanks everybody in here for making that happen :) |
| 00:26 | <krijn> | And before I get to emotional, nn everybody |
| 00:26 | <TabAtkins> | later |
| 00:26 | <krijn> | o. |
| 00:27 | <krijn> | o/ |
| 00:27 | <ttepasse> | Why are there such strong restriction for permissible aria roles on some elements? |
| 00:27 | <ttepasse> | By my reading I can't do <table role="grid main"> or am I wrong? |
| 00:32 | <TabAtkins> | Where's that section again? I can never remember the name of it so I can't find it in the TOC. |
| 00:33 | <ttepasse> | 3.2.6 |
| 00:36 | <TabAtkins> | Hmm, so you're saying that the table itself is the main content all by itself? |
| 00:38 | <ttepasse> | Yes. Think about a better markuped webserver directory listing. There may be additional stuff like a logo and navigation but the main content is the listing of files and directories. |
| 00:38 | <Hixie> | send mail if you think the restrictions should be relaxed |
| 00:40 | <tantek> | TabAtkins - the obv use case for a <table> being the main content all by itself is a CSV file that's been transcoded into an HTML <table> |
| 00:40 | <TabAtkins> | Yeah, I was thinking something like that. |
| 00:40 | <Hixie> | can a role="" take two values btw? i thought it could only take one. |
| 00:41 | <TabAtkins> | Well, we've got a use-case for such right here. |
| 00:41 | <ttepasse> | /xhtml-role/ has even an example with two, so yes. |
| 00:41 | <TabAtkins> | A combination of a type and landmark role. |
| 00:41 | <tantek> | in fact, I wouldn't mind seeing a <csv> ... </csv> element that acted like a <pre> except 1. parsed for the comma separation and implied columns accordingly, and 2. provided a DOM similar to <table> for accessing all the rows and columns. |
| 00:41 | <TabAtkins> | ... |
| 00:42 | <TabAtkins> | I must code support for this tonight. |
| 00:42 | <Hixie> | i wonder what the UA conformance criteria are for two roles |
| 00:42 | <tantek> | This would rapidly accelerate the "webification" of the numerous CSV files out there (more and more being published due to OpenGov and OpenScience) efforts |
| 00:42 | <Hixie> | i don't understand what it would mean |
| 00:44 | <hober> | ttepasse: keep in mind that aria's role="" isn't the same attribute as the xhtml2wg role attribute spec |
| 00:44 | <tantek> | hober, thank goodness. |
| 00:44 | <ttepasse> | Oh it is? |
| 00:44 | <hober> | tantek: :) srsly people, we already got one (class="") |
| 00:44 | <ttepasse> | There should be a "/TR/ for dummies" tutorial. |
| 00:46 | <ttepasse> | Hixie, http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224/#mapping_role |
| 00:47 | tantek | adds <csv> to the list of (perhaps crazy) proposals he has to write up for HTML5. |
| 00:47 | <Hixie> | ok so basically they allow it and then immediately say it's pointless |
| 00:47 | <Hixie> | good work |
| 00:48 | <tantek> | Hixie, of course, there's nothing like that in the HTML5 spec, <cough>img border="0"</cough> |
| 00:48 | <tantek> | ;) |
| 00:51 | <ttepasse> | ?Because landmarks do not generally have mappings in platform accessibility APIs, they may occur anywhere within the role string without affecting how the first widget role is exposed.? ... sounds like my <table role="grid main"> is not so pointless but makes me wonder what landmarks are for. Custom UI in UAs? |
| 00:51 | <Hixie> | tantek: blame hsivonen, i hate that as much |
| 00:52 | <tantek> | Hixie - is there "blame" markup in the HTML5 spec? Kind of like blame in CVS... |
| 00:53 | <Hixie> | svn blame blames me for everything, but at least one of the checkin comments says "blame: hs" :-) |
| 00:55 | <Hixie> | btw, tantek, any idea when zeldman and co are sending their feedback in? |
| 00:57 | <Hixie> | tantekc: btw, any idea when zeldman and co are sending their feedback in? |
| 00:57 | <tantekc> | Hixie, I believe we are all taking bits and pieces of http://www.zeldman.com/superfriends/guide/ and emailing them in - hence the "we are optimistic that the official channels provided by the working group will offer a sufficient and fair hearing of our concerns" |
| 00:57 | <tantekc> | Hixie, I believe we are all taking bits and pieces of http://www.zeldman.com/superfriends/guide/ and emailing them in - hence the "we are optimistic that the official channels provided by the working group will offer a sufficient and fair hearing of our concerns" |
| 00:57 | <Hixie> | k |
| 00:58 | <Hixie> | any idea what the time frame on that is? |
| 00:58 | <tantekc> | As you know, I prefer to document things on the web first, and then email in URLs. |
| 00:58 | <tantekc> | timeframe: as soon as possible |
| 00:58 | <Hixie> | if you could mail in text, that would make my life much easier, fwiw |
| 00:58 | <tantekc> | ok I will mention that you prefer plain text email |
| 00:58 | <Hixie> | thanks |
| 00:59 | <tantekc> | Hixie, have you documented your Communication Preferences anywhere online? E.g. http://tr.im/comms |
| 00:59 | <tantekc> | if you have, please give me the URL and I will happily link to it |
| 00:59 | <Hixie> | tantekc: "Comments are very welcome, please send them to whatwg⊙wo Thank you." |
| 00:59 | <Hixie> | (top of the spec) |
| 00:59 | <tantekc> | I meant in general, your personal prefs. |
| 01:00 | <tantekc> | because obviously you eventually look at bugs filed, blog posts, blog post comments etc. |
| 01:00 | <tantekc> | (perhaps not guaranteed, but that seems to be the emergent behavior) |
| 01:00 | <Hixie> | oh you mean in general? no, no preferred communication style. |
| 01:01 | <Hixie> | i have an antipreference for phone communication and anything involving burning gasoline or going through TSA checkpoints |
| 01:01 | <tantekc> | so the only communication preference you have has to do with the HTML5 project |
| 01:01 | <Hixie> | yeah |
| 01:01 | <Hixie> | well, i mean, my preferences are specific to whatever i'm doing |
| 01:01 | <tantekc> | you've written up a scathing deconstruction of telcons for example (most of which I agree with) |
| 01:01 | <Hixie> | (i have a preference for HTML5, simply because there are certain things that are easier to dealing with) |
| 01:01 | <Hixie> | i wrote an e-mail recently... let's see |
| 01:02 | <tantekc> | anyway - it might be useful to see them in an ordered list |
| 01:02 | <tantekc> | with perhaps a threshold for, -- below this point I will avoid these forms of communication -- |
| 01:02 | <Hixie> | http://lists.w3.org/Archives/Public/public-html/2009Jun/0616.html |
| 01:02 | <tantekc> | and then you can list phone, f2f, flying etc. |
| 01:03 | <tantekc> | yeah that one - I read it. |
| 01:03 | <tantekc> | a good write up |
| 01:03 | <Hixie> | e-mail, irc, jabber, aim, msn, yahoo messenger; twitter, blogs; forums i have to register for; meetings. I don't have a phone. |
| 01:03 | <Hixie> | where ";" indicates a threshold, so all things between ; are equally ok |
| 01:04 | <TabAtkins> | tantekc: http://www.xanthir.com/etc/csv.html |
| 01:04 | <tantekc> | anyway - g2g, but just wanted say thanks Hixie for already fixing a bunch of stuff in HTML5 that Zeldman et al gave feedback on (e.g. the "HTML5" vs. "HTML 5" inconsistency) - pretty much all that feedback was a consensus result of the "HTML5 Super Friends" |
| 01:04 | <TabAtkins> | Not perfect yet - I need to copy over all attributes of the original <csv> element - but still, working! |
| 01:05 | <tantekc> | TabAtkins - WHOA! that is super cool |
| 01:05 | <TabAtkins> | Super easy. ^_^ |
| 01:05 | <tantekc> | I might wrap the <csv> in a <pre> for backward compat display |
| 01:06 | <TabAtkins> | Would be fine - you sorta expect csvs to be fixed-width anyway. |
| 01:06 | <tantekc> | right |
| 01:06 | <tantekc> | or maybe just use a style sheet |
| 01:06 | <tantekc> | csv {whitespace:pre} |
| 01:06 | <tantekc> | that ought to do it |
| 01:06 | <TabAtkins> | Yeah, that'd work. |
| 01:07 | <tantekc> | TabAtkins - want to collaborate on a joint <csv> proposal submission for HTML5? |
| 01:07 | <tantekc> | like I said, g2g now, but I can start drafting something based on the above |
| 01:07 | <TabAtkins> | Note - that would make the original CSV, and presumably a native CSV, look pre, but wouldn't affect the js-shim csv. |
| 01:07 | <TabAtkins> | Sure, tantekc. |
| 01:09 | <tantekc> | scientists will *love* <csv> for easily publishing data sets on the web |
| 01:09 | <tantekc> | this is going to be a big enabler for open science on today's web. (my current thoughts: http://tr.im/openscience ) |
| 01:09 | <TabAtkins> | Heh, cool. |
| 01:13 | <TabAtkins> | So, how do I iterate through a DOM Node's attributes? |
| 01:13 | <TabAtkins> | node.namedNodeMap()? |
| 01:16 | <othermaciej> | node.attributes |
| 01:17 | <othermaciej> | (or really, element.attributes) |
| 01:17 | <TabAtkins> | Since I program in jQuery, not js, does that return an array? Or some exotic DOM structure? If the latter, how do I iterate through it? |
| 01:18 | <Binarytales> | i think it's an array |
| 01:18 | <TabAtkins> | It looks like it at least acts like one. $.each() can handle anything with .length |
| 01:19 | <othermaciej> | it's a NamedNodeMap; I don |
| 01:19 | <othermaciej> | 't know about jQuery details |
| 01:19 | TabAtkins | is testing |
| 01:22 | <TabAtkins> | All right, got it. Yeah, $.each() handles it fine. |
| 01:24 | <TabAtkins> | Though I should probably translate this to plain DOM... |
| 01:25 | <TabAtkins> | I need to go look at what jQuery actually does for each of these functions so I can back-translate. |
| 01:35 | <TabAtkins> | Hrm, does IE treat linebreaks funny? I'm trying to do a .split("\n"), but it's a no-go in IE. Perhaps auto-translating to \r\n? |
| 01:35 | <TabAtkins> | Context: textContent of an unknown element, hacked into recognition with the document.createElement shim. |
| 01:36 | <GPHemsley> | TabAtkins: That sounds familiar, but I can't say more than that. |
| 01:36 | <TabAtkins> | Hm, doesn't seem to help. |
| 01:36 | <GPHemsley> | :P |
| 01:36 | <GPHemsley> | hey hey! |
| 01:36 | <TabAtkins> | Not you. ^_^ Changing to .split("\r\n") doesn't help. |
| 01:37 | <GPHemsley> | oh, heh |
| 01:48 | <TabAtkins> | Okay, IE does newline normalization immediately, unless it has white-space:pre. |
| 01:48 | <TabAtkins> | So I got the newlines, now I'm just trying to figure out how to split by them... |
| 02:02 | <dpranke> | hixie / anyone : is there a reason why <select>, <input type="range">, and <input type="number"> don't support the "readonly" attribute? |
| 02:02 | <Hixie> | type=number does |
| 02:03 | <Hixie> | <select>, <input type=range>, <input type=radio>, <button>, etc, don't, because they're not text fields. |
| 02:04 | <dpranke> | you're right about number, sorry, I read too fast. |
| 02:07 | <dpranke> | what's the difference between disabled and readonly? It looks like disabled is readonly plus the control doesn't receive events? Why have readonly be able to receive events? |
| 02:07 | <dpranke> | or is there some other useful difference between disabled and readonly? |
| 02:08 | <Hixie> | the point of readonly is to allow users to copy the text from the control |
| 02:08 | <TabAtkins> | OMG, finally got IE to recognize a newline and split on it. The <csv> proposal marches on! |
| 02:09 | <dpranke> | ah. okay. does it make sense to add a clarifying note to that effect to the spec, or is this common knowledge? |
| 02:09 | <Hixie> | it's basic UI design :-) |
| 02:11 | <dpranke> | ok, thanks! |
| 02:14 | jcranmer | marvels at how much space The Great Codec Wars took up in his WHATWG folder |
| 02:21 | <Hixie> | oh dear, othermaciej is now being dragged into actually running these meetings |
| 02:21 | <othermaciej> | Hixie: I can live with running 1/3 of them or so |
| 02:21 | <othermaciej> | but yes, that was part of the cost, along with my soul |
| 02:21 | <Hixie> | nothing says we _must_ have telecons |
| 02:22 | <othermaciej> | I'm not going to propose canceling telecons, at least not right now |
| 02:22 | <Hixie> | in fact our charter, rather than requiring one a week, says that we're not allowed to have _more_ than one a week |
| 02:22 | <Hixie> | and says they should only be as needed |
| 02:22 | <Hixie> | it's your time :-) |
| 02:22 | <Hixie> | you spend it as you think best :-) |
| 02:22 | <othermaciej> | I think some of the people who attend get value out of it, and I'm willing to spend an hour of my time to give them that value |
| 02:23 | <othermaciej> | particularly if it helps some of those people also get involved by email |
| 02:36 | <othermaciej> | this is kind of sad, but I'm actually proud of the way I formatted the agenda email |
| 02:38 | <rubys> | http://www.w3.org/html/wg/tracker/actions/103?changelog |
| 02:39 | <rubys> | that action was assigned to Lachlan... but he never responded to emails checking for status. |
| 02:39 | <rubys> | 2009-01-29 17:54:35: Owner changed to 'Lachlan Hunt' [Dan Connolly] |
| 02:39 | <rubys> | 2009-05-07 16:10:37: Owner changed to 'Julian Reschke' [Dan Connolly] |
| 02:40 | <rubys> | http://www.w3.org/html/wg/tracker/issues/75 is already closed |
| 02:52 | <othermaciej> | rubys: I'll just make those adjustments in-flight rather than confusing people by changing the agenda |
| 02:52 | <othermaciej> | rubys: thanks! |
| 06:31 | <cardona507> | is there a firefox extension similar to codeburner (the firebug plug-in) for html 5? |
| 07:09 | <hsivonen> | looks like we have a new case of adding attributes in JS to work around validators: http://stackoverflow.com/questions/1145880/can-autocapitalize-be-turned-off-with-javascript-in-mobile-safari |
| 08:10 | <Lachy> | dammit, why did apple feel the need to create more proprietary attributes for autocapitalize and autocorrect?! |
| 08:22 | <Hixie> | did printers get slower? i could have sworn that 20 years ago laserjets were printing at least as fast as the ones i'm seeing on HP's site today, and they warmed up faster at that. |
| 08:23 | <hsivonen> | Hixie: the high end probably hasn't gotten slower but a lower end got introduced and people started bying those |
| 08:23 | <Hixie> | where do you find the high end? |
| 08:24 | <Hixie> | i can't even find a single 802.11x printer on HP's site |
| 08:24 | <hsivonen> | Hixie: at Kinko's |
| 08:24 | <Hixie> | (laserjet printer, that is) |
| 08:24 | <Hixie> | heh |
| 08:24 | <Hixie> | i mean to buy :-) |
| 08:25 | <hsivonen> | hmm. I don't know if HP has exited the high end market and left it to Xerox and Canon |
| 08:25 | <hsivonen> | (I don't know where to buy those) |
| 08:25 | <Hixie> | "First color page in less than 16 seconds" $3199.99 |
| 08:25 | <Hixie> | 16 seconds?! |
| 08:26 | <Hixie> | (HP Color LaserJet 5550dn Printer ) |
| 08:26 | <annevk2> | is that including boot-time or so? |
| 08:26 | <annevk2> | and 3200 for a printer is a lot |
| 08:27 | <Hixie> | yes and yes |
| 08:27 | <Hixie> | for $3199.99 i expect my printer to be printing before i ask it to |
| 08:29 | annevk2 | has a EUR 80 (or less, don't really remember) black/white-laserjet that he almost never needs |
| 08:30 | <Lachy> | I gave up on owning a printer. My old, affordable, inkjet printers kept drying out cause I don't print frequently enough, and when I do, I just do it at the office |
| 08:31 | <Hixie> | yeah this isn't for me |
| 08:31 | <Hixie> | i haven't printed in like a decade |
| 08:33 | <Hixie> | what are the quality printer manufacturers these days? is HP still it? |
| 08:33 | <Lachy> | Hixie, is it intended for personal use by whoever you're getting it for, or office use? |
| 08:33 | <Hixie> | what's the difference? |
| 08:34 | <Lachy> | different feature requirements |
| 08:34 | <annevk2> | Hixie, canon is also ok, not sure about laserjet |
| 08:35 | <Lachy> | like, an office printer would probably need an ethernet connection and be optimised for network setup, whereas personal use might not need that |
| 08:36 | <annevk2> | for network setup you could always buy one of those apple thingies |
| 08:36 | <annevk2> | with a usb-in |
| 08:36 | <Hixie> | the requirements are: high quality (laser jet), network printer using 802.11g or n, color, automatic double-sided printing, fast per page and fast from cold. |
| 08:36 | <Hixie> | and reliable. |
| 08:36 | <Lachy> | annevk2, the Airport Extreme or possibly Airport Express |
| 08:36 | <Hixie> | i'd rather it have built in networking |
| 08:38 | <Hixie> | HP doesn't have a printer that meets those requirements. |
| 08:38 | <annevk2> | i've no experience at all with such beasts |
| 08:38 | <Hixie> | at least not according to their site. |
| 08:38 | <Lachy> | Hixie, so just printing, and no need for scanner/copier/fax functions? |
| 08:38 | <annevk2> | my printer is in the closet and I take it out every couple of months to print some stupid expense report |
| 08:38 | <Hixie> | right |
| 08:40 | <Lachy> | Hixie, http://www.brother-usa.com/Printer/ModelDetail.aspx?ProductID=HL4070CDW |
| 08:41 | <Hixie> | looks interesting |
| 08:41 | <Lachy> | still 17 seconds for first print though |
| 08:41 | <Lachy> | for colour |
| 08:41 | <Philip`> | annevk2: You should use a commercial printing service for that, and then charge it on expenses |
| 08:42 | <Hixie> | yeah, still slow though |
| 08:42 | <Hixie> | both starting up and printing |
| 08:42 | <Lachy> | you consider 21ppm slow? |
| 08:43 | <Lachy> | that's 1 page every 3 seconds |
| 08:44 | <Hixie> | that's not faster than 20 years ago |
| 08:44 | <annevk2> | Philip`, I'll ask for your advice next time :) |
| 08:44 | <Hixie> | so yes, i consider that slow |
| 08:44 | <annevk2> | Philip`, meanwhile, charset stats? :) |
| 08:44 | <Lachy> | so how many pages per minute are you expecting? |
| 08:44 | <annevk2> | Hixie, is this how you remember 20 years ago? |
| 08:44 | <Hixie> | annevk2: :-P |
| 08:44 | <Philip`> | Does anybody give double-sided printing speeds? |
| 08:45 | hsivonen | only has a printer for paper-based accounting use cases |
| 08:46 | Philip` | presumes 21ppm is one-sided, because all printers he's seen do double-sided make the paper go backwards and forwards lots of times before popping out and it takes forever |
| 08:46 | <hsivonen> | though when it exists, it can occasionally be used for printing train tickets |
| 08:47 | <Hixie> | Philip`: yeah, agreed |
| 08:47 | <Lachy> | http://www.office.xerox.com/printers/color-printers/phaser-7760/enus.html |
| 08:48 | <Lachy> | 35ppm for colour |
| 08:48 | <Lachy> | 45ppm for black |
| 08:48 | <Lachy> | "First-page-out time as fast as 9 seconds for color" |
| 08:49 | <Lachy> | Is that fast enough? |
| 08:49 | <annevk2> | no wifi though |
| 08:50 | <Lachy> | yeah, but I was only searching for speed to see if it was possible to find anything at all fast enough for Hixie |
| 08:50 | <Hixie> | Lachy: hmm, that's better than i've seen so far |
| 08:51 | <Lachy> | Hixie, "With print speeds of up to 35 pages per minute for colour and 45 ppm for black and white and a first-page-out time of nine seconds for colour, the Phaser is considered one of the fastest printers in its class. " -- http://www.highbeam.com/doc/1G1-158653373.html |
| 08:51 | <jgraham> | Maybe there is a limit to how fast you can physically pull paper through a printer without bad side effects |
| 08:53 | <jgraham> | Anyway we had some Xerox phaser thing when I was doing my PhD and it seemed OK. It got used a lot and didn't break down often or anything |
| 08:53 | <Hixie> | cool |
| 08:54 | <Hixie> | good to know what the top of the line is, at least |
| 08:54 | <jgraham> | Colour reprodution was pretty poor. Dunno how fast it was or anything |
| 08:54 | <hsivonen> | are there color lasers whose color reproduction doesn't suck? |
| 08:54 | hsivonen | thought color lasers were for printing powerpoint slides |
| 08:55 | <hsivonen> | and ad bureaus and the like used slower and more expensive non-laser stuff |
| 08:55 | <jgraham> | In this case they were for printing science papers where relative colour tends to be more important than absolute colour |
| 08:55 | <jgraham> | s/they were/it was/ |
| 08:55 | <Hixie> | yeah if you want to do something where colour really matters, you do ink jets, i think |
| 08:56 | <Hixie> | but then if i'm printing photos, i'm gonna be using a photo printing shop |
| 08:56 | <hsivonen> | are wax printers still on the market? |
| 08:57 | <Hixie> | is that "solid ink"? |
| 08:57 | <jgraham> | 9we were very licky to have a good colour printer at all; it was only because my group had seperate funding from the rest of the department. The department colour laserjet _really_ sucked) |
| 08:57 | <hsivonen> | Hixie: could be. I don't know. |
| 08:58 | <jgraham> | s/9/(/ and s/licky/lucky/ |
| 09:33 | <Mrmil> | I hate IE |
| 09:34 | <krijnh> | High five! |
| 09:35 | <Mrmil> | Highway to Hell |
| 10:04 | <hsivonen> | I'm puzzled. With my latest HTML5 parser refactoring, jquery on http://webtrendmap.com/craigmod/161/ dies due to document.body being null |
| 10:04 | <hsivonen> | I wonder how that can happen |
| 10:04 | <gsnedders> | Because there's a bug. |
| 10:04 | <Dashiva> | hsivonen: Script in <head> before body is created? |
| 10:05 | <hsivonen> | Dashiva: jquery is in head, yes |
| 10:05 | <hsivonen> | Dashiva: but it works without the HTML5 parser refactoring |
| 10:05 | <hsivonen> | I wonder if I've accidentally caused onload or DOMContentLoaded to fire prematurely or something like that |
| 10:08 | <gsnedders> | I think you should never fire them. |
| 10:09 | <jgraham> | gsnedders: You miss Philip`? |
| 10:10 | <gsnedders> | Huh? |
| 10:10 | <gsnedders> | jgraham: No, it's my Swedish Mummy, Daddy, and Nanny I miss :P |
| 10:10 | <jgraham> | Well you have started filling in the "useless suggestions" role |
| 10:10 | <gsnedders> | I've always done that quite a bit, though. |
| 10:12 | <hsivonen> | sigh. I have a crash, too. |
| 10:12 | <hsivonen> | how hard can it be to move some code around? |
| 10:13 | <gsnedders> | Very. |
| 10:13 | <hsivonen> | refcounting is a house of cards |
| 10:15 | <hsivonen> | apparently moving code around is fairly easy, but splitting one refcounted object into many is a can of worms |
| 10:15 | <annevk2> | xmlns issue still unadressed |
| 10:16 | <annevk2> | are these people just incompetent at XML namespaces while happily using them? |
| 10:16 | <gsnedders> | annevk2: Then I guess we can free it |
| 10:16 | <hsivonen> | annevk2: in the RDFa draft? |
| 10:16 | <annevk2> | yes |
| 10:16 | <Philip`> | gsnedders: You don't miss me? :-( |
| 10:16 | <gsnedders> | Philip`: Sorry, but jgraham just means so much more to me. |
| 10:16 | <annevk2> | it has been raised like a bazillion times |
| 10:17 | <annevk2> | my last email on this subject never had a reply I think |
| 10:17 | <annevk2> | I think they just don't get it |
| 10:17 | <Philip`> | Their response to http://rdfa.info/wiki/Rdfa-in-html-issues#Script-based_modification_of_DOM (further down that page) seems to miss the issue with that example |
| 10:17 | <annevk2> | I guess if you don't get XML namespaces they look all nice and dandy :) |
| 10:17 | <hsivonen> | annevk2: usually, if one "gets" namespaces, one wants to avoid them |
| 10:17 | Philip` | should probably look at this again some time, and try to clarify what still seems to be a problem |
| 10:17 | <annevk2> | right :) |
| 10:22 | <annevk2> | ah, othermaciej raised the issue as well and manu didn't get it |
| 10:23 | <annevk2> | he in fact simply snipped that comment from othermaciej's review |
| 10:23 | <othermaciej> | did he? |
| 10:23 | <othermaciej> | I thought he replied to that point (and I replied back) |
| 10:24 | <othermaciej> | it also looks like he pasted my comments about xmlns in text/html into the wiki |
| 10:24 | <annevk2> | http://lists.w3.org/Archives/Public/public-html/2009Sep/0082.html in 4.3 your point about the DOM being different is no longer there |
| 10:24 | <othermaciej> | it is here though: http://rdfa.info/wiki/Html5-rdfa-wd-issues#4.2_Invalid_XMLLiteral_values |
| 10:25 | <othermaciej> | er |
| 10:25 | <othermaciej> | not in the 4.2 section |
| 10:25 | <othermaciej> | but you know what I mean |
| 10:25 | <othermaciej> | he only directly replied to a few of my points and recorded the rest on the wiki |
| 10:25 | <annevk2> | i see |
| 10:26 | <othermaciej> | if you look at my further email, what XHTML+RDFa says about prefix binding is broken even for XML |
| 10:26 | <annevk2> | his reply still shows misunderstanding of the issue but I guess they're working on that then... |
| 10:27 | <annevk2> | i love it that such crap comes from the same people who claim XML is easy |
| 10:29 | <hsivonen> | othermaciej: I suspect RDFa is layered on top of XML 1.0--not on top of XML 1.0 + Namespaces |
| 10:30 | <othermaciej> | hsivonen: does that negate the error I pointed out in its rules about prefix bindings? |
| 10:30 | <hsivonen> | othermaciej: which is a pretty fundamental layering violation but gets an applause, because it looks like it's layered on top of Namespaces |
| 10:30 | <othermaciej> | (I don't think it does) |
| 10:31 | <annevk2> | hsivonen, that cannot be for real |
| 10:31 | <annevk2> | hsivonen, RDFa also references XMLNS |
| 10:31 | <hsivonen> | othermaciej: I think what you said stands |
| 10:32 | <othermaciej> | RDFa cites XMLNS, I am not sure what aspect makes it layered on top of XML 1.0 |
| 10:32 | <hsivonen> | annevk2: I guess I need to look up an email from Mark Birbeck |
| 10:33 | <othermaciej> | the text I cited does seem to be treating XML namespace declarations as just ordinary attributes, but that seems to be just a symptom of its generally wrong use of terminology |
| 10:33 | <Philip`> | hsivonen: I thought the idea is it's layered on XHTML (1.1 or Modularization or something), which is layered on Namespaces to some extent |
| 10:34 | <Philip`> | (though not to a particularly well defined extent) |
| 10:34 | <Philip`> | http://www.w3.org/mid/4A291657.9020805⊙cau |
| 10:34 | <hsivonen> | othermaciej: I think it's a symptom of not layering the spec over Namespace but using xmlns as a trompe-l’œil |
| 10:35 | <othermaciej> | it would probably make more sense for it to cite Namespaces in XML for namespace scoping instead of having its own rule for how to do it |
| 10:35 | <Philip`> | It might partly come from viewing XML documents as strings which follow a certain grammar, instead of as a DOM/Infoset-like tree |
| 10:35 | <annevk2> | hsivonen, ah yeah, it does do that |
| 10:35 | <othermaciej> | although that would mean more work to define how it works in text/html |
| 10:36 | <Philip`> | (The XML spec itself seems to be designed from the string viewpoint) |
| 10:36 | <annevk2> | Philip`, which is weird at least for <?xml encoding="..." |
| 10:37 | <hsivonen> | annevk2: http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Feb/0109.html |
| 10:37 | <othermaciej> | anyway, I'm glad Manu put forth a technical proposal this time instead of a procedural one, even if it seems like it needs work |
| 10:38 | <hsivonen> | gotta go to lunch |
| 10:39 | <hsivonen> | just got Snow Leopard in the mail. I wonder if I should wait until 10.6.1 before I install... |
| 10:39 | <othermaciej> | it seems like they could just use the "Namespaces in XML" definition of namespace prefixes in scope, even if they use the prefixes for non-namespace reasons |
| 10:40 | <othermaciej> | 10.6.0 is better than the average 10.n.0 |
| 10:41 | <othermaciej> | it seems like HTML+RDFa needs to make @rev and various other attributes conforming |
| 10:42 | <Philip`> | It probably needs to do something similar to what's in http://philip.html5.org/docs/rdfa/ |
| 10:43 | <Philip`> | (except probably without copying-and-pasting the RDFa-in-XHTML processing model, because duplication is bad) |
| 10:43 | <Philip`> | (and the issues with e.g. precisely defined attribute parsing apply to XHTML as much as to HTML) |
| 10:48 | <othermaciej> | Philip`: that draft looks much more precise, despite its unfinished state |
| 10:48 | <othermaciej> | Philip`: might be good to point out that draft on the list |
| 10:49 | <Philip`> | I wonder if I should try rewriting it to remove the duplication of the processing model, since that seemed to be the main objection to it |
| 10:51 | Philip` | could probably attempt that this afternoon |
| 10:55 | <othermaciej> | Philip`: if you have the time to pursue it, then I would encourage you to pursue that and post the draft |
| 10:55 | <alkarin> | greetings everybody |
| 10:55 | alkarin | posts: http://kunter.posterous.com/html-5-super-concerns |
| 11:05 | <beowulf> | is it worth saying that <dialog> should allow <li> rather that <dt><dd>, or if no <dialog> then the old advice of using <dl> for dialog should be updated to allow <li>? |
| 11:06 | <annevk2> | it's prolly better to start from scratch if you want to do something different |
| 11:06 | <alkarin> | unless one of us not planning to unleash a chat server or a walky-talky page, I think most designer will straight pass this dialog idea. |
| 11:06 | <annevk2> | because it's unclear what use cases everyone has in mind |
| 11:06 | <alkarin> | : concurs. |
| 11:06 | <beowulf> | annevk2: my use case is krijnh's logs |
| 11:07 | <annevk2> | i think just like for footnotes the spec should just give a few ideas on how you can mark such things up |
| 11:07 | <alkarin> | if we are to avoid DIV tags because they are regarded as unambigious, then we'll need to have a hundred more |
| 11:07 | <annevk2> | instead of dedicating an element to it |
| 11:08 | <annevk2> | or like tag clouds |
| 11:08 | <beowulf> | annevk2: sounds fair |
| 11:17 | <erlehmann> | beowulf, can you tell me again how several people saying the same thing could be conveyed with ordered lists ? |
| 11:17 | <erlehmann> | beowulf, also got around to researching the alledged small screen rendering issues ? |
| 11:18 | <erlehmann> | annevk2, i was thinking footnotes were <aside> ? |
| 11:20 | <erlehmann> | i'll probably style them as small inline text or expandable inline container (with :hover and :focus) as long as CSS hasn't footnote / endnote capabilities |
| 11:25 | <annevk2> | erlehmann, not always |
| 11:30 | <erlehmann> | annevk2, can you clarify the other possibilities ? |
| 11:32 | <annevk2> | see spec |
| 11:35 | <beowulf> | erlehmann: surely i only need to tell you once, then you accept or deny my claim |
| 11:36 | <erlehmann> | beowulf, curse your sudden and inevitable dialog-hate :D |
| 11:37 | <beowulf> | erlehmann: i no longer work for dotmobi so getting access to the test suite isn't easy, but as i recall default styling on dd's creates an indent that makes viewing content difficult due to the shortened measure. |
| 11:37 | <erlehmann> | oh, its that |
| 11:37 | <erlehmann> | but its only default styiling |
| 11:38 | <beowulf> | that's all some mobile have |
| 11:38 | <beowulf> | mobiles |
| 11:38 | <erlehmann> | o.0 |
| 11:38 | <beowulf> | i did say low end |
| 11:38 | <erlehmann> | then speak to mobile browser vendors ? |
| 11:39 | <beowulf> | lol |
| 11:39 | <erlehmann> | i must admit, i have not heard of the low-end you are talking about. i tried WAP and went straight to smartfones that CAN do CSS |
| 11:39 | <beowulf> | cool |
| 11:39 | <erlehmann> | but bad default styling is not something to be said against an element, but against an implementation, amiwrong? |
| 11:40 | <beowulf> | i did say this wasn't a big issue with dt/dd in dialog |
| 11:40 | <beowulf> | a corner case i'd say |
| 11:40 | <beowulf> | a corner of a corner case |
| 11:41 | <erlehmann> | so whats the big issue then ? chatlogs surely are markup-able in <dialog>s |
| 11:42 | <erlehmann> | maybe the timestamp thingy needs more consideration. <time> elements in dialogs seem nice |
| 11:42 | <beowulf> | the issue for me is it's not clear how you'd mark up a join, away, part, quit, disconnect, netsplit, nickchange, status change, etc in a dt/dd |
| 11:42 | <erlehmann> | besides, i can envision an XML transform to convert an XMPP stream into <dialog> |
| 11:43 | <beowulf> | but i don't think anyone cares enough about dialog, so... :) |
| 11:43 | <erlehmann> | beowulf, i believe you are looking for something completely different than anyone else. <dialog> seems to be a natural conversation |
| 11:43 | <erlehmann> | like, a play |
| 11:43 | <erlehmann> | OH ROMEO |
| 11:43 | <erlehmann> | etc. |
| 11:43 | <beowulf> | exeunt |
| 11:44 | <beowulf> | romeo and juliet in dt/dd would be horrible |
| 11:45 | <Binarytales> | could you not just do <dialog><dt class"joins"><time>12:46</time>Dave</dt>..... or <dialog><time>12:46</time><span class="action">joined</span>Dave</dt> |
| 11:45 | <Binarytales> | there are too many different "actions" to give them a special attribute or tag |
| 11:46 | <erlehmann> | Binarytales, i would break from the dialog and describe the actions in a simple paragraph |
| 11:47 | <erlehmann> | maybe <p> inside <dialog> should be allowed ? |
| 11:48 | <Binarytales> | yeah that would make sense, especially for longer things like stage directions for plays or describing non dialougue souns or actions in transcriptts |
| 11:48 | <Binarytales> | IRC always turns my typing to mush :( |
| 11:49 | <erlehmann> | i'll type a mail to the list |
| 11:50 | <beowulf> | <section item id=dialog>...</section> |
| 11:52 | <Binarytales> | I'm guessing the same rules apply to dialouge that do to dl so that if multiple people say the same thing at the same time then you could use multiple dt for the same dd |
| 11:52 | <hsivonen> | <dialog> is doing great at stopping permathreads... |
| 11:53 | <Binarytales> | oh..... "Zero or more pairs of one dt element followed by one dd element." |
| 11:53 | <Binarytales> | i think that should be the same as a dl |
| 11:53 | <Binarytales> | "Zero or more groups each consisting of one or more dt elements followed by one or more dd elements." |
| 11:54 | <Binarytales> | then if <p> was allowed you should be able to do <dt>Dave</dt><dd>Hmmm....</dd><p>he goes to the window</p><dd>I hadn't though of that</dd> |
| 11:59 | <Binarytales> | I also think that dt's in dialogue should be allowed the datetime attribute |
| 12:05 | <Hixie> | I simply cannot find a full duplex, wifi-enabled, mac-compatible, color printer with a good consumables story and that isn't really slow for under $2000. |
| 12:06 | <jgraham> | Hixie: What is your use case that requires > 20ppm but is used infrequently enough that cold start up time is a major issue? |
| 12:06 | <Hixie> | it doesn't have to be > 20ppm really |
| 12:06 | <Hixie> | the use case is me not tearing my hair out if i want to print something |
| 12:07 | <Hixie> | i expect my hardware to do what i tell it to, when i tell it |
| 12:07 | <Hixie> | not three minutes later |
| 12:07 | <Hixie> | some of these printers have multi-minute boot times |
| 12:07 | <Hixie> | my fricking _computers_ don't take that long to boot |
| 12:07 | <annevk2> | I thought it was not for you? :) |
| 12:08 | <Hixie> | it isn't, but i know who's going to end up doing the drafting for the work that does get printed |
| 12:08 | <Hixie> | :-) |
| 12:09 | <Hixie> | the Brother HL 4070CDW is the only one that matches the criteria on paper for under $2000, but it apparently does a horrible job of consumables |
| 12:09 | <Hixie> | it literally has a page count after which it just claims the toner is empty |
| 12:09 | <Hixie> | rather than actually caring about whether there really is toner left |
| 12:09 | <annevk2> | i'm sure people hacked that :) |
| 12:10 | <Hixie> | i shouldn't need to hack my printer to make it work right |
| 12:10 | <hsivonen> | hmm. I wonder if my Brother laser printer does that. I've never had to change the toner |
| 12:10 | <Dashiva> | What if you drop wifi-enabled? |
| 12:11 | <hsivonen> | isn't hacking a toner cartridge a DMCA violation these days or something? |
| 12:11 | <Hixie> | if i drop wifi-enabled, there's a number of printers, such as the Phaser 8560/DN, that look rather nice |
| 12:11 | <Hixie> | but wifi-enabled without an external dongle is not something i want to drop |
| 12:12 | <Hixie> | the Canon Color imageRUNNER LBP5975 looks pretty nice and has (optional) built-in wifi, but it costs about $3000. |
| 12:12 | <annevk2> | don't you have an Apple router of some sorts with usb-in? |
| 12:12 | annevk2 | thought everyone had an Airport Express these days |
| 12:12 | <Hixie> | the room i'm putting this in has no networking at all |
| 12:12 | <hsivonen> | I learned recently that sometimes it pays to accept external dongles even though they suck |
| 12:13 | <Dashiva> | Still, a dongle seems preferable to $1000 or more in extra price |
| 12:13 | <annevk2> | airport express just requires electricity |
| 12:13 | <Hixie> | (and i honestly do not believe that the airport extreme with a usb port on the back is going to work that well) |
| 12:13 | <hsivonen> | my parents bought a silly expensive TV in order to have a built-in DVR |
| 12:13 | <Hixie> | (e.g. can i print from linux to an airport extreme?) |
| 12:13 | <annevk2> | Hixie, you don't need extreme |
| 12:13 | <jgraham> | It seems like an external router might be worth it for a saving of $1000 |
| 12:13 | <hsivonen> | after hardware and firmware upgrades they returned it |
| 12:13 | <fupp> | where can I find docs on the treewalker in html5lib? |
| 12:13 | <Hixie> | s/airport extreme/airport express/, sorry |
| 12:13 | <hsivonen> | because the firmware upgrade to make parts of it work regressed more essential features |
| 12:13 | <annevk2> | Hixie, I've never tried that, but I think there are ways to make it work for Linux |
| 12:13 | <Dashiva> | Let printers be printers and TVs be TVs :) |
| 12:14 | <Hixie> | annevk2: my willingless to spend time making things work is minimal |
| 12:14 | <Hixie> | annevk2: i expect to plug the printer into a power outlet, and be able to print. |
| 12:14 | <jgraham> | fupp: If there aren't any on the wiki page (http://code.google.com/p/html5lib/ ) they probably don't exist |
| 12:14 | <jgraham> | There should be some there though |
| 12:15 | <jgraham> | Hixie: Ah, I see you really haven't used a printer for 10 years |
| 12:15 | <fupp> | jgraham: there was a small example, but only how to create the treewalker, I didn't find anything about what method it has |
| 12:15 | <jgraham> | fupp: It's an iterator. So you can do for item in tw: print item |
| 12:15 | <Hixie> | jgraham: it seems to work that way at work, with the network printers there |
| 12:15 | <jgraham> | Hixie: I assume google has sysadmins and stuff |
| 12:16 | <Hixie> | well, if the printer comes with a sysadmin in the box that's fine too |
| 12:16 | <fupp> | jgraham: okay, thanks |
| 12:16 | <jgraham> | I guess you need to pay a lot more to get that :) |
| 12:17 | <annevk2> | might be illegal too |
| 12:17 | <fupp> | is there a way to use filters like with the DOM2 TreeWalker? |
| 12:18 | <Lachy_> | Hixie, an ethernet enabled network printer plugged into a port on a wireless router (as opposed to a USB printer plugged into an airport express) that is configured to extend your existing network would probably suit your needs |
| 12:19 | <jgraham> | fupp: There are a few filters provided, you can look at them. You don't need a specific api because you can just use a generator function |
| 12:19 | <Hixie> | Lachy_: yeah, though then i need to add yet another router to the network |
| 12:19 | <jgraham> | function filter(node): yield node is the identity filter |
| 12:19 | <Hixie> | my home network is complicated enough already that i had to draw a network map to figure it out |
| 12:20 | <Lachy_> | Hixie, that's not really much of a problem if it's just set up in bridge mode |
| 12:21 | <Lachy_> | I have 3 routers in my home network |
| 12:21 | Hixie | wonders what the difference is between a "HP Jetdirect ew2400 External Wireless Print Server" and a "HP Wireless G USB Print Server" is |
| 12:45 | <Philip`> | "External Wireless" |
| 12:45 | <Philip`> | Can you get a printer that's internally wireless too? |
| 12:46 | <gsnedders> | Hixie: Correct solution: don't print. |
| 12:46 | <Philip`> | You could get rid of the circuit boards and just have every chip communicate via wifi |
| 12:47 | <Lachy> | Philip`, that depends what is meant by "External Wireless", and what you mean by "internally wireless" |
| 12:47 | <Hixie> | gsnedders: yeah that's my choice too |
| 12:47 | <Lachy> | if you mean, containing no wires, rather than having an internal wifi connection, then no |
| 12:52 | <Hixie> | can an airport express be used as a bridge to connect an _ethernet_ printer to the network? |
| 12:52 | <Hixie> | as opposed to usb? |
| 12:52 | <Hixie> | or is the ethernet port on the express only for uplink to the internet |
| 12:53 | <Hixie> | i'm thinking an HP Color LaserJet CP3525dn is probably my best choice, with a router to get it on the network. |
| 12:53 | jgraham | wonders why Hixie wants a fancy apple thing rather than a common or garden router |
| 12:53 | <Hixie> | well if it works, it's a whole heck of a lot easier to maintain than other routers |
| 12:54 | <annevk2> | Hixie, you should ask your employer, it pointed me to http://forums.macrumors.com/showthread.php?t=92055 |
| 12:54 | <Hixie> | my experience with forums is that you guys are more reliable :-P |
| 12:55 | <annevk2> | we do sometimes get people join this channel with highly off-topic questions of things discussed in the past :) |
| 12:55 | <Philip`> | http://web3d.org/pipermail/x3d-public_web3d.org/2009-September/000341.html ("X3D - HTML 5 minutes Sept. 01, 2009") |
| 12:56 | Philip` | isn't sure what those people actually want to do |
| 12:57 | <Hixie> | i guess i'll plug my laptop into my existing airport express and see if that works |
| 12:57 | <Binarytales> | what about ethernet over powerlines. my brother uses it for his xbox and it works like a charm, the adapter are pretty inexpesive too, a lot cheaper than an airport |
| 12:58 | <annevk2> | Philip`, literally reading that it seems they want to obsolete <embed> and give X3D the same kind of support as SVG |
| 12:59 | <Hixie> | Binarytales: dunno if that'll work for me, our power setup is ancient and not at all something i'd trust with data |
| 12:59 | <Philip`> | annevk2: As far as I'm aware they only care about XHTML, not text/html |
| 13:00 | <zcorpan> | Hixie: should <video> use MIMESNIFF rules? |
| 13:00 | <Binarytales> | we have it working on wiring that was done the 60's and its stable enough for xbox live |
| 13:00 | <Hixie> | zcorpan: not currently |
| 13:00 | <Philip`> | (or maybe they don't realise the distinction) |
| 13:00 | <Hixie> | Binarytales: ah, interesting. what products should i be looking at? maybe it's worth a try |
| 13:00 | <Philip`> | Does Ethernet over powerlines work during powercuts? |
| 13:01 | <Hixie> | my wifi network won't work during powercuts |
| 13:01 | <Hixie> | so that point is moot |
| 13:01 | jgraham | has heard that the reliability of ethernet over powerlines is widely variable depending on the wiring of your house and can have unexpected interference if you try to e.g. make toast |
| 13:02 | <Philip`> | You can solve that by switching to a battery-powered toaster |
| 13:02 | <Hixie> | ok well i'll look into the networking part of this tomorrow |
| 13:02 | <Hixie> | i must sleep now |
| 13:02 | <Hixie> | thanks for the help |
| 13:07 | <jgraham> | Does WebIDL have anything to say about what should happen if I do something like __lookupGetter__ or __defineSetter__ on a DOM object? |
| 13:07 | <jgraham> | heycam: ^ |
| 13:08 | jgraham | is hoping someone more familiar than him with WebIDL will know since the spec is quite dense and it is possible he has missed something |
| 13:20 | <hsivonen> | why are the X3D folks keen on getting rid of <embed>? |
| 13:20 | <heycam> | jgraham, no it doesn't |
| 13:20 | <heycam> | i should probably get around to making webidl relevant for ES5 kinda things like that |
| 13:23 | heycam | heads to bed |
| 13:23 | <Philip`> | hsivonen: Probably because of the reasons in the bottom of http://lists.w3.org/Archives/Public/public-html/2009Aug/1220.html |
| 13:24 | <hsivonen> | I don't see why it would be productive to ask Flash embedding snippet generators to change |
| 13:24 | <hsivonen> | but then, I don't see why it's productive to ask Java applet embedding snippet generators to change, either |
| 13:26 | <Philip`> | (My assumption that those are the relevant reasons is because they come from an X3D person, rather than because they're necessarily good reasons) |
| 13:28 | <Lachy> | Is <object> even capable of doing everything needed to embed an applet, that <applet> can do? |
| 13:29 | <hsivonen> | Lachy: I'm not sure, but HTML5-compatible <object> for Java has near-non-existent documentation while <applet> has plenty |
| 13:29 | <hsivonen> | http://webtrendmap.com/craigmod/161/ is such a pain to debug |
| 13:43 | <hsivonen> | so far I've figured that the jquery crasher is due to OnLocationChange running differently |
| 13:43 | annevk3 | wonders why Sam is playing games regarding <keygen> |
| 13:43 | <Creap> | How does 'required' work on checkboxes? |
| 13:45 | <Creap> | Is it required to be changed, or to be checked |
| 13:45 | <Creap> | oh, nevermind, I missed a note |
| 13:45 | <Creap> | "If the element is required and its checkedness is false, then the element is suffering from being missing." |
| 13:47 | <Lachy> | hsivonen, yeah, I know I argued to have <applet> added to HTML5 as conforming once. I can't remember the reason Hixie rejected it |
| 13:50 | <Lachy> | we should make keygen non-conforming, and just keep the implementation requirements in the spec for now |
| 13:51 | Philip` | guesses making <keygen> optional would make Microsoft happy, since then they wouldn't have to intentionally violate the spec, and it would still be documented for everyone else who wants to bother implementing it |
| 13:51 | <Lachy> | given that it's a really badly designed feature, we should do as much as possible to discourage its use, rather than encourage it by making it conforming |
| 13:52 | <Lachy> | Philip`, I didn't say we should make it optional. Just make it a document conformance error to use it. |
| 13:52 | <hsivonen> | Lachy: the reason basically boils down to <applet> being specific to Java while <embed> isn't specific to Flash in theory |
| 13:53 | <Lachy> | hsivonen, that sounds like an argument from theoretical purity, in spite of practicality |
| 14:00 | <hsivonen> | Hixie: ^ |
| 14:28 | <markhuot> | Wow, I have to say that HTML5 worried me with all the element confusion. But now that I've found custom data attributes I think I may be in love: http://www.whatwg.org/specs/web-apps/current-work/#embedding-custom-non-visible-data |
| 14:33 | <miketaylr> | markhuot: for reals. |
| 14:35 | <hsivonen> | markhuot: what element confusion are you referring to? <footer>? |
| 14:40 | <markhuot> | hsivonen: yea, FOOTER and ASIDE really. |
| 14:41 | <markhuot> | Actually, I think TabAtkins was going to make a post about it the other day. Does anyone know where that would have been posted, if it was? |
| 14:41 | <TabAtkins> | Yo. |
| 14:41 | <TabAtkins> | I sent it in the thread I'm currently responding to, I think. |
| 14:41 | TabAtkins | scans... |
| 14:42 | <TabAtkins> | "Implementor feedback on new elements in HTML5". 16 hours ago. |
| 14:43 | <markhuot> | Hey there TabAtkins. Ah, thanks. I've been reading the archives up until now, I guess I should bite the bullet and subscribe though so I'm not a few days behind all the time. |
| 14:43 | <Philip`> | You could just increase your polling frequency on the archives |
| 14:43 | <TabAtkins> | 250ms should be sufficient. |
| 14:44 | <markhuot> | :) Now that sounds like just the ticket. |
| 14:44 | <Philip`> | Opera is good for that since you can bind the archives to a speed-dial button, and whenever you're bored or distracted (i.e. every five minutes, at least when I did this) you can compulsively hit the key to view the archives for any nice blue unread links |
| 14:46 | <gsnedders> | (So be careful) |
| 14:47 | <TabAtkins> | Since Hixie explained it, though, I'm cool with <aside>. I'm proposing an amendment to the spec text for it right now for the list. <footer> is still no good as written. |
| 14:47 | <markhuot> | Ah, I'm going back and reading Hixie's explanation of ASIDE now. |
| 14:48 | <TabAtkins> | Yeah, the generalization of "tangential to content" to "tangential to page" was not one I was comfortable making as an informed author. |
| 14:48 | <TabAtkins> | Which is ironic, since it's precisely the reasoning I used at first when I tried to use <aside> as a sidebar. |
| 14:51 | gsnedders | sighs at h2g2 |
| 14:51 | <markhuot> | It can be confusing though. However, reading through Hixie's explanation seems to clear things up a bit… |
| 14:52 | <miketaylr> | markhuot: can you post a link to that? i'd like to read it as well |
| 14:53 | <Philip`> | gsnedders: The book, or the web site? |
| 14:54 | <gsnedders> | Philip`: The web site |
| 14:55 | <Lachy> | TabAtkins, you should just give in and use aside for a sidebar as it was initially designed |
| 14:56 | <TabAtkins> | Lachy: I have. ^_^ Which is why I'm now proposing an amendment to the spec text, to make that clear again. |
| 14:56 | <gsnedders> | http://www.bbc.co.uk/dna/h2g2/A184060 |
| 14:56 | <Lachy> | TabAtkins, have you sent the proposal, or still writing it? |
| 14:57 | <TabAtkins> | Writing it now. |
| 14:57 | <Philip`> | h2g2 is like a cross between Wikipedia and Uncyclopedia |
| 14:59 | <TabAtkins> | It reminds me of everything2 (IIRC the name). |
| 14:59 | <gsnedders> | "Possibly the best place to meet someone [for a first date] is a record shop - you can always browse the shelves while you're waiting, and if you get stood up you can at least pick up a few bargains in the process." |
| 15:00 | <Lachy> | how does anyone get h2g2 as an abbreviation for "The Hitchhiker's Guide to the Galaxy"? - http://www.bbc.co.uk/dna/h2g2/dontpanic-tour |
| 15:00 | <TabAtkins> | HitchHikers Guide to the Galaxy |
| 15:00 | <TabAtkins> | Clearly inferior as an abbreviation, but shrug. |
| 15:00 | <gsnedders> | (note the two words beginning to t, too) |
| 15:00 | <Lachy> | oh. That's the most obscure abbreviation ever |
| 15:00 | <Lachy> | and Hitchhiker's is written as one word |
| 15:00 | <TabAtkins> | Yeah, took me forever to realize what it meant when the movie was coming out. |
| 15:01 | <Lachy> | I don't remember that abbr being used for the movie |
| 15:16 | <TabAtkins> | Hrm. I doubt it's possible for a Location-header redirect to take advantage of the <base> url... |
| 15:16 | <Lachy> | With all the discussion about how temperature doesn't really have an upper bound (in the <meter> thread), someone should inform thermometer manufacturers that they're doing things wrongly by limiting their gauges between, e.g. -20 and 60˚C (for outdoor weather thermometers) |
| 15:17 | <TabAtkins> | Already hit that. ^_^ |
| 15:17 | <TabAtkins> | Anyway, you eventually run out of entropy - a given system *does* technically have an upper bound. |
| 15:18 | <TabAtkins> | Albeit in high exponentials. |
| 15:19 | <Lachy> | TabAtkins, that depends if you accept the hypothesis of their being an Absolute Hot, at the opposite end of the scale from Absolute Zero |
| 15:19 | <TabAtkins> | No, it's a theorem based on thermodynamics. |
| 15:19 | <Philip`> | What if you have a meter showing the temperature of the universe, updating dynamically with t moving towards 0? |
| 15:19 | <TabAtkins> | Where temperature is correlated with entropy, and a given system has a maximum level of entropy. |
| 15:20 | <TabAtkins> | Philip` <progress toward=heat-death>? |
| 15:20 | <jcranmer> | I thought temperature was enthalpy, not entropy |
| 15:20 | <TabAtkins> | jcranmer: Different formulation of entropy. |
| 15:20 | <jcranmer> | t = time or temperature, Philip` ? |
| 15:20 | <TabAtkins> | temperature is T, not t. |
| 15:20 | <Philip`> | t = time |
| 15:20 | <Lachy> | I struggle with the concept of entropy already. I don't even know what enthalpy is. |
| 15:20 | <Philip`> | (Sorry, I assumed that was obvious :-p ) |
| 15:20 | <jcranmer> | at the big bang, the temperature was.. er.. |
| 15:20 | <Philip`> | so heat-death is the wrong end of the universe |
| 15:21 | <TabAtkins> | Buh, sorry. Missed the t->0 bit. |
| 15:24 | <TabAtkins> | Ah, good. Turns out I store the <base href> in the db with the site info anyway. |
| 15:24 | <Lachy> | so at t = (0 + 1/infinity), at the instant the universe began expanding, all the energy of the universe was condenced into such a small, hot region of plasma, that would be the hottest possible temperature in this universe. Is that right? |
| 15:24 | <TabAtkins> | Given an appropriately rigorous definition of an infinitesimal moment from the singularity, yeah. |
| 15:25 | <Philip`> | Given the assumption that physics works at that time too |
| 15:25 | <TabAtkins> | I think we can't reason about it if we don't assume physics still works. |
| 15:25 | <Philip`> | (which it doesn't, as far as I'm aware) |
| 15:25 | <Philip`> | s/physics/known models of physics/ |
| 15:25 | <TabAtkins> | *At* the singularity we lose it, but not *just afeter*. |
| 15:25 | <Lachy> | so is that the same as the theoretical Absolute Hot? Or if some hypothetical universe began with more engergy than this one, would it be hotter? |
| 15:26 | <TabAtkins> | Some stuff just works weird at those energy levels. |
| 15:26 | <TabAtkins> | Lachy: under that definition, Absolute Hot is universe-specific. |
| 15:26 | <TabAtkins> | Under the definition I was referring to before (the weird thermodynamic one) you can actually achieve Absolute Hot in the lab, and then wrap right back around to negative temperatures. |
| 15:27 | <TabAtkins> | That is to say, you can overflow temperature itself. ^_^ |
| 15:27 | <Lachy> | Philip`, I'm using a hypothetical model of physics in which the issues of general relativity and quantum mechanics have been resolved into a unified theory of everything. |
| 15:28 | <Philip`> | How are you defining the notion of temperature in that model? |
| 15:28 | <TabAtkins> | http://en.wikipedia.org/wiki/Negative_temperature |
| 15:28 | <TabAtkins> | Like that. |
| 15:31 | <Lachy> | Philip`, if I knew that, my model wouldn't be hypothetical. |
| 15:32 | <TabAtkins> | Philip` something like energy density is probably a good idea there. |
| 15:32 | <Philip`> | Lachy: If you don't know what temperature is, it's hard to work out whether there's a maximum value for it |
| 15:32 | TabAtkins | notes that this becomes confused with the gauge changes, though... |
| 16:04 | <TabAtkins> | All right, just sent proposal for <aside>. After thinking about it, I don't think the text itself really needs to change, so I suggested an additional example that makes it clear that website sidebars are appropriate uses of the element. |
| 16:21 | <cardona507> | forgive me if this is phrased wrong- are touch gestures supported in html 5? |
| 16:21 | <cardona507> | multi-touch |
| 16:23 | <inimino> | cardona507: that would be more a feature of browsers, not of HTML |
| 16:23 | <cardona507> | wouldn't the spec be the place to clearly define it so that the browsers implement it uniformly - or is that wishful thinking? |
| 16:23 | <markhuot> | inimino: not necessarily, there would probably need to be events for "pinch" (as an example) |
| 16:26 | <Philip`> | Sounds like more of a Web Apps WG thing |
| 16:56 | <TabAtkins> | Breadcrumbs: <nav> or not? |
| 16:57 | <beowulf> | <pwd>...</pwd> |
| 16:57 | <TabAtkins> | Ah, of course. |
| 17:24 | <markhuot> | beowulf, was that serious? I don't see any reference to a PWD element… |
| 17:24 | <TabAtkins> | Nah, that was a joke. ^_^ |
| 17:25 | <markhuot> | :) Darn, it made so much sense though ;-) |
| 17:25 | <TabAtkins> | pwd on a linux box lists the current path |
| 17:25 | <TabAtkins> | Hehe. |
| 17:25 | <markhuot> | Yup, yup. It made perfect sense to me. I'd love a PWD just for bread crumbs and the like. |
| 17:26 | <TabAtkins> | Really, though, breadcrumbs are just a nav. But are they primary enough to be <nav> is the question. |
| 17:26 | <TabAtkins> | I'm gonna lean toward yes. |
| 17:26 | <TabAtkins> | Because otherwise I'm splitting hairs way too finely for my taste. |
| 17:27 | <markhuot> | Hum, I'd lead towards no, only because I wouldn't want duplicate NAV items point to the About page (for example). |
| 17:27 | <markhuot> | But that's a personal preference thing I think. Not the fault of the spec's definition of NAV. |
| 17:30 | <markhuot> | Philip`, to go way way back to what you said about the Web Apps WG, I was simply saying that if the spec includes references to `onclick` then it may need a reference to `pinch` or `tofingertap`, etc… |
| 17:34 | <Binarytales> | surely pinch could be discovered by polling for a change in the size of something (as it's pretty much always used to scale) and fingertaps or covered by onclick and onmousedown? |
| 17:42 | <markhuot> | Hum, but how would you know if someone pressed with one finger or two on a link or button with onclick? |
| 17:42 | <markhuot> | Pinch, could be discovered with polling, but then couldn't `keyup` as well? I'd say as a measure of convenience `onpinch` would be as helpful as `onkeyup` |
| 17:44 | <Binarytales> | I see what your saying |
| 17:51 | <Binarytales> | it would be cool if onpinch were to return deltas for the amount of pinch or pehaps an array of onmousedown events of something (I've not done a lot of javascript stuff so that might not make sense) |
| 19:24 | <rubys> | tantek: http://intertwingly.net/blog/2009/09/02/Polyglot-Validation |
| 19:49 | <tantek> | hi rubys - reading now |
| 19:55 | <rubys> | hi tantek, let me know what you think |
| 19:56 | <TabAtkins> | tantek: got the <cvs> example working in ie, but I"m gonna have to scrap the implementation in any case to account for separator characters appearing in quoted fields. I'll move to a character-by-character parser instead. |
| 19:56 | <tantek> | rubys - more details also added to the sf guide: http://www.zeldman.com/superfriends/guide/#validation |
| 19:56 | <tantek> | TabAtkins, your implementation is still an excellent "proof of concept" |
| 19:57 | <tantek> | for now, it's worth publishing and explicitly noting the limitations (e.g. characters appearing in quoted fields) |
| 19:57 | <TabAtkins> | Yeah, it works perfectly as I want it now if you can trust the separator character perfectly. |
| 19:57 | <TabAtkins> | I got it to move all of the <cvs> attributes to the generated <table> too. |
| 19:57 | <TabAtkins> | I need someone to help me translate it from jQuery to DOM, though. |
| 19:58 | <tantek> | rubys - I disagree that XHTML 1.0 named entities shouldn't be allowed. |
| 19:58 | <rubys> | tantek, yes that "more" details, but I have experience with developing a validator... and that's why I'm insisting on concrete test cases. |
| 19:58 | <tantek> | requesting test cases is reasonable |
| 19:58 | <TabAtkins> | In fact, someone (possibly me) needs to make a tutorial - "Turning your jQuery into normal javascript". |
| 19:59 | <tantek> | heh - indeed |
| 19:59 | <tantek> | again, for a proof of concept, jQuery is fine |
| 19:59 | <tantek> | which is all we need for a spec proposal per se |
| 19:59 | <tantek> | it shows implementability, utility, etc. |
| 19:59 | <TabAtkins> | Yeah. |
| 19:59 | <rubys> | tantek: cool. Produce a few this week, and I will try to see if I can implement some of them next week, and get Mike to deploy the results publicly for you and everybody else to bang on. |
| 20:00 | TabAtkins | will be back in a few, needs to hit up Sonic before returning to work. |
| 20:01 | <tantek> | rubys - I'll try to add to the "etc." and answer Henri's questions first - then the next logical step would be to produce a test case for each bullet point in http://www.zeldman.com/superfriends/guide/#validation |
| 20:02 | <gsnedders> | If we want to do that, do we want to check if the page is valid XHTML as well as HTML? |
| 20:02 | <tantek> | (and perhaps even link to the test cases from the bullet points) |
| 20:02 | <gsnedders> | Do we want to check whether it parses to the same tree in both XHTML in HTML? |
| 20:02 | <gsnedders> | *as |
| 20:02 | <gsnedders> | *and |
| 20:02 | <tantek> | gsnedders - that's a reasonable add |
| 20:02 | <rubys> | gsnedders: see the comments on my blog post. There may be differences that don't matter. |
| 20:03 | <tantek> | since tree differences would result in DOM differences, and may result in CSS styling differences, since CSS rules apply to the tree |
| 20:03 | <rubys> | Henri's point about <pre> followed by new-line is a valid one. |
| 20:03 | <tantek> | rubys - so far, for each difference, I've been able to find a case where it could cause an unintended runtime error |
| 20:03 | <Philip`> | (<textarea> too) |
| 20:03 | <gsnedders> | I guess it means making all entities apart from the four XML ones errors, as they aren't allowed in XHTML |
| 20:03 | <gsnedders> | and <listings> |
| 20:03 | <gsnedders> | or listing |
| 20:03 | <gsnedders> | or whatever it is |
| 20:03 | <tantek> | gsnedders - no - XHTML 1.0 includes named entities |
| 20:03 | <gsnedders> | :P |
| 20:03 | <Philip`> | gsnedders: Nobody cares about obsolete elements :-p |
| 20:03 | <tantek> | therefore so should XHTML syntax |
| 20:04 | <gsnedders> | tantek: Aren't we checking HTML 5 and XHTML 5, though? |
| 20:04 | <gsnedders> | tantek: Or are we doing HTML 4.01 and XHTML 1.0, which makes things like <img> impossible to use |
| 20:04 | <tantek> | gsnedders, there is no such thing as "HTML 5", there is only HTML5. there is no such things as "XHTML 5" there is only "XHTML syntax of HTML5". |
| 20:04 | <tantek> | gsnedders - read: http://www.zeldman.com/superfriends/guide/#validation |
| 20:05 | <gsnedders> | tantek: I have. |
| 20:05 | <tantek> | that answers your question |
| 20:05 | <gsnedders> | It doesn't. |
| 20:05 | <tantek> | read it again |
| 20:05 | <Philip`> | If you want the same tree in HTML and XHTML, you couldn't even write "<ul><li>item 1</li> <li>item 2</li><ul>" |
| 20:05 | <Philip`> | Wait, I'm probably being stupid |
| 20:06 | <Philip`> | That's just in IE, not HTML5, I think |
| 20:06 | <Philip`> | Please ignore me |
| 20:06 | <tantek> | it's ok Philip`, this is IRC, we all expect to say things before we've fully thought them through :) |
| 20:07 | <Philip`> | Am I still being stupid if I think you can't even write "<!DOCTYPE html><html>...all the normal body stuff...</html> " ? |
| 20:07 | <gsnedders> | tantek: My understanding of that is we want to check that a document is both valid HTML and the corresponding version of XHTML, which if we want to check parse trees are the same is rather useless for HTML 4.01 as <img /> is parsed differently. |
| 20:07 | <gsnedders> | Philip`: You could, why couldn't you? |
| 20:08 | <tantek> | gsnedders - false. they are allowed in XHTML 1.0. |
| 20:08 | <tantek> | and in practice, no, <img /> is not parsed differently |
| 20:08 | <gsnedders> | tantek: How is that false? Parsed per HTML 4.01 you get an img element followed by ">", and XHTML you get a single img element. |
| 20:08 | <gsnedders> | tantek: Sure, but we're checking against the spec, and if we're dealing with HTML 4.01, then that is true. |
| 20:09 | <tantek> | gsnedders - your HTML 4.01 spec literalism is a waste of time. |
| 20:09 | <Philip`> | gsnedders: Because in HTML5 the whitespace goes inside the body, in XHTML it doesn't, so the trees are different |
| 20:09 | <gsnedders> | tantek: Then educate people to not use HTML 4.01 if they want their XML-isms |
| 20:10 | <tantek> | gsnedders - like I said - reread http://www.zeldman.com/superfriends/guide/#validation to understand the purpose |
| 20:10 | <gsnedders> | tantek: I have. I am asking questions to try and understand the purpose. |
| 20:11 | <gsnedders> | If you want to check coding standards exactly per XHTML, these are all valid questions |
| 20:11 | <tantek> | no - the HTML4.01 shorttag net crap questions is just a waste of time - you're asking theoretical questions that have zero impact in practice - therefore you are wasting time. |
| 20:12 | <gsnedders> | So why don't we just validate against what creates an identical parse tree in all browsers, and ignore all specs? |
| 20:13 | <gsnedders> | Making <u> throw an error is theoretical and has zero impact in practice. |
| 20:13 | <tantek> | gsnedders - reductio ad absurdum arguments are not useful either. |
| 20:13 | <tantek> | ("ignore all specs") |
| 20:14 | Philip` | presumes the aim is to find the underlying principles behind the specific suggestions, so that it's possible to tell what other suggestions would fit in |
| 20:14 | <gsnedders> | So we should be validating against the parts of HTML 4.01 that are relevant in the real world? |
| 20:14 | <tantek> | gsnedders - next homework assignment: read http://en.wikipedia.org/wiki/List_of_fallacies |
| 20:15 | <tantek> | gsnedders, no, you should be ignoring any nitpicky details of HTML4.01 which have never been implemented in practice. |
| 20:15 | <hober> | I didn't even think we were talking about validating HTML 4.01 at all, but instead validating documents which purport to be simultaneously XHTML5 and HTML5 |
| 20:16 | <tantek> | and in fact have been *interoperably* implemented in other ways |
| 20:20 | <fupp> | how do I parse a webpage with iso-8859-1 encoding with html5lib? I tried the stuff in the docs but it doesn't work |
| 20:24 | <tantek> | rubys - really appreciate your volunteering to help with the validation stuff |
| 20:25 | <rubys> | and if you scroll back, you can see why I'm limiting myself to vetted test cases :-) |
| 20:26 | <rubys> | I don't want to get sucked into those arguments. |
| 20:31 | <gsnedders> | hober: But the "Super Friends" document explicitly refers to XHTML 1.0 |
| 20:32 | <gsnedders> | tantek: Also, FWIW, according to HTML 5 section 1.7, there is both HTML5 and XHTML5. |
| 20:33 | <hober> | I think you're misreading that paragraph (of the sf document), gsnedders |
| 20:33 | <hober> | they're not saying "We want to validate a document as simultaneously both HTML5 and XHTML 1.0" |
| 20:34 | <gsnedders> | Then I wish someone would tell me _how_ I'm meant to be reading that document instead of just telling me to read it again. |
| 20:34 | <hober> | they're saying "in the past, we could validate documents-served-as-text/html as XHTML 1.0; in the future, we'd like to be able to validate documents-served-as-text/html as XHTML5" |
| 20:34 | <hober> | tantek: please correct me if my interpretation is wrong |
| 20:34 | <gsnedders> | But you can already do that, just change the parser to XML. |
| 20:35 | <hober> | gsnedders: indeed. |
| 20:35 | <gsnedders> | Which is why are far as I can tell it's about checking a document is both valid HTML and XHTML |
| 20:35 | <gsnedders> | But apparently we're meant to ignore certain parts of the spec we're validating against |
| 20:37 | <gsnedders> | I just want to know quite what this dual-mode validation is meant to be. |
| 20:39 | <TabAtkins> | Man, I need a corpus of representative CSVs. How are quote characters typically quoted within a quoted field? Are the doubled? Slashed? ?_? |
| 20:40 | <gsnedders> | It varies by producer massively |
| 20:40 | <TabAtkins> | That's what I thought. Damn legacy formats. |
| 20:40 | <gsnedders> | And most variations are incompatible with each other :P |
| 20:41 | <TabAtkins> | ;_; |
| 20:41 | <hober> | TabAtkins: there's an RFC |
| 20:41 | <TabAtkins> | hober: Any idea if the RFC corresponds to reality, though? |
| 20:41 | <hober> | RFC 4180 |
| 20:42 | <hober> | it does IIRC |
| 20:44 | <TabAtkins> | Yeah, that describes the doubling-behavior that I think is pretty common. But I'm not sure if \ing them is prevalent enough to make me care about it too. |
| 20:48 | <tantek> | TabAtkins - see http://www.data.gov/ for a ton of CSVs :) |
| 20:49 | <Philip`> | Probably not a good way to see a wide range of formats |
| 20:50 | <tantek> | Philip` - you might be surprised. different government agencies do their own thing. |
| 20:50 | <tantek> | TabAtkins - also: http://datasf.org/ |
| 20:51 | <TabAtkins> | All right, cool. |
| 20:52 | <tantek> | also, you might find this useful: http://www.creativyst.com/Doc/Articles/CSV/CSV01.htm |
| 20:53 | <tantek> | which was linked from this CSV file editor tool: http://csved.sjfrancke.nl/index.html |
| 20:53 | <TabAtkins> | Yeah, the ability of fields to contain linebreaks is another reason why I need to move to a full parser, rather than a simple regexp-based implementation. |
| 20:54 | <tantek> | which itself was linked from a page of "open science resources" - CSV may be the most used format in open science |
| 20:54 | <TabAtkins> | Yeah, my wife's a biologist by degree, and has done intern work in labs. CSVs are *everywhere*. |
| 20:55 | <TabAtkins> | http://www.xanthir.com/etc/csv.html contains the current working version. As long as you don't mess around with quotes or anything, it works like a charm in every browser I've tried. |
| 20:56 | <tantek> | TabAtkins - I find it kind of awesome that someone with the first name "Tab" is implementing <csv> element support - just saying :) |
| 20:56 | <TabAtkins> | And I recommend always enclosing <csv> in <pre>, just like you do with <code> - it prevents CSS accidents (or non-CSS UAs) from making the table unintelligible, and the js parser won't even *work* in IE without whitespace protection. |
| 20:57 | TabAtkins | sighs. ^^; |
| 20:57 | <tantek> | yes - authoring recommenations - good point |
| 20:58 | <hober> | hmm. you could make your code work with <pre><code class="csv">...</code></pre> as well |
| 21:00 | <TabAtkins> | Well, that's blessing a class, which works individually, but not if you're trying to provide a migration path to native support. |
| 21:00 | <TabAtkins> | <pre><code csv>...</code></pre> is a possibility, but I dunno if that's a good semantic. |
| 21:01 | <TabAtkins> | Plus, right now I've got two attributes on <csv>, and they wouldn't really make sense on <code>. |
| 21:01 | <hober> | I'm not suggesting that the spec bless a class; I'm suggesting that your hack could use that for people deploying to exisitng UAs/versions of HTML |
| 21:01 | <tantek> | csv is data not code |
| 21:01 | <TabAtkins> | Yeah, but <csv> works fine in existing UAs. |
| 21:01 | <tantek> | I would call that semantic abuse |
| 21:01 | <TabAtkins> | Especially if wrapped in <pre>. |
| 21:01 | <tantek> | (using <code> for csv that is) |
| 21:02 | <tantek> | TabAtkins - agree |
| 21:02 | <tantek> | agreed |
| 21:02 | <hober> | it works in IE without a document.createElement() hack? |
| 21:02 | <TabAtkins> | Yes. And if you're using the js-based csv-to-table shim that I'm developing, you automatically have the ability to include document.createElement('csv'). |
| 21:03 | <TabAtkins> | Without the hack (and without the js upward-compat), you just have the CSV data being displayed a preformatted plain text. |
| 21:03 | <hober> | re: <code> semantics, agreed; so put the class="" on <pre> :) |
| 21:04 | <hober> | *nod* a very sensible fallback |
| 21:04 | <TabAtkins> | Yeah, it works well. Yay <pre>! |
| 21:05 | <TabAtkins> | And yeah, you'll probably put class="csv" on your <pre> anyway, just like you currently do <pre .code><code>... |
| 21:05 | <TabAtkins> | Gives you a good styling hook. |
| 21:06 | <tantek> | also, here is source of *science* CSV files |
| 21:06 | <tantek> | http://www.google.com/search?q=science+filetype%3Acsv |
| 21:06 | <tantek> | :D |
| 21:06 | <hober> | heh |
| 21:15 | <TabAtkins> | Hmm, looks like I only need one-character look-ahead to implement this. |
| 21:23 | <tantek> | rubys,hsivonen - why the attitude about "how hard it really is" and "isn't really worth it"? Do programmers try to convince each other that fixing code to pass various lint tools "aren't worth it"? Or that running PHP on dev sandboxes with maximum level of warnings and treat warnings as errors is "not worth it"? |
| 21:25 | <rubys> | tantek: I don't think we will have any problems. |
| 21:25 | <rubys> | tantek: we can start with quoted attributes and matched tags. |
| 21:25 | <rubys> | tantek: we can add more and more as you see fit. |
| 21:26 | <tantek> | rubys - writing more and more up as we speak. |
| 21:26 | <rubys> | it may turn out that there are errors that are hard to detect and nobody cares about... that's fine with me. |
| 21:26 | <tantek> | rubys - agreed. |
| 21:27 | <tantek> | every additional type of error detected by a validator is a net win. |
| 21:27 | <tantek> | regardless of whether we reach some theoretical 100% or something |
| 21:27 | <rubys> | +1 |
| 21:27 | <tantek> | hence why I'm dismissive of theoretical questions/requests like the SHORTTAG NET crap. |
| 21:27 | <rubys> | hence why I don't even participate in such discussions. |
| 21:28 | <tantek> | understandable. I suppose I still believe folks *want* to be practically productive, and thus offering an explanation as to why such discussions are not productive seems reasonable. |
| 21:29 | <rubys> | remember: my blog is 100% valid XHTML5 and 100% valid HTML5. (with one minor exception at the moment, to make a point about SVG) |
| 21:29 | <tantek> | rubys you mean it's both valid XHTML syntax and HTML syntax of HTML5? ;) |
| 21:29 | tantek | dislikes the term XHTML5 - it is misleading. |
| 21:29 | <rubys> | sure, whatever the PC way to say that these days is. |
| 21:30 | <tantek> | rubys, not trying to be PC, just *precise* in order to reduce confusion. |
| 21:30 | <rubys> | I doubt "HTML syntax of HTML5" will catch on. |
| 21:31 | <tantek> | rubys, sure, I think by default that's what people will mean by "HTML5" |
| 21:31 | <tantek> | and hence will only need to make that distinction when also talking about the "XHTML syntax" |
| 21:31 | <Dashiva> | Considering HTML5 closes the XHTML-as-text/html hole, if anything there will be even less XHTML going forward |
| 21:31 | <rubys> | so it will end up in a situation where "guy" can be gender neutral or male. |
| 21:32 | <tantek> | rubys - more like "they" can mean a singular non-gender reference |
| 21:32 | <tantek> | non-gender-specific |
| 21:32 | <tantek> | Dashiva there will be less application/xhtml+xml sure but that mimetype was already dying. |
| 21:32 | <rubys> | no, people will say HTML5, and mean it to mean a specific syntax or both syntaxes. And when it means one (the normal case) it will mean a specific one. |
| 21:33 | <rubys> | kinda like "guy" |
| 21:33 | <Dashiva> | tantek: I meant that fewer people will be saying they make XHTML. |
| 21:34 | <tantek> | Dashiva - sure, there will be less marketing of XHTML |
| 21:34 | <rubys> | Dashiva: officially URLs no longer exist, per the specs, but the term lives on (and even is getting resurrected in HTML5) |
| 21:34 | tantek | doesn't understand the URL kerfluffle. |
| 21:35 | <Dashiva> | rubys: Indeed, but their doctype won't say xhtml anymore. The label is fading. :) |
| 21:36 | <rubys> | the label will outlive the doctype |
| 21:38 | <Binarytales> | Dashiva - you don't even need to doctype when using the xhtml syntax |
| 21:38 | <Dashiva> | Binarytales: We're talking about XHTML as text/html |
| 21:38 | <Binarytales> | oh right, sorry |
| 21:39 | <rubys> | Dashiva: correction: you are. |
| 21:39 | <Dashiva> | But yes, that's also kind of amusing. A document is more likely to say "I'm XHTML" at the top if it isn't. |
| 21:40 | <rubys> | A document is also likely to say "strict" at the top but not be. |
| 21:42 | tantek | gets the big red comment posting warning box on intertwingly.net. |
| 21:42 | <rubys> | ignore it |
| 21:43 | <rubys> | it is just there to scare away the spammers |
| 21:43 | tantek | goes ahead and submits comment anyway and identifies self via OpenID - sweet. |
| 21:44 | <rubys> | I have no moderation, just big scary signs. |
| 21:45 | <rubys> | tantek: if you post again tomorrow (on any post) or within 90 days, you shouldn't see any scary signs. |
| 21:46 | <rubys> | I've got a list of "known" commenters (both by IP and URI) that updates a few times a day. |
| 21:58 | <KevinMarks> | a lot of data.goc CSV's are actually sensibly tab-separated |
| 21:59 | <TabAtkins> | I'm already supporting tab-separated stuff fine. |
| 22:02 | <dpranke> | TabAtkins: what "rendering" section are you referring to? Someplace other than 4.10.10? |
| 22:03 | <TabAtkins> | dpranke: 11.4.15 |
| 22:04 | <dpranke> | TabAtkins: ah. thanks! |
| 22:04 | <TabAtkins> | no proble! |
| 22:04 | <TabAtkins> | ... s/proble/problem/ |
| 22:06 | <gsnedders> | Since when did Opera support typing "/." in the address bar to get to /.? |
| 22:07 | <TabAtkins> | Haha, awesome. |
| 22:07 | <TabAtkins> | 10b2, at least. ^_^ |
| 22:09 | <tantek> | they might as well add support for typing "@username" to navigate to http://twitter.com/username |
| 22:13 | <Philip`> | gsnedders: It's done that since forever |
| 22:14 | <Philip`> | or at least since 9.0 |
| 22:14 | <gsnedders> | Philip`: Yeah, I know it predates 9.5 :P |
| 22:25 | <tantek> | rubys, hsivonen - I've followed up on your comment re: validation - hope this helps: http://www.zeldman.com/2009/08/31/loving-html5/#comment-48070 |
| 22:28 | <rubys> | tantek: you've switched positions on XHTML 1.0 entitites? |
| 22:28 | <tantek> | rubys - not switched, moved |
| 22:29 | <rubys> | cool. Note that jacques distler has nominated two tests: http://intertwingly.net/blog/2009/09/02/Polyglot-Validation#c1251926776 |
| 22:30 | <tantek> | rubys, part of the use case of XHTML for me has always been enabling XML tool chain uses - see: http://tantek.com/log/2003/01.html#L20030114t1345 |
| 22:31 | tantek | feels a bit old citing 6+ year old blog posts. |
| 22:31 | <rubys> | that's one that zeldman may disagree with, but I'll leave that up to you two. To me, it simply is an if-check. |
| 22:32 | <tantek> | rubys - hence why I said non-XML XHTML 1.0 named entities should be a *warning*, not an error |
| 22:32 | <rubys> | [my blog and my planet either use numeric entity references or pure utf-8] |
| 22:33 | <rubys> | initially, these will all be warnings... we can make fine grained distinctions later. |
| 22:33 | <tantek> | As my intuition says that Zeldman and other web designers will want to continue using named entities and still "validate" |
| 22:33 | <tantek> | rubys - the ones that will more likely cause runtime errors I'm advocating as "errors" if the "check XHTML syntax" checkbox is checked. |
| 22:33 | <tantek> | e.g. missing tbody would be an error |
| 22:34 | <rubys> | I think that eventually there won't be a single XHTML profile, but a series of ones... suitable for education (named entities OK) and suitable for enterprises (only 5 named entities and the numeric set) |
| 22:34 | <tantek> | I believe warning on the XHTML 1.0 named entities accomplishes that. |
| 22:35 | <rubys> | Suggestion for a useful test case: one that would be treated as iso-8859-1 when parsed as HTML and utf-8 when parsed as xhtml. |
| 22:35 | <tantek> | I'm hoping that HTML5 obeys the meta charset |
| 22:36 | <rubys> | HTML5 served as text/html does |
| 22:36 | <rubys> | HTML5 when parsed by an XML parser does not |
| 22:36 | <tantek> | heck I'd even be ok with a warning for any document that uses iso-8859-1 |
| 22:36 | <rubys> | that's basically my thinking |
| 22:36 | <tantek> | and have the warning say use UTF8 instead |
| 22:36 | <tantek> | srsly |
| 22:36 | <TabAtkins> | Woo, I'll become a regular user of Opera soon, now that the Wii Internet Channel is free. |
| 22:36 | <rubys> | agreed |
| 22:36 | <TabAtkins> | That explains the menacing glow yesterday. |
| 22:38 | <tantek> | rubys - btw your blog posts cites "Jeffrey Zeldman" at the start - note that the "guide" was a collaboratively written document - a more accurate cite would be "The HTML5 Super Friends" (as signed at the bottom of the "guide" http://www.zeldman.com/superfriends/guide/ |
| 22:39 | <tantek> | Jeffrey is hosting it at zeldman.com, not saying he wrote it, though of course he contributed to it heavily. |
| 22:39 | <rubys> | that term incites riots in certain sectors |
| 22:39 | <tantek> | usually the rioters stop when they become transfixed by the unicorn. |
| 22:40 | <tantek> | besides, the threat of rioting hasn't stopped you from being precise in the past ;) |
| 22:44 | <rubys> | ah, what the heck. Fixed. |
| 22:49 | <othermaciej> | hi all |
| 22:49 | <othermaciej> | tantek: do you know if more of the Superfriends are planning to join the HTML WG? |
| 22:50 | <tantek> | I have encouraged and am encouraging all of them to do so. Some already have. |
| 22:50 | <Hixie> | i just block-moved all the public-html and whatwg feedback today into my pile to deal with -- was there anything important i should have seen? |
| 22:51 | <othermaciej> | tantek: do you know if anyone is going to send the collected feedback in direct email form? I think that would be helpful (even though there is already some discussion) |
| 22:51 | <tantek> | othermaciej - yes, Hixie requested that the feedback be given in email form yesterday on IRC as well. |
| 22:52 | <tantek> | and yes, that has/is already happening |
| 22:52 | <tantek> | different people are picking up different pieces of the feedback and emailing them in |
| 22:52 | <tantek> | e.g. Jeremy Keith (@adactio) has already sent a bunch to the public-html list |
| 22:53 | <tantek> | and I believe Jeffrey Zeldman has emailed some of the feedback/suggestions directly to Hixie (and many fixes appear to have already been made) |
| 22:53 | <Hixie> | i haven't received any direct feedback since the superheroes made their superannouncement indicating that they had feedback |
| 22:53 | <Hixie> | and jeremy doesn't seem to have sent any new feedback to public-html |
| 22:53 | <tantek> | Hixie, one *really* important thing, there's a typo in the last example in the time element section - http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-time-element |
| 22:53 | <tantek> | lt; should be < |
| 22:53 | <Hixie> | (though he has commented on a few threads) |
| 22:54 | <Hixie> | tantek: file a bug using the feedback form in the spec :-) |
| 22:54 | <tantek> | I did - didn't seem to have any effect |
| 22:54 | <Hixie> | cool |
| 22:54 | <Hixie> | i'll get to it in due course |
| 22:54 | <tantek> | (yesterday) |
| 22:54 | <tantek> | cool |
| 22:55 | <tantek> | Hixie, feedback started being sent to the list (and to you directly) *before* the announcement was posted, as we didn't think waiting was necessary, so everyone was given freedom to make feedback ASAP, not wait for anything. |
| 22:55 | <Hixie> | ah ok |
| 22:55 | <tantek> | s/given freedom/encouraged |
| 22:56 | <Hixie> | so long as all the feedback is sent through one of the usual channels, that's good |
| 22:56 | <Hixie> | it just seemed like there was much more on zeldman's blog than had been sent |
| 22:56 | <Hixie> | maybe i was just confused by the font size :-) |
| 22:58 | <tantek> | Hixie - you might say that people are having open discussions regarding some points of feedback to clarify / improve them before sending them in officially so that when you see them on the list, your time is better spent. |
| 22:58 | <Hixie> | i might? |
| 22:59 | <tantek> | no reason to waste your time shooting down half-baked feedback. blog commenters are perfectly good at that. ;) |
| 23:00 | <othermaciej> | tantek: I'm kind of interested in the figure/details/legend feedback, since that seems to be a point where both the design folks and browser implementors are not entirely satisfied with the current state of the spec |
| 23:00 | <tantek> | othermaciej - I agree, and there was much debate on that point too. |
| 23:01 | <tantek> | or rather on details/legend specifically |
| 23:01 | <tantek> | figure is well liked AFAIK |
| 23:01 | <othermaciej> | what I meant specifically is use of legend for both details and figure - the big feedback post commented on both of those (though IIRC proposed different solutions for each) |
| 23:04 | <othermaciej> | I was prepared to drop this, but it seems in the 1.5 years since we last discussed this issue, there has been no progress on legend parsing in any of the browsers, and dissatisfaction with the state of things continues |
| 23:04 | <Hixie> | there's been massive progress |
| 23:04 | <Hixie> | mozilla implemented the entire html5 parser algorithm |
| 23:04 | <othermaciej> | when they ship it there will be progress |
| 23:05 | TabAtkins | loves SVL's quit message. |
| 23:07 | <TabAtkins> | I'm guessing that Gecko's new algo, a <legend> that's not a child of a <fieldset> is just treated like a normal block for styling purposes? |
| 23:08 | <othermaciej> | it should act like a normal inline, no? |
| 23:08 | <TabAtkins> | Oh, right. |
| 23:08 | <TabAtkins> | I think. |
| 23:08 | TabAtkins | shrugs. |
| 23:08 | <TabAtkins> | "Normal element" is what I was getting at, rather than "crazy element that doesn't use the normal display engine". |
| 23:09 | <othermaciej> | that's how it is supposed to be per spec, whether Mozilla has implemented that, I don't know |
| 23:10 | <annevk3> | hsivonen's parser does the correct thing |
| 23:10 | <tantek> | othermaciej - <details> is useful. I don't think <legend> is necessarily the right answer though. |
| 23:11 | <TabAtkins> | parser, yeah. But does it respond correctly to CSS? <legend> in <fieldset> doesn't, because it has some magic display issues. |
| 23:11 | <othermaciej> | tantek: that's sort of what I think - it's a tradeoff between minting a few more elements vs. making <figure> and <details> effectively unusable for years |
| 23:11 | <hober> | it's too bad <legend> and <caption> both have unfortunate legacy parsing concerns; it seems a shame to mint another element with effectively the same semantics. nevertheless, that might be what we need to do |
| 23:11 | <tantek> | precisely |
| 23:11 | <tantek> | (in reply to othermaciej) |
| 23:11 | <annevk3> | TabAtkins, yes it does, try a recent Firefox and put <legend> in the DOM in XML mode or some such |
| 23:12 | <tantek> | <legend> may be too legacy-encumbered to be useful for <figure> and <details> |
| 23:12 | <TabAtkins> | annevk3: Thanks, I only have the latest public release of FF. |
| 23:12 | <tantek> | and you know how much I am a strong advocate of re-use whenever possible. |