Skip to content

Editorial: fix COOP argument, variable, and link mix-ups - #13026

Open
shannonbooth wants to merge 5 commits into
whatwg:mainfrom
shannonbooth:coop-args
Open

shannonbooth wants to merge 5 commits into
whatwg:mainfrom
shannonbooth:coop-args

Conversation

@shannonbooth

@shannonbooth shannonbooth commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

While implementing COOP, I ran into "enforce a response's opener policy" not passing "check if COOP values require a browsing context group switch" in an order that matches its declaration. Reviewing that fix with AI turned up a few more issues nearby, which this fixes too.

Changes:

  • fix COOP group switch check argument order
  • fix undefined variable in report-only COOP check
  • fix type confusion in popup COOP check
  • fix link to access to another window COOP report
  • fix COOP access from an opened window report body

Reporting integration seems to have some further problems (some normative?), but I've tried keeping this to editorial fixes.


/browsers.html ( diff )

"Check if enforcing report-only COOP would require a browsing context
group switch" referred to activeDocumentCOOPReportOnly, but its
parameter is named activeDocumentCOOP.
activeDocumentCOOPValue is already an opener policy value, so it has
no value of its own.
"Queue violation reports for accesses" linked to "queue a violation
report for access to an opened window" when neither window opened the
other, although the text and arguments are those of "queue a violation
report for access to another window".
"Queue a violation report for access from an opened window" set
effectivePolicy to an undefined coopValue and property to the report-only
value. Use the report-only value and propertyName respectively, as the
other access reports do.
@shannonbooth shannonbooth reopened this Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant