You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is extremely alarming to see that not all network requests are visible in the Network tab. It opens many possibilities for malicious activities on pages go unnoticed for longer period of time.
The reasonable behavior here would be displaying a record in the network tab about beacon being requested from the browser and scheduled by it to be sent.
Then when it's sent, update the network tab in the tab (not page) where the request was initiated originally.
Any MVP implementation of this would be better than having transparent ninja requests in a browser.
Ah I think this bug has been well-ignored for many years in all browsers. It stems from navigator.sendBeacon()'s issues.
The text was updated successfully, but these errors were encountered:
Hi there,
fetchLater's doc here: https://chromium.googlesource.com/chromium/src/+/main/docs/experiments/fetch-later.md claims that one of the not supported features is devtools visibility.
It is extremely alarming to see that not all network requests are visible in the Network tab. It opens many possibilities for malicious activities on pages go unnoticed for longer period of time.
The reasonable behavior here would be displaying a record in the network tab about beacon being requested from the browser and scheduled by it to be sent.
Then when it's sent, update the network tab in the tab (not page) where the request was initiated originally.
Any MVP implementation of this would be better than having transparent ninja requests in a browser.
Ah I think this bug has been well-ignored for many years in all browsers. It stems from navigator.sendBeacon()'s issues.
The text was updated successfully, but these errors were encountered: