Meeting minutes
<xfq> w3c/
<xfq> scribe:
xfq: welcome to our Chinese-IG meeting
… first, we have Qingjian Song from Microsoft Edge to talk about a few update in the PWA slide bar
PWA in Sidebar: Leveraging innovation trends to improve user experience by Qingjian Song (Microsoft)
Qingjian: currently PWA is usable in different browsers and different devices
qinigjain: what's the difference of PWA and website runniing ini a standalone window?
… you can write a PWA on Windows to handle the JPEG editing and view
… in one simple sentence, it's like a Windows PWA application
… through the Project Fugu
… we keep adding native features to PWAs
… one thiing to be pay attention to iis responsive design
… people can use App Copilot to create more scenarios that the user can interact with
… it's a new ecosystem that you can create an app in the sidebar
… now we plan to open it to the ecosystem
… to showcase web apps
… it means that it will get some new users and new straffic
… because it's a new surface
… we hope that it is a very little barrier and contains very minor changes to existing web apps
… so how to build a sidebar app?
[Qingjian shows a web app manifest]
qingjian: you can configure your site's web app manifest
… we write an explainer to get all kinds of feedback
… I think it's a very important stage
… to upstream everything into web standards
… if for some scenario you didn't want to install your website as PWA
… @@
… we propose that we add edge_side_panel member to web app manifest
… in the future we will consider to use name, short_name, description etc. from web app manifest
… we different different user agents
… because there are some different requiirements for different developers
qingjian: @@1
[Qingjian shows a demo]
qingjian: the demo iis in a very early stage
… we work with iQIYI to add short video
… you can easily open that into a tab
… it can also be a source to promote a website
… here is the new design
… natively in the browser we will have more features to try to promote the usage of the sidebar
… it's quite different with traditional PWAs
… for next step we try to bring more capabilities to PWAs
… like manifest shortcuts
[Qingjian introduces the use cases]
qingjiani: it's a bit like extensions
… but the difference is that extension tries to access the DOM
… it's very low level
… we hope that we can keep a high level iinterface
… we try to standardize the side_panel member
… you can also use diisplay_override
… that's a direction of our upstream work
… I also notice that even Chromium is experimenting this
… welcome to go to read the sidebar explainer on github
… because that's in a very early stage
… configure PWA is just a first step
… how to land it into Edge is important
xiaoqian: thanks Qingjian
… during TPAC Chromium proposed a Menu App API
xiaoqian: is there any difference between this and the API you proposed?
https://
<xfq> s/Chromium proposed a @@ API/Chromium proposed an App Menu API/
Qingjian: this is different from sidebar API
… it provides convenience for already installed PWA
… it allows website A to install website B
… sidebar PWA is for enabling siidebar of a PWA
… it's like sidebar extensions
… extensions require additional installation by the user, while the sidebar does not require additional permission consent by the user.
… it is currently on github as an explainer
xfq: your talk reminds me of our MiniApps Widgets specs
… I wonder if we can work together in the future
Qingjian: yeah
Qingjian: also the -1 screen use cases
… happy to work with the MiniApps community
https://
Qingjian: the design is actually quite similar
… both using declarative, Manifest
… to minimise the cost, but maximise the opportunity to interact with the users
… now Windows has opened this APIs to the developers
xfq: but the entrance is still the browsers, right? unlike the installable WebApps
@@: how the sidebar apis communicate with the main web pages?
… once it's opened?
Qingjian: it's an independent web content
@@: how did it get the content of the web page?
Qingjian: it's not opened to the normal web pages, some extra files will offer this capacity
… with the permission from users to transfer the content to the sidebar
… so there will be some extra API required of the browsers
@@: so right now it's still independent?
Qingjian: right, but we are looking forward to future extensions
… right now it's a slight improvement to the traditional web apps
Lei_Zhao: how the sidebar update the content?
Qingjian: since Sidebar is within the browsers
… there should be a web store inside
… all the update request should go to the web store
… but right now it still needs further design and implementation
… please talk to me if you have any thoughts or advice
… we are working on the basic architecture of the Sidebar APIs
… so very few partners are inside the experiment
xfq: there has been several breakout sessions from the Chinese members this week
… shall we have some discussion on the follow-up actions?
… let's start with Accelerating the Web performance by compiling Javascript code to WASM session from Lin Shi
Accelerating the Web performance by compiling Javascript code to WASM
Summaries and follow-up actions for the breakout sessions
https://
Wei: this is one of our attempts to work with the W3C community
… we hear some good feedback from the other vendors
… some of them show interest
… some of them were doing similar works
Shi: these are our exception for WASM
… DLL Support, this is under consideration in the WASM community
… GC Support is very vital
… DOM Support
… using WASM as a fundamental language is a long term experiment
… we would like to share the outcome of our experiment with the W3C community
… right now we are working on stage 3
… expecting more datas and performance metrics
xfq: it'd nice if there would some reports or proposals, as the basic of future discussion
Wei: I talked with Mike yesterday
… look for a host of this open source project
… we are still exploring the possibilities
… it'd be great if the open source communities could work with the standard communities
xfq: agree
… let's continue the discussion in the future
Lin: the high demanding RTC use cases session
<angel_> WebRTC doc:https://
WebRTC use cases and requirements under high-demanding real-time communication scenarios
Lin: we got these use cases from our usage of WebRTC in practice
… one is about the statics of the freezing time
https://
Lin: we would like to have more precise metrics of the freezing time
… this is about the video
… another requirement is about the audio
… we would like to have more parameters for the freezing of audio as well
… there is another issues about the packaging of the audio
… once it's bigger than 1500 characters
… although it's still an unusual use case
… but we have still some experiment in Audio Vivi
… on high quality audio and video transmission
… happy to work with all the vendors in the industry
… the third issue is about the resuming the video once it goes to the background in iOS
… we have filed an issue about it in Chromium
… these are the suggestions from WebRTC usage
… would like to work together to improve the user experience of the WebRTC together
<xiaoqian> s/WebRTC together /WebRTC
xfq: let's work on some requirement documents in the WNIG
… there has been a lot of discussions within the Chinese members
Lin: right, we should also communicate the other participants in the breakout session
… from the WebTransport WG, the WoT WG, and from the WebRTC WG
… we should have further discussion about how to improve the specs
Feel the Vibe: enhancing haptics for accessibility and more fun
https://
https://
[Roy shares screen]
roy: In the process of developing games, Tencent Games discovered some needs for haptics, and used different haptics to feedback different information in the game
… They felt haptics could serve as a universal human language
… They hope to advance haptics technology in various orgnizations
… What kind of haptics represents what kind of information?
… maybe standardize it in W3C or some other SDO
… Through haptics, a lot of information can be given to low vision people
[Roy introduces use cases]
Roy: it is not just an accessibility use case
… also for media
… we also discussed with security folks
… it can also be used with Web Authentication
… In response to these needs, Tencent has already done a lot
… in ISO, MPEG, IETF, Khronos Group OpenXR etc.
… W3C has a Vibration API
… But many needs cannot be met
… Microsoft is also developing a HapticsDevice API for the Web
… they want to work with various groups to move it forward
xiaoqian: Tencent would like to work with vibration sensor vendors
… Maybe we can start a community group to discuss it
How is your 2023 with W3C?
xfq: anything you would like to share about your 2023 in the W3C community?
… any plan for next year?
… please talk with your China team during the tea break
[adjourned]