Skip to content

fix: treat empty tab URL as debuggable (fixes first-run failure)#259

Merged
jackwener merged 1 commit intomainfrom
fix/empty-url-debuggable
Mar 22, 2026
Merged

fix: treat empty tab URL as debuggable (fixes first-run failure)#259
jackwener merged 1 commit intomainfrom
fix/empty-url-debuggable

Conversation

@jackwener
Copy link
Owner

First-run doctor --live fails because new tab URL is empty while loading. isDebuggableUrl('') was returning false. Now only rejects known non-debuggable URLs (chrome://, chrome-extension://).

Version bump to 1.2.5.

… failure)

When a new automation window is created, the initial tab URL may be
empty briefly while Chrome loads the data: URI. isDebuggableUrl('') was
returning false, causing ensureAttached to reject the tab.

Fix: only reject known non-debuggable URLs (chrome://, chrome-extension://).
Empty/undefined URLs are now treated as debuggable since they represent
tabs still loading.

Also adds 200ms delay after window creation to let Chrome populate the
tab URL.
@jackwener jackwener merged commit 7f57e76 into main Mar 22, 2026
@jackwener jackwener deleted the fix/empty-url-debuggable branch March 22, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant