w3c / w3c/csswg-drafts

[css-view-transitions-2] Declarative view transitions for same-document navigations.

Open
#8,300 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

css-view-transitions-2
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

Cross-document same-origin transitions build on the idea of View transitions being implicitly triggered by a navigation. While it's obvious that this should be done for cross-document navigations, authors could use the declarative transition for same-document navigations involving a hash change as well.

This can be made configurable with the declarative opt-in we decide in #8048.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the cross-document same-origin transitions section of the linked View Transitions explainer, then read issue #8048 for the proposed declarative opt-in. The work is complete when the chosen opt-in also defines the behavior for same-document hash navigations.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.