-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to "Pop" Video Back into YouTube #16
Comments
This may not be needed, as the embedded YouTube player (used for the popout window) typically shows a "YouTube" button for opening the video on the full YouTube site. The only real difference between the existing (native) functionality and what was proposed in this request is that the existing (native) button does NOT update the original tab/window (if the user left it open when opening the popout player). Instead, it simply opens another window/tab altogether, so the video would then be open in 2 regular windows/tabs (plus the popout window), although the original one and the popout one are both paused. As such, I'm going to leave this open, but the priority for implementing this is low. |
#25 complicates this a little bit, as it hides the custom controls in the popout player (although users can disable that to restore the custom controls in the popout player). So there could be a need for several settings related to the custom controls in the popout player in order to accommodate both requests:
|
#32 probably further complicates this, as that would allow the user to hide all video player controls (not just the custom popout player button) on the popout player. |
After opening a video in the popout player, it would be nice to be able to "pop" the video back into YouTube (even if the original YouTube window/tab was closed).
For the implementation, this would likely mean:
This should be possible in the Web Extension, but probably not possible in the userscript version (unless pure JavaScript messaging is used instead of the Web Extension APIs for messaging).
The text was updated successfully, but these errors were encountered: