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] Apply new @view-transition rule syntax #9523

Merged
merged 4 commits into from
Oct 26, 2023

Conversation

noamr
Copy link
Collaborator

@noamr noamr commented Oct 25, 2023

  • Use the @view-transition { navigation: auto | none; type: ... } syntax as per the resolution
  • type: none means that type is unspecified, needs a resolution
  • reloads are ignored as per previous resolution
  • Renamed the JS param "type" instead of "types"
  • Currently types are resolved both at old and new document separately, this needs a resolution.

Closes #9383

See resolution: #9383 (comment)

- Use the `@view-transition { navigation: auto | none; type: ... }` syntax as per the resolution
- `type: none` means that type is unspecified, needs a resolution
- reloads are ignored as per previous resolution
- Renamed the JS param "type" instead of "types"
- Currently types are resolved both at old and new document
  separately, this needs a resolution.

Closes w3c#9383

See resolution: w3c#9383 (comment)
@noamr
Copy link
Collaborator Author

noamr commented Oct 25, 2023

cc @bokand

@noamr noamr changed the title [css-view-transitions-2] Apply new CSS rule syntax [css-view-transitions-2] Apply new @view-transition rule syntax Oct 25, 2023
@noamr noamr merged commit d6c50e9 into w3c:main Oct 26, 2023
1 check passed
@noamr noamr deleted the vt-rule branch October 26, 2023 14:47

1. Set |document|'s [=document/ready to render fired=] to true.
1. If |matchingRule| contains a ''@view-transition/type'' descriptor, then return a [=list=] of strings corresponding to that descriptor's [=computed value=].
Copy link
Member

Choose a reason for hiding this comment

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

@noamr an empty list vs null has the same effect right? Based on my reading here it does so just confirming.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, though there is no way to specify an empty list.


1. Let |transition| be the result of getting the [=inbound cross-document view-transition=] for |document|.
1. [=Fire an event=] named <code>pagereveal</code> at |document|'s [=relevant global object=],
using {{PageRevealEvent}}, with [=PageRevealEvent/view transition=] initialized to .
Copy link
Member

Choose a reason for hiding this comment

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

I think you meant "initialized to the [=inbound cross-document view-transition=]".

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Oops, should be |transition|. Will follow up.

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] Decide on naming for navigation-triggered view-transition rule
3 participants