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

Update CORS documentation for stricter Safari handling #9178

Open
jazzsequence opened this issue Aug 15, 2024 · 0 comments
Open

Update CORS documentation for stricter Safari handling #9178

jazzsequence opened this issue Aug 15, 2024 · 0 comments
Labels
Process: SME Wanted Issues/PRs that benefit SME. Set a date to proceed if SME input does not come Source: Desk Issue originated from Support Ticket Topic: Code Structure Related to Upstreams and other code structure details Type: Fix Content Issue or PR to resolve incorrect information in the docs

Comments

@jazzsequence
Copy link
Contributor

Re: Create a WordPress MU-Plugin for Actions and Filters: Cross-Origin Resource Sharing (CORS)

Priority: Medium

Issue Description

A customer requested for an additional note regarding CORS issues on Safari in this doc

Safari has stricter rules compared to chromium-based browser, which leads to CORS issues only there (reference here). The customer is aware of the scope of the issue, and stated it would be helpful if an additional note mentions that CORS issues may continue in certain browsers even if the correct steps are followed.

Suggested Resolution

  • Update the doc to note Safari rules.
  • If it's possible to suggest a solution/alternative, we should document that, too. May require SME to validate.
@jazzsequence jazzsequence added Type: Fix Content Issue or PR to resolve incorrect information in the docs Source: Desk Issue originated from Support Ticket Topic: Code Structure Related to Upstreams and other code structure details Process: SME Wanted Issues/PRs that benefit SME. Set a date to proceed if SME input does not come labels Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Process: SME Wanted Issues/PRs that benefit SME. Set a date to proceed if SME input does not come Source: Desk Issue originated from Support Ticket Topic: Code Structure Related to Upstreams and other code structure details Type: Fix Content Issue or PR to resolve incorrect information in the docs
Projects
None yet
Development

No branches or pull requests

1 participant