[jira] [Updated] (WEEX-101) how to resolve voice-over navigation order specify in iOS

[xingZhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/WEEX-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

xingZhang updated WEEX-101:
---
Description: 
voice-over visit view element, we can visit a view tree using  BFS or  DFS,  I 
find out that voice-over  visit its 

element in horizontal row maybe BFS , but sometimes we need to make it column 
navigation, maybe DFS, 

that's to say, voice-over  should visit subviews first, and then its sibling 
views using DFS maybe, so I try to search

apple developer document about this, iOS developers can specify 
shouldGroupAccessibilityChildren to change its

navigation order,  I haven't find  similar way on Android.


here is the dot-we case about test accessible order:
   
http://dotwe.org/vue/5d43492eb707a797a04efebae93eddd5   

default order horizontal order:1->5->2->6->3->4->7->8

expected order is column order: 1->2->3->4->5->6->7->8

The attachment is the view hierarchy in iOS.

  was:
voice-over visit view element, we can visit a view tree using  BSF or  DSF,  I 
find out that voice-over  visit its 

element in horizontal row maybe BSF , but sometimes we need to make it column 
navigation, maybe DSF, 

that's to say, voice-over  should visit subviews first, and then its sibling 
views using DSF maybe, so I try to search

apple developer document about this, iOS developers can specify 
shouldGroupAccessibilityChildren to change its

navigation order,  I haven't find  similar way on Android.


here is the dot-we case about test accessible order:
   
http://dotwe.org/vue/5d43492eb707a797a04efebae93eddd5   

default order horizontal order:1->5->2->6->3->4->7->8

expected order is column order: 1->2->3->4->5->6->7->8

The attachment is the view hierarchy in iOS.


> how to resolve voice-over navigation order specify in iOS
> -
>
> Key: WEEX-101
> URL: https://issues.apache.org/jira/browse/WEEX-101
> Project: Weex
>  Issue Type: Improvement
>  Components: iOS
>Reporter: xingZhang
>Assignee: Adam Feng
> Attachments: image.png
>
>
> voice-over visit view element, we can visit a view tree using  BFS or  DFS,  
> I find out that voice-over  visit its 
> element in horizontal row maybe BFS , but sometimes we need to make it column 
> navigation, maybe DFS, 
> that's to say, voice-over  should visit subviews first, and then its sibling 
> views using DFS maybe, so I try to search
> apple developer document about this, iOS developers can specify 
> shouldGroupAccessibilityChildren to change its
> navigation order,  I haven't find  similar way on Android.
> here is the dot-we case about test accessible order:
>
> http://dotwe.org/vue/5d43492eb707a797a04efebae93eddd5   
> default order horizontal order:1->5->2->6->3->4->7->8
> expected order is column order: 1->2->3->4->5->6->7->8
> The attachment is the view hierarchy in iOS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (WEEX-102) element's appear event in waterfall will fire wrongly

[xingZhang (JIRA)]

xingZhang created WEEX-102:
--

 Summary: element's appear event in waterfall will fire wrongly
 Key: WEEX-102
 URL: https://issues.apache.org/jira/browse/WEEX-102
 Project: Weex
  Issue Type: Bug
Reporter: xingZhang
Assignee: Adam Feng


dot-we case: http://dotwe.org/vue/4ff50d978f973cd725c4c4ae3196e856

When first screen rendered, the block in blue have not appeared, but the appear 
event fired.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [HELP] Randomly crash on Android 5.0.2

[xiaowei.chai]

Hi,
We’ve upgrade SDK to 0.16.0 and this problem still exists.
Thank
XiaoWei

在 17/11/9 10:31，“Adam Feng” 写入:

Hi,

Thanks for the detailed issue,  can you provide the WeexSDK version you 
used,  and is the issue still  happening when you upgrade to the newest version 
?

Thanks.
Adam Feng

On 9 Nov 2017, 9:57 AM +0800, xiaowei.chai , 
wrote:
> Hi,
>
> We found our app randomly crashing on Android 5.0.2.
>
> This issue cannot be reproduced manually, but can be reproduced using 
monkey test.
>
> We found there is only one weex related exception in the logs:
>
>
>
> E/weex ( 8226): Argument format error! value is 
java.lang.NumberFormatException: Invalid float: ""
>
> E/weex ( 8226): at 
java.lang.StringToReal.invalidReal(StringToReal.java:63)
>
> E/weex ( 8226): at 
java.lang.StringToReal.parseFloat(StringToReal.java:308)
>
> E/weex ( 8226): at java.lang.Float.parseFloat(Float.java:306)
>
> E/weex ( 8226): at 
com.taobao.weex.utils.WXUtils.getFloat(WXUtils.java:263)
>
> E/weex ( 8226): at 
com.taobao.weex.ui.component.WXComponent.setProperty(WXComponent.java:706)
>
> E/weex ( 8226): at 
com.taobao.weex.ui.component.WXA.setProperty(WXA.java:255)
>
> E/weex ( 8226): at 
com.taobao.weex.ui.component.WXComponent.updateProperties(WXComponent.java:646)
>
> E/weex ( 8226): at 
com.taobao.weex.ui.WXRenderStatement.updateStyle(WXRenderStatement.java:464)
>
> E/weex ( 8226): at 
com.taobao.weex.ui.WXRenderManager.updateStyle(WXRenderManager.java:393)
>
> E/weex ( 8226): at 
com.taobao.weex.dom.WXDomStatement$8.execute(WXDomStatement.java:871)
>
> E/weex ( 8226): at 
com.taobao.weex.ui.WXRenderManager$1.run(WXRenderManager.java:288)
>
> E/weex ( 8226): at 
com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:235)
>
> E/weex ( 8226): at android.os.Handler.handleCallback(Handler.java:739)
>
> E/weex ( 8226): at android.os.Handler.dispatchMessage(Handler.java:95)
>
> E/weex ( 8226): at android.os.Looper.loop(Looper.java:135)
>
> E/weex ( 8226): at 
android.app.ActivityThread.main(ActivityThread.java:5539)
>
> E/weex ( 8226): at java.lang.reflect.Method.invoke(Native Method)
>
> E/weex ( 8226): at java.lang.reflect.Method.invoke(Method.java:372)
>
> E/weex ( 8226): at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960)
>
> E/weex ( 8226): at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
>
>
>
> We’ve checked all weex pages and there is no chance to provide an empty 
string to a number-typed target.
>
>
>
> If you want to reproduce, please follow below instructions:
>
> 1. Install our app via 
http://sj.qq.com/myapp/detail.htm?apkName=com.zhaopin.social
>
> 2. Launch the app, select ‘我是学生党’(the young man, not the old one) if it 
asks
>
> 3. Connect your phone to computer via USB
>
> 4. Start monkey test via ADB
>
> 5. Monkey will make the app navigating across weex pages, native pages 
and html pages. But the app always crashed on weex pages.
>
>
>
> Any suggestion will be appreciated.
>
>
>
> Thanks
>
>
>
> Xiao-Wei Chai
>
> www.zhaopin.com
>
>
>

