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

Update user prompt handler note for fallbackDefault #1831

Merged
merged 2 commits into from
Jul 23, 2024
Merged

Update user prompt handler note for fallbackDefault #1831

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e957210
Update user prompt handler note for fallbackDefault
juliandescottes Jul 16, 2024
6058d03
Update index.html
juliandescottes Jul 19, 2024
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
21 changes: 13 additions & 8 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10454,13 +10454,18 @@ <h3>User Prompt Handler</h3>
"<code>default</code>", "<code>prompt</code>"».

<p class="note">The "<code>default</code>" type represents a fallback
when no specific handler is defined for a given prompt type. The
"<code>beforeUnload</code>" prompt type does not use this default
handler, but instead falls back to the "<code>accept</code>" handler
if no more specific handler is defined. This is because HTTP-only
sessions do not allow the "<code>beforeUnload</code>" handler to be
customized, and enabling other protocols isn&apos;t expected to change
the user prompt handling as a side effect.
when no specific handler is defined for a given prompt type, including
the "<code>beforeUnload</code>" prompt type. It can only be set if the
unhandled prompt behavior is a <a data-cite=infra>map</a> which
[=map/contains=] "<code>default</code>". For HTTP-only sessions setting
unhandled prompt behavior as a string value, the value will be assigned to
the internal type "<code>fallbackDefault</code>". The
"<code>fallbackDefault</code>" value is not used for the
"<code>beforeUnload</code>" prompt type, instead it falls back to the
"<code>accept</code>" handler. This is because HTTP-only sessions do not
allow the "<code>beforeUnload</code>" handler to be customized, and enabling
other protocols isn&apos;t expected to change the user prompt handling as a
side effect.

<p>To <dfn>deserialize as an unhandled prompt behavior</dfn> given
argument <var>value</var>:
Expand Down Expand Up @@ -10635,7 +10640,7 @@ <h3>User Prompt Handler</h3>
and [=prompt handler configuration/notify=] false.

<li><p>If <var>handlers</var> contains "<code>fallbackDefault</code>"
return <var>handlers</var>["<code>default</code>"].
return <var>handlers</var>["<code>fallbackDefault</code>"].

<li><p>Return a <a>prompt handler
configuration</a> with [=prompt handler
Expand Down
Loading