Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Jonas Sicking
On Fri, Nov 18, 2011 at 6:25 PM, Tab Atkins Jr. wrote: > On Fri, Nov 18, 2011 at 4:29 PM, Jonas Sicking wrote: >> On Fri, Nov 18, 2011 at 3:54 PM, Tab Atkins Jr. wrote: >>> On Fri, Nov 18, 2011 at 3:44 PM, Jonas Sicking wrote: Personally it seems to me that moving the elements out of the D

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Tab Atkins Jr.
On Fri, Nov 18, 2011 at 4:29 PM, Jonas Sicking wrote: > On Fri, Nov 18, 2011 at 3:54 PM, Tab Atkins Jr. wrote: >> On Fri, Nov 18, 2011 at 3:44 PM, Jonas Sicking wrote: >>> Personally it seems to me that moving the elements out of the DOM such >>> that you can't find them using gEBI/querySelector

Re: [whatwg] @font-face rules in

2011-11-18 Thread Daniel Glazman
Le 18/11/11 23:40, Ian Hickson a écrit : I'm happy to add clarifying text or an example to the spec if that would help. [cc to www-style, reply-to to www-style ] Wow, wow, wow. Slowly please. I think you should discuss that in www-style before any addition to html. The complete mechanism for

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Jonas Sicking
On Fri, Nov 18, 2011 at 3:54 PM, Tab Atkins Jr. wrote: > On Fri, Nov 18, 2011 at 3:44 PM, Jonas Sicking wrote: >> Personally it seems to me that moving the elements out of the DOM such >> that you can't find them using gEBI/querySelector/firstChild is more >> surprising than useful. >> >> It woul

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Tab Atkins Jr.
On Fri, Nov 18, 2011 at 3:44 PM, Jonas Sicking wrote: > Personally it seems to me that moving the elements out of the DOM such > that you can't find them using gEBI/querySelector/firstChild is more > surprising than useful. > > It would basically reduce the feature to syntax sugar for setting > .i

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Jonas Sicking
On Fri, Nov 18, 2011 at 2:58 PM, Rafael Weinstein wrote: > On Fri, Nov 18, 2011 at 2:47 PM, Jonas Sicking wrote: >> On Fri, Nov 18, 2011 at 2:31 PM, Rafael Weinstein >> wrote: >>> On Fri, Nov 18, 2011 at 1:33 PM, Jonas Sicking wrote: On Thu, Nov 17, 2011 at 11:21 AM, Adam Barth wrote: >>

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Rafael Weinstein
On Fri, Nov 18, 2011 at 2:47 PM, Jonas Sicking wrote: > On Fri, Nov 18, 2011 at 2:31 PM, Rafael Weinstein > wrote: >> On Fri, Nov 18, 2011 at 1:33 PM, Jonas Sicking wrote: >>> On Thu, Nov 17, 2011 at 11:21 AM, Adam Barth wrote: Another option is to tokenize the elements as usual, but put

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Jonas Sicking
On Fri, Nov 18, 2011 at 2:31 PM, Rafael Weinstein wrote: > On Fri, Nov 18, 2011 at 1:33 PM, Jonas Sicking wrote: >> On Thu, Nov 17, 2011 at 11:21 AM, Adam Barth wrote: >>> Another option is to tokenize the elements as usual, but put them into >>> a new document created for the element (presumab

Re: [whatwg] @font-face rules in

2011-11-18 Thread Ian Hickson
On Fri, 18 Nov 2011, Roland Steiner wrote: > > When thinking about implementation details of @font-face rules in scoped>, I started to wonder whether a (nested) scoped style-sheet > should be able to create a new - or even override an existing - a > font-family declared in an outside scope. To

Re: [whatwg] Drag-and-drop folders/files support with directory structure using DirectoryEntry

2011-11-18 Thread Glenn Maynard
On Fri, Nov 18, 2011 at 1:36 AM, Kinuko Yasuda wrote: > I would say the approach has a bloating per-page bookkeeping problem but > not a 'leak'. It's a reference leak: an object which remains referenced after it's no longer needed. I'm not aware of anything standardized in the platform with th

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Rafael Weinstein
On Fri, Nov 18, 2011 at 1:33 PM, Jonas Sicking wrote: > On Thu, Nov 17, 2011 at 11:21 AM, Adam Barth wrote: >> Another option is to tokenize the elements as usual, but put them into >> a new document created for the element (presumably using >> the usual tree-building rules).  Because this docum

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Jonas Sicking
On Thu, Nov 17, 2011 at 11:21 AM, Adam Barth wrote: > Another option is to tokenize the elements as usual, but put them into > a new document created for the element (presumably using > the usual tree-building rules).  Because this document won't have a > browsing context, all the elements would

Re: [whatwg] Declarative Inert DOM (e.g. the element)

2011-11-18 Thread Jonas Sicking
On Thu, Nov 17, 2011 at 11:15 AM, Rafael Weinstein wrote: > Problem: > > Dynamic web pages often need to author and deliver fragments of DOM > which *may* be used at some point during the page's lifetime, but have > them be "inert" until they are needed. > > In this context, "inert" means not only

Re: [whatwg] I have feature requests for and tags.

2011-11-18 Thread Jonas Sicking
On Thu, Nov 17, 2011 at 12:46 PM, Glenn Maynard wrote: > On Thu, Nov 17, 2011 at 3:29 PM, Jonas Sicking wrote: >> >> Authors do however know how loud the volume of the media is though. If >> a video is encoded with a very loud volume, or a very quiet volume, it >> can be quite useful to be able t