Repository navigation
Group fresh locator reads on macOS ARM and point the dialog trial at beta - #20
Merged
Merged
Conversation
PerchAnton
changed the title
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.
Why the third macOS job blocked
In the original job, T05.restore.001.unchanged recorded a 106.5 ms gap. The host reading took 106.87 ms. The browser clock shows 102.6 ms between the previous observation and the first of ten new callbacks. Callback bodies each took at most 0.2 ms. The evidence does not isolate an OS scheduler or transport fault.
Changes
Group eligible declared target locators during manual-tab windows with a Playwright union. The three-tab fixture uses four fresh queries per subsequent reading instead of ten. Original locators still execute on every reading. Unexpected matches, changed IDs, structure changes and ambiguity fall back to individual queries. The two gap controls delay an essential role query in both paths. The 100 ms threshold, zero retries and the three macOS 15 ARM allocations remain in force.
The README also links to the published beta, its React example and its source-bound validation record. This development change is separate from the published beta qualification.
Local verification
Build, TypeScript checks, 65 unit/script checks and ten focused Chromium tests passed. The vertical manual Home/End case recorded four calls per measured interval. The delay controls blocked at 160.6 and 164.5 ms before activation. Three new cases cover extra matches, a rebound locator and swapped DOM IDs.