KEMBAR78
Parse URLs relative to the relevant settings object, not entry by domenic · Pull Request #963 · w3c/ServiceWorker · GitHub
Skip to content

Conversation

@domenic
Copy link
Contributor

@domenic domenic commented Aug 26, 2016

Fixes #922. Web platform tests at web-platform-tests/wpt#3449. Part of the overall effort in whatwg/html#1431.

In the process, fixes some ambiguity about how to parse URLs in the Link header, as previous it parsed relative to the entry settings object, which did not exist during this algorithm.

<li>If <var>request</var>'s <a for="request">client</a> is not a <a>secure context</a>, abort these steps.</li>
<li>Let <var>scriptURL</var> be the result of <a for="url">parsing</a> the <a>target IRI</a> of the <code>Link</code> header.</li>
<li>Let <var>scopeURL</var> be the "<code>scope</code>" <a>target attribute</a> of the <code>Link</code> header, or null if no such attribute is present.</li>
<li>Let <var>scopeURL</var> null.
Copy link
Collaborator

Choose a reason for hiding this comment

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

"be" is missing.

@jungkees
Copy link
Collaborator

jungkees commented Sep 6, 2016

@domenic, thanks for sorting out the behavior and working on this PR!

LGTM % the above nits

Fixes #922. Web platform tests at web-platform-tests/wpt#3449. Part of the overall effort in whatwg/html#1431.

In the process, fixes some ambiguity about how to parse URLs in the Link header, as previous it parsed relative to the entry settings object, which did not exist during this algorithm.
@jungkees jungkees merged commit 7a3189e into w3c:master Sep 7, 2016
jungkees added a commit that referenced this pull request Sep 7, 2016
Parse URLs relative to the relevant settings object, not entry: #963
@domenic domenic deleted the no-entry branch November 6, 2016 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Eliminate usage of entry and incumbent settings objects

2 participants