Editorial: Use the right "active document" definition in a focus algorithm #9498
Conversation
There was a problem hiding this comment.
Nice find, thanks!
Can you make your membership in the Intel GitHub organization public, to appease the IPR bots? See https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership for more.
rakuco
force-pushed
the
editorial-reference-the-right-active-document-dfn
branch
from
e983f09
to
023ceb6
Compare
Whoa, I didn't know my membership was private in a bunch of organizations! In any case, looking at the new failure I seem to be signed up to work on other WHATWG specs like WebIDL but not HTML :( I'll try to solve this internally (and it will probably take a long time) and will get back here once everything's done. |
…rithm The "currently focused area of a top-level traversable" algorithm was referencing the "active document" associated with a browsing context rather than the one associated with a navigable.
rakuco
force-pushed
the
editorial-reference-the-right-active-document-dfn
branch
from
023ceb6
to
1ce008f
Compare
|
@domenic I've finally been added to the right group. The pull request is ready to land at last! |
The "currently focused area of a top-level traversable" algorithm was referencing the "active document" associated with a browsing context rather than the one associated with a navigable.
/interaction.html ( diff )