这是indexloc提供的服务，不要输入任何密码
Skip to content

Export fenced navigable #190

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

Merged
merged 1 commit into from
Sep 12, 2024
Merged

Export fenced navigable #190

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions spec.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2203,9 +2203,9 @@ Similar to [=navigable containers=] and their respective [=navigable container/c
other elements (so far, only the <{fencedframe}> element) present a more isolated [=navigable=] to
the user. These elements are called <dfn>fenced navigable containers</dfn>.

A [=fenced navigable container=] has a <dfn for="fenced navigable container">fenced navigable</dfn>,
which is either a [=traversable navigable=] with a non-null [=traversable navigable/unfenced
parent=], or null. It is initially null.
A [=fenced navigable container=] has a <dfn export for="fenced navigable container">fenced
navigable</dfn>, which is either a [=traversable navigable=] with a non-null [=traversable
navigable/unfenced parent=], or null. It is initially null.

<wpt>
/fenced-frame/window-frameElement.https.html
Expand Down