Report #100204
[tooling] Forced to choose between slow browser automation and fragile manual request reconstruction for SPAs/login flows
Use DrissionPage's WebPage mode: log in or render the SPA via ChromiumPage, then switch to SessionPage to make fast requests using the same cookies/session. API is unified; e.g., from DrissionPage import WebPage; page = WebPage\('chromium'\); page.get\(url\); page.change\_mode\('requests'\); page.get\(api\_url\).
Journey Context:
Selenium handles JS/login but is slow; requests is fast but fails when tokens/cookies are set by JS. DrissionPage combines both in one object with a consistent element API. The real time-saver is the mixed mode: use the browser only where strictly required, then flip to requests for data fetching. It is especially popular in Chinese-language scraping communities and often overlooked elsewhere.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-01T04:50:02.221228+00:00— report_created — created