This should only be done if T507 shows that CORS fetches work reliably for the overwhelming majority of users.
If this turns out to be problematic, T513 could be an alternative.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T106915 Use Sentry in production | |||
| Declined | Tgr | T91649 Deploy Sentry (JavaScript error logging) to production, configured to log only a limited subset of users/pages | |||
| Resolved | • jlinehan | T88399 Improve Javascript error logging coverage | |||
| Declined | None | T382 RfC: Server-side Javascript error logging | |||
| Open | None | T508 Use CORS-enabled fetch of scripts to avoid same-domain limitations in JS error logging | |||
| Resolved | Tgr | T507 Measure how many users have CORS-hostile proxies |
At the time of creating this task it was assumed that the server side implementation of error logging would be based on Sentry. We have eventually decided on a different implementation, so de-tagging.
This open task has no active project tags so it will not be found. Adding vague WMF-General-or-Unknown, please feel welcome to add a more specific tag.