Issue Tracker
Filter controls will go here
Created: 1776207644 Priority: B Status: doing Description: Implement reliable cross-origin behavior for PWAs and apps that are using the javascript fullscreen API. By default, state is lost when moving from one origin to another inside of installed PWA. This could be implemented, for example, by detecting that the application is in fullscreen or is in a PWA and using "soft-switching" to give the illusion of going cross origin while actually remaining within the starting origin itself. It could also include methods such as implementing a visual clue that indicates that the current application is a preview of another, embedded within the first, along with an option to navigate to said app in another tab/PWA window. For PWAs, investige cross-PWA linking and see what the best user experience is for this. Currently, PWA capability are fullscreen via the API are disabled until this is resolved. Furthermore, PWAs install with a static name - we should use the static, short, menu-compatable title of the app as its PWA title and not its dynamic page title. Installed PWAs reset to the starting state when closing and opening again. This should be fixed - they should probably start in the last place they left off. Hopefully, a local storage API and a "dummy" starting state can resolve this. Affected Parts: None Linked Issues: Full Desktop Window SupportBdoing