Open chiefcll opened 3 years ago
Just came across this issue. I would be happy to work with the MEIG folks to organize a joint call with the MiniApps CG/WG.
(MiniApps for TV may be a topic to discuss. Feel free to suggest others.)
did a joint call take place? CTA Wave has an active discussion on this topic, related to a smart TV survey on the use of HTML5.
We haven't had the joint meeting yet. @xfq I'll email you to plan this for an upcoming MEIG meeting.
Thanks to @xfq, we've organised this for the November MEIG meeting, which will be at a different time to usual:
Tuesday 2 November 01:00 London (UTC) / 09:00 Beijing / Monday 1 November 21:00 US Eastern / 18:00 US Pacific
Meeting details: https://www.w3.org/events/meetings/24197f7d-7516-47be-94fe-d43977c22708
Thanks, @chrisn! I have a question. In https://github.com/w3c/media-and-entertainment/issues/75#issuecomment-926051056 you said the meeting date is 2 November, but on the W3C Calendar, it's 9 November. Which date is correct?
Sorry, I somehow put the wrong date. The meeting is on 2 November. I have sent an updated calendar invitation.
In the MiniApps introduction, it was mentioned that, at least in some implementations, CSS gets used to style apps even though HTML in itself is actually not supported for now.
CSS rules start with selectors. I'm wondering what these selectors select in such a design and what properties are actually supported?
For instance, CSS gets used in Qt as well, with the documentation explaining what selectors get interpreted, as well as the list of CSS properties that are supported.
Said differently, I'm wondering about the role of CSS in a model where the app controls the rendering, either going through some platform-provided graphics API or using a canvas-based approach.
There is some basic information about CSS in https://w3c.github.io/miniapp-packaging/#sec-miniapp-resources-css and https://web.dev/mini-app-markup-styling-and-scripting/
The MiniApps WG does have plans to document CSS support in more detail, but they are not currently the top priority.
MiniApps have some interesting parallels with app development on smart TVs, set-top boxes and other embedded devices. As part of TPAC 2021 plans (#71), it could be worth considering a joint call with the Mini Apps CG
Some things to discuss:
Shared Framework Code: Set top boxes are limited by performance and typically use the same JS libraries (especially if developed by the same company). Being able to create a runtime library that is shared by multiple browser pages could reduce overall memory usage. For instance, we could create a bundle React + libs, give it a name, and then share that same bundle with another window.
Native UI Components: The ability for browser to include a framework for UI components that could be used by apps could reduce development time and increase performance. Something like being able to define Web Components that are embedded in the browser (maybe even native code / web assembly) that are available for all windows without needing to be loaded.
Anything else?