Re: Community building?

[Hanks Zhang]

Hi Raphael,

I wonder what's the next about the "GitHub issue" discussion. Can we be
allowed to use GitHub to manage issues?

Looking forward to further discussion.

Best regards, Hanks


2017-10-24 13:29 GMT+08:00 Raphael Bircher :

> Hi all
>
> First of all, thanks for the work. We at Apache tend to do not a vote on
> such a Topic. This one is a typical case for lazy consensus.
>
> We let this thread now open and allow a discussion. It gives us the chance
> to make a good proposal even better. You have not this chance if you vote,
> you can only say yes or no. That's the reason we normally avoid voting (if
> possible)
>
> Sometimes you have no discussion on a proposal, this means for as: "all
> are happy". Often people who are happy with the proposal simply give a +1,
> to show the support.
>
> If a discussion starts, we discuss it out and try to rich consensus within
> the community. Normally this goes much quicker then anyone expect. If the
> discussion is settle down. the proposal is accepted.
>
> I will answer to the other points in a separate mail
>
> Regards, Raphael
>
>
> Am .10.2017, 06:39 Uhr, schrieb Hanks Zhang :
>
> Hi, Raphael
>>
>> As far as I know, our workflow is adjusted, documents are reorganized and
>> assigned to the specific person to rewritten them. We all take part in it.
>> After all the documents are ready we'll deploy the new website to the
>> server.
>>
>> 1. The "contribution" related documents [1] are finished and being
>> reviewed.
>> 2. The "" component document is treated as the template,
>> its structure and details are under adjusting.
>> 3. The tutorial document [2] is on the halfway.
>>
>> There is another thing we are discussing: whether to use GitHub to manage
>> issues.
>>
>> I think is more convenient to use GitHub issue if we have permissions to
>> manage them, such as close, assign, add labels, etc. We can also use a bot
>> to close or fast reply issues, in order to keep the quality and remove
>> redundancy.
>>
>> Should we start a vote on this question?
>>
>> [1] https://github.com/apache/incubator-weex-site/pull/2
>> [2]
>> https://github.com/apache/incubator-weex-site/blob/master/
>> source/guide/index.md
>>
>>
>> 2017-10-24 11:50 GMT+08:00 Raphael Bircher :
>>
>> Hi everybody
>>>
>>> Can someone bring me update about the community building efforts at the
>>> weex project? Thanks a load!
>>>
>>> Regards Raphael
>>>
>>> --
>>> My introduction https://youtu.be/Ln4vly5sxYU
>>>
>>>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>

