The implementation in js framework is finished, and I sent a PR [1] to
merge it into the master branch.
The Vue.js framework and native render engines have already achieved it and
all unit tests are passed (poison: [2] validator: [3]). I think it's time
to test it in some real cases, such as the
For the Vue.js framework, I sent a PR [1] to achieve it. I think Rax should
do the same thing.
In the PR, I removed legacy framework APIs and use "createInstanceContext"
instead of "createInstance" to create the Vue module instance for each page.
Native render engines should also call
+1. Currently, multiple js bundles are executed in the same js context, and
the isolation is implemented by js, which is not robust.
In my opinion, the most reasonable solution is to distinguish the "Global
Context" and the "Instance Context", move the logic of instance management
and code
ipt http://dotwe.org/vue/
> 522f075bbeed1479486c067781c41adc to change global object, if other page
> use "setTimeout" may throw js exception. So we want use multi context for
> Weex page, that one page cannot impact other pages.
>
>
> As the picture shows, create globla class on G
. For example,
we could use this script
http://dotwe.org/vue/522f075bbeed1479486c067781c41adc to change global
object, if other page use "setTimeout" may throw js exception. So we want
use multi context for Weex page, that one page cannot impact other pages.
As the picture shows, create gl
