Bug 278887
| Summary: | Safari refreshes document when WiFi is turned off then on multiple times. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrew Hodel <andrewhodel> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, beidson |
| Priority: | P2 | ||
| Version: | Safari 17 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 17 | ||
Andrew Hodel
iPadOS version 17.6.1
WebSocket attempts connection if not connected.
The Safari browser on iPad chooses to refresh the document if you disconnect and reconnect the WiFi network using the iPadOS menu to force the socket to close and the WebSocket `close` event to fire. (This is another bug, https://bugs.webkit.org/show_bug.cgi?id=278313)
It has done this after 3 disconnect and connect iterations.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Thank you for the report. Can you please share the link for testing?
Andrew Hodel
The website you shared for testing does not automatically reconnect and you need to test this while there is a disgraced network connection.
Andrew Hodel
It is more reasonable to search the code for the methods that can refresh the page during a network event.
Alexey Proskuryakov
This is almost certainly a WebContent process crash, not a "refresh", even though it looks this way to the user. And while it is (was?) definitely a bug in WebKit, we won't be able to do anything about it unless you provide steps to reproduce or at the very least a crash log.
Making as INVALID for now.
Andrew Hodel
Why don't you put a web console and element inspector in the iPad's Safari interface that can provide a log instead of requiring that it be connected via a cable to a MacOS system?
That would increase the probability of getting what you need to solve these complicated problems.