[Bug 28522] New: [Shadow] Cascading for trees of no-inner/outer and no-younger/older relationship

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28522 Bug ID: 28522 Summary: [Shadow] Cascading for trees of no-inner/outer and no-younger/older relationship Product: WebAppsWG Version: unspecified Hardware: All

Re: [clipboard] Feature detect Clipboard API support?

(Aside: I was testing the queryCommandEnabled()/onbefore* idea with this script: https://gist.github.com/hallvors/59a90f2e3816cb57f044 ) On Tue, Apr 21, 2015 at 7:29 AM, James M. Greene wrote: > Patrick Kettner offered up another idea for this as well on a related > Modernizr issue [1]: > > Give

Web Storage Rec errata?

Hi, Is there a plan to publish an errata to sync the Web Storage Rec [1] with the latest? I counted 8 commits cherry picked into the Editor's Draft since Rec [2]. If no errata publication is planned, I'd expect the Rec to clearly indicate its status. Thanks, -Anssi [1] http://www.w3.org/TR/w

Re: XMLHttpRequest and timing of upload events

On Mon, Apr 20, 2015 at 2:00 PM, Hallvord Reiar Michaelsen Steen wrote: > On Tue, May 20, 2014 at 2:55 PM, Anne van Kesteren wrote: >> Because redirects are atomic, we cannot dispatch loadend events and >> such on the XMLHttpRequestUpload class. > > Does this change mean we can no longer send 'lo

Re: [admin] Registration for April 24 2015 Web Components f2f meeting; deadline April 10

On 2/24/15 3:37 PM, Arthur Barstow wrote: The registration page for the April 24 Web Components f2f meeting at Google's Mount View CA office is now open: The meeting/agenda page is:

Re: [clipboard] Feature detect Clipboard API support?

> > If we did that, authors could not use synthetic clipboard events for > anything - right? I'm assuming that authors are going to find use cases for > it - for example a "cloud clipboard" implementation may want to fire actual > paste events so that data from the "cloud" is processed like data fr

Re: JSON imports?

I just checked the html living standard, all it says about prefetch is > The prefetch keyword indicates that preemptively fetching and caching the > specified resource is likely to be beneficial This is pretty vague, and I sense the caching mechanism used by one vendor is not guaranteed to be

Proposal for changes to manage Shadow DOM content distribution

Hi all, Following WebApps discussion last year [1] and earlier this year [2] about template transclusions and inheritance in shadow DOM, Jan Miksovsky at Component Kitchen, Ted O'Connor and I (Ryosuke Niwa) at Apple had a meeting where we came up with changes to the way shadow DOM distributes n

Re: Proposal for changes to manage Shadow DOM content distribution

Hi Ryosuke, I want to start by thanking you, Ted, and Jan for taking the time to make this proposal. I read through the proposal, and had a quick question about how redistribution should work with this slot concept. I created a quick example that would take two date inputs (start date and end da

Re: Proposal for changes to manage Shadow DOM content distribution

On Tue, Apr 21, 2015 at 9:43 PM, Daniel Freedman wrote: > Hi Ryosuke, > > I want to start by thanking you, Ted, and Jan for taking the time to make > this proposal. > > I read through the proposal, and had a quick question about how > redistribution should work with this slot concept. > I created

Re: Proposal for changes to manage Shadow DOM content distribution

> On Apr 21, 2015, at 9:43 PM, Daniel Freedman wrote: > > Hi Ryosuke, > > I want to start by thanking you, Ted, and Jan for taking the time to make > this proposal. > > I read through the proposal, and had a quick question about how > redistribution should work with this slot concept. > I cr

Re: Proposal for changes to manage Shadow DOM content distribution

On Apr 21, 2015 8:22 PM, "Ryosuke Niwa" wrote: > > Hi all, > > Following WebApps discussion last year [1] and earlier this year [2] about template transclusions and inheritance in shadow DOM, Jan Miksovsky at Component Kitchen, Ted O'Connor and I (Ryosuke Niwa) at Apple had a meeting where we came

Re: Proposal for changes to manage Shadow DOM content distribution

I do want the ability to redirect distributed nodes into a holes in the base template, so that part is welcome to me. However, my first reaction to the slot idea is that forcing users to add the content-slot attribute on children significantly impairs the DOM API surface area of custom elements. F

Re: Proposal for changes to manage Shadow DOM content distribution

> On Apr 21, 2015, at 10:17 PM, Brian Kardell wrote: > On Apr 21, 2015 8:22 PM, "Ryosuke Niwa" > wrote: > > > > Hi all, > > > > Following WebApps discussion last year [1] and earlier this year [2] about > > template transclusions and inheritance in shadow DOM, Jan Miksov

Re: Proposal for changes to manage Shadow DOM content distribution

> On Apr 21, 2015, at 10:23 PM, Justin Fagnani wrote: > > I do want the ability to redirect distributed nodes into a holes in the base > template, so that part is welcome to me. However, my first reaction to the > slot idea is that forcing users to add the content-slot attribute on children >

Re: Proposal for changes to manage Shadow DOM content distribution

> On Apr 21, 2015, at 11:08 PM, Domenic Denicola wrote: > > From: Ryosuke Niwa [mailto:rn...@apple.com] > >> At the conceptual level, they're equivalent. However, we didn't find the >> extra flexibility of using CSS selectors compelling as we mentioned in our >> proposal [1]. > > is such