回复：[HELP] Randomly crash on Android 5.0.2

[谷宝剑(剑白)]

            this log exception will not lead to crash,  it just an warning that 
number is not illegal,  then return Float.NaN.  can you prodive more detail 
log, and more weex info .
--发件人：Adam Feng 
发送时间：2017年11月9日(星期四) 10:31收件人：dev 
主　题：Re: [HELP] Randomly crash on Android 5.0.2
Hi,

Thanks for the detailed issue,  can you provide the WeexSDK version you used,  
and is the issue still  happening when you upgrade to the newest version ?

Thanks.
Adam Feng

On 9 Nov 2017, 9:57 AM +0800, xiaowei.chai , wrote:
> Hi,
>
> We found our app randomly crashing on Android 5.0.2.
>
> This issue cannot be reproduced manually, but can be reproduced using monkey 
>test.
>
> We found there is only one weex related exception in the logs:
>
>
>
> E/weex ( 8226): Argument format error! value is 
>java.lang.NumberFormatException: Invalid float: ""
>
> E/weex ( 8226): at java.lang.StringToReal.invalidReal(StringToReal.java:63)
>
> E/weex ( 8226): at java.lang.StringToReal.parseFloat(StringToReal.java:308)
>
> E/weex ( 8226): at java.lang.Float.parseFloat(Float.java:306)
>
> E/weex ( 8226): at com.taobao.weex.utils.WXUtils.getFloat(WXUtils.java:263)
>
> E/weex ( 8226): at 
>com.taobao.weex.ui.component.WXComponent.setProperty(WXComponent.java:706)
>
> E/weex ( 8226): at com.taobao.weex.ui.component.WXA.setProperty(WXA.java:255)
>
> E/weex ( 8226): at 
>com.taobao.weex.ui.component.WXComponent.updateProperties(WXComponent.java:646)
>
> E/weex ( 8226): at 
>com.taobao.weex.ui.WXRenderStatement.updateStyle(WXRenderStatement.java:464)
>
> E/weex ( 8226): at 
>com.taobao.weex.ui.WXRenderManager.updateStyle(WXRenderManager.java:393)
>
> E/weex ( 8226): at 
>com.taobao.weex.dom.WXDomStatement$8.execute(WXDomStatement.java:871)
>
> E/weex ( 8226): at 
>com.taobao.weex.ui.WXRenderManager$1.run(WXRenderManager.java:288)
>
> E/weex ( 8226): at 
>com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:235)
>
> E/weex ( 8226): at android.os.Handler.handleCallback(Handler.java:739)
>
> E/weex ( 8226): at android.os.Handler.dispatchMessage(Handler.java:95)
>
> E/weex ( 8226): at android.os.Looper.loop(Looper.java:135)
>
> E/weex ( 8226): at android.app.ActivityThread.main(ActivityThread.java:5539)
>
> E/weex ( 8226): at java.lang.reflect.Method.invoke(Native Method)
>
> E/weex ( 8226): at java.lang.reflect.Method.invoke(Method.java:372)
>
> E/weex ( 8226): at 
>com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960)
>
> E/weex ( 8226): at 
>com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
>
>
>
> We’ve checked all weex pages and there is no chance to provide an empty 
>string to a number-typed target.
>
>
>
> If you want to reproduce, please follow below instructions:
>
> 1. Install our app via 
>http://sj.qq.com/myapp/detail.htm?apkName=com.zhaopin.social
>
> 2. Launch the app, select ‘我是学生党’(the young man, not the old one) if it asks
>
> 3. Connect your phone to computer via USB
>
> 4. Start monkey test via ADB
>
> 5. Monkey will make the app navigating across weex pages, native pages and 
>html pages. But the app always crashed on weex pages.
>
>
>
> Any suggestion will be appreciated.
>
>
>
> Thanks
>
>
>
> Xiao-Wei Chai
>
> www.zhaopin.com
>
>
>

Re: [HELP] Randomly crash on Android 5.0.2

[Adam Feng]

