| 00:13 | <paul_irish> | othermaciej: do you have a recommendation on how to feature detect the new input types in safari? |
| 00:14 | <paul_irish> | assuming the tests would fail now.. |
| 00:16 | <othermaciej> | paul_irish: I hadn't thought about it - I don't know if the spec has any mechanism for feature detection |
| 00:17 | <othermaciej> | in any case feature tests would currently pass, even though our implementations are pretty crufty |
| 00:17 | <Hixie> | checking the value of input.type should work iirc |
| 00:17 | <Hixie> | iirc it'll be "text" if the type isn't supported at all |
| 00:17 | <paul_irish> | yeah.. basic approachis to check value of input.type and see if it isn't 'text' .. chrome loves to false positive with that |
| 00:17 | <Hixie> | yeah that's the problem with feature tests :-) |
| 00:17 | <othermaciej> | I believe both Chrome and Safari will claim to support almost all the types by that standard |
| 00:18 | <othermaciej> | which in a sense we do, but perhaps not in a way you would actually want to use |
| 00:18 | <Hixie> | using cutting edge feature is fraught with such difficulties |
| 00:18 | <paul_irish> | so i've been throwing text like ':)' into the value of input type="date" and reading it out.. assuming that a proper date input would only allow proper date input.. that's seemed to work so far |
| 00:18 | <Hixie> | othermaciej: i was sad to see the incomplete implementations ship, didn't expect that |
| 00:39 | <MikeSmith> | latest HTML WG heartbeat WDs and FPWDs are now alive at http://www.w3.org/TR/html5/ etc. |
| 00:40 | <MikeSmith> | for convenient access, see reverse-chronological index at http://www.w3.org/TR/tr-date-drafts |
| 00:41 | MikeSmith | also notices http://www.w3.org/TR/2010/WD-media-frags-20100624/ |
| 00:41 | <MikeSmith> | whatever that is, it's at LC |
| 00:41 | <MikeSmith> | so perhaps worth reviewing |
| 00:42 | MikeSmith | sees nessy1 listed there among the editors |
| 00:42 | <MikeSmith> | "specifies the syntax for constructing media fragment URIs and explains how to handle them when used over the HTTP protocol." |
| 00:44 | MikeSmith | notices LC of SVG 1.1 "Second Edition" |
| 00:44 | <MikeSmith> | http://www.w3.org/TR/2010/WD-SVG11-20100622/ |
| 00:45 | <MikeSmith> | which appears to have a pretty big list of substantive changes |
| 00:45 | <MikeSmith> | http://www.w3.org/TR/2010/WD-SVG11-20100622/changes.html#Substantial |
| 00:46 | <MikeSmith> | seems the precedent set by XML 1.0 doing the "Fifth Edition" thing to incorporate substantive changes and not just errata is now firmly rooted |
| 00:47 | <MikeSmith> | that seems to perhaps be a really unfortunate trend |
| 00:47 | <MikeSmith> | anyway, the SVG 1.1 draft is at LC also |
| 00:48 | <MikeSmith> | reminds me that I want to send LC comments on MathML3 before July 1 deadline |
| 00:50 | <othermaciej> | MikeSmith: woot! |
| 00:50 | <MikeSmith> | othermaciej: yeah, sorry I didn't get them out yesterday |
| 00:50 | <MikeSmith> | I blame it on too much reefer |
| 00:50 | <othermaciej> | do you know if the w3c plans to post any kind of announcement? |
| 00:51 | <othermaciej> | or should it just be announced on the list? |
| 00:51 | <MikeSmith> | we will do an announcement soon |
| 00:51 | <othermaciej> | it would be nice if there was a single thing to link to for the set of all the new drafts |
| 00:51 | <MikeSmith> | yes |
| 00:51 | <MikeSmith> | I think we will have that by end of day US/West |
| 00:52 | <MikeSmith> | they will all be linked to in the announcement |
| 00:52 | <othermaciej> | cool beans |
| 00:52 | <MikeSmith> | Home Page News |
| 00:56 | <MikeSmith> | Hixie: I realize you are probably long ago bored with my mentioning the processing issues of the annotation-xml element |
| 00:56 | <MikeSmith> | but I remembered something I didn't mention before |
| 00:57 | <MikeSmith> | the annotation-xml element has an "encoding" attribute |
| 00:57 | <MikeSmith> | which specifies a MIME type |
| 00:58 | <MikeSmith> | so if that is present and it specifies text/html, then seems like the parsing algorithm could use that info to do the similar behavior it does with SVG in there now |
| 00:58 | <Hixie> | that might make sense, yeah |
| 00:58 | <Hixie> | file a bug? |
| 00:58 | <MikeSmith> | so, we would not need a <div> wrapper or <body> or <html> |
| 00:58 | <MikeSmith> | yeah, I will update the bug I already opened |
| 00:59 | <MikeSmith> | after I get some sleep |
| 00:59 | <Hixie> | k |
| 01:59 | <boblet> | Anyone know what Microformats wiki means by “Avoid the "microdata vCard" vocabulary as it is an out-of-date fork/snapshot of hCard”? http://microformats.org/wiki/html5 |
| 02:00 | <boblet> | I thought Microdata vCard was based on vCard |
| 02:00 | <boblet> | are there some issues regarding this I’m not aware of? |
| 02:13 | <MikeSmith> | boblet: I remember hearing some details from tantek about that |
| 02:13 | <MikeSmith> | maybe ping him on twitter |
| 02:13 | <boblet> | MikeSmith: ok will do, thanks |
| 02:14 | <boblet> | also have yet to check µF mail archives |
| 02:14 | <MikeSmith> | but iirc the problem is that the RFC that the microdata vCard vocab was based on is superseded now |
| 02:14 | <MikeSmith> | by an updated RFC |
| 02:14 | <MikeSmith> | which the hCard vocab is in sync with |
| 02:15 | <boblet> | woah holy shit. They *update* RFCs? |
| 02:15 | <MikeSmith> | replace them |
| 02:15 | <MikeSmith> | new ones obsolete the old ones |
| 02:15 | <boblet> | I thought those things got carved into stone back in the mesozoic era |
| 02:15 | <TabAtkins> | Um. I'm not authorized to comment on the Issue-30 poll. |
| 02:16 | <boblet> | (which is why they’re fixed width) |
| 02:16 | <boblet> | thanks for the info MikeSmith. bbl |
| 02:16 | <MikeSmith> | TabAtkins: lemme check now |
| 02:17 | <TabAtkins> | It's possible that I'm logged in as tabatkins, rather than tabatkins2 |
| 02:18 | <MikeSmith> | ah |
| 02:18 | <MikeSmith> | that might be it |
| 02:18 | <TabAtkins> | I don't know how to log out of Basic Auth. |
| 02:19 | <MikeSmith> | arr, me neither |
| 02:19 | <MikeSmith> | lemme check |
| 02:19 | TabAtkins | heads home, and will respond on Monday he guesses. |
| 02:21 | <MikeSmith> | ok |
| 03:54 | <Hixie> | boblet: i think that's out of date -- the microdata vcard spec has been changed to just work directly from vCard rather than hCard |
| 04:38 | <jmcneese> | howdy canvasers |
| 04:40 | <jmcneese> | so, can anyone answer if it is per spec/functionality that if i stroke a line in a canvas, it does not clear if if reset the canvas via changing the width or clearRect()? |
| 04:41 | <Hixie> | how do you mean? |
| 04:41 | <Hixie> | do you have a sample page showing the problem? |
| 04:41 | <jmcneese> | not on a reachable server. |
| 04:42 | <jmcneese> | it's simple to replicate. start with an empty canvas. draw a line down the center. do a clearRect() on the canvas. the line stays |
| 04:43 | <jmcneese> | curious if i'm missing a step |
| 04:45 | <Hixie> | what arguments are you passing clearRect()? |
| 04:48 | <jmcneese> | 0,0,CANVASWIDTH,CANVASHEIGHT |
| 04:48 | <jmcneese> | it's working for any canvas i draw actual shapes on (rects, arcs, etc) |
| 04:49 | <Hixie> | so like: |
| 04:49 | <Hixie> | c.beginPath(); |
| 04:49 | <Hixie> | c.moveTo(100,100); |
| 04:49 | <Hixie> | c.lineTo(200,300); |
| 04:49 | <Hixie> | c.stroke(); |
| 04:49 | <Hixie> | c.clearRect(0, 0, 640, 480); |
| 04:49 | <Hixie> | ...doesn't work? |
| 04:49 | <Hixie> | (where c is the context of course) |
| 04:50 | <jmcneese> | aha... is beginPath required? |
| 04:50 | <Hixie> | unless you do beginPath(), you're just adding to the last line each time |
| 04:50 | <Hixie> | stroke() doesn't reset the path |
| 04:51 | <jmcneese> | ok, noted. but i don't see how that prevents the line from clearing when calling clearRect |
| 04:51 | <Hixie> | e.g. try: |
| 04:51 | <Hixie> | c.lineWidth=100; c.strokeStyle = 'red'; c.stroke(); |
| 04:51 | <Hixie> | c.lineWidth=50; c.strokeStyle = 'orange'; c.stroke(); |
| 04:51 | <Hixie> | c.lineWidth=10; c.strokeStyle = 'yellow'; c.stroke(); |
| 04:52 | <Hixie> | well it's not that it prevents the line from being cleared, so much as you're probably calling stroke() again after you clear |
| 04:52 | <Hixie> | e.g. on a timer or something |
| 04:52 | <Hixie> | right? |
| 04:52 | <Hixie> | hard to say without seeing the code |
| 04:52 | <jmcneese> | i am calling redraw on mousedrag |
| 04:53 | <jmcneese> | now, since i couldn't get it to clear the lines for a grid, i ended up drawing rectangles (with three sides off canvas), which clear just fine |
| 04:54 | <Hixie> | yeah the rect methods don't affect the path |
| 04:55 | <Hixie> | so they wouldn't get added each time |
| 04:55 | <Hixie> | the key is just that all the liens you add to the path don't get reset until you call beginPath() again |
| 04:55 | <jmcneese> | so, paths must be aha |
| 04:55 | <jmcneese> | that makes sense |
| 04:58 | <jmcneese> | thanks mate |
| 04:58 | <Hixie> | np |
| 06:54 | <boblet> | Hixie: re: vcard & hcard, I’m guessing that the microdata vcard and vevent specs have been updated to the latest RFCs right? (apparently the reason for the microformats.org comment) |
| 06:54 | <boblet> | if so I’ll edit the wiki or contact Tantek about it |
| 06:54 | <Hixie> | have the RFCs changed recently? |
| 06:55 | <Hixie> | like in the last year? |
| 07:00 | <boblet> | Hixie: Mike seemed to think that was the reason. Will do some digging… |
| 07:06 | <Hixie> | i know there was some work to update the rfcs, but i haven't updated the vocabs to the new ones if that's it |
| 07:06 | <Hixie> | i didn't think hcard had been updated to them either though |
| 07:08 | <boblet> | Hixie: yeah it seems vcard 1.1 is still draft anyhow: http://datatracker.ietf.org/doc/draft-ietf-vcarddav-vcardrev/ |
| 07:09 | <Hixie> | k |
| 07:09 | <boblet> | guess I’ll have to ping tantek and see what was meant by those statements. seems a bit strange |
| 07:54 | <annevk> | oh look |
| 07:54 | <annevk> | http://www.w3.org/News/2010#entry-8843 |
| 07:54 | <annevk> | yay for Mike |
| 07:58 | <MikeSmithX> | annevk: yay for editors getting their work done |
| 07:58 | <MikeSmith> | annevk: btw, thanks for all the time you spent on responding to comments about the diffs doc |
| 07:58 | <MikeSmith> | I know it took a lot of time |
| 07:59 | <MikeSmith> | and most people have no idea how much time and work goes into |
| 07:59 | <MikeSmith> | but it's a very useful document to have available |
| 07:59 | <MikeSmith> | for people who are trying to follow the changes |
| 07:59 | <MikeSmith> | and especially for people who are just starting to read up on HTML5 |
| 08:00 | <MikeSmith> | when people ask me where to start with learning about HTML5, I always tell them to start with reading that document |
| 08:02 | <annevk> | cool man |
| 08:04 | <MikeSmith> | so along with getting updated WDs published and despite all the drama, all the actually important stuff still keeps on getting done |
| 08:05 | <MikeSmith> | e.g., giantly newsworthy stuff like canvas support finally being added to IE |
| 08:06 | <MikeSmith> | which the IE tech people deserve a lot of serious congrats for |
| 08:06 | <MikeSmith> | despite it taking some time to make it happen |
| 08:07 | <MikeSmith> | two years from now nobody will even remember that it took so long |
| 08:07 | <MikeSmith> | well I guess we may remember |
| 08:07 | <MikeSmith> | but nobody else will |
| 08:08 | <MikeSmith> | and then all kinds of other bits of important work are steadily and mostly quietly getting done |
| 08:08 | <MikeSmith> | e.g., moving ahead with getting agreement on Notifications |
| 08:09 | <annevk> | the way WebKit reverses what to switch first on in the tree builder is interesting |
| 08:09 | <annevk> | what you pointed out in a blog post |
| 08:09 | <MikeSmith> | heh |
| 08:09 | <MikeSmith> | ah yeah |
| 08:09 | <annevk> | euh tweet |
| 08:09 | <MikeSmith> | that's a good example |
| 08:10 | <MikeSmith> | abarth was talking about that a little bit here a few hours back |
| 08:10 | <MikeSmith> | example of "there's more than one way to skin a cat" |
| 08:10 | <MikeSmith> | dunno what that equivalent idiom is elsewhere |
| 08:10 | <MikeSmith> | I don't know if that began as a UK idiom or a US one |
| 08:11 | <MikeSmith> | seems like a US one |
| 08:11 | MikeSmith | tries to think of a less opaque idiom to capture that same meaning |
| 08:13 | <MikeSmith> | annevk: dunno how many people in this world would judge that to be interesting |
| 08:13 | <MikeSmith> | I mean, I did not because I know a whole lot but mostly because I had spent time looking at hsivonen htmlparser code |
| 08:13 | <MikeSmith> | and htmllib |
| 08:14 | <MikeSmith> | and not just looking at in the case of hsivonen code |
| 08:14 | <MikeSmith> | but actually copying and tweaking it |
| 08:14 | <MikeSmith> | for the xml-stylesheet checking feature that I added to validator.nu a while back |
| 08:15 | <MikeSmith> | needed it for pseudo-attribute-value parsing |
| 08:15 | <MikeSmith> | so it is really interesting to compare, anyway |
| 08:17 | <boblet> | who’s in charge of the W3 CSS validator? and will they ever change vendor prefixes from error to warning? ;-) |
| 08:17 | <MikeSmith> | boblet: not sure who is currently |
| 08:17 | <MikeSmith> | DanC rewrote it recently |
| 08:17 | <MikeSmith> | or wrote a new one |
| 08:17 | <MikeSmith> | hmm, not sure if that is public info |
| 08:17 | <boblet> | it is now :) |
| 08:18 | <MikeSmith> | well, maybe there was an announcement about it |
| 08:18 | <MikeSmith> | I don't keep up with it so much |
| 08:18 | <MikeSmith> | anyway, DanC wrote something in Scala |
| 08:18 | <boblet> | I might ask on wwwstyle |
| 08:18 | <MikeSmith> | part of the problem with getting people interested in working on the current CSS validator code is that it's written in Java |
| 08:19 | <MikeSmith> | which must people immediately just say "ick" |
| 08:19 | <MikeSmith> | Philippe le Hegaret wrote the CSS validator originally, I think |
| 08:20 | <MikeSmith> | boblet: lemme go look at the source repo know and see who's working on it currently |
| 08:20 | <boblet> | thanks MikeSmith |
| 08:20 | <MikeSmith> | boblet: btw, did you figure out what actual difference there are between vcard microformat and hcard one? |
| 08:21 | <MikeSmith> | I remember tantek telling me what the differences were and I remember those differences between important |
| 08:21 | <MikeSmith> | but I can't remember now that the differences actually are :( |
| 08:22 | <boblet> | MikeSmith: no. am planning to ping Tantek after checking µF email archives. the notes were added Oct 2009 though, so I’m guessing it’s something to do with the old hcard-based Microdata vcard (although currently it’s RFC2426-based so theoretically no worries) |
| 08:22 | <MikeSmith> | OK |
| 08:24 | <MikeSmith> | boblet: I find http://dev.w3.org/cvsweb/2002/css-validator/org/w3c/css/css/ |
| 08:24 | <MikeSmith> | etc. |
| 08:25 | <MikeSmith> | and I remember that my W3C sempai Yves Lafon is the main one making CSS validator maintenance changes these days |
| 08:25 | <boblet> | heh, searching http://lists.w3.org/Archives/Public/www-validator-css/ atm |
| 08:25 | <MikeSmith> | most recent change seems to be from 7 days ago |
| 08:25 | <MikeSmith> | boblet: anyway, it is very much one of those "squeaky wheel gets the grease" kind of things |
| 08:26 | <MikeSmith> | if you really want some particular changes made, file a bugzilla bug |
| 08:26 | <boblet> | MikeSmith: thanks. will squeak a bit then :) |
| 08:26 | <MikeSmith> | and feel free to Cc me on the bug, at mike⊙wo |
| 08:27 | <MikeSmith> | and I can then harass Yves about it until he his tired of me mentioning it |
| 08:27 | <MikeSmith> | boblet: http://www.w3.org/Bugs/Public/enter_bug.cgi?product=CSSValidator |
| 08:27 | <boblet> | cheers — will do! |
| 08:28 | <MikeSmith> | yeah, please do |
| 08:28 | <MikeSmith> | also consider mentioning it on the www-validator list, and including a link to the bug |
| 08:29 | <MikeSmith> | and others who are interested can add themselves to the Cc for the bug |
| 08:29 | <boblet> | har, paul_irish bet me by 10 days http://www.w3.org/Bugs/Public/show_bug.cgi?id=9932 |
| 08:29 | <MikeSmith> | well, there you go |
| 08:29 | <MikeSmith> | God is clearly on your side |
| 08:30 | <MikeSmith> | and paul_irish is one of his secret agents |
| 08:30 | MikeSmith | adds himself to the Cc for that bug |
| 08:30 | <boblet> | Thank science! … uh thank God! |
| 08:31 | <MikeSmith> | I suspect I might probably be able to make that change relatively quickly and easily myself |
| 08:31 | <MikeSmith> | but I'm not going to try |
| 08:32 | <MikeSmith> | because if I start fixing css validator bugs, I will then become at least partially responsible for maintaining it too |
| 08:32 | <boblet> | ref http://lists.w3.org/Archives/Public/www-validator-css/2009Jul/0002.html |
| 08:33 | <MikeSmith> | thanks |
| 08:33 | <MikeSmith> | yipes |
| 08:33 | <MikeSmith> | [[ |
| 08:33 | <MikeSmith> | > /* Do not Validate BEGIN */ |
| 08:33 | <MikeSmith> | > -moz-.... |
| 08:33 | <MikeSmith> | > -webkit-... |
| 08:33 | <MikeSmith> | > /* Do not Validate END */ |
| 08:33 | <MikeSmith> | ]] |
| 08:33 | <MikeSmith> | yuck |
| 08:34 | <boblet> | yeah I agree with Yann. but if the reason they generate an error is the starting hyphen, that’s bs |
| 08:34 | <MikeSmith> | well, I hope some people can step up to the plate to help Yves out with maintenance |
| 08:34 | <boblet> | if the validator doesn’t validate them (and assuming hyphen is the correct way to add a vendor prefix) they should be a warning not error |
| 08:34 | <MikeSmith> | true I guess |
| 08:35 | <MikeSmith> | but there are many other things that the CSS validator is not handling |
| 08:35 | <MikeSmith> | CSS3 stuff |
| 08:36 | <MikeSmith> | it is to the point that pretty much every working-draft we go to publish these days, when I check it with the W3C "pubrules" checker, which includes a CSS check, I get errors about the CSS |
| 08:36 | <MikeSmith> | which I and pubs team now pretty much just have to ignore |
| 08:36 | <MikeSmith> | because most of them are spurious |
| 08:37 | <MikeSmith> | and so that defeats the purpose of having a CSS check to begin with |
| 08:37 | <MikeSmith> | so we really should fix it |
| 08:37 | <MikeSmith> | I am pretty sure that Yves would be very happy to hand over the reins to anybody who could commit to helping with it |
| 08:38 | <MikeSmith> | and who had the coding chops |
| 08:38 | <MikeSmith> | or would at least be willing to spend some time learning |
| 08:39 | <MikeSmith> | I wish I could make time to help out with it myself |
| 08:39 | <MikeSmith> | but I would be the wrong person to do it anyway |
| 08:39 | <MikeSmith> | since I don't know jack about CSS |
| 08:40 | <MikeSmith> | boblet: learn some little Java, and you can get commit access and make the changes yourself directly |
| 08:40 | <boblet> | will add it to my list of things to do ＞＿＜ |
| 08:40 | <MikeSmith> | or maybe you know some Java already |
| 08:40 | <MikeSmith> | but you are keeping it quiet |
| 08:41 | <boblet> | har! |
| 08:41 | <MikeSmith> | so that you don't get stuck with maintaining the code |
| 08:41 | <MikeSmith> | I'm on to you, man |
| 08:41 | <MikeSmith> | boblet: btw, DanC's new code is at http://dvcs.w3.org/hg/css-val/ |
| 08:42 | <MikeSmith> | http://dvcs.w3.org/hg/css-val/file/f5931981d7dd/ |
| 08:42 | <MikeSmith> | http://dvcs.w3.org/hg/css-val/raw-file/f5931981d7dd/README.html |
| 08:42 | <MikeSmith> | Scala seems to be relatively easier and less painful to learn than Java |
| 08:42 | <MikeSmith> | and more forgiving, maybe |
| 08:44 | <MikeSmith> | "CSS syntax evolves in a backward- and forward-compatible way; the CSS 2.1 specification includes a uniform grammar, applicable to all CSS versions. The original (2002) W3C CSS Validator predates this uniform grammar and maintenance is becoming an undue burden as a result. This is an attempt to build a validator using the uniform syntax." |
| 08:44 | <MikeSmith> | hmm, so sounds like we are in pretty much the same situation with the CSS validator that we are with the current W3C Markup Validator |
| 08:45 | <boblet> | hrm, hopefully DanC gets some volunteers then eh |
| 08:45 | <boblet> | ok bbl, the little princess demands I play with her |
| 08:46 | <MikeSmith> | from what Dan says there, I can see that the existing CSS validator code, like the existing W3C Markup Validator code, is based on an obsolete backend, and we are not getting a good return on investment for the time we might put into maintaining it any further |
| 08:46 | <MikeSmith> | we just need to replace it |
| 08:46 | <MikeSmith> | boblet: k |
| 08:50 | <MikeSmith> | annevk: (if you are around) do you know, is there a formal grammar for CSS3 |
| 08:50 | <MikeSmith> | ? |
| 08:50 | <MikeSmith> | yet |
| 08:51 | <MikeSmith> | I don't know what "uniform grammar" means |
| 08:53 | <MikeSmith> | I have serious misgivings about basing checking in a validator on a formal grammar to begin with |
| 08:53 | <MikeSmith> | but maybe the CSS case is different than others |
| 08:54 | MikeSmith | finds http://www.w3.org/TR/css3-syntax/ |
| 08:54 | <annevk> | hmm not really |
| 08:54 | <MikeSmith> | http://www.w3.org/TR/css3-syntax/#detailed-grammar |
| 08:54 | <annevk> | we just patch the CSS 2.1 grammar basically |
| 08:54 | <MikeSmith> | annevk: seems like dbaron is working on that |
| 08:55 | <MikeSmith> | oh |
| 08:55 | <MikeSmith> | well, that's better than nothing |
| 08:55 | <annevk> | css3-syntax is hopelessly out of date |
| 08:55 | <annevk> | it's from 2003 |
| 08:55 | <MikeSmith> | http://www.w3.org/TR/css3-syntax/#lexical |
| 08:55 | <MikeSmith> | ah |
| 08:55 | <annevk> | many many grammar changes have been made since then |
| 08:56 | <MikeSmith> | yet another spec in need of an active editor |
| 08:58 | <MikeSmith> | I wish the people who aren't otherwise actually yet doing editing or implementing or testing or documenting but instead seem to have endless amounts of time to repeatedly engage in process discussions ad nauseam might actually consider trying to really help out |
| 08:59 | <MikeSmith> | help out in other ways than suggesting ways to fix decision process, etc. |
| 09:00 | <MikeSmith> | which is not to say that is not useful as well |
| 09:00 | <MikeSmith> | but damn |
| 09:00 | <annevk> | everyone their talent I guess o_O |
| 09:00 | <MikeSmith> | well, everybody benefits from us having an up-to-date CSS validator |
| 09:01 | <MikeSmith> | that groks CSS3 |
| 09:01 | <MikeSmith> | and we need some sound modern backend to base it on |
| 09:01 | <MikeSmith> | rather than throwing good money after bad on the old one |
| 09:01 | <annevk> | yeah, done in such a way that Validator.nu can invoke it, too |
| 09:02 | <annevk> | Validator.nu code, that is |
| 09:02 | <MikeSmith> | yeah |
| 09:02 | <MikeSmith> | and we need a good grammar to use for that -- to base the CSS checker on .. and a we need a good spec to hold that.. and we need an active editor for the spec |
| 09:03 | <MikeSmith> | everyone their talent, yeah |
| 09:03 | <MikeSmith> | but christ |
| 09:04 | <MikeSmith> | it is not a massive undertaking for somebody who's already smart to learn a little bit about how to write a grammar |
| 09:04 | <MikeSmith> | and to do a little bit of spec editing maybe |
| 09:04 | <MikeSmith> | we ain't asking for the world here |
| 09:07 | MikeSmith | notices a typo in home-page news for announcement of updated HTML WG drafts |
| 09:07 | <MikeSmith> | s/machine-readable date/machine-readable data/ |
| 09:07 | <MikeSmith> | dam |
| 09:07 | <MikeSmith> | mnit |
| 09:07 | <MikeSmith> | my fault, too |
| 09:08 | <MikeSmith> | but I don't have perms to change it now |
| 09:08 | <MikeSmith> | ah well |
| 10:30 | <boblet> | foolip: yt? |
| 11:17 | <Philip`> | "why do we care about 1%? Who decided where we draw the line?" - I thought it was 1% because there's lots of Opera people in the group and Opera isn't much more than 1% |
| 11:35 | <gsnedders> | boblet: Probably flying now. |
| 11:40 | <MikeSmith> | annevk: btw, update of diffs doc has already been added to the Japanese translation at html5.jp |
| 11:40 | <MikeSmith> | http://twitter.com/futomi/status/17073669143 |
| 11:40 | <MikeSmith> | http://www.html5.jp/trans/w3c_differences.html |
| 13:28 | <Philip`> | The W3C Test Suite License seems to have not been designed with the idea of including its text in the files you're going to distribute under the license |
| 13:29 | <Philip`> | since it uses hyperlinks and bold and italic and non-ASCII |
| 13:35 | <boblet> | gsnedders: ok thanks |
| 14:18 | <erlehmann> | can anyone advise me on this issue ? wordpress is using <em> and <strong> by default, but the buttons are marked <i> and <b> http://core.trac.wordpress.org/ticket/10465 |
| 14:19 | <erlehmann> | it's just too dumb and i don't know how to tell them to change this. |
| 14:19 | <erlehmann> | last time i tried, they kicked me out of #wordpress :/ |
| 14:24 | <Philip`> | erlehmann: Since i/em and b/strong are synonyms in practice, it seems a waste of time to try to get them to change |
| 14:26 | <erlehmann> | Philip`, but emphazised text is different from italiced text (like names that need to be set apart from the regular flow of text), especially in quotes. |
| 14:26 | <erlehmann> | also, these buttons confuse me. |
| 14:26 | <erlehmann> | all other buttons do what's on the label :( |
| 14:27 | <Philip`> | erlehmann: Few people care about the distinction, and the people who do care are usually on the wrong side, so it doesn't seem a good fight to get into :-) |
| 14:28 | <erlehmann> | fine. i will call my next helper script „bake_cake.zsh“ then. but make it burn the users home directory. huehuehue |
| 14:33 | <Philip`> | I've already learned not to trust anyone who promises to bake me a cake, so that's fine |
| 14:55 | <gsnedders> | Oooo! Cake nom nom! |
| 15:52 | <jgraham> | gsnedders: No! You can't om nom ... oh wait what? Ah. I've just ben told that om noming cake is fine. As you were. |
| 16:09 | <erlehmann> | gsnedders, jgraham, the WHATWG wishes to remind you that upon completion of the spec, there will be cake. |
| 16:14 | <boblet> | erlehmann: cake that deletes completed specs? |
| 16:17 | <boblet> | in foolip’s excellent http://foolip.org/microdatajs/live/ the hcard in <span itemprop="location" itemscope itemtype="http://microformats.org/profile/hcard">; isn’t shown unless the itemprop="location" is removed. looks like a bug |
| 16:40 | <boblet> | nimbupani inna house! |
| 16:40 | <nimbupani> | yo boblet !! |
| 16:40 | <nimbupani> | emoticon koan guru :) |
| 16:40 | <boblet> | so was it the 微妙 or the … aah, the emoticons huh |
| 16:40 | <boblet> | :| |
| 16:40 | <boblet> | didn’t realise I was being so deep ;-) |
| 16:42 | <nimbupani> | boblet: you were very deep coz I did not understand 微妙 :) |
| 16:43 | <boblet> | bimyou = Japanese for dodgy or iffy |
| 16:43 | <nimbupani> | ohh okie :) |
| 17:24 | <boblet> | hixie: yt? |
| 17:24 | <boblet> | or anyone into microdata? |
| 17:25 | <boblet> | when I add itemscope to a property, that property now represents the contained item’s name-value pairs, but does it also have a value of all contained text as well? |
| 17:28 | <boblet> | eg <p itemprop="members" itemscope>The band is <b itemprop="name">Bob</b> and <b itemprop="name>Sally</b></p>; members = contained name-value pairs (name:Bob, name:Sally) only, or also the value “The band is Bob and Sally.”? |
| 21:13 | <Hixie> | has hober been around recently? |