Audit auxiliary browsing context checks · Issue #5680 · whatwg/html (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Models New Manage and compare prompts
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Based on code inspection it seems that Chrome (not shipped) and Safari perform browsing context name resetting based on whether the top-level browsing context has an opener, not on whether it is auxiliary. These are distinct as a non-auxiliary top-level browsing context can still get an opener by being name targeted.

Nika told me that Firefox does have a concept of an initial opener so there might well be some valid uses of auxiliary browsing context.

It seems the one other use of this distinction is #313 due to "familiar with".