W3C home > Mailing lists > Public > public-publ-wg@w3.org > February 2018

RE: A followup/writeup on our Monday discussions (was Re: Continuing discussion on Polyfills)

From: Matt Garrish <matt.garrish@gmail.com>
Date: Wed, 7 Feb 2018 15:12:51 -0500
To: "'Hadrien Gardeur'" <hadrien.gardeur@feedbooks.com>
Cc: "'Romain'" <rdeltour@gmail.com>, "'Ivan Herman'" <ivan@w3.org>, "'W3C Publishing Working Group'" <public-publ-wg@w3.org>
Message-ID: <042301d3a050$08bcdfe0$1a369fa0$@gmail.com>
> The entry page would link to the fallback app, no need for a link in the manifest or for the browser to be WP-aware.

 

Ah, so this isn't like having a default_applications for fallback apps, but the entry page is its own WAM?

 

Matt

 

From: Hadrien Gardeur [mailto:hadrien.gardeur@feedbooks.com] 
Sent: February 7, 2018 2:48 PM
To: Matt Garrish <matt.garrish@gmail.com>
Cc: Romain <rdeltour@gmail.com>; Ivan Herman <ivan@w3.org>; W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: Re: A followup/writeup on our Monday discussions (was Re: Continuing discussion on Polyfills)

 

The entry page would link to the fallback app, no need for a link in the manifest or for the browser to be WP-aware.

This wouldn't get in the way of other apps for the following reasons:

*	a WP-aware browser would trigger the "switch to publication mode" or "add to publication list" affordances on the entry page (or any other page with a link to the manifest)
*	web and native apps (including browser extensions) would only use the entry page to detect the link as well, and then they would immediately go to the first resource in the default reading order
Received on Wednesday, 7 February 2018 20:40:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:21 UTC