Repository navigation
v0.4.0
Minor Changes
-
3f0b64f: A login may now pass through an identity provider, and a diagnostic switch can show whether the mark after a login matters. Neither was in 0.3.0, so a worker built from it refuses a login that leaves the app's origin with
left-originbefore NVDA is started.auth.idpOriginsis a new optional request field: a list of exact origins (scheme, host and port, no path, query, fragment or credential, and no wildcard) that the login steps, and only those, may navigate through. The list is normalised toURL.originand de-duplicated. An entry that is not an origin, or is the app's own origin, is refused withauth.idpOrigins entry <n> …and never echoed back, since a request may have put a credential in it. Absent means none, and the plan keeps its old shape. An origin that is not listed still ends the captureleft-origin, and so does any origin after the login, in theflowsteps.- The window is marked navigated after a login even when the requested page is not loaded again. A login that ends on the requested page used to skip the reload, so the mark NVDA needs to re-read its buffer was never made. It is now made once the sign-in has finished.
A11Y_DIAG_SKIP_LOGIN_MARK=1is a diagnostic-only switch in the worker process's environment (not in a request): the login then does not mark the window, and the capture's record carriesloginMarkSuppressed. Only the exact value1turns it on, and it is read at each capture; unset, empty,0or anything else changes nothing. No request field, CLI flag or Action input can set it. A capture taken with it set is not a product reading.