-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
can't login into https://riot.im due to shields blocking cross-origin requests #2521
Labels
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
webcompat/shields
Shields is breaking a website.
Milestone
Comments
have been noticing the same for about a day |
Should fixed as a duplicate of #2252 |
iefremov
modified the milestones:
1.x Backlog,
0.58.x - Release Hotfix 3 (Release Channel)
Jan 9, 2019
Verification passed on
Verification PASSED on
Verified passed with
|
This was referenced Jan 9, 2019
kjozwiak
changed the title
"3rd-party cookies blocked" seems to also block cross-origin requests as well
can't login into https://riot.im due to shields blocking cross-origin requests
Jan 11, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release-notes/include
webcompat/shields
Shields is breaking a website.
Description
A user reported that our site was broken in Brave. It appears that the Brave mode "3rd-party cookies blocked" also blocks cross-origin requests, which seems like a bug based on the setting's name.
Steps to Reproduce
Actual result:
Expected result:
If I set to allow cookies, then I get:
Reproduces how often:
Always.
Brave version (brave://version info)
Brave | 0.57.18 Chromium: 71.0.3578.80 (Official Build) (64-bit)
Revision | 2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860}
OS | Mac OS X
Reproducible on current release:
Yes, reproduces on Dev as well.
Website problems only:
Yes, disabling the shield (or just changing the cookies part) resolves it.
No, Chrome works correctly.
The text was updated successfully, but these errors were encountered: