Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[css-view-transitions-2] Allow auto as a keyword #10922

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

noamr
Copy link
Collaborator

@noamr noamr commented Sep 19, 2024

auto resolves to either the element's ID, or to a unique identifier that is stable for the duration of the transition and is not web-observable.

Resolution: #8320 (comment)
Closes #8320

`auto` resolves to either the element's ID, or to a unique identifier
that is stable for the duration of the transition and is not web-observable.

Resolution: w3c#8320 (comment)
Closes w3c#8320
@@ -755,7 +755,20 @@ div.box {

# Nested view-transitions # {#nested-view-transitions}

## Overview ## {#nested-overview}
## Overview ## {#auto-name-overview}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this under Nested view-transitions? Doesn't have anything to do with that feature. Looks like you inadvertently overrode the overview for nested view-transitions..?

1. If |computed| is a <<custom-ident>>, return |computed|.
1. Assert: |computed| is <css>auto</css>.
1. If |element| has an associated [=Element/id=], then return |element|'s [=Element/id=].
1. Return a unique string, which is not a <<custom-ident>>. This string should remain consistent at least for the lifetime of |element|'s [=node document=]'s [=active view transition=].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure how exactly to reword this but a couple of things are not obvious right now:

  • The string needs to uniquely identify the element. Right now it's ambiguous whether we mean unique for that specific transition.
  • For the cross-doc case, this sounds like any auto element without an id will become an exit animation since there won't be a match in the new Document. Is that the intention? If so, the string should remain unique even the document changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[css-view-transitions-2] view-transition-name determined by element
2 participants