[jira] [Created] (WEEX-586) WXEmbed Support Listen scroll scrollEnd scrollStart Event
codefurture created WEEX-586: Summary: WXEmbed Support Listen scroll scrollEnd scrollStart Event Key: WEEX-586 URL: https://issues.apache.org/jira/browse/WEEX-586 Project: Weex Issue Type: Bug Reporter: codefurture Assignee: codefurture WXEmbed Support Listen scroll scrollEnd scrollStart Event -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-568) Add Scan Delay Interface For AutoScanConfigRegister
[ https://issues.apache.org/jira/browse/WEEX-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-568. Resolution: Fixed > Add Scan Delay Interface For AutoScanConfigRegister > --- > > Key: WEEX-568 > URL: https://issues.apache.org/jira/browse/WEEX-568 > Project: Weex > Issue Type: Bug >Reporter: codefurture >Assignee: codefurture >Priority: Major > > Add Scan Delay Interface For AutoScanConfigRegister -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-580) view key is not unique, RecycleList data repeat render not right,
codefurture created WEEX-580: Summary: view key is not unique, RecycleList data repeat render not right, Key: WEEX-580 URL: https://issues.apache.org/jira/browse/WEEX-580 Project: Weex Issue Type: Bug Reporter: codefurture Assignee: codefurture view key is not unique,RecycleList data repeat render not right, change viewTreeKey to unique -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-530) weex-playground-app weex_sdk 0.18.0-beta3 RecyclerView的加载更多功能在AccessibilityService模拟下滑操作下不能触发
[ https://issues.apache.org/jira/browse/WEEX-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-530. Resolution: Invalid > weex-playground-app weex_sdk 0.18.0-beta3 > RecyclerView的加载更多功能在AccessibilityService模拟下滑操作下不能触发 > - > > Key: WEEX-530 > URL: https://issues.apache.org/jira/browse/WEEX-530 > Project: Weex > Issue Type: Task >Reporter: xing >Assignee: codefurture >Priority: Major > > 我写了个AccessibilityService的服务，用来监听weex-playground-app的列表页面，想要实现模拟滑动recyclerView，但是发现，加载更多这种功能无法触发，普通的下滑是支持的。 > 没有细看weex关于recyclerView的实现，猜测是加载更多的实现有些特殊吧，跟我们平常写recyclerView的加载更多不一样，或者是(其他的细节问题) > (关于weex recyclerView的代码我没太看懂) > 请指教 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-530) weex-playground-app weex_sdk 0.18.0-beta3 RecyclerView的加载更多功能在AccessibilityService模拟下滑操作下不能触发
[ https://issues.apache.org/jira/browse/WEEX-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586845#comment-16586845 ] codefurture commented on WEEX-530: -- you can use scroll to with offset > weex-playground-app weex_sdk 0.18.0-beta3 > RecyclerView的加载更多功能在AccessibilityService模拟下滑操作下不能触发 > - > > Key: WEEX-530 > URL: https://issues.apache.org/jira/browse/WEEX-530 > Project: Weex > Issue Type: Task >Reporter: xing >Assignee: codefurture >Priority: Major > > 我写了个AccessibilityService的服务，用来监听weex-playground-app的列表页面，想要实现模拟滑动recyclerView，但是发现，加载更多这种功能无法触发，普通的下滑是支持的。 > 没有细看weex关于recyclerView的实现，猜测是加载更多的实现有些特殊吧，跟我们平常写recyclerView的加载更多不一样，或者是(其他的细节问题) > (关于weex recyclerView的代码我没太看懂) > 请指教 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-486) when i use navigator to implement multipage on android , OOM crash will easily happened
[ https://issues.apache.org/jira/browse/WEEX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-486. Resolution: Won't Fix > when i use navigator to implement multipage on android , OOM crash will > easily happened > > > Key: WEEX-486 > URL: https://issues.apache.org/jira/browse/WEEX-486 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.19 >Reporter: fdh19979 >Assignee: codefurture >Priority: Critical > > 修改webpack，实现多页面打包，在原生每个activity或者controller中render一个JS文件 > 我发现在安卓中，使用WXFileUtils中loadAsset时，很容易在readStreamToString中出现OOM内存溢出 > 使用android profile发现，不停开启新页面的情况下，内存占用一直上升，关闭页面后，内存占用并不会下降 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-519) scroller子项touchend事件在滚动时无法获取或触发
[
https://issues.apache.org/jira/browse/WEEX-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586840#comment-16586840
]
codefurture commented on WEEX-519:
--
when you scroll, touch is comsumed by scroller
> scroller子项touchend事件在滚动时无法获取或触发
> ---
>
> Key: WEEX-519
> URL: https://issues.apache.org/jira/browse/WEEX-519
> Project: Weex
> Issue Type: Bug
> Components: Project
>Affects Versions: 0.18
> Environment: 测试在Android手机上，ios还未测试过
>Reporter: gexiaoming
>Assignee: codefurture
>Priority: Critical
>
> 需要获取scroller子项的touchend,touchstart事件
> touchstart事件都可以获取到
> 但是touchend事件比较奇怪，子项加入@touchend，如果只是触碰一下，没有滚动的话，事件是有触发的，一旦滚动起来，事件就没了
> 代码如下
> {code:java}
>
>
>
>
>
> 1234
>
>
>
> delete
>
>
>
>
>
> const modal = weex.requireModule("modal");
> export default {
> methods: {
> touchstart: function(e) {
> modal.toast({ message: "touchstart" });
> },
> touchend: function(e) {
> modal.toast({ message: "touchend" + e });
> }
> }
> };
>
>
> .panel {
> width: 600px;
> height: 250px;
> margin-left: 75px;
> margin-top: 35px;
> margin-bottom: 35px;
> flex-direction: column;
> justify-content: center;
> border-width: 2px;
> border-style: solid;
> border-color: rgb(162, 217, 192);
> background-color: rgba(162, 217, 192, 0.2);
> }
> .text {
> font-size: 50px;
> text-align: center;
> color: #41b883;
> }
> .list {
> flex-direction: row;
> height: 300px;
> }
> .delete {
> width: 200px;
> height: 250px;
> margin-left: 75px;
> margin-top: 35px;
> margin-bottom: 35px;
> flex-direction: column;
> justify-content: center;
> border-width: 2px;
> background-color: red;
> }
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (WEEX-519) scroller子项touchend事件在滚动时无法获取或触发
[
https://issues.apache.org/jira/browse/WEEX-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
codefurture closed WEEX-519.
Resolution: Not A Problem
> scroller子项touchend事件在滚动时无法获取或触发
> ---
>
> Key: WEEX-519
> URL: https://issues.apache.org/jira/browse/WEEX-519
> Project: Weex
> Issue Type: Bug
> Components: Project
>Affects Versions: 0.18
> Environment: 测试在Android手机上，ios还未测试过
>Reporter: gexiaoming
>Assignee: codefurture
>Priority: Critical
>
> 需要获取scroller子项的touchend,touchstart事件
> touchstart事件都可以获取到
> 但是touchend事件比较奇怪，子项加入@touchend，如果只是触碰一下，没有滚动的话，事件是有触发的，一旦滚动起来，事件就没了
> 代码如下
> {code:java}
>
>
>
>
>
> 1234
>
>
>
> delete
>
>
>
>
>
> const modal = weex.requireModule("modal");
> export default {
> methods: {
> touchstart: function(e) {
> modal.toast({ message: "touchstart" });
> },
> touchend: function(e) {
> modal.toast({ message: "touchend" + e });
> }
> }
> };
>
>
> .panel {
> width: 600px;
> height: 250px;
> margin-left: 75px;
> margin-top: 35px;
> margin-bottom: 35px;
> flex-direction: column;
> justify-content: center;
> border-width: 2px;
> border-style: solid;
> border-color: rgb(162, 217, 192);
> background-color: rgba(162, 217, 192, 0.2);
> }
> .text {
> font-size: 50px;
> text-align: center;
> color: #41b883;
> }
> .list {
> flex-direction: row;
> height: 300px;
> }
> .delete {
> width: 200px;
> height: 250px;
> margin-left: 75px;
> margin-top: 35px;
> margin-bottom: 35px;
> flex-direction: column;
> justify-content: center;
> border-width: 2px;
> background-color: red;
> }
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-466) 升级weex sdk 0.19后weex无法初始化
[ https://issues.apache.org/jira/browse/WEEX-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586837#comment-16586837 ] codefurture commented on WEEX-466: -- have release right version > 升级weex sdk 0.19后weex无法初始化 > - > > Key: WEEX-466 > URL: https://issues.apache.org/jira/browse/WEEX-466 > Project: Weex > Issue Type: Bug > Environment: weex sdk 0.19 ndk 15 > 直接引入的源码，没做任何修改 > 升级weex sdk 0.19后出现的问题，之前是0.11版本没有问题 >Reporter: 张波 >Assignee: codefurture >Priority: Major > > get NL80211_STA_INFO_CNAHLOAD > 06-20 16:43:46.401 1164-1848/? E/WificondControl: Noise: -90, Snr: 31, > Chload: -1 > 06-20 16:43:46.504 13662-13706/com.flightmanager.view E/zygote: No > implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > 06-20 16:43:46.504 13662-13706/com.flightmanager.view E/SafeRunnable: > SafeRunnable run throw expection:No implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > 06-20 16:43:46.510 13662-13706/com.flightmanager.view E/AndroidRuntime: FATAL > EXCEPTION: WeexJSBridgeThread > Process: com.flightmanager.view, PID: 13662 > java.lang.UnsatisfiedLinkError: No implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > at > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(Native > Method) > at > com.taobao.weex.bridge.WXBridge.setRenderContainerWrapContent(WXBridge.java:497) > at > com.taobao.weex.bridge.WXBridgeManager.setRenderContentWrapContentToCore(WXBridgeManager.java:2656) > at com.taobao.weex.WXSDKInstance$2.run(WXSDKInstance.java:264) > at com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:48) > at android.os.Handler.handleCallback(Handler.java:808) > at android.os.Handler.dispatchMessage(Handler.java:101) > at android.os.Looper.loop(Looper.java:166) > at android.os.HandlerThread.run(HandlerThread.java:65) > 06-20 16:43:46.518 740-2802/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-466) 升级weex sdk 0.19后weex无法初始化
[ https://issues.apache.org/jira/browse/WEEX-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-466. Resolution: Fixed > 升级weex sdk 0.19后weex无法初始化 > - > > Key: WEEX-466 > URL: https://issues.apache.org/jira/browse/WEEX-466 > Project: Weex > Issue Type: Bug > Environment: weex sdk 0.19 ndk 15 > 直接引入的源码，没做任何修改 > 升级weex sdk 0.19后出现的问题，之前是0.11版本没有问题 >Reporter: 张波 >Assignee: codefurture >Priority: Major > > get NL80211_STA_INFO_CNAHLOAD > 06-20 16:43:46.401 1164-1848/? E/WificondControl: Noise: -90, Snr: 31, > Chload: -1 > 06-20 16:43:46.504 13662-13706/com.flightmanager.view E/zygote: No > implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > 06-20 16:43:46.504 13662-13706/com.flightmanager.view E/SafeRunnable: > SafeRunnable run throw expection:No implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > 06-20 16:43:46.510 13662-13706/com.flightmanager.view E/AndroidRuntime: FATAL > EXCEPTION: WeexJSBridgeThread > Process: com.flightmanager.view, PID: 13662 > java.lang.UnsatisfiedLinkError: No implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > at > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(Native > Method) > at > com.taobao.weex.bridge.WXBridge.setRenderContainerWrapContent(WXBridge.java:497) > at > com.taobao.weex.bridge.WXBridgeManager.setRenderContentWrapContentToCore(WXBridgeManager.java:2656) > at com.taobao.weex.WXSDKInstance$2.run(WXSDKInstance.java:264) > at com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:48) > at android.os.Handler.handleCallback(Handler.java:808) > at android.os.Handler.dispatchMessage(Handler.java:101) > at android.os.Looper.loop(Looper.java:166) > at android.os.HandlerThread.run(HandlerThread.java:65) > 06-20 16:43:46.518 740-2802/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (WEEX-510) weex fix布局在安卓上面需要滚动到最后才能显示
[ https://issues.apache.org/jira/browse/WEEX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture reassigned WEEX-510: Assignee: YorkShen (was: codefurture) > weex fix布局在安卓上面需要滚动到最后才能显示 > -- > > Key: WEEX-510 > URL: https://issues.apache.org/jira/browse/WEEX-510 > Project: Weex > Issue Type: Bug > Environment: 安卓系统，全部手机信号 >Reporter: xiaomingzilong >Assignee: YorkShen >Priority: Major > > weex使用了fixed布局，将bottom:0的组件放在页面最底部的时候，要是首屏元素太多的话，页面需要滚动到最后才能显示出fixed,bottom:0的组件出来 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-510) weex fix布局在安卓上面需要滚动到最后才能显示
[ https://issues.apache.org/jira/browse/WEEX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586836#comment-16586836 ] codefurture commented on WEEX-510: -- please provide a link example > weex fix布局在安卓上面需要滚动到最后才能显示 > -- > > Key: WEEX-510 > URL: https://issues.apache.org/jira/browse/WEEX-510 > Project: Weex > Issue Type: Bug > Environment: 安卓系统，全部手机信号 >Reporter: xiaomingzilong >Assignee: codefurture >Priority: Major > > weex使用了fixed布局，将bottom:0的组件放在页面最底部的时候，要是首屏元素太多的话，页面需要滚动到最后才能显示出fixed,bottom:0的组件出来 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-367) android P兼容
[ https://issues.apache.org/jira/browse/WEEX-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586835#comment-16586835 ] codefurture commented on WEEX-367: -- have try catch, it will works ok > android P兼容 > --- > > Key: WEEX-367 > URL: https://issues.apache.org/jira/browse/WEEX-367 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: owenli >Assignee: codefurture >Priority: Blocker > Attachments: WechatIMG28.jpeg, cdf6c5a081fa2662ced71b6f99fada1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-280) weex_sdk0.18.0 degradeToH5|createInstance fail|wx_create_instance_error isJSFrameworkInit==false reInitCount == 1
[
https://issues.apache.org/jira/browse/WEEX-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
codefurture closed WEEX-280.
Resolution: Fixed
> weex_sdk0.18.0 degradeToH5|createInstance fail|wx_create_instance_error
> isJSFrameworkInit==false reInitCount == 1
> --
>
> Key: WEEX-280
> URL: https://issues.apache.org/jira/browse/WEEX-280
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.17, 0.18
>Reporter: aixiaoxiang
>Assignee: codefurture
>Priority: Blocker
>
> {color:#ff}weex_sdk:0.18.0{color} 在安卓下面冷启动app（切记不要加app欢迎引导页，直接进入主页）会报
> +*degradeToH5|createInstance fail|wx_create_instance_error
> isJSFrameworkInit==false reInitCount == 1*+
> 只要冷启动之后，重新进入app不会报错，界面也正常渲染。
>
> {color:#ff}weex_sdk:0.16.0{color} 没有这个问题。
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-331) 在手机oppo R11中weex image组件无法渲染高度超过10000px的图片
[ https://issues.apache.org/jira/browse/WEEX-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16586830#comment-16586830 ] codefurture commented on WEEX-331: -- in image adapter limit image size > 在手机oppo R11中weex image组件无法渲染高度超过1px的图片 > -- > > Key: WEEX-331 > URL: https://issues.apache.org/jira/browse/WEEX-331 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: 廖柏林 >Assignee: codefurture >Priority: Blocker > Attachments: 图片无法渲染.jpg > > > 使用image组件加载高度超过1px的图片时，图片加载并获得宽高之后并没有显示出来，出现满屏的空白。 > 手机： oppo r11 > 系统： 安卓 > demo： http://dotwe.org/vue/65f567cbb0ab11cb999c23f073fcbe5c > 经测试，weex playground app 也有此问题，期待回复！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-331) 在手机oppo R11中weex image组件无法渲染高度超过10000px的图片
[ https://issues.apache.org/jira/browse/WEEX-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-331. Resolution: Fixed > 在手机oppo R11中weex image组件无法渲染高度超过1px的图片 > -- > > Key: WEEX-331 > URL: https://issues.apache.org/jira/browse/WEEX-331 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: 廖柏林 >Assignee: codefurture >Priority: Blocker > Attachments: 图片无法渲染.jpg > > > 使用image组件加载高度超过1px的图片时，图片加载并获得宽高之后并没有显示出来，出现满屏的空白。 > 手机： oppo r11 > 系统： 安卓 > demo： http://dotwe.org/vue/65f567cbb0ab11cb999c23f073fcbe5c > 经测试，weex playground app 也有此问题，期待回复！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-568) Add Scan Delay Interface For AutoScanConfigRegister
codefurture created WEEX-568: Summary: Add Scan Delay Interface For AutoScanConfigRegister Key: WEEX-568 URL: https://issues.apache.org/jira/browse/WEEX-568 Project: Weex Issue Type: Bug Reporter: codefurture Assignee: codefurture Add Scan Delay Interface For AutoScanConfigRegister -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-526) How to implement an `wrap_content` TextView in android
[ https://issues.apache.org/jira/browse/WEEX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-526. Resolution: Fixed > How to implement an `wrap_content` TextView in android > -- > > Key: WEEX-526 > URL: https://issues.apache.org/jira/browse/WEEX-526 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 >Reporter: biaomingzhong >Assignee: codefurture >Priority: Major > > There is no document about this. > Please add some tutorials or just comment on this with some guidance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-526) How to implement an `wrap_content` TextView in android
[ https://issues.apache.org/jira/browse/WEEX-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563334#comment-16563334 ] codefurture commented on WEEX-526: -- the support by default you can se this example: http://dotwe.org/vue/cda93c88ff6b89777d467a2a817d9340 > How to implement an `wrap_content` TextView in android > -- > > Key: WEEX-526 > URL: https://issues.apache.org/jira/browse/WEEX-526 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 >Reporter: biaomingzhong >Assignee: codefurture >Priority: Major > > There is no document about this. > Please add some tutorials or just comment on this with some guidance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-466) 升级weex sdk 0.19后weex无法初始化
[ https://issues.apache.org/jira/browse/WEEX-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544880#comment-16544880 ] codefurture commented on WEEX-466: -- which 0.19 version do you use? did you compile the sdk by your self? weex playground in master runs ok. > 升级weex sdk 0.19后weex无法初始化 > - > > Key: WEEX-466 > URL: https://issues.apache.org/jira/browse/WEEX-466 > Project: Weex > Issue Type: Bug > Environment: weex sdk 0.19 ndk 15 > 直接引入的源码，没做任何修改 > 升级weex sdk 0.19后出现的问题，之前是0.11版本没有问题 >Reporter: 张波 >Assignee: Adam Feng >Priority: Major > > get NL80211_STA_INFO_CNAHLOAD > 06-20 16:43:46.401 1164-1848/? E/WificondControl: Noise: -90, Snr: 31, > Chload: -1 > 06-20 16:43:46.504 13662-13706/com.flightmanager.view E/zygote: No > implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > 06-20 16:43:46.504 13662-13706/com.flightmanager.view E/SafeRunnable: > SafeRunnable run throw expection:No implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > 06-20 16:43:46.510 13662-13706/com.flightmanager.view E/AndroidRuntime: FATAL > EXCEPTION: WeexJSBridgeThread > Process: com.flightmanager.view, PID: 13662 > java.lang.UnsatisfiedLinkError: No implementation found for void > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(boolean, > java.lang.String) (tried > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent and > Java_com_taobao_weex_bridge_WXBridge_nativeSetRenderContainerWrapContent__ZLjava_lang_String_2) > at > com.taobao.weex.bridge.WXBridge.nativeSetRenderContainerWrapContent(Native > Method) > at > com.taobao.weex.bridge.WXBridge.setRenderContainerWrapContent(WXBridge.java:497) > at > com.taobao.weex.bridge.WXBridgeManager.setRenderContentWrapContentToCore(WXBridgeManager.java:2656) > at com.taobao.weex.WXSDKInstance$2.run(WXSDKInstance.java:264) > at com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:48) > at android.os.Handler.handleCallback(Handler.java:808) > at android.os.Handler.dispatchMessage(Handler.java:101) > at android.os.Looper.loop(Looper.java:166) > at android.os.HandlerThread.run(HandlerThread.java:65) > 06-20 16:43:46.518 740-2802/? E/iMonitor: FaultDetect: DUMPTOOL_PRINTF return. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-475) fix Weex list component in the Android without scroll bars
[ https://issues.apache.org/jira/browse/WEEX-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-475. Resolution: Fixed > fix Weex list component in the Android without scroll bars > -- > > Key: WEEX-475 > URL: https://issues.apache.org/jira/browse/WEEX-475 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: aixiaoxiang >Assignee: codefurture >Priority: Major > > fix Weex list component in the Android without scroll bars > https://github.com/apache/incubator-weex/pull/1287 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-276) weex list data lost when I pull down to load more then pull up to refresh
[ https://issues.apache.org/jira/browse/WEEX-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-276. Resolution: Fixed > weex list data lost when I pull down to load more then pull up to refresh > - > > Key: WEEX-276 > URL: https://issues.apache.org/jira/browse/WEEX-276 > Project: Weex > Issue Type: Bug > Components: Android > Environment: android 设备，supportLibVersion 大于 "26.1.0"，如26.1.0 ／ > 27.0.1 都有问题 >Reporter: zhuyifei >Assignee: codefurture >Priority: Critical > > weex list > 上拉加载更多然后下拉刷新出现数据丢失，稳定重显。经过排查，发现跟supportLibVersion相关，回退到25.2.0版本就没问题了，高于26.1.0就会稳定出现。 > 附上android demo https://github.com/yifei8/android-weex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-276) weex list data lost when I pull down to load more then pull up to refresh
[ https://issues.apache.org/jira/browse/WEEX-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544866#comment-16544866 ] codefurture commented on WEEX-276: -- it bug in support library. > weex list data lost when I pull down to load more then pull up to refresh > - > > Key: WEEX-276 > URL: https://issues.apache.org/jira/browse/WEEX-276 > Project: Weex > Issue Type: Bug > Components: Android > Environment: android 设备，supportLibVersion 大于 "26.1.0"，如26.1.0 ／ > 27.0.1 都有问题 >Reporter: zhuyifei >Assignee: codefurture >Priority: Critical > > weex list > 上拉加载更多然后下拉刷新出现数据丢失，稳定重显。经过排查，发现跟supportLibVersion相关，回退到25.2.0版本就没问题了，高于26.1.0就会稳定出现。 > 附上android demo https://github.com/yifei8/android-weex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-247) list中包含scoller时卡顿
[ https://issues.apache.org/jira/browse/WEEX-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-247. Resolution: Fixed > list中包含scoller时卡顿 > - > > Key: WEEX-247 > URL: https://issues.apache.org/jira/browse/WEEX-247 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 > Environment: 安卓和ios均卡顿，安卓低端机效果更明显 >Reporter: fudongrong >Assignee: codefurture >Priority: Critical > Attachments: 1522726701.jpg > > > 在纵向List中包含横向scoller时，占用内存过大，导致页面卡顿，安卓平台较明显。代码大致如下： > :style="list_style" > loadmoreoffset="10" > @loadmore="onloadmore" > > > > scroll-direction="horizontal" > show-scrollbar="false"> > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-486) when i use navigator to implement multipage on android , OOM crash will easily happened
[ https://issues.apache.org/jira/browse/WEEX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544864#comment-16544864 ] codefurture commented on WEEX-486: -- what size of multi file package to single file? please check you file size. > when i use navigator to implement multipage on android , OOM crash will > easily happened > > > Key: WEEX-486 > URL: https://issues.apache.org/jira/browse/WEEX-486 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.19 >Reporter: fdh19979 >Assignee: codefurture >Priority: Critical > > 修改webpack，实现多页面打包，在原生每个activity或者controller中render一个JS文件 > 我发现在安卓中，使用WXFileUtils中loadAsset时，很容易在readStreamToString中出现OOM内存溢出 > 使用android profile发现，不停开启新页面的情况下，内存占用一直上升，关闭页面后，内存占用并不会下降 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-280) weex_sdk0.18.0 degradeToH5|createInstance fail|wx_create_instance_error isJSFrameworkInit==false reInitCount == 1
[
https://issues.apache.org/jira/browse/WEEX-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544863#comment-16544863
]
codefurture commented on WEEX-280:
--
you can submit code merge request on github to fix the issues, welcome joint
weex community
> weex_sdk0.18.0 degradeToH5|createInstance fail|wx_create_instance_error
> isJSFrameworkInit==false reInitCount == 1
> --
>
> Key: WEEX-280
> URL: https://issues.apache.org/jira/browse/WEEX-280
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.17, 0.18
>Reporter: aixiaoxiang
>Assignee: codefurture
>Priority: Blocker
>
> {color:#ff}weex_sdk:0.18.0{color} 在安卓下面冷启动app（切记不要加app欢迎引导页，直接进入主页）会报
> +*degradeToH5|createInstance fail|wx_create_instance_error
> isJSFrameworkInit==false reInitCount == 1*+
> 只要冷启动之后，重新进入app不会报错，界面也正常渲染。
>
> {color:#ff}weex_sdk:0.16.0{color} 没有这个问题。
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-331) 在手机oppo R11中weex image组件无法渲染高度超过10000px的图片
[ https://issues.apache.org/jira/browse/WEEX-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544860#comment-16544860 ] codefurture commented on WEEX-331: -- :) > 在手机oppo R11中weex image组件无法渲染高度超过1px的图片 > -- > > Key: WEEX-331 > URL: https://issues.apache.org/jira/browse/WEEX-331 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: 廖柏林 >Assignee: codefurture >Priority: Blocker > Attachments: 图片无法渲染.jpg > > > 使用image组件加载高度超过1px的图片时，图片加载并获得宽高之后并没有显示出来，出现满屏的空白。 > 手机： oppo r11 > 系统： 安卓 > demo： http://dotwe.org/vue/65f567cbb0ab11cb999c23f073fcbe5c > 经测试，weex playground app 也有此问题，期待回复！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-326) instanceId:, exception function:initFramework, exception:spinWaitPeer timeout
[ https://issues.apache.org/jira/browse/WEEX-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-326. Resolution: Fixed > instanceId:, exception function:initFramework, exception:spinWaitPeer timeout > - > > Key: WEEX-326 > URL: https://issues.apache.org/jira/browse/WEEX-326 > Project: Weex > Issue Type: Bug >Reporter: mjsornp >Assignee: codefurture >Priority: Major > > Sometimes found wx_create_instance_error, errCode:1001 > > Log as below: > 04-17 10:48:33.096 E/jsengine( 2213): spinWaitPeer timeout > 04-17 10:48:33.096 E/weex ( 2213): reportJSException instanceId:, > exception function:initFramework, exception:spinWaitPeer timeout > 04-17 10:48:33.096 E/weex ( 2213): reportJSException:spinWaitPeer timeout > 04-17 10:48:33.096 E/weex ( 2213): null > 04-17 10:48:33.096 E/weex ( 2213): [WXBridgeManager] invokeInitFramework > ExecuteJavaScript fail > 04-17 10:48:33.096 D/dalvikvm( 893): GC_CONCURRENT freed 567K, 85% free > 3835K/24752K, paused 308ms+39ms, total 883ms > 04-17 10:48:33.096 D/dalvikvm( 893): WAIT_FOR_CONCURRENT_GC blocked 740ms > 04-17 10:48:33.306 W/weex ( 2213): WXComponentRegistry Duplicate the Module > name: modal > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-475) fix Weex list component in the Android without scroll bars
[ https://issues.apache.org/jira/browse/WEEX-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541353#comment-16541353 ] codefurture commented on WEEX-475: -- use showScrollbar = false > fix Weex list component in the Android without scroll bars > -- > > Key: WEEX-475 > URL: https://issues.apache.org/jira/browse/WEEX-475 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: aixiaoxiang >Assignee: codefurture >Priority: Major > > fix Weex list component in the Android without scroll bars > https://github.com/apache/incubator-weex/pull/1287 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-474) Toast ,crash!
[
https://issues.apache.org/jira/browse/WEEX-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
codefurture closed WEEX-474.
Resolution: Fixed
has been fixed
> Toast ,crash!
> -
>
> Key: WEEX-474
> URL: https://issues.apache.org/jira/browse/WEEX-474
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.16, 0.18
>Reporter: 武晨
>Assignee: codefurture
>Priority: Blocker
> Fix For: 0.18
>
>
> when the app's WXInstance destroy, but Weex page call toast()，sometimes app
> crash, because null point exception *context is null !!!*, inside toast().
>
> code class *WXModalUIModule*:
> @JSMethod(uiThread = true)
> public void toast(String param) {
> String message = "";
> int duration = Toast.LENGTH_SHORT;
> if (!TextUtils.isEmpty(param)) {
> try
> { param = URLDecoder.decode(param, "utf-8"); JSONObject jsObj =
> JSON.parseObject(param); message = jsObj.getString(MESSAGE); duration =
> jsObj.getInteger(DURATION); }
> catch (Exception e)
> { WXLogUtils.e("[WXModalUIModule] alert param parse error ", e); }
> }
> if (TextUtils.isEmpty(message))
> { WXLogUtils.e("[WXModalUIModule] toast param parse is null "); return; }
> if (duration > 3)
> { duration = Toast.LENGTH_LONG; }
> else
> { duration = Toast.LENGTH_SHORT; }
> if (toast == null) {
> {color:#ff}*//crash here sometime, mWXSDKInstance.getContext() is
> null *{color}
> t*oast = Toast.makeText(mWXSDKInstance.getContext(), message, duration);*
> } else
> { toast.setDuration(duration); toast.setText(message); }
> toast.setGravity(Gravity.CENTER, 0, 0);
> toast.show();
> }
>
> ps：when weex page closed, and wxSDKInstance destroy，but weex page still
> working on background like asynchronous request(network)，on this time.when
> the request is back, and call toast()，now context is null，bug show!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (WEEX-493) How to use the latest android weex sdk version 0.18.7-beta-1
[ https://issues.apache.org/jira/browse/WEEX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541347#comment-16541347 ] codefurture edited comment on WEEX-493 at 7/12/18 8:56 AM: --- use new version, we have release new version was (Author: codefurture): use new version > How to use the latest android weex sdk version 0.18.7-beta-1 > > > Key: WEEX-493 > URL: https://issues.apache.org/jira/browse/WEEX-493 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 >Reporter: YorkGu >Assignee: codefurture >Priority: Major > > When I changed version 0.18.0 to the latest version in gradle file like this > implementation 'com.taobao.android:weex_sdk:0.18.7-beta-1' > The gradle sync failed with error: > > Unable to resolve dependency for ':app@gp2Debug/compileClasspath': Could not > find weex_sdk.jar (com.taobao.android:weex_sdk:0.18.7-beta-1). > > How to fix? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-493) How to use the latest android weex sdk version 0.18.7-beta-1
[ https://issues.apache.org/jira/browse/WEEX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-493. Resolution: Fixed > How to use the latest android weex sdk version 0.18.7-beta-1 > > > Key: WEEX-493 > URL: https://issues.apache.org/jira/browse/WEEX-493 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 >Reporter: YorkGu >Assignee: codefurture >Priority: Major > > When I changed version 0.18.0 to the latest version in gradle file like this > implementation 'com.taobao.android:weex_sdk:0.18.7-beta-1' > The gradle sync failed with error: > > Unable to resolve dependency for ':app@gp2Debug/compileClasspath': Could not > find weex_sdk.jar (com.taobao.android:weex_sdk:0.18.7-beta-1). > > How to fix? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-493) How to use the latest android weex sdk version 0.18.7-beta-1
[ https://issues.apache.org/jira/browse/WEEX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541347#comment-16541347 ] codefurture commented on WEEX-493: -- use new version > How to use the latest android weex sdk version 0.18.7-beta-1 > > > Key: WEEX-493 > URL: https://issues.apache.org/jira/browse/WEEX-493 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 >Reporter: YorkGu >Assignee: codefurture >Priority: Major > > When I changed version 0.18.0 to the latest version in gradle file like this > implementation 'com.taobao.android:weex_sdk:0.18.7-beta-1' > The gradle sync failed with error: > > Unable to resolve dependency for ':app@gp2Debug/compileClasspath': Could not > find weex_sdk.jar (com.taobao.android:weex_sdk:0.18.7-beta-1). > > How to fix? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-483) get options from arguments in callNativeModule
[ https://issues.apache.org/jira/browse/WEEX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-483. Resolution: Fixed > get options from arguments in callNativeModule > -- > > Key: WEEX-483 > URL: https://issues.apache.org/jira/browse/WEEX-483 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 >Reporter: Yayun Dong >Assignee: codefurture >Priority: Minor > Fix For: 0.18 > > > get options from arguments in callNativeModule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-494) InitFramework get params failed
[ https://issues.apache.org/jira/browse/WEEX-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541346#comment-16541346 ] codefurture commented on WEEX-494: -- please provide more details > InitFramework get params failed > --- > > Key: WEEX-494 > URL: https://issues.apache.org/jira/browse/WEEX-494 > Project: Weex > Issue Type: Task > Components: Android >Reporter: xumin >Assignee: codefurture >Priority: Major > > InitFramework get params failed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-483) get options from arguments in callNativeModule
[ https://issues.apache.org/jira/browse/WEEX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541344#comment-16541344 ] codefurture commented on WEEX-483: -- you should handle the arguments in your javascript code, not in weex sdk > get options from arguments in callNativeModule > -- > > Key: WEEX-483 > URL: https://issues.apache.org/jira/browse/WEEX-483 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 >Reporter: Yayun Dong >Assignee: codefurture >Priority: Minor > Fix For: 0.18 > > > get options from arguments in callNativeModule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-485) change the index of Slider works bad when set its 'scrollable' as 'false'
[ https://issues.apache.org/jira/browse/WEEX-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-485. Resolution: Fixed > change the index of Slider works bad when set its 'scrollable' as 'false' > - > > Key: WEEX-485 > URL: https://issues.apache.org/jira/browse/WEEX-485 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 >Reporter: billy >Assignee: codefurture >Priority: Major > > slider设置scrollable为false后，在Android平台上，通过点击导航tab切换index时slider页面切换正常，但如果用户在slider中进行横向滑动操作，再点击导航tab切换index会显示异常： > index从2切换到3时表现为切换不成功页面未切换， > index从2切换到0时表现为页面显示空白， > 再从0切换到2时，恢复正常。 > 如果用户再进行横向滑动操作，又会出现相同的情况 > --- 新增测试页面 > - > 测试页面： [http://dotwe.org/vue/df7ad923bb42464ebc5c2df388cbbcf5] > 复现步骤： > 1. 用android版playground扫描二维码打开页面 > 2. 点击red > 3. 点击yellow > 4. 横向手势滑动 > 5. 点击red（复现成功：没有切换到red） -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-486) when i use navigator to implement multipage on android , OOM crash will easily happened
[ https://issues.apache.org/jira/browse/WEEX-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541340#comment-16541340 ] codefurture commented on WEEX-486: -- multi page in single file? dou you mini js file? how large is the file? > when i use navigator to implement multipage on android , OOM crash will > easily happened > > > Key: WEEX-486 > URL: https://issues.apache.org/jira/browse/WEEX-486 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.19 >Reporter: fdh19979 >Assignee: codefurture >Priority: Critical > > 修改webpack，实现多页面打包，在原生每个activity或者controller中render一个JS文件 > 我发现在安卓中，使用WXFileUtils中loadAsset时，很容易在readStreamToString中出现OOM内存溢出 > 使用android profile发现，不停开启新页面的情况下，内存占用一直上升，关闭页面后，内存占用并不会下降 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-487) Slider控件设置scrollable="false"在android上无法禁止滑动
[
https://issues.apache.org/jira/browse/WEEX-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
codefurture closed WEEX-487.
Resolution: Fixed
has been fixed
> Slider控件设置scrollable="false"在android上无法禁止滑动
> ---
>
> Key: WEEX-487
> URL: https://issues.apache.org/jira/browse/WEEX-487
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
>Reporter: billy
>Assignee: codefurture
>Priority: Major
>
> 需求是实现一个导航tab + 多个页面进行切换，但希望禁用其滑动手势，通过导航tab切换index
> 使用Slider控件，但按照文档设置scrollable="false"在Android设备上并没有禁用滑动手势，发现网上也有人遇到同样的问题：
> [https://segmentfault.com/q/101014254067]
> 查看WXSlider的源码发现：在setScrollable方法中进行了判断：
> if(mAdapter.getRealCount() > 0) {
> mViewPager.setScrollable(scrollable);
> }
> 在刚创建的时候getRealCount()为0，所以未生效，我们现在采用的临时方案是在mounted回调函数中设置Slider的scrollable属性
> 这个mAdapter.getRealCount() > 0的判断是否可以移除呢？
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-491) navigator 是否能增加清除页面栈的方法？
[ https://issues.apache.org/jira/browse/WEEX-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541331#comment-16541331 ] codefurture commented on WEEX-491: -- [~xyyxyy1234] you should remove; which will be works ok Intent.FLAG_ACTIVITY_NEW_TASK > navigator 是否能增加清除页面栈的方法？ > > > Key: WEEX-491 > URL: https://issues.apache.org/jira/browse/WEEX-491 > Project: Weex > Issue Type: Wish > Components: Android, iOS >Reporter: weifengsmile >Assignee: codefurture >Priority: Major > Labels: easyfix > > 目前的navigator模块，做跳转时只能push，pop，open或close，并不能清除之前的页面栈，所以能不能增加这个功能，否则在某些场景，页面可能被无限push导致堆栈内存占用不断增加最终OOM > 或者说，目前有什么方案可以解决这个问题吗？ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-491) navigator 是否能增加清除页面栈的方法？
[ https://issues.apache.org/jira/browse/WEEX-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16541330#comment-16541330 ] codefurture commented on WEEX-491: -- may be we can add navigator.finish method to finish page. font developer on use broadcast channel to control finish background pages. > navigator 是否能增加清除页面栈的方法？ > > > Key: WEEX-491 > URL: https://issues.apache.org/jira/browse/WEEX-491 > Project: Weex > Issue Type: Wish > Components: Android, iOS >Reporter: weifengsmile >Assignee: codefurture >Priority: Major > Labels: easyfix > > 目前的navigator模块，做跳转时只能push，pop，open或close，并不能清除之前的页面栈，所以能不能增加这个功能，否则在某些场景，页面可能被无限push导致堆栈内存占用不断增加最终OOM > 或者说，目前有什么方案可以解决这个问题吗？ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (WEEX-502) Weex Template List Support Animation & queryElement & scrollToElement
[ https://issues.apache.org/jira/browse/WEEX-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture updated WEEX-502: - Summary: Weex Template List Support Animation & queryElement & scrollToElement (was: Weex Template List Support Animation & queryElement) > Weex Template List Support Animation & queryElement & scrollToElement > - > > Key: WEEX-502 > URL: https://issues.apache.org/jira/browse/WEEX-502 > Project: Weex > Issue Type: Bug >Reporter: codefurture >Assignee: Adam Feng >Priority: Major > > Weex Template List Support Animation & queryElement -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-502) Weex Template List Support Animation & queryElement
codefurture created WEEX-502: Summary: Weex Template List Support Animation & queryElement Key: WEEX-502 URL: https://issues.apache.org/jira/browse/WEEX-502 Project: Weex Issue Type: Bug Reporter: codefurture Assignee: Adam Feng Weex Template List Support Animation & queryElement -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (WEEX-474) Toast ,crash!
[
https://issues.apache.org/jira/browse/WEEX-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523301#comment-16523301
]
codefurture edited comment on WEEX-474 at 6/26/18 7:54 AM:
---
good suggestion, we will fix this issues.
https://github.com/apache/incubator-weex/pull/1292
was (Author: codefurture):
good suggestion, we will fix this issues
> Toast ,crash!
> -
>
> Key: WEEX-474
> URL: https://issues.apache.org/jira/browse/WEEX-474
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.16, 0.18
>Reporter: 武晨
>Assignee: codefurture
>Priority: Blocker
> Fix For: 0.18
>
>
> when the app's WXInstance destroy, but Weex page call toast()，sometimes app
> crash, because null point exception *context is null !!!*, inside toast().
>
> code class *WXModalUIModule*:
> @JSMethod(uiThread = true)
> public void toast(String param) {
> String message = "";
> int duration = Toast.LENGTH_SHORT;
> if (!TextUtils.isEmpty(param)) {
> try
> { param = URLDecoder.decode(param, "utf-8"); JSONObject jsObj =
> JSON.parseObject(param); message = jsObj.getString(MESSAGE); duration =
> jsObj.getInteger(DURATION); }
> catch (Exception e)
> { WXLogUtils.e("[WXModalUIModule] alert param parse error ", e); }
> }
> if (TextUtils.isEmpty(message))
> { WXLogUtils.e("[WXModalUIModule] toast param parse is null "); return; }
> if (duration > 3)
> { duration = Toast.LENGTH_LONG; }
> else
> { duration = Toast.LENGTH_SHORT; }
> if (toast == null) {
> {color:#ff}*//crash here sometime, mWXSDKInstance.getContext() is
> null *{color}
> t*oast = Toast.makeText(mWXSDKInstance.getContext(), message, duration);*
> } else
> { toast.setDuration(duration); toast.setText(message); }
> toast.setGravity(Gravity.CENTER, 0, 0);
> toast.show();
> }
>
> ps：when weex page closed, and wxSDKInstance destroy，but weex page still
> working on background like asynchronous request(network)，on this time.when
> the request is back, and call toast()，now context is null，bug show!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-474) Toast ,crash!
[
https://issues.apache.org/jira/browse/WEEX-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523301#comment-16523301
]
codefurture commented on WEEX-474:
--
good suggestion, we will fix this issues
> Toast ,crash!
> -
>
> Key: WEEX-474
> URL: https://issues.apache.org/jira/browse/WEEX-474
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.16, 0.18
>Reporter: 武晨
>Assignee: codefurture
>Priority: Blocker
> Fix For: 0.18
>
>
> when the app's WXInstance destroy, but Weex page call toast()，sometimes app
> crash, because null point exception *context is null !!!*, inside toast().
>
> code class *WXModalUIModule*:
> @JSMethod(uiThread = true)
> public void toast(String param) {
> String message = "";
> int duration = Toast.LENGTH_SHORT;
> if (!TextUtils.isEmpty(param)) {
> try
> { param = URLDecoder.decode(param, "utf-8"); JSONObject jsObj =
> JSON.parseObject(param); message = jsObj.getString(MESSAGE); duration =
> jsObj.getInteger(DURATION); }
> catch (Exception e)
> { WXLogUtils.e("[WXModalUIModule] alert param parse error ", e); }
> }
> if (TextUtils.isEmpty(message))
> { WXLogUtils.e("[WXModalUIModule] toast param parse is null "); return; }
> if (duration > 3)
> { duration = Toast.LENGTH_LONG; }
> else
> { duration = Toast.LENGTH_SHORT; }
> if (toast == null) {
> {color:#ff}*//crash here sometime, mWXSDKInstance.getContext() is
> null *{color}
> t*oast = Toast.makeText(mWXSDKInstance.getContext(), message, duration);*
> } else
> { toast.setDuration(duration); toast.setText(message); }
> toast.setGravity(Gravity.CENTER, 0, 0);
> toast.show();
> }
>
> ps：when weex page closed, and wxSDKInstance destroy，but weex page still
> working on background like asynchronous request(network)，on this time.when
> the request is back, and call toast()，now context is null，bug show!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-469) weex list component in the Android has no scroll bars
[ https://issues.apache.org/jira/browse/WEEX-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523067#comment-16523067 ] codefurture commented on WEEX-469: -- you can use showScrollbar="true" the let the scroll bar show. example like this: > weex list component in the Android has no scroll bars > - > > Key: WEEX-469 > URL: https://issues.apache.org/jira/browse/WEEX-469 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: aixiaoxiang >Assignee: codefurture >Priority: Major > Attachments: image-2018-06-21-12-22-09-211.png > > > weex list component in the Android has no scroll bars > iOS has scroll bars > android: > > !image-2018-06-21-12-22-09-211.png|thumbnail! > Related link: > https://stackoverflow.com/questions/27056379/is-there-any-way-to-enable-scrollbars-for-recyclerview-in-code -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-435) Weex Android Playground app DO NOT prompt permission dialog when user clicked
[ https://issues.apache.org/jira/browse/WEEX-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523065#comment-16523065 ] codefurture commented on WEEX-435: -- in your onRequestPermissionsResult you don't handle WRITE_EXTERNAL_STORAGE_PERMISSION_REQUEST_CODE and give an tips. please add this case. when we will merge the request > Weex Android Playground app DO NOT prompt permission dialog when user clicked > - > > Key: WEEX-435 > URL: https://issues.apache.org/jira/browse/WEEX-435 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 >Reporter: Shen >Assignee: codefurture >Priority: Major > > As I've created a PR, please see > [https://github.com/apache/incubator-weex/pull/1221#issue-191124184] for more > info about this issue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-424) Support SVG in
[ https://issues.apache.org/jira/browse/WEEX-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture resolved WEEX-424. -- Resolution: Workaround > Support SVG in > -- > > Key: WEEX-424 > URL: https://issues.apache.org/jira/browse/WEEX-424 > Project: Weex > Issue Type: New Feature > Components: Android >Affects Versions: 0.18 >Reporter: Francis >Assignee: codefurture >Priority: Major > > SVG format is best for icons and graphics and are scalable to different > resolutions. > Also, they are often smaller in file size compared to raster formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-424) Support SVG in
[ https://issues.apache.org/jira/browse/WEEX-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523062#comment-16523062 ] codefurture commented on WEEX-424: -- we have an svg plugin in alibaba's aliweex components, which will be open source latter > Support SVG in > -- > > Key: WEEX-424 > URL: https://issues.apache.org/jira/browse/WEEX-424 > Project: Weex > Issue Type: New Feature > Components: Android >Affects Versions: 0.18 >Reporter: Francis >Assignee: codefurture >Priority: Major > > SVG format is best for icons and graphics and are scalable to different > resolutions. > Also, they are often smaller in file size compared to raster formats. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-409) weex页面白屏检测和分析
[ https://issues.apache.org/jira/browse/WEEX-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-409. Resolution: Fixed > weex页面白屏检测和分析 > - > > Key: WEEX-409 > URL: https://issues.apache.org/jira/browse/WEEX-409 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.17 >Reporter: ou >Assignee: codefurture >Priority: Major > > 我们针对weex的渲染做了白屏上报，集成的是sdk 0.17.0，发现异常回调还是蛮多的，主要错误是以下五个： > 第一种：错误占比60.8%，检测方式是我们在onViewCreated中延时一秒检测渲染的view是否存在元素，如果不存在则上报异常；这样的检测是否存在问题和误报？ > 第二种：错误占比10.2%，wx_network_error，这种的存在也蛮多的，这种是js文件访问不到，还是js的内部请求（如图片等请求不到）导致的异常呢？ > 第三种：错误占比8.8%，调用js异常：返回的错误信息是：ReferenceError: Can't find variable: > event\n(global function):13:25438\n(weex framework):3:30993\nforEach@[native > code]\np@(weex framework):3:30892\n(weex framework):8:26566\n template md5 > null 这种要怎么解决呢？ > 第四种：错误占比8.4%，wx_create_instance_error，这种的日志只有createInstance > fail，这种情况需要怎么定位分析呢？ > 第五种：错误占比5.6%，wx_network_error ，Unable to resolve host \"XXX域名": No address > associated with hostname ，这种情况是什么原因导致的呢？这个域名应该是可以访问到的。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (WEEX-342) The index attribute of the slider component does not work on Android.
[ https://issues.apache.org/jira/browse/WEEX-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture reassigned WEEX-342: Assignee: codefurture (was: YorkShen) > The index attribute of the slider component does not work on Android. > - > > Key: WEEX-342 > URL: https://issues.apache.org/jira/browse/WEEX-342 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 >Reporter: 杜相国 >Assignee: codefurture >Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (WEEX-408) measure func not right recyclelist update measure function
[ https://issues.apache.org/jira/browse/WEEX-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture updated WEEX-408: - Summary: measure func not right recyclelist update measure function (was: measure func在recyclelist上显示异常，功能回滚) > measure func not right recyclelist update measure function > -- > > Key: WEEX-408 > URL: https://issues.apache.org/jira/browse/WEEX-408 > Project: Weex > Issue Type: Bug >Reporter: jike >Assignee: Adam Feng >Priority: Major > > measure func功能回滚 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-396) Android project setup failed with error - Gradle sync failed: A problem occurred configuring project ':weex_sdk'.
[ https://issues.apache.org/jira/browse/WEEX-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488376#comment-16488376 ] codefurture commented on WEEX-396: -- pease install ndk bundle > Android project setup failed with error - Gradle sync failed: A problem > occurred configuring project ':weex_sdk'. > -- > > Key: WEEX-396 > URL: https://issues.apache.org/jira/browse/WEEX-396 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: Shikha >Assignee: codefurture >Priority: Major > > While setting up incubator-weex Android project, I followed the steps in > README.md. It resulted in the build error - Gradle sync failed: A problem > occurred configuring project ':weex_sdk'. > Consult IDE log for more details (Help | Show Log) (2s 858ms). > Android studio version - 3.1.2 > Gradle version - 4.4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-359) weex init fail
[ https://issues.apache.org/jira/browse/WEEX-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482317#comment-16482317 ] codefurture commented on WEEX-359: -- you can build custom sdk with master source, @ h3. *[YorkShen|https://github.com/YorkShen]* > weex init fail > -- > > Key: WEEX-359 > URL: https://issues.apache.org/jira/browse/WEEX-359 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: fudongrong >Assignee: codefurture >Priority: Major > Attachments: 1526278267(1).jpg, 1526541856(1).jpg, 1526541871(1).jpg > > > when i use weex of gradle import ways.just like this: >compile 'com.taobao.android:weex_sdk:0.18.7-beta-1@aar' > but the weex initial fail,and my app is crash.the simple of error is: > java.lang.NoClassDefFoundError: Failed resolution of: > Lorg/jacoco/agent/rt/internal_b0d6a23/Offline > all detail look for the attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482257#comment-16482257
]
codefurture commented on WEEX-279:
--
!image-2018-05-21-15-26-19-427.png!
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: codefurture
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4
> {code}
> 我尝试根据 ’GitHub Pull Request #1102‘ 去修改对应的文件，当前组件的循环确实可以正常运行，
> *但是* 如果当前组件下有{color:#FF}带有循环的子组件{color}时，问题依旧存在
> {code:java}
> // index.vue
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482256#comment-16482256
]
codefurture commented on WEEX-279:
--
!image-2018-05-21-15-26-01-400.png!
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: codefurture
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4
> {code}
> 我尝试根据 ’GitHub Pull Request #1102‘ 去修改对应的文件，当前组件的循环确实可以正常运行，
> *但是* 如果当前组件下有{color:#FF}带有循环的子组件{color}时，问题依旧存在
> {code:java}
> // index.vue
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-359) weex init fail
[ https://issues.apache.org/jira/browse/WEEX-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478485#comment-16478485 ] codefurture commented on WEEX-359: -- use [0.18.0|https://bintray.com/alibabaweex/maven/weex_sdk/0.18.0] release version @yugan please see the new version issules > weex init fail > -- > > Key: WEEX-359 > URL: https://issues.apache.org/jira/browse/WEEX-359 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: fudongrong >Assignee: codefurture >Priority: Major > Attachments: 1526278267(1).jpg > > > when i use weex of gradle import ways.just like this: >compile 'com.taobao.android:weex_sdk:0.18.7-beta-1@aar' > but the weex initial fail,and my app is crash.the simple of error is: > java.lang.NoClassDefFoundError: Failed resolution of: > Lorg/jacoco/agent/rt/internal_b0d6a23/Offline > all detail look for the attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-367) android P兼容
[ https://issues.apache.org/jira/browse/WEEX-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477128#comment-16477128 ] codefurture commented on WEEX-367: -- weex runing ok on android P, can you provide which module you call? or which api your call, please give more information > android P兼容 > --- > > Key: WEEX-367 > URL: https://issues.apache.org/jira/browse/WEEX-367 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: owenli >Assignee: codefurture >Priority: Blocker > Attachments: WechatIMG28.jpeg, cdf6c5a081fa2662ced71b6f99fada1.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
codefurture resolved WEEX-279.
--
Resolution: Fixed
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: Adam Feng
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4
> {code}
> 我尝试根据 ’GitHub Pull Request #1102‘ 去修改对应的文件，当前组件的循环确实可以正常运行，
> *但是* 如果当前组件下有{color:#FF}带有循环的子组件{color}时，问题依旧存在
> {code:java}
> // index.vue
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (WEEX-355) recycle-list adapter for weex-core new architecture
codefurture created WEEX-355: Summary: recycle-list adapter for weex-core new architecture Key: WEEX-355 URL: https://issues.apache.org/jira/browse/WEEX-355 Project: Weex Issue Type: Bug Components: Android Reporter: codefurture Assignee: Adam Feng recycle-list adapter for weex-core architecture -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-336) recycle-list 数据变动 页面抖动厉害
[ https://issues.apache.org/jira/browse/WEEX-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465444#comment-16465444 ] codefurture commented on WEEX-336: -- can you provide a link to repeat the scene? show you update data? do you update data via setListData ? please provide a link example on http://dotwe.org/vue > recycle-list 数据变动 页面抖动厉害 > > > Key: WEEX-336 > URL: https://issues.apache.org/jira/browse/WEEX-336 > Project: Weex > Issue Type: Bug > Components: Android, iOS >Affects Versions: 0.18 >Reporter: dadatang >Assignee: xingZhang >Priority: Major > Original Estimate: 12h > Remaining Estimate: 12h > > recycle-list 遍历数据 渲染列表, 当数据发送变动时,页面有明显的闪动情况 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-332) framework.js uninitialized
[
https://issues.apache.org/jira/browse/WEEX-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463439#comment-16463439
]
codefurture commented on WEEX-332:
--
weex only has x86 and armeabi so. if your has others platform so, which will
cause so file not fount when load so. just remove others, which will works ok
for all android devices
> framework.js uninitialized
> --
>
> Key: WEEX-332
> URL: https://issues.apache.org/jira/browse/WEEX-332
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
>Reporter: fudongrong
>Assignee: Adam Feng
>Priority: Major
>
> my app's build gradle's ndk is:
>
> ndk {
>abiFilters "armeabi-v7a", "x86", "armeabi", "mips"
> }
> and we use weex sdk 0.18.0，but it was not use，it seems like framework.js
> uninitialized，
> the error log is
> {color:#d04437}[WXinvokeRegisterModulesBridgeManager] invokeRegisterModules:
> framework.js uninitialized.
> [WXBridgeManager] invokeRegisterComponents: framework.js uninitialized.{color}
> what should i do? very critical
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (WEEX-331) 在手机oppo R11中weex image组件无法渲染高度超过10000px的图片
[ https://issues.apache.org/jira/browse/WEEX-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463294#comment-16463294 ] codefurture edited comment on WEEX-331 at 5/4/18 2:21 AM: -- is your image link is ok. i check on the browser which the image link is wrong, cann't se the image link was (Author: codefurture): is your image link is ok. i check on the browser which the image link is wrong > 在手机oppo R11中weex image组件无法渲染高度超过1px的图片 > -- > > Key: WEEX-331 > URL: https://issues.apache.org/jira/browse/WEEX-331 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: 廖柏林 >Assignee: Adam Feng >Priority: Blocker > Attachments: 图片无法渲染.jpg > > > 使用image组件加载高度超过1px的图片时，图片加载并获得宽高之后并没有显示出来，出现满屏的空白。 > 手机： oppo r11 > 系统： 安卓 > demo： [http://dotwe.org/vue/11f71d5048406e148586368dec516c59] > 经测试，weex playground app 也有此问题，期待回复！ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-332) framework.js uninitialized
[
https://issues.apache.org/jira/browse/WEEX-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463293#comment-16463293
]
codefurture commented on WEEX-332:
--
edit \{ abiFilters "armeabi-v7a", "x86", "armeabi", "mips" } to \{ abiFilters
"armeabi"} which will works ok.
when you set many abiFilters, you should make sure that all the so file has
every target abi
> framework.js uninitialized
> --
>
> Key: WEEX-332
> URL: https://issues.apache.org/jira/browse/WEEX-332
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
>Reporter: fudongrong
>Assignee: Adam Feng
>Priority: Major
>
> my app's build gradle's ndk is:
>
> ndk {
>abiFilters "armeabi-v7a", "x86", "armeabi", "mips"
> }
> and we use weex sdk 0.18.0，but it was not use，it seems like framework.js
> uninitialized，
> the error log is
> {color:#d04437}[WXinvokeRegisterModulesBridgeManager] invokeRegisterModules:
> framework.js uninitialized.
> [WXBridgeManager] invokeRegisterComponents: framework.js uninitialized.{color}
> what should i do? very critical
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (WEEX-299) Touch event will transmit to next layer
[
https://issues.apache.org/jira/browse/WEEX-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456115#comment-16456115
]
codefurture edited comment on WEEX-299 at 4/27/18 8:49 AM:
---
i know your issues. the stopPropagation should be reset eveny touch. i will
fix the issues。 the issued has been fixed in this pull request:
https://github.com/apache/incubator-weex/pull/1138
was (Author: codefurture):
i know your issues. the stopPropagation should be reset eveny touch. i will
fix the issues later in today
> Touch event will transmit to next layer
> ---
>
> Key: WEEX-299
> URL: https://issues.apache.org/jira/browse/WEEX-299
> Project: Weex
> Issue Type: Bug
>Reporter: quanyun wei
>Assignee: Adam Feng
>Priority: Critical
>
> This is the test demo in
> [dotwe|[http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464]|http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464],]
> when touch the text, the div will also response the touch event.
> {code:java}
> //代码占位符
>
> ontouchcancel='ontouchcancel' ontouchend="ontouchend"
> @touchstart="ontouchstart" @touchmove="ontouchmove" @touchend="ontouchend"
> @shouldStopPropagation="shouldStopPropagation"
> >{{forceValue}}
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-299) Touch event will transmit to next layer
[
https://issues.apache.org/jira/browse/WEEX-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456115#comment-16456115
]
codefurture commented on WEEX-299:
--
i know your issues. the stopPropagation should be reset event touch. i will
fix the issues later in today
> Touch event will transmit to next layer
> ---
>
> Key: WEEX-299
> URL: https://issues.apache.org/jira/browse/WEEX-299
> Project: Weex
> Issue Type: Bug
>Reporter: quanyun wei
>Assignee: Adam Feng
>Priority: Critical
>
> This is the test demo in
> [dotwe|[http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464]|http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464],]
> when touch the text, the div will also response the touch event.
> {code:java}
> //代码占位符
>
> ontouchcancel='ontouchcancel' ontouchend="ontouchend"
> @touchstart="ontouchstart" @touchmove="ontouchmove" @touchend="ontouchend"
> @shouldStopPropagation="shouldStopPropagation"
> >{{forceValue}}
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (WEEX-299) Touch event will transmit to next layer
[
https://issues.apache.org/jira/browse/WEEX-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456115#comment-16456115
]
codefurture edited comment on WEEX-299 at 4/27/18 8:40 AM:
---
i know your issues. the stopPropagation should be reset eveny touch. i will
fix the issues later in today
was (Author: codefurture):
i know your issues. the stopPropagation should be reset event touch. i will
fix the issues later in today
> Touch event will transmit to next layer
> ---
>
> Key: WEEX-299
> URL: https://issues.apache.org/jira/browse/WEEX-299
> Project: Weex
> Issue Type: Bug
>Reporter: quanyun wei
>Assignee: Adam Feng
>Priority: Critical
>
> This is the test demo in
> [dotwe|[http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464]|http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464],]
> when touch the text, the div will also response the touch event.
> {code:java}
> //代码占位符
>
> ontouchcancel='ontouchcancel' ontouchend="ontouchend"
> @touchstart="ontouchstart" @touchmove="ontouchmove" @touchend="ontouchend"
> @shouldStopPropagation="shouldStopPropagation"
> >{{forceValue}}
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-299) Touch event will transmit to next layer
[
https://issues.apache.org/jira/browse/WEEX-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456084#comment-16456084
]
codefurture commented on WEEX-299:
--
stopPropagation means the touch event should stop propagation on response
chain. when it return true, the parent will not receive touch event. if it
return false, the parent will receive touch event.
> Touch event will transmit to next layer
> ---
>
> Key: WEEX-299
> URL: https://issues.apache.org/jira/browse/WEEX-299
> Project: Weex
> Issue Type: Bug
>Reporter: quanyun wei
>Assignee: Adam Feng
>Priority: Critical
>
> This is the test demo in
> [dotwe|[http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464]|http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464],]
> when touch the text, the div will also response the touch event.
> {code:java}
> //代码占位符
>
> ontouchcancel='ontouchcancel' ontouchend="ontouchend"
> @touchstart="ontouchstart" @touchmove="ontouchmove" @touchend="ontouchend"
> @shouldStopPropagation="shouldStopPropagation"
> >{{forceValue}}
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (WEEX-317) v-if 指令处理有问题，还是布局引擎有问题？
[ https://issues.apache.org/jira/browse/WEEX-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture updated WEEX-317: - Comment: was deleted (was: provide a link?) > v-if 指令处理有问题，还是布局引擎有问题？ > --- > > Key: WEEX-317 > URL: https://issues.apache.org/jira/browse/WEEX-317 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: aixiaoxiang >Assignee: Adam Feng >Priority: Major > Attachments: image-2018-04-27-14-10-32-611.png > > > !image-2018-04-27-14-10-32-611.png! > 图片是存在的 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-299) Touch event will transmit to next layer
[
https://issues.apache.org/jira/browse/WEEX-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456071#comment-16456071
]
codefurture commented on WEEX-299:
--
if you don't want div receive touchstart event, in your function return true,
to stop touch event propagation. the example is like this:
http://dotwe.org/vue/e03984d688351b9fd985b8c291804d49
> Touch event will transmit to next layer
> ---
>
> Key: WEEX-299
> URL: https://issues.apache.org/jira/browse/WEEX-299
> Project: Weex
> Issue Type: Bug
>Reporter: quanyun wei
>Assignee: Adam Feng
>Priority: Critical
>
> This is the test demo in
> [dotwe|[http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464]|http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464],]
> when touch the text, the div will also response the touch event.
> {code:java}
> //代码占位符
>
> ontouchcancel='ontouchcancel' ontouchend="ontouchend"
> @touchstart="ontouchstart" @touchmove="ontouchmove" @touchend="ontouchend"
> @shouldStopPropagation="shouldStopPropagation"
> >{{forceValue}}
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-299) Touch event will transmit to next layer
[
https://issues.apache.org/jira/browse/WEEX-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456067#comment-16456067
]
codefurture commented on WEEX-299:
--
the old version use shouldStopPropagation when beta, when release it become
short name, stopPropagation.
> Touch event will transmit to next layer
> ---
>
> Key: WEEX-299
> URL: https://issues.apache.org/jira/browse/WEEX-299
> Project: Weex
> Issue Type: Bug
>Reporter: quanyun wei
>Assignee: Adam Feng
>Priority: Critical
>
> This is the test demo in
> [dotwe|[http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464]|http://dotwe.org/vue/d269c46eabb5da4bda6c8ac91a11c464],]
> when touch the text, the div will also response the touch event.
> {code:java}
> //代码占位符
>
> ontouchcancel='ontouchcancel' ontouchend="ontouchend"
> @touchstart="ontouchstart" @touchmove="ontouchmove" @touchend="ontouchend"
> @shouldStopPropagation="shouldStopPropagation"
> >{{forceValue}}
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-317) v-if 指令处理有问题，还是布局引擎有问题？
[ https://issues.apache.org/jira/browse/WEEX-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456061#comment-16456061 ] codefurture commented on WEEX-317: -- [http://dotwe.org/vue/585bcca12ebf26f0506ca8ef45459da9] i test on this demo which works ok. your image is black ? maybe check your src and your image library support load it . > v-if 指令处理有问题，还是布局引擎有问题？ > --- > > Key: WEEX-317 > URL: https://issues.apache.org/jira/browse/WEEX-317 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: aixiaoxiang >Assignee: Adam Feng >Priority: Major > Attachments: image-2018-04-27-14-10-32-611.png > > > !image-2018-04-27-14-10-32-611.png! > 图片是存在的 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-317) v-if 指令处理有问题，还是布局引擎有问题？
[ https://issues.apache.org/jira/browse/WEEX-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16455996#comment-16455996 ] codefurture commented on WEEX-317: -- provide a link? > v-if 指令处理有问题，还是布局引擎有问题？ > --- > > Key: WEEX-317 > URL: https://issues.apache.org/jira/browse/WEEX-317 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: aixiaoxiang >Assignee: Adam Feng >Priority: Major > Attachments: image-2018-04-27-14-10-32-611.png > > > !image-2018-04-27-14-10-32-611.png! > 图片是存在的 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-281) Supported ZIndex Feature
codefurture created WEEX-281: Summary: Supported ZIndex Feature Key: WEEX-281 URL: https://issues.apache.org/jira/browse/WEEX-281 Project: Weex Issue Type: Improvement Components: Android, iOS Reporter: codefurture Assignee: xingZhang Supported ZIndex Feature -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429583#comment-16429583
]
codefurture commented on WEEX-279:
--
please give an example, sub component context is isolated render context.
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: Adam Feng
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4
> {code}
> 我尝试根据 ’GitHub Pull Request #1102‘ 去修改对应的文件，当前组件的循环确实可以正常运行，
> *但是* 如果当前组件下有{color:#FF}带有循环的子组件{color}时，问题依旧存在
> {code:java}
> // index.vue
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429307#comment-16429307
]
codefurture commented on WEEX-279:
--
please send one link in dotwe.org com
谷宝剑
邮箱：gubaoj...@163.com
签名由 网易邮箱大师 定制
在2018年04月07日 17:33，Zisong Lu (JIRA) 写道：
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zisong Lu updated WEEX-279:
---
Description:
安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
{code:java}
{{n}} -- {{k}}
export default {
data () {
return {
lists: [
{ ts: ['零', '一', '二', '三', '四'] }
]
}
}
}
// 显示结果
//
// 安卓: 零 -- 0ios: 零 -- 0
// 安卓: 一 -- 0ios: 一 -- 1
// 安卓: 二 -- 0ios: 二 -- 2
// 安卓: 三 -- 0ios: 三 -- 3
// 安卓: 四 -- 0ios: 四 -- 4
{code}
我尝试根据 ’GitHub Pull Request #1102‘ 去修改对应的文件，当前组件的循环确实可以正常运行，
*但是* 如果当前组件下有{color:#FF}带有循环的子组件{color}时，问题依旧存在
{code:java}
// index.vue
{code}
was:
安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
{code:java}
{{n}} -- {{k}}
export default {
data () {
return {
lists: [
{ ts: ['零', '一', '二', '三', '四'] }
]
}
}
}
// 显示结果
//
// 安卓: 零 -- 0ios: 零 -- 0
// 安卓: 一 -- 0ios: 一 -- 1
// 安卓: 二 -- 0ios: 二 -- 2
// 安卓: 三 -- 0ios: 三 -- 3
// 安卓: 四 -- 0ios: 四 -- 4
{code}
我尝试根据 ’‘
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: Adam Feng
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4
> {code}
> 我尝试根据 ’GitHub Pull Request #1102‘ 去修改对应的文件，当前组件的循环确实可以正常运行，
> *但是* 如果当前组件下有{color:#FF}带有循环的子组件{color}时，问题依旧存在
> {code:java}
> // index.vue
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428350#comment-16428350
]
codefurture commented on WEEX-279:
--
https://github.com/apache/incubator-weex/pull/1102
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: Adam Feng
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4 {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-279) recycle-list 组件下的多重循环 错误
[
https://issues.apache.org/jira/browse/WEEX-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428346#comment-16428346
]
codefurture commented on WEEX-279:
--
i have find this issues loop index not ++ and fix it.
> recycle-list 组件下的多重循环 错误
>
>
> Key: WEEX-279
> URL: https://issues.apache.org/jira/browse/WEEX-279
> Project: Weex
> Issue Type: Bug
> Components: Android
>Affects Versions: 0.18
> Environment: Weex SDK Version
> 0.18.0-beta-3
> JS Framework 0.24.5
> platform android
> osVersion 5.1
> deviceModel m1 metal
>Reporter: Zisong Lu
>Assignee: Adam Feng
>Priority: Blocker
>
> 安卓环境 组件下的 v-for = "(xx, index) in xxx 循环" ， index 无法取得 （ios 正常）
> {code:java}
>
>
>
>
> {{n}} -- {{k}}
>
>
>
>
>
> export default {
> data () {
> return {
> lists: [
> { ts: ['零', '一', '二', '三', '四'] }
> ]
> }
> }
> }
>
> // 显示结果
> //
> // 安卓: 零 -- 0ios: 零 -- 0
> // 安卓: 一 -- 0ios: 一 -- 1
> // 安卓: 二 -- 0ios: 二 -- 2
> // 安卓: 三 -- 0ios: 三 -- 3
> // 安卓: 四 -- 0ios: 四 -- 4 {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-247) list中包含scoller时卡顿
[ https://issues.apache.org/jira/browse/WEEX-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425351#comment-16425351 ] codefurture commented on WEEX-247: -- http://dotwe.org/vue/7aa9f8be7d205a617aedd912f7dfa429 > list中包含scoller时卡顿 > - > > Key: WEEX-247 > URL: https://issues.apache.org/jira/browse/WEEX-247 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 > Environment: 安卓和ios均卡顿，安卓低端机效果更明显 >Reporter: fudongrong >Assignee: zhengshihan >Priority: Critical > Attachments: 1522726701.jpg > > > 在纵向List中包含横向scoller时，占用内存过大，导致页面卡顿，安卓平台较明显。代码大致如下： > :style="list_style" > loadmoreoffset="10" > @loadmore="onloadmore" > > > > scroll-direction="horizontal" > show-scrollbar="false"> > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-273) The application may be doing too much work on its main thread
[ https://issues.apache.org/jira/browse/WEEX-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425343#comment-16425343 ] codefurture commented on WEEX-273: -- when spa will lead too many views, when you change to page 2, remove page one node and state > The application may be doing too much work on its main thread > - > > Key: WEEX-273 > URL: https://issues.apache.org/jira/browse/WEEX-273 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: platform:android > version:5.1.0 > weex version:0.18.0-beta-2 >Reporter: mjsornp >Assignee: zhengshihan >Priority: Critical > > our android platform operate step as below: > # weex page（SPA mode, page 1） start anothor APK to scan QR code > # another APK scan QR code and then finish() > # weex onActivityResult invoke jsCallBack to show QR code content in weex > page(SPA mode, page2) > # The weex page2 sometimes display slow after another APK scan code > Activity has finished. > > The android log show: > Choreographer: Skipped 37 frames! The application may be doing too much work > on its main thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-276) weex list data lost when I pull down to load more then pull up to refresh
[ https://issues.apache.org/jira/browse/WEEX-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425342#comment-16425342 ] codefurture commented on WEEX-276: -- get the issues, we will have a try and fix it after qingming holiday > weex list data lost when I pull down to load more then pull up to refresh > - > > Key: WEEX-276 > URL: https://issues.apache.org/jira/browse/WEEX-276 > Project: Weex > Issue Type: Bug > Components: Android > Environment: android 设备，supportLibVersion 大于 "26.1.0"，如26.1.0 ／ > 27.0.1 都有问题 >Reporter: zhuyifei >Assignee: Adam Feng >Priority: Critical > > weex list > 上拉加载更多然后下拉刷新出现数据丢失，稳定重显。经过排查，发现跟supportLibVersion相关，回退到25.2.0版本就没问题了，高于26.1.0就会稳定出现。 > 附上android demo https://github.com/yifei8/android-weex -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-278) Android中readerByUrl的默认超时为3秒，请开放设置接口
[ https://issues.apache.org/jira/browse/WEEX-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425341#comment-16425341 ] codefurture commented on WEEX-278: -- config it when native application init > Android中readerByUrl的默认超时为3秒，请开放设置接口 > --- > > Key: WEEX-278 > URL: https://issues.apache.org/jira/browse/WEEX-278 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18 >Reporter: chen wu >Assignee: Adam Feng >Priority: Major > Fix For: 0.18 > > > 在android中，网络访问js， > DefaultWXHttpAdapter默认超时3秒，可不可以发开这个设置通过配置进行修改 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-224) WXDomObject Destory Method Should Be Called AVoid Memory Leak
[ https://issues.apache.org/jira/browse/WEEX-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture closed WEEX-224. has been close > WXDomObject Destory Method Should Be Called AVoid Memory Leak > - > > Key: WEEX-224 > URL: https://issues.apache.org/jira/browse/WEEX-224 > Project: Weex > Issue Type: Improvement > Components: Android >Reporter: codefurture >Assignee: zhengshihan >Priority: Minor > > WXDomObject Destory Method Should Be Called, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-247) list中包含scoller时卡顿
[ https://issues.apache.org/jira/browse/WEEX-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423418#comment-16423418 ] codefurture commented on WEEX-247: -- list add and direction > list中包含scoller时卡顿 > - > > Key: WEEX-247 > URL: https://issues.apache.org/jira/browse/WEEX-247 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 > Environment: 安卓和ios均卡顿，安卓低端机效果更明显 >Reporter: fudongrong >Assignee: zhengshihan >Priority: Critical > > 在纵向List中包含横向scoller时，占用内存过大，导致页面卡顿，安卓平台较明显。代码大致如下： > :style="list_style" > loadmoreoffset="10" > @loadmore="onloadmore" > > > > scroll-direction="horizontal" > show-scrollbar="false"> > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-224) WXDomObject Destory Method Should Be Called AVoid Memory Leak
[ https://issues.apache.org/jira/browse/WEEX-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture resolved WEEX-224. -- Resolution: Fixed > WXDomObject Destory Method Should Be Called AVoid Memory Leak > - > > Key: WEEX-224 > URL: https://issues.apache.org/jira/browse/WEEX-224 > Project: Weex > Issue Type: Improvement > Components: Android >Reporter: codefurture >Assignee: zhengshihan >Priority: Minor > > WXDomObject Destory Method Should Be Called, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-248) slide中嵌套list，在小米手机上list滑动事件失效
[ https://issues.apache.org/jira/browse/WEEX-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414969#comment-16414969 ] codefurture commented on WEEX-248: -- use recyclerview which is better > slide中嵌套list，在小米手机上list滑动事件失效 > - > > Key: WEEX-248 > URL: https://issues.apache.org/jira/browse/WEEX-248 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: 小米note、小米4 安卓7.1 >Reporter: fudongrong >Assignee: zhengshihan >Priority: Blocker > > 当slide的每个项都是list时，slide第一个项中的list完全正常，但是切换到第二项时，该项中的List显示不完全，也不能向下滑动。华为手机没有该问题，猜测是小米手机上滑动事件冲突或者是封装的时候list高度没有重新计算，导致只显示了一页并且滑动不了。大致代码如下,其中myactivity > 是我们自己封装的纵向list： > > :index="group_current" > :style="group_style" > infinite="false" > @change="groupChange" > > > > > :cur_index="sidebar_current" > :list_style="list_style" > :ref="'gp-' + i" > @refreshSidebar="refreshSidebar" > /> > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (WEEX-221) Can I use wx in my project
[
https://issues.apache.org/jira/browse/WEEX-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414931#comment-16414931
]
codefurture edited comment on WEEX-221 at 3/27/18 2:49 AM:
---
yes, this is equals 88 dp, please has suffix wx unit
was (Author: codefurture):
yes, this is equals 88 dp
> Can I use wx in my project
> --
>
> Key: WEEX-221
> URL: https://issues.apache.org/jira/browse/WEEX-221
> Project: Weex
> Issue Type: Wish
> Components: Project
>Reporter: Xu XiaoTeng
>Assignee: zhengshihan
>Priority: Critical
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I want to find an absolute css unit to show some ui element, then I found wx
> unit is possible to implement this function. But there's some warning at
> Android App running. (The wx unit is about to deprecated in the future.)
> I know there is a faq explain this issue:
> {code:java}
> var height = 88 * 750 / env.deviceWidth{code}
> Is there a simple way to implement this function?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-221) Can I use wx in my project
[
https://issues.apache.org/jira/browse/WEEX-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414931#comment-16414931
]
codefurture commented on WEEX-221:
--
yes, this is equals 88 dp
> Can I use wx in my project
> --
>
> Key: WEEX-221
> URL: https://issues.apache.org/jira/browse/WEEX-221
> Project: Weex
> Issue Type: Wish
> Components: Project
>Reporter: Xu XiaoTeng
>Assignee: zhengshihan
>Priority: Critical
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I want to find an absolute css unit to show some ui element, then I found wx
> unit is possible to implement this function. But there's some warning at
> Android App running. (The wx unit is about to deprecated in the future.)
> I know there is a faq explain this issue:
> {code:java}
> var height = 88 * 750 / env.deviceWidth{code}
> Is there a simple way to implement this function?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (WEEX-247) list中包含scoller时卡顿
[ https://issues.apache.org/jira/browse/WEEX-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414926#comment-16414926 ] codefurture commented on WEEX-247: -- use horizontal list, and have a try > list中包含scoller时卡顿 > - > > Key: WEEX-247 > URL: https://issues.apache.org/jira/browse/WEEX-247 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 > Environment: 安卓和ios均卡顿，安卓低端机效果更明显 >Reporter: fudongrong >Assignee: zhengshihan >Priority: Critical > > 在纵向List中包含横向scoller时，占用内存过大，导致页面卡顿，安卓平台较明显。代码大致如下： > :style="list_style" > loadmoreoffset="10" > @loadmore="onloadmore" > > > > scroll-direction="horizontal" > show-scrollbar="false"> > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-89) View with linear gradient could not render its border radius correctly
[ https://issues.apache.org/jira/browse/WEEX-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414923#comment-16414923 ] codefurture commented on WEEX-89: - i test it on android, which works right > View with linear gradient could not render its border radius correctly > -- > > Key: WEEX-89 > URL: https://issues.apache.org/jira/browse/WEEX-89 > Project: Weex > Issue Type: Bug > Components: iOS >Reporter: leozdgao >Assignee: Adam Feng >Priority: Blocker > Attachments: correct-without-gradient.PNG, incorrect-with-gradient.PNG > > > A view with linear gradient could not render its border radius correctly, > check the attachment please, the file 'incorrect-with-gradient' shows the > problem, and the file `correct-without-gradient` is the view without linear > gradient and it render its border-radius correctly. > And my style is right here: > ``` > backgroundImage: linear-gradient(to right, '#FF00A0', '#FF0041'); > border-top-left-radius: 8px; > border-top-right-radius: 8px; > ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-248) slide中嵌套list，在小米手机上list滑动事件失效
[ https://issues.apache.org/jira/browse/WEEX-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414920#comment-16414920 ] codefurture commented on WEEX-248: -- is your list use recyclerview? give an height for your list > slide中嵌套list，在小米手机上list滑动事件失效 > - > > Key: WEEX-248 > URL: https://issues.apache.org/jira/browse/WEEX-248 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: 小米note、小米4 安卓7.1 >Reporter: fudongrong >Assignee: zhengshihan >Priority: Blocker > > 当slide的每个项都是list时，slide第一个项中的list完全正常，但是切换到第二项时，该项中的List显示不完全，也不能向下滑动。华为手机没有该问题，猜测是小米手机上滑动事件冲突或者是封装的时候list高度没有重新计算，导致只显示了一页并且滑动不了。大致代码如下,其中myactivity > 是我们自己封装的纵向list： > > :index="group_current" > :style="group_style" > infinite="false" > @change="groupChange" > > > > > :cur_index="sidebar_current" > :list_style="list_style" > :ref="'gp-' + i" > @refreshSidebar="refreshSidebar" > /> > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-261) Flat GUI NullPointerException fix
codefurture created WEEX-261: Summary: Flat GUI NullPointerException fix Key: WEEX-261 URL: https://issues.apache.org/jira/browse/WEEX-261 Project: Weex Issue Type: Improvement Reporter: codefurture Assignee: Adam Feng Flat GUI NullPointerException fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (WEEX-253) WXScroller Handler should use mainLooper ensure main thread
[ https://issues.apache.org/jira/browse/WEEX-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] codefurture updated WEEX-253: - Attachment: 圖片.png > WXScroller Handler should use mainLooper ensure main thread > --- > > Key: WEEX-253 > URL: https://issues.apache.org/jira/browse/WEEX-253 > Project: Weex > Issue Type: Improvement >Reporter: codefurture >Assignee: Adam Feng >Priority: Minor > Attachments: 圖片.png > > > WXScroller Handler should use mainLooper ensure main thread -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-253) WXScroller Handler should use mainLooper ensure main thread
codefurture created WEEX-253: Summary: WXScroller Handler should use mainLooper ensure main thread Key: WEEX-253 URL: https://issues.apache.org/jira/browse/WEEX-253 Project: Weex Issue Type: Improvement Reporter: codefurture Assignee: Adam Feng WXScroller Handler should use mainLooper ensure main thread -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-244) Weex Android Support W3c Force Api
codefurture created WEEX-244: Summary: Weex Android Support W3c Force Api Key: WEEX-244 URL: https://issues.apache.org/jira/browse/WEEX-244 Project: Weex Issue Type: Improvement Components: Android Reporter: codefurture Assignee: zhengshihan * [https://github.com/apache/incubator-weex-site/pull/90/files] [https://developer.mozilla.org/en-US/docs/Web/API/Touch/force] * [http://dotwe.org/vue/91b6929f4f9f97a099a30c516dc2db06] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-222) Sticky header in waterfall is not sticky
[ https://issues.apache.org/jira/browse/WEEX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387485#comment-16387485 ] codefurture commented on WEEX-222: -- issues has been fixed > Sticky header in waterfall is not sticky > > > Key: WEEX-222 > URL: https://issues.apache.org/jira/browse/WEEX-222 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: Playground App Android >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Critical > > * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in > playground app. > * [DotWe link is official waterfall > example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0] > * I have tried this waterfall example in Taobao app. Scan result has same > problem that the sticky header is not sticky. > * But I downgrade to SDK 0.17. It works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-230) input bug
[ https://issues.apache.org/jira/browse/WEEX-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387479#comment-16387479 ] codefurture commented on WEEX-230: -- the value update was filter by diffupdates, becasue domobject value is not sync with input. i will disabled diff update first. > input bug > -- > > Key: WEEX-230 > URL: https://issues.apache.org/jira/browse/WEEX-230 > Project: Weex > Issue Type: Bug >Reporter: 郑江荣 >Assignee: Adam Feng >Priority: Blocker > > input 当设置的绑定的变量值为空字符串之后，再次改变绑定的值，界面上输入框的值不再改变，不设置空字符串就没问题 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-226) WXModuleManager add new callback named onNewIntent()
[ https://issues.apache.org/jira/browse/WEEX-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380080#comment-16380080 ] codefurture commented on WEEX-226: -- great works, you commit an pull request, we will review the code and merge this commit > WXModuleManager add new callback named onNewIntent() > > > Key: WEEX-226 > URL: https://issues.apache.org/jira/browse/WEEX-226 > Project: Weex > Issue Type: Improvement > Components: Android >Affects Versions: 0.18 >Reporter: 华逢义 >Assignee: zhengshihan >Priority: Major > Attachments: image-2018-02-27-08-48-07-120.png, > image-2018-02-27-08-48-59-494.png, image-2018-02-27-08-49-36-808.png > > > As android NFC need use onNewIntent() in Module as callback to get the > RFIDTag.We need add onNewIntent() in WXModuleManager to support NFC plugin > development > !image-2018-02-27-08-47-13-700.png! > !image-2018-02-27-08-48-07-120.png! > !image-2018-02-27-08-48-59-494.png! > !image-2018-02-27-08-49-36-808.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (WEEX-228) ShouldStopPropagation Use ShortName StopPropagation
codefurture created WEEX-228: Summary: ShouldStopPropagation Use ShortName StopPropagation Key: WEEX-228 URL: https://issues.apache.org/jira/browse/WEEX-228 Project: Weex Issue Type: Improvement Reporter: codefurture Assignee: Adam Feng ShouldStopPropagation Use ShortName StopPropagation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-222) Sticky header in waterfall is not sticky
[ https://issues.apache.org/jira/browse/WEEX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376784#comment-16376784 ] codefurture commented on WEEX-222: -- the issues has been fixed [https://github.com/apache/incubator-weex/pull/1041/files] > Sticky header in waterfall is not sticky > > > Key: WEEX-222 > URL: https://issues.apache.org/jira/browse/WEEX-222 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: Playground App Android >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Critical > > * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in > playground app. > * [DotWe link is official waterfall > example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0] > * I have tried this waterfall example in Taobao app. Scan result has same > problem that the sticky header is not sticky. > * But I downgrade to SDK 0.17. It works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
