Google's account widget and cookie rotation frames (accounts.google.com / ogs.google.com) on a signed-in Play Console no longer count as a sign-in page. Each detection logs its rule and URL; heartbeats name the page; a copied Chrome session that lands on a sign-in URL is said plainly; the sign-in wait gets a watchdog dump, and --debug-dump up to 3 dumps. Fixtures and tests for the chooser and home with the widget frames and a top-level accounts.google.com page; pitfall 16.
12 lines
687 B
HTML
12 lines
687 B
HTML
<!doctype html>
|
|
<!-- MODELED, not recorded: Google's sign-in page as a top-level page on accounts.google.com (where Play Console sends
|
|
a signed-out browser). storebound must detect it by its top-level URL, never type or click there. -->
|
|
<html lang="en"><head><meta charset="utf-8"><title>Sign in - Google Accounts</title><script src="/_common.js"></script></head>
|
|
<body>
|
|
<h1>Sign in</h1>
|
|
<p>to continue to Google Play Console</p>
|
|
<p><input id="identifier" type="email" aria-label="Email or phone"></p>
|
|
<a href="https://accounts.google.com/signin/v2/usernamerecovery">Forgot email?</a>
|
|
<button type="button">Create account</button>
|
|
<button type="button">Next</button>
|
|
</body></html>
|