[blink-dev] Intent to Prototype: Call stacks in crash reports from unresponsive web pages

Contact emails issackj...@microsoft.com, seth.bren...@microsoft.com Explainer https://github.com/WICG/crash-reporting/issues/12 Specification https://docs.google.com/document/d/19DpvHIiYbmB9wgIP0BdI4vOnfVLcAZFmfIAml7SqRQA/edit?u

Re: [blink-dev] Intent to Prototype: Call stacks in crash reports from unresponsive web pages

you are going to >>>> restrict this only to execution stacks in the main world? >>>> If you get an extension executing scripts in the main world how will >>>> you prevent the endpoint from knowing about the agent's execution >>>> environment s

[blink-dev] Ready for Developer Testing: Call stacks in crash reports from unresponsive web pages

Contact emails issackj...@microsoft.com, seth.bren...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/CrashReporting/AddStackToCrashReports.md https://github.com/WICG/crash-reporting/issues/12

[blink-dev] Intent to Experiment: Call stacks in crash reports from unresponsive web pages

Contact emails issackj...@microsoft.com, seth.bren...@microsoft.com Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/CrashReporting/AddStackToCrashReports.md https://github.com/WICG/crash-reporting/issues/12

Re: [blink-dev] Intent to Experiment: Call stacks in crash reports from unresponsive web pages

gt; Can you work on filing for TAG review, and asking other browsers for >> signals? >> > > I agree it's a good idea to file all these at this point, but they are not > a blocker for an initial OT request. (they would be for extensions, along > with spec work) >

Re: [blink-dev] Intent to Experiment: Call stacks in crash reports from unresponsive web pages

> Can you work on filing for TAG review, and asking other browsers for >>> signals? >>> >> >> I agree it's a good idea to file all these at this point, but they are >> not a blocker for an initial OT request. (they would be for extensions,

Re: [blink-dev] Intent to Experiment: Call stacks in crash reports from unresponsive web pages

s? >>>> >>> >>> I agree it's a good idea to file all these at this point, but they are >>> not a blocker for an initial OT request. (they would be for extensions, >>> along with spec work) >>> >>> >>>> >>>

Re: [blink-dev] Intent to Extend Experiment: Call stacks in crash reports from unresponsive web pages

Since the initial trial, we've made signification progress towards shipping: 1. We have included the feature in the Draft Spec for crash reporting. 2. The feature has completed a TAG review. 3. We've requested signals. We have received positive feedback fr

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

Thank you all for the reviews! :) On Tuesday, March 18, 2025 at 7:32:56 PM UTC-7 vmp...@chromium.org wrote: > LGTM3 > > On Tuesday, March 18, 2025 at 8:47:30 AM UTC-4 Mike Taylor wrote: > >> LGTM2 - I see that Mozilla has proposed a positive position via comment. >> On 3/17/25 2:25 PM, 'Dan Clar

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

; no obvious attempts to re-enable them. I only raise this because this means > there are no web platform tests, *and* no Chromium-specific browser > tests, so the feature is not tested at all. Maybe that shouldn't block the > I2S, but enabling the tests for good should be a priori

Re: [blink-dev] Re: Intent to Ship: Call stacks in crash reports from unresponsive web pages

e been "please fix the tests and come back and report." > > What is the downside to disabling until we're in that state? > On 3/27/25 4:57 PM, 'Issack John' via blink-dev wrote: > > Hi Dom and Mike, > > I have made multiple attempts to debug and resolve t

Re: [blink-dev] Re: Intent to Ship: Spec-compliant JSON MIME type detection

-default and using Finch as an emergency kill switch if something (very) unexpected happens. On Tue, May 20, 2025 at 5:32 AM 'Issack John' via blink-dev < blin...@chromium.org> wrote: We plan to deploy the feature as an enabled-by-default base::Feature, primarily to act as an e

[blink-dev] Intent to Ship: Spec-compliant JSON MIME type detection

Contact emails issackj...@microsoft.com, dan...@microsoft.com Explainer None Specification https://mimesniff.spec.whatwg.org/#json-mime-type Summary Chromium now recognizes all valid JSON MIME types as defined by the WHATWG mimesnif

[blink-dev] Re: Intent to Ship: Spec-compliant JSON MIME type detection

We plan to deploy the feature as an enabled-by-default base::Feature, primarily to act as an emergency shutoff valve rather than going through a formal feature rollout. This approach aligns with the consensus-based standards section, which doesn’t call for a gradual rollout, and given the low r