Skip to content

Conversation

@markafoltz
Copy link
Contributor

@markafoltz markafoltz commented Jan 18, 2023

See Issue #509 for background. This PR is intended to fix the current crop of ReSpec errors and warnings.

WhatWG HTML makes the following recommendation,

Modern specifications should avoid using the browsing context concept in most cases, unless they are dealing with the subtleties of browsing context group switches and agent cluster allocation. Instead, the Document and navigable concepts are usually more appropriate.

In the future we may want to update the spec to refer to current concepts like navigables and traversables, instead of browsing contexts. However that is out of scope for right now.


Preview | Diff

@markafoltz markafoltz requested a review from tidoust January 18, 2023 22:18
…ument"

The notion of "list of descendant browsing contexts" also needed to be replaced
by "descendant navigables". This was not reported by ReSpec because the previous
term was not exported by HTML so it was defined locally in the Terminology
section. Good news is "descendant navigables" is exported, so we can link to it
directly.

It seems a pity to lose the link to "unload a document" just because HTML no
longer export the term. This update adds it back as a local definition that
links to the (private for now) definition in HTML. We'll need to check that
list of terms at some point and exchange with HTML editors to see whether they
could export them, think we're doing something wrong, or think we should
continue with the current setting.
Copy link
Member

@tidoust tidoust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took the liberty to push an update. The "list of descendant browsing contexts" also needed to be replaced by "descendant navigables", which also has the benefit to be exported by the HTML spec.

Also, I think we should keep a link to the notion of "unload a document", even though the HTML spec no longer exports that notion, since it helps clarify what implementations should do.

@markafoltz
Copy link
Contributor Author

Thanks @tiidoust. This looks good to me.

@markafoltz markafoltz merged commit e7f2d4d into main Jan 19, 2023
@markafoltz markafoltz deleted the issue-509-fix-xref branch January 19, 2023 18:41
github-actions bot added a commit that referenced this pull request Jan 19, 2023
SHA: e7f2d4d
Reason: push, by mfoltzgoogle

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants