20:36:10 RRSAgent has joined #webapps 20:36:10 logging to http://www.w3.org/2011/11/02-webapps-irc 20:36:19 scribe: weinig 20:36:27 RRSAgent, draft minutes 20:36:27 I have made the request to generate http://www.w3.org/2011/11/02-webapps-minutes.html anne 20:36:41 RRSAgent, make minutes public 20:36:41 I'm logging. I don't understand 'make minutes public', anne. Try /msg RRSAgent help 20:36:51 RRSAgent, make public 20:36:51 I'm logging. I don't understand 'make public', anne. Try /msg RRSAgent help 20:36:55 dg: We are starting with an overview and demo 20:37:04 dg: [looks for dongle] 20:37:10 darobin has joined #webapps 20:37:53 fjh has joined #webapps 20:37:57 RRSAgent, make logs public 20:38:15 RRSAgent, also, fuck you 20:38:15 I'm logging. I don't understand 'also, fuck you', anne. Try /msg RRSAgent help 20:38:33 morrita1 has joined #webapps 20:39:23 ar: We are working on an imperative model that allows subclassing HTML Elements 20:39:35 ar: We are working on a declarative form, but it is not ready 20:39:41 ar: [gives a demo] 20:40:20 ar: In the demo we are creating an idiomatic JavaScript class that subclasses from HTMLElement 20:40:27 shepazu has joined #webapps 20:40:28 rniwa has joined #webapps 20:40:40 ar: the class is registered as an extension, must start with x- 20:41:08 ar: this plugs into the parser to add your own element types 20:41:26 travis: would you subclass from Node 20:41:39 stakagi has joined #webapps 20:42:05 ar: that wouldn't make much sense, you really need to subclass HTMLElement 20:42:13 richt has joined #webapps 20:42:19 yehuda: can you subclass HTMLInputElement 20:42:39 ar: that would be hard, since we would have to define the shadow DOM for form controls for all browsers 20:42:48 Meeting: Component Model session 20:43:01 ar: it might make sense to only inherit from HTMLElement 20:43:04 RRSAgent, make minutes 20:43:04 I have made the request to generate http://www.w3.org/2011/11/02-webapps-minutes.html Ms2ger 20:43:09 yehuda: what about span? 20:43:11 abarsto has joined #webapps 20:43:18 ar: span is just like HTMLElement 20:43:32 ar: another aspect is the Shadow DOM, from XBL 20:43:47 ar: any element should be allowed to have a shadow DOM 20:44:12 travis: CSS has generated content, how is this different 20:44:27 i/We are starting with an overview and demo/Topic: Overview 20:44:29 RRSAgent, make minutes 20:44:29 I have made the request to generate http://www.w3.org/2011/11/02-webapps-minutes.html Ms2ger 20:44:45 ar: generated content has certain restrictions, just before and after for instance 20:45:22 yehuda: can shadow DOM listen for new events 20:45:36 myakura has joined #webapps 20:45:52 ar: [notes that events will work] 20:46:35 evanli has joined #webapps 20:46:38 ar: using the shadow dom, you could use canvas as the rendering, while still having the DOM 20:46:45 paul_irish has joined #webapps 20:46:54 ar: shadow DOM is conceptually different, and can be specified seperately 20:47:36 ar: [notes in demo that subclassed element has multiple parts, though only one real child in the DOM] 20:48:19 kensaku has joined #webapps 20:48:21 ar: many complicated components suffer from "div soup" today, and shadow dom helps this 20:48:37 ar: shadow DOM is created using ShadowRoot constructor 20:49:27 ar: shadow DOM API allows you to set a content element 20:50:12 dg: content element gives you an insertion point 20:50:40 dg: it also doesn't effect the DOM, only the layout 20:50:54 dc: a good example is
20:51:04 dc: with 20:51:20 dc: [draws disclosure triangle UI] 20:51:56 mixedpuppy has joined #webapps 20:52:07 dc: details would have a shadow DOM with an image for the disclosure triangle 20:52:36 dc: will be forwarded to content elements in the shadow dom 20:53:10 dc: content elements get chosen in document order 20:53:23 ar: this is all about creating HTML element subclassing 20:54:05 cyril_ has joined #webapps 20:54:16 ar: [shows using subclassing of HTML Elements using ecmascript 6 syntax] 20:54:31 js: Why is ShadowRoot a new node type? 20:54:32 holstege_lt has joined #webapps 20:54:40 js: Why not use element 20:54:50 ar: we consider it like a document fragment 20:55:10 ar: unlike HTCs, this is not a new document 20:55:39 js: adding a new node seems like a big deal 20:55:49 js: XBL just uses a template element 20:56:03 si-wei has joined #webapps 20:56:15 ar: I would be ok with that, since shadow root combines both creating the root and attaching it 20:56:30 dg: we originally just wanted to use document fragment 20:56:38 dg: the shadow root never renders 20:57:00 dg: dominic thinks we should only render the shadow root 20:57:08 mjs has joined #webapps 20:57:08 dg: then do css magic 20:58:05 dc: we want innerHTML to work, so we don't use document fragment 20:59:18 dc: if shadow root are elements, we would probably want to not replace the children, but rather the element it is the shadow of 20:59:19 mixedpuppy has joined #webapps 21:00:30 holstege_lt has left #webapps 21:00:36 rs: one question is how does styling the host element effect shadow content 21:01:19 ar: we think that starting with subclassing just HTML elements is a good start 21:01:36 wilhelm has joined #webapps 21:01:36 JonathanJ1 has joined #webapps 21:01:53 ar: form serialization is something we should allow through a protocol that any element can implement 21:01:58 Hixie: is web controls still up? 21:02:22 http://www.whatwg.org/specs/web-controls/current-work/ 21:02:25 ar: the component model is helping us flesh out what problems remain in the web platform 21:02:50 kensaku has joined #webapps 21:03:02 nothing much there 21:03:17 tlr has joined #webapps 21:03:20 ar: yes, you could describe implementations using this, but we don't want that right away 21:03:58 ar: one thing we should discuss is what is needed from the declarative model 21:04:14 sriramyadavalli has joined #webapps 21:04:17 macrus: I was part of the team that made HTC 21:04:38 marcus: we took the opposite approach, with the declarative model first 21:05:02 marcus: what are the hurdles 21:05:14 ar: we are thinking about and element 21:05:57 yehuda: I found the declarative part of XTC the most confusing 21:06:10 yehuda: may have been documentation 21:06:25 yehada: may have been my background as a web developer 21:07:01 ar: [types on the screen] 21:08:30 ar: what happens when we are loading the webcomponent and the unknown elements are parsed 21:08:57 ar: one problem is that doing it after the fact is that people may have references to the unknown elements already 21:09:24 ar: we would have a "becomes" event 21:09:47 someone: why not sync 21:09:57 everyone: sync is bad, no one likes sync 21:10:41 anne: another options is to make it like html manifest 21:11:35 anne: that solves the source order (unknown element before ) but not loading issue 21:11:57 js: changing elements in place seems bad 21:12:03 ar: we are not doing that 21:13:01 ar: the "becomes" events will create a new element, and the old one gets yanked out the tree 21:14:06 [lots of yelling] 21:14:54 shepazu has joined #webapps 21:15:04 rniwa_ has joined #webapps 21:15:22 anne: the new element will actually be created before the event 21:15:53 js: it doesn't matter if the element is in the document 21:15:59 js: we can fire events on all elements 21:16:08 rniwa_ has joined #webapps 21:16:43 ar: [is showing stuff on a projector] 21:17:59 Rossen has joined #webapps 21:18:23 Scribe: heycam 21:18:41 ar: [explains how the proposed declarative syntax maps to js] 21:19:10 ar: we use