Bryan Chen 15fc669eed
telemetry: report ResizeObserver delivery context (#328065)
* telemetry: report ResizeObserver delivery context

The browser's ResizeObserver loop ErrorEvent contains only a generic message; it does not expose the skipped target or causative callback. Prefixing that warning with the most recently invoked DisposableResizeObserver therefore turned callback order into false causal attribution.

Record the wrapped observers that ran in the current rendering frame instead. Context is scoped per window, deduplicated, sorted for stable bucketing, and bounded to the canonical smallest eight names plus an overflow marker. The telemetry prefix explicitly calls these recent wrapped observers rather than an offending consumer.

Clear context at the next animation frame, after Blink dispatches any loop warning from the current rendering update. Unit coverage locks deduplication, canonical overflow, window isolation, and frame cleanup; a real Chromium component fixture deliberately triggers a self-resize loop and verifies context survives until the native warning.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: aacd276e-cf84-48bd-a2ab-6f6a4d4c3431

* telemetry: shorten ResizeObserver context prefix

ResizeObserverLoopContext already identifies the observer names as non-causal context, so remove the redundant 
ecentWrappedObservers= label from the emitted error string.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: aacd276e-cf84-48bd-a2ab-6f6a4d4c3431

---------

Copilot-Session: aacd276e-cf84-48bd-a2ab-6f6a4d4c3431
2026-07-29 15:53:37 -07:00
..

VS Code Tests

Contents

This folder contains the various test runners for VS Code. Please refer to the documentation within for how to run them:

  • unit: our suite of unit tests (README)
  • integration: our suite of API tests (README)
  • smoke: our suite of automated UI tests (README)
  • sanity: release sanity tests (README)