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

Jump to bottom

Add small section about handling saving a page for offline usage. #135

Merged
merged 1 commit into from
Dec 1, 2022
Merged

Add small section about handling saving a page for offline usage. #135

Show file tree
Hide file tree
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
11 changes: 11 additions & 0 deletions Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,6 +383,17 @@ If the content does not specify a specific method:
<td>Client makes initial request to server with the patch request header. Server does not reply with the patch-subset magic number, and sends the full font file to the client from beginning to end.
</table>


Offline Usage
-------------

Special consideration must be taken when saving a page for offline usage that uses an incrementally
transferred font since the saved page won't be able to increment the font if content changes (eg.
due to javascript execution). In these cases the page saving mechanism should download the full font
by making a normal GET request without the [=patch request header=] to the font url. Additionally
when URL's are rewritten to point to the saved full font any of the incremental tech specifiers should
be removed.

Patch Based Incremental Transfer {#patch-incxfer}
=================================================

Expand Down
13 changes: 10 additions & 3 deletions Overview.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,7 @@
<meta content="WD" name="w3c-status">
<meta content="Bikeshed version 63e66730b, updated Tue Oct 25 12:35:05 2022 -0700" name="generator">
<link href="https://www.w3.org/TR/IFT/" rel="canonical">

<meta content="7cf4ac62d44684e373f41d83891eb61264f6fea9" name="document-revision">

<meta content="2f4835b6f6a3480d6ecdb832b2e50064f4806324" name="document-revision">
<style>
.conform:hover {background: #31668f}
.conform:target {padding: 2px; border: 2px solid #AAA; background: #31668f }
Expand Down Expand Up @@ -321,6 +319,7 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
<ol class="toc">
<li><a href="#method-negotiation"><span class="secno">3.1</span> <span class="content">IFT Method Negotiation</span></a>
<li><a href="#fallback"><span class="secno">3.2</span> <span class="content">IFT Method Fallback</span></a>
<li><a href="#offline-usage"><span class="secno">3.3</span> <span class="content">Offline Usage</span></a>
</ol>
<li>
<a href="#patch-incxfer"><span class="secno">4</span> <span class="content">Patch Based Incremental Transfer</span></a>
Expand Down Expand Up @@ -671,6 +670,13 @@ <h3 class="heading settled" data-level="3.2" id="fallback"><span class="secno">3
<td>Client makes initial request without the patch request header, and possibly with the <code>Range</code> header. Server replies without <code>Accept-Ranges</code> header, and sends the full font file to the client from beginning to end.
<td>Client makes initial request to server with the patch request header. Server does not reply with the patch-subset magic number, and sends the full font file to the client from beginning to end.
</table>
<h3 class="heading settled" data-level="3.3" id="offline-usage"><span class="secno">3.3. </span><span class="content">Offline Usage</span><a class="self-link" href="#offline-usage"></a></h3>
<p>Special consideration must be taken when saving a page for offline usage that uses an incrementally
transferred font since the saved page won’t be able to increment the font if content changes (eg.
due to javascript execution). In these cases the page saving mechanism should download the full font
by making a normal GET request without the <a data-link-type="dfn" href="#patch-request-header" id="ref-for-patch-request-header①">patch request header</a> to the font url. Additionally
when URL’s are rewritten to point to the saved full font any of the incremental tech specifiers should
be removed.</p>
<h2 class="heading settled" data-level="4" id="patch-incxfer"><span class="secno">4. </span><span class="content">Patch Based Incremental Transfer</span><a class="self-link" href="#patch-incxfer"></a></h2>
<h3 class="heading settled" data-level="4.1" id="font-subset-info"><span class="secno">4.1. </span><span class="content">Font Subset</span><a class="self-link" href="#font-subset-info"></a></h3>
<p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="font-subset">font subset</dfn> is a modified version of a font file that contains only the data needed to
Expand Down Expand Up @@ -3027,6 +3033,7 @@ <h2 class="no-num no-ref heading settled" id="issues-index"><span class="content
<b><a href="#patch-request-header">#patch-request-header</a></b><b>Referenced in:</b>
<ul>
<li><a href="#ref-for-patch-request-header">3.1. IFT Method Negotiation</a>
<li><a href="#ref-for-patch-request-header①">3.3. Offline Usage</a>
</ul>
</aside>
<aside class="dfn-panel" data-for="abstract-opdef-handle-server-response">
Expand Down