You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also understand the hesitancy to write site specific code but I think giving us the option to customize under the extension settings for things like most commonly used websites like YouTube would be great.
Also I do think it is possible to give further option of writing scripts for power users so we can turn the entire webpage or specific div element into a PIP or multiple PIP would be great. (Lots of work ik and maybe deserves a dedicated issue or I will just fork this when time permits)
Closed and Open Issues that are related and can be addressed with the updated API #23 #26 #28 #38 #51 #53
The text was updated successfully, but these errors were encountered:
Since the document PIP is linked to the tab that opened it you are able to open multiple PIP. One for each browser tab. Documentation doesn't explicitly state this but it appears that it is possible given how the API is structured.
Also I've been trying to get this to work for generically for websites, but because it is (more than with normal fullscreen-faking) a lot of moving around of DOM nodes, it does break most sites consistently 😱
Chrome API has been updated with latest PIP feature. Here is the link
https://developer.chrome.com/docs/web-platform/document-picture-in-picture
I also understand the hesitancy to write site specific code but I think giving us the option to customize under the extension settings for things like most commonly used websites like YouTube would be great.
Also I do think it is possible to give further option of writing scripts for power users so we can turn the entire webpage or specific div element into a PIP or multiple PIP would be great. (Lots of work ik and maybe deserves a dedicated issue or I will just fork this when time permits)
Closed and Open Issues that are related and can be addressed with the updated API
#23
#26
#28
#38
#51
#53
The text was updated successfully, but these errors were encountered: