> If we don't have information like that available, then it seems like we end up in a strange place where we're asking the browser to weed out the author-provided interface (it could be done, but is there precedent for this?) or we risk overlapping feature deployment. That's exactly why I think we should absolutely avoid having affordances from our publication mode being implemented using a polyfill in individual resources. If the fallback is a Web App, it doesn't get in the way. But if each resource in a publication starts implementing affordances from our publication mode, it will be nearly impossible for certain user agents (Web and native apps) to avoid the kind of overlapping that you're describing even with cleanly implemented polyfills.
Received on Wednesday, 7 February 2018 17:12:35 UTC