[jira] [Commented] (WEEX-90) Remove The Legacy Weex DSL 1.0 (.we) Front-End Framework
[ https://issues.apache.org/jira/browse/WEEX-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301079#comment-16301079 ] ASF GitHub Bot commented on WEEX-90: Github user weex-bot commented on the issue: https://github.com/apache/incubator-weex/pull/955 Messages :book: has no jsfm file changed. :book: jsfm test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/";>dangerJS > Remove The Legacy Weex DSL 1.0 (.we) Front-End Framework > > > Key: WEEX-90 > URL: https://issues.apache.org/jira/browse/WEEX-90 > Project: Weex > Issue Type: Bug >Reporter: Hanks Zhang >Assignee: Adam Feng > > Weex DSL 1.0 (.we) front-end framework is inspired by Vue.js 1.0. Since Weex > supports the official Vue.js 2.0 in v0.10.0 [1] at 2017-02-17, the ".we" > framework is deprecated. In order to optimize the performance, stability, and > package size, this legacy framework should be removed from the WeexSDK. > I suggest removing the ".we" framework in the 2018 January release of WeexSDK. > For the projects who are still using the ".we" framework, you can read the > "Migration From .we Framework" [2] and "The Syntax Difference Between .we and > .vue" [3] documents to help you migrate your ".we" project to Vue.js 2.0 > project. But those documents only have Chinese version. > [1] https://github.com/alibaba/weex/releases/tag/v0.10.0 > [2] http://weex-project.io/cn/references/migration/migration-from-weex.html > [3] http://weex-project.io/cn/references/migration/difference.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-90) Remove The Legacy Weex DSL 1.0 (.we) Front-End Framework
[ https://issues.apache.org/jira/browse/WEEX-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301078#comment-16301078 ] ASF GitHub Bot commented on WEEX-90: GitHub user Hanks10100 opened a pull request: https://github.com/apache/incubator-weex/pull/955 [WEEX-90][example] remove legacy .we examples Remove source codes of .we examples, then rebuild the examples, replace the generated bundles in ios and android. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Hanks10100/incubator-weex WEEX-90 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/955.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #955 commit 8668b0f9ee4c42407c69240542b80dda4729848f Author: Hanks Date: 2017-12-22T07:40:06Z - [example] remove legacy .we examples Remove source codes of .we examples, then rebuild the examples, replace the generated bundles in ios and android. > Remove The Legacy Weex DSL 1.0 (.we) Front-End Framework > > > Key: WEEX-90 > URL: https://issues.apache.org/jira/browse/WEEX-90 > Project: Weex > Issue Type: Bug >Reporter: Hanks Zhang >Assignee: Adam Feng > > Weex DSL 1.0 (.we) front-end framework is inspired by Vue.js 1.0. Since Weex > supports the official Vue.js 2.0 in v0.10.0 [1] at 2017-02-17, the ".we" > framework is deprecated. In order to optimize the performance, stability, and > package size, this legacy framework should be removed from the WeexSDK. > I suggest removing the ".we" framework in the 2018 January release of WeexSDK. > For the projects who are still using the ".we" framework, you can read the > "Migration From .we Framework" [2] and "The Syntax Difference Between .we and > .vue" [3] documents to help you migrate your ".we" project to Vue.js 2.0 > project. But those documents only have Chinese version. > [1] https://github.com/alibaba/weex/releases/tag/v0.10.0 > [2] http://weex-project.io/cn/references/migration/migration-from-weex.html > [3] http://weex-project.io/cn/references/migration/difference.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-177) scroll to element offset has none affect when none touch
[ https://issues.apache.org/jira/browse/WEEX-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301063#comment-16301063 ] ASF GitHub Bot commented on WEEX-177: - GitHub user gubaojian reopened a pull request: https://github.com/apache/incubator-weex/pull/950 [WEEX-177][android]scroll to element offset has none affect when none touch [WEEX-177][android]scroll to element offset has none affect when none touch You can merge this pull request into a Git repository by running: $ git pull https://github.com/gubaojian/incubator-weex release-0.17-scroll Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/950.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #950 commit 8a66ff813e128e1e44be3a885b2fc6d4dc9132c6 Author: jianbai.gbj Date: 2017-12-20T09:45:59Z [WEEX-177][android]scroll to element offset has none affect when none touch > scroll to element offset has none affect when none touch > > > Key: WEEX-177 > URL: https://issues.apache.org/jira/browse/WEEX-177 > Project: Weex > Issue Type: Bug >Reporter: codefurture >Assignee: Adam Feng > > scroll to element offset has none affect when none touch -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-177) scroll to element offset has none affect when none touch
[ https://issues.apache.org/jira/browse/WEEX-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301062#comment-16301062 ] ASF GitHub Bot commented on WEEX-177: - Github user gubaojian closed the pull request at: https://github.com/apache/incubator-weex/pull/950 > scroll to element offset has none affect when none touch > > > Key: WEEX-177 > URL: https://issues.apache.org/jira/browse/WEEX-177 > Project: Weex > Issue Type: Bug >Reporter: codefurture >Assignee: Adam Feng > > scroll to element offset has none affect when none touch -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Separate the weex-vue-render from the incubator-weex repo
Yes.. About that, I think we should have more discussion on not just renders but all the js codes in 'html5' folder, because there may be other legacy codes we might want to remove or archive. Firstly, the codes in html5/render/ include three different web renderer. They should be removed, but the render/native is just a entry file for frameworks. Maybe the native render should be moved to the html5/frameworks as well. Secondly, should we remove it once for all, or should we just archive it into the path of html5/render/legacy ? Since the way we dealing with the old js-framework is like this. At last, what we do here is to clear out the DSL layer code, making weex more concentrative and foucs on the core SDK and js-runtime, so that our main project structure could be much clearer and more lightweight. I tend to remove all the codes in html5 including frameworks and renders, move runtime codes into a 'runtime' path, and import whichever js-framework into that runtime codes from npm packages. The structure might be like this: ``` - android - ios - html5 - runtime (new) / all the js runtime code here... - ... ``` 2017-12-22 14:17 GMT+08:00 Hanks Zhang : > I noticed that the weex-vue-render have already been moved to > https://github.com/weexteam/weex-vue-render > > So, I think the source code of it should be removed from the > [apache/incubator-weex] repo. I created an issue to track it: > https://issues.apache.org/jira/browse/WEEX-181 > > > > 2017-12-19 23:42 GMT+08:00 He Sai : > > > @Jonathan Dong, Great, Thanks ! I'll transfer it into weexteam group > soon. > > > > 2017-12-19 19:04 GMT+08:00 Jonathan Dong >: > > > > > That is nice. I can help to create a repo in > https://github.com/weexteam > > > to host the codes here instead of using a personal github account. > > > > > > On 19 Dec 2017, 5:52 PM +0800, He Sai , wrote: > > > I think it's better to separate it from this repo. It's more like a DSL > > > layer stuff, a > > > javascript framework to run the dot vue file on web platform, not a > > feature > > > of > > > weex SDK it self. Since the rax DSL framework is not included in this > > repo, > > > it's > > > more or less the same. > > > > > > I have already created a new repo for these codes, with building > scripts > > > and > > > test cases: > > > > > > https://github.com/MrRaindrop/weex-vue-render > > > > > > The main project in this repo should be more focusing and cleaner, > > > and the render codes in html5 folder could all be removed later. > > > > > > 2017-12-19 17:31 GMT+08:00 Hanks Zhang : > > > > > > The "weex-vue-render" is a component and module library for Vue.js. It > > > enables pages written in Weex + Vue to run on the Web platform. It can > be > > > used to downgrade the weex native pages to web pages. > > > > > > However, I think this package should separate from the incubator-weex > > repo. > > > > > > Because it doesn't rely on any code of WeexSDK, and WeexSDK doesn't > rely > > on > > > any code of weex-vue-render neither. Even the vue framework itself is > > > separated from the incubator-weex repo, weex require it as a > dependency, > > > not to mention that weex-vue-render is not a part of WeexSDK. > > > > > > Moreover, weex-vue-render also required many web dependencies which > could > > > not be used in WeexSDK. I think it's a better to keep the source code > of > > > incubator-weex more simple and move the weex-vue-render and its > > > dependencies to a separate repo. > > > > > > > > > > > > > > > -- > > > > > > Best Wishes！ > > > _danz > > > > > > > > > > > -- > > > > Best Wishes！ > > _danz > > > -- Best Wishes！ _danz
[jira] [Commented] (WEEX-182) JS framework send empty attributes and styles to native
[ https://issues.apache.org/jira/browse/WEEX-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301059#comment-16301059 ] ASF GitHub Bot commented on WEEX-182: - GitHub user Hanks10100 reopened a pull request: https://github.com/apache/incubator-weex/pull/953 [WEEX-182][jsfm] only update batched and mutated attributes and styles Check if the batched styles and attributes are empty, and then, only send the mutations to native. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Hanks10100/incubator-weex jsfm-feature-attr-diff Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/953.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #953 commit 94368e362b8bcc0b5ee72b33266bf10ceacbb944 Author: Hanks Date: 2017-12-22T06:48:40Z * [jsfm] only update batched and mutated attributes and styles Check if the batched styles and attributes are empty, and then, only send the mutations to native. > JS framework send empty attributes and styles to native > --- > > Key: WEEX-182 > URL: https://issues.apache.org/jira/browse/WEEX-182 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > > After JS Framework support batched update of attributes and styles. > (https://github.com/apache/incubator-weex/pull/819) Sometimes it will send > empty or the whole attributes and styles to native because there is no diff > in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-182) JS framework send empty attributes and styles to native
[ https://issues.apache.org/jira/browse/WEEX-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301057#comment-16301057 ] ASF GitHub Bot commented on WEEX-182: - Github user Hanks10100 closed the pull request at: https://github.com/apache/incubator-weex/pull/953 > JS framework send empty attributes and styles to native > --- > > Key: WEEX-182 > URL: https://issues.apache.org/jira/browse/WEEX-182 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > > After JS Framework support batched update of attributes and styles. > (https://github.com/apache/incubator-weex/pull/819) Sometimes it will send > empty or the whole attributes and styles to native because there is no diff > in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-183) append="tree" doesn't work on the root element
[ https://issues.apache.org/jira/browse/WEEX-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301044#comment-16301044 ] ASF GitHub Bot commented on WEEX-183: - Github user weex-bot commented on the issue: https://github.com/apache/incubator-weex/pull/954 Warnings :warning: No Changelog changes! :warning: This PR should update related documents as well. Messages :book: danger test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/";>dangerJS > append="tree" doesn't work on the root element > -- > > Key: WEEX-183 > URL: https://issues.apache.org/jira/browse/WEEX-183 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > > For this example: http://dotwe.org/vue/c479b4f8b2e7243efe1cfed2f442e35a > Even there is an append="tree" on the root element, js framework will send > two render directives to native. JS Framework does it on purpose to ensure > the performance of sending the first render directive (createBody). I think > it should be fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-183) append="tree" doesn't work on the root element
[ https://issues.apache.org/jira/browse/WEEX-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301043#comment-16301043 ] ASF GitHub Bot commented on WEEX-183: - GitHub user Hanks10100 opened a pull request: https://github.com/apache/incubator-weex/pull/954 [WEEX-183][jsfm] support append tree on root element See this example: http://dotwe.org/vue/c479b4f8b2e7243efe1cfed2f442e35a Even there is an append="tree" on the root element, js framework will send two render directives to native. JS Framework does it on purpose to ensure the performance of sending the first render directive (`createBody`). I think this feature is no longer needed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Hanks10100/incubator-weex jsfm-feature-root-append-tree Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/954.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #954 commit 7b2111270c1b193c3bd394b177723fbbb8a08a66 Author: Hanks Date: 2017-12-22T06:57:48Z * [jsfm] support append tree on root element > append="tree" doesn't work on the root element > -- > > Key: WEEX-183 > URL: https://issues.apache.org/jira/browse/WEEX-183 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > > For this example: http://dotwe.org/vue/c479b4f8b2e7243efe1cfed2f442e35a > Even there is an append="tree" on the root element, js framework will send > two render directives to native. JS Framework does it on purpose to ensure > the performance of sending the first render directive (createBody). I think > it should be fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-182) JS framework send empty attributes and styles to native
[ https://issues.apache.org/jira/browse/WEEX-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301039#comment-16301039 ] ASF GitHub Bot commented on WEEX-182: - Github user weex-bot commented on the issue: https://github.com/apache/incubator-weex/pull/953 Warnings :warning: No Changelog changes! :warning: These new JS files do not have Flow enabled: html5/test/unit/runtime/utils.js :warning: This PR should update related documents as well. Messages :book: danger test finished. Generated by :no_entry_sign: http://github.com/danger/danger-js/";>dangerJS > JS framework send empty attributes and styles to native > --- > > Key: WEEX-182 > URL: https://issues.apache.org/jira/browse/WEEX-182 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > > After JS Framework support batched update of attributes and styles. > (https://github.com/apache/incubator-weex/pull/819) Sometimes it will send > empty or the whole attributes and styles to native because there is no diff > in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-182) JS framework send empty attributes and styles to native
[ https://issues.apache.org/jira/browse/WEEX-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301038#comment-16301038 ] ASF GitHub Bot commented on WEEX-182: - GitHub user Hanks10100 opened a pull request: https://github.com/apache/incubator-weex/pull/953 [WEEX-182][jsfm] only update batched and mutated attributes and styles Check if the batched styles and attributes are empty, and then, only send the mutations to native. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Hanks10100/incubator-weex jsfm-feature-attr-diff Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/953.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #953 commit 94368e362b8bcc0b5ee72b33266bf10ceacbb944 Author: Hanks Date: 2017-12-22T06:48:40Z * [jsfm] only update batched and mutated attributes and styles Check if the batched styles and attributes are empty, and then, only send the mutations to native. > JS framework send empty attributes and styles to native > --- > > Key: WEEX-182 > URL: https://issues.apache.org/jira/browse/WEEX-182 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > > After JS Framework support batched update of attributes and styles. > (https://github.com/apache/incubator-weex/pull/819) Sometimes it will send > empty or the whole attributes and styles to native because there is no diff > in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (WEEX-183) append="tree" doesn't work on the root element
Hanks Zhang created WEEX-183: Summary: append="tree" doesn't work on the root element Key: WEEX-183 URL: https://issues.apache.org/jira/browse/WEEX-183 Project: Weex Issue Type: Bug Components: JSFM Reporter: Hanks Zhang Assignee: Hanks Zhang For this example: http://dotwe.org/vue/c479b4f8b2e7243efe1cfed2f442e35a Even there is an append="tree" on the root element, js framework will send two render directives to native. JS Framework does it on purpose to ensure the performance of sending the first render directive (createBody). I think it should be fixed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (WEEX-182) JS framework send empty attributes and styles to native
Hanks Zhang created WEEX-182: Summary: JS framework send empty attributes and styles to native Key: WEEX-182 URL: https://issues.apache.org/jira/browse/WEEX-182 Project: Weex Issue Type: Bug Components: JSFM Reporter: Hanks Zhang Assignee: Hanks Zhang After JS Framework support batched update of attributes and styles. (https://github.com/apache/incubator-weex/pull/819) Sometimes it will send empty or the whole attributes and styles to native because there is no diff in it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Separate the weex-vue-render from the incubator-weex repo
I noticed that the weex-vue-render have already been moved to https://github.com/weexteam/weex-vue-render So, I think the source code of it should be removed from the [apache/incubator-weex] repo. I created an issue to track it: https://issues.apache.org/jira/browse/WEEX-181 2017-12-19 23:42 GMT+08:00 He Sai : > @Jonathan Dong, Great, Thanks ! I'll transfer it into weexteam group soon. > > 2017-12-19 19:04 GMT+08:00 Jonathan Dong : > > > That is nice. I can help to create a repo in https://github.com/weexteam > > to host the codes here instead of using a personal github account. > > > > On 19 Dec 2017, 5:52 PM +0800, He Sai , wrote: > > I think it's better to separate it from this repo. It's more like a DSL > > layer stuff, a > > javascript framework to run the dot vue file on web platform, not a > feature > > of > > weex SDK it self. Since the rax DSL framework is not included in this > repo, > > it's > > more or less the same. > > > > I have already created a new repo for these codes, with building scripts > > and > > test cases: > > > > https://github.com/MrRaindrop/weex-vue-render > > > > The main project in this repo should be more focusing and cleaner, > > and the render codes in html5 folder could all be removed later. > > > > 2017-12-19 17:31 GMT+08:00 Hanks Zhang : > > > > The "weex-vue-render" is a component and module library for Vue.js. It > > enables pages written in Weex + Vue to run on the Web platform. It can be > > used to downgrade the weex native pages to web pages. > > > > However, I think this package should separate from the incubator-weex > repo. > > > > Because it doesn't rely on any code of WeexSDK, and WeexSDK doesn't rely > on > > any code of weex-vue-render neither. Even the vue framework itself is > > separated from the incubator-weex repo, weex require it as a dependency, > > not to mention that weex-vue-render is not a part of WeexSDK. > > > > Moreover, weex-vue-render also required many web dependencies which could > > not be used in WeexSDK. I think it's a better to keep the source code of > > incubator-weex more simple and move the weex-vue-render and its > > dependencies to a separate repo. > > > > > > > > > > -- > > > > Best Wishes！ > > _danz > > > > > > -- > > Best Wishes！ > _danz >
[jira] [Created] (WEEX-181) Move weex-vue-render out to weexteam
Hanks Zhang created WEEX-181: Summary: Move weex-vue-render out to weexteam Key: WEEX-181 URL: https://issues.apache.org/jira/browse/WEEX-181 Project: Weex Issue Type: Improvement Reporter: Hanks Zhang Assignee: Danz He As discussed in https://lists.apache.org/thread.html/2c009f1b741a7f1baec07e5a26a9d2c2e8d846abedd85fbb7de32559@%3Cdev.weex.apache.org%3E , the weex-vue-render should be separated from the current repo. The new repo is located in https://github.com/weexteam/weex-vue-render , I think the source code of it should be removed from the apache/incubator-weex repo. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: 回复： Thefocus of thepage keyboard trigger led to the top of thenavigation barcan not berestored
Can you try to debug by dependency the source code? as I can not re-produce the problem here. 2017-12-20 14:55 GMT+08:00 唐波 <765471...@qq.com>: > Just try to use Weex Playground scan code is no problem, the installation > to the iOS native app to run there will be just the problem. > > > > > -- 原始邮件 -- > 发件人: "我自己的邮箱";<765471...@qq.com>; > 发送时间: 2017年12月20日(星期三) 下午2:33 > 收件人: "dev"; > > 主题: 回复： 回复： Thefocus of thepage keyboard trigger led to the top of > thenavigation barcan not berestored > > > > Iphone 6 plus phone for use, iOS 11, weex sdk version 0.17 > > > -- 原始邮件 -- > 发件人: "xing zhang";; > 发送时间: 2017年12月20日(星期三) 下午2:28 > 收件人: "dev"; > > 主题: Re: 回复： Thefocus of thepage keyboard trigger led to the top of > thenavigation barcan not berestored > > > > what's your environment, like iOS version, weex sdk version and input > method, try to update it maybe could resolve it, > I can not reproduce with your case on iOS 11 , WeexSDK 0.17.0 > > 2017-12-20 14:14 GMT+08:00 唐波 <765471...@qq.com>: > > > like address: > > > > > > http://dotwe.org/vue/af78353d2f73a9881b94e45f6e2f5a42 > > > > > > > > > > -- 原始邮件 -- > > 发件人: "Adam Feng";; > > 发送时间: 2017年12月20日(星期三) 下午2:05 > > 收件人: "dev";"dev" > incubator.apache.org>; > > > > 主题: Re:回复： 回复： Thefocus of thepage keyboard trigger led to the top of > > thenavigation barcan not berestored > > > > > > > > Maybe you should give a demo on http://dotwe.org/vue > > > > > > Thanks. > > Adam Feng > > > > On 20 Dec 2017, 2:00 PM +0800, 唐波 <765471...@qq.com>, wrote: > > > Not a hot issue, right? The same is true of closed hot spots > > > > > > > > > > > > > > > -- 原始邮件 -- > > > 发件人: "Adam Feng";; > > > 发送时间: 2017年12月20日(星期三) 中午1:50 > > > 收件人: "dev";"dev" > incubator.apache.org>; > > > > > > 主题: Re: 回复： The focus of thepage keyboard trigger led to the top of > > thenavigation bar can not berestored > > > > > > > > > > > > It looks something wrong happen with the layout while the personal > > hotspot is open. > > > > > > Thanks. > > > Adam Feng > > > > > > On 20 Dec 2017, 1:45 PM +0800, 唐波 <765471...@qq.com>, wrote: > > > > Due to the inability to add picture attachments, picture link > address: > > > > one: https://segmentfault.com/img/bV0xW6?w=639&h=1136 > > > > two: https://segmentfault.com/img/bV0xXu?w=639&h=1136 > > > > three: https://segmentfault.com/img/bV0xXL?w=639&h=1136 > > > > > > > > > > > > -- 原始邮件 -- > > > > 发件人: "xing zhang";; > > > > 发送时间: 2017年12月20日(星期三) 中午11:42 > > > > 收件人: "dev"; > > > > > > > > 主题: Re: The focus of the page keyboard trigger led to the top of > > thenavigation bar can not be restored > > > > > > > > > > > > > > > > Did you use weex for navigationBar? Sure, you can attach > > > > > > > > 2017-12-20 10:53 GMT+08:00 唐波 <765471...@qq.com>: > > > > > > > > > Can I attach a picture? > > > > > > > > > > > > > > > > > > > > > > > > > -- 原始邮件 -- > > > > > 发件人: "我自己的邮箱";<765471...@qq.com>; > > > > > 发送时间: 2017年12月19日(星期二) 下午2:30 > > > > > 收件人: "dev"; > > > > > > > > > > 主题: The focus of the page keyboard trigger led to the top of the > > > > > navigation bar can not be restored > > > > > > > > > > > > > > > > > > > > Hi Weex Team: > > > > > we have a problem . The bottom of the page input trigger keyboard > > event > > > > > causes the navigation bar to be top up. After the keyboard is > > collapsed, > > > > > the navigation bar is restored, and the overall effect is like the > > entire > > > > > page layout being topped up. > > >
[jira] [Commented] (WEEX-179) List View Component supported show scrollbar options
[ https://issues.apache.org/jira/browse/WEEX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299835#comment-16299835 ] ASF GitHub Bot commented on WEEX-179: - Github user gubaojian closed the pull request at: https://github.com/apache/incubator-weex/pull/951 > List View Component supported show scrollbar options > > > Key: WEEX-179 > URL: https://issues.apache.org/jira/browse/WEEX-179 > Project: Weex > Issue Type: Bug >Reporter: codefurture >Assignee: Adam Feng > > List View Component supported show scrollbar options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-179) List View Component supported show scrollbar options
[ https://issues.apache.org/jira/browse/WEEX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299834#comment-16299834 ] ASF GitHub Bot commented on WEEX-179: - GitHub user gubaojian reopened a pull request: https://github.com/apache/incubator-weex/pull/951 [WEEX-179][android]List View Component supported show scrollbar options [WEEX-179][android]List View Component supported show scrollbar options You can merge this pull request into a Git repository by running: $ git pull https://github.com/gubaojian/incubator-weex release-0.17-support-show-scroll-bar Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/951.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #951 commit bc96b6525215fe7dde55ad3b11d27e0d98020a47 Author: jianbai.gbj Date: 2017-12-21T02:41:39Z [WEEX-179][android]List View Component supported show scrollbar options > List View Component supported show scrollbar options > > > Key: WEEX-179 > URL: https://issues.apache.org/jira/browse/WEEX-179 > Project: Weex > Issue Type: Bug >Reporter: codefurture >Assignee: Adam Feng > > List View Component supported show scrollbar options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
