w3c/miniapp-components

MiniApp Components

This repository is the home of the MiniApp Common UI Components document being worked on by the MiniApps Community Group.

Useful links

• Explainer
• MiniApp Common UI Components
• The MiniApps CG homepage

miniapp-components's Issues

Sections and content of the components specification

For those that are not following the discussions, this work doesn't want to replace the Web Component mechanisms. Instead, it aims to collect and inform about the common features of the different MiniApp implementations.

I've drafted a first proposal with the outline of the document ant the sections that can have the document (#5), but it's just an early suggestion.

1. MiniApp Pages and Components (intro to explain relation, custom components, the difference with Custom Components, etc.)
2. Markup and templating (can we find a common pattern?)
3. MiniApp Interface (properties and methods)
4. Component Declaration and Reuse
5. Component Events (Binding, Listeners, Types)
6. Scripting Resources (ECMAScript support)
7. Stylesheets (CSS profile, non-standard properties)
8. Component Lifecycle (if it differs from the MiniApp Lifecycle spec)
9. MiniApp Elements (or vendors' built-in components)

Feel free to comment here on the overall structure of the document, also the parts we should (or should not) include, and what is the content for each section.

Load ReSpec script in defer mode

Change the load mode of the ReSpec script, using defer instead of async as recommended in the specification.

This approach seems to duplicate and redefine HTML

I know this is relatively early; however, I'm very concerned by the approach taken here. It seems there is overlap and redefinition of the Web platform pieces themselves - as in, subsetting HTML+CSS+JS would be concerning, but this is defining elements like <image> all over again, in a way that is close to but not quite "the Web". (For example, the CSS and JS files are, presumably, automatically applied to the HTML file, since there's no mention of <LINK>, <STYLE> or <SCRIPT> support?). It also seems (from the inclusion of a <text> element) that the flow text model is very different from the normal HTML one as well. (what happens to text outside a <text>?)

I really think this should be defined in terms of custom elements, and default HTML/CSS/JS.

Maps

As the Report on the Joint W3C-OGC Workshop on Maps for the Web says:

Geospatial information on the Web is fragmented, inadequately covered by Web standards, and lacking interoperability.

Most miniapp user agents have their own map components. At the same time, W3C is also discussing the standardization of maps for the web. I included some links here as a reference for future component standardization:

• Use Cases and Requirements for Standardizing Web Maps
• map in Alipay
• map in Baidu
• map in ByteDance
• map in QQ
• map in Quick Apps
• map in Weixin/WeChat