nextjs - 💡(How to fix) Fix ViewTransition not working in rtl app [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#87773Fetched 2026-04-08 02:06:11
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
1
Timeline (top)
commented ×2cross-referenced ×1issue_type_added ×1subscribed ×1

Code Example

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
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Change the dir attribute in the HTML to handle right-to-left (RTL) text direction correctly in the Next.js application.

Guidance

  • Verify that the issue is indeed related to the RTL text direction by checking the HTML and CSS code for any hardcoded or missing dir attributes.
  • Check the Next.js configuration and page components for any potential issues with handling RTL text direction.
  • Test the application with different dir attributes (e.g., dir="rtl" and dir="ltr") to see if the issue persists.
  • Review the CSS styles for any potential conflicts or overrides that might be affecting the RTL layout.

Example

No specific code snippet can be provided without more context, but the fix likely involves adding or modifying the dir attribute in the HTML template or component.

Notes

The issue seems to be related to the handling of RTL text direction in the Next.js application, but more information about the specific code and configuration would be helpful to provide a more accurate solution.

Recommendation

Apply a workaround by manually adding the dir attribute to the HTML template or component to handle RTL text direction correctly, as the root cause of the issue is not entirely clear from the provided information.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix ViewTransition not working in rtl app [2 comments, 3 participants]