|
|
image.png (12,567 bytes) |
|
|
image-2.png (42,277 bytes) |
|
|
1) Fixed in 3032 2) Testing https://cef-builds.spotifycdn.com/index.html -- the newest version 126 => https://cef-builds.spotifycdn.com/cef_binary_126.2.4%2Bg5e718e0%2Bchromium-126.0.6478.62_windows64_client.tar.bz2 => works to sign-in to YouTube music -- versions 120, 123, 124, 125 => fails to sign in (same as MM5 that is currently running version 123) So it is because we are not running the newest chromium version and can be resolved by updating to Chromium 126 |
|
|
Setting as resolved, even though 2) isn't. It doesn't seem possible to always use the latest Chromium. We certainly can try to keep releasing it, but we also depend on the cef project pace. |
|
|
Verified it works now on 3032, however the Title isn't grabbed correctly. image-5.png (11,425 bytes) image-6.png (2,028 bytes) |
|
|
Yes, because when adding the bookmark and there is the cookies acceptation dialog with title element including "Before you continue..." so therefore the 'music.youtube.com' is suggested as title instead.. User can define it's own.. image-7.png (10,427 bytes) |
|
|
You still can't login to YouTube Music. image-8.png (46,646 bytes) |
|
|
Yes, see 0021031:0076067 , we would always need to use the latest Chromim version, currently we are on 123 and 126 is working.. i.e. as Jiri wrote it doesn't seem possible to always use the latest Chromium. We certainly can try to keep releasing it, but we also depend on the cef project pace. |
|
|
As I wrote in Forum 3034 it works for me no prompts and YTM works normally https://www.mediamonkey.com/forum/viewtopic.php?p=520170#p520170 |
|
|
@Peke: The issue is that Sign-in works only with the newest Chromium |
|
|
But I am signed on YTM in MM 3034 EDIT: I can't log back once I signed out. |
|
|
Re-resolving. As indicated at 0021031:0076068 this issue can only be solved by always updating to the current version of chromium which MM tries to do, but it's not always practical to be on the latest version (e.g. at this point in the release of 5.1 it would be impractical to update chromium). |
|
|
Related to 0020897 which will also be resolved after upgrading to 127 |
- Anonymous
