Maybe the problem comes from not distinguishing elements being created and
ready for API access versus elements is ready for interactions?
I’d also imagine that the exact appearance of a custom element between the time
the element is created and the time it is ready for interaction will depend
Yes, I agree with what R. Niwa says.
I believe there are many variations on what should happen during element
lifecycle, and the element itself is best positioned to make those choices.
`:unresolved` is special because it exists a-priori to the element having
any control.
Scott
On Wed, Mar
On Wed, Mar 26, 2014 at 4:53 PM, Scott Miles sjmi...@google.com wrote:
Yes, I agree with what R. Niwa says.
I believe there are many variations on what should happen during element
lifecycle, and the element itself is best positioned to make those choices.
`:unresolved` is special because
Do custom elements present any new challenges in comparison to non-custom
elements here? I feel like you have the same issue with filling a select with
data from a remote source.
From: Brian Kardell bkard...@gmail.com
Sent: Tuesday, March 25, 2014 17:31
To:
Let me try and repeat this back to you, standards-nerd-style:
Now that we have custom elements, there's even more need for notifying a
style engine of a change in internal elements state -- that is, without
expressing it in attributes (class names, ids, etc.). We want the ability
to make custom
On Tue, Mar 25, 2014 at 6:10 PM, Domenic Denicola
dome...@domenicdenicola.com wrote:
Do custom elements present any new challenges in comparison to
non-custom elements here? I feel like you have the same issue with filling
a select with data from a remote source.
Only really the fact that
On Tue, Mar 25, 2014 at 6:27 PM, Dimitri Glazkov dglaz...@chromium.orgwrote:
Let me try and repeat this back to you, standards-nerd-style:
Now that we have custom elements, there's even more need for notifying a
style engine of a change in internal elements state -- that is, without
It seems to me you probably should have just not included :unresolved in your
very small subset. In reality, it seems, :unresolved for existing elements is
just { display: none; }. That is, if you do
`selectoptiona/option/select` you don't see the unstyled string a on
the page, only later
