Clarification required: polyfill-vendor-differences

[oori]

Clarification requested for: https://github.com/HaNdTriX/generator-chrome-extension-kickstart/blob/master/DOCUMENTATION.md#polyfill-vendor-differences

Related to this list: https://bugzilla.mozilla.org/show_bug.cgi?id=1161828
And this: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Chrome_incompatibilities

Thanks for your code.

[HaNdTriX]

Hi @oori

I haven't published any polyfills yet. I believe it will depend on your use cases, which polyfills should be included. Neither do i have a list on vendor differences yet (PRs welcome!).

Here you can find an example how the config for polyfilling chrome apis might look like:
https://gist.github.com/HaNdTriX/77916f3fcdd7d285f7c9#example-webpack-polyfill-config

[oori]

Thanks for the clarification.
I'd suggest to leave this issue open as a placeholder for the polyfill topic. Perhaps over time, web extensions would be standardised making this obsolete.. let's see which comes first.

[yxliang01]

Although I can see different commands in package.json that are for building extensions for different browsers (called vendors there), but, I still don't see any folder that is meant to be placing browser-specific files. Could you clarify this?

Thanks

[yxliang01]

My rough proof-of-concept of the universal webextension extension template is at https://github.com/yxliang01/generator-chrome-extension-kickstart/tree/universal . You may take a look. It is basically what I meant by the comment above. It's however not yet completed. Anyway, I would like to hear your ideas.

Thanks