Meeting minutes
Dan_Zhou: Zitao_Wang will introduce the gap analysis between components in HTML5 and miniapps
Dan_Zhou: we will also discuss the progress of GitHub issues
Common UI Components
[Zitao_Wang shares his screen]
zitao: want to introduce the gap analysis between common events in the components of HTML5 and miniapps
[Zitao shows a comparison table between MiniApp vs HTML5 / Open UI]
zitao: here I listed the common events in 20 components in MiniApp / Quick Apps
… same function but different names
… like globalX/globalY and screenX/screenY in touch event
… some events have different definitions
… like localX and localY in miniapps
… going to the next slide
… this slide shows a comparison of components
… even some components have correspondents in HTML5 / Open UI
… they miss some attributes
[Zitao shows a comparison of the select component in Huawei MiniApp and the select element in HTML]
zitao: some are common attributes, some are only supported by Huawei miniapp, and some are only supported by HTML
… we should harmonize with each other
… define a standard to describe miniapp components
… reuse HTML5 components
… any comment?
… I only list the differences between HTML5 and Huawei Quick Apps here, not the differences between the various MiniApp platforms
… we also need to unifiy the miniapp platforms
Dan_Zhou: can we start a spec about component?
Zitao_Wang: I'd like to
Zitao_Wang: I'd like to hear your comments
Zitao_Wang: on whether we have consensus on this area
Dan_Zhou: xfq?
xfq: Before discussing specific attributes, we need to decide how to define a component
https://
xfq: I suggest Zitao_Wang write specific suggestions in the GitHub issue, or write an explainer / draft spec, so that we have content to discuss.
GitHub issues
<martin> For our reference, issue related to UI components: https://
https://github.com/w3c/miniapp/issues/162
Dan_Zhou: Changhao_Liang has come comments on this
Changhao_Liang: I'm a new member of the Baidu MiniApp Architecture Development team
Changhao_Liang: I'm also a beginner of developing miniapps
… I can give comments about the issue about supporting the DOM
… there are actually two issues
… one is accessibility tree
… the other is DOM support
… unfortunately MiniApps don't support DOM manipulation like the web
… MiniApps use two threads
… there are some limitations
… we can use some vue (?) like framework
… instead of use low-level DOM APIs
… miniapps support querying the DOM information
… but do not support manipulating the DOM directly
… the second issue is a11y
… we think that we should support accessibility in our standards
… in the current state our princeple is to expose the DOM as little as possible
… we need to make a survey to collect requirements as English documentation
… we review it together
… we don't know how to support accessibility tree now
xfq: We need to collect the requirements first
xfq: Regarding accessibility tree, I can reach out to the accessibility groups to see how we can collaborate
zitao: if we want to support standard HTML and DOM we already support accessibility tree
… if we don't want to support standard HTML5 and expose the DOM we need to do more work on accessibility
… So before we solve the accessibility tree problem, we have to decide whether we need to support standard HTML5 and the DOM first
Dan_Zhou: I think the MiniApps architecture may be difficult to change
… because MiniApps usually need to be reviewed by the hosting platform to go online
zitao: we need to summarize our reason and put it in the GitHub issue
Dan_Zhou: I'll write it down in the issue
yongjing: can we separate the DOM and accessibility tree issue?
yongjing: accessibility is important and we should address this issue
yongjing: but we don't need to couple it with DOM support
Dan_Zhou: agreed
xfq: will file a separate issue
MiniApp Widgets
Dan_Zhou: I raised an issue re MiniApp widgets
https://
[Dan_Zhou explains this issue]
Dan_Zhou: maybe Yongqing can talk about the plan for MiniApp widget
Yongqing_Dong: widget in MiniApps are currently mostly used in the "card" scenario
… right now it is not often used in other scenarios such as in apps
… so this is the current status
Dan_Zhou: I think the card in the host app can be also defined in terms of widget
… we can talk about this definition fo widget
… our platform has some exploration about this
Yongqing_Dong: sure, but the fact is the widget which is defined in the card scenario is the same as @@
… could cause performance issuses
zhoudan: maybe we can comment in the issue
… any other comment on miniapp widgets?
Yongjing_Zhang: I think the current document it's a requirement document
… I'm not sure how it will be implemented
… I'm expecting some follow-up
… either a separate document
… or more content in a normative spec such as MiniApp Packaging
… regarding Dan's comment whether it's a card in OS or in an app
… we could find some common requirements
… we can work together
… my two cents
https://github.com/w3c/miniapp/issues/165
Dan_Zhou: shall we give more explanation about differences of PWA and MiniApps?
xfq: We haven't updated the white paper since TPAC 2019. If we want to restart the work, we need volunteer(s) to edit the document.
https://
Dan: Do we need to discuss other issues today, such as TV and IoT?
xfq: If Qing is not there, it's a bit difficult to discuss these issues
Dan: any other issues?
Next meeting time
June 17, same time