You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Ports/JavaScriptPort/STATUS.md
+21-5Lines changed: 21 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ Current State
16
16
-`TOP_BLOCKER=none|none|none`
17
17
- The screenshot pipeline now decodes/report-generates reliably from logs, but screenshot content is still mostly wrong (white-frame capture path is still being used in CI artifacts).
18
18
- New patch (not yet CI-validated in this document revision): worker-side fallback screenshot path now waits for a host-side UI-settle barrier before ready-callback dispatch and before canvas capture, to avoid pre-paint frame capture.
19
+
- New patch (not yet CI-validated in this document revision): `BaseTest.registerReadyCallback` fallback now attempts to force-show the target `Form` before UI-settle/callback dispatch to avoid running screenshot setup against a stale previous form.
19
20
20
21
What Was Fixed In This Pass
21
22
---------------------------
@@ -86,6 +87,18 @@ What Was Fixed In This Pass
86
87
- Motivation:
87
88
- CI showed near-identical screenshot payloads (same hash/size) indicating repeated capture of a stale frame rather than per-test painted UI.
88
89
90
+
8. Added force-show step in ready-callback fallback for per-test form activation.
91
+
- File:
92
+
-`Ports/JavaScriptPort/src/main/webapp/port.js`
93
+
- Changes:
94
+
- In `BaseTest.registerReadyCallbackImmediate`, attempt `Form.show()` before UI-settle and callback execution.
- CI diagnostics showed canvas signature locking to a single frame after initial tests, consistent with callbacks running while stale form remains active.
101
+
89
102
Known Failing Symptoms (Latest CI Logs/Artifacts)
90
103
-------------------------------------------------
91
104
@@ -110,11 +123,14 @@ Priority Next Steps
110
123
1. Validate CI output after UI-settle barrier:
111
124
- Expect non-identical PNG hashes for distinct tests.
112
125
- Confirm `settleChanged` and `canvasSig` diagnostics vary across tests.
113
-
2. If white-frame reuse persists, capture and compare per-test `settleSig`/`canvasSig` to identify whether paint is not happening or capture target is wrong.
114
-
3. Fix per-test null receiver/init path (`__classDef` null) at first failing stack, not via broad fallbacks.
115
-
4. Fix missing `Button.initLaf(UIManager)` symbol resolution in worker runtime path.
116
-
5. Fix worker-mode orientation lock path so DOM access is host-bridge mediated (no direct `document` access in worker).
117
-
6. Confirm VM completeness stability in CI with parser/runtime patches (`expected 7` consistently).
126
+
2. Validate force-show diagnostics in CI:
127
+
- Expect `forceShow=1` for screenshot tests with forms.
128
+
- Expect per-test `canvasSig` to vary for graphics tests if activation works.
129
+
3. If white-frame reuse persists, capture and compare per-test `settleSig`/`canvasSig` to identify whether paint is not happening or capture target is wrong.
130
+
4. Fix per-test null receiver/init path (`__classDef` null) at first failing stack, not via broad fallbacks.
131
+
5. Fix missing `Button.initLaf(UIManager)` symbol resolution in worker runtime path.
132
+
6. Fix worker-mode orientation lock path so DOM access is host-bridge mediated (no direct `document` access in worker).
133
+
7. Confirm VM completeness stability in CI with parser/runtime patches (`expected 7` consistently).
0 commit comments