sendBeacon() integration
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
According to https://bugs.webkit.org/show_bug.cgi?id=177579 no browser implements this. This appears true in Chromium and WebKit.
- Load https://tests.caniuse.com/?feat=beacon.
- Once everything has loaded, run
performance.getEntriesByType("resource"). - Observe no "
beacon" entries in the result.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the caniuse test at https://tests.caniuse.com/?feat=beacon and running performance.getEntriesByType("resource") after loading. Read the Resource Timing specification's treatment of sendBeacon() and determine the required integration; done means the expected beacon resource is represented consistently with the specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100