Bug 231272
| Summary: | Cross origin Javascript dialogs (confirm(), prompt(), alert()) not working on iOS 15.0.1 | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | derrick.r.chao |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | cdumez |
| Priority: | P2 | ||
| Version: | Safari 15 | ||
| Hardware: | iPhone / iPad | ||
| OS: | macOS 10.15 | ||
derrick.r.chao
Hello, I have noticed that cross origin dialogs have stopped working for my apps running on Safari starting in iOS 15.0.1. The only mention I've found of this issue is in this random Salesforce helpdesk article: https://trailblazer.salesforce.com/issues_view?&Id=a1p4V000002RSkA
According to the article, this will be fixed in iOS 15.1 - can anyone from Apple please "confirm"? As developers should we be moving away from cross-origin JS dialogs? Thank you.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
We cannot confirm Apple release plans. This change was undone in WebKit in bug 229737, duping to that.
> As developers should we be moving away from cross-origin JS dialogs?
I don't think that it is entirely clear at this point. WebKit bug tracker is not the right place for getting such advice anyway, we keep it focused on tracking WebKit bugs and enhancement requests.
*** This bug has been marked as a duplicate of bug 229737 ***
Chris Dumez
(In reply to derrick.r.chao from comment #0)
> Hello, I have noticed that cross origin dialogs have stopped working for my
> apps running on Safari starting in iOS 15.0.1. The only mention I've found
> of this issue is in this random Salesforce helpdesk article:
> https://trailblazer.salesforce.com/issues_view?&Id=a1p4V000002RSkA
>
> According to the article, this will be fixed in iOS 15.1 - can anyone from
> Apple please "confirm"? As developers should we be moving away from
> cross-origin JS dialogs? Thank you.
Yes, I have confirmed that we have reverted the change in iOS 15.1 beta.
As Alexey said, it is unclear at this point if we'll try again or not. My understanding is that this change was not yet reverted from the HTML specification and that Chrome intends to try again.
derrick.r.chao
Thank you both.