Bug 263326
| Summary: | pagehide, visibilitychange, beforeunload ALL not working when navigating away or closing tab/app/window | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | yanstiac |
| Component: | History | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Major | CC: | beidson, karlcow, webkit-bug-importer |
| Priority: | P2 | Keywords: | BrowserCompat, InRadar |
| Version: | Safari 17 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
yanstiac
pagehide, visibilitychange, beforeunload ALL broken when navigating away or closing either the tab or window/app rendering navigator.sendBeacon useless
We need to get this sorted. More and more developers rely on live up-to-date analytics on user activity and knowing "when" a user has navigated away has to be by definition a major part of it.
pagehide, visibilitychange, beforeunload do not have any effect whenever the user navigates away (by inputting a new url, using back/forward, using favorites, closing current tab or window)
All other major browsers support this.
What is going on?
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/117486857>
Karl Dubost
Thanks for the report.
It would be cool if you had a minimal testcase, that the WebKit Team could work with.
Brady Eidson
> What is going on?
All of these events are implemented, and many dozens/hundreds (if not thousands) of automated regression tests demonstrate they're working as expected.
Karl asked for at least one reproducible test case here https://bugs.webkit.org/show_bug.cgi?id=263326#c2
If you could provide step-by-step instructions on what to look at, we can explore what's going on in that case!
Brady Eidson
(In reply to Brady Eidson from comment #3)
> > What is going on?
>
> All of these events are implemented, and many dozens/hundreds (if not
> thousands) of automated regression tests demonstrate they're working as
> expected.
>
> Karl asked for at least one reproducible test case here
> https://bugs.webkit.org/show_bug.cgi?id=263326#c2
>
> If you could provide step-by-step instructions on what to look at, we can
> explore what's going on in that case!
Gentle ping.
For the above stated reasons, there's little progress we can make here without a concrete example.
Karl Dubost
Without more information, we can't really do anything.
I'm closing the bug. If the issue was still happening. It would be great to have a test case to reproduce.
Thanks for the bug report.