Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Improve startViewTransition() data#28541

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
chrisdavidmills wants to merge1 commit intomdn:main
base:main
Choose a base branch
Loading
fromchrisdavidmills:update-document-startViewTransition

Conversation

@chrisdavidmills
Copy link
Contributor

@chrisdavidmillschrisdavidmills commentedNov 27, 2025
edited
Loading

Summary

Chrome and Safari have both supported view transition types (seehttps://chromestatus.com/feature/5089552511533056) for a while, so it is high time I got them documented on MDN.

Having checked BCD, it seems that we have pretty much all of the data we need in place already, but I wanted to improve theDocument.startViewTransition() data:

  1. Originally, the method only took one parameter, a callback function.
  2. It then got updated so that it can either take the callback function, or an options object containing the callback function as a property, plus a types array as a property.
  3. The current data has two sub-data points:
    a.updateCallback makes sense — this is the callback parameter mentioned in 1.
    b.callbackOptions doesn't make sense. This refers to a mixin in the spec that represents the possible parameter values as one item. This is a spec construct and not a real value that developers can use. It would be better to have a sub-data point for the options object, with sub-sub-data points for the possible object properties. This last bit is maybe not totally necessary, but I thought it would be useful for developers who are specifically checking the compat table fortypes support.

This PR updates the data as described above, and also updates the spec URLs so they all point to the Level 2 of the spec

Test results and supporting details

Related issues

@github-actionsgithub-actionsbot added data:apiCompat data for Web APIs. https://developer.mozilla.org/docs/Web/API size:m[PR only] 25-100 LoC changed labelsNov 27, 2025
@github-actions
Copy link
Contributor

Tip: Review these changesgrouped by change (recommended for most PRs), orgrouped by feature (for large PRs).

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@caugnercaugnerAwaiting requested review from caugner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

data:apiCompat data for Web APIs. https://developer.mozilla.org/docs/Web/APIsize:m[PR only] 25-100 LoC changed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@chrisdavidmills

[8]ページ先頭

©2009-2025 Movatter.jp