Re: Is polyfilling future web APIs a good idea?

Brian, prollyfills seems pragmatic. But what about when the logic of an API changes, but not the name? The node.replaceWith() API for example is about to be revamped to cover some edge cases. If the prollyfills exposed node._replaceWith(), what should it do when the new node.replaceWith() comes

Fwd: [webappsec] CfC: Proposed non-normative updates to CORS

(Dang, just realized I forgot to include WebApps on this joint deliverable.) Members of WebApps, please note the below Call for Consensus on proposed non-normative updates to the CORS recommendation and comment on public-webapp...@w3.org by Monday, August 10, 2015. Thank you, Brad Hill co-chair,

Re: Is polyfilling future web APIs a good idea?

On Mon, Aug 3, 2015 at 9:07 PM, Glen Huang wrote: > Brian, > > prollyfills seems pragmatic. But what about when the logic of an API changes, > but not the name? The node.replaceWith() API for example is about to be > revamped to cover some edge cases. If the prollyfills exposed > node._replaceW