Hi,

Thanks for the detailed issue,  can you provide the WeexSDK version you used,  
and is the issue still  happening when you upgrade to the newest version ?

Thanks.
Adam Feng

On 9 Nov 2017, 9:57 AM +0800, xiaowei.chai , wrote:
> Hi,
>
> We found our app randomly crashing on Android 5.0.2.
>
> This issue cannot be reproduced manually, but can be reproduced using monkey 
> test.
>
> We found there is only one weex related exception in the logs:
>
>
>
> E/weex ( 8226): Argument format error! value is 
> java.lang.NumberFormatException: Invalid float: ""
>
> E/weex ( 8226): at java.lang.StringToReal.invalidReal(StringToReal.java:63)
>
> E/weex ( 8226): at java.lang.StringToReal.parseFloat(StringToReal.java:308)
>
> E/weex ( 8226): at java.lang.Float.parseFloat(Float.java:306)
>
> E/weex ( 8226): at com.taobao.weex.utils.WXUtils.getFloat(WXUtils.java:263)
>
> E/weex ( 8226): at 
> com.taobao.weex.ui.component.WXComponent.setProperty(WXComponent.java:706)
>
> E/weex ( 8226): at com.taobao.weex.ui.component.WXA.setProperty(WXA.java:255)
>
> E/weex ( 8226): at 
> com.taobao.weex.ui.component.WXComponent.updateProperties(WXComponent.java:646)
>
> E/weex ( 8226): at 
> com.taobao.weex.ui.WXRenderStatement.updateStyle(WXRenderStatement.java:464)
>
> E/weex ( 8226): at 
> com.taobao.weex.ui.WXRenderManager.updateStyle(WXRenderManager.java:393)
>
> E/weex ( 8226): at 
> com.taobao.weex.dom.WXDomStatement$8.execute(WXDomStatement.java:871)
>
> E/weex ( 8226): at 
> com.taobao.weex.ui.WXRenderManager$1.run(WXRenderManager.java:288)
>
> E/weex ( 8226): at 
> com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:235)
>
> E/weex ( 8226): at android.os.Handler.handleCallback(Handler.java:739)
>
> E/weex ( 8226): at android.os.Handler.dispatchMessage(Handler.java:95)
>
> E/weex ( 8226): at android.os.Looper.loop(Looper.java:135)
>
> E/weex ( 8226): at android.app.ActivityThread.main(ActivityThread.java:5539)
>
> E/weex ( 8226): at java.lang.reflect.Method.invoke(Native Method)
>
> E/weex ( 8226): at java.lang.reflect.Method.invoke(Method.java:372)
>
> E/weex ( 8226): at 
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960)
>
> E/weex ( 8226): at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
>
>
>
> We’ve checked all weex pages and there is no chance to provide an empty 
> string to a number-typed target.
>
>
>
> If you want to reproduce, please follow below instructions:
>
> 1. Install our app via 
> http://sj.qq.com/myapp/detail.htm?apkName=com.zhaopin.social
>
> 2. Launch the app, select ‘我是学生党’(the young man, not the old one) if it asks
>
> 3. Connect your phone to computer via USB
>
> 4. Start monkey test via ADB
>
> 5. Monkey will make the app navigating across weex pages, native pages and 
> html pages. But the app always crashed on weex pages.
>
>
>
> Any suggestion will be appreciated.
>
>
>
> Thanks
>
>
>
> Xiao-Wei Chai
>
> www.zhaopin.com
>
>
>

[HELP] Randomly crash on Android 5.0.2

[xiaowei.chai]

Hi,

We found our app randomly crashing on Android 5.0.2. 

This issue cannot be reproduced manually, but can be reproduced using monkey 
test.

We found there is only one weex related exception in the logs:

 

E/weex( 8226): Argument format error! value is 
java.lang.NumberFormatException: Invalid float: ""

E/weex( 8226):at 
java.lang.StringToReal.invalidReal(StringToReal.java:63)

E/weex( 8226):at 
java.lang.StringToReal.parseFloat(StringToReal.java:308)

E/weex( 8226):at java.lang.Float.parseFloat(Float.java:306)

E/weex( 8226):at 
com.taobao.weex.utils.WXUtils.getFloat(WXUtils.java:263)

E/weex( 8226):at 
com.taobao.weex.ui.component.WXComponent.setProperty(WXComponent.java:706)

E/weex( 8226):at 
com.taobao.weex.ui.component.WXA.setProperty(WXA.java:255)

E/weex( 8226):at 
com.taobao.weex.ui.component.WXComponent.updateProperties(WXComponent.java:646)

