Add fallback redirect button for browser-restricted auto redirection #417
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.
Summary
Some browsers block automatic redirection when initiated from an iframe or without a user gesture due to security restrictions (e.g., Chrome's cross-origin navigation policies). This update introduces a fallback button that allows users to manually trigger the redirect if the automatic redirection fails.
Changes
<button>
element to the redirect page.click
event to ensure compliance with browser security policies.Why This Is Needed
Automatic redirection can fail silently in certain browser contexts, particularly when embedded or without user interaction. The fallback ensures consistent user flow across all environments.
Testing
Tested in:
Redirection now works either automatically or via user interaction when needed.