Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS Code is stuck with infinite loading on Safari v16 and lower #197473

Closed
raphaeldn28 opened this issue Nov 5, 2023 · 5 comments · Fixed by #198717
Closed

VS Code is stuck with infinite loading on Safari v16 and lower #197473

raphaeldn28 opened this issue Nov 5, 2023 · 5 comments · Fixed by #198717
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug confirmed Issue has been confirmed by VS Code Team member *out-of-scope Posted issue is not in scope of VS Code settings-editor VS Code settings editor issues
Milestone

Comments

@raphaeldn28
Copy link

ADD ISSUE DESCRIPTION HERE

It does not matter which file I load or opem, it is stuck with infinite loading

Version: 1.84.0
Commit: d037ac0
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36
Embedder: codespaces

@Raubzeug
Copy link

I have the same issue. I've done some investigations and found out the problem is here

const camelParts = word.split(/(?<=[a-z])(?=[A-Z])/g);
. It doest works with Safari < v17 because of error invalid group specifier name.

@vscodenpa vscodenpa added the stale Issues that have not been triaged in an appropriate amount of time label Nov 17, 2023
@rebornix rebornix removed their assignment Nov 17, 2023
@mjbvz mjbvz assigned rzhao271 and unassigned mjbvz Nov 20, 2023
@vscodenpa vscodenpa removed triage-needed stale Issues that have not been triaged in an appropriate amount of time labels Nov 20, 2023
@vscodenpa vscodenpa added the unreleased Patch has not yet been released in VS Code Insiders label Nov 21, 2023
@vscodenpa vscodenpa added this to the November 2023 milestone Nov 21, 2023
@vscodenpa vscodenpa added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Nov 22, 2023
@rzhao271 rzhao271 added bug Issue identified by VS Code Team member as probable bug settings-editor VS Code settings editor issues labels Nov 22, 2023
@eleanorjboyd eleanorjboyd added the verification-steps-needed Steps to verify are needed for verification label Nov 29, 2023
@rzhao271
Copy link
Contributor

I do have an older macOS VM, but it doesn't seem to be booting right now. My current macOS device is on Safari 17.

@raphaeldn28 @Raubzeug is the issue fixed for either of you?

One way to test is to launch https://insiders.vscode.dev, and then to search just "a" in the Settings editor while having GitHub Copilot Chat disabled or not installed. If the Settings editor is able to finish the search, then the fix worked.

@rzhao271 rzhao271 removed the verification-steps-needed Steps to verify are needed for verification label Nov 30, 2023
@rzhao271 rzhao271 changed the title VScode is stuck with infinite loading VS Code is stuck with infinite loading on Safari v16 and lower Nov 30, 2023
@Raubzeug
Copy link

@rzhao271 Hi! I've just checked with Safari 15 and 16 and https://insiders.vscode.dev doest'n work. The problem is here now:

Screenshot 2023-11-30 at 10 08 03

By the way, it works properly with Safari 17.

@rzhao271 rzhao271 reopened this Nov 30, 2023
@rzhao271 rzhao271 added the verification-found Issue verification failed label Nov 30, 2023
@rzhao271 rzhao271 modified the milestones: November 2023, Backlog Nov 30, 2023
@vscodenpa vscodenpa removed the insiders-released Patch has been released in VS Code Insiders label Nov 30, 2023
@rzhao271 rzhao271 removed the verification-found Issue verification failed label Dec 19, 2023
@rzhao271 rzhao271 added the confirmed Issue has been confirmed by VS Code Team member label Dec 19, 2023
@rzhao271
Copy link
Contributor

I finally confirmed the unexpected token issue with a VM, but I'm unsure which part of the code it comes from.

Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vs-code-engineering vs-code-engineering bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug confirmed Issue has been confirmed by VS Code Team member *out-of-scope Posted issue is not in scope of VS Code settings-editor VS Code settings editor issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants