GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Window name targeting: which subtree to search is not interoperable · Issue #10848 · whatwg/html

Window name targeting: which subtree to search is not interoperable #10848

New issue
Copy link
New issue
Copy link
Open
Open
Window name targeting: which subtree to search is not interoperable#10848
Copy link
Labels
interopImplementations are not interoperable with each otherImplementations are not interoperable with each othertopic: frames/navigables/browsing contexts

Description

@domenic
domenic
opened on Dec 11, 2024
Issue body actions

What is the issue with the HTML Standard?

After #10818 merges, we will have an implementation-defined step which establishes subtreesToSearch in "find a navigable by target name".

@kjmcnee states:

WebKit and Chromium search the requesting window's subtree then search from the top. Firefox iterates and searches from each ancestor. If there's a way to express in the spec that the implementation-defined behavior is fixed for the instance of the user agent, then that'd be appropriate here.

We should probably standardize on the 2/3 behavior here, unless Gecko has a strong argument for why theirs is better. This issue tracks doing so.

The only hard part will be writing appropriate web platform tests. For inspiration on how to write such tests, you can see Kevin's web-platform-tests/wpt#49631 . We just need to establish a setup where the two strategies give different results and then assert the WebKit/Chromium behavior.

Activity

  1. domenic
    added
    interopImplementations are not interoperable with each otherImplementations are not interoperable with each other
    topic: frames/navigables/browsing contexts
    on Dec 11, 2024
  2. domenic
    added a commit that references this issue on Dec 12, 2024

    Make named window lookup more precise and correct BCG swap logic

    f23f559
  3. lozy219
    added a commit that references this issue on Mar 10, 2025

    Make named window lookup more precise and correct BCG swap logic

    b9a5344
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    interopImplementations are not interoperable with each otherImplementations are not interoperable with each othertopic: frames/navigables/browsing contexts

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.