On Thu, Sep 19, 2013 at 4:09 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
So, to be clearer, we'd be adding two new combinators, ^ and ^^.
^, the shadow combinator (or hat), pierces the upper-boundary
encapsulation of a shadow root. The LHS has to be a component,
something with an actual
For context here's another thread about ::part where we start to look a
little into the rabbit hole:
http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0012.html
One wants the expressiveness of css applied to ::part but things get
complicated very fast and the 'shadow cat' starts to
On Mon, Sep 9, 2013 at 4:32 PM, Dimitri Glazkov dglaz...@google.com wrote:
Part 1: Revenge of the :host
Turns out, it's bad to be Super Man. After the Shadow DOM meetup,
where we decided that shadow host could be matched by both outer and
inner trees
On Tue, Sep 10, 2013 at 1:32 AM, Dimitri Glazkov dglaz...@google.com wrote:
To calm the brave guinea people down, I showed them a magic trick. Out
of my sleeve, I pulled out two new combinators: A hat (^) and a cat
(^^).
The syntax here certainly looks interesting. However how are we
planning
On Tue, Sep 10, 2013 at 6:54 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Sep 10, 2013 at 1:32 AM, Dimitri Glazkov dglaz...@google.com wrote:
To calm the brave guinea people down, I showed them a magic trick. Out
of my sleeve, I pulled out two new combinators: A hat (^) and a cat
(^^).
On Tue, Sep 10, 2013 at 6:14 PM, Dimitri Glazkov dglaz...@google.com wrote:
On Tue, Sep 10, 2013 at 6:54 AM, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Sep 10, 2013 at 1:32 AM, Dimitri Glazkov dglaz...@google.com wrote:
To calm the brave guinea people down, I showed them a magic trick. Out
This progress update is brought to you in part by the Sith Order:
Sith: When The Light Side Just Ain't Cuttin' It.
Part 1: Revenge of the :host
Turns out, it's bad to be Super Man. After the Shadow DOM meetup,
where we decided that shadow host could be matched by both outer and
inner trees
I'm one of the guinea people, for whatever biases that gives me. Fwiw and
IMO, Dimitri summarized our thinking better than our own brains did.
finally ruined encapsulation?
As I see it the main Web Components system is based on soft encapsulation.
Each boundary is in force by default, but each
On Mon, Sep 9, 2013 at 4:32 PM, Dimitri Glazkov dglaz...@google.com wrote:
For what it's worth, it would be fairly easy to make shadow tree rules
match shadow host only when :host is present in a rule.
Unfortunately, this would leave Tab (and other CSS WG folks) in a sad
state, since
since you have no clue what parts of your existing markup structure are
being depended on by others.
But we already have no clue. In all cases we are talking about guidelines.
You cannot outright prevent people from poking around in the guts of your
component.
In either case you can be assured
On Mon, Sep 9, 2013 at 6:20 PM, Scott Miles sjmi...@google.com wrote:
I'd greatly prefer to stick with the current plan of having to mark
things to be exposed explicitly,
Fwiw, we tried that and got in the weeds right away. See Dimitri's post for
details. I'm afraid of trading real-life pain
On Sep 9, 2013 9:32 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Sep 9, 2013 at 6:20 PM, Scott Miles sjmi...@google.com wrote:
I'd greatly prefer to stick with the current plan of having to mark
things to be exposed explicitly,
Fwiw, we tried that and got in the weeds right
12 matches
Mail list logo