E/weex( 8226):at 
com.taobao.weex.ui.WXRenderStatement.updateStyle(WXRenderStatement.java:464)

E/weex( 8226):at 
com.taobao.weex.ui.WXRenderManager.updateStyle(WXRenderManager.java:393)

E/weex( 8226):at 
com.taobao.weex.dom.WXDomStatement$8.execute(WXDomStatement.java:871)

E/weex( 8226):at 
com.taobao.weex.ui.WXRenderManager$1.run(WXRenderManager.java:288)

E/weex( 8226):at 
com.taobao.weex.common.WXThread$SafeRunnable.run(WXThread.java:235)

E/weex( 8226):at android.os.Handler.handleCallback(Handler.java:739)

E/weex( 8226):at android.os.Handler.dispatchMessage(Handler.java:95)

E/weex( 8226):at android.os.Looper.loop(Looper.java:135)

E/weex( 8226):at 
android.app.ActivityThread.main(ActivityThread.java:5539)

E/weex( 8226):at java.lang.reflect.Method.invoke(Native Method)

E/weex( 8226):at java.lang.reflect.Method.invoke(Method.java:372)

E/weex( 8226):at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:960)

E/weex( 8226):at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

 

We’ve checked all weex pages and there is no chance to provide an empty string 
to a number-typed target.

 

If you want to reproduce, please follow below instructions:

1.  Install our app via 
http://sj.qq.com/myapp/detail.htm?apkName=com.zhaopin.social

2.  Launch the app, select ‘我是学生党’(the young man, not the old one) if it 
asks

3.  Connect your phone to computer via USB

4.  Start monkey test via ADB

5.  Monkey will make the app navigating across weex pages, native pages and 
html pages. But the app always crashed on weex pages.

 

Any suggestion will be appreciated.

 

Thanks

 

Xiao-Wei Chai

www.zhaopin.com

 

Re: [HELP] Failed to upgrade SDK to 0.16.0

[xiaowei.chai]

Hi Wentao,
Thanks for your help, we’ve resolved this problem and our app in the market is 
running with 0.16.0 now.

XiaoWei Chai

在 17/10/26 13:31，“wentao shi” 写入:

hi  all
   in order to  reduce package size, weex use armeabi to support
armeabi-v7a, so when we config android project as:
   ndk{abiFilters "x86","armeabi"}
   notice: don't include abiFilters "armeabi-v7a"
v7a cpu architecture so support had been planning, will release on
future
BRs,
toretto

2017-10-26 11:00 GMT+08:00 Adam Feng :

> Maybe @shiwen can help with the problem
>
> Thanks.
> Adam Feng
>
> On 25 Oct 2017, 2:24 PM +0800, xiaowei.chai ,
> wrote:
>
> Hi,
>
> Sorry, here is the screenshot: http://c-m-bucket.zhaopin.cn/
> c/m/imgs/356d44f0-a466-422c-9a20-b3481ab69617.jpeg
>
>
>
> Thank you.
>
>
>
> 发件人: Raphael Bircher  组织: Apache Software Foundation
> 答复:  日期: 2017年10月25日 星期三 13:58
> 至:  主题: Re: [HELP] Failed to upgrade SDK to 0.16.0
>
>
>
> Hi
>
>
>
> The mailing list program cut attachments of. Can you upload your
> screenshot somewhere, and just send a link?
>
>
>
> Regards Raphael
>
>
>
> Am .10.2017, 07:56 Uhr, schrieb xiaowei.chai  >:
>
>
>
> Re-attach the exception log screenshot.
>
>
>
> 发件人: "xiaowei.chai"  答复:  日期: 2017年10月25日 星期三 13:53
> 至:  主题: [HELP] Failed to upgrade SDK to 0.16.0
>
>
>
>
> We recently tried to upgrade weex SDK to 0.16.0 from 0.11.0. After
> upgraded, we found all weex pages turns blank and an exception log:
>
>
>
>
>
>
>
> --
>
> My introduction https://youtu.be/Ln4vly5sxYU
>
>

[jira] [Created] (WEEX-101) how to resolve voice-over navigation order specify in iOS

[xingZhang (JIRA)]

xingZhang created WEEX-101:
--

 Summary: how to resolve voice-over navigation order specify in iOS
 Key: WEEX-101
 URL: https://issues.apache.org/jira/browse/WEEX-101
 Project: Weex
  Issue Type: Improvement
  Components: iOS
Reporter: xingZhang
Assignee: Adam Feng
 Attachments: image.png

