Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

Strengthen advice to keep default context menu available #882

Merged
merged 3 commits into from May 22, 2017
Merged

Strengthen advice to keep default context menu available #882

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8be122e
Strengthen advice to keep default context menu available
Apr 18, 2017
dfbec6b
remove class="impl"
Apr 18, 2017
d8c1e41
cleaner structure?
May 22, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
23 changes: 6 additions & 17 deletions sections/semantics-interactive-elements.include
View file
Open in desktop
Expand Up @@ -42,7 +42,7 @@
The <{details}> element is not appropriate for footnotes. Please see [[#footnotes]] for details on how to mark up footnotes.
</p>

The <span class="impl">first</span> <{summary}> element child of the element, if any,
The first <{summary}> element child of the element, if any,
<a>represents</a> the summary or legend of the details. If there is no
child <{summary}> element, the user agent should provide its own legend (e.g.,
in English "Details" or Spanish <span lang="es">"Detalles"</span>).
Expand Down Expand Up @@ -478,8 +478,6 @@
present, that the command is the one that would have been invoked if the user had directly
activated the menu's subject instead of using the menu. The <code>default</code> attribute is a <a>boolean attribute</a>.

<div class="impl">

<hr />

The <dfn attribute for="HTMLMenuItemElement"><code>type</code></dfn> IDL attribute must
Expand All @@ -505,8 +503,6 @@
If the element's <a facet for="menuitem">Disabled State</a> is true
(disabled) then the element has no <a>activation behavior</a>.

</div>

<p class="note">
The <{menuitem}> element is not rendered except as <a element lt="menu">part of a context menu</a>.
</p>
Expand Down Expand Up @@ -629,18 +625,11 @@
the user agent must <a>build and show</a> the menu for
<var>menu</var> with <var>subject</var> as the subject.

The user agent may also provide access to its default context menu, if any, with the context
menu shown. For example, it could merge the menu items from the two menus together, or provide the
page's context menu as a submenu of the default menu. In general, user agents are encouraged to
de-emphasize their own contextual menu items, so as to give the author's context menu the
appearance of legitimacy — to allow documents to feel like "applications" rather than "mere
Web pages".

User agents may provide means for bypassing the context menu processing model, ensuring that
the user can always access the user agent's default context menus. For example, the user agent could
handle right-clicks that have the Shift key depressed in such a way that it does not fire the
<code>contextmenu</code> event and instead always shows the default
context menu.
The user agent should also provide access to its default context menu, with the context
menu shown. For example, it could merge the menu items from the two menus together,
provide the page's context menu as a submenu of the default menu, or
handle right-clicks that have the Shift key depressed by showing the default context menu
instead of firing the <code>contextmenu</code> event.

<hr />

Expand Down