FWIW, there are also W3C best practices available for polyfills: https://www.w3.org/2001/tag/doc/polyfills/ Le 06.02.2018 10:33, Hadrien Gardeur a écrit : > IMO we should separate things on the authoring side from the user agent side. > > Authoring > > 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 [1]), 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 Links: ------ [1] https://github.com/w3c/wpub/pull/130
Received on Tuesday, 6 February 2018 10:58:46 UTC