Re: "Save Page As"

On 22 November 2010 22:22, Behdad Esfahbod <behdad@google.com> wrote:
> On Mon, Nov 22, 2010 at 10:15 AM, John Hudson <tiro@tiro.com> wrote:
>> Dave Crossland wrote:
>>
>>> On 22 November 2010 21:48, John Hudson <tiro@tiro.com> wrote:
>>>>
>>>> Our of interest, what currently happens when this option is used to save
>>>> pages that use @font-face to link to naked TTFs?
>>
>>> Currently Chromium and Firefox do not implement saving linked fonts in
>>> any format, which I consider to be a bug.
>>
>> See, I don't, because I wouldn't consider a particular font to be part of
>> the *content* of the web page, and the fact that CSS provides for a list of
>> fallback fonts is a clear indicator that a particular font is not part of
>> the content of the page but is only one possible way of *displaying* the
>> page.
>
> With the same reasoning can't you also argue that CSS is categorically not
> part of the *content* of the web page and hence should not be  saved?!

I would consider a particular font to be part of the *content* of the
web page, just like a background image.

The CSS looks pretty similar to me:

@font-face { font-family: "TheFont"; src: url("TheFont.woff") format("woff");} 

body { background-image: url('paper.jpeg'); }

and I imagine the feature in the "Save Page As" code that understands
that paper.jpeg is needed to render the page faithfully offline will
soon be upgraded to understand TheFont.woff is also  needed to render
the page faithfully offline.

>> and the fact that CSS provides for a list of
>> fallback fonts is a clear indicator that a particular font is not part of
>> the content of the page but is only one possible way of *displaying* the
>> page.

There is a "Save Page As" option "Web page, HTML only" which will use
CSS fallbacks to render content without any assets.

Do you disagree that the point of the "Save Page As" option "Web page,
complete" is to render the page faithfully offline?

-- 
Cheers
Dave

Received on Monday, 22 November 2010 15:36:57 UTC