Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Inspect and debug browser pages from an Ace channel

Ouverte
  • Quelque chose ne va pas ?
#50 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Une pull request liée a déjà été fusionnée.

  • #163 par @iamnbutler — fusionnée

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
developer-experience

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
1
Forks
0
Aucune PR mergée en 30 j

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/ace2

Toutes les issues de githubnext/ace2

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.