Meeting minutes
UI Components
[martin shares his screen]
martin: this is also related to https://
… please review the diagram
… regarding to components
… we have been discussing internally
… I will describe briefly about the differences with web components
[martin describes his proposal]
martin: reusing the HTMLElement interface
… the current MiniApp implementations follow the model–view–viewmodel architectural pattern
… regarding the common events, I won't go into details here
… most of these events are similar to DOM events
… longpress, swipe, etc. are not in the standard events
… in case those are not standards we can propose to existing WGs
… or just discuss them based on existing DOM events
… I think the proposed solution is to use the standard html+DOM
… it would be compatible with the existing HTML+DOM standards
… some discussions in the open issue some folks recommend us using existing standards
… if they're not in the current standards we can propose them in the relevant WGs
[martin shows a list of basic elements]
martin: some of them have equivalent elements in HTML
… we can just change the name
… some are under discussion under the Open UI community
… in terms of the structure of the markup language, events, and attributes
… the best way to do it is to propose them to the Open UI community
… some elements list list
… we have HTML elements that are related
… but we have other requirements
… so we can use web components
… we can reach out to the Open UI community
… if we can reuse the existing elements we can just use it
… some challenges we have include new elements not in the html spec, but somehow in frameworks
… 2) similar elements, like <image>, <progress>, <text>, etc.
… @@
… 3) non-standard attributes in MiniApp components
… like disable and focusable
… we can adapt and use the standard attributes
… or create a basic MiniAppElement that extends HTMLElement, but this prevents MiniApps from using web components
… in the case of events
… we can adopt the standard events like PointerEvents
… for new events we can propose to relevant WGs if needed
… @@
… once we have consensus we can start writing the proposals
… we should document what are really in the standards
… in a note
… requirements
… subset of CSS features we use
… also for events etc.
… if we push a new solution
… for a non-HTML-based standard
… we need to create a domain specific language based on XML
… create an XML schema
… and scripting
… these are the two main options
… 1) following the standards
… there are some implications for most of the miniapp implementations
… 2) bring a new set of languages and new model for MiniApps
… also, we can refer to the SVG spec for graphics
… we can find examples of how to define elements, how to do styling
… we can also look into TTML
… in case we need to create a vocabulary
Zitao_Wang: we have disucssed this for a long time
… especially how to make it compatible with existing specs
… how to develop standards that make sense
… how to move the proposal forward?
xiaoqian: thank you
… excellent presentation
… wonder whether you can share this with the public
… Mike Smith is in the W3C HTML WG
… I wonder if you'd like to ask his opinion on this work
martin: it's also interesting to hear other vendors' opinions
xiaoqian: we should get more attention from other people in the w3c community
… can we have a breakout session in TPAC about MiniApp components?
… or an agenda item in the MiniApps WG meeting?
xiaoqian: TPAC is just like two months away from now
… we can prepare for TPAC
martin: I think it's important having this discussion
xiaoqian: as a follow up we should get opinions from Alibaba, Baidu, Xiaomi, and other MiniApp vendors
… we can set a deadline for comments
martin: we can set a special meeting on this if anyone wants to discuss this
Dan_Zhou: I agree to reuse HTML elements
… we can have more readability and SEO
… I don't know if developers are allowed to access the DOM in JavaScript
Dan_Zhou: currently the DOM is not allowed to be accessed for security and perf reasons
martin: it could be a subset of HTML elements for any reason, I don't know
… full CSS is not mandatory
… for scripting we can restrict for security or other reasons
… for apis we can have similar discussions
… perhaps in a dedicated spec
Dan_Zhou: we can discuss when we have some concrete proposal
martin: for epub they define attributes for ebooks
… subset of CSS
… also with scripting
Zitao_Wang: another topic is API
… if we want to discuss it in a TPAC breakout session
… we can discuss it in the later TPAC-related agenda
Dan_Zhou: we can do more work on UI components and API
<maritn> +1 to a session on UI Components and APIs at TPAC
Dan_Zhou: can we collect topics in an issue?
Dan_Zhou: so that other people can give their opinions
Testing
<maritn> Open issue: https://
martin: the idea is to reuse the structure of EPUB tests
martin: we can include both the documentation and the tests
… anyone from the community can help us
… to create new test cases
… we can classify the topics
[martin shows an example test]
martin: must vs should vs may
… the system will automatically generate the documentation
… the test is a JSON-LD document
… we can link the test and the spec
… in the spec we can see the test coverage
… it's already proven in the EPUB testing process
… the system can automatically generate a MiniApp package
… this is the idea
… if you agree with the methodology we can move forward
… we can do it in many other ways but I think this is a way to do it easily
Dan_Zhou: very wonderful example for us to learn
xiaoqian: I agree
… excellent work
… I think for this part the WG and CG should work on a Chinese version of the readme
… some contributors may have some difficulties reading English
martin: I think if we agree to use this approach
… we can develop this as soon as possible
<xfq> +1
martin: I'd be glad to explain more technical details if anyone is interested
Dan_Zhou: I need to look into it to see if i can help you
Widget
[Xiaoping shows his screen]
Xiaoping: I'll introduce the draft widget spec
[Xiaoping shows the outline of the widget spec]
[Xiaoping explains the terminologies]
Xiaoping: unlike MiniApp pages, there isn't a start widget for a MiniApp widget
Dan_Zhou: thank you
… I look forward to the PR
Zitao_Wang: I also look forward to the PR
… some work is related to existing WG work
… especially the lifecycle-related work
https://
Dan_Zhou: we can review this PR
AOB
Dan_Zhou: next CG meeting will be July 21
<maritn> +1 July 21 for next meeting
xiaoqian: W3C WebApps WG is waiting for our feedback about joint meeting on manifest
… xfq can you create an issue for that?
xfq: yes