- From: Nick Doty <notifications@github.com>
- Date: Thu, 27 Apr 2023 15:15:22 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 27 April 2023 22:15:27 UTC
Just a +1 for including some explanation of how or why this would benefit users. It seems like the implicit reasoning here (as with previous Beacon APIs) is that websites want to send potentially large amounts of data particularly when a user navigates away from a page. Doing this in the background perhaps makes current abusive behavior (attempts to block navigation altogether until the data is sent) less annoying. But as a side effect, it means that the network traffic happens when the user is doing something else. The page that collected and sent the traffic is more opaque to the user, and any slowdowns that happen won't be attributed back to the page causing them, so more pages may feel comfortable collecting and sending more data. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/776#issuecomment-1526609159 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/776/1526609159@github.com>
Received on Thursday, 27 April 2023 22:15:27 UTC