-
The current spec mentions a UA defined timeout as part of `resolve inbound cross-document view-transition`, which then cancels the active view transition (in a queued task).
The `pageswap-long-dela…
-
Follow up on #10334 (nested transitions)
It's clear what happens when both the old and new state have the same `view-transition-group`.
We need to specify, however what happens when there is a mis…
-
Apparently there are invalid types (see #9534):
> type can accept any idents, except 'none' or '-ua-' prefixes
I would suggest throwing a TypeError or a SyntaxError when these are used in DOM APIs…
-
If an element in the new Document for a cross-document transition has `content-visibility: auto`, it's `view-transition-name` is skipped. This is because the algorithm to look for names runs before th…
-
With the full screen API we can take any DOM element and request it to be displayed full screen.
This works great but the transition often looks very bad.
example : https://www.maison-osain.com/pr…
-
The cross-document [spec](https://drafts.csswg.org/css-view-transitions-2/) currently limits transitions to Document in the same-origin. This misses a common use-case of transitions on same-site cross…
-
Follow up on #10334
It's unclear how to specify `view-transition-group` in terms of shadow trees.
Sure, we can make the `` a tree-scoped reference, which means it can't reference names from a dif…
noamr updated
1 month ago
-
Currently, the default behavior for the content pseudo-elements (`::view-transition-old` and `::view-transition-new`) is to animate to/from `opacity: 0`. This is usually sufficient, and customizable b…
-
# The double flash experience
I love Adaptive Tab Bar Color and this theme's integration with it! However, when switching tabs for example, the change in color lags behind the change of page by a tin…
-
### Тема
Анимация переходов между страницами с использованием View Transitions API.
Обязательно два разных примера.
- Переходы между разными документами (страницами)
- Переходы внутри одного док…