| 00:02 | <_bga> | Evet its hell but yes, its possible |
| 00:02 | <_bga> | you will have tons of fallbacks and workarounds |
| 00:03 | <_bga> | ie5.5 hasnt even Function#apply |
| 00:04 | <hober> | hsivonen: just got an Internal Error on validator.nu |
| 00:04 | <Rik`> | why build for ie 5.5 ? it's dead nowadays |
| 00:04 | <hober> | hsivonen: http://html5.validator.nu/?doc=http%3A%2F%2Fspaceup.org%2Fsandiego%2Fsponsors%2F |
| 00:06 | <Evet> | there must be some people using ie 5.5 |
| 00:07 | <Rik`> | Evet: yes but there are also some people using lynx or netscape 3 |
| 00:07 | _bga | <3 console browsers |
| 00:08 | <Evet> | shouldnt i consider ie 5.5 users? |
| 00:08 | <Rik`> | Evet: I don't think you should |
| 00:08 | <Rik`> | except if you're working for an intranet tool |
| 00:11 | <Rik`> | Evet: http://marketshare.hitslink.com/browser-market-share.aspx?qprid=2 |
| 00:12 | <Rik`> | if you look there, there is no sign of IE 5.5 |
| 00:12 | <Evet> | interesting |
| 00:13 | <Evet> | microsoft forces windows users to upgrade to 6.0? |
| 00:13 | <Rik`> | I don't remember the why, but IE 5.5 is just dead |
| 00:13 | <Philip`> | I think XP ships with 6.0, and approximately nobody uses anything older than that |
| 00:14 | <Philip`> | (Any older Windows, I mean) |
| 00:15 | <MikeSmith> | hober: got a test case I can try? |
| 00:15 | <MikeSmith> | (for that validator error) |
| 00:16 | <Rik`> | Evet: I think Philip` is right, http://en.wikipedia.org/wiki/Internet_Explorer_6 |
| 00:16 | <MikeSmith> | oh |
| 00:16 | <Evet> | oh, it was released in 2001 |
| 00:17 | MikeSmith | notices hober link |
| 00:17 | <MikeSmith> | ah cool |
| 00:18 | <MikeSmith> | was able to reproduce it |
| 00:18 | <MikeSmith> | java.lang.NullPointerException in the IRI checker |
| 00:20 | <MikeSmith> | oops |
| 00:21 | <MikeSmith> | cause is some code I added recently to check for non-empty IRIs |
| 00:21 | <hober> | ahh |
| 00:21 | <MikeSmith> | but without checking for null before I do the non-emptiness check |
| 00:22 | <MikeSmith> | (fixing it now) |
| 00:23 | <hober> | rad |
| 00:25 | <Evet> | http://www.amplesdk.com/about/compatibility/ |
| 00:25 | <Evet> | it means, HTML5 even in IE 5.5+? |
| 00:26 | <benschwarz> | Hixie: Where can I get what you'd consider "input" for the author-spec? |
| 00:27 | <benschwarz> | I want to generate a working copy here |
| 00:29 | <_bga> | Evet IE has very good abilities of extension. i mean 'behaviour, css expressions, filters, ...'. You can emulate any new api and spec using this features |
| 00:38 | <MikeSmith> | hober: fix checked in - https://bitbucket.org/validator/syntax/changeset/3b2c143408d2 |
| 00:39 | <MikeSmith> | will probably get pushed to validator.nu some time this week or next when hsivonen |
| 00:39 | <benschwarz> | Morning folks |
| 00:39 | <MikeSmith> | *hsivonen reploys |
| 00:40 | <MikeSmith> | damn |
| 00:40 | <MikeSmith> | re-deploys |
| 00:40 | <MikeSmith> | he benschwarz |
| 00:40 | <MikeSmith> | are you mobile? |
| 00:40 | <MikeSmith> | as in , able to walk around? |
| 00:40 | <benschwarz> | I can walk, but very stiff and sore |
| 00:40 | <benschwarz> | Fluid on the knee :/ |
| 00:41 | <MikeSmith> | ouch |
| 00:41 | <hober> | MikeSmith: thanks! |
| 00:41 | <MikeSmith> | hober: thanks for catching it |
| 00:42 | <AryehGregor> | What does this "function() { atob(input) } threw with code INVALID_CHARACTER_ERR (5) expected INVALID_CHARACTER_ERR (5)" error in Firefox and Opera mean? It's confusing me. I'm told it's unrelated, so perhaps I shouldn't worry about it . . . http://aryeh.name/tests-root/tests/submission/AryehGregor/base64.html |
| 00:43 | <AryehGregor> | But at least the reporting framework could surely have a clearer error message. |
| 00:43 | AryehGregor | pings jgraham |
| 00:43 | <MikeSmith> | hober: fwiw, there appear to be no other errors on that page |
| 00:43 | <gsnedders> | jgraham is asleep. |
| 00:44 | <MikeSmith> | (other than the one about the profile attribute) |
| 00:44 | <MikeSmith> | http://www.w3.org/html/check?doc=http%3A%2F%2Fspaceup.org%2Fsandiego%2Fsponsors%2F |
| 00:44 | <MikeSmith> | http://www.w3.org/html/check runs whatever code I currently have in my workspace |
| 00:45 | <MikeSmith> | which includes changes that Henri or I have committed but that may not have gotten deployed at validator.nu yet, as well as changes that I've not committed yet |
| 00:46 | <MikeSmith> | so it's not stable |
| 00:46 | <MikeSmith> | but it's useful for testing |
| 00:47 | <MikeSmith> | hsivonen: btw, http://www.w3.org/html/check?doc=data%3Atext%2Fhtml%3Bcharset%3Dutf-8%2C%3C%21DOCTYPE%2520html%3E%250A%3Ctitle%3E%3C%252Ftitle%3E%250A%3Cp%3E%3Cb%3E%3Ci%3E%3C%252Fp%3E%250A |
| 00:47 | <MikeSmith> | (which shows the duplicate error reports problem I mentioned) |
| 00:54 | <Evet> | do you recommend any specific IDE to use with Ample SDK? |
| 00:57 | <MikeSmith> | benschwarz: input for the author view of the spec would be either http://svn.whatwg.org/webapps/complete.html or http://svn.whatwg.org/webapps/index |
| 00:57 | <MikeSmith> | I think |
| 00:57 | <MikeSmith> | or both |
| 00:59 | <MikeSmith> | depending on whether you want the author view to be of the HTML5 subset or of the full version that includes Workers, etc. |
| 01:01 | <MikeSmith> | or you could just use http://www.whatwg.org/specs/web-apps/current-work/complete.html or http://www.whatwg.org/specs/web-apps/current-work/index |
| 01:02 | <Evet> | _bga: may i pm you? |
| 01:02 | <_bga> | yes |
| 01:10 | <benschwarz> | MikeSmith: Single page vs Multi ? |
| 01:12 | <MikeSmith> | benschwarz: I think what you need to do is use the single page as source to generate the author view, then run the spec splitter on your output to generate for the multi-page author view |
| 01:12 | <benschwarz> | MikeSmith: How complicated :) |
| 01:13 | <MikeSmith> | would be much more complicated to use the multi-page version as your source |
| 01:13 | <MikeSmith> | the spec splitter is actually really quite fast |
| 01:14 | <MikeSmith> | and it handles re-writing URLs for all the inter-file links |
| 01:14 | <MikeSmith> | among other things |
| 01:16 | <MikeSmith> | anyway, I think all that your build needs to do is take the full source, run some kind of filter on it to remove the class=impl parts, save that as the file that'll be the single-page author view, then run the spec splitter on that file to generate the multi-page view |
| 01:18 | <MikeSmith> | plus whatever other tweaks you might want to also have the filer to do add any additional intro stuff or whatever that you want to be specific to the author view |
| 01:19 | <AryehGregor> | I think I really do have to specify the base64 decoding algorithm. |
| 01:38 | <AryehGregor> | Okay, comments requested again: http://aryeh.name/tmp/spec.html |
| 01:43 | <AryehGregor> | Hixie, oh, should I put Google copyright notices on the tests I submit or something like that? |
| 01:44 | <AryehGregor> | Also, I wonder if I should put them in the Google/ directory instead of AryehGregor/. Seems kind of silly, it's not like I'm working with any actual Google employees here. |
| 01:44 | <jamesr_> | AryehGregor: are we giving you $$$? |
| 01:45 | AryehGregor | supposes it makes no difference if he puts copyright notices or not |
| 01:45 | <AryehGregor> | jamesr_, yeah, but as a vendor, since I didn't want to start a full-time job just yet. |
| 01:45 | <jamesr_> | it |
| 01:46 | <jamesr_> | depending on where you are and blah blah blah it's probably work for hire then which means the copyright belongs to the party supplying the $$$ |
| 01:46 | <AryehGregor> | It was specified that the copyright would belong to Google, I just wonder whether I need to bother with notices or whatever. |
| 01:47 | <AryehGregor> | The tests in Google/ don't have them, so I won't. |
| 02:59 | <MikeSmith> | http://www.flock.com/node/162703 |
| 02:59 | <MikeSmith> | Zynga aquiring Flock |
| 05:05 | <artenix> | First time here. Hello all. |
| 05:07 | <artenix> | |
| 05:09 | <MikeSmith> | artenix: hi |
| 05:09 | <MikeSmith> | it's pretty quiet here this time of day |
| 05:10 | <MikeSmith> | off hours for Americas and Europe |
| 05:12 | <wirepair> | anyone else from here happen to be going to: http://www.owasp.org/index.php/Summit_2011#tab=Working_Sessions |
| 05:13 | <artenix> | It is 11.15 pm here. I'm looking for the differences between HTML5 and 4 |
| 05:13 | <MikeSmith> | artenix: http://dev.w3.org/html5/html4-differences/ |
| 05:13 | <wirepair> | http://dev.w3.org/html5/html4-differences/ |
| 05:13 | <wirepair> | beat me :/ |
| 05:13 | <wirepair> | ehe |
| 05:13 | <MikeSmith> | heh |
| 05:14 | <MikeSmith> | what is owasp? |
| 05:14 | <wirepair> | open web application security |
| 05:14 | <wirepair> | basically a commitee for web application security |
| 05:14 | <MikeSmith> | ah |
| 05:14 | <MikeSmith> | cool |
| 05:14 | <wirepair> | but looks like this year gettign some representation from the browser community |
| 05:14 | <wirepair> | i see 5 people or so from mozilla attending |
| 05:15 | <wirepair> | more and more web app + browser security is becoming entwined |
| 05:15 | <MikeSmith> | where's the attendee list? |
| 05:15 | <wirepair> | http://www.owasp.org/index.php/Summit_2011#tab=Attendees_And_Sponsors |
| 05:15 | <artenix> | Tnx both of you. I will read it. Is W3C HTML5 final spec spected on 2011? |
| 05:15 | <wirepair> | ah. MS people as well |
| 05:16 | <MikeSmith> | artenix: the spec development is ongoing and will continue to be refined after we start in earnest on a test suite |
| 05:17 | <MikeSmith> | and as the implementations get refined |
| 05:17 | <MikeSmith> | there's not much point in focusing on the finality of the spec |
| 05:18 | <MikeSmith> | the important milestones are really around what actually gets implemented across browsers |
| 05:19 | <artenix> | cool. implementations are always better than documents :-) |
| 05:19 | <MikeSmith> | yeah |
| 05:19 | <MikeSmith> | wirepair: you might encourage abarth to attend if he's not planning to already |
| 05:19 | <wirepair> | i don't really know him personally, but if i see him on irc i'll /msg him :) |
| 05:20 | <wirepair> | but yeah it would be good to have him there i think |
| 05:20 | <abarth> | i'm here on IRC :) |
| 05:20 | <wirepair> | oh hi :) |
| 05:21 | <wirepair> | so, every year there is a web application summit hosted by owasp, this year there is some representation from the browser community |
| 05:21 | <wirepair> | in particular microsoft and mozilla |
| 05:21 | <abarth> | (reading the wiki) |
| 05:21 | <wirepair> | if you're interested i could shoot over an email to justin clarke who is as far as i know organizing this |
| 05:22 | <artenix> | I'm from México, programmed before HTML 4 and XML, and want to see a giant leap on Web apps. kudos for WHATWG. |
| 05:22 | <abarth> | in general, i'm trying to travel less these days |
| 05:22 | <abarth> | sounds cool though |
| 05:22 | <wirepair> | yeah, it's in lisbon so.. kind of a hike |
| 05:23 | <Hixie> | AryehGregor: make it all public domain so that there's no restriction on who can reuse it or how |
| 05:23 | <MikeSmith> | artenix: hanging out on this channel is a great way to get up to speed |
| 05:23 | <Hixie> | AryehGregor: google has no interest in owning the copyright on standards stuff, we just want to have them exist so we get better interop |
| 05:23 | <MikeSmith> | the #html5 channel as well |
| 05:23 | <artenix> | Time to read, have nice day |
| 05:23 | <MikeSmith> | artenix: vaya con dios |
| 05:24 | <artenix> | Will visit html5 then. |
| 05:24 | <artenix> | S/then/too |
| 05:24 | <artenix> | Mike Spanish? |
| 05:25 | <MikeSmith> | artenix: that's about all the Spanish I know |
| 05:25 | <artenix> | HTML5 es grandioso = HTML5 is great. :-) see you all |
| 05:26 | <MikeSmith> | cheers |
| 05:27 | <MikeSmith> | Hixie: would be interested in knowing if you have thoughts about http://www.w3.org/Bugs/Public/show_bug.cgi?id=11597 at this point |
| 05:27 | Hixie | looks |
| 05:28 | <Hixie> | ' is a valid URL?! |
| 05:28 | <MikeSmith> | yup |
| 05:28 | <MikeSmith> | wacky |
| 05:28 | <Hixie> | you have got to be kidding me |
| 05:28 | <MikeSmith> | heh |
| 05:29 | <Hixie> | is " allowed also? |
| 05:29 | <MikeSmith> | yeah |
| 05:29 | <wirepair> | hu, i didn't know that |
| 05:29 | <Hixie> | are you sure? |
| 05:30 | <Hixie> | that seems seriously wacked |
| 05:30 | <Hixie> | even for, you know, the uri spec |
| 05:30 | <MikeSmith> | I am pretty sure |
| 05:30 | <MikeSmith> | I discussed it with Julian earlier |
| 05:30 | <MikeSmith> | which is what resulted in that bug getting raised |
| 05:31 | <MikeSmith> | I'm interested because I want to add additional checking to the validator for the case of " or ' in the url part of meta refresh |
| 05:32 | <Hixie> | commented on the bug |
| 05:32 | <MikeSmith> | the proposal of adding a new "valid optionally quoted URL" microsyntax seems sound |
| 05:32 | MikeSmith | reads bug comment |
| 05:32 | <wirepair> | just out of curiousity, what characters *are* invalid? |
| 05:33 | <MikeSmith> | …but "...a valid URL that does not contain any literal U+0027APOSTROPHE (') or U+0022 QUOTATION MARK (") characters" wfm too |
| 05:33 | <MikeSmith> | wirepair: whitespace |
| 05:33 | <Hixie> | if there are other places that do this, then yeah... are there? |
| 05:34 | <Hixie> | there's all kinds of things that are invalid in various parts of URLs |
| 05:34 | <zcorpan> | MikeSmith: it should be ok to do URL='foo"bar' or URL="foo'bar" |
| 05:35 | <MikeSmith> | zcorpan: why would somebody want to do that? |
| 05:35 | <MikeSmith> | the bar is just going to be ignored |
| 05:35 | <zcorpan> | MikeSmith: no it's isn't |
| 05:35 | <MikeSmith> | it is if it's in the refresh value |
| 05:36 | <MikeSmith> | which is the only case I care about at the moment |
| 05:36 | <zcorpan> | no it isn't :) |
| 05:37 | <MikeSmith> | zcorpan: so Julian's description in that bug is wrong, then? |
| 05:37 | <zcorpan> | MikeSmith: no |
| 05:37 | <MikeSmith> | oh |
| 05:37 | <zcorpan> | MikeSmith: Julian's case is 'foo'bar' |
| 05:37 | <MikeSmith> | yeah, I see, different case |
| 05:38 | <MikeSmith> | so Julian's proposal of adding a new "valid optionally quoted URL" microsyntax seems better than "...a valid URL that does not contain any literal U+0027 APOSTROPHE (') or U+0022 QUOTATION MARK (") characters" |
| 05:39 | <Hixie> | having a microsyntax for one case is dumb :-) |
| 05:41 | <zcorpan> | the spec should just ban " and ' as the first character of the URL |
| 05:41 | <Hixie> | that'd be fine too |
| 05:41 | <MikeSmith> | that also would work fine for me too |
| 05:41 | <zcorpan> | since currently it doesn't try to make quoted url conforming |
| 05:41 | <MikeSmith> | easy to implement |
| 05:42 | <Hixie> | commented again to that effect |
| 05:42 | <MikeSmith> | thanks |
| 05:43 | <benschwarz> | Hixie: I don't have permissions to read from the directory that you pointed me to |
| 05:44 | <Hixie> | oh, right |
| 05:44 | <Hixie> | just grab it from the website i guess |
| 05:45 | <benschwarz> | http://svn.whatwg.org/webapps/, index, right? |
| 05:45 | <Hixie> | the most reliable URL to grab from is http://www.whatwg.org/specs/web-apps/current-work/ |
| 05:45 | <Hixie> | (same file, but sometimes svn goes down) |
| 05:46 | <Hixie> | (whereas if the other url is down, nothing is gonna work on developers.whatwg.org either :-) ) |
| 05:46 | <benschwarz> | Hixie: single file html? |
| 05:46 | <benschwarz> | I thought we were going to aim for the multiple file version? |
| 05:46 | <Hixie> | yup |
| 05:47 | <benschwarz> | ok. |
| 05:47 | <Hixie> | oh i assumed your build makefile thing did the splitting |
| 05:47 | <Hixie> | there's a script philip` set up that does the splitting if you need it |
| 05:48 | <benschwarz> | Hixie: yeah, I'll need that |
| 05:48 | <benschwarz> | unless MikeSmith can tie up my confusion :) |
| 05:49 | <Hixie> | MikeSmith has the script, or some version of it |
| 05:49 | <Hixie> | failing that Philip` does too |
| 05:49 | MikeSmith | looks for the URL |
| 05:49 | <Hixie> | (i actually just farm out the file to a CGI script on Philip`'s site that then returns me a tarball) |
| 05:49 | <Hixie> | (so i don't have a copy myself) |
| 05:50 | <MikeSmith> | http://code.google.com/p/html5/source/browse/trunk/spec-splitter/ |
| 05:50 | <MikeSmith> | I made some modifications to it for the dev.w3.org version |
| 05:50 | <MikeSmith> | but not sure if those would be relevant outside |
| 05:50 | MikeSmith | peruses the changes |
| 05:52 | <MikeSmith> | seems I added some stuff related to generating the index of terms |
| 05:52 | <MikeSmith> | but not sure if you want to use that |
| 05:52 | <benschwarz> | MikeSmith, Hixie, this is the Makefile that I have from the previous work I did. |
| 05:52 | <benschwarz> | https://gist.github.com/767586 |
| 05:53 | <MikeSmith> | man that's ugly |
| 05:53 | <MikeSmith> | benschwarz: you don't need most of that |
| 05:54 | <MikeSmith> | I think all you really need from that is the MANIFEST target |
| 05:54 | <MikeSmith> | which is what runs the splitter |
| 05:54 | <MikeSmith> | in the ugly makefile |
| 05:55 | <MikeSmith> | and the grep and perl stuff in there is only for the purpose of figuring out the filenames and writing them to that manifest |
| 05:56 | <MikeSmith> | and the manifest is really only useful for the clean target |
| 05:57 | <MikeSmith> | so really all you probably need is the $(PYTHON) $(PYTHONFLAGS) $(SPLITTER) $(SPLITTERFLAGS) $< part |
| 05:58 | <MikeSmith> | and maybe you don't even really need to use a makefile at all, but just put it into a shell script |
| 05:58 | <benschwarz> | so, just the `make manifest` block |
| 05:58 | <benschwarz> | ? |
| 05:58 | <MikeSmith> | yeah |
| 05:59 | <MikeSmith> | with the dependency being the full spec source |
| 05:59 | <MikeSmith> | that is, instead of "spec.html", just whatever source you pull from Hixie -- "complete.html" or "index" |
| 05:59 | <MikeSmith> | oh |
| 06:00 | <MikeSmith> | strike that |
| 06:00 | <MikeSmith> | you will first need to do something to filter out the class=impl parts |
| 06:01 | <MikeSmith> | I guess you could reuse that xslt stylesheet I have there |
| 06:01 | <MikeSmith> | oh wait |
| 06:02 | <MikeSmith> | the stylesheet doesn't do that part |
| 06:02 | <MikeSmith> | anolis does |
| 06:02 | <MikeSmith> | so you should keep the spec.html target |
| 06:02 | <MikeSmith> | but remove the xslt stuff from it |
| 06:03 | <benschwarz> | forgive me, but how confusing! |
| 06:04 | <MikeSmith> | benschwarz: https://gist.github.com/767595 |
| 06:04 | <benschwarz> | thats all that I need? |
| 06:05 | <MikeSmith> | hang on, I'll edit down the whole makefile to what you need |
| 06:05 | <benschwarz> | legend! |
| 06:12 | <MikeSmith> | benschwarz: ok, updated https://gist.github.com/767595 |
| 06:13 | <MikeSmith> | ah wait |
| 06:13 | <MikeSmith> | you probably don't want "--enable terms" for now |
| 06:13 | <MikeSmith> | it will add a bunch of time to the build if you use it |
| 06:14 | <MikeSmith> | ok, removed that from the gist |
| 06:15 | <MikeSmith> | oh, need to remove "-make-index-of-terms" |
| 06:16 | <MikeSmith> | (updated) |
| 06:24 | <zcorpan> | MikeSmith: for title, script, style, etc, the validator just says "Error: End of file seen when expecting text or an end tag." and marks the last character of the file |
| 06:24 | <MikeSmith> | zcorpan: hmm |
| 06:25 | <MikeSmith> | yeah, that ain't good |
| 06:25 | <MikeSmith> | we will need to further refine Henri's refinement of my original patch |
| 06:27 | <MikeSmith> | Henri asked why I had implemented it using some additional lists (as stacks, basically) instead of just using the existing stack the parser already maintains |
| 06:27 | <MikeSmith> | and I couldn't remember at the time why |
| 06:27 | <MikeSmith> | now I remember :) |
| 06:29 | <MikeSmith> | but I guess it is better for the long term to have it implemented the way he refined it (by saving the location information in the existing stack) |
| 06:30 | <MikeSmith> | because there are probably other ways in which that will prove useful eventually |
| 06:30 | <MikeSmith> | so I guess I need to figure out how I can work with it to get it to handle the title, script, style cases |
| 06:30 | <MikeSmith> | as well as have it not report duplicate errors |
| 06:31 | <MikeSmith> | e.g., for http://www.w3.org/html/check?doc=data%3Atext%2Fhtml%3Bcharset%3Dutf-8%2C%3C%21DOCTYPE%2520html%3E%250A%3Ctitle%3E%3C%252Ftitle%3E%250A%3Cp%3E%3Cb%3E%3Ci%3E%3C%252Fp%3E%250A |
| 06:32 | <MikeSmith> | for data:text/html;charset=utf-8,<!DOCTYPE%20html>%0A<p><i><b><%2Fp>%0A<%2Fbody> |
| 06:51 | <benschwarz> | MikeSmith: https://github.com/benschwarz/developers.whatwg.org |
| 06:51 | <benschwarz> | ;) |
| 06:53 | <Hixie> | you probably don't need the --w3c flag either :-) |
| 06:53 | <Hixie> | not sure what it does though so i could be wrong |
| 06:53 | <MikeSmith> | yeah, don't need it |
| 06:53 | MikeSmith | updates the gist |
| 06:54 | <Hixie> | also you probably want .../, not .../complete.html |
| 06:54 | <Hixie> | since complete.html contains a bunch of stuff for which i haven't added the class=impl annotations |
| 06:54 | <Hixie> | and for which i haven't written the domintro blocks |
| 06:55 | <MikeSmith> | ah |
| 06:56 | MikeSmith | updates the gist |
| 07:24 | <hsivonen> | MikeSmith: good point about duplicates. I have designed a fix (makin a taintable subclass of LocatorImpl and making cloned elements share one locator object so that they share taint) |
| 07:24 | <hsivonen> | MikeSmith: I'll implement later today when I get to my better text input method |
| 07:26 | <MikeSmith> | hsivonen: sounds great |
| 07:31 | <MikeSmith> | hsivonen: the case that Simon mentioned will seem to require additional/different finagling |
| 07:31 | <MikeSmith> | that is, unclosed title, script, style |
| 08:16 | <benschwarz> | Philip`: in the edition of the spec that I'm messing around with–spec-splitter.py adds a second doctype… Are you aware of this happening for anything else? |
| 08:40 | <MikeSmith> | heh, "XML is like violence — if it doesn’t solve your problems, you are not using enough of it" |
| 08:40 | <MikeSmith> | I guess that motto has been around for a while |
| 08:40 | <MikeSmith> | dunno how I missed it so far |
| 09:03 | <MikeSmith> | Hixie: if you still awake, can you get the spec ready for WD publication on Jan 13 |
| 09:55 | <hsivonen> | looks like reporting the unclosed elements as errors is yet another nail in the coffin of test cases testing the exact number of parse errors for number > 0 |
| 09:57 | <MikeSmith> | hsivonen: yeah |
| 10:49 | <annevk> | updated http://wiki.whatwg.org/wiki/Companion_specifications#DOM |
| 10:50 | <MikeSmith> | annevk: can you make any needed updates to the html4-diffs doc for publication on the 13th? |
| 10:51 | <Philip`> | benschwarz: I think I may have had doctype-related issues when changing between different versions of lxml |
| 10:51 | <benschwarz> | Philip`: cool… just wanted to give you a heads up |
| 10:52 | <Philip`> | I think I just made it so it works on my own machine, which is all that matters to me :-) |
| 10:52 | <annevk> | MikeSmith, yeah, that's doable |
| 10:54 | <MikeSmith> | annevk: OK |
| 10:54 | <MikeSmith> | so if you can please get it ready I'd appreciate it |
| 10:59 | <annevk> | MikeSmith, is it ok after the weekend? |
| 10:59 | <annevk> | MikeSmith, or during? |
| 10:59 | <MikeSmith> | after is fine |
| 11:45 | <hsivonen> | I wonder how this WebKit bug came into being: https://bugs.webkit.org/show_bug.cgi?id=48593 |
| 11:46 | <hsivonen> | was someone trying to be helpful instead of reading specs? |
| 11:46 | <hsivonen> | or did someone accidentally lump comment nodes together with text and CDATA nodes in a branch condition somewhere? |
| 11:48 | <annevk> | sort of curious what happens with processing instructions now |
| 11:56 | <MikeSmith> | hsivonen: I have a simple patch for the xmlparser that I've also been meaning to ask you about |
| 11:56 | <MikeSmith> | for addressing http://bugzilla.validator.nu/show_bug.cgi?id=805 |
| 11:57 | <MikeSmith> | dude is getting a "Error: The shape attribute on the a element is obsolete" for all a elements in his source despite not having any shape attribute on any of them |
| 11:58 | <MikeSmith> | due to the fact that he's selected "XML: load external entities" |
| 11:58 | <MikeSmith> | so the parser is reading the DTD and defaulting the shape attribute to "rect" |
| 11:58 | <MikeSmith> | because that's what the DTD requires |
| 11:59 | <MikeSmith> | but it's not something that's obvious at all to most end users |
| 11:59 | <annevk> | http://www.w3.org/Bugs/Public/show_bug.cgi?id=11124 -- consider doing A; considered A and rejected it; omg TrackerIssue! |
| 12:00 | <MikeSmith> | hsivonen: hence the proposed patch: https://bitbucket.org/validator/xmlparser-patches/qseries?apply=t&qs_apply=warn-default-attrs |
| 12:00 | <annevk> | editorial stuff that ends up as TrackerIssue is soooo... *yawn* |
| 12:03 | <MikeSmith> | if somebody adds the TrackerRequest keyword, the decision policy requires the chairs to issue-ify it |
| 12:05 | <MikeSmith> | though I guess that's not one that seems like it should merit much of everybody else's attention |
| 12:06 | <hsivonen> | MikeSmith: r=hsivonen |
| 12:06 | <hsivonen> | on the patch |
| 12:06 | <MikeSmith> | cool |
| 12:06 | <MikeSmith> | thanks |
| 12:06 | <MikeSmith> | wording is OK? |
| 12:06 | <MikeSmith> | no tweaks to suggest? |
| 12:06 | <hsivonen> | yes |
| 12:07 | <hsivonen> | yes to OK. no tweaks to suggest. |
| 12:07 | <MikeSmith> | ok |
| 12:08 | <hsivonen> | so what's the point of having multiple SSL cert classes below EV? |
| 12:09 | <hsivonen> | aren't they equivalent to the weakest level for practical purposes anyway if they are presented the same way to the user? |
| 12:09 | <hsivonen> | that is, what's the point of getting a class 3 cert if you can get the SSL indicator in browser UI using a class 1 cert? |
| 12:10 | hsivonen | wonders why Netscape didn't build itself a business model by charging CAs for the root certs they shipped |
| 12:16 | <Philip`> | Nobody would have paid to become a CA before SSL became popular enough to make it clear that it was worth it |
| 12:17 | <Philip`> | and once SSL became popular enough, Netscape couldn't demand money from CAs because the CAs could say no and Netscape couldn't remove them without hurting their users who want their online banks to continue working |
| 12:17 | <Philip`> | perhaps |
| 12:22 | <annevk> | CAs always seem kind of dodgy to me |
| 12:43 | <benschwarz> | ping! Hixie |
| 12:49 | <annevk> | benschwarz, not sure what timezone you are on, but Hixie seems to have adjusted his schedule to be slightly more sane (he's in California) |
| 12:49 | <benschwarz> | AEST |
| 12:49 | <benschwarz> | and I thought as much |
| 12:50 | <benschwarz> | I was just hopeful |
| 12:50 | <annevk> | Australia; tough :) |
| 13:04 | <annevk> | "For the first time, we included HTML5 H.264 video directly in posts." -- IEBlog |
| 13:13 | <annevk> | what is Mounir's IRC nick again? |
| 13:16 | <volkmar> | annevk: volkmar |
| 13:16 | <annevk> | ah right |
| 13:16 | <annevk> | so why can't the comma thing only be relevant for serialization? |
| 13:17 | <annevk> | it seems you don't want to remove it while the user is still editing |
| 13:18 | <volkmar> | what do you mean? |
| 13:20 | <annevk> | your solution 1 would do that |
| 13:23 | <volkmar> | annevk: my solution 1 would remove the last comma in the DOM if there is nothing else than trailing whitespaces after it |
| 13:26 | <MikeSmith> | tried https://github.com/aredridel/html5 -- HTML5 parser for node.js -- and seems usable |
| 13:26 | <MikeSmith> | though slow |
| 13:26 | <MikeSmith> | slower than html5lib |
| 13:27 | <MikeSmith> | 1m47.097s to parse the HTML5 spec on my machine, versus 0m51.145s with html5lib |
| 13:27 | <annevk> | volkmar, but the user would still have it? |
| 13:28 | <annevk> | I guess it depends on what the field looks like :) |
| 13:28 | <annevk> | ideally it probably does not involve the user actually having to type commas |
| 13:28 | <hsivonen> | MikeSmith: what's the most popular XML tree representation for node.js? Does aredriedel's parser use whatever the most popular tree is? |
| 13:29 | hsivonen | should learn about node.js some day |
| 13:30 | <hsivonen> | I wonder if the GWT compiler manages to produce code that has few enough browser deps to work on node.js |
| 13:30 | <MikeSmith> | yeah, would be great if it did |
| 13:31 | <MikeSmith> | hsivonen: dunno which tree APIs are available now for node and which ones others might be using |
| 13:31 | <hsivonen> | ok :-( |
| 13:31 | <MikeSmith> | but things are still changing pretty rapidly in node-land |
| 13:32 | <MikeSmith> | but aredridel seems to have his head in the right place |
| 13:33 | <MikeSmith> | see the "Interesting features" part of https://github.com/aredridel/html5#readme |
| 13:33 | <MikeSmith> | [[ |
| 13:33 | <MikeSmith> | Streaming parser: You can pass parser.parse an EventEmitter and the parser will keep adding data as it's received. |
| 13:33 | <MikeSmith> | HTML5 parsing algorithm. If you find something this can't parse, I'll want to know about it. It should make sense out of anything a browser can. |
| 13:33 | <MikeSmith> | ]] |
| 13:34 | <MikeSmith> | hsivonen: anyway, I think hober is probably a lot more current than me around the state of the parsing and document API stuff in node |
| 13:34 | <MikeSmith> | jsdom |
| 13:38 | <MikeSmith> | window = jsdom.createWindow(null, null, {parser: HTML5}); |
| 13:38 | <MikeSmith> | jsdom.jQueryify(window, 'deps/jquery/dist/jquery.js', function(window, jquery) { |
| 13:38 | <MikeSmith> | Script.runInNewContext('jQuery("p").append("<b>Hi!</b>")', window); |
| 13:38 | <MikeSmith> | sys.puts(window.document.innerHTML); |
| 13:38 | <MikeSmith> | interesting |
| 13:38 | <volkmar> | annevk: if there is a UI for autocompletion for example, it needs to know which token is currently edited so when you select on item in the list a comma needs to be added |
| 13:38 | <volkmar> | that way you can select multiple values one after the other |
| 13:39 | <volkmar> | but this comma should not block the form submission |
| 13:39 | <volkmar> | and i don't see anything changed in the specs to make this happen |
| 13:40 | <hsivonen> | MikeSmith: is that jsdom a DOM impl. in pure JS? |
| 13:40 | <MikeSmith> | yes |
| 13:40 | <hsivonen> | MikeSmith: does it do Level 2? |
| 13:40 | <MikeSmith> | yeah, it does now, I think |
| 13:41 | <MikeSmith> | did not initially |
| 13:41 | <MikeSmith> | but was added within the last few months |
| 13:41 | <hsivonen> | well, then it should be easy to use the V.nu parser on node.js |
| 13:41 | <hsivonen> | might be worth trying if it already runs as-is |
| 13:42 | <MikeSmith> | see https://github.com/tmpvar/jsdom/blob/master/example/browser/browser.js |
| 13:42 | <hsivonen> | assuming node.js has setTimeout() |
| 13:42 | <MikeSmith> | it does |
| 13:42 | <MikeSmith> | it has everything that V8 has currently |
| 13:43 | <hsivonen> | I really should play with node.js some time |
| 13:43 | <MikeSmith> | yeah |
| 13:43 | <MikeSmith> | I definitely recommend it |
| 13:43 | <MikeSmith> | just hard to keep up with because things are getting changed/added daily |
| 13:43 | <MikeSmith> | embarrassment of riches |
| 13:44 | <MikeSmith> | #Node.js channel is a good place to reach some of the core node devs |
| 13:44 | <hsivonen> | ok. I implemented duplicate error suppression for unclose elements |
| 13:44 | <MikeSmith> | oh cool |
| 13:44 | <MikeSmith> | you fast |
| 13:44 | <hsivonen> | I'll get it pushed. |
| 13:46 | <annevk> | volkmar, how does the "latest values" concept not work? |
| 13:47 | <annevk> | although it does not seem entirely clear how everything fits together :/ |
| 13:47 | <hsivonen> | MikeSmith: writing code in Java without proper unit tests is so much faster than writing C++ with unit tests. |
| 13:47 | <MikeSmith> | heh |
| 13:52 | <artenix> | Hi. Is this a channel to discuss the HTML5 spec doc on w3c site? |
| 13:53 | <volkmar> | annevk: for what i understand, the "latest values" concept doesn't take into account the case where the last value is the empty string after removing whitespaces |
| 13:53 | <Philip`> | artenix: Yes |
| 13:53 | <volkmar> | so "a, b, c, " will be changed to "a,b,c," |
| 13:54 | <artenix> | Philip tnx. One sentence says: "Another example of the mark element is highlighting parts of a document that are matching some search string. If someone looked at a document, and the server knew that the user was searching for the word "kitten", then the server might return the document with one paragraph modified as follows" I remember Google has been granted a patent for doing something very similar |
| 13:56 | <annevk> | volkmar, is that actually a value though? hmm |
| 13:57 | <annevk> | I guess it should remove those that are empty from latest values just in case |
| 14:00 | <artenix> | it is just an example of use of mark tag, but it sounds like google's patent |
| 14:01 | <annevk> | artenix, well, the W3C has a Patent Policy and Google is a member of the group |
| 14:02 | <artenix> | im just a developer not a lawyer |
| 14:03 | <artenix> | Annevk so there is ok to have that example on spec right? |
| 14:03 | <artenix> | s/there is/is it |
| 14:05 | <MikeSmith> | hsivonen: have you ever done any benchmarking with the GWT version of the parser? |
| 14:05 | <annevk> | well, I'm not a lawyer either, but the basic idea is that if a Member organization holds a patent on some technology in a specification, which the Member organization helps developing through a W3C Working Group, the Member organization gives away a RF-license for said patent for everyone to use |
| 14:07 | <artenix> | annvek cool I was not aware of that. Tnx! Have to go. See you all later. |
| 14:13 | <hsivonen> | MikeSmith: I have but JS engines and JS-to-DOM glue have improved since then |
| 14:14 | <MikeSmith> | ok |
| 14:14 | <hsivonen> | MikeSmith: back in the Firefox 3.5 days, either DOM/layout dominated or the code didn't get traced |
| 14:14 | <hsivonen> | MikeSmith: because back then tracer on vs tracer off showed no difference |
| 14:15 | <MikeSmith> | I see |
| 14:16 | <MikeSmith> | well, current node -- 0.3 -- is up to date with latest V8 I think |
| 14:16 | <MikeSmith> | so in addition to the performance stuff that was there already, it has the crankshaft optimizations that were added more recently |
| 14:43 | <annevk> | https://github.com/aredridel/html5 didn't know about this |
| 14:43 | <annevk> | cool |
| 16:28 | <webr3> | I've just said: "one huge ommission from html imho, is that you can't include remote document fragments, would cater for many needs which are thrown on to "ajax" and iframes" - and somebodies replied that you can do this in HTML5 |
| 16:28 | <webr3> | is that right? pointer to a spec or section? |
| 16:31 | <annevk> | <iframe>? |
| 16:32 | <MikeSmith> | XHR.responseText… |
| 16:32 | <webr3> | nah, more like an ssi where the document fragment becomes part of the main doc context, not in it's own frame/context |
| 16:32 | <Philip`> | <iframe seamless>? |
| 16:32 | <webr3> | Philip` that may be it, will check |
| 16:33 | <annevk> | SSI is server-side |
| 16:33 | <annevk> | and the rest is details, really |
| 16:33 | <Philip`> | It's still like an iframe in the DOM, so it doesn't introduce scary security issues, but should render less like an independent frame |
| 16:34 | <webr3> | Philip` cool - cheers |
| 16:34 | <annevk> | <iframe sandbox seamless> to be totally safe |
| 16:34 | <annevk> | but it's just a specific form of <iframe> |
| 16:36 | <webr3> | and iframes allow document fragments (as in no html/head/body etc?) |
| 16:36 | <webr3> | and can inherit css from main doc? |
| 16:38 | <annevk> | former no, latter yes |
| 16:39 | <webr3> | annevk, ty |
| 16:39 | <Philip`> | Full documents don't need html/head/body tags, though |
| 16:40 | <Philip`> | so you can write something that looks a lot like a fragment |
| 16:40 | <webr3> | is doctype still required? |
| 16:41 | <webr3> | our would say "<ul><li>foo</li></ul>" w/ text/html media type be "valid" html? |
| 16:42 | <annevk> | need doctype |
| 16:42 | <annevk> | except maybe in srcdoc="" |
| 16:43 | <Philip`> | Hmm, also need <title> unless it's in srcdoc |
| 16:43 | <webr3> | Philip`, ty that was my next question lol |
| 16:43 | <Philip`> | Maybe it's not quite so fragmenty, then :-( |
| 16:44 | <webr3> | would be nice if there was a media-type for html fragments, w/ +xml variant for the obvious |
| 16:45 | <annevk> | what's wrong with merging server-side? |
| 16:45 | <webr3> | cacheing, network effects etc etc |
| 16:45 | <webr3> | anyhow, random train of thought, which I've not thought about long enough to warrent a full discussion (or for me to back up why I'm asking ;) |
| 16:45 | <webr3> | tyvm :) |
| 16:46 | <annevk> | right... would need to be researched first before we add a bunch more complexity |
| 16:46 | <webr3> | exactly |
| 16:47 | <annevk> | typically though not having to do an additional request wins from caching |
| 16:47 | <annevk> | this is also e.g. why google.com has a bunch of stuff inlined rather than as external resource |
| 17:27 | <Ms2ger> | Hixie, ping |
| 17:42 | <charlvn> | i seem to be getting "This is a work in progress!" on the actual editors draft which the message links to |
| 17:46 | <annevk> | that's temporary |
| 17:47 | <annevk> | we're about to publish drafts |
| 17:53 | <charlvn> | cool np |
| 18:07 | <Hixie> | Ms2ger: pong |
| 18:11 | <annevk> | shit |
| 18:11 | <annevk> | I replied on public-html |
| 18:34 | <annevk> | Hixie, I think what volkmar is missing is that the empty string is not a value |
| 18:35 | <Hixie> | ah |
| 18:35 | <annevk> | e.g. if the user has a@a,b@b,c@c and then deletes b@b through backspace from his list |
| 18:35 | <Hixie> | well we'll see when he replies i guess |
| 18:35 | <annevk> | or deletes c@c but not the comma |
| 18:35 | <Hixie> | hey does hallvord ever hang out on irc? |
| 18:35 | <annevk> | seldomly |
| 18:35 | <Hixie> | k |
| 18:36 | <annevk> | -ly, apparently |
| 18:38 | <Hixie> | afk, bbiab |
| 18:40 | <Philip`> | If I want to display some program code with <pre><code>... the code ...</code></pre>, and then want to insert some annotations inline to highlight particular features (like "// This section is setting up stuff for the thing", probably rendered in a different colour), what's appropriate markup? |
| 18:40 | <annevk> | http://www.asymco.com/2011/01/06/this-is-the-most-exciting-ces-ever/ |
| 18:41 | <annevk> | "These actions confirm the end of the PC era." |
| 18:44 | <charlvn> | why does this sound so familiar... oh yes 10 years ago the media said the same thing :P |
| 18:44 | <volkmar> | Hixie: so "a@a, b@b, c@c," should be reprensented as "a@a,b@b,c@c" in the DOM? |
| 18:45 | <charlvn> | oh wait, after reading the post it seems it was just misworded. should have been "end of the windows era" |
| 18:46 | <AryehGregor> | Hixie, you told me in an e-mail on November 29 that all spec prose and tests are supposed to be copyright Google. |
| 18:46 | <annevk> | volkmar, the basic idea is that what the user sees is "irrelevant" |
| 18:46 | <volkmar> | annevk: i got that |
| 18:47 | <annevk> | volkmar, so if you have a bunch of values the user entered and want to serialize them, you end up with your second representation |
| 18:47 | <annevk> | assuming the values were a@a / b@b / c@c |
| 18:48 | <annevk> | but if the user enters these space-separated, comma-separated, colon-separated, or via some kind of better UI is very much up to the UA |
| 18:48 | <volkmar> | annevk: it's not clear to me that the serialization algorithm doesn't take into account empty values |
| 18:48 | <annevk> | yeah, when I told Hixie that he said "well we'll see when he replies i guess" |
| 18:50 | <annevk> | I wonder if it is implied somehow because everywhere else empty is equal to no value, but it would not hurt if it was made more explicit |
| 18:52 | <Workshiva> | annevk: The article also seems to ignore the existence of AMD |
| 18:53 | <annevk> | AMD? |
| 18:53 | <Workshiva> | You know, the company that isn't intel but still makes CPUs |
| 18:59 | <Philip`> | The one that's less than 20% of the x86 CPU market? |
| 19:07 | <Workshiva> | Philip`: What percentage of the PC market does ARM currently have? :) |
| 19:08 | <Philip`> | ARM doesn't make processors so it has zero percent in any market :-p |
| 19:08 | <Workshiva> | Besides, Microsoft long ago decided to port windows to x64, an architecture from Intel's arch enemy. |
| 19:09 | <mpilgrim> | ah Philip`, always the pedant |
| 19:12 | <Philip`> | Workshiva: Intel could (and did) adopt and extend the x64 architecture (because of patent cross-licensing), so that didn't hurt them - they just implemented it and took all the market share |
| 19:12 | <Philip`> | I expect they can't do that with ARM architectures |
| 19:14 | <AryehGregor> | Didn't I just read that NVIDIA is expanding into ARM? |
| 19:14 | <AryehGregor> | It would be cool if ARM killed x86 sometime, but it seems unlikely as long as Windows remains the dominant OS. Windows is a pretty lame contender without the massive base of binary applications. |
| 19:15 | <Workshiva> | And the massive base of existing hardware |
| 19:15 | <Philip`> | http://pressroom.nvidia.com/easyir/customrel.do?easyirid=A0D622CE9F579F09&version=live&releasejsp=release_157&xhtml=true&prid=705184 |
| 19:15 | <Philip`> | "NVIDIA announced today that it plans to build high-performance ARM® based CPU cores, designed to support future products ranging from personal computers and servers to workstations and supercomputers." |
| 19:16 | <AryehGregor> | Workshiva, people replace their hardware every few years, that's no issue if their software continues to work. |
| 19:16 | <AryehGregor> | So is NVIDIA planning to back Linux and kill Microsoft, or get Mac to switch its CPU architecture for a second time in a few years, or what? |
| 19:17 | <Workshiva> | Did you miss the announcement of Windows 8 supporting ARM? |
| 19:17 | <Philip`> | AryehGregor: http://blogs.nvidia.com/2011/01/project-denver-processor-to-usher-in-new-era-of-computing/ - "Microsoft’s announcement that it is bringing Windows to ultra-low power processors like ARM-based CPUs provides the final ingredient needed to enable ARM-based PCs based on Denver." |
| 19:17 | <AryehGregor> | Ah. |
| 19:17 | <Philip`> | Sounds like they're happy to stick with Microsoft |
| 19:17 | <AryehGregor> | Yeah, but who's actually going to use Windows if you can't get all the applications? |
| 19:18 | <AryehGregor> | I'd think it'd be squarely worse than Linux in that case. |
| 19:18 | <AryehGregor> | Although maybe I'm biased, since I hate Windows. And hate Linux significantly less (usually). |
| 19:19 | <Philip`> | I thought people didn't use applications nowadays, except for Office and a web browser |
| 19:19 | <Philip`> | which Microsoft are porting to ARM |
| 19:19 | <Workshiva> | You'd be surprised how bad Linux is without a fiercely devoted relative tech support |
| 19:20 | <AryehGregor> | Windows can be pretty terrible too if you don't have a relative for tech support. |
| 19:20 | <Workshiva> | With Windows everyone is your tech support |
| 19:20 | <AryehGregor> | What with all the viruses and such. Although granted, when it fails, it usually doesn't fail as horribly. |
| 19:20 | <AryehGregor> | True. |
| 19:20 | <AryehGregor> | Well, we'll see. |
| 19:20 | <AryehGregor> | Competition in the CPU market can only be a good thing. |
| 19:21 | <Philip`> | (I suppose people still run games, but usually mostly new games, and NVIDIA can ask the developers to port their new games) |
| 19:21 | <Workshiva> | I'm sure emulation isn't impossible either |
| 19:21 | <AryehGregor> | If the ARM chips are fast enough, then emulation would be workable, yeah. |
| 19:21 | <AryehGregor> | But not if we're talking low-powered notebooks where you're hoping to save lots of power. |
| 19:22 | <AryehGregor> | Philip`, games are often assembly-optimized . . . |
| 19:22 | <Philip`> | AryehGregor: Usually only tiny bits of them, and they already have to support PPC anyway (for consoles) |
| 19:23 | <Philip`> | so they already have to deal with portability issues |
| 19:26 | <annevk> | anyone been following reddit lately? http://www.reddit.com/r/reddit.com/comments/exdpc/b/ this guy really |
| 19:26 | <Workshiva> | really |
| 19:27 | <miketaylr> | annevk: that Sure_Ill_Draw_That guy is awesome |
| 19:27 | <Hixie> | volkmar: what do you mean by "a@a, b@b, c@c,"? |
| 19:27 | <Hixie> | AryehGregor: copyright google works as well |
| 19:34 | <AryehGregor> | Hixie, now what spec do I submit my spec prose to for atob() and btoa()? |
| 19:34 | <AryehGregor> | (in case you didn't see the latest version: http://aryeh.name/tmp/spec.html) |
| 19:35 | <Hixie> | they're on Window? |
| 19:35 | <Hixie> | i guess the html spec |
| 19:35 | <Hixie> | unless DOM Core has any Window stuff? annevk? |
| 19:36 | <Hixie> | comments on the draft spec: |
| 19:36 | <Ms2ger> | No |
| 19:36 | <annevk> | Hixie, don't want Window |
| 19:36 | <Ms2ger> | DOM Core isn't touching Window |
| 19:36 | <Hixie> | k |
| 19:37 | <Hixie> | then yeah, html |
| 19:37 | <Hixie> | AryehGregor: send mail to whatwg with the text and link to the tests, and then when i add it to the spec we can add the tests to the htmlwg's test suite |
| 19:37 | <annevk> | One of the goals is to not reference HTML5 |
| 19:37 | <AryehGregor> | Hixie, I already added it to the HTMLWG's test suite. |
| 19:37 | <Hixie> | awesome |
| 19:37 | <Hixie> | anyawy, comments on the spec: |
| 19:38 | <Hixie> | the regexp scares me, but i can't come up with a rational argument against it. |
| 19:38 | <AryehGregor> | http://dvcs.w3.org/hg/html/ |
| 19:38 | <AryehGregor> | I tried to write it in prose, but it looked like it would be way more complicated. |
| 19:38 | <Hixie> | the "repeat" step is unclear about when you end the loop, e.g. if the input is the empty string, do you run it at least once? (that's why i end up using gotos a lot rather than structured loops... english is hard to make structured loops with) |
| 19:39 | <AryehGregor> | The Firefox implementation actually just throws exceptions at various points in the algorithm proper, but that would be significantly longer to write. |
| 19:40 | <AryehGregor> | I guess the reason against the regex is that nobody's likely to implement it that way. |
| 19:40 | <AryehGregor> | So it's harder to check if the implementation is correct by source inspection. |
| 19:40 | <AryehGregor> | Although it's easier to check that the tests are correct, since in JavaScript it's simpler. |
| 19:40 | <AryehGregor> | I dunno, do any implementers have opinions? |
| 19:41 | <AryehGregor> | As for the loop, how about: "While position does not point past the end of input:" |
| 19:41 | <AryehGregor> | That clearly suggests the C definition of "while", so I think it's nicer than a purely procedural way. Of course, we could define what we mean by "while" for extra clarity. |
| 19:42 | <AryehGregor> | But if it's going in HTML, obviously you get the final say over the exact wording, so maybe no point in nitpicking. |
| 19:42 | <AryehGregor> | (I'm sure you'll make my <ul>s into <ol>s too, even though that degrades appearance in all UAs, irreparably in non-CSS UAs.) |
| 19:42 | <annevk> | AryehGregor, what you describe under atob is not a binary string |
| 19:42 | <annevk> | AryehGregor, it's a series of octets |
| 19:43 | <AryehGregor> | What's the difference? |
| 19:43 | <annevk> | a string consists of Unicode characters, not bytes |
| 19:43 | <Hixie> | atob() takes a string as input |
| 19:43 | <annevk> | sure |
| 19:43 | <Hixie> | as does btoa() |
| 19:43 | AryehGregor | changes it to "sequence of octets" |
| 19:43 | <Hixie> | since JS only has a string type |
| 19:44 | <annevk> | you should read the spec again Hixie :) |
| 19:44 | <AryehGregor> | Not now, I've changed it. |
| 19:44 | <Hixie> | AryehGregor: btw, you wouldn't be able to rely on the regexp to do the JS tests, since that would mean that an implementation that uses the regexp engine to implement it, yet has a bug in the JS engine, would fail both the test and the control |
| 19:44 | <annevk> | it's about the input to base64 |
| 19:44 | <Hixie> | annevk: oh, my bad |
| 19:44 | <Hixie> | annevk: i thought you meant btoa() |
| 19:44 | <Hixie> | annevk: got them backwards |
| 19:44 | <AryehGregor> | It said "Otherwise, the user agent must convert [the input string] to a binary string . . ." |
| 19:45 | <AryehGregor> | Hixie, hmm. But we have ES tests for that, right? I mean, maybe there will be some bug in the browser so that the test harness is run incorrectly and sometimes reports wrong results. |
| 19:45 | <AryehGregor> | I think that if the test is written in JS, we have to assume a correct implementation of JS itself. |
| 19:45 | <annevk> | regular expressions, yay |
| 19:45 | <Hixie> | generally you want your tests to be as unlikely as possible to have false positives |
| 19:46 | <Hixie> | (false negatives, or rather, misattributed negatives, aren't a big deal) |
| 19:46 | <hsivonen> | so is this newly-announced desktop ARM stuff 32 or 64-bit? |
| 19:47 | <AryehGregor> | I could write a JavaScript file that generates the test file, but that seems excessively cumbersome for a theoretical correctness improvement. In particular, I've reviewed all the test results and they look sane, and I also happen to know that Firefox doesn't actually use a regex to throw an exception. |
| 19:47 | <Hixie> | AryehGregor: personally i'd spec it without regexp, meaning you can test it with regexp with no problem, but that's just a personal preference. regexp in the spec is fine by me from a rational perspective. :-) |
| 19:47 | <AryehGregor> | I'll change it to non-regex if implementers prefer. |
| 19:47 | <AryehGregor> | I mainly did it in regex because it was shorter to spec and easier to write the test, but it's probably more annoying to implement. |
| 19:47 | <AryehGregor> | And implementers > spec writers, after all. |
| 19:47 | <Hixie> | AryehGregor: btw, having numbers in the steps is a good thing for discussion (otherwise, refering to specific steps is a pain) |
| 19:48 | <Hixie> | AryehGregor: "While position does not point past the end of input:" seems reasonable |
| 19:48 | <hsivonen> | bah. the Ballmer keynote requires Silverlight. Not gonna install that. |
| 19:48 | <AryehGregor> | The numbers change all the time, though. That's the problem with all the numbers in HTML5. |
| 19:48 | <AryehGregor> | I originally filed feedback giving section numbers instead of names and you told me to stop because the numbers were different by the time you read the feedback. |
| 19:48 | <Hixie> | yeah but the sections have names, the steps don't :-) |
| 19:49 | <Hixie> | better to have _something_ to refer than nothing :-) |
| 19:49 | <Hixie> | anyway, <ul> is wrong because the order matters |
| 19:49 | <AryehGregor> | Using numbers creates the expectation that you'll actually refer to the numbers someplace in the prose. But you don't do that. I once suggested that you do that (or someone did) and you said you wouldn't because then you'd forget when the numbers changed and you'd make the spec wrong. |
| 19:49 | <Hixie> | yeah i used to refer to numbers and algorithms kept breaking when i changed them |
| 19:49 | <Hixie> | we really need a <ref> element to fix that |
| 19:50 | <AryehGregor> | You can give the number of the step even if it's not written down, assuming you're able to count. |
| 19:50 | <Hixie> | but that can wait til v2 |
| 19:50 | <AryehGregor> | Or just improve your preprocessor. :) |
| 19:50 | <Hixie> | hey that's not a bad idea |
| 19:50 | <Hixie> | i'll have to think about that |
| 19:50 | <Hixie> | as an anolis feature |
| 19:50 | <AryehGregor> | As for the definition, I realize that my usage is wrong according to what HTML5 says. But authoring conformance requirements in HTML5 are more or less your personal opinion, so I feel free to ignore them if I disagree. |
| 19:50 | <Hixie> | anyway, counting is fine with the btoa() algorithm, but it doesn't scale |
| 19:50 | <AryehGregor> | So quote the beginning of the step. |
| 19:50 | <Hixie> | <ol>/<ul> hasn't changed since, like, html2 |
| 19:51 | <Hixie> | hardly my opinion :-) |
| 19:51 | <hsivonen> | View Source reveals a VLC-compatible video stream. Lame to pretend that SIlverlight is needed. |
| 19:51 | <AryehGregor> | The fact that your opinion happens to accord with your predecessors' opinions on this point is immaterial. |
| 19:51 | <Hixie> | actually my opinion is that we should only have one list element |
| 19:51 | <Hixie> | i don't really see why we have two |
| 19:52 | <Hixie> | but i try not to let my opinion affect the spec _too_ much :-P |
| 19:52 | <AryehGregor> | So <list type=1> instead of <ol>, or what? You can't leave the numbering to CSS, clearly. |
| 19:52 | <annevk> | might end up with HHTML |
| 19:52 | <annevk> | if you did that |
| 19:52 | <Hixie> | AryehGregor: dunno, haven't thought about it much, since it doesn't matter :-) |
| 19:52 | <AryehGregor> | :) |
| 19:52 | <Hixie> | if i got to write HHTML according to my opinions, it would look so different it's not even funny |
| 19:53 | <Hixie> | we'd get to strip out microdata :-) |
| 19:53 | <AryehGregor> | Okay, I'll put that text at a more permanent URL and send a link to whatwg. |
| 19:53 | <Hixie> | and <object>, <div>, clas=""... |
| 19:53 | <Hixie> | AryehGregor: thanks |
| 19:53 | <Hixie> | also we'd use a totally different syntax |
| 19:53 | <annevk> | @html@ what is happening?! @-html@ |
| 19:54 | <AryehGregor> | Do I have my headings backwards? |
| 19:54 | <AryehGregor> | I have the btoa algorithm labeled atob and vice versa. |
| 19:54 | <AryehGregor> | Oops. |
| 19:54 | <annevk> | that explains why Hixie was confused |
| 19:54 | <AryehGregor> | Poof. |
| 19:54 | <Hixie> | i thought the names were a bit odd, but i just figured that it was yet more historical weirdness :-) |
| 19:55 | <annevk> | btoa (formerly atob) still says binary string |
| 19:55 | <annevk> | there were two instances originally |
| 19:56 | <AryehGregor> | I fixed that like a minute before you pointed it out. |
| 19:56 | <annevk> | no -moz-column-count and -o-column-count? |
| 19:56 | <annevk> | ninja edits... |
| 19:56 | <AryehGregor> | Oops. |
| 19:57 | <AryehGregor> | I intended to make that cross-browser but forgot about it. |
| 19:58 | <annevk> | there must be an easier way to say what you did there btw |
| 19:58 | <AryehGregor> | Which part? |
| 19:58 | <annevk> | like take the code point and subtract some amount |
| 19:58 | <AryehGregor> | (It seems like display: run-in isn't working as I expect except in WebKit.) |
| 19:58 | <AryehGregor> | You have to have about five cases then. |
| 19:58 | <Hixie> | oh one thing you should add is a class=note explaining why you didn't defer to the base64 spec for decoding |
| 19:58 | <volkmar> | Hixie: i meant "a@a, b@b, c@c, " in the UI, what should be the DOM value in that case? |
| 19:58 | <Hixie> | otherwise julian will ask me to add such a note |
| 19:58 | <AryehGregor> | It's what I do in my test implementation, but I thought it was simpler to understand at a glance if I wrote the spec this way. |
| 19:59 | <AryehGregor> | I carefully chose five columns so they'd line up nicely. |
| 19:59 | <Hixie> | volkmar: depends. Does the UI think that's four values or three? |
| 19:59 | <annevk> | AryehGregor, oh okay, then a table is probably easier |
| 20:00 | <Hixie> | volkmar: i.e. has the user entered three e-mail addresses, or has he entered four, one of which is the empty string? |
| 20:01 | <Hixie> | volkmar: it's probably easier to think about it if we describe the UI in other terms, e.g. "[a@a] [b@b] [c@c]" is obviously three items, and "[a@a] [b@b] [c@c] []" is obviously four -- which one describes what you meant? |
| 20:02 | <AryehGregor> | Note added. |
| 20:02 | <volkmar> | Hixie: if you see the control as a text field, the user can write textually "a@a, b@b, c@c, " |
| 20:02 | <AryehGregor> | Actually, come to think of it, if we threw an exception for like one more thing, I could defer to RFC 4648 for decoding too. |
| 20:02 | <volkmar> | but if you leave that choice to the UI... ok |
| 20:03 | <AryehGregor> | As far as I can tell, there's only one fairly marginal corner case of invalid input where Firefox doesn't throw an exception. |
| 20:03 | <AryehGregor> | (note in second-to-last step) |
| 20:04 | <oojacoboo> | just to clarify, <section> tags should all be on the same level, not having any child <section> elements, corect? |
| 20:04 | <Hixie> | volkmar: i dunno that atstraight text field is a particularly good UI for this, but yeah, it's up to the UA. So in this case it'd probably be most helpful if the UA considered empty strings as being entries removed from the list, and didn't include them in the /value/ |
| 20:04 | <AryehGregor> | Well, other than if the trailing = signs are missing. |
| 20:04 | <Hixie> | oojacoboo: you can nest <section> elements |
| 20:04 | <Hixie> | oojacoboo: those are subsections |
| 20:04 | <oojacoboo> | Hixie: ok, thanks |
| 20:05 | <Hixie> | oojacoboo: e.g. the example in http://www.whatwg.org/specs/web-apps/current-work/complete/sections.html#the-h1,-h2,-h3,-h4,-h5,-and-h6-elements |
| 20:05 | <Hixie> | AryehGregor: that would certainly simplify the spec! |
| 20:06 | <Hixie> | AryehGregor: you can also just hard-code the return values for specific inputs, e.g. if the empty string is an undefined case, you can just say "return the empty string" for that case and only defer to the algorithm for the well-defined cases |
| 20:06 | <AryehGregor> | Then I could specify that if you add trailing = signs, btoa(atob(s)) == s unless one of the functions throws an exception. |
| 20:06 | <oojacoboo> | Hixie: ok cool, I was under the impression that it was best not to nest, but that makes sense for sub-sections |
| 20:06 | Hixie | changes the HTML spec on the WHATWG site from "Draft Standard" to "Living Standard" to more accurately reflect reality |
| 20:06 | <AryehGregor> | That would be a good correctness check. |
| 20:06 | Ms2ger | likes |
| 20:14 | <annevk> | makes it sound like it needs watering |
| 20:15 | <Ms2ger> | Well, it does |
| 20:16 | <Hixie> | indeed |
| 20:16 | <annevk> | and I guess it grows things too |
| 20:16 | <annevk> | still |
| 20:16 | <annevk> | :) |
| 20:20 | <AryehGregor> | Okay, e-mail sent. |
| 20:21 | <AryehGregor> | I'll ask for the tests to be approved by the Testing Task Force as soon as something is added to the spec. |
| 20:22 | <AryehGregor> | hallvors is working on copy-paste stuff? Does he have a public spec, and how can I contact him? |
| 20:23 | <annevk> | see wiki.whatwg.org/wiki/Specs |
| 20:23 | <Ms2ger> | AryehGregor, he sends snapshots to public-webapps, apparently |
| 20:23 | <AryehGregor> | Oh, right, thanks. |
| 20:23 | <annevk> | his email address can be found in the archives to public-webapps |
| 20:27 | <AryehGregor> | Does the web app WG share its test suite with the HTMLWG, or is it separate? |
| 20:29 | <Ms2ger> | Officially separate |
| 20:33 | <AryehGregor> | Tiresome. |
| 20:33 | <beowulf> | hgroup, would it perhaps make things less confusing for whoever is confused if it were named <headline> ? |
| 20:33 | <AryehGregor> | Is it set up the same way, at least? |
| 20:35 | <AryehGregor> | Looks like it, so no big deal. |
| 20:37 | <annevk> | we want to use the same framework and all |
| 20:37 | <beowulf> | my reasoning, which is no doubt faulty, is that hgroup is about headlines of various types, the sort described here for example http://goo.gl/5wCVt |
| 20:38 | <Hixie> | is the title and subheading of the spec a headline? |
| 20:38 | <beowulf> | depends if the are run on i suppose |
| 20:39 | beowulf | goes to look at the spec headline |
| 20:39 | <Hixie> | top of whatwg.org/c |
| 20:39 | <Hixie> | (top of whatwg.org/C if you prefer the multipage copy) |
| 20:39 | <beowulf> | i'm tempted to say yes |
| 20:43 | <aho> | hm. hgroup>h1+h2+h2 (zen expression) is fine, too, right? |
| 20:43 | <aho> | i.e. <hgroup><h1>...</h1><h2>...</h2><h2>...</h2></hgroup> |
| 20:45 | <beowulf> | i don't understand the question :) |
| 20:45 | <aho> | well, having one h1 and two h2s there |
| 20:46 | <aho> | http://kaioa.com/k/td/docs/javascript%20code%20conventions/index.html |
| 20:46 | <aho> | rev + date got the same weight |
| 20:46 | <aho> | brs are silly :> |
| 20:47 | <beowulf> | works for me |
| 20:49 | <Philip`> | hsivonen: Since NVIDIA explicitly mentions supercomputers, it sounds quite likely that either they're thinking of 64-bit addressing or whoever wrote the press release was wildly misinformed |
| 20:50 | <Philip`> | (Looks like ARM hasn't released or announced anything 64-bit yet, though) |
| 20:50 | <AryehGregor> | Sheesh, ARM isn't 64-bit? That will have to change for the server market, let alone supercomputers. |
| 20:52 | <Philip`> | It can apparently do 1TB RAM with PAE, which is probably okay for servers that run lots of small processes |
| 20:53 | <Philip`> | (It only hurts when you need >4GB in a single virtual address space) |
| 20:55 | <AryehGregor> | Like, say, a database server. |
| 20:55 | <AryehGregor> | Or any kind of data processing. |
| 21:07 | <Philip`> | AryehGregor: About btoa: What if the input string contains U+FFFF? That's a noncharacter, so it's not a character whose code point is strictly greater than U+00FF |
| 21:08 | <AryehGregor> | Philip`, how is U+FFFF not a character? What are JavaScript strings if not sequences of characters? Sequences of UTF-16 thingies, the maybe-characters-maybe-half-characters? |
| 21:08 | <Philip`> | It's defined as a noncharacter, and I don't think noncharacters are characters |
| 21:08 | <Philip`> | hence being called noncharacters |
| 21:09 | <Philip`> | JS strings are sequences of 16-bit code units, I think |
| 21:10 | <Philip`> | which sometimes are conceptually decoded as (possibly invalid) UTF-16 into a sequence of Unicode characters |
| 21:11 | <Philip`> | (I don't know what WebIDL strings are) |
| 21:12 | <heycam> | same |
| 21:12 | <Philip`> | Ah, that sounds minimally crazy then |
| 21:19 | <annevk> | hmm |
| 21:19 | <annevk> | so whenever we talk about characters we should use 16-bit code units? |
| 21:20 | <annevk> | and define the mapping somewhere between 16-bit code units and Unicode? |
| 21:20 | <annevk> | XMLHttpRequest has the greather than U+00FF thing too |
| 21:20 | <annevk> | greater* |
| 21:21 | <Philip`> | In the >U+00FF case it's kind of pointless pedantry because everyone will presumably implement what you expect |
| 21:22 | <annevk> | wait, you can just substitute character for code point |
| 21:22 | <Philip`> | It might matter more in the case of lone surrogates |
| 21:22 | <annevk> | just talk about code points and it's okay |
| 21:22 | <annevk> | afaik |
| 21:24 | <Philip`> | Is "\ud800\udc00" two code points or one? |
| 21:24 | <Philip`> | Maybe "code units" is a safer term since it's not suggesting a direct correspondence to Unicode characters |
| 21:26 | <Philip`> | (and when you do care about the correspondence, you should use an explicit encoding/decoding step) |
| 21:26 | <annevk> | a single surrogate is a code point |
| 21:26 | <annevk> | not sure Unicode has defined code unit |
| 21:26 | <heycam> | "code unit" is on http://unicode.org/glossary/ |
| 21:29 | <annevk> | http://en.wikipedia.org/wiki/Unicode#Character_categories |
| 21:29 | <jamesr_> | AryehGregor: JavaScript strings are sequences of 16 bit numbers |
| 21:36 | <Hixie> | the html spec uses "character" to mean "code point", fwiw |
| 21:36 | <Hixie> | i guess maybe i should add that to the terminology section |
| 21:38 | <jamesr_> | Hixie: wait, so what's the number of "characters" (as per the html spec) in this string: "a𐅐c" ? 3? |
| 21:39 | <jamesr_> | it's 3 unicode code points, but in javascript "a𐅐c".length === 4 |
| 21:40 | <jamesr_> | because it's 4 16-bit code units |
| 21:40 | <jamesr_> | and does it ever matter? |
| 21:40 | <Hixie> | i don't have a utf-8 clean workflow, so i'm not sure what you pasted, but the answer is likely 3 if i guessed correctly what you meant. |
| 21:40 | <Hixie> | i don't think the length ever matters |
| 21:40 | <Hixie> | maybe for textarea.length or whatever that's called |
| 21:41 | <jamesr_> | i pasted "a" "character that is represented by a surrogate pair in utf-16" "c" |
| 21:41 | <Hixie> | yeah, that's three characters |
| 21:41 | <jamesr_> | but .length on it in JS is 4 |
| 21:41 | <Hixie> | where things are done in 16bit code units it's called out explicitly |
| 21:41 | <jamesr_> | grr. javascript is the worst |
| 21:41 | <Hixie> | (that might be nowhere) |
| 22:09 | <stevela> | Am wondering what the behavior for a video element should be when presented with a non-video src (e.g. an mp3). webkit will play it, but controls are messed up (as are those in chrome) due to the size being 0x0. Visually, should it appear as an audio element? |
| 22:10 | <stevela> | i.e. with an non-video source, and the controls attribute set |
| 22:15 | <aho> | it should cause the monitor to explode into the developers face. obviously. |
| 22:15 | <AryehGregor> | stevela, doesn't sound like a standards issue to me, sounds like a QoI issue. File bugs against the browsers. |
| 22:17 | <Hixie> | stevela: unless there's css setting the size, it should render a 0x0 box and play the music. |
| 22:18 | <Hixie> | stevela: if there's css setting the size, it should render a box of the given size and play the music. |
| 22:18 | <Hixie> | well, playing the music depends on autoplay="" being set and on the mp3 being music, obviously. |
| 22:19 | <stevela> | [btw - am working on chrome]. Thx. what about the controls though. I guess as they're inside the box, then they shouldn't be visible, even if asked for. |
| 22:19 | <AryehGregor> | (listen to Hixie, not me) |
| 22:20 | <Hixie> | well what happens to the controls is independent of whether the video is a video or an mp3 -- the same should happen regardless, if the size is 0x0 |
| 22:20 | <Hixie> | or 1x1, or anything smaller than the controls expect |
| 22:20 | <stevela> | thx Hixie, |
| 22:21 | <Hixie> | basically, do a best-effort attempt to make useful controls i the given size, maybe floating over the page, bigger than the <video>'s rendering area, or displaying just a single button that pops up a control window, or just have a context menu, or maybe just do nothing |
| 22:21 | <Hixie> | but especially, whatever you do should be clearly superior to what any other browser does :-) |
| 22:22 | <stevela> | :-) |
| 22:28 | <jamesr_> | make a really, really, really small pause button |
| 22:29 | <AryehGregor> | 0 pixels wide? |
| 22:36 | <Hixie> | if you add an element with qualified name "foo:bar" and namespace "baz" to an HTML element in an HTML document, and then get its parent's innerHTML, what should you get? |
| 22:36 | <Hixie> | <foo:bar></foo:bar>? <bar></bar>? nothing? |
| 22:36 | <Hixie> | i guess the former |
| 22:43 | <Hixie> | xmlns:xmlns="" and xmlns="" are the same attribute? |
| 22:43 | <Hixie> | that's just confusing |
| 22:50 | <annevk> | Hixie, they're not |
| 22:50 | <annevk> | Hixie, you cannot declare xmlns as a prefix |
| 22:51 | <annevk> | Hixie, see http://www.w3.org/TR/xml-names/#xmlReserved |
| 22:51 | <Hixie> | sure, it's invalid |
| 22:51 | <Hixie> | or non-well-formed or whatever |
| 22:51 | <Hixie> | i just meant conceptually |
| 22:51 | <karlcow> | conceptually or practically in the browser? |
| 22:52 | <annevk> | it's not a concept per the XML spec :) |
| 22:52 | <karlcow> | because conceptually :) we can imagine a lot of cool things |
| 22:52 | <annevk> | karlcow, browsers handle this correctly |
| 22:52 | <Hixie> | xmlns="" is in the xmlns namespace, so it's basically xmlns:xmlns=""... so conceputally, setting the xmlns: prefix's namespace is what you're doing when you set the default namespace for element names. :-P |
| 22:52 | <Hixie> | that's all i'm saying :-P |
| 22:53 | <karlcow> | Hixie: did you watch too much of inception lately? ;) |
| 22:54 | <Hixie> | k, 11099 is resolved |
| 22:57 | <annevk> | hmm, interesting way of solving it |
| 22:57 | <annevk> | I guess it makes sense to have element specific knowledge |
| 22:58 | <annevk> | I mean namespace |
| 22:59 | <Hixie> | well there had to be some namespace-specific knowledge to address hsivonen's point |
| 22:59 | <Hixie> | but i tried to keep it to a minimum |
| 23:01 | <annevk> | hmm |
| 23:01 | <annevk> | HTML5 Tracker has no homepage link |
| 23:01 | <annevk> | fail |
| 23:01 | <annevk> | something for tomorrow |
| 23:08 | <benschwarz> | Hixie: !ping |
| 23:08 | <Hixie> | yo |
| 23:10 | <benschwarz> | Hixie: I wanted to see what we can do about making some changes to the markup for developers. |
| 23:11 | <Hixie> | sure thing |
| 23:11 | <benschwarz> | how is best to request the changes? |
| 23:11 | <benschwarz> | I can give you a couple of simple ones to get runnning |
| 23:12 | <Hixie> | let's start by discussing them here |
| 23:12 | <benschwarz> | sure— |
| 23:12 | <benschwarz> | I'd like some kind of wrapping element around the main title |
| 23:13 | <benschwarz> | "HTML5 (including next generation additions still in development)" |
| 23:13 | <benschwarz> | either moving the "including next gener…" to another element, or wrapping it with a span |
| 23:14 | <Hixie> | i really should just change that entire line to "HTML" |
| 23:14 | <Hixie> | but people complained when i did that because they wanted the "HTML5" buzzword there, even though the spec is no longer HTML5 |
| 23:15 | <benschwarz> | Hixie: really, I'd like it to say something like |
| 23:15 | <benschwarz> | http://dev.w3.org/html5/spec-author-view/ |
| 23:15 | <benschwarz> | but that isn't up to me :) |
| 23:17 | <Hixie> | ok i put a span around the parenthetical and gave you some IDs so you can just drop the span and add another h2 or something for the "Edition for Web Developers" bit |
| 23:17 | <Hixie> | take a look |
| 23:19 | <Hixie> | and it is up to you btw :-) |
| 23:19 | <Hixie> | you have full authority over what the dev copy says |
| 23:20 | <benschwarz> | Hixie: Excellent :) |
| 23:20 | <benschwarz> | Hixie: https://github.com/benschwarz/developers.whatwg.org |
| 23:21 | <Hixie> | man you have to love the rube goldberg machine we're building here |
| 23:22 | <Hixie> | between the scripts i have (perl, bash, and python), the web services that my stuff invokes (anolis, the spec splitter), the stuff mike uses at w3c, and now the stuff you're doing (adding ruby to the mix), it's really astounding. |
| 23:23 | <benschwarz> | Hixie: I found the python really over whelming. I'd be happy to convert it all to something more simple |
| 23:23 | <benschwarz> | that is, across the board |
| 23:23 | <Hixie> | oh no, do whatever is easiest! it wasn't a criticism at all. |
| 23:23 | <benschwarz> | Hixie: but yeah, what a mix-mash! |
| 23:24 | <benschwarz> | You'll also note deploy.sh |
| 23:24 | <benschwarz> | otherwise, there isn't a lot going on. |
| 23:24 | <Hixie> | and we have to have at least five different version control mechanisms at this point, i think - svn at whatwg.org, cvs at w3c, the google code svn for some of the spec splitter code and the tracker code, plus you're using what, git? mercurial? |
| 23:25 | <Hixie> | i love it |
| 23:25 | <benschwarz> | my ruby removes all styles and scripts… from the spec |
| 23:25 | <benschwarz> | so like mike was saying to me yesterday |
| 23:25 | <benschwarz> | the links that were hidden with js |
| 23:25 | <benschwarz> | or inactivated or whatever |
| 23:25 | <benschwarz> | will need some attention, but I just won't know which ones for a bit |
| 23:25 | <Hixie> | hmm... you know, maybe we're better off having me generate you a version of the spec that doesn't have the styles and scripts to start off with |
| 23:26 | <Hixie> | would that help? |
| 23:26 | <Hixie> | or is it a sunk cost now |
| 23:27 | <benschwarz> | Hixie: I really don't mind… whatever is easiest. Being that I'm injecting my own scripts and styles… |
| 23:29 | <benschwarz> | oh, and I'm using git |
| 23:30 | <benschwarz> | Hixie: so if we can change the wording to read something like the dev.w3c author spec… |
| 23:31 | <benschwarz> | Hixie: can you please add <meta name="viewport" content="width=device-width;"> |
| 23:32 | <benschwarz> | and <meta content='IE=edge,chrome=1' http-equiv='X-UA-Compatible'> |
| 23:33 | <Hixie> | ew |
| 23:33 | <Hixie> | neither of those are, like, standard |
| 23:33 | <Hixie> | but sure! |
| 23:33 | <benschwarz> | Have you read the HTML in the spec? :P |
| 23:34 | <Hixie> | how do you mean? |
| 23:34 | <benschwarz> | Oh its just hard to style |
| 23:35 | <Hixie> | ah, well, yes, possibly :-) |
| 23:35 | <Hixie> | if there's anything not too invasive i can do to help, let me know |
| 23:35 | <benschwarz> | Hixie: I'll think about it. Right now I'm just porting everything over and getting back to step 1 :) |
| 23:35 | <Hixie> | :-) |
| 23:37 | <benschwarz> | Hixie: FYI, I've been pushing builds http://developers.whatwg.org/ on a regular basis |
| 23:37 | <benschwarz> | not really ready yet though |
| 23:37 | <Hixie> | cool |
| 23:37 | <benschwarz> | Hixie: where can I track the changes to this? |
| 23:37 | <benschwarz> | or are you editing live then commiting later? |
| 23:38 | <Hixie> | editing live, but i'm updating my script to generate you a clean header without scripts and styles and stuff, and i ran into a minor problem in my script doing that |
| 23:38 | <Hixie> | so it'll be a moment |
| 23:42 | <benschwarz> | Hixie: no worries |
| 23:47 | <Hixie> | ok i've added a separate output for my system for developers.whatwg.org specifically, so i can now include or exclude whole sections for you, and can have a separate header too |
| 23:48 | <Hixie> | at some point i'll work out how to give you the header file so that you can edit it yourself without needing to ask me to make the edits |
| 23:48 | <Hixie> | (though i'll still need to run the script manually) |
| 23:48 | <Hixie> | http://www.whatwg.org/specs/web-apps/current-work/dev-index |
| 23:48 | <Hixie> | use that instead of the file you're using now |
| 23:49 | <Hixie> | let's see, how can we make that file easily accessible for you |
| 23:49 | <Hixie> | oh, i know |
| 23:50 | <Hixie> | benschwarz: put http://www.whatwg.org/specs/web-apps/current-work/header-whatwg-dev somewhere on developers.whatwg.org in a location i can wget |
| 23:51 | <benschwarz> | Hixie: um, okay :) |
| 23:51 | <benschwarz> | this is so meta |
| 23:51 | <Hixie> | heh |
| 23:52 | <benschwarz> | I think that will mess with my build process and confuse other people a bit |
| 23:52 | <Hixie> | hm, possibly |
| 23:52 | <Hixie> | alternatively i can just make the header file as blank as possible so you can just mutate it as you want afterwards |
| 23:52 | <benschwarz> | I won't make a lot more changes |
| 23:53 | <benschwarz> | probably to other sections, I reckon |
| 23:54 | <Hixie> | well if you change your mind we can figure out where to put that file later |
| 23:54 | <Hixie> | in the meantime, use http://www.whatwg.org/specs/web-apps/current-work/dev-index as your input |
| 23:54 | <Hixie> | it has a bare minimum header, just what you asked for and nothing else |
| 23:55 | <benschwarz> | Yeah, excellent :) |
| 23:55 | <Hixie> | i can make it ever barer if you'd rather have your script add the <meta>s and stuff |
| 23:55 | <Hixie> | up to you |
| 23:55 | <benschwarz> | https://gist.github.com/7bc50d8b81601db45031 |
| 23:55 | <benschwarz> | oh noes! |
| 23:56 | <Hixie> | uh oh |
| 23:56 | <Hixie> | what do i need to add back, any idea? |
| 23:57 | <benschwarz> | no idea |
| 23:57 | <benschwarz> | that scary splitter |
| 23:58 | <Hixie> | ah, it wants a class=head |