Skip to content

Resolve YouTube Error 153 and add graceful degradation in JourneyModal - #1687

Open
PARTH-TUSSLE wants to merge 3 commits into
layer5io:masterfrom
PARTH-TUSSLE:fix/getting-started-video-fallback
Open

Resolve YouTube Error 153 and add graceful degradation in JourneyModal#1687
PARTH-TUSSLE wants to merge 3 commits into
layer5io:masterfrom
PARTH-TUSSLE:fix/getting-started-video-fallback

Conversation

@PARTH-TUSSLE

@PARTH-TUSSLE PARTH-TUSSLE commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Notes for Reviewers

Description

This PR resolves "Error 153: Video player configuration error" that occurs in the Getting Started widget's YouTube iframe when running on localhost (insecure HTTP) and playground.meshery.io due to the browser's default cross-origin referrer policy.

Changes Made

  • Added referrerPolicy="strict-origin-when-cross-origin" to the existing YouTube iframe in JourneyModal.tsx.
{89290EE3-5D32-49DD-908F-7210E80F06BB}

Related issue -> meshery/meshery#20118
Related PR -> meshery/meshery#20520

Signed commits

  • [✅] Yes, I signed my commits.

Summary by CodeRabbit

  • Bug Fixes
    • Improved privacy and security when displaying embedded YouTube videos by applying stricter referrer handling.

Signed-off-by: Parth Gartan <parthgartan26feb@gmail.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request adds a fallback link below the embedded YouTube video iframe in the JourneyModal component to allow users to watch the video directly on YouTube if they encounter issues, and updates the iframe with a strict referrer policy. The review feedback recommends extracting the hardcoded YouTube video ID into a constant to prevent duplication and exposing the fallback link text as a configurable prop to support internationalization and localization.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread src/custom/DashboardWidgets/GettingStartedWidget/JourneyModal.tsx Outdated
Comment thread src/custom/DashboardWidgets/GettingStartedWidget/JourneyModal.tsx Outdated
Signed-off-by: Parth Gartan <parthgartan26feb@gmail.com>
@PARTH-TUSSLE

Copy link
Copy Markdown
Contributor Author

@leecalcote leecalcote left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Where is the link to your other PR and the feedback already received?

@PARTH-TUSSLE

Copy link
Copy Markdown
Contributor Author

Where is the link to your other PR and the feedback already received?

@leecalcote I've updated the PR description with the open PR in meshery regarding this issue. And I actually closed the other PR ( the one which I was working on earlier ) because it had many commits now cause I was working on it for 2 weeks, and to start fresh from synced masters, I created new branches and PRs . Should I link the closed PR as well, in case someone wants to see the earlier reviews?

@leecalcote

Copy link
Copy Markdown
Member

This widget shouldn't be included in Sistent in the first place.

@PARTH-TUSSLE

Copy link
Copy Markdown
Contributor Author

This widget shouldn't be included in Sistent in the first place.

@leecalcote Agreed, sistent should only have reusable componenets. I was only making these changes here to fix the YouTube Error 153 on strict browsers bug , where the code currently lives. Along with this Getting started widget, there are several other specific widgets in Sistent right now (e.g., RecentDesignWidget, WorkspaceActivityWidget, TeamSearchField etc.). Should we now migrate the GettingStartedWidget (and potentially the other Dashboard widgets) directly into the meshery repository? Let me know how to proceed.

@PARTH-TUSSLE
PARTH-TUSSLE requested a review from leecalcote July 7, 2026 09:54
Signed-off-by: Parth Gartan <parthgartan26feb@gmail.com>
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

JourneyModal adds an explicit strict-origin-when-cross-origin referrer policy to the YouTube video iframe.

Changes

Journey video embedding

Layer / File(s) Summary
YouTube iframe referrer policy
src/custom/DashboardWidgets/GettingStartedWidget/JourneyModal.tsx
The YouTube iframe now sets referrerPolicy to strict-origin-when-cross-origin.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: leecalcote

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the YouTube iframe change and its intended purpose of resolving Error 153.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Utkarsh-Mauryaa

Copy link
Copy Markdown

@PARTH-TUSSLE The description currently only mentions that Error 153 occurs on localhost. However, the same error is also occurring on playground.meshery.io. It would be good to update the description to reflect that the issue is reproducible on the playground website as well.

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.

3 participants