21:49:16 RRSAgent has joined #w3cdev 21:49:16 logging to http://www.w3.org/2009/11/05-w3cdev-irc 21:49:24 rrsagent, set logs public 21:50:18 TabAtkins has joined #w3cdev 21:50:35 caribou has joined #w3cdev 21:50:40 dom has joined #w3cdev 21:51:14 dbaron has joined #w3cdev 21:52:33 gerald has joined #w3cdev 21:53:10 smfr has joined #w3cdev 21:53:22 Tobias has joined #w3cdev 21:53:27 mib_igkf72 has joined #w3cdev 21:53:42 darobin has joined #w3cdev 21:54:02 AnnB has joined #w3cdev 21:54:12 is this mostly for scribing or can we also make fools of ourselves? 21:54:23 jun has joined #w3cdev 21:54:53 ScribeNick: timeless 21:54:55 darobin: Do we need to choose one? 21:54:55 Scribe: timeless 21:55:00 fantasai has joined #w3cdev 21:55:28 RRSAgent: make minutes 21:55:28 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html timeless 21:56:01 TabAtkins: well, so long as we don't talk about unicorns 21:56:21 soonho has joined #w3cdev 21:57:00 nathany has joined #w3cdev 21:57:38 nathany has joined #w3cdev 21:57:52 RRSAgent: make minutes 21:57:52 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html fantasai 21:57:59 Vagner-br has joined #w3cdev 21:59:14 nathany has joined #w3cdev 21:59:22 annevk has joined #w3cdev 21:59:59 Arron has joined #w3cdev 22:02:36 -> http://www.w3.org/2009/11/05-w3cdev-minutes.html 22:03:28 "it's 203" — as in "203 Non-Authoritative Information" ? :) 22:03:39 IanJ: Welcome everyone 22:03:43 ... My name is Ian Jacobs 22:03:51 ... welcome to the first developer meeting we've ever had 22:03:56 ... we have a great lineup 22:04:01 ... and i will get out of the web 22:04:05 s/web/way/ 22:04:15 ... your names are up here, so just get up on time 22:04:27 ... We have w3c groups and non w3c groups represented 22:04:35 ... timeless has accepted to scribe 22:04:48 ... the proceedings will all be public 22:04:58 Arun: My name's Arun for people who haven't met me personally 22:05:03 ... I work for Mozilla on Firefox 22:05:07 ... on evangelism 22:05:16 krisk has joined #w3cdev 22:05:16 maxf has joined #w3cdev 22:05:16 ... A lot of what we do is reach out to developers 22:05:21 ... to see what we should be doing 22:05:28 ... How many people are web developers? 22:05:34 ... that's the lion's share 22:05:44 ... How many people are in the business of developing web applications? 22:05:48 ... interesting a smaller number of hands 22:06:07 ... Both as part of my work at mozilla and as someone who works on standards 22:06:16 myakura has joined #w3cdev 22:06:24 ... I'm an author of a spec in W3C ... File API (?) 22:06:36 yes, File APIO 22:06:36 ... I also work on a spec outside W3C WebGL 22:06:37 er, API 22:06:46 ... We work in Web Apps WG 22:06:58 ... You should be able to access databases on a client just as you can on a server 22:07:11 ... Today you guys have come to the hallowed precincts of a sausage factory 22:07:19 ... you're actively following a list-serve 22:07:26 ... a lot of developers out there don't follow 22:07:36 ... to them, they may be happy to take an API and run with it 22:07:49 ... We'd like to get them more involved in standards 22:07:54 marie has joined #w3cdev 22:08:06 ... For examples, two browser vendors released browsers with a SQL API 22:08:20 ... but two vendors: Mozilla and Microsoft indicated they don't want to do this 22:08:33 ... We got feedback from developers indicating they didn't want a SQL API 22:08:42 ... ... In html5 and web apps 22:08:49 ... How many people recognize this movie? 22:08:56 [Back to the future Movie picture] 22:09:04 ["Where we're going, we don't need roads"] 22:09:23 ... I wanted to condense how standards work into one day 22:09:35 ... In fact, there's a story on CNet referring to a date in 2012 22:09:51 ... So I thought about last night how to condense this into a day 22:09:59 [Slide: Morning, Afternoon, Evening] 22:10:04 ... Basic rules of thumb on Time 22:10:10 ... Morning is the period that already passed 22:10:15 ... Morning is a little while ago 22:10:27 ... Features that are already available in browsers today 22:10:48 ... The afternoon is things you can build on right now, but you may not be able to do that in a cross platform manner 22:11:09 ... How many people do things for some platforms and worry about other browsers (esp IE6) 22:11:17 ... The evening is stuff that has yet to come 22:11:22 ... it holds in it the promise of a good night 22:11:31 ... it holds in it the promise of things that are still being fleshed out 22:11:41 ... it's a bit more than that, but it's not something that you can rely on in your bag of tricks 22:11:51 ... The morning includes things like LocalStorage 22:12:04 ... It's supported in IE8, Opera, Safari, Firefox 3.X (?) 22:12:11 ... As for XMLHttpRequest 22:12:12 AtticusLake has joined #w3cdev 22:12:23 ... it's implemented in most browsers (?) 22:12:33 .. and XDomainRequest (in IE8) 22:12:48 ... and they're implemented with the same security approach (?) 22:13:10 ... And you can grab me and we can look at snippets of code where I can show you how you can do this in a cross browser manner 22:13:20 ... postMessage is also available in IE8, Firefox, ... 22:13:24 benjick has joined #w3cdev 22:13:31 ... CSS2.1 support, reasonably good, even in IE 22:13:39 ... you can look to it for better support than before 22:13:41 IE8 22:13:50 s/in IE/in IE8/ 22:13:56 ... That's the morning 22:14:03 ... The afternoon gets a little bit more interesting 22:14:13 ... it introduces more things about the platform 22:14:20 ... things aren't as mature 22:14:32 ... supported in Firefox (25% of the market) 22:14:37 ... Safari, and Chrome 22:14:45 [Slide: Afternoon] 22:14:49 ... HTML5 Canvas 22:14:52 ... HTML5 Video 22:14:57 ... HTML5 Drag and Drop 22:15:00 Is this slide online somewhere? 22:15:02 .... CSS WebFonts (...) 22:15:11 ... and geolocation 22:15:18 [ Demo ] 22:15:29 ... This demo brings together a lot of pieces of the platform 22:15:36 ... it sorta does, but the color isn't so great 22:15:43 ... I've got a colleague of mine 22:15:46 Kangchan has joined #w3cdev 22:15:57 ... doing a fanning gesture between two iPhones 22:16:04 mauro has joined #w3cdev 22:16:06 azunix has joined #w3cdev 22:16:13 ... if I click here, I've got a video supplanted between the two iPhones 22:16:32 Hi Developepers! 22:16:34 ... this only works if video is part of the browser, I can't do this with Flash 22:16:40 s/pep/p/ 22:16:49 demo dynamically injecting content into a canvas (within a video element) 22:16:58 ... I can also embed a video inside the animation 22:17:06 ... This works when video is a first class citizen of the web 22:17:10 ... and this comes from html5 22:17:12 Arun: You get this flexibility when video is a first-class citizen of hte web 22:17:14 ... here's another demo 22:17:34 JonathanJ has joined #w3cdev 22:17:44 rrsagent, draft minutes 22:17:44 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html JonathanJ 22:17:49 ... The color isn't great 22:17:51 ... [about the demo] 22:18:00 ... the pixels of the video are dumped into a canvas 22:18:10 ... i'm going to label extracted bits 22:18:19 sof has joined #w3cdev 22:18:20 [names which people might not recognize] 22:18:39 tantek has joined #w3cdev 22:18:53 [ fwiw, this usually works better, but for some reason one of the pins on the cable seems to be doing strange things ] 22:19:49 [arun uses the demo to establish facial recognition] 22:20:12 ... this demo uses localStorage 22:20:17 ... because i switch between two urls 22:20:24 http://people.mozilla.com/~prouget/demos/facedetector/new/play.xhtml 22:20:49 ... I have a lot of demos, please come visit me later 22:21:03 dsr has joined #w3cdev 22:21:03 ... this is in the context of "the afternoon" 22:21:10 ... I wanted to show you this demo 22:21:19 [IanJ: t-minus 10 minutes] 22:21:24 [very impressive demon for video] 22:21:29 ... I'm going to open font book, a handy dandy application on my mac 22:21:37 s/demon/demo/ 22:21:44 ... what i'm going to do now 22:21:51 ... is show a bunch of technologies working together 22:21:55 ... HTML5 Drag and Drop 22:22:00 ... CSS Font Face 22:22:04 ... HTML localStorage 22:22:12 ... X (?) 22:22:20 ... I'm going to drag a font onto the page 22:22:26 ... and dropped it onto the page 22:22:38 ... and the page restyled itself using the font 22:22:46 [drags a font onto the page] 22:23:02 [arun misses the drop target] 22:23:02 http://labs.thecssninja.com/font_dragr/ 22:23:14 ... I'm going to drop in garamond 22:23:23 ... now you can see the page has taken on a different look 22:23:28 ... this is directly using localStorage 22:23:33 ... to store the stuff that I dragged 22:23:44 ... it's using the drag and drop api 22:23:54 ... and it's using font-face to set the font 22:24:04 ... and it's using contentEditable 22:24:11 s/X (?)/contentEditable/ 22:24:20 ... if i got to a page flickr.com/maps 22:24:26 ... I can share my location 22:24:39 [ Arun shares our location ] 22:24:52 ... this is the GeoLocation API introduced in Firefox 3.5 22:25:10 .... and I can drag my mouse over locations and see pictures from there 22:25:21 ... this is flikr using pieces of an API that recently became a spec 22:25:26 r12a-nb has joined #w3cdev 22:25:28 ... and now... "Evening" 22:25:37 ... We're looking at pushing the hardware 22:25:43 brutzman has joined #w3cdev 22:25:45 ... we're discussing storage 22:25:52 ... and orientation events (angles) 22:25:58 ... multitouch 22:26:14 [Arun holds up an n900 proto] 22:26:22 ... Firefox Mobile will ship for this device 22:26:34 [Arun demos playing a game by tilting his macbook pro] 22:26:47 ... this is a pretty popular go-kart game 22:27:12 [ demos an expanding red panda but tilting his laptop] 22:27:19 ... this is stuff we'd like to do in the evening 22:27:24 ... pending discussion with other folks 22:27:36 ... this is stuff in the evening, the promise of a tomorrow, or a tomorrow morning 22:27:49 ... and of course there's 3d graphics 22:27:52 ... 3d graphics are extensions of the html5 canvas element 22:28:00 ... and exposes a new way to do hardware accelerated 3d graphics 22:28:13 Kangchan has joined #w3cdev 22:28:13 ... these are the things i'm talking about from the promise of an evening 22:28:26 Van Ryper (Krillion): 22:28:40 ... I've heard a lot about the web3d consortium 22:28:49 Arun: the deliverable of web3d (x3d) 22:28:58 ... is an interchange format that represents 3d graphics 22:29:06 ... it's the ability for javascript to parse such graphics 22:29:15 ... and use webGL to expose those graphics 22:29:21 Robin: and someone's done that 22:29:27 Arun: X3D OM 22:29:42 ... The promise of today is that javascript's performance have improved so much 22:29:58 IanJ: so... Don Bredsman a chance to speak 22:30:11 DonB: We'll be showing this tomorrow morning at X-oclock 22:30:25 9-oclock 22:30:32 s/Bredsman/Brutzman 22:30:34 X3DOM: http://www.x3dom.org/ 22:30:37 Tom Strobers (user): 22:30:44 ... Java - JavaScript ? 22:30:52 ...in the HTML5 WG Meeting 22:30:52 Arun: that's an interesting question 22:31:01 ... and i'll speak in a continum 22:31:11 ... java has historically been used as a technology that can be used anywhere 22:31:16 ... and so in fact can javascript 22:31:22 ... javascript as it now runs in browsers 22:31:38 ... and browsers run on mobile devices 22:31:46 sof has left #w3cdev 22:31:51 Fantasai: JavaScript and Java has no relation 22:31:58 ... JavaScript runs natively in the browser 22:32:11 ... whereas java runs separetly 22:32:28 s/separetly/separately/ 22:32:38 Arun: JavaScript is the defacto language of the web 22:32:53 IanJ: I'll see if we can talk about moving things into programming languages and out of declarative languages 22:32:57 ... I want to keep things moving 22:33:06 ... we have a lot of interesting speakers 22:33:10 ... we have 3 bottles of wine 22:33:26 ... You can use a business card, or just a piece of paper 22:33:34 ... thank you Arun 22:33:41 ... fantasai come up 22:33:53 fantasai: I'm an invited expert of the CSS WG 22:34:05 ... I've brought along a number of people from the CSS WG with exciting demos 22:34:24 ... first speaker is David Baron 22:34:37 ... he writes specs, makes interesting comments, ... 22:34:40 [ laughter ] 22:34:55 dbaron: ... 22:35:08 ... there've been a lot of demos of css stuff floating around lately 22:35:20 ... i've wanted to demo a few features that are not the ones that get the most press 22:35:29 ... the stuff that people demo are these new visual effects 22:35:39 ... shadows, columns, rounded corners, transforms 22:35:43 ... one of them is border image 22:35:55 ... the ability to take an image and then logically that image gets split up into 9 pieces 22:36:07 ... and then you can use those slices to form the border of something else 22:36:14 [demo] 22:36:24 ... and this will now resize as i resize the window 22:36:31 ... another feature that's been in specs for almost 10 years 22:36:38 ... but that hasn't been implemented until recently 22:36:41 ... is font-size-adjust 22:36:50 ... it lets you get better font behavior 22:37:00 AtticusLake has left #w3cdev 22:37:03 ... one of the problems is that font size is whatever the font designer wants it to mean 22:37:08 rrsagent, make minutes 22:37:08 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html IanJ 22:37:10 ... what font-size-adjust lets you do 22:37:25 ... is that instead of letting font size do what it does 22:37:51 ... font-size-adjust lets you operate on the x height 22:38:01 [ demo of font-size-adjust ] 22:38:12 ... another feature that's now pretty widely implemented 22:38:16 ... Mozilla, WebKit, and Opera 22:38:20 ... are CSS Media Queries 22:38:29 ... which let you change the style of the web page 22:38:37 ... based on characteristics of the thing that's displaying it to you 22:38:51 ... so you can change the page based on, e.g. the width of the window 22:39:11 ... e.g. you can specify something that only operates for windows >22em's wide 22:39:22 ... the final thing, is a feature that I think is only implemented in Mozilla 22:39:43 ... many designers have struggled with css using intrinsic widths in basic ways 22:39:52 ... there's the longest word of the line 22:39:57 ... and (??) 22:40:07 ... so you can say the width is the min-content-width 22:40:13 ... or the width is the mac-content-width 22:40:19 ... or that it fits the container 22:40:24 ... which is the same algorithm used for tables 22:40:34 fantasai: we'll have a couple of questions after each talk 22:40:40 dbaron: questions now... 22:40:47 VanR: 22:40:54 ... how pervasive are things 22:41:11 dbaron: most of these that i've demo'd are supported in Firefox, Opera and Safari, but not IE 22:41:24 quirksmode.com suggested 22:41:26 VanR: ... meta question, is there a way to see supported list 22:41:33 Tab Atkins: 22:41:42 ... quirksmode ... and ... 22:41:47 mauro has left #w3cdev 22:41:50 cappert has joined #w3cdev 22:41:52 unknown-speaker: 22:41:58 s/speaker/questioner/ 22:42:03 ... status of a test suite? 22:42:04 s/unknown-speaker/Ian: 22:42:13 fantasai: we're working on it 22:42:19 ... next speaker is Tab Atkins 22:42:22 TabA: 22:42:33 ... i just got brought in based on my work on the gradient spec for CSS3 22:42:44 s/unknown-questioner/Ian/ 22:42:46 ... I'm going to take this opportunity to go over how spec work is done 22:43:04 ... because page designers often wonder how to get things added 22:43:06 ... steps: 22:43:16 ... look at the problem and figure out what the actual problem is 22:43:17 my slides were at http://dbaron.org/talks/2009-11-05-w3c-css/slide-1.xhtml 22:43:29 ... and then there's a mailing list 22:43:35 ... it's a public list 22:43:43 ... I have an example 22:43:43 thanks dbaron 22:43:45 ... gradients 22:43:57 ... Safari introduced experimental support for css gradients in 2008 22:44:04 ... I don't know if these will work in Chrome 22:44:12 ... that's ok... I have other things that will work 22:44:27 ... We kick things around on the mailing list 22:44:35 ... later Mozilla created something similar 22:44:38 TabAtkins was showing: http://webkit.org/blog/175/introducing-css-gradients/ 22:44:45 ... they said that they didn't like the way it was done 22:44:58 IE have had CSS gradients for ever! 22:44:59 ... each vendor uses its own prefix (-webkit-, -moz-) 22:45:01 now showing: https://developer.mozilla.org/en/CSS/-moz-linear-gradient 22:45:07 ... not the bad old browser wars 22:45:28 ... gradients can be done in CSS, performantly 22:45:36 ... without the network bandwidth 22:45:46 ... the problem with gradients, was the syntax 22:45:52 ... we kicked it around on the mailinglist 22:46:00 ... it's all public, you can read it on the mailinglist 22:46:07 ... what it ended up with was a proposal by me 22:46:14 www-style archive : http://lists.w3.org/Archives/Public/www-style/ 22:46:14 ... i just proposed it on the list 22:46:22 ... it grew out of discussions with people 22:46:30 Current proposal: http://dev.w3.org/csswg/css3-images/#gradients- 22:46:30 ... talking about what people were trying to do 22:46:41 [shows the detailed description of the proposal ?] 22:46:50 ... these are based on the firefox implementation 22:46:55 ... this is a Minefield build of Firefox 22:46:58 ... it's now in the nightlies 22:47:07 dbaron: it will be in Firefox 3.6 22:47:12 ... as of a few hours ago 22:47:23 TabA: so 3.6 will have the new syntax 22:47:31 ... so you can do things like you want to do 22:47:49 [ demos creating _beautiful_ gradients ] 22:47:55 ... this is directly using the syntax 22:48:03 TabAtkins is testing with http://www.xanthir.com/etc/gradient.html 22:48:05 ... i'm just using js to set the background 22:48:23 Robin: ... do you have demos? 22:48:30 TabA: it's an open problem 22:48:37 ... it shows the evolution of an idea 22:48:41 s/do you have demos/do you have demos where it's animated/ 22:48:42 ... from someone identifying a problem 22:48:45 ... to implementations 22:48:56 ... to implementations(?) on the style list 22:49:10 ... to proposals(?) 22:49:32 ... so if you have a problem 22:49:36 ... you tell us about i 22:49:40 s/i/it/ 22:49:50 ... we kick it around 22:49:54 mcf has joined #w3cdev 22:49:56 ... or we decide to put it off until later 22:50:02 ... browser developers are not always page authors 22:50:14 fantasai: coming to a browser near you 22:50:18 ... next up, Simon Fraser 22:50:26 ... giving a demo of transforms and transitions 22:50:36 ... these are new drafts that are coming up 22:50:48 ... Simon works for Apple on WebKit, and used to work for Mozilla 22:50:55 Simon= smfr 22:51:00 smfr: so... 22:51:05 darobin, I failed! 22:51:07 ... with transitions and transforms 22:51:23 ... this is some content that we put together using assets from a band called willco (?) 22:51:32 ... as I hover over things on the left 22:51:40 ... you see transitions 22:51:47 [ shows the basic bits ] 22:51:56 ... we've got a standard color 22:52:05 ... and the nice red color? 22:52:10 ... using completion in textmate 22:52:17 ... let's put a transition right here 22:52:22 ... over one second 22:52:29 ... so now when i go back to the page 22:52:40 ... you can see the transition 22:52:52 ... transitions take a comma separated list 22:53:12 ... another thing that dbaron mentioned was transforms 22:53:19 ... so let's put a hover on the transform 22:53:30 ... a precanned rotate of say X degrees 22:53:39 ... and now let's make this nice and smooth 22:53:45 ... so let's say ... .5 22:53:48 s/5/5s/ 22:53:56 ... you can use milliseconds too 22:54:05 ... so let's go back to our original page 22:54:08 ... but this slideshow 22:54:18 ... you can have crossfades 22:54:24 ... we can use a translate 22:54:29 ... and vertical scales 22:54:37 ... that's a keyframe animation 22:54:42 ... it's a little bit more complex 22:54:51 ... they're not as advanced as transitions 22:54:56 ... we can do a spin 22:55:04 ... we're also proposing a 3d transform 22:55:18 ... we're rotating around the vertical axis with some perspective 22:55:29 IanJ: so are all the images there? 22:55:42 smfr: yes, it's all there, it's just css classes tweaking 22:55:52 Dan (HP): 22:56:03 ... we've got all these transforms that we can use on a page 22:56:06 ... we've also got canvas 22:56:12 ... why should you use one or the other 22:56:27 smfr: with canvas, you draw and then don't know what's there 22:56:41 AtticusLake has joined #w3cdev 22:56:42 ... with transforms, you aren't making the content more opaque 22:56:45 ... you still have links 22:56:56 ... we've also got examples of applying 3d to slices of a page 22:57:07 ... and revealing things from the page 22:57:22 ... and we can hover over here and see hit testing still works 22:57:36 AtticusLake has left #w3cdev 22:57:49 ... all done with css transforms 22:57:53 ... we've done this inside apple 22:58:00 ... this demo was done by charles ying (?) 22:58:03 ... outside apple 22:58:12 ... it uses flikr to fetch images as a wall 22:58:21 ... hold keys down, move backwards and forwards 22:58:43 [ wiring glitch, we dimmed another room ] 22:58:52 ... thanks 22:58:56 fantasai: so that's our three speakers 22:59:01 ... we also have people from Microsoft here 22:59:10 ... we've got a bunch of members from the CSS WG 22:59:18 Bernard Ling (?): 22:59:26 ... when does it appear in ie6? [just kidding] 22:59:41 dbaron: Mozilla has 2d transforms in FF3.5 22:59:49 ... transitions will be in FF3.7 23:00:03 smfr: 2d transforms should be identical in behavior 23:00:19 dbaron: 3d would be after 3.7 23:00:28 if we did it 23:00:29 IanJ: how to tell css wg your idea's 23:00:35 fantasai: www-style@w3.org 23:00:37 ademoissac has joined #w3cdev 23:00:52 xx-? : 23:01:04 ... is there any work being done on opacity across browsers 23:01:13 ms-1: 23:01:16 http://lists.w3.org/Archives/Public/www-style/ 23:01:21 ... currently it's available through filters 23:01:31 ... it's a proprietary property 23:01:39 ... we can sit down and i can try to help you with it 23:01:43 ... moving forward in the future 23:01:50 ... we can see about looking to expand 23:02:04 fantasai: css3 color is a CR 23:02:09 ... there's an opacity property 23:02:18 ... I believe WebKit, Gecko and Opera 23:02:27 IanJ: ok... 23:02:38 RRSAgent: make minutes 23:02:38 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html timeless 23:03:13 Thanks everyone, your talks were amazing! :) 23:03:23 very impressive, indeed 23:03:35 Next Speaker: Philippe Le Hégaret (W3C) 23:03:46 IanJ: Philippe has worked on building a test suite 23:03:56 Philippe: let's talk about something embarassing 23:03:58 ... testing at w3c 23:04:08 ... i'm responsible for [long list of wg's] 23:04:15 AtticusLake has joined #w3cdev 23:04:19 ... one of my plans is how do we test all that 23:04:28 ... talking about testing at w3c 23:04:30 AtticusLake has left #w3cdev 23:04:34 smfr has joined #w3cdev 23:04:39 ... we already have plenty of test suites at w3c 23:04:51 ... css1, ... dom event 2, css2.1, ... 23:05:04 ... why do we have those test suites? 23:05:07 s/dom/DOM/ 23:05:15 ... one of those reasons is that in 1999 in the DOM working group 23:05:30 ... we came up with this phase called Candidate Recommendation (CR) 23:05:44 ... "we think we're done", but now we want to prove that we're actually done 23:05:50 ... this came out of the DOM WG 23:06:02 ... to come out of the phase 23:06:14 ... the WG _should_ come out with two implementations of each feature 23:06:20 http://www.w3.org/QA/TheMatrix we need to brush up the matrix 23:06:26 ... it's a negotiation with the [TBL role] 23:06:49 ... what working groups tend to do 23:07:00 ... is just demonstrate that each feature has been implemented 23:07:07 ... do they actually do this? 23:07:13 ... no, they don't have enough resources 23:07:20 ... and no one really wants to write tests 23:07:29 ... but do we get interoperability on the web? 23:07:34 ... and i would argue no 23:07:37 karl, I actually updated it (somewhat) a few weeks ago 23:07:48 ... how can we make the web a better place? 23:07:51 ... w3c has limited resources 23:07:53 ... yes we have microsoft 23:07:58 ... but we have limited amount of time 23:08:07 ... limited amount of budget, for product teams as well 23:08:08 plinss has joined #w3cdev 23:08:14 ... so what we really want is the community to help us 23:08:18 ... tell us what works 23:08:22 ... you run into problems all the time 23:08:25 ... tell us about it 23:08:31 ... can you please submit a test about it? 23:08:41 ... what i'd like to see is the community help us 23:08:46 ... let's make it a bit harder 23:09:06 [ slide: svg, mathml, video, ...] 23:09:44 ... I can manipulate the DOM tree 23:09:46 dom, excellent 23:09:54 s/dom, excellent// 23:10:14 ... if i want to play a video, i just click a button which is just a thing with css style on it 23:10:19 ... and it will work 23:10:24 ... but who is going to test all this? 23:10:44 ... while we have produced some test suites 23:11:00 ... we haven't produced combinations of specs 23:11:04 ... css+svg+ ... 23:11:11 ... so how do we test that? 23:11:19 ... first we need to test the parsers 23:11:47 ... we need to guarantee that the document you're righting will generate one single DOM 23:11:52 s/righting/writing/ 23:12:04 ... how do we test dynamic scripting 23:12:09 ... if i want to test a css animation 23:12:17 ... how do i test it if it's 3 seconds 23:12:26 ... i don't want to test just the first frame and the last frame 23:12:35 ... we need to understand that there are limitations 23:12:42 ... it's impossible to test everything 23:12:48 ... and we have to acknowledge that 23:12:53 ... but at the same time 23:12:58 ... we need to do something 23:13:02 ... the most common thing 23:13:09 ... is a test that requires a human 23:13:20 ... a "self describing test" 23:13:31 ... [ pass with green, fail with red ] 23:13:38 ... we can also test plain text output 23:13:42 ... we can compare screen shots 23:13:48 ... if you have for example in svg 23:13:54 ... we know exactly what the output should be 23:14:03 ... if you have a rectangle, we know what it should be 23:14:12 ... we can take a screen capture 23:14:14 mcf has joined #w3cdev 23:14:18 ... with fonts, it's different 23:14:22 ... what dbaron did 23:14:31 ... is that instead of trying to write tests 23:14:43 ... is how about we write two pages that should have the same rendering 23:14:48 ... using different features 23:14:52 ... that's called reftests 23:15:06 ... the advantage is that it can be cross platform/browser 23:15:10 s/write tests/ write tests to match a static image/ 23:15:17 ... with webkit, you can 23:15:29 ScribeNick: fantasai 23:15:30 ... do a dump of a dom tree 23:15:41 rrsagent, make minutes 23:15:41 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html IanJ 23:15:43 ... and there are probably other ways that I'm not aware of. 23:15:44 -> http://trac.webkit.org/wiki/Writing%20Layout%20Tests%20for%20DumpRenderTree Webkit DumpRenderTree, an example of layout tree comparison 23:15:54 ... one of the things I've been tryin got push inside the consortium is to have a browser testing framework 23:16:08 ... that other groups can use. They can choose a method to test their specification. 23:16:14 ... we want to make this as automatic as possible. 23:16:18 ... we need to produce a lot of tests. 23:16:32 ... e.g. Microsoft submitted 7000 tests that were all self-describing tests 23:16:36 ... that is not scalable 23:16:43 ... it takes a long time to go through those tests 23:16:46 cappert has joined #w3cdev 23:17:00 ... because of our limited resources, we need to produce a mechanism to help our working groups 23:17:12 ... if they are reviewing tests, they are not writing specs 23:17:20 ... they should just be able to focus on controversial tests 23:17:33 ... if others can submit a test, then we can look if there's a problem 23:17:43 ... we can also see if its a bug in the browser, and they have to change their impl 23:17:59 ... We also have to be careful here, because if the tests are wrong we get interop on the wrong behavior! 23:18:26 ... We need to have testing for all these technologys, not just one of them, or each separately 23:18:30 ... but all of them togethers 23:18:44 ... with HTML5 normatively integrating with SVG and MathML, we need to test them together, not just each on the side. 23:18:47 midnaz has joined #w3cdev 23:18:51 ... We need to be able to test HTML inside SVG 23:19:00 and SVG inside HTML inside SVG 23:19:01 ... As I said there are multiple ways to test a browser, and we should allow more than one 23:19:19 ... The browser implementors are not going to rewrite all their tests for us 23:19:35 ... but agree on some common formats so that we can all share tests 23:19:51 ... We also need to have a life after the Recommendation stage 23:20:02 ... the specs still exist after Rec, and we need to continue testing them 23:20:13 ... I don't want W3C to run that test suite. We don't have the resources. 23:20:24 ... We can't buy 100 servers and run tests on every possible version of everybrowser 23:20:37 s/everybrowser/every browser/ 23:20:38 LeslieB has joined #w3cdev 23:20:41 ... So we want to allow others to run the tests. To run screen shots on their own computer 23:20:57 ... THere are some difficulties. E.g. I don't know how to take a screen shot by script on all the platforms 23:21:01 s/THere/There/ 23:21:05 ... What happens then? 23:21:11 ... We can make the test results useful to you. 23:21:24 ... Show reports of what works, and what doesnt. Let's make the test suites useful for the community as well. 23:21:32 s/doesnt/doesn't/ 23:21:33 ... And we should improve our validators at W3C. 23:21:43 ... Maybe make it use test results. 23:21:58 ... e.g. it notices You are using this feature, note that it doesn't work on FF3.6! 23:22:13 ... We're not a lone, there are others who are trying to do the same thing. 23:22:21 s/a lone/alone/ 23:22:39 ... test swarm for example is an effort from jQuery author, because he was running into the same problem 23:22:54 ... he cannot run every OS /browser combination himself 23:23:12 ... browserscope is interesting too. It allows you to compare screenshots across platforms 23:23:36 ... It uses a web server locally to determine when to take the screen shot 23:23:49 ... We need to produce these tools incrementally 23:23:58 ... and try to get them to work on all borwsers 23:24:07 s/borwsers/browsers/ 23:24:10 ... I think the message that I like you to get out of this is that we need help. 23:24:29 ... I can get some help from browser vendors, but ultimately we need help from the community because you are the ones suffer every day. 23:24:41 ... and until you tell us what is wrong, we are not able to help you 23:24:43 s/suffer/suffering/ 23:24:44 For the record, Help W3C Validators program at http://www.w3.org/QA/Tools/Donate 23:24:55 Ian: Questions for Philippe? 23:24:55 interesting article on mobile testing: http://www.quirksmode.org/blog/archives/2009/09/testing_mobile_2.html 23:25:04 Liam has joined #w3cdev 23:25:04 Dianna Adair: 23:25:22 RRSAgent: make minutes 23:25:22 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html timeless 23:25:22 Dianna Adair: Could there be any hooks in the syntax so that you can pass arguments to the syntax automaticall, through some sort of test generation program 23:25:31 Dianna Adair: Are there valid simulators for the major browsers? 23:25:43 s/automaticall/automatically/ 23:25:51 Dianna: So that you can push the tests agains the simulated suite of browsers 23:25:58 s/agains/against/ 23:26:11 plh: FOr the first question, yes, because we are starting from scratch 23:26:19 s/FOr/For/ 23:26:21 plh: For the other we can get screenshots of the major browsers 23:26:26 henriquev has joined #w3cdev 23:26:41 plh: browsertest.org was done by an engineer in Switzerland 23:26:54 timbl has joined #w3cdev 23:26:56 rrsagent, make minutes 23:26:56 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html IanJ 23:26:59 plh: At the beginning of Sept. a few folks including me and a few Moz developers got together and started writing code to do that 23:27:04 -> http://www.browsertests.org/ BrowserTests.org 23:27:15 plh: We made a prototype that works on the 3 major platforms 23:27:23 plh: He is improving his browser test framework 23:27:34 plh: At W3C we have a way to do human testing, I showed a demo of the mobile web browser 23:27:40 plh: It requires a human to click pass fail pass fail 23:27:49 s/browsertest.org/browsertests.org/ 23:27:54 Dianna: One way I've seen that works, is to set up a location and have some sort of "bugfest" 23:28:22 Dianna: You have people all over the world trying to test things simultaneously 23:28:24 plh: ... 23:28:36 plh: My goal is not to point fingers at browsers and tell them they're doing bad stuff 23:28:39 plh: I want to serve the community 23:28:56 IanJ: Have you set up a mailing list or public place for people to come help out? 23:28:59 plh: Not yet 23:29:05 IanJ: ACTION Phillipe? :) 23:29:13 plh: We need to create a group within W3C itself 23:29:24 plh: I know for example Mozilla and Microsoft are interested in helping 23:29:37 plh: We need to organize and provide a venue for the community to come together 23:29:53 Dianna: I propose that Universities are a great source intelligence and creativity and might be able to help 23:30:06 Chris (MSFT): There is a test suite alias in the HTMLWG 23:30:26 plh: Yes, we also want cross-tech testing 23:30:37 Kevin Marks: Do you know the test suite for .. ? 23:30:42 s/Chris/Kris 23:30:56 plh: I only mentioned testing framework. There are plenty of efforts out there 23:31:01 s/.. ?/called doctype at Google/ 23:31:05 plh: One thing I did in August was to collect some of that 23:31:15 plh: We are not alone, there are a lot of others trying to solve the same problem 23:31:25 IanJ: Ok, we have 4 more speakers after the break 23:31:32 IanJ: I'll hand over to Tim for now 23:31:46 TimBL: Thanks for coming 23:31:56 there was http://lists.w3.org/Archives/Public/www-html-testsuite/ 23:32:02 Tim: It's importat that everyone designing specs is in contact with lots and lots of people using their specs 23:32:10 and now http://lists.w3.org/Archives/Public/public-html-testsuite/ 23:32:13 Tim: Good to have feedback, and feedback on how to get feedback. 23:32:33 rrsagent, make minutes 23:32:33 I have made the request to generate http://www.w3.org/2009/11/05-w3cdev-minutes.html IanJ 23:42:00 LeslieB has joined #w3cdev 23:43:49 ademoissac has joined #w3cdev 23:47:36 RRSagent, this meeting spans midnight 23:52:49 nathany has joined #w3cdev 23:56:26 LeslieB has joined #w3cdev 00:02:45 smfr has joined #w3cdev 00:03:59 Arron has joined #w3cdev 00:04:08 ScribeNick: timeless 00:04:11 Scribe: timeless 00:04:16 marie has joined #w3cdev 00:04:17 IanJ: Next speaker, Brendan Eich, representing ECMA 00:04:27 ... and ECMA harmony 00:04:37 brendan: I'm here from Mozilla 00:04:46 ... I'm here to talk about ECMA Harmony 00:04:57 ... which is a ... which we reached last summer 00:05:06 ... before that, we had problems 00:05:14 ... the figure of XX ... 00:05:31 ... identified as gandalf ... 00:06:00 ... there were people like Doug and sometimes me 00:06:05 ... advocating for JS Hobbits 00:06:13 ... small enough and based on principals from Scheme itself 00:06:14 darobin has joined #w3cdev 00:06:26 ... it had virtues which were only discovered years later on the web 00:06:28 pjsg has joined #w3cdev 00:06:33 ... it was the dumb kid brother to Java 00:06:43 ... JavaScript was supposed to be the duct tape language 00:06:57 ... you were supposed to write it around the real language .. Java 00:07:07 ... I think people will agree that Java is basically dead on the client 00:07:13 ... there were problems with Java 00:07:23 ... the main issues was that JavaScript was a dynamic language 00:07:49 ... is a dynamic language, and will continue to be a dynamic language 00:07:51 ... the fear with ECMAScript 4 (?) 00:07:56 ... was that it would become a static language 00:08:04 ... the fear, as with Visual Basic 7 00:08:13 ... was that you take a dynamic language 00:08:19 ... and you convert it into a large proof system 00:08:26 mib_bmpvrc has joined #w3cdev 00:08:30 ... and that's not how languages are built 00:08:47 ... if ES4 would have been that, i'd be that guy with Gandalf 00:08:57 ... there was a point in 2006 where the committee seemed united 00:09:11 ... the MS representative was going to put some old version into JScript.net 00:09:16 ... and we were all united 00:09:26 [ Slide: The Fellowship of JS ] 00:09:36 ... the fellowship was broken 00:09:41 [ Slide: Conflict (2007) ] 00:09:53 ... some of it was based on the real prospect that i was somehow working toward 00:10:06 ... of pulling the drive language of flash, actionscript, into the web 00:10:22 ... and again, microsoft was working on pulling a version into JScript.net 00:10:34 ... based on waldemar horwat 00:10:41 ... ECMA requires consensus 00:10:45 ... and we didn't have that 00:10:49 ... at the time this happened in march 00:11:01 tantek has joined #w3cdev 00:11:04 ... it was clear to me that this wasn't going to work, someone was going to win, and someone was going to lose 00:11:10 ... but this was going to be ok 00:11:27 ... because it would involve improvements to the language for the web (?) 00:11:40 ... ecma was stagnating 00:11:48 ... 4th edition was mothballed in 2003 00:12:12 ... netscape was dying - partially because of its own failings, and partly because of microsoft (see antitrust) 00:12:18 ... msie was sleeping 00:12:40 ... in 200x (?) ... there was a chance of things improving 00:12:46 ... in April 2007, there were things like 00:12:55 ... Microsoft's Silverlight offering 00:13:17 ... a JScript Chess demo was converted into C# 00:13:22 ... it was 100s of times faster 00:13:36 [ Slide: The Two Towers ] 00:13:39 * ES4 00:13:57 * Waldemar Horwat's work at Netscape, 1999-2003 00:14:03 * JScript.NET, 2000 00:14:12 * ActionScript 3, 2005-2006 00:14:14 ---- 00:14:19 * ES3.1 00:14:23 * Dougt's recommendations 00:14:34 s/Dougt/Doug/ 00:14:43 * Document JScript deviations 00:14:49 brendan: ... 00:15:01 ... there were a lot of bugs in IE's implementation of JavaScript 00:15:17 ... and MS was heavily involved in the standard writing for ECMAscript 2/3 00:15:27 ... and there were serious bugs in the MS implementation 00:15:41 * "No new syntax" 00:15:48 brendan: ... 00:16:07 ... if you never add things, you can't break things 00:16:15 KevinMarks has joined #w3cdev 00:16:25 ... if you aren't careful, and you add global objects/methods 00:16:28 ... you can break the web 00:16:30 ... (facebook) 00:16:42 ... no new syntax doesn't save you 00:16:50 ... time was passing, we were trying to get es4 out 00:16:58 [ Slide: Synthesis (2008) ] 00:17:02 brendan: .... 00:17:10 dbaron has joined #w3cdev 00:17:18 ... Allen proposed meta object API 00:17:25 ... on the ES3.1 side 00:17:47 ... Lars Hansen on the ES4 side, "Packages must go" 00:17:51 ... in April 2008 00:17:53 ... Namespaces must go too (June-July) 00:17:58 ... unfortunately, we lost Adobe 00:18:20 ... because they felt they lost the bits they had derived from the standard 00:18:28 ... but that's a risk when working on standards 00:18:36 ... when we reached harmony in July in Oslo 00:18:41 jun has joined #w3cdev 00:18:49 ... the language again is inspired by Scheme with influences from Self 00:18:56 ... one of the foundations of Scheme is lexical scope 00:19:04 ... javascript has some broken bits of scope 00:19:18 ... Doug's teaching and attitude 00:19:30 ... in es4 we're looking toward a strict mode 00:19:42 ... we have a hope for "use strict mode" for es5 00:19:50 ... similar to perl5 00:20:04 ... we're trying to avoid "use stricter" for future versions 00:20:13 ... that's my quick recap of how we reached harmony 00:20:22 .... ES3.1 was renamed ES5 (March 2009) 00:20:36 ... We decided not to trouble ECMA with fractional standard version numbering 00:20:39 ... ES4 died 00:20:59 ... we're not sure if Harmony will really be 5 00:21:09 ... we might need to do some quick versions for standardization reasons 00:21:17 ... the committee is not the gatekeeper 00:21:25 ... a chokepoint for all innovation 00:21:38 [ Slide: Namespaces ] 00:21:43 brendan: ... 00:21:52 ... who here knows about Namespaces in Flash? 00:21:57 [ hands raised ] 00:22:07 ... there's ECMAScript For XML (e4x) 00:22:15 ... it has a lot of problems as a spec IMO 00:22:28 ... it's a spec whose pseudo code was extracted from java code 00:22:43 ... so you have bugs from the code, translation, etc. 00:22:52 ... it almost broke the object model 00:22:58 ... it had integrated query 00:23:05 ... it had namespace objects 00:23:25 ... you had to use ::'s to qualify stuff 00:23:37 ... sometimes people complain about namespaces in XML documents 00:23:48 ... es4 was much worse 00:24:00 ... it was very powerful 00:24:20 ... because you could use lexical scope to change how code behaves 00:24:24 [ Slide: Packages ] 00:24:30 ... packages are built on namespaces 00:24:42 ... even today in actionscript, there are some funny things about them 00:24:58 ... there's a temptation to think that using long chains of dotted things 00:25:17 ... there's a temptation to think that the dotted things can win 00:25:25 ... but because the language is dynamic 00:25:43 ... the winner can be the normal object with similar property paths 00:25:53 ... I think this problem still exists in actionscript 00:26:01 ... and then there are problems with