Skip to content

Keep captured Performance methods on one timeline - #130

Closed
wieslawsoltes wants to merge 3 commits into
review/code-oss-performance-method-basefrom
fix/performance-method-timeline
Closed

wieslawsoltes wants to merge 3 commits into
review/code-oss-performance-method-basefrom
fix/performance-method-timeline

Conversation

@wieslawsoltes

@wieslawsoltes wieslawsoltes commented Sep 16, 2026 •

Copy link
Copy Markdown
Collaborator

Problem and change

A captured early performance.mark method and the current performance.measure method could observe different stores, causing a same-turn Code OSS User Timing failure.

This change routes captured and current methods through one retained realm timeline, then hydrates the iframe before the focused Performance probe and waits for that realm deterministically. Coverage includes main/iframe method identity, bounded 50,000-mark behavior, and missing-mark regressions. The focused range is three directly related commits across seven files.

Closes #83. Equivalent commits are already in draft consolidation PR #76. This PR targets its recorded pre-fix review base for isolated validation and must remain open; do not merge it to main.

@wieslawsoltes

Copy link
Copy Markdown
Collaborator Author

Closing this older isolated review as superseded by merged native Stack #159. PR #134 carries the corrected retained Performance timeline behavior and focused 50,000-mark/missing-mark coverage on current main; #134/#135/#136 merged atomically at 5a133110a74ef6066d716ec8d61d9abe52051cdf, and issue #83 is closed. Keeping #130 open would duplicate the merged implementation on an obsolete review base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant