vercel / vercel/next.js

ViewTransition not working in rtl app

Open
#87,773 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

Link to the code that reproduces this issue

https://github.com/vercel/next-view-transition-example

To Reproduce
  1. Clone next-view-transition-example.
  2. Change the html dir to rtl
    Or you can just test it directly in here and change the dir of the page then test it
Current vs. Expected behavior

https://github.com/user-attachments/assets/cee90b97-c45f-4af8-a5e3-39f3a8b00a0f

Provide environment information
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 7988
  Available CPU cores: 8
Binaries:
  Node: 24.12.0
  npm: 11.1.0
  Yarn: 1.22.22
  pnpm: 10.8.1
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

Additional context

No response

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

Clone the linked next-view-transition-example reproduction and change the page's HTML direction to rtl. Compare the ViewTransition behavior locally and on the deployed example, then identify the relevant Next.js or browser integration entry point; done means the transition behaves correctly in the rtl reproduction. No file or test is named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nextjs, react
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.