@ai-ecoverse/slicc-cdp 1.41.3 → 1.41.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/bin/curlwright.wasm +0 -0
- package/bin/playwright-cli.wasm +0 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -125,7 +125,9 @@ The holder retains its observing CDP session. A `dialog-opened` event supplies `
|
|
|
125
125
|
|
|
126
126
|
### Input on background tabs
|
|
127
127
|
|
|
128
|
-
Headed Chrome doesn't deliver trusted input to a tab it isn't showing, and playwright-cli's tabs usually stay in the background next to seven's. So `click`, `dblclick`, `hover`, `type` and `press` check from an isolated world which events reached the page. If Chrome dropped them, the same events are dispatched in place to the element under the point, or to the focused element, without bringing the tab forward. The page then sees them with `isTrusted: false`: there is no user activation, `:hover` doesn't change, and `click` is dispatched just after the command returns, so a dialog it opens doesn't block it. `type` needs a focused editable element. `press` handles printable keys, `Enter`, `Escape`, `Backspace
|
|
128
|
+
Headed Chrome doesn't deliver trusted input to a tab it isn't showing, and playwright-cli's tabs usually stay in the background next to seven's. So `click`, `dblclick`, `hover`, `type` and `press` check from an isolated world which events reached the page. If Chrome dropped them, the same events are dispatched in place to the element under the point, or to the focused element, without bringing the tab forward. The page then sees them with `isTrusted: false`: there is no user activation, `:hover` doesn't change, and `click` is dispatched just after the command returns, so a dialog it opens doesn't block it. `type` needs a focused editable element. `press` handles printable keys, `Enter`, `Escape`, `Backspace`, `Delete` and the modifier keys in place.
|
|
129
|
+
|
|
130
|
+
`drag`, `mousemove`, `mousedown`, `mouseup`, `keydown` and `keyup` take the same path. A `drag` counts as arrived only when both its press and its release did; if only part of it arrived, it is finished in place from the first missing step. In place, the mouse commands dispatch pointer and mouse events with the held buttons and modifiers, `pointerover`/`pointerout` and `mouseenter`/`mouseleave` as the element under the pointer changes from the saved position, focus on `mousedown`, and on `mouseup` a `click` (`auxclick` for other buttons) on the nearest common ancestor of the element under the press point and the one under the release, just after the command returns. A `mouseup` after a `mousedown` that was dispatched in place is dispatched in place too, without Chrome's release, since Chrome never saw the press and would send no click. `drag` does that for its whole move, press, move and release. `keydown` dispatches only `keydown`, with `keypress` and the default action of `press`, and `keyup` only `keyup`. Modifier keys and `Escape` get no `keypress` and no default action. A key `press` can't handle, `keyup` of Space on a button or link, a `drag` from or to a ref inside a frame, and a point with no element take the front-and-back path below, the last without the arrival check, since no element is there to see it. Each refuses rather than reports success when it can't be brought forward.
|
|
129
131
|
|
|
130
132
|
Only when that can't work (another key, focus inside a frame, or nothing at the point) does it bring the tab to the front, send the input again, check that it arrived and switch back to the tab that was in front. The guard does the switching. It reads which tab is visible from isolated worlds of the ordinary tabs in the window, and switches back to seven's tab only when no ordinary tab there was visible and seven's is the one protected tab in that window. A tab alone in its window is brought forward with nothing to switch back. It refuses, so that no tab is activated, when the vault, another protected or unknown tab could have been in front, when a protected tab is in another window, or when the window is minimized. The error names `tab-select --foreground`. Input that still doesn't arrive fails with an error rather than reporting success.
|
|
131
133
|
|
package/bin/curlwright.wasm
CHANGED
|
Binary file
|
package/bin/playwright-cli.wasm
CHANGED
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ai-ecoverse/slicc-cdp",
|
|
3
|
-
"version": "1.41.
|
|
3
|
+
"version": "1.41.4",
|
|
4
4
|
"description": "SLICC's CDP layer: client, browser API, transports, HAR, and ARIA snapshot",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -69,7 +69,7 @@
|
|
|
69
69
|
},
|
|
70
70
|
"devDependencies": {
|
|
71
71
|
"@ai-ecoverse/slicc-browsers": "1.18.12",
|
|
72
|
-
"@ai-ecoverse/slicc-kernel": "1.
|
|
72
|
+
"@ai-ecoverse/slicc-kernel": "1.159.1",
|
|
73
73
|
"@ai-ecoverse/slicc-shared-web": "2.12.0",
|
|
74
74
|
"@ai-ecoverse/wasm-bash": "5.3.0-23",
|
|
75
75
|
"@ai-ecoverse/wasm-coreutils": "9.12.0-15",
|