[css-view-transitions-1] A few clarifications and nits #9028
Conversation
- Separated view transition activation to own algorithm, to prepare for cross-doc - Clarifying that new elements are invisible during the transition - Changed type of image from ImageData to 2D-bitmap - Fixed a few broken refs See w3c#8958
|
@fantasai FYI |
Co-authored-by: Khushal Sagar <[email protected]>
| @@ -787,6 +789,9 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface; | |||
| since that results in a circular dependency. | |||
| Therefore, the [=view transition layer=] is a sibling of all other content. | |||
|
|
|||
| When a {{Document}}'s [=document/active view transition=]'s [=ViewTransition/phase=] is "`animating`", | |||
There was a problem hiding this comment.
Should this have both <code> and quotes?
There was a problem hiding this comment.
(I'm not familiar with the conventions here, so just asking.)
There was a problem hiding this comment.
I don't think so. This spec uses <code> for syntax which can be used by an author. phase is internal UA state.
| * Effects applied on the element and its descendants, such as 'opacity' and 'filter', are applied to the capture. | ||
| Effects applied to the element from its ancestors are ignored. |
There was a problem hiding this comment.
Where is “Effects” as used here defined?
There was a problem hiding this comment.
That is a good question. Is there a definition in CSS for visual effects on an element which affect its descendants? The list here is the closest I've seen in documentation. I can also just add all these properties explicitly but nicer if we can have one definition to cross-reference.
| @@ -787,6 +789,9 @@ urlPrefix: https://wicg.github.io/navigation-api/; type: interface; | |||
| since that results in a circular dependency. | |||
| Therefore, the [=view transition layer=] is a sibling of all other content. | |||
|
|
|||
| When a {{Document}}'s [=document/active view transition=]'s [=ViewTransition/phase=] is "`animating`", | |||
There was a problem hiding this comment.
I don't think so. This spec uses <code> for syntax which can be used by an author. phase is internal UA state.
| * Effects applied on the element and its descendants, such as 'opacity' and 'filter', are applied to the capture. | ||
| Effects applied to the element from its ancestors are ignored. |
There was a problem hiding this comment.
That is a good question. Is there a definition in CSS for visual effects on an element which affect its descendants? The list here is the closest I've seen in documentation. I can also just add all these properties explicitly but nicer if we can have one definition to cross-reference.
See #8958