-
Notifications
You must be signed in to change notification settings - Fork 158
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
Manifest V3 killed video query selector #75
Comments
This extension is an actual chrome extension and uses manifest v2. See https://github.com/GoogleChromeLabs/picture-in-picture-chrome-extension/blob/master/src/manifest.json#L38 |
Isn't this builtin or does it use https://github.com/GoogleChromeLabs/picture-in-picture-chrome-extension |
This icon comes from Chrome and has nothing with this extension. |
I know... I'm just wondering if the chrome built in one is an extension thats internal or its built to the browser.
I'm also well aware this is an extension... |
It is built into the browser. See https://source.chromium.org/chromium/chromium/src/+/main:components/global_media_controls/ for details. It doesn't use any extension mechanism as far as I can tell. This extension was created when Global Media Controls (the UI you've mentioned above) was not created there. I still use this extension because of the global keyboard shortcut for what it's worth. |
@shanewazabbas #78 Is a V3 migration |
Tried to see why
Array.from(document.querySelectorAll('video'))
was returning videos for this extension, so I made some changes to make it work in manifest v3 and the query selector no longer finds videos in certain websites. Those in iframes to be specific. Which is odd since the setting:allFrames
is true. I was using this extension as a reference for my own where I need to find the playing video in any site, but ran into this one issue.Not really sure this can be fixed, but wanted to post it just for visibility. Now the real question is: was the chrome built in pip extension an actual chrome extension (and does it use v3?) or was it developed directly in the browser source code.
The text was updated successfully, but these errors were encountered: