Repository navigation
Release PaddockJS 4.4.0 - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release PaddockJS 4.4.0 with cooperative browser startup and stable Grid Walk framing. Track preparation and expensive drawing loops yield to input/painting while preserving automatic startup, cancellation, cleanup and existing APIs. Add optional
gridWalk.initialPosition: 'start-line'for right/top alignment and retain selected-entry centering by default.Also includes the v12 lifecycle, participant-reset, timing-crossing and canvas-color fixes. Version manifests, lockfiles, Changesets output, changelog and host migration notes are synchronized.
Validation: 1,568 exhaustive tests passed; full Chromium and demo smoke, runtime benchmark and isolated portfolio integration passed. Clean install, public types, dry pack, fresh packed-consumer build and subpath boundaries passed for 4.4.0. Local profiling reduced the longest startup task from 597–627 ms to 62–71 ms, with about 0.3–0.4 s more elapsed initialization time. See
docs/browser_startup.mdfor methodology.Two environment assertions failed once in an initial exhaustive run; repeated baseline/candidate files and the exhaustive rerun passed without weakening tests. Retained in the Linear work log as a follow-up.