vscode-web.md: Add sentence about Firefox #7892
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@joaomoreno Can you review this docs PR for vscode.dev? |
mbete78
reviewed
Jan 22, 2025
| @@ -179,7 +179,7 @@ Edge and Chrome today support the [File System API](https://developer.mozilla.or | |||
|
|
|||
| ### Browser support | |||
|
|
|||
| You can use VS Code for the Web in the latest versions of Chrome, Edge, Firefox, and Safari. Older versions of each browser may not work - we only guarantee support for the latest version. | |||
| You can use VS Code for the Web in the latest versions of Chrome, Edge, Firefox, and Safari. Note that on Firefox, if you have enabled the "strict" Enhanced Tracking Protection, you need to to exempt `vscode.dev` for some functionality to work (such as opening a git repo). Older versions of each browser may not work - we only guarantee support for the latest version. | |||
|
|
|||
| > **Tip:** One way to check the compatible browser version is to look at the version of [Playright](https://playwright.dev/) currently used for testing VS Code and review its supported browser versions. You can find the currently used Playwright version in the VS Code repo's [package.json](https://github.com/microsoft/vscode/blob/main/package.json) file at `devDependencies/@playwright/test`. Once you know the Playwright version, for example `1.37`, you can then review the **Browser Versions** section in their [Release notes](https://playwright.dev/docs/release-notes). | |||
There was a problem hiding this comment.
what? if you're a maintainer, feel free to edit the PR as you see fit.
|
@mb21 Can you show me exactly what happens if you don't exempt vscode.dev? I just tried it on my machine: I set the Protection Settings to Strict, and vscode.dev still works just fine. |
|
@joaomoreno I believe it only fails if your GitHub account isn't linked to vscode.dev yet. So to test it you'd need to remove the 'app' from your GitHub profile. Then the first time it gives the error:
See e.g. https://www.reddit.com/r/Floorp/comments/1gbymgr/comment/m3rexzg/?context=3 |
omgm18
approved these changes
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.