Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Ignore a URL with an unsupported scheme#447

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.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
markafoltz merged 2 commits intow3c:gh-pagesfromtomoyukilabs:unsupported-scheme
Mar 26, 2018
Merged
Changes from1 commit
Commits
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
17 changes: 14 additions & 3 deletionsindex.html
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -422,6 +422,11 @@ <h2>
"https://www.w3.org/TR/html51/browsers.html#parse-the-sandboxing-directive">
parse a sandboxing directive</a></dfn>
</li>
<li>
<dfn><a href=
"https://www.w3.org/TR/html51/infrastructure.html#reparsed">parse a
URL</a></dfn>
</li>
<li>
<dfn><a href=
"https://www.w3.org/TR/html51/webappapis.html#queuing">queue a
Expand DownExpand Up@@ -1182,13 +1187,19 @@ <h4>
<ol>
<li>Resolve <var>U</var> relative to the API base URL specified
by the <a>current settings object</a>, and add the resulting
absolute URL (if any) to <var>presentationUrls</var>.
absolute URL (if any, and if the resulting scheme is supported
Copy link
Contributor

@markafoltzmarkafoltzMar 22, 2018
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This might be easier to read if it were broken into three steps. Here is one way that could be done.

  1. Let A be absolute URL that is the result of resolvingU relative to the API base URL specified by the current settings object.
  2. If the parse a URL algorithm failed, then throw a SyntaxError exception and abort all remaining steps.
  3. If A has a scheme supported by the controlling user agent, add A to presentationUrls.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM. Thanks for your suggestion.

by the <a>controlling user agent</a>) to
<var>presentationUrls</var>.
</li>
<li>If the resolve a URL algorithm failed, then <a>throw</a> a
<a>SyntaxError</a> exception and abort all remaining steps.
<li>If the <a>parse a URL</a> algorithm failed, then
<a>throw</a> a <a>SyntaxError</a> exception and abort all
remaining steps.
</li>
</ol>
</li>
<li>If <var>presentationUrls</var> is an empty list, then throw a
<a>NotSupportedError</a> and abort all remaining steps.
</li>
<li>If any member of <var>presentationUrls</var> is not an <a>a
priori authenticated URL</a>, then throw a <a>SecurityError</a> and
abort these steps.
Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp