Jan 28 2021 08:04 PM
Jan 28 2021 08:04 PM
yesterday, when entering the applications intalled through web pages, i saw that the applications were running but they had to run completely by opening the application twice. i hope they review this problem soon because if it bothers me to start the application twice.
Jan 29 2021 01:55 AM
Jan 29 2021 10:33 AM - edited Jan 29 2021 01:07 PM
Thank you, it is fixed now Version 90.0.782.0 (Official build) canary (64-bit)
I have a quick question about link capturing for PWAs in Edge canary
I'm using these 2 flags
and I have Twitter and YouTube installed as PWAs.
when I try to share a YouTube link to Twitter using the share button on YouTube page, I see Twitter PWA opening and I also see a new Edge window opening with Twitter website.
so this causes 2 things to open, instead of 1. I've sent feedback before but was wondering if this is an expected behavior (I hope not) or just a bug.
Twitter opening in Edge window loads my feed, Twitter that opens in Twitter PWA shows me the content I shared from YouTube, ready for me to click on post.
so the extra Twitter that opens in Edge window is unnecessary.
Jan 29 2021 11:26 AM
@HotCakeX , interesting. I'm not seeing that with my builds. If I launch the youtube app and click to share a video to Twitter, I see twitter load in the browser itself, not as a PWA. We're actually doing work on Share currently that is blocked by work coming in some upcoming releases, so I wasn't expecting it to launch the PWA yet.
I wonder if there is an additional flag you have set or something subtle I'm missing.
All that said, it is a bug if we launch Edge as well as the PWA. When all is said and done, if you have the PWA installed, that should be the target for the share contract.
Jan 29 2021 12:50 PM - edited Jan 29 2021 01:10 PM
oh yes, sorry, I also have this flag:
and I installed Twitter as a Tabbed PWA, in fact I install all my PWAs as tabbed since this tabbed PWA feature was introduced, i find it very useful.
(just to clear any confusion in the way I explained it, when I try to share a YouTube video, I use the share button that's under the video itself, not the share button on Edge toolbar)
all the flags I've enabled that produce this behavior:
so I'm experiencing something that's from the future? :)
because it's been happening for ~a month.
please let me know if there is any other data I can send to help.
Jan 29 2021 01:24 PM
ah @HotCakeX !
This is quite interesting. I enabled the Tabbed PWA experience and now I see what you mean. That is a bug that I'm logging today. The Tabbed PWA experience is relatively untested because we want more design before we enable it. Google introduced the feature and they have been working through feedback they are getting as well.
One super interesting thing that we could probably do is: install as tabbed, see a bug, uninstall and reinstall without tabs, see if it still repros.
I'm surprised that Tabs are affected by the Share scenario, so I'm now confident there will be more :)
Jan 29 2021 02:38 PM
Glad to hear that,
oh, well i turned it on the day it was added to Edge canary, been using it since then, makes things easier, when i middle click on links in Twitter or YouTube videos, i don't have to switch back and forth between windows anymore.
I uninstall all my PWAs, and now installed YouTube and Twitter as a regular PWA, that open in a separate window with no tabs.
now, when sharing YouTube video to Twitter, only Edge window opens, no more PWA opening.
I'm going to switch back to the tabbed mode and keep using it.
I think it'd be useful if you guys gave us quests, to tell us which feature to focus on and test, which flag to turn on, etc.
something else i feel the need for is to have the global media controls and PiP in PWA UI. when i watch YouTube in PWA, i have to open a new Edge window in order to use its UI to click on PiP button.
Jan 29 2021 03:01 PM
@HotCakeX, PiP and global controls are definitely in our backlog. Any time you need to switch to the browser to do something is a case where my team feels you have a bug. Others might say it's by design, but I want PWAs to behave as separate entities, which means only switching to the browser when absolutely necessary.
As for quests: that's a really good idea. We used to do that when Edge was part of Windows. As part of Windows Insiders I'd write quests and push them out. We have not implemented that yet, but I think it's got a lot of value, so I'm going to look into starting something soon.
Feb 03 2021 11:36 AM
I totally agree with you,
you know exactly how PWAs are supposed to work, "separate entities" and "only switching to the browser when absolutely necessary"
and that's interesting, I didn't know the same team members used to work on EdgeHTML are working on Edge Chromium now.