+1. > On Jul 9, 2019, at 6:43 PM, Alex Harui <[email protected]> wrote: > > IMO, adding an API for missing.js should only be done for APIs that are truly > cross-browser. If an API requires a polyfill, then if we add it to > missing.js and someone tries to use it on the browser that doesn't support > it, it won't work for them without the polyfill. > > Either there should be a separate typedefs SWC for it, or we should see what > changes to the toolchain are needed to allow the missing API to be supplied > by a source extern in the SWC that uses it.
- RE: Build failed in Jenkins: roya... Yishay Weiss
- Re: Build failed in Jenkins: roya... Carlos Rovira
- Re: Build failed in Jenkins: roya... Harbs
- Re: Build failed in Jenkins: roya... Carlos Rovira
- Re: Build failed in Jenkins: roya... Piotr Zarzycki
- Re: Build failed in Jenkins: roya... Harbs
- Re: Build failed in Jenkins: roya... Piotr Zarzycki
- Re: Build failed in Jenkins: roya... Josh Tynjala
- Re: Build failed in Jenkins: roya... Carlos Rovira
- Re: Build failed in Jenkins: roya... Alex Harui
- Re: Build failed in Jenkins: roya... Harbs
- Re: Build failed in Jenkins: roya... Carlos Rovira
- Re: Build failed in Jenkins: roya... Harbs
- Re: Build failed in Jenkins: roya... Josh Tynjala
- Re: Build failed in Jenkins: roya... Alex Harui
- Re: Build failed in Jenkins: roya... Carlos Rovira
- Re: Build failed in Jenkins: roya... Alex Harui
- Re: Build failed in Jenkins: roya... Harbs
- Re: Build failed in Jenkins: roya... Harbs
- Build failed in Jenkins: royale-asjs_jsonly #3220 Apache Royale CI Server
- Build failed in Jenkins: royale-asjs_jsonly #... Apache Royale CI Server
