LGTM3
/Daniel
On 2025-06-18 17:16, Mike Taylor wrote:
LGTM2
On 6/18/25 10:58 AM, Yoav Weiss (@Shopify) wrote:
LGTM1
On Monday, June 16, 2025 at 6:25:02 AM UTC+2 Chromestatus wrote:
Contact emails
zhoupeng.1...@bytedance.com
Explainer
https://github.com/w3c/reporting/issues/263
<https://github.com/w3c/reporting/issues/263>
https://github.com/WICG/crash-reporting/issues/24
<https://github.com/WICG/crash-reporting/issues/24>
https://github.com/WICG/crash-reporting/pull/30
<https://github.com/WICG/crash-reporting/pull/30>
Specification
https://wicg.github.io/crash-reporting/#crash-reports-delivery-priority
<https://wicg.github.io/crash-reporting/#crash-reports-delivery-priority>
Design docs
https://github.com/WICG/crash-reporting/pull/30
<https://github.com/WICG/crash-reporting/pull/30>
Summary
This feature ensures developers receive only crash reports by
specifying the endpoint named `crash-reporting `. By default,
crash reports are delivered to the `default` endpoint which
receives many other kinds of reports besides crash reports.
Developers can supply a separate URL to the well-known endpoint
named `crash-reporting`, to direct crash reports there, instead
of the `default` endpoint. See
https://wicg.github.io/crash-reporting/#crash-reports-delivery-priority
<https://wicg.github.io/crash-reporting/#crash-reports-delivery-priority>.
Blink component
Blink
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%22>
TAG review
As this feature is a trivial API addition with no impact on
default behavior, the TAG Specification Review is unnecessary.
TAG review status
Not applicable
Risks
Interoperability and Compatibility
None
/Gecko/: Positive
(https://github.com/mozilla/standards-positions/issues/288#issuecomment-2944953563
<https://github.com/mozilla/standards-positions/issues/288#issuecomment-2944953563>)
/WebKit/: No signal
(https://github.com/WebKit/standards-positions/issues/456#issuecomment-2944940233
<https://github.com/WebKit/standards-positions/issues/456#issuecomment-2944940233>)
/Web developers/: Positive
(https://github.com/w3c/reporting/issues/263
<https://github.com/w3c/reporting/issues/263>)
/Other signals/:
Security
This feature only adds a way to report crash reports exclusively.
Therefore, we believe there are no security concerns.
WebView application risks
Does this intent deprecate or change behavior of existing APIs,
such that it has potentially high risk for Android WebView-based
applications?
None
Debuggability
None
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android
WebView)?
Yes
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
No
There are no web platform tests for this tiny addition to the
crash reporting API, because the crash reporting API itself
cannot be tested this way at the moment. WPTs do not support
crashing the renderer process for a contrived set of reasons
(OOM, unresponsiveness, etc). Note that this has been documented
in all of the other parts of this API that have shipped. See
https://groups.google.com/a/chromium.org/g/blink-dev/c/tgRcEnqIb1A
<https://groups.google.com/a/chromium.org/g/blink-dev/c/tgRcEnqIb1A>,
for example.
Flag name on about://flags
None
Finch feature name
OverrideCrashReportingEndpoint
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/414723480
<https://issues.chromium.org/issues/414723480>
Estimated milestones
Shipping on desktop 139
Shipping on Android 139
Shipping on WebView 139
Anticipated spec changes
Open questions about a feature may be a source of future web
compat or interop issues. Please list open issues (e.g. links to
known github issues in the project for the feature specification)
whose resolution may introduce web compat/interop risk (e.g.,
changing to naming or structure of the API in a
non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5129218731802624?gate=5083702916546560
<https://chromestatus.com/feature/5129218731802624?gate=5083702916546560>
Links to previous Intent discussions
Intent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68408874.170a0220.190b19.0101.GAE%40google.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68408874.170a0220.190b19.0101.GAE%40google.com>
This intent message was generated by Chrome Platform Status
<https://chromestatus.com>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f792ad6a-0654-4da6-be18-c2680a170bcbn%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f792ad6a-0654-4da6-be18-c2680a170bcbn%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bcdb72d8-20be-477f-90a3-0777b53ca891%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/bcdb72d8-20be-477f-90a3-0777b53ca891%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dfc5896a-d21f-4ff9-b4f0-905a4b445b03%40gmail.com.