voice-over visit view element, we can visit a view tree using  BSF or  DSF,  I 
find out that voice-over  visit its 

element in horizontal row maybe BSF , but sometimes we need to make it column 
navigation, maybe DSF, 

that's to say, voice-over  should visit subviews first, and then its sibling 
views using DSF maybe, so I try to search

apple developer document about this, iOS developers can specify 
shouldGroupAccessibilityChildren to change its

navigation order,  I haven't find  similar way on Android.


here is the dot-we case about test accessible order:
   
http://dotwe.org/vue/5d43492eb707a797a04efebae93eddd5   

default order horizontal order:1->5->2->6->3->4->7->8

expected order is column order: 1->2->3->4->5->6->7->8

The attachment is the view hierarchy in iOS.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

回复：Weex accessibility discussion about voice-over in iOS read order

[李剑锋(墨循)]

Hi there,Now I am also researching accessibility in Android. after the actual 
test, I found out the order of Talkback visit view tree is from child to 
sibling, that is what you say DSF.
I think we should not limit its order in BSF or DSF, but according to the 
actual situation of the business, according to the visit path of normal user. 
In Android, we have API like setNextFocusUp/Down/Left/Right to guide Talkback 
to visit page. Maybe this is a more generic solution to exposed interface as 
Weex.
Thanks-
在(日期)2017年11月8日, 在(时间)22:20, xing zhang 写到   hi, all
   Recently I am researching accessibility in iOS,  developer can write simple 
accessible app using weex now.
There is a case for me to be confused，that's the voice-over navigation order , 
you can just think of how the 
voice-over visit view element, we can visit a view tree using  BSF or  DSF,  I 
find out that voice-over  visit its 
element in horizontal row maybe BSF , but sometimes we need to make it column 
navigation, maybe DSF, 
that's to say, voice-over  should visit subviews first, and then its sibling 
views using DSF maybe, so I try to search
apple developer document about this, iOS developers can specify 
shouldGroupAccessibilityChildren to change its
navigation order,  I haven't find  similar way on Android.

here is the dot-we case about test accessible order:       
http://dotwe.org/vue/5d43492eb707a797a04efebae93eddd5   
default order horizontal order:    1->5->2->6->3->4->7->8
expected order is column order: 1->2->3->4->5->6->7->8
The attachment is the view hierarchy in iOS.


I expose this shouldGroupAccessibilityChildren property, so that weex 
developers can change the navigation 

order in iOS  easily,  but it is not standard and arbitrary, I want make this 
more practical and last for a longer 
timer , actually  there are some related feature in native API but  WAI don't  
refer to, such as hint,  but we needs
it to make our app more accessible to everyone. I don't know  whether I make 
this clear.
Any suggestion about this?

[jira] [Commented] (WEEX-100) Support customize button title for picker module

[Shaojun Yang (JIRA)]

[ 
https://issues.apache.org/jira/browse/WEEX-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244006#comment-16244006
 ] 

Shaojun Yang commented on WEEX-100:
---

Just as same as *picker.pick* method, like:

{code:javascript}
var picker = weex.requireModule('picker');
picker.pickDate({
value: '2017-11-08',
max: '2029-11-08',
min: '2015-11-08',
confirmTitle: 'Cancel Date',
cancelTitle: 'Confirm Date'
});
picker.pickTime({
value: '19:24',
confirmTitle: 'Cancel Time',
cancelTitle: 'Confirm Time'
});
{code}

