Hello,
this is a preliminary announcement.
There will be a meeting hosted in the Bay Area of California (i.e. between
San Francisco and San Jose, roughly speaking), focusing on Custom Elements.
A meeting registration page will be available soon, and will be announced.
We will try to provide
Wouldn't it likely need to be called just before layout? All the issues
Dimitri highlighted are symptoms of layout running before distribution.
On Fri, May 15, 2015 at 3:46 PM, Olli Pettay o...@pettay.fi wrote:
On 05/15/2015 05:37 PM, Wilson Page wrote:
Would it be possible to leave the
On 05/15/2015 06:39 PM, Wilson Page wrote:
Wouldn't it likely need to be called just before layout?
Probably yes, but it is not defined when that actually happens.
All the issues Dimitri highlighted are symptoms of layout running before
distribution.
On Fri, May 15, 2015 at 3:46 PM, Olli
Polymer really wants Shadow DOM natively, and we think the `slot` proposal
can work, so maybe let's avoid blocking on design of an imperative API
(which we still should make in the long run).
As our entire stack is built on Web Components, the Polymer team is highly
motivated to assist browser
On Fri, May 15, 2015 at 5:45 PM, Scott Miles sjmi...@google.com wrote:
How does it work for redistribution
We've done some investigation and think it can work.
Note that distributions work just fine with slots. The only thing that
doesn't is partial redistributions, and we haven't been able
How does it work for redistribution
We've done some investigation and think it can work.
and the other downsides that have been brought up?
We have to tackle these deliberately, but mostly we think there is room for
consensus.
You're okay with the required to plaster content-slot='foo' all
On 05/15/2015 05:37 PM, Wilson Page wrote:
Would it be possible to leave the calling of the shadowRoot's distribute()
function to the engine? This way the engine can be in full control over
*when* distribution happens.
We would need to define when the engine calls it, otherwise web pages
Would it be possible to leave the calling of the shadowRoot's distribute()
function to the engine? This way the engine can be in full control over
*when* distribution happens.
On Wed, May 13, 2015 at 5:46 PM, Dimitri Glazkov dglaz...@google.com
wrote:
I did a quick experiment around
With respect to Dimitri's *unpacking* notion, we think it can work.
In most cases today the redistribution tree is not large; however, if there
were a lot of final destination points in that tree, unpacking would be
cumbersome because you need to define a slot at every level for every final
Hi folks,
please register for the meeting:
https://www.w3.org/2002/09/wbs/42538/WebComponents21July2015/
There is also a meeting page - at this stage still somewhat light on details,
as we don't yet have too many confirmed:
https://www.w3.org/wiki/Webapps/WebComponentsJuly2015Meeting
cheers
10 matches
Mail list logo
