00:00 | <kennyluck> | I still don't know why can't we just reuse the <b> pattern or perhaps modified as "stylistically offset from the normal props without conveying extra importance, emphasis and document edit (for <ins>)" |
00:01 | <Hixie> | kennyluck: because if it's the same as <b>, then why do we need it at all? |
00:01 | <kennyluck> | Hixie, it's a subset of <b> like <i> is a subset of <b>. |
00:01 | <kennyluck> | (HTML5-logy) |
00:01 | <Hixie> | <i> is a superset of <b> |
00:01 | <Hixie> | actually that's not quite true |
00:02 | <Hixie> | they cover different and mostly not overlapping roles |
00:02 | <Hixie> | see the earlier discussion |
00:46 | <Hixie> | i found a way to define <u> that i can live with. finding the right terminology wasn't easy, and i'm not sure i really succeeded, so i might tweak it some more. |
00:54 | <Hixie> | still not really sure the use cases justify its existence, but i guess the same applies to <samp> and that one is still in, so... |
01:03 | <hober> | Hixie: there's an en-GB-x-Hixie'ism in the <u> text |
01:03 | <hober> | misspelt should be misspelled |
01:07 | <Hixie> | heh |
01:07 | <Hixie> | thanks |
01:07 | <Hixie> | hober: actually all my dictionaries say both are accetpable |
01:08 | <Hixie> | acceptable |
01:08 | <TabAtkins> | Your dictionaries are too friendly to the crown. |
01:08 | <Hixie> | and by "my dictionaries" i mean, apple's, wiktionary, and the ones i found on google |
01:08 | <Hixie> | none mention that this is a Brit vs US thing |
01:08 | <Hixie> | which they usually do |
01:18 | <Philip`> | http://thespellingblog.blogspot.com/2010/12/learned-or-learnt-spelled-or-spelt.html has potentially relevant graphs |
01:29 | <TabAtkins> | It's odd that your dictionaries don't mention the "t" as a Britishism. American English has a strong preference for "ed", as the graphs at Philip`'s link show. |
01:31 | <Hixie> | well if you care, one of them at least is user-editable |
01:31 | <Hixie> | :-) |
01:33 | <TabAtkins> | Indeed. "spelled" and "spelt" clearly list each one as a british or american/canadian variant, as appropriate, but "misspelt" doesn't. |
01:36 | <TabAtkins> | Fixed, woo! |
02:23 | <zewt> | clicking on a reference in the spec (http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#dom-canvas-getcontext "getContext"), then right-clicking on the real "#dom-canvas-getcontext" link in the overlay, causes the overlay to disappear, so I can't copy-link-location the link; guessing it's a missing e.button==0 check |
03:31 | <karlcow> | http://www.mobilexweb.com/blog/symbian-anna-browser-html5 |
03:31 | <karlcow> | "Nokia has just announced Symbian ‘Anna’, an updated version of Symbian^3 that will be shipped with new devices, such as X7 and E6" |
05:35 | <Hixie> | seriously? we have <table border> now too? |
05:35 | <Hixie> | jesus |
05:35 | <Hixie> | it's like we're back in 1997 |
05:38 | <zewt> | better do the macarena |
06:23 | <hsivonen> | I wonder what SanDisk is going to get out of being a W3C Member. |
07:30 | <zcorpan> | i wonder how ie's software rendering compares to other browsers' software rendering |
07:32 | <othermaciej> | well for one thing, it's way more native |
08:04 | <hsivonen> | how did a synchronous thing like Blob.size end up in a new API? that's sadness. |
08:05 | <ryanseddon> | Would that syncchronous stuff be so it can run in a worker |
08:05 | <ryanseddon> | *synchronous |
08:08 | hsivonen | wonders if Apple's marketing feels it missed a huge opportunity to be the first to promote Native HTML5. |
08:08 | <ryanseddon> | hsivonen: they'll market it as magical HTML5 |
08:09 | <hsivonen> | I believe Firefox already has awesome HTML5. |
08:09 | <Hixie> | revolutionary html5! which would be ironic given how html5 was first introduced ("evolution not revolution") |
08:10 | <ryanseddon> | don't let facts get in the way Apple marketing |
08:10 | <othermaciej> | what are "facts"? |
08:12 | <ryanseddon> | Facts is a TV program in Hong Kong, which broadcast short films obtained or shoot with information from audiences. |
08:52 | <zcorpan> | instead of native HTML5, we should be marketing foreign HTML5 |
08:53 | <Hixie> | i don't really understand what there is to market |
08:53 | <Hixie> | but what do i know |
08:53 | <zcorpan> | well microsoft use the term to market their new CSS features |
08:54 | <Hixie> | in favour of what? |
08:54 | <zcorpan> | layout tables? |
08:55 | <Hixie> | they're markup advocates now? |
08:55 | <zcorpan> | yeah, last year they advocated use of custom elements |
08:56 | <zcorpan> | (in their video they also call css rules for 'markup') |
08:57 | <othermaciej> | I wonder, does their Native HTML5 still support Same Markup? |
08:58 | <zcorpan> | of course |
08:58 | <aho> | In this case "native" can be interpreted as "from Microsoft". So, technically they aren't lying. There are just manipulative bastards. #IE10 |
08:58 | <aho> | :> |
08:58 | <zcorpan> | same markup as last year |
08:59 | <zcorpan> | same as every year, james |
09:00 | <othermaciej> | I like that the IE team is working hard to improve their engine, but their marketing buzzwords are just really weird sometimes |
09:02 | <aho> | i agree |
09:02 | <aho> | there shall be less cocain for the pr department |
09:02 | <aho> | +e |
09:03 | <aho> | btw, ie10 changes/additons w/o the BS is over here: http://msdn.microsoft.com/en-us/ie/gg192966 |
09:06 | <Hixie> | "Internet Explorer Platform Preview must be in ”IE10 Standards Mode” to correctly display webpages" aka "we still don't follow the specs most of the time" |
09:06 | <Hixie> | ("even on things that we claim to follow the specs on") |
09:07 | <Peter`> | I wonder why they didn't decide to start deprecating the compatibility modes by not including the IE9-mode |
09:07 | <Peter`> | It would be a good starting point, seeing that it's a recent and more modern browser. |
09:08 | <zcorpan> | Peter`: indeed |
09:08 | <Hixie> | wow, a huge proportion of the stuff on that page is proprietary (i.e. vendor-prefixed) stuff |
09:08 | <zcorpan> | maybe now they just introduce more modes for the hell of it |
09:08 | <Hixie> | Peter`: the more modes they introduce, the more the web fragments, at least if they get much market share |
09:08 | <Peter`> | This is an interesting line as well: "In addition, do not use an “X-UA-Compatible” meta tag on the page or send a custom HTTP header from the web server." |
09:09 | <Hixie> | Peter`: luckily for the web, they've been losing market share fast enough that they haven't been able to really damage it |
09:09 | <aho> | huh? so even "edge" won't do the trick? |
09:10 | <Peter`> | Hixie: Yes, but there's several reasons why maintaining support for multiple rendering engines isn't ideal |
09:10 | <zcorpan> | aho: i guess it's just good advice (like there are other doctypes that trigger the latest mode too) |
09:10 | <Hixie> | Peter`: yeah there's a huge cost for them |
09:10 | <Hixie> | Peter`: i'm curious how many of these modes are in the mobile version of their browser |
09:10 | <Hixie> | (the one supposedly in ie8) |
09:10 | <Peter`> | Hixie: That'd be interesting to see, indeed |
09:11 | <aho> | http://gs.statcounter.com/#browser-ww-monthly-200807-201104 <- looks like a collision in about a year haha |
09:12 | <Hixie> | pity that data only goes back to '08 |
09:13 | <Hixie> | wow, IE is really low these days |
09:14 | <Hixie> | compared to its heyday |
09:15 | <aho> | http://gs.statcounter.com/#browser-ID-monthly-200807-201104 |
09:15 | <aho> | indonesia rocks <3 |
09:16 | <aho> | (internet is pretty expensive there... there aren't any casual users) |
09:17 | <hsivonen> | I'd have expected Opera to rank higher in Indonesia |
09:17 | <hsivonen> | does that graph exclude usage that is classified as "mobile"? |
09:17 | <aho> | yes |
09:17 | <hsivonen> | indeed Opera leads in Indonesia in the Mobile Browser graph |
09:17 | <aho> | well... i think... :> |
09:18 | <aho> | lol |
09:18 | <aho> | they got digg vs reddit stats |
09:20 | <gsnedders> | hsivonen: Worldwide, mobile browsers are 2.85% of the web. In Indonesia, 9.39%. |
09:20 | gsnedders | wonders how they count Opera Mini users in terms of their location |
09:21 | <hsivonen> | looks like in Europe, Chrome has recently been eating the market share of Firefox more than it has eaten the market share of IE, since the Firefox and IE lines are about to cross again |
09:22 | <hsivonen> | (while Opera and Safari are constant and Chrome is on an upwards slope) |
09:23 | <othermaciej> | depending on which stats you trust, in US share, Safari is close to passing Firefox |
09:23 | <othermaciej> | it's strange that browser shares are so different between different countries |
09:23 | <jgraham> | Safari? That sounds very [citation needed] |
09:24 | <hsivonen> | othermaciej: don't you have to miscount Chrome as Safari to get that result? |
09:24 | <jamesr> | sure you aren't counting chrome in those numbers (the UA string ends Chrome/12.0.712.0 Safari/534.27 on my build) |
09:24 | <jamesr> | ? |
09:24 | <gsnedders> | Russia is interesting… everything except Safari is losing share to Chrome. (Safari is constant.) |
09:24 | <othermaciej> | yes, http://marketshare.hitslink.com/browser-market-share.aspx?qprid=0 doesn't count Chrome as Safari |
09:24 | <othermaciej> | (those are the world stats) |
09:25 | <othermaciej> | I am not sure you can see per-country stats without an account |
09:25 | <hsivonen> | othermaciej: one can't |
09:26 | <aho> | i blame ff's decline on their delayed release of ff4. 3.x really started to look bad in comparison |
09:26 | <othermaciej> | I can post a screenshot of the US view (um, on imgur I guess?) |
09:26 | <aho> | ff4 still isn't pushed via notifications, is it? |
09:26 | <hsivonen> | aho: afaik, no |
09:26 | <othermaciej> | I paid for an account long ago and it never expired (even though the card it was on no longer exists) |
09:27 | <hsivonen> | I'm not sure if there's a policy, but I imagine the update push is waiting for 4.0.1 |
09:27 | <jamesr> | ffx4 should do quite well once they prompt ffx3.X users to update |
09:28 | <jamesr> | woah, according to the microsoft blog IE8 had "(full compliance with the CSS2.1 standard)" |
09:28 | <aho> | if the phase of the moon was just right, yes |
09:28 | <jamesr> | that's one of the most impressive claims they've made |
09:28 | <aho> | they also claimed that ie6 supports css 1.0 fully |
09:28 | <othermaciej> | http://i.imgur.com/Ix9T9.png |
09:28 | <aho> | well, it didn't :> |
09:28 | <othermaciej> | citation: ^ |
09:29 | <aho> | (background-attachment:fixed was missing... and well, there were of course lots of bugs, too) |
09:29 | <hsivonen> | jamesr: it's quite possible that IE8 passed some snapshot of the official CSS 2.1 test suite |
09:29 | <hsivonen> | othermaciej: wow. almost a percent still on Netscape |
09:29 | <aho> | lol |
09:30 | <othermaciej> | yeah, some Americans apparently have shitty computer setups |
09:30 | <hsivonen> | how are they counting? or, alternatively, what's wrong with the people using Netscape still? |
09:31 | <jamesr> | i wonder what the historical graph on those figures looks like |
09:31 | <othermaciej> | they count through statistical sampling of visits to selected site, then for world share numbers, weighting that by internet-using population per country |
09:31 | <hsivonen> | othermaciej: ooh. Bing as the search engine |
09:31 | <othermaciej> | sadly there doesn't seem to be a way to get a per-country tendline graph |
09:31 | <othermaciej> | and their custom queries are slow |
09:31 | <jgraham> | Hmm, that graph would be more consistent with other (less region-specific) stats with chrome and safari reversed |
09:32 | <othermaciej> | their worldwide stats seem vaguely in line with other people's worldwide stats |
09:32 | <othermaciej> | as do their europe stats |
09:33 | <othermaciej> | they do incorporate mobile browsing in the same stats |
09:33 | <othermaciej> | and it measures browser usage share, not market share (i.e. weighted by how much people browse, not by number of unique users) |
09:34 | <hsivonen> | in Germany, they really like to update Firefox before the prompted push: http://gs.statcounter.com/#browser_version-DE-daily-20110322-20110413 |
09:35 | <jgraham> | Germany seems to really like Firefox for some reason |
09:35 | <aho> | i like how even f-ing ff 3.0 got more than ie6 :> |
09:35 | <jamesr> | if you change that graph to USA then you can really strongly see workweek vs weekend effects: http://gs.statcounter.com/#browser_version-US-daily-20110322-20110413 |
09:36 | <aho> | (at the same time i'm also annoyed that ff 3.0 and ff 3.5 still exist) |
09:37 | <hsivonen> | aho: well, at least 3.0 isn't supported anymore |
09:37 | <hsivonen> | aho: there might be Camino still identifying as Firefox/3.0 |
09:37 | <aho> | browsers should auto-update. failing that they should self destruct :v |
09:38 | <hsivonen> | it's also possible for Linux distros to keep 3.0.x alive beyond what MoCo supports, but it seems even Debian stopped patching 3.0.x |
09:38 | <othermaciej> | their all-Europe share claims are: |
09:38 | <othermaciej> | IE - 42.17% |
09:39 | <othermaciej> | Firefox: 31.68% |
09:39 | <othermaciej> | Chrome: 13.4% |
09:39 | <othermaciej> | Safari: 8.10% |
09:39 | <othermaciej> | Opera: 3.6% |
09:41 | <othermaciej> | China is 80% IE |
09:41 | <othermaciej> | (I think it used to be closer to 90% a year ago) |
09:41 | <jamesr> | check out south korea |
09:41 | <jamesr> | started to move, but still 95%+ IE |
09:41 | <hsivonen> | othermaciej: if the stats are true, that might be explainable by new dual-engine browsers |
09:42 | <othermaciej> | Maxthon supposedly gets registered separately |
09:42 | <othermaciej> | India is near-even 3-way split among Firefox, IE and Chrome |
09:43 | <othermaciej> | Switzerland has the highest Safari share of any country I could find (16.2%) |
09:44 | <othermaciej> | Russia has 23% Opera |
09:46 | <zcorpan> | way to go Russia |
09:46 | <othermaciej> | wow, Indonesia is crazy, only 10% IE |
09:46 | <othermaciej> | and 65% Firefox |
09:47 | <hsivonen> | what's the story behind Opera's share in Ukraine? |
09:48 | <hsivonen> | IIRC, the story behind the share in Kazakhstan was the Turbo bypasses their censorship filter |
09:49 | <hsivonen> | s/the/that/ |
09:50 | <jgraham> | hsivonen: The story is that it has been high for a long time afaik |
09:51 | <jamesr> | my personal favorite: http://gs.statcounter.com/#browser-AL-monthly-200807-201104 |
09:51 | <gsnedders> | Yeah, AFAIK most of the Eastern European places with high marketshare have been high going back to the late 90s |
09:51 | <othermaciej> | Ukraine has even more Opera share than Russia it seems |
09:52 | <jgraham> | hsivonen: The origin presumably goes back to the time when Opera was pay-to-play or ad-supported |
09:53 | <hsivonen> | jgraham, gsnedders: ok. Did Opera have some specific language support advantage back then? |
09:53 | <othermaciej> | stat counter stats show some dubious looking artifacts |
09:53 | <othermaciej> | http://gs.statcounter.com/#browser-US-monthly-200807-201104 |
09:54 | <gsnedders> | hsivonen: Not AFAIK. But I can't claim to know much back then. I was just a little kid. |
09:54 | <othermaciej> | I disbelieve the giant IE spike / Firefox dip / Safari dip in early 2009 |
09:54 | <Ms2ger> | I disbelieve all those stats |
09:55 | <zcorpan> | lies! |
09:55 | <othermaciej> | three kinds of lies? |
09:55 | <aho> | things like that can be caused by changing the sampling size |
10:01 | <aho> | completely off-topic, but does anyone know if there is some list which shows some relationship between languages and character ranges? |
10:01 | <aho> | like... which languages can i cover with latin + latin supplement + latin extended A |
10:01 | <Lachy> | aho, http://www.unicode.org/charts/ |
10:02 | <Lachy> | I don't know if that has the detail you want though |
10:02 | <gsnedders> | Lachy: that just shows scripts to character ranges, not langauges |
10:02 | <gsnedders> | *languages |
10:02 | <gsnedders> | aho: I guess it's hard to classify… c.f. people who use "naïve" and "café" in English |
10:02 | <aho> | basically i want to know which character ranges i need to put into my texture fonts if i want to support some specific set of languages :> |
10:03 | <MikeSmith> | hsivonen: I think part of the story on Opera in Ukraine and elsewhere is that it is still runnable on really old hardware |
10:03 | <zcorpan> | aho: grep spellchecker dictionaries? |
10:03 | <MikeSmith> | 486 |
10:04 | <aho> | opera still works in win9x afaik :) |
10:04 | <gsnedders> | MikeSmith, hsivonen: and old OSes, too |
10:04 | <gsnedders> | aho: Yeah. |
10:04 | <gsnedders> | Not officially supported, but it still works |
10:04 | <MikeSmith> | gsnedders: right |
10:04 | <aho> | zcorpan, y'know what... that might actually do the trick |
10:04 | <hsivonen> | I thought Opera required Windows 2000 |
10:04 | <gsnedders> | hsivonen: "not officially supported". |
10:05 | <hsivonen> | so does WebM in Opera work on Windows 95? |
10:05 | <gsnedders> | Win95 doesn't work since 10.50, I think |
10:05 | <gsnedders> | Win98… dunno. |
10:05 | <aho> | a machine with win95 won't be fast enough ;) |
10:07 | <gsnedders> | hsivonen: But, well, being unsupported, crashing is perfectly acceptable behaviour. :P |
10:07 | <aho> | zcorpan, actually... i think i'll just create it straight from the translations. this way i'll automatically get everything i need and /only/ what i need |
10:08 | <jamesr> | aho: if you have the text then what you want is the set of glyphs in that text |
10:09 | <zcorpan> | aho: translations of what? |
10:09 | <aho> | i don't have any translations yet :) |
10:09 | <aho> | text messages in my game |
10:10 | <zcorpan> | ah |
10:10 | <zcorpan> | yeah there are tools to subset fonts |
10:10 | <zcorpan> | Philip` even wrote one |
10:10 | <aho> | i want to use texture fonts for that because they look better and because i cannot be arsed to implement all that text stuff in the flash emulation thingy :> |
10:11 | <aho> | http://i.imgur.com/BEmv2.png |
10:11 | <MikeSmith> | what are texture fonts? |
10:11 | <aho> | "soft" outlines and drop shadows for free :> |
10:12 | <aho> | MikeSmith, bitmap based font rendering |
10:12 | <aho> | there are one or more images which contain the glyphs and you then just draw what you need |
10:13 | <jamesr> | bitmap fonts AKA ugly-ass fonts |
10:13 | <aho> | <aho> http://i.imgur.com/BEmv2.png <- does that look ugly? |
10:13 | <jamesr> | yup |
10:13 | <aho> | looks much better than the native font rendering you get on windows |
10:15 | <aho> | http://i.imgur.com/oOXtd.png |
10:15 | <aho> | see? |
10:16 | <aho> | ClearType only looks good at smaller size if the font is properly hinted |
10:16 | <aho> | *sizes |
10:18 | <zcorpan> | only the 36px one looks good |
10:20 | <aho> | looks pretty jaggy to me :l |
10:21 | <MikeSmith> | I'm not sure that particular font would look good now matter how it's rendered… |
10:21 | <aho> | the sub pixel rendering on mac and linux looks a lot better at bigger sizes |
10:21 | <aho> | http://www.google.com/webfonts/family?family=Crafty+Girls&subset=latin |
10:22 | <MikeSmith> | "Crafty Girkl |
10:23 | <MikeSmith> | that font is kawaii |
10:24 | <zcorpan> | hybi changed the framing again |
10:26 | <zcorpan> | and they also started to mask their own emails |
10:26 | <jgraham> | They are better that way |
10:28 | <jamesr> | they make more sense that way |
10:28 | <zcorpan> | they forgot to do a handshake, so i'll refuse to read their messages |
10:29 | <jgraham> | I don't understand the IETF subprotocol anyway so I am dropping the connections |
10:32 | <zcorpan> | previously i thought that browsers would never fragment, but now that the long length is in plaintext many we should always fragment if length is >= 2^16 so that the long length encoding is never used |
10:33 | <zcorpan> | s/many/maybe/ |
10:34 | <jgraham> | For security reasons? |
10:35 | <zcorpan> | yeah, just in case. another benefit is pongs can be sent with low latency (although who cares about that) |
10:42 | <jgraham> | othermaciej: Admit it, the point of that email was to get the phrases "Chomsky hierarchy" and "infelicities" into the same message and thereby intimidate any future scrabble opponents |
10:43 | <othermaciej> | jgraham: I'm actually not all that good at Scrabble! |
10:43 | <othermaciej> | but I did enjoy the opportunity to be gratuitously pedantic |
10:51 | <hsivonen> | yeah, it's questionable not to consider content models part of syntax |
12:11 | <zcorpan> | anyone read 'Smashing HTML5'? |
12:12 | <hsivonen> | zcorpan: sounds violent to HTML5. |
12:13 | <hsivonen> | if it's an adjective instead, is "Smashing" better than "Native"? |
12:13 | <jgraham> | It is more indicative that mashed potato will be involved |
12:14 | <jgraham> | scare quotes implied |
12:14 | gsnedders | wonders if that's just a British thing or not |
12:14 | <jgraham> | I'm pretty sure it is |
12:14 | <gsnedders> | Wikipedia says it is. |
12:15 | <jgraham> | "The texture of Smash is not identical to that of real mashed potato, being somewhat smoother" |
12:16 | <jgraham> | Neither is the taste, although smoother is not the adjective one would use |
13:53 | <zcorpan> | how often is developers.whatwg.org synced with the spec? |
13:53 | zcorpan | noticed it still has <table summary> |
14:03 | <MikeSmith> | zcorpan: I think Ben syncs it manually |
14:03 | <MikeSmith> | but not sure |
14:24 | <GlitchMr> | "<input type="text"> needs a minlength="" attribute" |
14:24 | <GlitchMr> | I love reading FAQ |
14:24 | <GlitchMr> | <input type="text" pattern=".{3}"> |
14:55 | <zcorpan> | uh ok maybe that's enough tweeting for today |
14:55 | <benschwarz> | heyo |
14:55 | <benschwarz> | Just got home :) |
14:55 | <karlcow> | hmm still not interop for document.lastModified :( |
14:55 | <karlcow> | https://bugs.webkit.org/show_bug.cgi?id=4363#c7 |
14:56 | <benschwarz> | Hixie, zcorpan, Keep me in the loop on http://www.w3.org/Bugs/Public/show_bug.cgi?id=12491, I'll do whatever I can do to help |
14:57 | <zcorpan> | benschwarz: btw how often is developers.whatwg.org synced? |
14:57 | <hsivonen> | is there an easy way to find the cases in the spec where navigation occurs without replacement enabled? |
14:59 | <zcorpan> | hsivonen: load single page, search for 'navigate'? |
15:00 | <jgraham> | zcorpan: "no" would have been fewer characters |
15:02 | <hsivonen> | zcorpan: ok |
15:02 | <benschwarz> | zcorpan: I do it manually still… |
15:02 | <benschwarz> | at first it was very regular |
15:02 | <benschwarz> | but I processed it last week |
15:03 | <hsivonen> | I wonder if other browser have nicer code for implementing browsing contexts |
15:03 | <benschwarz> | zcorpan: Running it now ;0 |
15:12 | <zcorpan> | benschwarz: ah, i thought you had a cron job or something set up |
15:22 | <AryehGregor> | Browser developer people: who would be good people to ask (from all the major browsers) whether browsers would be willing to implement this requirement from CSS 3 Text? "The UA should place the start and end of the line inwards from the content edge of the decorating element so that, e.g. two underlined elements side-by-side do not appear to have a single underline. (This is important in Chinese, where underlining is a form of punctuation.)" |
15:22 | <AryehGregor> | I'm pretty sure this would break sites and browsers wouldn't be willing to do it, but I'd like to know, since I'm currently arguing about it on www-style. |
15:23 | <AryehGregor> | I'd like to e-mail someone from each of the major browsers asking, and CC www-style. |
15:24 | <AryehGregor> | I'm guessing bzbarsky is good for Mozilla, but no idea who to ask at WebKit or Opera (let alone Microsoft). |
15:24 | AryehGregor | pokes WebKit and Opera people: TabAtkins, dglazkov|away, jgraham, zcorpan |
15:25 | <wilhelm> | See /msg. (c: |
15:25 | <karlcow> | AryehGregor: how do you do with vertical text? |
15:25 | <AryehGregor> | wilhelm, since you only told me the address privately, does that imply that I shouldn't e-mail him CCd to a public list? |
15:26 | <AryehGregor> | karlcow, I dunno, that's a whole separate issue. |
15:33 | <zcorpan> | what, ie doesn't support name getters on forms? |
15:33 | <zcorpan> | oh it's just <img>? |
15:35 | <karlcow> | AryehGregor: yup, I was curious. your sentence popped up this issue. |
15:37 | <zcorpan> | Oprah supports File.slice? who knew |
15:49 | <kennyluck> | AryehGregor, I'm pretty sure that's not a bad idea too (re. holes in consecutive underlines). What I proposed was a new value in a property no browser has implemented yet http://lists.w3.org/Archives/Public/www-style/2010Dec/thread#msg102 |
15:49 | <kennyluck> | s/a bad/a good/ |
15:50 | <AryehGregor> | kennyluck, yeah, but fantasai and Koji don't seem to agree, so I need to get implementers to decide. |
16:32 | <AryehGregor> | Hixie, you know, my execCommand() spec is already around 100 KB of source code, and probably isn't even half done. How do you plan to review it and incorporate it into HTML5 when it's ready? |
16:36 | <Ms2ger> | Review? Who needs that? :) |
16:36 | <jgraham> | AryehGregor: s/How// |
16:36 | <AryehGregor> | Well, the plan is that he's going to be the one maintaining it while I'm off studying, so he'll have to understand it. |
16:37 | <AryehGregor> | jgraham, my contract says the execCommand() work is to be included in HTML5. |
16:38 | <jgraham> | AryehGregor: That sounds dangerous. W3C will presumably reject it from HTML5 |
16:38 | <AryehGregor> | More specifically, it says "the HTML spec". |
16:38 | <AryehGregor> | It can be HTML6, whatever. |
16:38 | <Ms2ger> | Does it say "spec"? |
16:38 | <AryehGregor> | "Have the HTML spec updated accordingly." |
16:38 | <AryehGregor> | The point is, I'm not going to be around to maintain it. |
16:39 | <AryehGregor> | So someone has to take it over, and the plan had been that it would be Hixie. |
16:39 | <AryehGregor> | Who's perennially swamped with work. |
16:39 | <jgraham> | Updated accordingly could be a reference to your spec in a different document |
16:39 | <AryehGregor> | In theory, but it still needs an editor, unless we want it to bitrot. |
16:51 | <jgraham> | Not really sure why it would bitrot unless implementations make lots of changes to their ExecCommand stuff |
16:51 | <AryehGregor> | It will need to be updated to reflect implementation feedback. |
16:52 | <AryehGregor> | In a spec this size, there are going to be plenty of issues that will only come up during or after implementation. |
16:53 | <jgraham> | Indeed, if you get to the stage where browsers are making changes based on the spec then active editing will be needed |
16:54 | <AryehGregor> | Would be kind of a waste if we don't get to that stage, won't it? |
16:55 | <jgraham> | Not if you come back, pick it up, and we get to that stage |
16:56 | <AryehGregor> | Possible. I don't really know how things will go. I won't typically be around, but there are a few breaks in the year of a couple weeks to a month where I might be able to do work. |
16:57 | <AryehGregor> | So maybe that would be enough to maintain the spec. |
16:57 | <AryehGregor> | I can't really guarantee anything. |
16:58 | <AryehGregor> | (I can't even guarantee that I'll be studying this fall, although I already signed up for it and paid a non-refundable fee to reserve a spot, because it's possible I'll wind up getting engaged to someone or other in the next few months, which will turn everything upside down. It's a perpetual hazard for young Orthodox Jews.) |
17:07 | <jgraham> | How very strange-sounding. Still, whatever works for you I guess. |
17:07 | <AryehGregor> | Which parts sound strange? |
17:08 | <jgraham> | "it's possible I'll wind up getting engaged to someone or other in the next few months" |
17:08 | <AryehGregor> | Yeah, I figured that part would sound strange. |
17:08 | <AryehGregor> | You silly non-Jews, waiting for years to get to know someone before getting engaged instead of proposing after commonly two months or less. |
17:09 | <AryehGregor> | Chassidim commonly propose on the second date or so, but in my circles it's usual to wait until at least seven or so. |
17:10 | <jgraham> | That at least indicates an element of control that was lacking in your original phrasing of the situation |
17:10 | <AryehGregor> | Well, I don't know when I'll meet someone I like, so that much I don't control. |
17:10 | <wilhelm> | Sounds like an … optimistic approach. |
17:11 | <AryehGregor> | Works well for us. |
17:11 | jgraham | finds the whole concept of marriage very strange so maybe isn't the right pwerson to comment here |
17:11 | <jcranmer> | the secretary problem! |
17:12 | <jcranmer> | reject the first N people, and then accept the first person you meet after them who is better |
17:12 | <jcranmer> | provably optimal! |
17:12 | <AryehGregor> | The conditions don't seem applicable. |
17:12 | jgraham | is disappointed to discover the secretary problem is not "people in high powered jobs often have affairs with their secretaries" |
17:13 | <AryehGregor> | The secretary problem assumes a small and fixed pool of people to choose from, and only gives you points if you pick the absolute best one. |
17:14 | <jgraham> | AryehGregor: Maybe you could use the theory if you combined it with a speed-dating approach to partner finding |
17:14 | <jcranmer> | http://en.wikipedia.org/wiki/Secretary_problem#Unknown_number_of_applicants |
17:14 | <AryehGregor> | Also, you can always go out with someone you rejected before. |
17:15 | <AryehGregor> | The cardinal payoff variant with an unknown number of applicants sounds like the best fit. |
17:15 | <jcranmer> | sqrt(N) is optimal if the number is known in the latter case |
17:16 | <AryehGregor> | The model that seems like a natural fit would be to assign each applicant some value between 0 and 1, and decrease the value of all applicants by some factor every time you reject someone. |
17:16 | <AryehGregor> | With an unlimited number of applicants. |
17:16 | <AryehGregor> | This reflects the fact that you'd prefer to find someone you like and marry at age 25 than to wait until 40 but find the perfect person. |
17:16 | <AryehGregor> | At least, I would. |
17:16 | <AryehGregor> | So you have to discount with time. |
17:17 | <AryehGregor> | Supposing the distributions are known, what's the optimal strategy then? |
17:17 | <AryehGregor> | Hmm, accounting for the cost of evaluation is important too. But my model naturally does that. |
17:17 | <AryehGregor> | Too bad I have no idea how to go about finding an optimal solution. |
17:18 | <AryehGregor> | I always wanted to study game theory. |
17:18 | <jgraham> | AryehGregor: I think optimising the problem description is a pretty big waste of time since it is so fundamentally flawed :) |
17:32 | <AryehGregor> | Hmm, this doesn't handle the case of inserting a doctype in the wrong place, does it? http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-node-insertbefore |
17:33 | <Ms2ger> | That's handles in the nodes model above |
17:33 | <Ms2ger> | -s+d |
17:33 | <Ms2ger> | (Actually, we haven't got around to it) |
17:34 | <AryehGregor> | There's no normative requirement that nodes model violations throw a HIERARCHY_REQUEST_ERR. |
17:34 | <AryehGregor> | In fact, such a requirement would be kind of scary, because it would inject exceptions into specs that look like there can't be any exceptions. |
17:35 | <Ms2ger> | Yeah, I know |
17:35 | <Ms2ger> | Patches accepted ;) |
17:35 | <AryehGregor> | Actually, what I'd like to see is some low-level "insert a node" algorithm that more or less acts like insertBefore() but is the single place that everything references when inserting nodes. |
17:36 | <AryehGregor> | Which specifies that mutation events are fired, things like that that need to be in one place. |
17:36 | <Ms2ger> | Would be nice, indeed |
17:36 | <AryehGregor> | If I finish all the execCommand() and DOM Range work before using up all my contract hours, maybe I can use the rest on DOM Core. |
17:36 | <AryehGregor> | (No idea how likely that is.) |
17:37 | <AryehGregor> | Actually, the problem with having the "insert a node" algorithm throw exceptions is that if an exception will be thrown, you often want to bail out in advance. |
17:37 | <AryehGregor> | Like I'm doing Range.insertNode() right now, and that will invoke splitText() in some cases, but you don't want to do that if you won't wind up inserting the node. |
17:38 | <AryehGregor> | So better to have one algorithm to do the insert, another to throw the exceptions. |
17:42 | <rafaelw> | Hello, all. |
17:42 | <rafaelw> | Is anyone at Opera present? |
17:42 | <wilhelm> | Usually. |
17:42 | <jgraham> | In mind or body? |
17:42 | <rafaelw> | At keyboard will suffice. |
17:42 | <rafaelw> | =-) |
17:43 | <rafaelw> | I work on the chromium team. |
17:44 | <rafaelw> | I've been working with Hixie's guidaince on developing an some ideas around a proposal for including templating/databinding functionality in html. |
17:45 | <rafaelw> | I'm hoping to find someone at Opera interested in this problem space. |
17:46 | <jgraham> | rafaelw: Have you tried posting your ideals to a mailing list somewhere public? |
17:46 | <jgraham> | *ideas |
17:47 | <hsivonen> | rafaelw: I'm not from Opera, but do you have a use case document in public? |
17:47 | <rafaelw> | jgraham: Yup, we're planning that. |
17:48 | <jgraham> | rafaelw: Basically if you post use cases and whatever design ideas you have to, say, whatwg then we will pay attention |
17:48 | <rafaelw> | We'd like to include microsoft on the discussion, so we're planning to go through public-webapps @ w3c |
17:48 | <jgraham> | Works for us, although there is probably lots of charter realted crap to get through |
17:49 | <jgraham> | Unless someone had the good sense to make the webapps charter "more or less anything involving technologies to be used in web pages that browsers are interested in implementing" |
17:49 | <jgraham> | or similar |
17:50 | <rafaelw> | Yeah, I'm aware of the dissatisfaction with the process overhead at w3c. |
17:50 | <jgraham> | Well I'm not saying that going through W3C is a bad idea |
17:50 | <jgraham> | There are definite upsides |
17:51 | <rafaelw> | Unfortunately, MSFT isn't able to work through w3c, and they're being very supportive of this problem space and I think they have alot of experience to bring to the discussion. |
17:51 | <rafaelw> | I'm hoping (maybe naively) that the consensus/process overhead won't be too bad. |
17:51 | <jgraham> | Anyway, like I said, we are more than happy to look at idea that come through the webapps list |
17:52 | <jgraham> | Yeah, maybe it will be fine |
17:52 | <rafaelw> | Ok. We've prototyped our ideas as a js shim and are working to get that to a sensible state and have docs that answer all of the obvious questions about it. |
17:53 | <rafaelw> | I've got to go through the google open source process to release that. I'm hoping to email public-webapps and reference the docs/prototype within a week or two. |
17:53 | <jgraham> | Actually it looks like the webapps charter is pretty vauge. So that's good |
17:53 | <bga_> | more and more ppl refuses to update browsers. internet becomes unsecure(pushState, fs access, system info, clipboard, ect), eat battery(webgl, css3), annoys(css3). ppl want old plain html :) |
17:53 | <jgraham> | Out of interest, does this involve markup additions? If so it might be a target for HTMLWg rather than webapps |
17:54 | <jgraham> | (yes I just engaged in the process wrangling I was previously lambasting) |
17:54 | <rafaelw> | Yes. |
17:55 | <rafaelw> | Jonas, Hixie and Maciej have all suggested public-webapps under roughly the idea that this work is largely related to XBL2. |
17:55 | <jgraham> | Fair enough |
17:56 | <jgraham> | It's pretty novel for a webapps spec to add markup (the new XBL draft notwithstanding) |
17:56 | <rafaelw> | Anyhow, I'm trying to be care about approaching this problem because "templating" and "databinding" are so overloaded with meaning and there are so many existing approaches. |
17:56 | <rafaelw> | s/care/cafeful |
17:57 | jgraham | -> afk for a bit |
18:07 | <AryehGregor> | This list of HIERARCHY_REQUEST_ERRs is ridiculous: http://aryeh.name/tmp/dom-range.html#dom-range-insertnode |
18:08 | <AryehGregor> | And it's not even comprehensive, because I don't have to worry about the insertion node being a PI or DocumentType. |
18:08 | <AryehGregor> | [110414 13:12:48] <AryehGregor> This list of HIERARCHY_REQUEST_ERRs is ridiculous: http://aryeh.name/tmp/dom-range.html#dom-range-insertnode |
18:08 | <AryehGregor> | [110414 13:13:07] <AryehGregor> And it's not even comprehensive, because I don't have to worry about the insertion node being a PI or DocumentType. |
18:08 | AryehGregor | is pretty sure this is not the right way to spec it |
18:09 | AryehGregor | leaves it for now, so he can write his tests more easily |
19:30 | <AryehGregor> | Okay, so now I got IE9 to create a node whose parent is null and whose previousSibling is not null. |
19:30 | <AryehGregor> | Someone there really needs to look into making their DOM implementation a bit more failsafe. |
19:32 | <AryehGregor> | http://software.hixie.ch/utilities/js/live-dom-viewer/saved/929 |
19:44 | <Ms2ger`> | s/DOM // |
19:45 | <AryehGregor> | I've mostly noticed DOM inconsistencies. |
19:46 | <AryehGregor> | Ms2ger`, could I convert DOM Range to use the preprocessor I wrote for the edit commands spec? It's unspeakably obnoxious to have to type all those tags again and again and again and again. http://aryeh.name/gitweb.cgi?p=editcommands;a=blob_plain;f=preprocess;hb=HEAD |
19:46 | <Ms2ger`> | I'd rather you didn't, to be honest |
19:46 | <AryehGregor> | Sigh. |
19:46 | <AryehGregor> | Don't you agree that the current syntax is horrifyingly bad to type, though? |
19:47 | <Ms2ger`> | I end up copy-pasting a lot :) |
19:47 | <AryehGregor> | Me too, but it's still awful. |
19:47 | <AryehGregor> | Other anolis specs aren't nearly as bad, because they don't have the cross-spec xrefs. |
19:48 | <AryehGregor> | Maybe I could just write it my way and then preprocess it before commit. |
19:50 | <Ms2ger`> | Heh, that works |
19:51 | <AryehGregor> | As long as I don't need to edit existing stuff. |
19:53 | <mpilgrim> | when in doubt, add a layer of abstraction |
19:54 | <AryehGregor> | Works for brevity. |
19:54 | <mpilgrim> | i don't see how this plan can possibly fail |
19:55 | <AryehGregor> | Nor me, since I've been using it for my own spec for a while now. |
20:14 | <jgraham> | mpilgrim: It appears that AryehGregor has +5 against sarcasm |
20:14 | <jgraham> | your weapons are useless here |
20:14 | <jgraham> | :) |
20:14 | <AryehGregor> | jgraham, in fact, I once shelled out the money to get "protection from sarcasm" cast on me with "permanency". |
20:15 | <AryehGregor> | The only thing I have to worry about is "dispel magic". |
20:15 | <AryehGregor> | But I have good Will saves. |
20:15 | <AryehGregor> | The Nerd class gets bad Fortitude saves, but good Reflex and Will. |
20:15 | <AryehGregor> | (good Reflex saves stemming, of course, from all the video games) |
21:20 | <Hixie> | AryehGregor: no specific plan yet, but my vague plan was to rip out the execCommand stuff in the spec right now and split your stuff amongst the HTML spec, the DOM Core spec, and the DOM Range spec as appropriate (might not be anything in the latter two, haven't checked) |
21:21 | <AryehGregor> | Hixie, k. Still a while yet till we have to think about it. |
21:21 | <Hixie> | jgraham: i imagine that the stuff rafaelw is working on, if it goes anywhere, would likely end up in HTML itself. but it didn't seem public-html would be a good place to discuss it. |
21:21 | <Hixie> | AryehGregor: k |
21:28 | <Lachy> | reading the logs, what exactly is that templating/databinding stuff that rafaelw is working on? Is it like an alternative to XBL2, or something that works with XBL2 or something completely different? |
21:45 | <jgraham> | Hixie: Can't say I disagree with that assessment |
21:46 | <Hixie> | Lachy: from what i understand, he's looking more at something like the repetition templates stuff (but done much better) than a widget system like XBL. |
22:19 | <erlehmann> | > I propose to address this issue by ensuring that all drawing operations are done in linear space. |
22:19 | <erlehmann> | first i was like LOL TROLLING but then … |
22:25 | <AryehGregor> | Is setting location.hash synchronous? |
22:25 | AryehGregor | suspects not |
22:27 | <AryehGregor> | Because it's really the same as setting location.href, right? |
22:27 | <zewt> | erlehmann: as opposed to Mr. Application Cache ...... |
22:28 | <erlehmann> | zewt, step 1: submit proposal. step 2: ??? step 3: GOTO 1 |
22:28 | <zewt> | "please stop busy looping the mailing list" |
22:43 | <Hixie> | othermaciej: yt? |
22:43 | <Hixie> | othermaciej: i'm looking for advice on how to handle this url decision |
22:43 | <Hixie> | othermaciej: the revert i'm supposed to do no longer applies, the spec has changed a lot since then, and i'm wondering what i should be aiming for |
22:44 | <Hixie> | othermaciej: is it just putting a definition for "parse" and "resolve" back into the spec, or something else? |
22:53 | <othermaciej> | Hixie: I think the crux of the decision is that the spec should directly define URI parsing (and relative resolution) |
22:53 | <Hixie> | the CP selected doesn't define URI parsing directly |
22:53 | <othermaciej> | Hixie: if you have to refactor the content to match the rest of the spec, I think that would be fine, particularly if Adam doesn't object (which I highly doubt he would) |
22:53 | <Hixie> | it defines it as a diff of the URL spec |
22:54 | <othermaciej> | ah |
22:54 | <othermaciej> | well, anyway, I think refactoring the content as part of the original landing would be fine |
22:54 | <Hixie> | k |
22:54 | <othermaciej> | fixing any bugs with the algorithms would also be fine, but preferably as separate changes |
22:55 | <Hixie> | yeah this is gonna be messy enough as it is without fixing bugs at the same time |
22:55 | <othermaciej> | I don't think Adam (or anyone else who cares about this) will be excessively picky |
22:55 | <Hixie> | oh i'm sure julian will be |
22:57 | <othermaciej> | did he express a preference in the poll? |
22:57 | <Hixie> | he's the reason this all happened in the first place, no? |
22:57 | <Hixie> | maybe i just assume it's him because it involved the ietf and not violating other specs |
22:58 | <othermaciej> | I honestly can't remember who started it |
22:58 | <othermaciej> | his opinion on the poll was to go back to the drawing board and have Roy Fielding write some text |
22:58 | <othermaciej> | thus, I expect him to hate anything you do regardless |
22:58 | <Hixie> | that's a given |
22:59 | <Hixie> | i'd be fine with roy writing the text, fwiw. i don't at all care who writes it so long as (a) it's written and (b) it's not fiction. |
23:00 | <Hixie> | ooh, my script congratulated me for fixing two outstanding XXX issue markers |
23:00 | <Hixie> | (the XXXs i had for defining "parse" and "resolve") |
23:14 | Hixie | brings the url feedback back into his bucket of active feedback |
23:15 | <Hixie> | (50 e-mails dating back up to 2009) |
23:15 | <Hixie> | abarth: what's the status of the url work? |
23:15 | <abarth> | Hixie: status is that I have a bunch of time next week blocked off to work on it |
23:16 | <Hixie> | ok well the html spec just got its old text back |
23:16 | <abarth> | i saw |
23:16 | <abarth> | sorry if this is creating busy work for you |
23:16 | <Hixie> | eh no worries |
23:16 | <abarth> | the good news is that stpete seems interested in actually solving this problem |
23:17 | <Hixie> | stpete? |
23:17 | <abarth> | http://stpeter.im/ |
23:17 | <AryehGregor> | Oh, Grid is a new proposal by Microsoft? Wasn't there something like it floating around for a long time? |
23:17 | <abarth> | APPS area AD |
23:17 | <Hixie> | oh peter |
23:18 | <Hixie> | k |
23:18 | <Hixie> | so this is gonna be done like the cookie thing? |
23:18 | <abarth> | hopefully |
23:19 | <abarth> | peter seems to understand that the HTML WG wants a spec by LC |
23:19 | <Hixie> | well that's ok, we'll be in LC for years |
23:20 | <abarth> | he wants a spec in six months |
23:20 | <abarth> | including discussion |
23:20 | <abarth> | so, that means we need one mostly written soon |
23:20 | <boogyman> | lol, good luck with that |
23:20 | <Hixie> | isn't this an area for which discussion is pretty much not needed? |
23:20 | <Hixie> | i mean, it's not like anything is being designed here |
23:20 | <Hixie> | it's just describing reality |
23:20 | <Hixie> | anyway |
23:21 | <Hixie> | if you want to do this at ietf, that's your prerogative |
23:21 | <abarth> | i don't particularly care where it gets done |
23:21 | <Hixie> | is this going to include the API you were talking about? or is that separate? |
23:21 | <Hixie> | i noticed File API has created a URL object |
23:21 | <abarth> | that's separate |
23:21 | <Hixie> | k |
23:22 | <abarth> | the main thing that needs to happen is for me or someone to spend time and actually write up the spec |
23:22 | <Hixie> | k |
23:22 | <abarth> | once we have that, then we can see who's interested in publishing it |
23:23 | <Hixie> | well, my plan is to basically see what happens, and if nothing happens when i get around to looking at the url feedback i just threw back on my pile, i'll just start going through that feedback and fix the stuff in the html spec |
23:23 | <Hixie> | we can always extract it out again later |
23:23 | <Hixie> | though it would be nice to have a spec that doesn't defer to the URI spec |
23:24 | <Hixie> | what would be even nicer is a spec that obsoletes the URI and IRI specs altogether, goes back to calling everything URLs, and defines syntax and parsing and resolving all in one place, including error handling. |
23:24 | <Hixie> | then i could just point straight to one document instead of having to juggle who's in charge of what |
23:24 | <abarth> | that's politically more difficult |
23:25 | <abarth> | my current plan is to have an object in the spec that can be parsed from a sequence of characters |
23:25 | <abarth> | and serialized to a URI |
23:25 | <abarth> | I think the current spec calls that a ParsedURL |
23:26 | <abarth> | but i haven't looked at the document for a while |
23:26 | <Hixie> | current spec? |
23:26 | <Hixie> | oh the one you are doing? |
23:26 | <Hixie> | k |
23:26 | <abarth> | https://github.com/abarth/url-spec/blob/master/drafts/url.xml |
23:26 | <abarth> | there's not much there now |
23:26 | <Hixie> | well so long as you define parse and resolve in terms that work for the spec, that's fine by me for now |
23:26 | <abarth> | but hopefully there will be more in a couple weeks |
23:26 | <Hixie> | (that work for the html spec, that is) |
23:27 | <abarth> | a bunch of IETF folks seem very excited about the IDNA aspects of this issue |
23:27 | <Hixie> | o_O |
23:27 | <abarth> | which seem uninteresting to me |
23:27 | <abarth> | i don't plan to include anything about IDNA |
23:28 | <Hixie> | there's gonna have to be something about idna, so you can parse iris |
23:28 | <Hixie> | but i don't see what there's to get excited about |
23:28 | <othermaciej> | abarth: when he says "by LC" does he mean "by the point of entering LC", or "by the point of leaving LC" (which most people might call "by CR") |
23:29 | <othermaciej> | the former is probably about a month away, and the latter more than a year away, by my sestimate |
23:29 | <abarth> | Hixie: i'm just going to say what the cookie spec says, which is "do the IDNA thing to make this ascii" |
23:29 | <abarth> | othermaciej: he seems to have about six months in mind at a timeframe |
23:29 | <abarth> | i don't know where he's getting that timeframe from |
23:30 | <abarth> | tlr has also been involved in these discussions, so maybe that part comes from him? |
23:30 | <Hixie> | abarth: yeah i think that's pretty much what the html spec says currently |
23:30 | <Hixie> | abarth: there's a little more to it, e.g. handling errors from ToAscii, but not much |
23:31 | <TabAtkins_> | AryehGregor: Yes, Grid Layout is basically a slightly more powerful version of Template Layout. |
23:31 | <TabAtkins_> | Lachy: Do you still need to know about the data-binding stuff? I had my computer off for a bit, so I missed if anyone talked to you in the interim. |
23:42 | <Lachy> | TabAtkins_, I'm just curious about what the proposal is and how it will work. But I can wait till the proposal gets sent to the mailing list |