Example: [http://dotwe.org/vue/d90cb01d5d9ff75ba74781a0f003c95e]


> Support customize button title for picker module
> 
>
> Key: WEEX-100
> URL: https://issues.apache.org/jira/browse/WEEX-100
> Project: Weex
>  Issue Type: New Feature
>  Components: Android, iOS
>Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17
>Reporter: Shaojun Yang
>Assignee: zhengshihan
>  Labels: features
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Button title of picker module is related to system language, can not be 
> changed by the developer.
> Customize button title is useful in multiple language application, we should 
> provide extra options to support it, like *confirmTitle* and *cancelTitle*.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Weex accessibility discussion about voice-over in iOS read order

[xing zhang]

   hi, all

   Recently I am researching accessibility in iOS,  developer can write
simple accessible app using weex now.

There is a case for me to be confused，that's the *voice-over navigation
order* , you can just think of how the

voice-over visit view element, we can visit a view tree using  BSF or
DSF,  I find out *that voice-over  **visit its *

*element in horizontal row maybe BSF *, but sometimes we need to make it
column navigation, maybe DSF,

that's to say, voice-over  should visit subviews first, and then its
sibling views using DSF maybe, so I try to search

apple developer document about this, iOS developers can specify
shouldGroupAccessibilityChildren

to
change its

navigation order,  I haven't find  similar way on Android.


here is the dot-we case about test accessible order:

http://dotwe.org/vue/5d43492eb707a797a04efebae93eddd5

default order horizontal order:1->5->2->6->3->4->7->8

expected order is column order: 1->2->3->4->5->6->7->8

The attachment is the view hierarchy in iOS.

[image: 内嵌图片 3]

I expose this shouldGroupAccessibilityChildren

property,
so that weex developers can change the navigation

order in iOS  easily,  *but it is not standard and arbitrary*, I want make
this more practical and last for a longer

timer , actually  there are some related feature in native API but  WAI
 don't  refer to, such as hint,  but we
needs

it to make our app more accessible to everyone. I don't know  whether I
make this clear.

Any suggestion about this?





[image: 内嵌图片 1]

[jira] [Commented] (WEEX-99) The setViewport method in WXMetaModule is ASYN right now which makes weexInstance.viewportWidth setted after view created.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/WEEX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243972#comment-16243972
 ] 

ASF GitHub Bot commented on WEEX-99:


Github user cxfeng1 commented on the issue:

https://github.com/apache/incubator-weex/pull/844
  
@gubaojian please have a review.


> The setViewport method in WXMetaModule is ASYN right now which makes 
> weexInstance.viewportWidth setted after view created.
> --
>
> Key: WEEX-99
> URL: https://issues.apache.org/jira/browse/WEEX-99
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
>Reporter: myeveryheart
>Assignee: Adam Feng
> Attachments: 粘贴图片.png, 粘贴图片1.png, 粘贴图片2.png, 粘贴图片3.png
>
>
> The meta module can be used to declare meta information for a single page, 
> such as the viewport of the container.
> It provides a method 'setViewport' to change the viewport of the page.
> But the method is ASYN right now which makes weexInstance.viewportWidth 
> setted after view created.
> The bug is in iOS and Android.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (WEEX-94) scroller component can lead to crash in iOS 8 and older iOS version

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/WEEX-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243962#comment-16243962
 ] 

ASF GitHub Bot commented on WEEX-94:


Github user cxfeng1 commented on the issue:

https://github.com/apache/incubator-weex/pull/838
  
LGTM


> scroller component can lead to crash in iOS 8 and older iOS version
> ---
>
> Key: WEEX-94
> URL: https://issues.apache.org/jira/browse/WEEX-94
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
>Reporter: xingZhang
>Assignee: Adam Feng
> Attachments: 屏幕快照 2017-11-07 20.47.29.png
>
>
>As iOS developers knows, assign property object will not be set as nil 
> when its object deallocated, and weak property will do.
>We found crash only on iOS 8 about scrollview delegate zombie object now, 
> it is necessary to fix it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (WEEX-100) Support customize button title for picker module

[xingZhang (JIRA)]

[ 
https://issues.apache.org/jira/browse/WEEX-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243821#comment-16243821
 ] 

xingZhang commented on WEEX-100:


 Is there any expected input or output format case

> Support customize button title for picker module
> 
>
> Key: WEEX-100
> URL: https://issues.apache.org/jira/browse/WEEX-100
> Project: Weex
>  Issue Type: New Feature
>  Components: Android, iOS
>Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17
>Reporter: Shaojun Yang
>Assignee: zhengshihan
>  Labels: features
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Button title of picker module is related to system language, can not be 
> changed by the developer.
> Customize button title is useful in multiple language application, we should 
> provide extra options to support it, like *confirmTitle* and *cancelTitle*.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (WEEX-98) addEvent will lead to view load again, especially the view just re-used for memory usage

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/WEEX-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243799#comment-16243799
 ] 

ASF GitHub Bot commented on WEEX-98:


Github user cxfeng1 commented on the issue:

https://github.com/apache/incubator-weex/pull/837
  
LGTM


> addEvent will lead to view load again, especially the view just re-used for 
> memory usage
> 
>
> Key: WEEX-98
> URL: https://issues.apache.org/jira/browse/WEEX-98
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
>Reporter: xingZhang
>Assignee: Adam Feng
>
>   In most case , element in cell will be re-use for memory especially in very 
> long list, but if I call addEvent for this element, here will generate a new 
> view for this element.
>  For instance, image element in cell  will re-use if it is disappear in 
> vision area, and loaded again while it back to visual area. In this case , 
> when it disappear, just add event such as click, touch and so on , it will 
> then generate a new view ,and load image again, although it is off-screen.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [jira] [Commented] (WEEX-85) Improve the Weextoolkit's experience and add new features

