Files
fn_registry/functions/browser/cdp_wait_load.md
T
egutierrez d7f2c00d7b feat: externalize apps/analysis to Gitea repos, add analysis table
- Migration 007: repo_url on apps table + analysis table with FTS5
- Analysis struct, parser, CRUD, validation, hash computation
- Selective purge: remote-only apps/analysis preserved across fn index
- CLI: fn app list/clone/pull, fn analysis list/clone/pull
- search/show/list now include analysis results
- Apps removed from git tracking (content lives in Gitea repos)
- .gitkeep for apps/ and analysis/ dirs
- Bash functions: jupyter analysis pipeline, shell utilities
- Browser domain: CDP functions moved from infra to browser

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-01 04:23:51 +02:00

1.5 KiB

name, kind, lang, domain, version, purity, signature, description, tags, uses_functions, uses_types, returns, returns_optional, error_type, imports, tested, tests, test_file_path, file_path
name kind lang domain version purity signature description tags uses_functions uses_types returns returns_optional error_type imports tested tests test_file_path file_path
cdp_wait_load function go browser 1.0.0 impure func CdpWaitLoad(c *CDPConn, timeout time.Duration) error Espera a que la pagina actual termine de cargar completamente. Hace polling de document.readyState via Runtime.evaluate cada 200ms hasta que sea "complete", o hasta que se agote el timeout. Retorna error inmediato si CdpEvaluate falla (la conexion puede estar rota).
chrome
cdp
browser
automation
wait
polling
devtools
readystate
load
cdp_evaluate_go_browser
false error_go_core
fmt
time
false
functions/infra/cdp_wait_load.go

Ejemplo

conn, _ := CdpConnect(9222)
CdpNavigate(conn, "https://example.com")

// Esperar hasta 30 segundos a que la pagina cargue por completo
if err := CdpWaitLoad(conn, 30*time.Second); err != nil {
    log.Fatal("Timeout esperando carga:", err)
}

html, _ := CdpGetHTML(conn)

Notas

A diferencia de CdpWaitElement, que ignora errores de CdpEvaluate durante el polling (la pagina puede aun no estar lista), CdpWaitLoad retorna el error inmediatamente porque un fallo en document.readyState indica una conexion rota, no una condicion transitoria.

Si timeout <= 0 usa 30s por defecto (mas largo que CdpWaitElement porque la carga completa de red puede tardar mas que la aparicion de un elemento DOM).