| 00:02 | <Lachy> | Philip`, numerology: "The study of the occult meanings of numbers and their supposed influence on human life." - Just because we don't understand the mathematics of the divine, doesn't mean he isn't using maths to control our lives |
| 00:03 | <roc> | you must have taken physics --- you know he's using maths to control our lives |
| 00:03 | <Philip`> | Lachy: Fair enough |
| 00:05 | <Lachy> | roc, quantum physics is the work of the devil! You know he's just messing with you whenever you get close to figuring anything out :-) |
| 00:05 | <Philip`> | roc: Physics only taught me maths that was a horribly crude approximation of reality, and seemed to be hacked together just to match our observations, so I can't tell what really controls our lives |
| 00:06 | <roc> | God loves physicists, and he wanted to give them something to do in the 20th century |
| 00:08 | <roc> | I have to say that physics seems a lot more elegant than, say, the Web |
| 00:09 | <annevk> | maybe in 500 years the Web will seem logical too |
| 00:10 | <Philip`> | Many compost heaps seem more elegant than the Web |
| 00:10 | <roc> | if I try to think about the accumulated cruft of the Web in 500 years, I think I will pass out |
| 00:11 | <Dashiva> | Don't worry, the oil crash will make sure that doesn't happen |
| 00:14 | <Philip`> | Someone will build something that runs on top of the web, but doesn't depend on the web, and then it will become really popular, and nobody will care about the web since it's an implementation detail behind a layer of abstraction, and then the web can be replaced by a new cleaner more appropriate system |
| 00:14 | <Lachy> | given the exponential growth of the web in the last 15 years, which is likely to continue, I wonder if it could ever surpass the limits of a ZFS file system (if that in itself didn't require boiling the oceans) |
| 00:15 | <Philip`> | (See e.g. the internet on top of the old voice phone system, where now nobody cares about the phone system and it's all replaced with high-bandwidth fibre optics and IP) |
| 00:15 | <Lachy> | in fact, I wonder what the physical limit of the web's capacity will be |
| 00:16 | <annevk> | we hit a limit with IP |
| 00:16 | <Philip`> | Lachy: What do you mean by "the web's capacity"? |
| 00:16 | <annevk> | but that's being resolved in some way |
| 00:16 | <Lachy> | there's only so much data that could ever be stored in any possible storate system, given the limits of quantum mechanics |
| 00:17 | <Philip`> | I can make a site that serves a billion files that are each a gigabyte, but that isn't increasing capacity in any useful way |
| 00:17 | <annevk> | hsivonen, yeah http://pastebin.ca/992541 is a good start, thanks |
| 00:18 | annevk | saves the text in a file somewhere |
| 00:18 | <Lachy> | Philip`, yeah, I'm only considering data that is actually stored and not generated on the fly |
| 00:19 | <Lachy> | but I suppose, the universe is big enough such that the limit won't be reached before human civilisation dies out |
| 00:19 | <Philip`> | Lachy: So you could measure its upper bound as the combined storage space used by all devices connected to the internet? That sounds kind of reasonble |
| 00:19 | <Philip`> | s//a/ |
| 00:20 | <Lachy> | yes |
| 00:21 | <Philip`> | Lachy: You may be underestimating exponential growth |
| 00:22 | <Hixie> | annevk: i just recommend always starting threads publicly :-) |
| 00:23 | <Philip`> | Search engines index about 10^10 pages, and if that doubles every year then in 236 years you'll get 10^80 pages, which is about the number of atoms in the universe |
| 00:23 | <Dashiva> | But how many of those 10^10 are generated? |
| 00:23 | <Philip`> | and civilisation might survive that long |
| 00:23 | <Lachy> | But the IPv4 address range will run out in a few years, and the web will either level off or die out soon after |
| 00:24 | <annevk> | Hixie, fair enough |
| 00:24 | <Philip`> | Dashiva: Search engines cache those pages, so even if they were generated once then they're statically served now |
| 00:24 | <Dashiva> | Does google index e.g. live search? |
| 00:25 | <annevk> | Lachy, if that happens and IPv6 doesn't work we should start working on IPv5 :) |
| 00:25 | <Dashiva> | Recursion! :D |
| 00:25 | <Lachy> | annevk, ipv6 has already failed |
| 00:25 | <Hixie> | ipv6 hasn't failed as much as you might think |
| 00:25 | <Philip`> | Dashiva: archive.org says it has 10^11 pages already, and they're actually stored somewhere |
| 00:26 | <Lachy> | For it to succeed, ISPs should have been distributing IPv4 and IPv6 addresses to subscribers for the past 10 years |
| 00:26 | <Hixie> | e.g. comcast is deploying it internally and most of their set top boxes use it exclusively, because they've run out of IP addresses already for their customers |
| 00:26 | <Hixie> | ipv6 can be used without end-users seeing it |
| 00:26 | <Philip`> | but a few orders of magnitude aren't important, when we're multiplying it by 2^236 |
| 00:27 | <Lachy> | does http://ipv6.google.com/ work for anyone here? (I'm assuming it'll work for Hixie) |
| 00:28 | <Lachy> | it doesnt work for me, so my ISP isn't supporting IPv6 at all |
| 00:30 | <annevk> | I hope IPv6 does have some kind of extension mechanism so we never hit some wall again... |
| 00:31 | <Philip`> | We'll hit plenty of scalability walls before running out of IPv6 addresses |
| 00:32 | <Philip`> | largely in things that are nothing to do with IP |
| 00:32 | <Lachy> | annevk, ipv6 won't need it. It's 128 bit address space is large enough to last for billions of years |
| 00:32 | <Lachy> | 3.4×10^38 addresses |
| 00:32 | <annevk> | We never know what kind of thing needs an IP going forward... |
| 00:32 | <Hixie> | the problem isn't the number of addresses |
| 00:33 | <Hixie> | it's the way they are given out |
| 00:33 | <Philip`> | Lachy: Not really, since you can't just pick the next unused number and give it to somebody |
| 00:33 | <Hixie> | e.g. with ipv6, isps can and probably will give out 1000 IPs to their users |
| 00:33 | <Philip`> | since it has to be split up hierarchically |
| 00:33 | <Philip`> | Uh, like what Hixie's saying |
| 00:33 | <Lachy> | Philip`, yeah, I know, but ipv6 has better allocation strategy than ipv4 |
| 00:34 | <Hixie> | that's possible |
| 00:34 | <Hixie> | i'm just saying it's not a matter of numbers |
| 00:35 | <Philip`> | There seems to have been some concern in the internet routing world in the past few years, because autonomous networks get a unique 16-bit ID, and they're running out of numbers |
| 00:35 | <Philip`> | and they don't have a nice way of transitioning to an updated version of the protocol |
| 00:36 | <Philip`> | but at least there's 2^16 fewer people involved than with IP |
| 00:36 | <Hixie> | 16 bits isn't much for that kind of thing |
| 00:36 | <Hixie> | wow |
| 00:38 | <Philip`> | http://bgp.potaroo.net/cidr/autnums.html |
| 00:38 | <Philip`> | Each number is usually a fairly big organisation |
| 00:38 | <Hixie> | woot AS15169 |
| 00:38 | <Philip`> | but the world has too many fairly big organisations |
| 00:39 | <Philip`> | AS36561 too |
| 00:39 | <Lachy> | Philip`, that site won't load for me |
| 00:39 | <Hixie> | damn microsoft has a ton of these |
| 00:40 | <Hixie> | AS6432 too |
| 00:40 | <Hixie> | hehe |
| 00:40 | <Philip`> | Google has at least 9 |
| 00:40 | <Hixie> | oh? |
| 00:40 | <Philip`> | On that page, search for "google" :-p |
| 00:41 | <Lachy> | hmm. weird. It will load in Safari, but in Firefox it just gives up |
| 00:41 | <roc> | these are not fairly big organizations |
| 00:42 | <roc> | they are every man and his dog |
| 00:42 | <Hixie> | Philip`: oh i guess the page hadn't loaded yet |
| 00:44 | <Lachy> | I don't understand what those numbers are representing |
| 00:44 | <Philip`> | roc: At least they're fairly big compared to individual IP address users |
| 00:44 | <Philip`> | and I say anything larger than me is big |
| 00:45 | <roc> | how big is this page? |
| 00:46 | <roc> | ah finished |
| 00:46 | <Hixie> | less than 64k lines, i guess |
| 00:46 | <Philip`> | Lachy: They're the numbers used to identify nodes in the routing graph of the internet |
| 00:47 | <Philip`> | Lachy: (where each node is actually a whole network, usually administered by a single entity) |
| 00:47 | <roc> | it's at least 128K lines, there's all these AS1.xxxx numbers plus some random other stuff at the end |
| 00:50 | <Hixie> | roc: ah |
| 00:51 | <Philip`> | ASxxxx.xxxx is from the new 32-bit extension, but I have no idea how widely deployed or usable it is yet |
| 00:51 | <Philip`> | Someone should place bets on which fixed-size integer field in an internet protocol is going to run out of space next |
| 00:52 | <Hixie> | oh hey, i finally got that e-mail to which i received a reply two hours ago |
| 00:52 | <Hixie> | (al's e-mail about alt="") |
| 01:48 | <Hixie> | woah |
| 01:48 | <Hixie> | this e-mail suggests adding elements for all the following: |
| 01:48 | <Hixie> | verbs, proper nouns, words that score over 30 in Scrabble, palindromes, words that can be written upside-down on calculators, words defined in the Oxford English Dictionary |
| 01:48 | <Hixie> | (ok so it's being sarcastic. but still.) |
| 01:49 | <Philip`> | Hixie: It would have been clearer that it was sarcastic if you hadn't rejected the <sarcasm> element |
| 01:50 | <Hixie> | -_- |
| 01:51 | <Hixie> | i still love the question i got from the xhtml2 camp when i gave my talk at xtech in 2004 |
| 01:51 | <Hixie> | (or 2005?) |
| 01:51 | <Hixie> | 2005 i think |
| 01:51 | <Hixie> | after explaining how we were doing things in the open, etc |
| 01:51 | <Hixie> | they were like "well, how are you going to handle people who ask for an <irony> element???" |
| 01:52 | <Hixie> | apparently the concept of just saying "no" to requests hadn't come up before |
| 01:52 | <Dashimon> | Hixie: Maybe they were being ironic |
| 01:53 | <Hixie> | maybe |
| 01:53 | <Philip`> | Hixie: If you keep saying no to requests, you'll work yourself out of a job since there won't be any unrejected requests left to work on |
| 01:54 | <Hixie> | same happens if i say yes: http://www.whatwg.org/issues/data.html |
| 01:55 | <Philip`> | Either you have been processing issues very chaotically and travelling backwards and forwards in time, or Opera 9.2 has canvas bugs |
| 01:56 | <Dashimon> | I'm seeing two green lines in 9.2 |
| 01:56 | <Philip`> | Hopefully at some point people will start writing test cases, and finding lots of issues in the spec, so the line will start shooting up again |
| 01:57 | <Dashimon> | 9.5 gets the green line right, but only shows blue for the very latest week |
| 01:57 | <Philip`> | That's because the blue data only exists for the last week |
| 01:59 | <Dashimon> | How non-buggish |
| 02:00 | <Hixie> | heh |
| 02:01 | <Hixie> | if anyone wants to go back and pull every version of the spec back to last september and count the number of XXX/big-issue markers over time, be my guest :-D |
| 02:01 | <Dashimon> | I'm sure Philip` is already doing it |
| 02:02 | <Hixie> | on the extreme off-chance that some crazy person wants to do this, the times and dates for which i have green dots are the times and dates in this file: http://www.whatwg.org/issues/data.csv |
| 02:02 | <Philip`> | I think I'll go to bed instead :-p |
| 02:02 | <Hixie> | :-) |
| 02:03 | <Philip`> | (Does XXXX count as one?) |
| 02:03 | <Philip`> | (Not that I really care since I'm not going to do anything with this) |
| 02:04 | <Hixie> | my algorithm is: ... @issues = $spec =~ m/(XXX|big-issue)/gos; return scalar @issues; |
| 02:04 | Dashimon | hides from the perl |
| 02:04 | <Hixie> | also, if you did want to do this, but not do it for every day, the script already supports just having data for a few random days |
| 02:04 | <Philip`> | <p class=big-issue>Big Issue! Get yer Big Issue here!</p> |
| 02:04 | <Hixie> | it'll just draw the line straight across any points its missing |
| 02:04 | takkaria | chuckles |
| 02:04 | <Hixie> | it's |
| 02:06 | Philip` | once saw someone trying to sell the Big Issue by saying "spare a shekel for an old ex-leper" repeatedly |
| 02:07 | <Philip`> | (I'm not sure how successful that strategy was) |
| 02:09 | <Dashimon> | Hixie: So if it were to be done (which it won't) it would only be worthwhile to check points that have email data? |
| 02:10 | <Philip`> | Hixie: When Dashimon implements this, what should happen on days that have multiple commits and multiple distinct XXX counts? |
| 02:11 | <Philip`> | s/Dashimon/Dashiva/ |
| 02:11 | <Dashiva> | I figured I would simply (except I won't) take the commit closest to thet email ts |
| 02:12 | <Hixie> | Dashiva: well, if we get more data out of this than the precision of the green line, i'll have to rewrite the script that generates the graph to handle missing green dots too |
| 02:12 | <Hixie> | Dashiva: which would be work for me :-) |
| 02:12 | <Hixie> | Philip`: the .csv file has exact timestamps |
| 02:12 | <Hixie> | Philip`: so there's no ambiguity |
| 02:12 | <Philip`> | Ah |
| 02:12 | <Dashiva> | Man, we have it all figured out, too bad we aren't going to do it |
| 02:15 | <Hixie> | indeed |
| 02:15 | <Hixie> | how about if i give 15 points to someone for doing it |
| 02:15 | <Dashiva> | Nooo |
| 02:16 | <Dashiva> | I'm secretly going to do it in secret without telling anyone in a few days, but now it'll seem it was for the points |
| 02:16 | <Hixie> | lol |
| 02:16 | Hixie | makes a note to secretely not do any work in a few days since his server is going to be crushed by the load of 1000+ checkouts |
| 02:17 | <takkaria> | secretly doing it in secret without telling anyone seems like a lot of secrecy for one person to maintain. :) |
| 02:17 | <Dashiva> | How did you know I was going to do a new checkout for each timestamp? |
| 02:17 | <Hixie> | Dashiva: how else would you do it? |
| 02:18 | <takkaria> | svn update to a given time would be more efficient |
| 02:18 | <Hixie> | on your side maybe :-P |
| 02:18 | <Hixie> | svn update requires the server to do a diff :-P |
| 02:18 | takkaria | grins |
| 02:19 | Hixie | makes a note to increase his RAM allocation for a bit |
| 02:19 | <Philip`> | Use svnsync to make a local copy of the repository, then do checkouts on that |
| 02:19 | <Hixie> | heh |
| 02:20 | <takkaria> | even better, Hixie should just tarball up the repo and put it online briefly |
| 02:20 | <Hixie> | not sure how to do that |
| 02:20 | <Dashiva> | I recould reverse the commit timeline using the archive of commit-watchers |
| 02:20 | <Hixie> | heh |
| 02:20 | <Hixie> | i guess you could! |
| 02:21 | <Hixie> | if you really do want to do this, i really would just encourage you to do the simple route of a bunch of timestamp checkouts :-) |
| 02:21 | <Hixie> | do you want the code i used to get the counts? |
| 02:22 | <Dashiva> | Well, for now I'm just going to sleep. We'll see if I remember about it when I wake up :) |
| 02:22 | <Hixie> | http://junkyard.damowmow.com/312 |
| 02:22 | <Hixie> | nothing special |
| 02:22 | <Philip`> | Hmm, svnsync goes pretty slowly |
| 02:28 | <Philip`> | svn cat http://svn.whatwg.org/webapps/source -r "{`date -u --rfc-3339 seconds -d 'Sun Apr 20 03:08:19 2008'|cut -c-19`}"|perl -e'local $/; print scalar (() = <> =~ /XXX|big-marker/g)' |
| 02:29 | <Philip`> | That's the easy way to get the count for any given timestamp |
| 02:29 | <Hixie> | well |
| 02:29 | <Hixie> | you're nearly done then! |
| 02:30 | <Hixie> | put a loop around that and mail me the results and i'll add them to the data file :-D |
| 02:30 | <Philip`> | Oh, I don't want to be done, because then I'd have been wrong when I said I wasn't going to do it |
| 02:30 | <Hixie> | haha |
| 02:30 | <Hixie> | Dashiva: put a loop around it, then you'll be the one who did it :-) |
| 02:30 | <Philip`> | Anyway I'm just seeing if svnsync will make it run quicker from a local repository than remote |
| 02:30 | <Philip`> | except svnsync is taking forever |
| 02:36 | <Hixie> | <abbr> has optional title="" again. |
| 02:36 | <Hixie> | and i added another example to <abbr> to show this. |
| 02:43 | <Philip`> | cut -c19-42 data.csv|xargs -d '\n' -n 1 -I blah -- date -u --rfc-3339 seconds -d 'blah'|cut -c-19|perl -ne'chomp; print "$_ \t", scalar (() = `svn cat http://svn.whatwg.org/webapps/source -r "{$_}"` =~ /XXX|big-marker/g), "\n"' |
| 02:43 | <Philip`> | That does it for all the timestamps, I think |
| 02:44 | <Philip`> | Maybe that would help whoever's going to do this |
| 02:48 | <Philip`> | Hixie: The "Philip`" looks ugly with punctuation :-p |
| 02:50 | <Philip`> | Smallcaps styling seems a reason to have <acronym>, since you normally only want smallcaps on acronymic abbreviations and not any other kind of abbreviation |
| 02:50 | <Hixie> | class="" baby |
| 02:50 | <Hixie> | anyway, bbl |
| 03:05 | <Philip`> | Ooh, svnsync finished, so now I have a 50MB copy of the whole revision history |
| 03:06 | <Philip`> | and 'svn cat' works very much faster than on svn.whatwg.org |
| 03:09 | <Philip`> | Oh, someone should have told me that I wrote big-marker instead of big-issue |
| 03:13 | <Philip`> | Hixie: Dashiva just emailed me http://philip.html5.org/misc/spec-issue-marker-count.txt |
| 03:13 | <Philip`> | I guess I was too late :-( |
| 03:14 | <Philip`> | but I suppose that doesn't matter since I can't even remember what the point of this was |
| 03:14 | Philip` | sleeps |
| 03:41 | <Hixie> | man you guys are all crazy and awesome |
| 03:48 | <Hixie> | wtf did i do on Fri Apr 11 09:06:28 2008,504 |
| 03:49 | <Hixie> | oh. |
| 03:49 | <Hixie> | WebIDL XXXs. |
| 04:14 | <Hixie> | who implements <event-source> these days other than opera? |
| 04:18 | <othermaciej> | we had a preliminary patch for WebKit at one point |
| 04:19 | <othermaciej> | I think we were waiting for the design simplifications to settle |
| 04:22 | <Hixie> | they're pretty settled now |
| 04:22 | <Hixie> | i have no pending feedback |
| 04:22 | <Hixie> | just replied to the last mail on the topic |
| 04:23 | <jwalden> | there was a preliminary patch for Mozilla, too, circa 200612 or so, if I remember right |
| 04:39 | <weinig> | Hixie: would you say that the postMessage spec is also pretty settled now? |
| 04:40 | <Hixie> | no |
| 04:40 | <Hixie> | there's a bunch of feedback still outstanding on it |
| 04:40 | <Hixie> | in particular about sync vs async |
| 04:40 | <Hixie> | will probably address it tomorrow |
| 04:41 | <Hixie> | (i'm waiting for one piece of feedback in particular) |
| 04:41 | <Hixie> | (which should be coming tomorrow) |
| 04:44 | <weinig> | Hixie: ok |
| 04:53 | <Hixie> | what's an example of a list that gets edited a lot? |
| 04:54 | <roc> | firefox 3 release blocker bugs |
| 05:04 | <Hixie> | hmm, that's a good one |
| 05:21 | <jruderman> | that doesn't really get edited as a list, though |
| 05:26 | <jwalden> | a fault of the UI rather than of the mental model, I think |
| 06:54 | <mcarter> | Hixie, thanks for your quick solution with the lastEventId |
| 07:11 | <Hixie> | mcarter: my pleasure, though i should emphasise that you're actually just lucky :-) |
| 07:11 | <Hixie> | mcarter: i just happened to be going through folders that only had 1 e-mail |
| 07:12 | <mcarter> | Hixie, how did my email end up being the only one in a folder? |
| 07:12 | <Hixie> | mcarter: there was no other outstanding feedback for event-source |
| 07:12 | <mcarter> | so I've got a number of suggestions I'm working on for tcp connection |
| 07:12 | <mcarter> | any advice on how to make those go to just the right folder? ;-) |
| 07:17 | <othermaciej> | if I were offering bets on features in the final spec, I would give tcp connection slim odds of making the cut |
| 07:17 | <mcarter> | othermaciej, I think you're spot on giving its current state and lack of interest |
| 07:18 | <mcarter> | othermaciej, but I've succcessfully implemented it in javascript, on top of sse implemented in javascript, and I have a number of suggestions that might help |
| 07:19 | <othermaciej> | mcarter: I don't see how that is possible |
| 07:19 | <mcarter> | othermaciej, and even if it doesn't make it into browsers right away, having a spec to base the javascript implementation(s) on is very nice |
| 07:19 | <mcarter> | othermaciej, well, obviously not the protocol |
| 07:19 | <othermaciej> | since the whole point of the feature is that it makes a raw TCP connection |
| 07:19 | <othermaciej> | and does two-way messaging over the single established socket |
| 07:19 | <mcarter> | i'm not saying i've perfectly emulated a native implementation |
| 07:20 | <mcarter> | rather that if you make your sse server open the actual socket, and allow the sse server to receive upstream over xhr requests and have some way of identifiying messages to a particular connection |
| 07:20 | <othermaciej> | I do think a full duplex communication feature would be great |
| 07:20 | <mcarter> | then you end up with a nearly identical api to tcpconnection |
| 07:20 | <othermaciej> | but I a not a fan of the specific design of TCPConnection |
| 07:20 | <mcarter> | is it the api provided by tcpconnection, or the underlying protocol? |
| 07:21 | <othermaciej> | by TCPConnection |
| 07:21 | <othermaciej> | but I don't think the API is the big value add |
| 07:22 | <othermaciej> | if you want to emulate full duplex messaging and don't care how many connections you use, you can just use XHR |
| 07:22 | <MacDome> | another CD came! yay! |
| 07:23 | <mcarter> | othermaciej, so what is it that you think is wrong with TCP Connection? |
| 07:24 | MacDome | wonders if mcarter is talking about the SVG 1.2 Connection object... |
| 07:25 | <MacDome> | or something entirely different |
| 07:26 | <Hixie> | mcarter: just sending feedback to whatwg⊙wo is enough |
| 07:26 | <mcarter> | MacDome, http://www.w3.org/html/wg/html5/#tcp-connections |
| 07:26 | <Hixie> | mcarter: it'll be put in the right folder when i read it :-) |
| 07:26 | <mcarter> | Hixie, heh, the way othermaciej frames it, the right folder will be the trash |
| 07:26 | <Hixie> | MacDome: http://www.whatwg.org/specs/web-apps/current-work/#network |
| 07:27 | <Hixie> | i guarentee to reply to all actionable feedback sent to whatwg⊙wo |
| 07:27 | <MacDome> | hum... |
| 07:27 | <MacDome> | sounds scary |
| 07:27 | MacDome | wonders if Hixie saw mjs's feedback on SVG 1.2 Connection |
| 07:27 | <Hixie> | http://www.whatwg.org/issues/data.html tracks my progress on that front :-) |
| 07:27 | <Hixie> | MacDome: SVG 1.2 Connection was a disaster compared to this |
| 07:28 | <Hixie> | MacDome: though maciej things this is a disaster too, so... :-) |
| 07:28 | <Hixie> | thknks |
| 07:28 | <Hixie> | thinks |
| 07:28 | <mcarter> | Hixie, the first two proposals are api, and I'll send them when i finish. I think there should be an explicit connect() function, and one more ready state (before connect() is called is a new readystate) |
| 07:28 | <MacDome> | Hixie: well, I'm just glad you're the one specing this |
| 07:28 | <MacDome> | Hixie: but in general I would trust mjs over you in this area (nothing personal) |
| 07:28 | <mcarter> | Hixie, also, I have a pretty reasonable suggestion about the protocol, using HTTP upgrades instead of a custom protocol. I'll send that when i get it ready as well |
| 07:29 | <mcarter> | just giving you a bit of heads up |
| 07:29 | MacDome | would have to think about what sort of evil things are possible with Connection |
| 07:29 | <Hixie> | MacDome: his feedback is in the pile somewhere, and i have no intention of ignoring it :-) |
| 07:29 | <MacDome> | Hixie: again, why I'm glad you're specing this :) |
| 07:29 | <Hixie> | mcarter: cool, thanks |
| 07:29 | <MacDome> | his SVG 1.2 Connection feedback was ignored :( |
| 07:29 | <Hixie> | shocking |
| 07:30 | <Hixie> | MacDome: iirc my biggest problem with mjs' feedback was that he wants it to use HTTP instead, and that seems like a giant amount of work for the server side |
| 07:30 | <MacDome> | (for those who don't read Hixie, he's being facetious) |
| 07:30 | <MacDome> | Hixie: http is definitely a smaller problem space |
| 07:30 | <MacDome> | Hixie: and is stateless |
| 07:30 | <Lachy> | Hixie, these statement's seem redundant in the spec: "If a dl element contains only dt elements, then it consists of one group with names but no values." |
| 07:30 | <Lachy> | "If a dl element contains only dd elements, then it consists of one group with values but no names." - Since those cases are covered by the 2 subsequent conditions |
| 07:30 | <MacDome> | Hixie: but I'd have to give it some thought |
| 07:31 | <Hixie> | Lachy: hm, true, i guess |
| 07:31 | MacDome | just now realizes that he's in #whatwg instead of #webkit |
| 07:31 | MacDome | goes back to friendlier waters :) |
| 07:31 | <mcarter> | Hixie, if you use http you could tunnel through proxies a lot easier AND stop worrying about connections to the SMTP servers without adding yet another simple protocol to the world |
| 07:31 | <Hixie> | aww, MacDome, don't go away :-) |
| 07:32 | <MacDome> | Hixie: I'm never far. and you have plenty of ways to reach me ;) |
| 07:32 | <Hixie> | mcarter: but if you use http the server side goes from a ten line perl script to a 3000-line perl script |
| 07:32 | <Hixie> | mcarter: and you'll end up with nobody ever actually writing a compliant server |
| 07:32 | <MacDome> | Hixie: or you just put your stuff behind an http frontend |
| 07:32 | <Hixie> | MacDome: how? |
| 07:33 | <MacDome> | Hixie: how not? |
| 07:33 | <mcarter> | Hixie, how about a protocol that is a strict subset of http such that you only need to know how to read a couple of headers and send back an error or ok header? |
| 07:33 | <Hixie> | MacDome: the problem we're trying to solve is real-time duplex communication |
| 07:33 | <Hixie> | mcarter: then it's not HTTP |
| 07:33 | <Hixie> | mcarter: at which point, why bother with the pretense |
| 07:34 | <MacDome> | Hixie: which is possible with two HTTP connections, no? |
| 07:34 | <mcarter> | Hixie, the pretense is mostly there so that it starts as an http request and can use the browser's proxy settings to establish the connection |
| 07:35 | <mcarter> | Hixie, i think http is a bad solution for a tcp connection, but practically speaking we *really* want to get through locked down systems |
| 07:35 | <Hixie> | MacDome: the web browser can't receive connections, it's behind NAT typically |
| 07:36 | <Hixie> | mcarter: can't you tunnel anything through 443? |
| 07:36 | <MacDome> | Hixie: I meant that the browser could open up two conenctions, one which it sends on, the other which it receives on |
| 07:36 | <MacDome> | i mean, I guess you should be able to do it with one |
| 07:37 | <Hixie> | MacDome: if you layer that on top of an http frontend, you end up with two processes, where you really just want one |
| 07:37 | <Hixie> | MacDome: onthe server |
| 07:37 | <mcarter> | Hixie, the main issue isn't really the port number so much as the forward proxy sitting between you and the outside world (where "you" is some poor student or employee.) |
| 07:37 | MacDome | goes back to fixing CSS3 bugs |
| 07:37 | <Hixie> | mcarter: do https: connections go through said proxy? |
| 07:37 | <mcarter> | Hixie, yeah |
| 07:38 | MacDome | claims ignorance for all networking issues |
| 07:38 | <Hixie> | mcarter: i thought the way https worked was that all data was just forwarded through untouched |
| 07:38 | <Hixie> | mcarter: how does https work? |
| 07:38 | <mcarter> | Hixie, they start with a CONNECT, and then after that all data is untouched |
| 07:38 | <Hixie> | oh |
| 07:38 | <Hixie> | interesting |
| 07:38 | <Hixie> | didn't know that |
| 07:38 | <Hixie> | well we probably want to do something similar then, i agree |
| 07:39 | <mcarter> | but we can't just open a connection to an arbitrary external address |
| 07:39 | <mcarter> | we actually have to open the connection to the forward proxy, then use a CONNECT to specify the external address |
| 07:39 | <Hixie> | sure |
| 07:39 | <Hixie> | that's ok |
| 07:39 | <Hixie> | can't we just define that that is how this protocol is handled when there's a proxy? |
| 07:39 | <Hixie> | i.e. that you proxy it over whatever HTTP proxy is set up? |
| 07:40 | <mcarter> | so as long as the browser agrees to expose the proxy information to their TCPConnection implementation, and use connect, then it could work out |
| 07:40 | <mcarter> | exactly |
| 07:40 | <Hixie> | makes sense to me |
| 07:40 | <mcarter> | I'll put together a proposal that outlines the problem and that solution over the next couple of days and send it in |
| 07:40 | <Hixie> | that would be awesome |
| 07:40 | <Hixie> | thanks! |
| 07:41 | <Hixie> | basically my main requirements are that: (1) there be the ability for one process to have a full-duplex communication channel to the script running in the web page |
| 07:42 | <Hixie> | (2) the server-side be implementable in a fully conformant way in just a few lines of perl without support libraries |
| 07:42 | <Hixie> | (3) that it be safe from abuse (e.g. can't connect to smtp servers) |
| 07:42 | <Hixie> | (4) that it work from within fascist firewalls |
| 07:42 | <mcarter> | yeah, those requirements are spot on |
| 07:43 | <mcarter> | (2) is a bit tricky when you start requiring HTTP or even a subset of it |
| 07:43 | <Hixie> | right |
| 07:43 | <mcarter> | i still think there are a couple of other reasons why http might be a good idea, but i need to think about it more. I too want this to be as simple as possible so long as it works |
| 07:43 | <Hixie> | oh i agree that there are a number of compelling reasons to base this on http |
| 07:44 | <Hixie> | just not reasons that i would classify as requirements :-) |
| 07:44 | <mcarter> | heh |
| 07:44 | <mcarter> | so the spec seemed to indicate no resolution on the same-source origin policies for tcpconnection |
| 07:44 | <mcarter> | i think there was some comment about "maybe allowing cross-domain" connections or something |
| 07:45 | <Hixie> | yeah |
| 07:45 | <mcarter> | even for cross-subdomain stuff you have the afore-mentioned dns rebinding attack |
| 07:45 | <Hixie> | i plan to cut out all the crap about local network connections and peer to peer stuff and broadcast stuff |
| 07:45 | <Hixie> | and to make it cross-domain |
| 07:45 | <mcarter> | which a Host header you can solve dns rebinding |
| 07:45 | <Hixie> | yeah |
| 07:45 | <Hixie> | i was about to say i think we should include an equivalent to the Host header |
| 07:46 | <Hixie> | that would allow for shared hosting, too |
| 07:46 | <mcarter> | right |
| 07:46 | <Hixie> | in some future where there's some cool thing that everyone is doing using this |
| 07:46 | <mcarter> | also, i'm not convinced it makes sense to create a protocol that can't identify what version of the protocol it is |
| 07:46 | <Hixie> | yeah, people always think you should version protocols |
| 07:46 | <Hixie> | it's ok |
| 07:46 | <Hixie> | you grow out of it :-) |
| 07:47 | <mcarter> | haha |
| 07:47 | <mcarter> | at any rate, I really do have a pretty neat implementation of the TCPConnection api, but over sse and xhr |
| 07:47 | <mcarter> | it makes for a nice dream, of some day having that be native =) |
| 07:47 | <Hixie> | you don't need to version the protocol if it's designed in a way that it extends with well-defined behaviour in down-level clients |
| 07:47 | <Hixie> | :-) |
| 07:48 | <Hixie> | (e.g. css and html aren't versioned) |
| 07:48 | <Hixie> | (html4 and before look like they're versioned, but they're not really) |
| 07:48 | <mcarter> | I'm not convinced |
| 07:48 | <Hixie> | versioning doesn't work when you have multiple implementations and an evolving spec |
| 07:49 | <mcarter> | well, thats a good point I suppose |
| 07:49 | <mcarter> | Thats what headers are for |
| 07:51 | <mcarter> | I don't actually care too much if we use http or not, i just need to put all my thoughts down somewhere and come up with coherent comparison of advantages and disadvantages |
| 07:51 | <mcarter> | and send it to the list |
| 07:51 | <Hixie> | that would be great |
| 07:52 | <mcarter> | I am sort of hoping that a cross-browser implementation of the api (both server-side and client side, via javascript hackery and a server-side xhr/sse->socket proxy) can help push the standard forward in the face of browser non-adoption |
| 07:53 | <mcarter> | so with the orbited project (open source comet server in python www.orbited.org) we are getting close to that, and even if TCPConnection it drops out of the specification, its a nice abstraction for server-side and javascript-side developers |
| 07:53 | <mcarter> | I'll keep you posted |
| 07:55 | <inimino> | that would be excellent |
| 07:55 | <inimino> | (TCPConnection with a back-compat JS library) |
| 07:56 | <mcarter> | inimino, yeah, and we've already got all the proof of concept work done on it. So you can expect it in the near future |
| 07:57 | <Hixie> | please do (keep me posted). this sounds cool. |
| 07:57 | <Hixie> | man i hope the forms stuff gets resolved soon |
| 07:57 | <Hixie> | i have so many WF2 and WF3 feedback e-mails |
| 07:58 | <inimino> | Hixie: how much of the WF2 stuff do expect to survive? |
| 07:58 | <inimino> | (and what's WF3?) |
| 07:58 | <Hixie> | i expect most of it to survive other than the repetition blocks stuff |
| 07:59 | <Hixie> | though some minor buts might get axed or simplified |
| 07:59 | <inimino> | ok, good |
| 07:59 | <Hixie> | WF3 is the next version of WF2 |
| 07:59 | <Hixie> | of course, if the w3c xforms crowd gets their way and the browsers all misteriously change their minds and agree with them, then wf2 could die altogether |
| 07:59 | <Hixie> | i give that pretty low odds though |
| 07:59 | <inimino> | is WF3 published somewhere? |
| 08:00 | <inimino> | Hixie: yeah, I'm betting on XForms not going anywhere in browsers... |
| 08:00 | <Hixie> | inimino: there is no wf3 yet, just a lot of proposals in e-mail |
| 08:01 | <inimino> | Hixie: ok |
| 08:02 | <hsivonen> | well, title on abbr didn't last long |
| 08:02 | <annevk> | "The new custom-* attributes are an attempt to address these requests." |
| 08:02 | <annevk> | oops |
| 08:02 | <Lachy> | Hixie, is WF3 just waiting for the results for the forms tf before starting? |
| 08:03 | <Hixie> | Lachy: no, wf3 is mostly html6 |
| 08:04 | <Hixie> | annevk: heh, oops. data-... |
| 08:04 | <zcorpan_> | <section> This is the first paragraph. <del>This sentence was deleted. <div></div> This sentence was deleted too.</del> End of second paragraph... </section> |
| 08:04 | <zcorpan_> | s/</</ |
| 08:05 | <zcorpan_> | Hixie: isn't the above 2 paragraphs with 1 del element marking the end of the first and the start of the second? |
| 08:09 | <Hixie> | zcorpan_: it's two paragraphs and a div |
| 08:10 | <zcorpan_> | Hixie: hmm, yeah ok |
| 08:16 | <Lachy> | it's interesting that for all the reasons given to allow title="" to be omitted from <abbr>, the only convincing one was the styling issue. |
| 08:17 | <Hixie> | yeah |
| 08:17 | <Lachy> | The thread could have been a lot shorter if people stopped giving non-convincing arguments. |
| 08:17 | <Hixie> | in their defence they didn't know which would convince me :-) |
| 08:19 | <Lachy> | ignorance is no excuse! :-) |
| 08:25 | <Hixie> | annevk: i think you should look up the word "explicit" (as compared to its antonym "implicit") :-) |
| 08:26 | <annevk> | if I omit the argument it's an explicit choice :) |
| 08:26 | <Hixie> | no it's not :-) |
| 08:28 | gsnedders | notes that the commit about plurals doesn't actually really define anything |
| 08:28 | <Hixie> | hm? |
| 08:28 | <gsnedders> | Actually, it defines that the number in @title must match the number in the content |
| 08:28 | <gsnedders> | But that's all |
| 08:29 | <gsnedders> | implicitly I suppose it suggests not using <abbr title="working group">wg</abbr>s |
| 08:29 | <krijnh> | Hixie: Don't worry :) |
| 08:30 | <Hixie> | gsnedders: it gives an example showing both :-) |
| 08:30 | <Hixie> | it admittedly doesn't really answer the question the www-html guy asked |
| 08:30 | gsnedders | is too tired |
| 08:30 | <gsnedders> | zcorpan_'s theory is definitely right. Everything I say is bullshit :) |
| 08:31 | <gsnedders> | Hixie: My point is that it doesn't define which to use |
| 08:31 | gsnedders | nowadays always marks up the singular, though he used to use either the singular or plural |
| 08:32 | gsnedders | heads off to school |
| 08:34 | <annevk> | Hixie, the parser thing about <span> doesn't seem to be in any feedback folder |
| 08:35 | <annevk> | oh, but it's a marked issues it seems |
| 08:36 | <Hixie> | ? |
| 08:36 | <Hixie> | the idea of having <span><section> or whatever? |
| 08:37 | <annevk> | yeah |
| 08:37 | <Hixie> | i replied to that already iirc |
| 08:37 | <annevk> | no, not that |
| 08:37 | <annevk> | stuff like <p><i><div><p> |
| 08:37 | <Hixie> | iirc i replied both when i specced it and when i removed it again |
| 08:37 | <Hixie> | oh |
| 08:38 | <annevk> | I thought it was just <span>, but it's <i> too |
| 08:38 | <annevk> | The thing that also allows <ul> in <p> |
| 08:38 | <Hixie> | i have no idea what you're talking about |
| 08:38 | <annevk> | <p><span><ul></ul></span></p> or something |
| 08:38 | <Hixie> | right |
| 08:38 | <Hixie> | the stuff that's in the spec as XXXSPAN |
| 08:38 | <Hixie> | iirc i replied both when i specced it and when i removed it again |
| 08:39 | <annevk> | but shouldn't the parser support it? |
| 08:39 | <Hixie> | how does it not? |
| 08:39 | <Hixie> | i am very confused |
| 08:40 | <annevk> | search for '<p class="big-issue">This doesn't match browsers.</p>' |
| 08:40 | <Hixie> | ah |
| 08:40 | <Hixie> | ok |
| 08:40 | <Hixie> | well if it's in the spec |
| 08:48 | <annevk> | In other news, why do we need a telcon for Access Control if the IE Team has yet to reply to all the issues raised... |
| 08:49 | <Hixie> | dunno, ask |
| 08:49 | <Hixie> | is there a list of issues they haven't replied to? |
| 08:51 | <annevk> | s/Access Control/XDomainRequest/ makes more sense |
| 08:51 | <annevk> | Hixie, no, though some e-mail from Kris was quite complete |
| 08:52 | <annevk> | http://lists.w3.org/Archives/Public/public-webapi/2008Apr/0056.html |
| 08:53 | <hsivonen> | people don't change positions during telecons anyway, because they don't have enough time to think and verify claims to make an informed change of opinion |
| 08:53 | <Hixie> | YUP |
| 08:53 | <Hixie> | er |
| 08:53 | <Hixie> | yup |
| 08:54 | <Hixie> | been saying that for months |
| 08:54 | <Hixie> | if not years by now |
| 08:54 | <Hixie> | same with f2fs |
| 08:55 | <Lachy> | I hate telcon's cause it doesn't give enough time to think and give a well thought out response either |
| 08:56 | <annevk> | replied |
| 09:01 | <jruderman> | Hixie: http://software.hixie.ch/utilities/js/live-dom-viewer/?%3Cobject%20data%3Dflash%3E |
| 09:01 | <jruderman> | Hixie: in firefox, it somehow acquires a type attribute |
| 09:02 | <hsivonen> | jruderman: I don't see a type attribute in Firefox 3b5 |
| 09:02 | <jruderman> | try adding a space at the end |
| 09:03 | <jruderman> | seems like it only happens if ./flash is cached |
| 09:03 | <hsivonen> | whoa |
| 09:03 | <Hixie> | jruderman: yeah isn't it awesome |
| 09:04 | <annevk> | oh yeah, I noticed some scary activity in a bug report related to that |
| 09:04 | <jruderman> | a mozilla bug report? |
| 09:04 | <annevk> | yes |
| 09:04 | <jruderman> | i'm having trouble finding it |
| 09:05 | <hsivonen> | Hixie: I must say that the hardship of the datagrid content model is largely due to the content model being very abnormal |
| 09:05 | <annevk> | jruderman, https://bugzilla.mozilla.org/show_bug.cgi?id=395110 |
| 09:06 | <hsivonen> | Hixie: it's exceedingly weird that <datagrid><table/>foo</datagrid> is non-conforming but <datagrid>bar<table/>foo</datagrid> is conforming |
| 09:06 | <Hixie> | annevk: i think it would be helpful to list a bunch of e-mails they haven't replied to |
| 09:08 | <Hixie> | annevk: did they ever send technical comments on XHR and AC, btw? |
| 09:09 | <annevk> | there might be one where they agreed not sending cookies would be good |
| 09:09 | <hsivonen> | Hixie: I think they sent one basically saying that the XHR spec was too detailed |
| 09:09 | <annevk> | oh yes, they did e-mail comments on XMLHttpRequest, sorry |
| 09:09 | <annevk> | though it mostly came down to what hsivonen says :( |
| 09:10 | <Hixie> | i meant technical feedback |
| 09:12 | <jruderman> | annevk: i don't think that bug mentions the mysterious appearance of a type attribute |
| 09:12 | <annevk> | jruderman, could be, but that's the bug with the scary comments :) |
| 09:13 | <annevk> | Hixie, I don't remember if the offlist feedback they gave a couple of years back contained technical comments |
| 09:13 | <annevk> | Hixie, other than that I don't think so |
| 09:15 | <jruderman> | filed https://bugzilla.mozilla.org/show_bug.cgi?id=430424 |
| 09:18 | <zcorpan> | Hixie: Error loading the folder list: Internal Server Error. Let Hixie know. |
| 09:18 | <Hixie> | reload |
| 09:18 | <Hixie> | haha |
| 09:18 | <Hixie> | http://www.w3.org/2002/09/wbs/38482/XDRorNot/results |
| 09:18 | <Philip`> | You're not allowed to see the results of this questionnaire. |
| 09:19 | <Hixie> | annevk: what's the timeline on ac and xhr? |
| 09:19 | <jruderman> | i wish it were more obvious which URLs on w3.org are password-protected |
| 09:19 | <Hixie> | that url is the result of a vote on xdr |
| 09:19 | <Hixie> | the results are 11 vs 2 |
| 09:19 | <Philip`> | Which are for/against? |
| 09:20 | <hsivonen> | Philip`: that's Member-only information :-( |
| 09:20 | <Hixie> | put it this way |
| 09:20 | <Hixie> | 2 microsoft people voted |
| 09:20 | <Philip`> | Ah |
| 09:20 | <Hixie> | the vote was actually yes, no, concurr, and a space for rationale |
| 09:21 | <Philip`> | hsivonen: It's not Member-only any more :-) |
| 09:21 | <Hixie> | the results were 2/7/4, with the two yesses having no rationale |
| 09:21 | <Hixie> | and most of hte nos giving different reasons for voting no |
| 09:22 | <Hixie> | it's just funny how the only votes without rationale are the yesses and two of the concurrs |
| 09:23 | <Hixie> | i understand not having a rationale if you concurr |
| 09:23 | <Hixie> | but if you vote yes, you'd think you could give one |
| 09:24 | <jruderman> | what's the difference between concur and yes? |
| 09:25 | <Hixie> | if there are more nos than yesses, concurr means no |
| 09:25 | <Philip`> | What if the no and yes counts are equal? |
| 09:26 | <Hixie> | who knows |
| 09:27 | <annevk> | Hixie, AC depends on pending feedback from Mozilla which is still not there... |
| 09:27 | <annevk> | Hixie, XHR is in Last Call and will hopefully go to CR in June |
| 09:28 | <Hixie> | i meant xhr2 |
| 09:28 | <Hixie> | xxx if you will |
| 09:29 | <Hixie> | not sure what to do about ac |
| 09:30 | <Hixie> | i guess you could try to summarise the use cases we want to deal with |
| 09:30 | <jruderman> | Hixie: err... how is it different from abstain, then? |
| 09:30 | <Hixie> | and what the various concerns are |
| 09:30 | <Hixie> | so we could try to come up with solutions |
| 09:31 | <hsivonen> | jruderman: it affects quorum in some other voting cases |
| 09:31 | <Hixie> | jruderman: again, who knows |
| 09:31 | <Hixie> | voting is dumb |
| 09:32 | <hsivonen> | uh. not quorum but how much over 50% the majority goes |
| 09:32 | <jruderman> | lol |
| 09:32 | <annevk> | xhr2 pretty much depends on ac |
| 09:32 | <Hixie> | annevk: yeah |
| 09:33 | <annevk> | i think jonas is still saying we need a better solution for cookies, but it's a bit unclear to me why and how |
| 09:33 | <annevk> | mostly why at this point, because i thought we already discussed it and the moz sec team was eventually convinced but then it was too late |
| 09:34 | <Hixie> | annevk: in that case, propose to move it to LC and see what happens |
| 09:36 | <inimino> | Hixie: why was that mailing list message removed from www-archive? |
| 09:37 | <Lachy> | inimino, because Hixie responded to an off-list message by CCing www-archive, and Dean complained to the W3C that he didn't have permission to publish it publically |
| 09:37 | <inimino> | I see, thanks, Lachy |
| 09:40 | <annevk> | Hixie, I did and Jonas didn't like it |
| 09:40 | <annevk> | Hixie, http://lists.w3.org/Archives/Public/public-appformats/2008Apr/0043.html |
| 09:42 | <krijn> | http://krijnhoetmer.nl/irc-logs/whatwg/20080422#l-1148 - yeah, thanks Philip` ;) |
| 11:18 | <hsivonen> | Hixie: what's the chance of you banning nested forms in XHTML5 in order to make HTML5 and XHTML5 more consistent with each other? |
| 11:18 | <Hixie> | pretty good if you mail the list :-) |
| 11:19 | <Hixie> | although the chances are zero until i get to wf2 |
| 11:20 | <hsivonen> | ok |
| 11:20 | <annevk> | forms :( |
| 11:21 | <hsivonen> | aaarrgh!!! I've been trying to write code against a faulty set on test cases |
| 11:21 | <hsivonen> | no wonder XPath seems crazy |
| 11:28 | <Hixie> | jesus, "Uniform access to descriptions" is a long www-tag thread even for ww-tag |
| 11:29 | <annevk> | is it interesting? |
| 11:29 | <annevk> | i autodelete that thread |
| 11:30 | <Hixie> | no idea, didn't look at a single message |
| 11:31 | <hsivonen> | the moon message was funny if it was in that thread |
| 11:32 | <hsivonen> | no, it was a different thread |
| 11:32 | <hsivonen> | this one: http://lists.w3.org/Archives/Public/www-tag/2008Mar/0026.html |
| 11:37 | <Hixie> | wow |
| 11:38 | <Hixie> | that takes architectural astronauts to a whole new level |
| 11:38 | <hsivonen> | that's why it's funny |
| 11:39 | <Hixie> | good lord |
| 11:39 | <Hixie> | that thread gets worse |
| 11:39 | Hixie | closes the window |
| 11:48 | <hsivonen> | Hixie: email about nested forms sent |
| 11:57 | <Hixie> | thanks |
| 12:02 | <hsivonen> | let's see if there's any way to shorten this list based on current spec text... http://bugzilla.validator.nu/buglist.cgi?component=HTML5+schema&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED |
| 12:05 | <annevk> | Hixie, XHR2 also depends on progress events |
| 12:05 | <annevk> | apart from that it's done imo although it doesn't get getRequestHeader what Julian would really like to see because he's been the only one to suggest that so far to me |
| 12:06 | <annevk> | oh, and it doesn't have examples and an introduction ... |
| 12:06 | <hsivonen> | if I implement checking for WF2 email addresses and mailto: URIs, which spec for email addresses should I be reading? |
| 12:07 | <hsivonen> | make that mailto: *IRI*s |
| 12:07 | <hsivonen> | IIRC, the original RFC is nuts and allows crazy tokens that no one supports |
| 12:10 | <Hixie> | the wf2 spec should sidestep that |
| 12:10 | <Hixie> | iirc |
| 12:10 | <Hixie> | anyway, bed time |
| 12:10 | <hsivonen> | nn |
| 15:12 | Philip` | wishes Gmail didn't keep going out of sync with itself |
| 15:13 | <Philip`> | (It claims a message received from public-html has the label [Imap]/Drafts even though I sent it ten minutes ago) |
| 16:22 | <Philip`> | Oh, WF2 has a form attribute? That looks potentially useful |
| 16:22 | <Philip`> | (but less useful when I need things to work in IE6) |
| 16:24 | <zcorpan> | Philip`: i think there's at least one js implementation |
| 16:24 | <hsivonen> | WF2 is designed to be emulatable in IE6 |
| 16:25 | <hsivonen> | (I don't know if form='' in particular is emulatable) |
| 16:26 | <takkaria> | hehe, that TAG thread is amazing |
| 16:26 | <takkaria> | they should go read some philosophy of language |
| 16:28 | <Philip`> | http://code.google.com/p/webforms2/wiki/ImplementationDetails doesn't seem to say it supports @form |
| 16:29 | <hsivonen> | I wonder if Gecko and WebKit have a JS API for the form pointer |
| 16:29 | <Philip`> | Is anybody able to access http://webforms2.googlecode.com/svn/trunk/ or does it give the "your query looks similar to automated requests from a computer virus or spyware application" error? |
| 16:29 | <annevk> | hsivonen, <input>.form ? |
| 16:30 | <takkaria> | Philip`: I can get it |
| 16:30 | <hsivonen> | Philip`: I can GET it |
| 16:30 | <Philip`> | takkaria: Okay, I guess Google just hates me |
| 16:31 | <BenMillard> | Philip`, me too |
| 16:31 | <BenMillard> | Philip`, I mean, I can get it too |
| 16:31 | <hsivonen> | annevk: is that settable? |
| 16:31 | <annevk> | hsivonen, no |
| 16:31 | <hsivonen> | doesn't help then |
| 16:32 | <annevk> | oh, I see what you mean, yeah, form="" is new and brav |
| 16:32 | <annevk> | e |
| 16:33 | <hsivonen> | http://www.w3.org/2005/Incubator/cwl/charter |
| 16:34 | <hsivonen> | "Then CWL will realize a language barrier free world in the web and will also enable computers to extract semantic information and knowledge from web pages accurately." |
| 16:35 | hsivonen | believes the way to deal with the language barrier that actually works is *people* investing effort in learning English |
| 16:35 | <annevk> | i doubt that's what tye |
| 16:35 | <annevk> | they mean* |
| 16:35 | <hsivonen> | annevk: what do they mean? |
| 16:36 | <annevk> | i suppose people will have to modify said web pages first :) |
| 16:36 | <annevk> | ah, it says that in the previous paragraph :) |
| 16:38 | <hsivonen> | Esperanto and Interlingua aren't doing so great in enabling Finnish-Dutch communication |
| 16:38 | <hsivonen> | perhaps CWL will |
| 16:39 | <othermaciej> | language barrier free world? |
| 16:40 | <othermaciej> | what? |
| 16:41 | <hsivonen> | othermaciej: looks like RDF will free people from the oppression of having to learn English: http://www.w3.org/2005/Incubator/cwl/XGR-cwl-20080331/ |
| 16:41 | <Philip`> | On the subject of natural language programming, I saw http://www.inform-fiction.org/ recently, which looks kind of neat |
| 16:41 | <Philip`> | where you can write source code that looks like http://www.inform-fiction.org/I7Downloads/Examples/bronze/source_7.html |
| 16:42 | <zcorpan> | hsivonen: LOL |
| 16:44 | <othermaciej> | I see, so we'll solve the translation problem by just writing everything in the form of machine-understandable assertions |
| 16:45 | <othermaciej> | all we have to do to solve the hard problem of translation is solve an even harder problem |
| 16:45 | <Philip`> | You solve the problem by automatically converting from one natural language into a common machine-understandable intermediate form, and then converting back into another natural language |
| 16:46 | <Philip`> | so you don't have to write everything (or anything) as machine-understandable assertions |
| 16:46 | Lachy | published a new blog entry http://blog.whatwg.org/reverse-ordered-lists |
| 16:46 | <othermaciej> | instead of confusing English, I'll be able to read and write statements like agt(purchase(icl>buy(agt>person,obj>thing)).@entry.@past), I) |
| 16:47 | <Philip`> | At least that's how I assume they intend to solve problems, because anything else seems silly... |
| 16:47 | <Philip`> | ("CWL [...] shall enables [sic] users to develop conversion systems between CWL and each natural language." etc) |
| 16:50 | <Lachy> | othermaciej, for those of us who are still stuck in the past with english, care to translate that? :-) |
| 16:50 | <othermaciej> | Lachy: isn't it obvious? |
| 16:51 | <Philip`> | "I bought a person thing"? |
| 16:52 | <takkaria> | frankly they should just use lojban |
| 16:52 | <othermaciej> | this is better, lojban with RDF syntax! |
| 16:53 | <takkaria> | at least a couple hundred people already read lojban though. :) |
| 16:53 | <hsivonen> | takkaria: lojban isn't doing great in terms of supporting existing content and legacy agents |
| 16:54 | <zcorpan> | Lachy: it can be written as reversed="" in xhtml |
| 16:54 | <Philip`> | Millions of people have experience with the language Oddle Poddle |
| 16:55 | <Philip`> | and it's much less wastefully expressive than English, making it far easier for foreigners to learn |
| 16:55 | <Lachy> | zcorpan, yeah, I know, but people are more familiar with the expanded form |
| 16:57 | <Philip`> | Lachy: That blog post has fancy quotes in its example HTML, so it'll break miserably when someone tries to copy-and-paste it |
| 16:57 | <Lachy> | oops, where? |
| 16:58 | <Lachy> | I thought I removed them all |
| 16:58 | <zcorpan> | also has <!– instead of <!-- |
| 16:58 | <Philip`> | Lachy: Everywhere |
| 16:58 | <Lachy> | oh, no, that's WordPress automatically replacing them :-( |
| 16:59 | <zcorpan> | does writing " help? |
| 16:59 | <zcorpan> | or just omitting the quotes? |
| 17:00 | <zcorpan> | "The reversed attribute is a boolean attribute. If present, .... If the attribute is present, ...." |
| 17:01 | <zcorpan> | Hixie: ^ "if present" twice |
| 17:04 | <takkaria> | I think that to prove CWL is expressive enough, they should write a copy of the spec in it |
| 17:04 | <Lachy> | oh no, something has happened to blog.whatwg.org. It's not responding |
| 17:05 | <Lachy> | ah, it's back now |
| 17:06 | <Lachy> | fixed the quotes |
| 17:06 | <Lachy> | time to go home, cya |
| 17:23 | <Philip`> | Philip`: When Lachy gets back, remember to tell him that <ol reversed="reversed" start="10"> should say 100 instead |
| 17:24 | <Philip`> | and s/Movies Sagas/Movie Sagas/ |
| 17:34 | <Philip`> | Lachy: http://krijnhoetmer.nl/irc-logs/whatwg/20080423#l-910 |
| 17:34 | <Philip`> | Also it still says "<!– Items omitted here –>" instead of "<!-- ..." |
| 17:38 | <Lachy> | aargh! I hate WordPress! Why is it replacing my -- with en-dashes!? |
| 17:39 | <hasather_> | Lachy: yes, especially in <code> |
| 17:39 | <didymos> | Philip`, damn, I commented on the start="10", failed to see here first :) |
| 17:39 | <didymos> | s/see/look/ |
| 17:39 | <Philip`> | Lachy: It thinks bloggers are stupid and can't do punctuation, so it has to do it for them |
| 17:40 | <Philip`> | or maybe it thinks bloggers are lazy and don't want to write –, and don't have an en-dash key on their keyboards |
| 17:41 | <Lachy> | bloggers should just learn to type Option+- or Alt+0150 to get en-dashes |
| 17:41 | <Philip`> | I don't have an Option key |
| 17:41 | <Philip`> | or a numpad |
| 17:42 | <annevk> | 쌬ame issue here |
| 17:42 | <annevk> | ooh, what happened there :) |
| 17:42 | <annevk> | maybe something does work |
| 17:42 | <annevk> | 쌬 is what I get for ALT+0150 |
| 17:42 | <Lachy> | Philip`, you'll have to get a external number pad and install windows on your machine |
| 17:43 | <Philip`> | Hmm, how wide is ─? |
| 17:43 | <Lachy> | annevk, it doesn't work linux |
| 17:43 | BenMillard | joins the party by testing Alt+0150–. |
| 17:43 | Philip` | can't tell if it's en- or em- |
| 17:43 | <Philip`> | Lachy: Um, no thanks :-p |
| 17:43 | <annevk> | hmm, windows sounds like a nasty requirement |
| 17:43 | <Lachy> | 0150 is en-dash, ,0151 is em-dash on windows |
| 17:43 | <didymos> | Philip`, since it is monospaced, you really cannot tell :) |
| 17:43 | <hasather_> | I use Caps Lock as a Compoes key, and use Compose+..- for en dash, --- for em dash |
| 17:43 | <hasather_> | *Compose |
| 17:44 | <Lachy> | hasather_, on which system, or which editor? |
| 17:44 | <hasather_> | Ubuntu |
| 17:44 | <takkaria> | hasather_: how do you set that up? |
| 17:44 | Philip` | has never found out how to configure his keyboard to do more than the default |
| 17:44 | <hasather_> | takkaria: System > Prefs > Keyboard |
| 17:45 | <Philip`> | (where the default is altgr+, == ─ and various other things on other keys) |
| 17:45 | <hasather_> | takkaria: Layout Options > Compose key |
| 17:46 | <hasather_> | and it's --. for en dash, not ..- |
| 17:49 | <takkaria> | hasather_: v.useful, ta |
| 17:50 | <hasather_> | takkaria: np, see also: http://www.hermit.org/Linux/ComposeKeys.html |
| 17:54 | <Lachy> | wow, so far 3 different people have told me about that start="10" error using 3 different methods. |
| 17:55 | <Philip`> | Lachy: Well, it is a very blatant error :-p |
| 17:55 | <Lachy> | maybe if I had actually pressed save, they would stop telling me :-) |
| 17:55 | <Philip`> | It's even in bold |
| 17:56 | <Lachy> | I think it's odd that everyone has said it's the 10 that's in error, not the 100 in the sentence before it :-) |
| 17:57 | <Philip`> | Nobody could believe that creationists only use 10 logical fallacies |
| 17:57 | <Philip`> | and it said "counting down from 100" and "Top 100", so the 100 was used twice and was therefore most likely to be the intended value |
| 17:58 | <Lachy> | That's what I thought too. It was 10 in my first draft, then I thought should put it up a bit :-P |
| 18:00 | <Philip`> | blog.whatwg.org says: Internal Server Error |
| 18:01 | <Lachy> | wtf? |
| 18:02 | <Lachy> | sometimes it doesn't respond, sometimes it gives errors, other times it works perfectly |
| 18:04 | <Philip`> | It's strange how hard it is to make a computer accept a network message and send a file back without just randomly failing for no observable reason |
| 18:04 | <Lachy> | I haven't changed anything settings on the server for quite a while, so maybe dreamhost is having more troubles |
| 18:05 | <Lachy> | does anyone remember which server Hixie's site is running on? Is it Spunky? |
| 18:07 | <Lachy> | dreamhost status is only reporting mail issues with spunky, so that wouldn't explain it |
| 18:40 | <BenMillard> | I've had a few people e-mail me about scope being absent from <td>: http://www.whatwg.org/specs/web-apps/current-work/multipage/section-tabular.html#the-td |
| 18:41 | <BenMillard> | they want it back for authoring convenience, mainly for row headers |
| 18:41 | <annevk> | if it's header, shouldn't <th> be used? |
| 18:41 | <BenMillard> | they don't want centered bold text |
| 18:42 | <annevk> | interesting, I thought accessibility was all about semantics :) |
| 18:42 | <BenMillard> | these peeps work in the real world, with designers and managers |
| 18:42 | <Philip`> | The semantics could be defined so that <td scope> was a heading |
| 18:42 | <BenMillard> | Philip`, yes that's what I think should be the case |
| 18:43 | <annevk> | whatwg⊙wo :) |
| 18:43 | <takkaria> | BenMillard: th { font-weight: normal; text-align: left; }? |
| 18:43 | annevk | wonders about potential counter arguments |
| 18:44 | <annevk> | i guess it makes it less clear when to use <th> |
| 18:44 | <BenMillard> | takkaria, that kills column header styles as well |
| 18:44 | <takkaria> | ah. true |
| 18:44 | <zcorpan_> | tbody th { ... |
| 18:44 | <annevk> | th:first-child { } |
| 18:45 | <Philip`> | th.plain { ... } |
| 18:45 | <BenMillard> | zcorpan, that kills column header styles as well because nobody uses <thead> outside the blogs of markup enthusiasts :) |
| 18:45 | <Philip`> | Your selectors are all far to complex :-p |
| 18:45 | <zcorpan_> | BenMillard: :) |
| 18:45 | <annevk> | th[scope] { } |
| 18:45 | <zcorpan_> | annevk: doesn't work in ie6 |
| 18:45 | <zcorpan_> | moreover, why do you need scope if you use <th>? |
| 18:46 | <BenMillard> | indeed, if you use <th scope="row"> and then undo it with CSS you may as well use <td scope="row"> imho |
| 18:46 | <zcorpan_> | just <td>? |
| 18:47 | <Philip`> | BenMillard: "nobody" is a dangerous thing to say - |
| 18:47 | <Philip`> | s/end of line// |
| 18:47 | <Philip`> | http://www.budapestinfo.hu/ looks like a counter-example, since it's a touristical site and not a blog :-p |
| 18:47 | <Philip`> | and it seems to actually use <thead> sanely |
| 18:48 | <annevk> | If td and scope needs to work the next thing you get is headers pointing to td |
| 18:48 | <BenMillard> | annevk, yes I thought headers+id should match <td id> |
| 18:49 | <annevk> | that's not the case currently |
| 18:49 | <annevk> | I like the current model more, to be honest |
| 18:49 | <annevk> | But I don't really feel strongly about this |
| 18:50 | <BenMillard> | I think the advice we give should be "use <th> for all your headers. set styling with CSS" |
| 18:50 | <BenMillard> | but supporting existing content and current authoring practices makes me think <td scope> and suchlike should also work |
| 18:51 | <annevk> | should they be conforming? |
| 18:51 | <BenMillard> | probably. if they work, why complain? |
| 18:52 | <annevk> | true |
| 18:53 | <BenMillard> | mind if I send the mail to public-HTML rather than WHATWG? that's where the people who mailed me will expect to see any discussion |
| 18:53 | Philip` | is happy with anything that isn't cross-posted :-) |
| 18:54 | <annevk> | BenMillard, heh, no need to ask me permission where you'd like to send e-mail :) |
| 18:56 | <zcorpan_> | BenMillard: mail it to Hixie and cc the secret whatwg cabal |
| 18:56 | <BenMillard> | zcorpan, shhh, don't talk about that in public... |
| 18:56 | <zcorpan_> | oops! |
| 18:57 | <BenMillard> | :D |
| 18:57 | <annevk> | what, you're saying this channel is logged? |
| 18:57 | <Philip`> | Don't worry, we can delete that line from the logs |
| 18:57 | annevk | though this was the secret hangout of the whatwg cabal |
| 18:57 | <annevk> | thought, even |
| 18:57 | <zcorpan_> | krijn: gotta help us out here |
| 18:58 | <BenMillard> | I'm putting together a little e-mail to start a thread on public-HTML about <td scope> and <td> with headers+id now |
| 19:10 | <hsivonen> | BenMillard: I'd rather have align back |
| 19:11 | <Philip`> | hsivonen: That wouldn't solve the boldness problem |
| 19:11 | <Philip`> | and I don't think <th></b>Not bold text</th> could be made to work |
| 19:13 | <zcorpan_> | Philip`: would have worked in mosaic if it supported <th>, i guess |
| 19:14 | <annevk> | yet more flames: http://intertwingly.net/blog/2008/04/19/Ingrates#c1208969184 |
| 19:15 | <annevk> | "... I haven’t been tracking who’s on what side of the train wreck that is HTML5 ..." |
| 19:15 | <Philip`> | At least it's clear enough which side he's on |
| 19:16 | <Philip`> | Anyway, I like train wrecks, they make me think of Half Life 2 |
| 19:16 | <BenMillard> | e-mail sent |
| 19:19 | <BenMillard> | "Allowing <th scope> to avoid incorrect values also seems potentially useful." actually that's stupid and wrong and I feel stupid for writing it :P |
| 19:19 | <BenMillard> | simply writing <th> does that already |
| 19:20 | <hsivonen> | Philip`: why is the default bold a problem? |
| 19:20 | <BenMillard> | hsivonen, designs don't always want bold table headers |
| 19:21 | <BenMillard> | it's rather a heavy-handed style in designs which are otherwise light |
| 19:21 | <hsivonen> | turning it off in CSS is trivial |
| 19:21 | <Philip`> | hsivonen: Changing alignment in CSS is similarly trivial, so why would you rather have align back? |
| 19:22 | <hsivonen> | Philip`: cell alignment tends to be contextual |
| 19:22 | <BenMillard> | hsivonen, the problem is when some headers should be bold but others should not. commonly, bold column headers and non-bold row headers |
| 19:22 | <hsivonen> | while th font tends to be a site-global thing |
| 19:23 | <hsivonen> | BenMillard: hmm. that seems like a weird thing to want |
| 19:23 | <BenMillard> | hsivonen, that's why you and I aren't a designers :) |
| 19:23 | <hsivonen> | tbody th { font-weight: normal; } |
| 19:23 | <BenMillard> | hsivonen, that was suggested a bit earlier |
| 19:24 | <hsivonen> | I have a really hard time believing that a designer can have enough clue to use scope/headers but not enough clue to write the above style rule |
| 19:25 | <hsivonen> | I know, sense of logic at the door, but *still* |
| 19:25 | <BenMillard> | it's a fair point |
| 19:26 | <BenMillard> | the problem is it requires <thead> and <tbody> in the markup to work |
| 19:26 | <Philip`> | hsivonen: Enough clue to use scope/headers, or enough clue to use them correctly? |
| 19:26 | <zcorpan_> | hsivonen: the designer isn't necessarily the one writing the html and css |
| 19:26 | <hsivonen> | BenMillard: actually, it only requires thead in the markup :-) |
| 19:26 | <BenMillard> | hsivonen, pfeh :P |
| 19:27 | <hsivonen> | zcorpan_: well, it's hard to believe that the person writing the HTML couldn't write the style rule |
| 19:27 | <zcorpan_> | hsivonen: but <tbody> is shorter than </thead> |
| 19:27 | <Philip`> | <thead> appears to be used much less than @scope |
| 19:27 | <Philip`> | Everybody uses <tbody> but that's probably just output from tools |
| 19:27 | <hsivonen> | Philip`: I thought the assumption was that the baseline was using them to point at the right cells |
| 19:28 | <BenMillard> | philip`, that's in line with what I find amongst companies I work with |
| 19:28 | <BenMillard> | they've never seen a <thead> element, probably never noticed <tbody>, but have seen scope="col" and scope="row" |
| 19:29 | <Philip`> | http://www.banfill-locke.org/ uses a 'tbody th' rule but doesn't actually have any <th> elements |
| 19:31 | <Philip`> | http://finance.sina.com.cn/ used to have '#changeTop5 tbody th {text-align:left; font-weight:normal; padding-left:10px;}' but seemingly no more |
| 19:31 | <BenMillard> | the things authors currently do to get around default styling a pretty awful |
| 19:31 | <BenMillard> | s/a/are |
| 19:32 | <Philip`> | http://www.espoo.fi/peruskoulut/kuitinmaki had a a 'table.Calendar td, table.Calendar tbody th {' but I can't access that site now |
| 19:32 | <Philip`> | s/a // |
| 19:32 | <Philip`> | So, it's not a very commonly used technique at the moment |
| 19:33 | <BenMillard> | it actually takes quite a lot of imagination if you aren't a markup expert |
| 19:33 | <Philip`> | Oh, the page loaded, and it still has the calendar thing plus a 'table.Calendar thead th {' |
| 19:34 | <Philip`> | and seems to be using thead correctly |
| 19:35 | <Philip`> | so that's one page in 130K that uses CSS inside the HTML page (i.e. ignoring external CSS files) to style th differently in thead and tbody |
| 19:35 | <BenMillard> | the first row in the <thead> is navigation either side of a title; not a set of table headers imho |
| 19:36 | <Philip`> | Well, by "correctly" I only really mean "at the top of the table with some sort of headery stuff" (as opposed to e.g. wrapping the entire page in a thead in a layout table) |
| 19:37 | <BenMillard> | yes, for that definition it is "correct" :) |
| 19:37 | <Philip`> | I automatically lower my expectations whenever I'm looking at web content :-) |
| 19:38 | <BenMillard> | lots of bgcolor and style attributes (some just style="") yet it has a <link rel="stylesheet"> and a <style> |
| 19:39 | <BenMillard> | it will be nice when everyone writes markup as good as we can |
| 19:39 | <BenMillard> | I'm unsure if that will ever happen, though |
| 19:41 | <Philip`> | I don't think you should call my markup good, judging by some of what I seem to have written |
| 19:42 | <Philip`> | It's far better than average, judging by what I've seen of average code, but much of mine is definitely not at all good :-) |
| 19:45 | <Philip`> | Oops, looks like it'll start getting dark soon - time to go home... |
| 19:45 | <BenMillard> | Philip`, useful stats and use cases as always :) |
| 19:45 | hsivonen | wonders if < and > comparisons with NaN in XPath are true or false |
| 19:47 | <Philip`> | Maybe they are Not-a-Boolean |
| 19:48 | <hsivonen> | Philip`: everything in XPath can be coerced to truthiness |
| 19:49 | <Philip`> | Is everything necessarily coerced into a single deterministic state of truthiness, or could you split into a quantum superposition of every possible state? |
| 19:54 | <hsivonen> | I think test for attribute presence before trying to coerce into a number |
| 20:13 | <Hixie> | ~!!!!!!!!!!!!!!!!!!!!!!!!`````````````1111 |
| 20:14 | <hasather_> | Hixie: did your cat just walk on the kwyboard? |
| 20:15 | <virtuelv> | looks like something stuck between the ~ and 1? |
| 20:16 | <hsivonen> | custom kb layout? |
| 20:16 | <Hixie> | yes |
| 20:16 | <Hixie> | sorry about that |
| 20:16 | <Hixie> | love them dearly, but they need to learn to not sit on my laptop |
| 20:17 | <Hixie> | Lachy: i have a dreamhost ps, and it is configured to use slightly less cpu and ram than is sometimes necessary |
| 20:18 | <hsivonen> | Hixie: can Dreamhost VMs grow and shrink RAM/CPU elastically? |
| 20:20 | <Hixie> | hsivonen: yes, but you have to request the amount if you want it to chanve |
| 20:22 | <hsivonen> | Hixie: ok. It seems to me that Dreamhost and Amazon EC2 need some off-the-shelf Google App Engine-ish software for managing on-demand resource usage |
| 20:22 | <Hixie> | heh |
| 20:23 | <Hixie> | well google app engine has the same problem really |
| 20:23 | <Hixie> | if you hit your quota, you start serving 500s or some such |
| 20:23 | <Hixie> | i don't see any way to avoid that |
| 20:23 | <hsivonen> | credit card number and free license to grow on demand :-) |
| 20:23 | <annevk> | e-mail / sms when you nearly hit it and allow for grow on demand |
| 20:23 | <Hixie> | i'll take donations :-) |
| 20:24 | <hsivonen> | free as in not restricted |
| 20:24 | <hsivonen> | I took a look at what Amazon EC2 would offer for Validator.nu |
| 20:25 | <hsivonen> | with the current load, it would be more expensive than the current host |
| 20:25 | <hsivonen> | and the real problem with EC2 is that everyone needs to reinvent a system that fires up more VMs on demand and shuts them down on demand |
| 20:27 | <hsivonen> | (Validator.nu could be a good fit for App Engine for Java, since there's no writing to persistent storage or log-in, hence, the BigTable/Google Accounts lock-in risk would be avoided) |
| 20:37 | <Lachy> | Hixie, the spec doesn't clearly address this use case http://blog.whatwg.org/reverse-ordered-lists#comment-25249 |
| 20:37 | <annevk> | http://lists.w3.org/Archives/Public/public-forms/2008Apr/att-0099/2008-04-23.html#topic9 |
| 20:37 | <Lachy> | although, maybe that's because the use case itself isnt entirely clear. But, in any case, authors should be allowed to use ol for that instead of wasting time finding work arounds |
| 20:38 | <annevk> | ^^ Forms WG on Forms TF |
| 20:40 | <Hixie> | Lachy: i guess the strict answer is you use CSS, but yeah, few people are going to die if you just use <ol reversed> |
| 20:42 | <Lachy> | hixie, yeah, it's not so hard to style a ul with numbers, but when the spec causes people to seriously question borderline cases like that, it's sometimes easier to fix the spec than to get people to realise they're wasting time and effort |
| 20:43 | <othermaciej> | annevk: willI be depressed reading that? |
| 20:43 | <Lachy> | But I can't think of a way to fix the spec, without blurring the distinction between ol and ul. |
| 20:43 | <Lachy> | This makes little sense: "I think the disagreement is whether a core XForms processor should respond to the HTML brand of syntax. In the tag soup example, no, but if you had well-formed XML, would we expect an XForms processor to do that? Maybe RFC-2119 with May or Should instead of Must." |
| 20:44 | <Philip`> | Which/whose disagreement are they referring to? |
| 20:45 | <Lachy> | AFAICT, the suggestion is to use a relaxed conformance criteria in a way that leaves a big choice for implementers between 2 very different processing requirements. |
| 20:45 | <Lachy> | which is, of course, a great way to achieve interop. :-) |
| 20:47 | <Philip`> | It sounds to me (in the absence of knowledge and context) like the question is whether all XForms processors must support the XHTML forms syntax, or whether that should be an optional feature that only some people (e.g. browser developers) will implement |
| 20:48 | <Lachy> | ah, that makes a little more sense |
| 20:49 | <Philip`> | (where "XHTML forms syntax" is something that's backward-compatible with current form usage but gets mapped onto an underlying XForms processing model, or something, I guess) |
| 20:49 | <othermaciej> | I think they are talking about their proposal for a more HTML-like syntax for XForms |
| 20:49 | <othermaciej> | (but still with many of the XForms differences from classic HTML forms, like <select1>) |
| 20:51 | <Lachy> | I think, rather than focussing on syntax, they should be focussing on architectual consistency between the DOM/HTML's Form Processing model, and their XForms model. Syntax should be left entirely up to the HTMLWG |
| 20:52 | <annevk> | That depends on whether anyone is actually interested in implementing an XForms model |
| 20:52 | <annevk> | Any of the browser vendors, that is. |
| 20:53 | <Lachy> | annevk, I don't think any of the browser vendors would be. |
| 20:53 | <othermaciej> | Lachy: according to them, syntax is architecture |
| 20:53 | <annevk> | SVG WG has similar sentiments |
| 20:53 | <othermaciej> | also, they assume that HTML Forms should transition to having an underlying XForms processing model |
| 20:54 | <othermaciej> | also they seem to feel that "who specified this first" is architecture |
| 20:54 | <othermaciej> | "Part of the issue there is that at the broader architectural level, one of the principles I was trying to get across is that all of the efforts to improve HTML going forward should adopt the principle that features that people would like to have that are already expressed in a prior recommendation of the W3C, that those prior recommendations should take priority on how to make that feature." |
| 20:54 | <annevk> | fortunately HTML was defined first :) |
| 20:55 | <annevk> | (though that's a lame argument, see CSS Ani vs SVG Ani) |
| 20:55 | <hsivonen> | it's a lame argument, yes |
| 20:56 | <hsivonen> | but indeed HTML forms were here first and have awesome deployment and network effects |
| 20:58 | <Lachy> | maybe the problem is that the XForms WG are working on this backwards. They already have their solution, and their trying to map that solution onto HTML Forms, instead of looking directly at the problems with HTML forms and working out how to solve them without pre-conceived solutions |
| 20:58 | <othermaciej_> | well, their architecture is already perfect |
| 20:59 | <othermaciej_> | so they just have to figure out how to fix the flawed HTML Forms model to map to it |
| 21:00 | <hsivonen> | I don't see what their XForms business continuity case is once the outcome gets far enough from XForms code-wise |
| 21:00 | <takkaria> | I'm not quite sure what "We should ask how Web Forms 2.0 tables and repetition map into a recognized data layer, with their syntax?" means, esp. "recognised data layer" |
| 21:01 | <Slant> | Has anyone noticed that the CSS keywords "thin" and "thick" aren't includedi n the sanitization rules? |
| 21:02 | <annevk> | Slant, if you're talking about the wiki page on that, dunno, feel free to edit it :) |
| 21:03 | <Slant> | annevk: I did a long time ago, and apparently it was reverted. I also reported it August of '07 on the Google Code issue tracker. |
| 21:03 | <Slant> | I'm wondering what proper way to go about fixing this is? |
| 21:03 | <Slant> | (Write a script to go through the CSS spec and pull all the keywords?) |
| 21:03 | <annevk> | I don't really have an opinion on the matter :) |
| 21:04 | <annevk> | Did you add it to the talk page? |
| 21:04 | <takkaria> | oh, people might be interested, I got accepted to work on a C-language HTML5 parser in Google's summer of code |
| 21:05 | <annevk> | takkaria, html5lib like or for a product? |
| 21:06 | <annevk> | Hixie, nice work on the FAQ :) |
| 21:07 | <takkaria> | annevk: it's a standalone library intended to be used in a lightweight newish web browser |
| 21:07 | <annevk> | cool |
| 21:11 | <hsivonen> | takkaria: congratulations |
| 21:11 | <hsivonen> | takkaria: will it be libxml2-API-compatible |
| 21:11 | <hsivonen> | ? |
| 21:12 | <annevk> | othermaciej, yo, I raised an issue on DOM3Events and namespaces |
| 21:12 | <othermaciej> | annevk: cool |
| 21:13 | <annevk> | othermaciej, it seems MS is not that interested either |
| 21:13 | <takkaria> | hsivonen: my current plan is to build a tree directly using libxml2 structures, so libxml2 API calls should work with it |
| 21:17 | <annevk> | issue-123 :) |
| 21:20 | <Philip`> | takkaria: Sounds useful :-) |
| 21:20 | <Philip`> | When are you going to be working on that? |
| 21:20 | <Philip`> | (I need to try to finish my C++ parser before then :-p ) |
| 21:21 | <takkaria> | Philip`: from whenever ink arrives for my printer til September |
| 21:40 | <hsivonen> | ouch. progress has *lots* of inequalities to satisfy... |
| 21:41 | <Hixie> | only three! |
| 21:42 | <Hixie> | annevk: wasn't much work, but it needed it |
| 21:42 | <hsivonen> | Hixie: there are many pairwise inequalities |
| 21:43 | <hsivonen> | also, value and max sometimes coming from textContent is not helping |
| 21:43 | <Hixie> | yeah |
| 21:44 | <hsivonen> | I'm semisecretly hoping that the textContent alternative just went away, because doing it correctly in an internationalized way is going to be really complex |
| 21:45 | <hsivonen> | and leaving it English-only is a long list thread waiting to erupt |
| 21:59 | <Dashiva> | Hixie, Philip`: This is where I say "I told you so" :P |
| 22:02 | <Philip`> | Dashiva: Thanks for collecting all that graph data and sending it to me last night |
| 22:14 | <Lachy> | annevk, I just sent the proposal to drop NSResolver from selectors api to public-webapi |
| 22:15 | <annevk> | heh, some people will experience a no namespace overflow now |
| 22:16 | <Lachy> | yeah, I noticed. I wasn't expecting the issue to be raised againsed DOM3 Events |
| 22:17 | <annevk> | me neither, but I felt like saying it during the telcon and then I raised it so it was not forgotten |
| 22:17 | <Lachy> | I filled out the arguments a bit more from what I had sent internally. I tried to cover all the possible counter arguments I could think of |
| 22:17 | <annevk> | nice |
| 22:18 | <annevk> | though namespace fans will be glad to know that the first spec I take to CR will be about namespaces :) |
| 22:18 | <Lachy> | which spec is that? |
| 22:18 | <annevk> | css3-namespace |
| 22:19 | <Hixie> | Dashiva: about what? :-) |
| 22:20 | <Dashiva> | <Dashimon> I'm sure Philip` is already doing it |
| 22:20 | <Hixie> | ah |
| 22:20 | <Hixie> | hehe |
| 22:20 | <Hixie> | thanks! |
| 22:20 | <Philip`> | Dashiva: You were wrong about that, since I wasn't already doing it when you said that |
| 22:20 | <Hixie> | the graph is nicely flat |
| 22:20 | <Philip`> | In fact, I never did it at all, I don't know what you're talking about |
| 22:20 | <annevk> | will the lines ever cross :) |
| 22:22 | <Philip`> | By the way, if anybody ever wants to do something like 'svn blame' on the spec and doesn't want to hurt Hixie's server, I've got a local copy of the SVN repository on an otherwise-idle machine, though I suppose I have high latency and am therefore not very useful |
| 22:23 | <hsivonen> | does blame show anything else but blame Hixie for everything_ |
| 22:23 | <hsivonen> | ? |
| 22:23 | <gsnedders> | or someone could just make a git clone of it… |
| 22:24 | <gsnedders> | hsivonen: revision, date |
| 22:24 | <hsivonen> | ah right |
| 22:24 | <gsnedders> | (then other people could just clone the git clone) |
| 22:24 | <Philip`> | It show the revision in which each line was Hixie's fault |
| 22:24 | <Philip`> | s//s/ |
| 22:24 | <gsnedders> | But we already know it's Hixie's fault, so who care's when he made the mistake :P |
| 22:24 | <gsnedders> | (And yes, I know there is a valid use-case) |
| 22:27 | <Philip`> | gsnedders: Why would a git clone be better than svnsync? |
| 22:28 | <gsnedders> | Philip`: because it stores it more efficiently, and blame itself is far quicker. |
| 22:39 | <hsivonen> | Hixie: unless I'm mistaken, just the attribute cases (ignoring textContent altogether) yield 20 different assertions |
| 22:40 | <hsivonen> | first each pairwise inequality with attributes present and then comparisons against 0 or 1 when min/max is absent |
| 22:41 | <Philip`> | gsnedders: Who cares about efficiency? svn blame only takes 5m22.461s |
| 22:42 | <Hixie> | hsivonen: sounds like you're doing it in a more complicated way than necessary |
| 22:42 | <Hixie> | hsivonen: just get the values, set them to defaults if they're missing, and then check the inequalities in three steps |
| 22:42 | <Hixie> | assuming you have a language like python that can do chain inequalities |
| 22:42 | <Hixie> | otherwise, as 7 steps |
| 22:43 | <hsivonen> | Hixie: would that lead to an error message that sucks? |
| 22:43 | <Philip`> | Revision 1 is the most stable, with 8277 lines unchanged since then; then 1037, 1310, 1033 and 1036 still have more than a thousand lines remaining in the latest version |
| 22:43 | <hsivonen> | Hixie: now I have 20 different error messages |
| 22:43 | <Hixie> | hsivonen: ah well if you want to report each case differently then yes, you may well have a lot fo different checks |
| 22:45 | <hsivonen> | Hixie: also, XPath isn't that great |
| 22:46 | <Philip`> | XPath should have a python("...") function |
| 22:46 | <hsivonen> | indeed |
| 22:47 | <hsivonen> | or scheme() |
| 22:47 | <hsivonen> | or at least conditional experssions |
| 22:47 | <hsivonen> | or Python-style 'or' and 'and' return values |
| 22:48 | <hsivonen> | I suppose with Jython, it would be possible to make a Schematron flavor that used Python as its query language |
| 22:49 | <Philip`> | Or use Rhino and JS |
| 22:50 | <Lachy> | hsivonen, I've got a small feature enhancement idea for the validator. |
| 22:51 | <hsivonen> | Lachy: what is it? |
| 22:51 | <Lachy> | A general purpose metadata/atribute value inspection tool to help authors inspect the values of title="" attributes (especially for <abbr>), href attributes for links, etc. |
| 22:52 | <Lachy> | things that aren't strictly conformance errors, but are still subject to common authoring mistakes |
| 22:52 | <hsivonen> | Lachy: why do authors need to inspect href? |
| 22:53 | <hsivonen> | how like is it to link to a non-404 URI and have the wrong URI? |
| 22:53 | <hsivonen> | s/like/likely/ |
| 22:53 | <Lachy> | occasionally, I come across links in blogs posts that are marked up as <a href="">foo bar</a>, where the link was supposed to link to some 3rd party site, but they forgot to paste the link in |
| 22:53 | <hsivonen> | how likely would a person notice the error in a long list of URIs? |
| 22:53 | <hsivonen> | ah. that's a specific case |
| 22:53 | <Lachy> | so empty href values should be flagged |
| 22:54 | <hsivonen> | is the empty string a valid IRI ref? |
| 22:54 | <Lachy> | it is a valid reference to the current document |
| 22:54 | <Lachy> | but the use case for actually doing so are slim |
| 22:55 | <hsivonen> | looks like a case for a warning--not necessarily a special report |
| 22:55 | <gsnedders> | I use it fairly often, actually |
| 22:55 | <hsivonen> | gsnedders: why? |
| 22:55 | <Lachy> | for abbr, now that omitting title is allowed, some authors still might want to know if they missed one by mistake |
| 22:55 | <hsivonen> | gsnedders: why do you link to current doc without fragment? |
| 22:55 | gsnedders | notes he taken sleeping pills about half an hours ago and is about to fall alseep |
| 22:55 | <Philip`> | <form action=""> is more useful |
| 22:56 | <hsivonen> | oh yes indeed |
| 22:56 | <gsnedders> | hsivonen: In short, things like the link to current doc at top of spec for example |
| 22:56 | <gsnedders> | hsivonen: and quoting things from the page page |
| 22:56 | krijn | reminds zcorpan_ of his apathy ;) |
| 22:56 | <annevk> | krijn, yo |
| 22:56 | <annevk> | ah, pm |
| 22:56 | <hsivonen> | is zcorpan_ saying something that needs censoring? |
| 22:57 | <Philip`> | People can find abbr where they missed title by telling their text editor to search for "<abbr>" |
| 22:57 | <Lachy> | Philip`, and they can also search for href="" |
| 22:58 | <Lachy> | but having to manually search for each individual case like that is more time consuming that having a tool do so automatically |
| 22:59 | <Lachy> | WOW! Microsoft supports the proposal to drop NSResolver :-) |
| 22:59 | <krijn> | hsivonen: he did ^ |
| 23:01 | <hsivonen> | Lachy: I predict a TAG thread and an objection from another WG |
| 23:02 | <Lachy> | which WG? |
| 23:02 | Retrieving | #whatwg modes... |
| 23:02 | <annevk> | any |
| 23:02 | <hsivonen> | Lachy: the one now objecting to CSS namespace @-rules |
| 23:03 | <annevk> | they retracted that actualy |
| 23:03 | <annevk> | actually* |
| 23:03 | <hsivonen> | oh. good. |
| 23:03 | <hsivonen> | I though it was still part of telecon agenda and stuff |
| 23:04 | <hsivonen> | theught |
| 23:04 | <hsivonen> | thought |
| 23:04 | <hsivonen> | Lachy: I've filed your suggestion as http://bugzilla.validator.nu/show_bug.cgi?id=175 |
| 23:04 | <hsivonen> | Lachy: warning about empty href is going to happen |
| 23:04 | <hsivonen> | dunno about the rest |
| 23:04 | <Lachy> | oh, I didn't realise you had your own bugzilla |
| 23:05 | <hsivonen> | I don't want to build inspectors for metadata that is only marginally useful or downright useless |
| 23:05 | <hsivonen> | and I'm not sure about the usefulness of abbr title yet |
| 23:06 | <Lachy> | yeah, I'm not sure how useful it is either. Just wanted to get the idea out while I had it |
| 23:36 | <Lachy> | hmm. Maybe the approach to take now is to take Bjoern's advice and require UAs that don't support namespaces to throw a NOT_SUPPORTED_ERR if a non-null NSResolver is passed, but still keep NSResolver defined in the spec |
| 23:36 | <Lachy> | Then, when it comes time to exit CR, if we don't have 2 interoperable implementations of the NSResolver feature, we can drop it then |
| 23:39 | <othermaciej> | that would get in the way of finding a better solution than NSResolver |
| 23:42 | <Lachy> | oh, yeah. |
| 23:42 | <Lachy> | can you reply to the thread and say that? |