[Drew Hansen]

After some time using the development tools, I collected some new and
useful functional requirements of weex-devtool：

1. Provide support for weex storage management.
2. Provide compile-time performance data optimization recommendations of
weex project.
3. Provide run-time performance data optimization recommendations.
4. Provides the ability to collect and show fps, network, cpu, memory data.

Please give your comments if any.

2017-11-06 21:00 GMT+08:00 erha19 (JIRA) :

>
> [ https://issues.apache.org/jira/browse/WEEX-85?page=com.
> atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=16240247#comment-16240247 ]
>
> erha19 commented on WEEX-85:
> 
>
> Last week I decided not to carry out `weex-lint` function development, the
> main reason is divided into the following two points:
>
> # For equipment running information needs to be simulated in the real
> machine, the use of tools cannot simulate the real environment, can not
> test the real machine running problems. If you need to invest in
> development efforts, your output may not meet the expectations you expect.
> # The basic script's static checking tool can only check the format and
> the validity of the reference, and there are many lint tools in the front
> end such as eslint, which feels like we do not need the existing eslint to
> support the above functions.
>
>
> It is exciting that weex-devtool 2.0 has been basically developed, you can
> experience the latest version weex devtool the commands below:
>
> ```
> npm i weex-toolkit@latest -g
> weex xbind debugx weex-debugger
> weex debugx
> ```
>
> There are some new feature on the new weex devtool.
>
> # Consolidated inspector and runtime log information;
> # More intuitive and refreshing debugging interface and performance;
> # I18n support is provided
> # Provide performance analysis tools
>
> The package is published as name of [weex-debugger](https://www.
> npmjs.com/package/weex-debugger), after full testing it will be upgraded
> on the next version of weex-devtool.
>
> > Improve the Weextoolkit's experience and add new features
> > -
> >
> > Key: WEEX-85
> > URL: https://issues.apache.org/jira/browse/WEEX-85
> > Project: Weex
> >  Issue Type: Improvement
> >  Components: Project
> >Reporter: erha19
> >Assignee: zhengshihan
> >
> > The new version of the weex-toolkit will support some of the following
> features:
> > - weex-lint plugin
> > - weex-devtool 2.0
> > The `weex-lint` is a plugin for weex detects whether the syntax is
> normative and whether there is a runtime error.and a common fix.
> > The `weex-devtool 2.0` is an upgrade version of `weex-devtool`, the
> upgrade version will rewrite the message storeroom of  `weex-devtool`,
> unify the logger and inspector log information, provide a more beautiful
> interface and lower operating costs, and also The performance data provided
> by the weex module provides the developer with a page optimization basis.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

[jira] [Commented] (WEEX-97) font-weight and linear-gradient can't be reset on iOS and web

[Danz He (JIRA)]

[ 
https://issues.apache.org/jira/browse/WEEX-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243652#comment-16243652
 ] 

Danz He commented on WEEX-97:
-

On web it's a bug, since the merged style has deleted the style who's value is 
a array (and assign its values in the next tick before passed it to the vnode), 
therefore from the patch process' perspective there's no difference between the 
status of active and inactive. This should be fixed soon in the next patch 
version.

> font-weight and linear-gradient can't be reset on iOS and web
> -
>
> Key: WEEX-97
> URL: https://issues.apache.org/jira/browse/WEEX-97
> Project: Weex
>  Issue Type: Bug
>  Components: iOS, Web Renderer
>Reporter: Hanks Zhang
>Assignee: xingZhang
>
> See the example below, click the tex will toggle its styles. But the 
> font-weight couldn't be reset on iOS, the linear-gradient couldn't be reset 
> on web. Android is fine.
> http://dotwe.org/vue/ecf6a20bde4c42ae4e7b6314ebce4438



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (WEEX-100) Support customize button title for picker module

[Shaojun Yang (JIRA)]

Shaojun Yang created WEEX-100:
-

 Summary: Support customize button title for picker module
 Key: WEEX-100
 URL: https://issues.apache.org/jira/browse/WEEX-100
 Project: Weex
  Issue Type: New Feature
  Components: Android, iOS
Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17
Reporter: Shaojun Yang
Assignee: zhengshihan


Button title of picker module is related to system language, can not be changed 
by the developer.

Customize button title is useful in multiple language application, we should 
provide extra options to support it, like *confirmTitle* and *cancelTitle*.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)