- From: François REMY <francois.remy.dev@outlook.com>
- Date: Wed, 3 Jul 2013 19:58:35 +0200
- To: "Marcos Caceres" <w3c@marcosc.com>
- Cc: "Brian Kardell" <bkardell@gmail.com>, <public-nextweb@w3.org>
> What does "module" mean here? AMD? NPM? CommonJS?
An object that is self-contained. That includes any kind of module, even
just:
window.myProllyfill = {
Abc: function() {
...
},
Def: function() {
...
}
}
> - when you use some global namespace, use a prefix (no code should use
> your
> function by mistaking it for a native implementation)
Redefining an existing prollyfill that (you think) sucks by another one is
the best way to have problems because some code most probably rely on the
"sucking" implementation. That's why you simply do not want prollyfill to
clash with anything hence special names and prefixes.
You don't have to prefix everything, just enough to make sure people can use
the polyfill and still be sure no code that never "met" the prollyfill will
use it by mistake.
Received on Wednesday, 3 July 2013 17:58:59 UTC