Skip to content
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

Editorial: pop-up → popup #5499

Merged
merged 1 commit into from
Apr 30, 2020
Merged

Editorial: pop-up → popup #5499

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
16 changes: 7 additions & 9 deletions source
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1991,8 +1991,8 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
<p>A plugin can be <dfn data-x="concept-plugin-secure">secured</dfn> if it honors the semantics of
the <code data-x="attr-iframe-sandbox">sandbox</code> attribute.</p>

<p class="example">For example, a secured plugin would prevent its contents from creating pop-up
windows when the plugin is instantiated inside a sandboxed <code>iframe</code>.</p>
<p class="example">For example, a secured plugin would prevent its contents from creating popups
when the plugin is instantiated inside a sandboxed <code>iframe</code>.</p>

<div w-nodev>

Expand Down Expand Up @@ -79627,17 +79627,15 @@ interface <dfn>BarProp</dfn> {
keyword.</p>

<div class="note">

<p>The <code data-x="attr-iframe-sandbox-allow-same-origin">allow-same-origin</code> keyword
is intended for two cases.</p>

<p>First, it can be used to allow content from the same site to be sandboxed to disable
scripting, while still allowing access to the DOM of the sandboxed content.</p>

<p>Second, it can be used to embed content from a third-party site, sandboxed to prevent that
site from opening pop-up windows, etc, without preventing the embedded page from
communicating back to its originating site, using the database APIs to store data, etc.</p>

site from opening popups, etc, without preventing the embedded page from communicating back
to its originating site, using the database APIs to store data, etc.</p>
</div>
</li>

Expand Down Expand Up @@ -79802,8 +79800,8 @@ interface <dfn>BarProp</dfn> {
<code>Document</code> were opened.</p>

<p>An example of the latter would be something like keeping track of the precise coordinate from
which a pop-up <code>div</code> was made to animate, so that if the user goes back, it can be
made to animate to the same location. Or alternatively, it could be used to keep a pointer into a
which a popup <code>div</code> was made to animate, so that if the user goes back, it can be made
to animate to the same location. Or alternatively, it could be used to keep a pointer into a
cache of data that would be fetched from the server based on the information in the
<span>URL</span>, so that when going back and forward, the information doesn't have to be fetched
again.</p>
Expand Down Expand Up @@ -113271,7 +113269,7 @@ marquee {

<p>User agents are expected to honor the Unicode semantics of text that is exposed in user
interfaces, for example supporting the bidirectional algorithm in text shown in dialogs, title
bars, pop-up menus, and tooltips. Text from the contents of elements is expected to be rendered in
bars, popup menus, and tooltips. Text from the contents of elements is expected to be rendered in
a manner that honors <span>the directionality</span> of the element from which the text was
obtained. Text from attributes is expected to be rendered in a manner that honours the
<span>directionality of the attribute</span>.</p>
Expand Down