Replace uses of "browsing contexts" with "navigables"? #325
Comments
tidoust
added a commit
that referenced
this issue
Apr 17, 2024
The spec re-defined the `<link>` element with an incorrect fragment. This update uses Bikeshed's "link defaults" mechanism instead to fix the broken link. This would close #324. The spec also re-defined a couple of terms that did not need to be re-defined (since the HTML spec already exports them). Links to Media Capture and Streams also needed fixing. These issues were reported by Bikeshed during build as warnings. One problem remains: the reference to "nested browsing contexts" is invalid, see #325.
marcoscaceres
pushed a commit
that referenced
this issue
May 13, 2024
The spec re-defined the `<link>` element with an incorrect fragment. This update uses Bikeshed's "link defaults" mechanism instead to fix the broken link. This would close #324. The spec also re-defined a couple of terms that did not need to be re-defined (since the HTML spec already exports them). Links to Media Capture and Streams also needed fixing. These issues were reported by Bikeshed during build as warnings. One problem remains: the reference to "nested browsing contexts" is invalid, see #325.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The spec talks about (and tries to reference) "nested browsing contexts". That concept no longer exists in HTML. The HTML spec actually notes that specifications should avoid using the "browsing context" concept in most cases, and should rather use navigable (and child navigables for what used to be "nested browsing contexts").
Or is there a real need to use the "browsing context"?
Regardless, "nested browsing contexts" should disappear.
The text was updated successfully, but these errors were encountered: