fix(TU-18127): Replace __dangerous-disable-submissions with enable-sandbox=true#699
fix(TU-18127): Replace __dangerous-disable-submissions with enable-sandbox=true#699tom-ridsdale merged 1 commit intomainfrom
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
|
[BOT] Preview available with hash |
|
|
🥷 Code experts: No results found No code experts were identified for the files in this pull request based on git blame analysis. This may occur when:
If you expected to see expert suggestions, consider:
To learn more about /:\gitStream - Visit our Docs |
# [@typeform/embed-v5.5.1](https://github.com/Typeform/embed/compare/@typeform/embed-v5.5.0...@typeform/embed-v5.5.1) (2025-11-14) ### Bug Fixes * **TU-18127:** Replace __dangerous-disable-submissions with enable-sandbox=true ([#699](#699)) ([7bf7879](7bf7879))
|
🎉 This PR is included in version @typeform/embed-v5.5.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |



Summary
https://typeform.atlassian.net/browse/TU-18127
Separate sandbox mode behaviour from submission-disabled mode by introducing a distinct
enable-sandboxquery parameter.Problem
Previously,
enableSandbox: truein the embed SDK would pass__dangerous-disable-submissions=trueto therenderer, causing sandbox mode and submission-disabled mode to be treated identically. This prevents redirects from working in sandboxed embeds.Solution
Pass
enable-sandbox=trueinstead of__dangerous-disable-submissions=truewhenenableSandboxis set, allowing the renderer to distinguish between the two flows.