Re: JS - inside or out?

That certainly one possibility…

From: Laurent Le Meur <laurent.lemeur@edrlab.org>
Date: Thursday, November 17, 2016 at 10:37 AM
To: W3C Digital Publishing IG <public-digipub-ig@w3.org>
Subject: Re: JS - inside or out?
Resent-From: <public-digipub-ig@w3.org>
Resent-Date: Thursday, November 17, 2016 at 10:38 AM

If we use the dichotomy Reading System vs Content, do you mean that the Content metadata should contain information meaning e.g. "I'm dealing with the pagination" or "I'm dealing with the reader mode" (following your list of "JS features"), forcing the RS to turn these features off and lets the Content JS dealing with them?

Laurent Le Meur
EDRLab




Le 17 nov. 2016 à 16:03, Hadrien Gardeur <hadrien.gardeur@feedbooks.com<mailto:hadrien.gardeur@feedbooks.com>> a écrit :

I'm going to repeat myself, but I strongly believe that we can figure out a way to handle both:

We just need to figure out a way to:

  *   identify that a JS provides such progressive enhancements in order to turn it off eventually
  *   make sure that each progressive enhancement can be tested individually, this way we can have a much more fine grained approach for such a "Web Publication Polyfill"
I've listed a few of the progressive enhancements that could be supported at: https://github.com/HadrienGardeur/webpub-manifest/wiki/Web-Publication-JS-Features