Skip to content

Issues: whatwg/html

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
26 Open 97 Closed
26 Open 97 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Fire a load event for javascript: URL non-strings topic: frames/navigables/browsing contexts topic: javascript: URLs topic: navigation
#10957 opened Jan 28, 2025 by zcorpan Loading…
4 of 6 tasks
1
10
Navigate a navigable should probably use "matches about:srcdoc" clarification Standard could be clearer topic: frames/navigables/browsing contexts topic: navigation
#10900 opened Jan 7, 2025 by AtkinsSJ
1
Window name targeting: tie-breaking for same-named top-level traversables is not interoperable interop Implementations are not interoperable with each other topic: frames/navigables/browsing contexts
#10850 opened Dec 11, 2024 by domenic
Window name targeting: checking "allowed by sandboxing to navigate" is not interoperable interop Implementations are not interoperable with each other topic: frames/navigables/browsing contexts
#10849 opened Dec 11, 2024 by domenic
Window name targeting: which subtree to search is not interoperable interop Implementations are not interoperable with each other topic: frames/navigables/browsing contexts
#10848 opened Dec 11, 2024 by domenic
Force a browsing context group swap when navigating to and from file: URLs topic: frames/navigables/browsing contexts
#10842 opened Dec 10, 2024 by annevk
"check if an access between two browsing contexts should be reported" can be called with null browsing context but doesn't handle it topic: frames/navigables/browsing contexts
#10192 opened Mar 10, 2024 by awesomekling
1
Support for rel attribute on iframe addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: frames/navigables/browsing contexts
#8682 opened Jan 5, 2023 by 0xdevwrite
1
Regression: window.name should not be on navigable topic: cross-origin-opener-policy Issues and ideas around the new "inverse of rel=noopener" header topic: frames/navigables/browsing contexts
#8563 opened Nov 30, 2022 by annevk
@domenic @domfarolino
8
URL-bar triggered prerendering addition/proposal New features or enhancements topic: frames/navigables/browsing contexts topic: navigation
#7533 opened Jan 25, 2022 by domenic
3
Audit auxiliary browsing context checks topic: frames/navigables/browsing contexts
#5680 opened Jun 25, 2020 by annevk
1
Browsing context hierarchy needs to go through the embedding document topic: frames/navigables/browsing contexts topic: history
#5020 opened Oct 18, 2019 by annevk
6
load event handling for iframes with no src may not be web compatible compat Standard is not web compatible or proprietary feature needs standardizing topic: frames/navigables/browsing contexts
#4965 opened Oct 3, 2019 by bzbarsky
19
Initializing Feature Policy is racy integration Better coordination across standards needed topic: frames/navigables/browsing contexts topic: navigation
#4783 opened Jul 17, 2019 by dtapuska
2
Allow leeway when choosing hyperlink targets in special contexts topic: frames/navigables/browsing contexts topic: hyperlink
#4755 opened Jul 5, 2019 by daogottwald
2
Need to specify <style> only works on browsing-context-having documents topic: frames/navigables/browsing contexts topic: style
#4547 opened Apr 20, 2019 by domenic
7
window.close() during unload or beforeunload interop Implementations are not interoperable with each other topic: frames/navigables/browsing contexts
#4466 opened Mar 29, 2019 by domenic
window.opener can be cleared needs concrete proposal Moving the issue forward requires someone to figure out a detailed plan topic: frames/navigables/browsing contexts
#4429 opened Mar 12, 2019 by annevk
5
WindowProxy/Location and agent clusters topic: agent The interaction with JavaScript's agent and agent cluster concepts topic: event loop topic: frames/navigables/browsing contexts
#4390 opened Feb 24, 2019 by annevk
2
Add a pretty diagram for the references in "Garbage collection and browsing contexts" clarification Standard could be clearer topic: frames/navigables/browsing contexts
#3863 opened Jul 30, 2018 by domenic
6
Should "familiar with" use same origin or same origin-domain? interop Implementations are not interoperable with each other needs tests Moving the issue forward requires someone to write tests security/privacy There are security or privacy implications topic: frames/navigables/browsing contexts topic: navigation
#3747 opened Jun 8, 2018 by annevk
9
Enabling service workers when opener is not a secure context topic: frames/navigables/browsing contexts topic: navigation
#2687 opened May 16, 2017 by annevk
1
Allow chrome-initiated toplevel navigations to isolate browsing context topic: frames/navigables/browsing contexts topic: navigation
#2635 opened May 5, 2017 by mystor
6
Does the "script-closable" definition match reality? compat Standard is not web compatible or proprietary feature needs standardizing topic: frames/navigables/browsing contexts
#1866 opened Oct 5, 2016 by bzbarsky
6
Cause <a rel="noopener" target="_top"> navigations to create a new browsing context addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest topic: frames/navigables/browsing contexts topic: navigation
#1515 opened Jul 7, 2016 by mystor
3
ProTip! Find all open issues with in progress development work with linked:pr.