vmpstr

Results 68 comments of vmpstr

One other consequence of the TPAC resolution is that since the ::vt pseudo escapes the clips, and contains all of the participating elements, it means that view transition participants in...

If we make self participation mandatory, then I think that gives us a nice model to work with: we set up an automatic nesting, and have overflow: clip if the...

A comment on whether group-children is a direct child of the ::v-t: I'm happy to say that we also create an empty ::view-transition-group(!?) to nest this, just not the image-pair...

> > we would create `::view-transition-group-children(root)` even if the developer sets `view-transition-name: none` > > This breaks the basic promise of “Elements with a `view-transition-name` (other than `none`) get captured”,...

I've summarized the couple of options discussed and concerns about those below: 1. Make scope `view-transition-name` optional and have `view-transition-group: contain` by default. In a situation where `view-transition-name` is `none`,...

Yes, that's correct. Option 1 UA stylesheet would be `view-transition-name: root; view-transition-group: contain` with extra magic if name is none. Option 2 is `view-transition-name: root !important; view-transition-group: contain`, so no...

> Do they _need_ to be uniquely selectable by developers or could they have a generic unnamed pseudo-element tag or perhaps a name similar to match-element (i.e. not developer exposed)....

@bramus, are you happy with pursuing option 1 in light of -ua-root and other discussion here? Specifically, limiting the `view-transition-name: none` with `view-transition-group: contain` to only scopes on which startVT...