codesandbox / codesandbox/codesandbox-client

Private CodeSandbox infinitely reloads in Safari

Open
#6,606 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 bug report

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

Sandboxes marked as 'Private' (as opposed to 'Public' or 'Unlisted') infinitely reload on Safari, which makes working in them impossible.

How has this issue affected you? What are you trying to accomplish?

I've recently tried to have pairing sessions via Live Mode with others who use Safari as their default browser, and the only workaround is to use Chrome or Firefox. To be fair, it's not a big deal for my coworkers, but my company also uses it to conduct interviews so it'd be nice to not have to ask candidates to change browsers.

To Reproduce
  • Create any sandbox
  • Change the permissions from 'Public' to 'Private'
  • Reload the sandbox

Here's a video of changing to 'Private' and reloading. It stops immediately when I change it back to 'Public':
2022-04-06 11 51 35

Link to sandbox: Freshly forked vanilla app
Your Environment
Software Name/Version
Сodesandbox Latest
Browser Safari, 15.2 (17612.3.6.1.6)
Operating System macOS 12.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Safari 15.2 on macOS 12.1 using the linked sandbox: change its permissions from Public to Private and reload it, then compare the behavior with Chrome or Firefox and with a Public sandbox. Trace the private-sandbox loading flow to identify the reload loop; done means Private sandboxes load normally in Safari without requiring a browser change.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.