-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Document the known issues related to cookie blocking by different browsers #21853
Comments
@azatsarynnyy, if possible, please ask the assignee to reach out to the docs team, ideally before opening a PR to the docs repo, so that we can figure out together where to incorporate this new content in the docs. Here's the docs issue: https://issues.redhat.com/browse/RHDEVDOCS-4803. |
@max-cx I wrote some notes here https://gist.github.com/azatsarynnyy/bb2947b2fef01b2776162713add33505 @RomanNikitenko can you please help me to verify how the suggested workaround works on macOS? It would be great if you could check which of the described option works for you. |
About Firefox I can not reproduce the problem - it works fine for me without any workarounds. Today I tested it for:
My settings you can see here: |
Thanks, @RomanNikitenko for verifying it. |
@max-cx I've drafted content related to this issue. Please, find it here https://gist.github.com/azatsarynnyy/bb2947b2fef01b2776162713add33505 |
The PR eclipse-che/che-docs#2568 is under review. |
Is your task related to a problem? Please describe
Upstream VS Code has a known issue with the correct WebView work depending on the browser's settings related to the Third-Party Cookies blocking. ATM, it is not documented on the VS Code docs.
The Che user may face such an issue very easily when opening Che in Firefox on Mac OS.
The problem appears as an empty WebView-based page in VS Code UI. Also, the user gets a notification saying:
Describe the solution you'd like
We should document this upstream problem as a known issue and describe the possible options for how the user can work it around by changing the browser's settings.
The details I've described in #21852 (comment).
Describe alternatives you've considered
As a more general solution, we could create a dedicated page in Che docs describing:
Additional context
The text was updated successfully, but these errors were encountered: