Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

Thank you. I appreciate that. Then, let me migrate all open bugs of 'Component Model'. I think that include also HTML Imports bugs in addition to Custom Elements bugs. When I finish, I'll announce that. On Tue, Jun 30, 2015 at 11:21 PM Xiaoqian Wu wrote: > Hi Hayato, > > public-webapps has been

Re: PSA: publishing new WD of Service Workers on June 25

http://slightlyoff.github.io/ServiceWorker/publish/service_worker/WD-service-workers-20150625/ > Invoke Run Service Worker algorithm with serviceWorker as the arguement > [sic]. > Fetch invokes Handle Fetch with request. As a result of performing Handle > Fetch, the Service Woker [sic] retur

Re: [shadow-dom] ::before/after on shadow hosts

Yeah, ::before and ::after should be added as the children of the shadow host in the composed tree, as a *pseudo* first child and a *pseudo* last child. On Wed, Jul 1, 2015 at 1:15 PM Elliott Sprehn wrote: > On Wed, Jul 1, 2015 at 12:08 AM, Hayato Ito wrote: > >> > ::before and ::after are basi

Re: [shadow-dom] ::before/after on shadow hosts

On Wed, Jul 1, 2015 at 12:08 AM, Hayato Ito wrote: > > ::before and ::after are basically *siblings* of the shadow host, > > That's not a correct sentence. ::before and ::after shouldn't be a > siblings of the shadow host. > I just wanted to say that #2 is the desired behavior. > > Indeed they're

Re: [shadow-dom] ::before/after on shadow hosts

> ::before and ::after are basically *siblings* of the shadow host, That's not a correct sentence. ::before and ::after shouldn't be a siblings of the shadow host. I just wanted to say that #2 is the desired behavior. On Wed, Jul 1, 2015 at 1:01 PM Hayato Ito wrote: > The spec [1] also says: >

Re: [shadow-dom] ::before/after on shadow hosts

The spec [1] also says: > ::before > Represents a styleable child pseudo-element immediately before the originating element’s actual content. > ::after > Represents a styleable child pseudo-element immediately before the originating element’s actual content. It sounds to me that ::before and ::af

Re: [shadow-dom] ::before/after on shadow hosts

#2 for sure On Tue, Jun 30, 2015, 4:52 PM Tab Atkins Jr. wrote: > I was recently pointed to this StackOverflow thread > < > http://stackoverflow.com/questions/31094454/does-the-shadow-dom-replace-before-and-after/ > > > which asks what happens to ::before and ::after on shadow hosts, as > it's n

Re: [shadow-dom] ::before/after on shadow hosts

On 07/01/2015 02:48 AM, Tab Atkins Jr. wrote: I was recently pointed to this StackOverflow thread which asks what happens to ::before and ::after on shadow hosts, as it's not clear from the specs. I had t

[shadow-dom] ::before/after on shadow hosts

I was recently pointed to this StackOverflow thread which asks what happens to ::before and ::after on shadow hosts, as it's not clear from the specs. I had to admit that I hadn't thought of this corner-cas

Re: Async Image -> ImageData conversion

If it's difficult to make ImageBitmap both an efficient drawing source and a conversion intermediary, then we could add conversion functions to each object that can be converted, e.g.: HTMLImageElement.toBlob() HTMLImageElement.toImageData() Blob.toImageData() ImageData.toBlob() This seems incons

Re: [admin] Moving Custom Elements bugs to Github [Was: Re: Custom Elements bugs will be also migrated]

Hi Hayato, public-webapps has been removed from the default CC list of ‘Component Model’. Please let us know when you finish migrating and we will recover this component ASAP. Thanks. — xiaoqian > On 29 Jun, 2015, at 10:42 pm, Arthur Barstow wrote: > > Yves, Xiaoqian, Mike - would one of y

Components F2F

Can someone update https://www.w3.org/wiki/Webapps/WebComponentsJuly2015Meeting with a bit more information? I hear it might be in Mountain View? Will we have sufficient time to cover both Custom Elements and Shadow DOM? And could the drafts maybe be updated to cover what has been agreed to so far