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

Re: Continuing discussion on Polyfills

From: Ruffilo, Nick <Nick.Ruffilo@ingramcontent.com>
Date: Tue, 6 Feb 2018 14:56:02 +0000
To: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>, Jeff Buehler <jeff.buehler@knowbly.com>
CC: "deborah.kaplan@suberic.net" <deborah.kaplan@suberic.net>, "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Message-ID: <D26D829B-EDE1-4F39-8F31-BFE0643DA5EF@ingramcontent.com>
I like the way this is presented and said.

Responding to a previous note from Ivan – When I was talking about Polyfills, I was not referring to anything on the back-end.  What I was recommending is that a back-end script is what injects any polyfills into the documents.  Once I have the example, it will be more clear.

And while everyone might not have access to a customizable server, I promise you that if there is value – services will pop up to make it easier.  When the web first started, servers were expensive, but services like Geocities gave you a small chunk of space on their servers so you could get started.  Publishing is not easy, and that’s OK.  I believe we need to focus on making the overall process as Logical, accessible, and future-proof as possible.

As for all the Accessibility feedback – thank you.  I hear it loud and clear.


From: Hadrien Gardeur <hadrien.gardeur@feedbooks.com>
Date: Tuesday, February 6, 2018 at 4:33 AM
To: Jeff Buehler <jeff.buehler@knowbly.com>
Cc: "deborah.kaplan@suberic.net" <deborah.kaplan@suberic.net>, "Siegman, Tzviya - Hoboken" <tsiegman@wiley.com>, "Ruffilo, Nick" <Nick.Ruffilo@ingramcontent.com>, W3C Publishing Working Group <public-publ-wg@w3.org>
Subject: Re: Continuing discussion on Polyfills

IMO we should separate things on the authoring side from the user agent side.


A Web Publication MUST be entirely readable without any kind of polyfill, extension or specific browser support.
This means that all resources should be reachable through navigation, ideally in a sequence that follows the reading order.

For every other affordance (I'm working on those in the lifecycle branch<https://github.com/w3c/wpub/pull/130>), the author MAY attempt to support them from the entry page (HTML document returned by the WP address). This can be achieved by pointing to a Web App from that page.

User agent

A WP aware user agent SHOULD enhance the experience of reading a Web Publication by providing additional affordances that won't clash with the author's intent (easier said than done, user settings for example are very difficult to handle).

IMO, presentation and navigation affordances MUST only enhance resources that are within the scope of the WP which means:

  *   all resources listed in the default reading order and list of resources
  *   but this excludes the entry page or any other resource not listed in our collections
For resources that are not within the scope of a WP, a user agent MAY provide two other affordances instead:

  *   switch to publication mode
  *   add to the list of publications
Received on Tuesday, 6 February 2018 14:56:31 UTC

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