Inspect and debug browser pages from an Ace channel
Ein zugehöriger Pull Request wurde bereits gemerged.
- #163 von @iamnbutler — gemerged
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 42/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- developer-experience
Rechercherichtung
Start with docs/browser-tools.md (documented by merged PR #163, commit 8ae23e4) and the implementations of browser_tabs, browser_navigate, and browser_inspect to learn the channel/host boundary and how tools return through the history path. Then pick one unchecked acceptance item — DOM input with element references, console/network inspection, or managed browser launch/lifecycle — since each is a self-contained slice. Done means the new tool behaves like #163's: bounded text/images, honest failure messages, no replay after interruption, and a walkthrough from a native Ace channel.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Ace development used browser DOM/accessibility snapshots, interaction, screenshots, uploads, console/network inspection, and responsive checks. githubnext/desktop-tools#11 explicitly covers native browser Accessibility/pixels; DOM/browser-session integration needs its own capability.
Acceptance
- Select an explicit browser and tab on the execution host; navigate, inspect DOM/accessibility, interact, and capture screenshots. #163: exact tab selection, navigation, main-frame accessibility and viewport screenshots landed. Remaining: DOM input (click, fill, keys) with element references, DOM inspection, and iframe content.
- Inspect console errors and failed network requests; support file upload, viewport changes, and mobile/touch emulation used in the reviewed work. Remaining.
- Keep the browser target identifiable across reconnects. Local and hosted execution must target the execution machine, not the viewing client. #163: exact browser-instance and tab targets, execution-machine routing for local workers and workspace
Link/serve, and refusal of replaced browsers. Remaining: managed launch and lifecycle of the dedicated browser, and a deployed hosted-object check. - Return bounded text/images and actionable failures through the existing channel tool/history path. Done for githubnext/ace#163's tools; required for each remaining capability.
- From a native Ace channel, reproduce a real web UI defect, inspect its cause, fix its lane, and verify the result with retained evidence. Remaining.
Use an appropriate browser backend; external harness integration is not required. Follow the existing channel/host boundary, pi history ownership, and collaborator-agent switch.
Status
First slice landed in githubnext/ace#163 (8ae23e4, documented in docs/browser-tools.md): browser_tabs, browser_navigate and browser_inspect for Ace's dedicated loopback browser, with honest navigation outcomes and no replay after interruption. GitHub closed this issue automatically when githubnext/ace#163 merged because the PR was linked as closing it; githubnext/ace#163 itself says it doesn't close githubnext/ace#50, and the acceptance above isn't met. The Browser Preview tab is the separate channel preview surface in githubnext/ace#16.
Dogfooding MVP: githubnext/ace#5. Related: githubnext/desktop-tools#11, githubnext/ace#16. Review evidence.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Kein Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus githubnext/ace2
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 94/100
githubnext/ace2#487 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 90/100
githubnext/ace2#486 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 67/100
githubnext/ace2#459 ·
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
githubnext/ace2#437 ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
githubnext/ace2#442 ·
Alle Issues in githubnext/ace2
Ähnliche Issues
-
The inspector never shows the instances field, so scaling out is unreachableEvtl. vergeben @Mrkewl hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
xevrion/breakscale#96 ·
Maintainer antworten meist innerhalb von 4 Tagen
-
Object parameters lose their structure when resources is enabledEvtl. vergeben @asts-top hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
rossant/awesome-math#199 ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
jaegertracing/jaeger-ui#4618 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
mifi/lossless-cut#3125 ·
Maintainer antworten meist innerhalb von 1 Tag