Skip to content

Conversation

@danielhjacobs
Copy link
Contributor

We have now reached territory of how much we value compatibility over code complexity. This mimics behavior defined in https://html.spec.whatwg.org/multipage/nav-history-apis.html#named-access-on-the-window-object. I designed this to see how complex it would make the code. The answer, as it turns out, is fairly.

embed, form, img, or object elements that have a name content attribute whose value is name and are in a document tree with window's associated Document as their root;

See also #22442

@danielhjacobs danielhjacobs added A-web Area: Web & Extensions T-compat Type: Compatibility with Flash Player labels Dec 9, 2025
@danielhjacobs danielhjacobs force-pushed the support-polyfill-named-access-on-document branch from c4356d9 to b936679 Compare December 10, 2025 15:49
@danielhjacobs danielhjacobs force-pushed the support-polyfill-named-access-on-document branch from b936679 to 6a388ed Compare December 10, 2025 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-web Area: Web & Extensions T-compat Type: Compatibility with Flash Player

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant