Add referrerpolicy prop to Vimeo element to support whitelisted domains #209
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves 207 by adding a new
referrerpolicyprop to the Vimeo element configuration.Problem: When a parent page sets , the browser does not send the origin by default. This causes Vimeo videos with domain whitelisting enabled to be playback blocked.
Solution: By adding the
referrerpolicyprop (e.g., "strict-origin-when-cross-origin") to the Vimeo iframe, we ensure that the origin is sent even if the parent page has a restrictive referrer policy, allowing whitelisted videos to play correctly.