Skip to content

Fail with InvalidStateError when the document is not fully active at call time - #557

Open
marcoscaceres wants to merge 1 commit into
w3c-fedid:mainfrom
marcoscaceres:eng/tag-non-fully-active-invalidstateerror
Open

Fail with InvalidStateError when the document is not fully active at call time#557
marcoscaceres wants to merge 1 commit into
w3c-fedid:mainfrom
marcoscaceres:eng/tag-non-fully-active-invalidstateerror

Conversation

@marcoscaceres

@marcoscaceres marcoscaceres commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Per the TAG design principle on non-fully-active documents (§2.13), an API invoked when its associated document is not fully active should fail immediately with an InvalidStateError, distinct from the NotAllowedError used when the document lacks user attention.

This adds that fully-active check to the get() and create() algorithms ahead of the existing check, leaving the focus/visibility rejection as NotAllowedError.


Preview | Diff

An API invoked when its associated document is not fully active should fail
immediately with InvalidStateError, distinct from the NotAllowedError used when
the document lacks user attention. Add the fully-active check to the get() and
create() algorithms ahead of the existing check.
@marcoscaceres
marcoscaceres requested a review from a team as a code owner July 20, 2026 04:39
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.

2 participants