Skip to content

[css-view-transitions-1] Handling rendering constaints #8540

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

Merged
merged 10 commits into from
Apr 19, 2023

Conversation

jakearchibald
Copy link
Contributor

@jakearchibald jakearchibald commented Mar 7, 2023

Fixes #8139

Fixes #7882

Depends on w3c/fxtf-drafts#507 - merged

@khushalsagar
Copy link
Member

Just the one suggestion above. Feel free to merge with that applied if you're happy with it.

@@ -593,7 +607,7 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
This enables full customization of the transition.
</div>

### <dfn>::view-transition</dfn>
### <dfn>::view-transition</dfn> ### {#::view-transition}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just fixing some bikeshed errors while I'm here

Comment on lines +1288 to +1289
1. Let |namedElements| be |transition|'s [=ViewTransition/named elements=].

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Quick fix of something that was missed in an earlier refactor

@@ -497,6 +499,19 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface;
This may be confusing, since the elements themselves are not necessarily referring to the same object,
but it is a useful model to consider them to be visual states of the same conceptual page entity, that we happen to call "element".

# Layout and rendering changes # {#layout-rendering-changes}

Both {{Element}}s and [=pseudo-elements=] have a <dfn>involved in a view transition</dfn>, a boolean. Initially false.
Copy link
Member

Choose a reason for hiding this comment

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

Nitty nit, feel free to ignore. :)

Suggested change
Both {{Element}}s and [=pseudo-elements=] have a <dfn>involved in a view transition</dfn>, a boolean. Initially false.
Both {{Element}}s and [=pseudo-elements=] have a boolean: <dfn>involved in a view transition</dfn>. Initially false.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm, all other concept definitions in the spec are "name, a type. Initially value"

Copy link
Member

Choose a reason for hiding this comment

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

Cool. If this is already a pattern in the spec, SGTM.

@jakearchibald jakearchibald merged commit d74719a into w3c:main Apr 19, 2023
@jakearchibald jakearchibald deleted the rendering-constraints branch April 19, 2023 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants