Thx. We don't use vanilla in production, so I just want to figure out what happening there. It's fine if the problem only affects Vanilla(if fixed, then better).
On Fri, Mar 24, 2017 at 2:57 PM 申远 <[email protected]> wrote: > This is a known issue, and you will meet this problem if you build weex > from source code. However, the release version of weex is not affected. I > think this problem has been solved by @fkysly . You can try rebuild weex > from https://github.com/apache/incubator-weex/tree/0.11-dev < > https://github.com/apache/incubator-weex/tree/0.11-dev> or use a release > version, either of which fix your problem. > > 在 2017年3月23日，12:34，jiyinyiyong <[email protected]> 写道： > > > > I encountered the problem yesterday that `setTimeout(function(){})` > return > > `undefined` to me, which was supposed to be a number since it's a number > in > > JavaScript. For some cases, I need to use `clearTimeout` to manage some > > delayed tasks. > > > > At first I was playing around on Android, it does not work. I tried iOS, > > failed too. > > > > By reading the code, it's just simply not implemented... it that right? > > > > > https://github.com/apache/incubator-weex/blob/master/html5/shared/setTimeout.js#L24-L27 > > > > Any previous plan for setTimeout? > >
