Amazon music shows outdated Chrome message even with shields down

[srirambv]

Description

Amazon music shows outdated Chrome message even with shields down

Steps to Reproduce

1. Visit https://music.amazon.co.uk/ in Brave (any channel)
2. Disable/Enable shields, shows Chrome outdated error
3. Open dev tools, console logs error even when shields is disabled

Actual result:

on Chrome

Expected result:

Same behaviour as Chrome

Reproduces how often:

Easy

Brave version (brave://version info)

Happens on all release/beta/dev channel builds

Reproducible on current release:

• Does it reproduce on brave-browser dev/beta builds?
  Yes

Website problems only:

• Does the issue resolve itself when disabling Brave Shields?
• Is the issue reproducible on the latest version of Chrome?

Additional Information

Issue reported on community
https://community.brave.com/t/not-working-on-amazon-music-website-brave-v-0-59-34-chromium-72-0-3626-81/44666/1

[mrzealot]

As per Slack, this is related to the Widevine component that the site detects as missing. Probably not much we can do, apart from making our native warning more obvious, as discussed in #1940.

[bbondy]

We already landed the new UX for making Widevine more obvious, so I'm closing this.

[jonathansampson]

Looks like this is still an issue, and unlikely related to Widevine.

Doesn't appear to work with shields down.

[kjozwiak]

Reproduced the issue on macOS 10.14.5 x64 using the following build:

Brave	0.66.101 Chromium: 75.0.3770.142 (Official Build) (64-bit)
Revision	8d93477bd18154c67a70a67019cb8032382c55dd-refs/branch-heads/3770@{#1160}
OS	Mac OS X

When you initially visit https://music.amazon.com, you receive the Widevine modal as expected:

However, once you start attempting to play some music, you'll receive the following as @srirambv & @jonathansampson pointed out above:

[kjozwiak]

Looks like this has been fixed on dev & nightly:

• 0.70.3 Chromium: 76.0.3809.62 (Official Build) nightly - Couldn't reproduce (Working)
• 0.69.91 Chromium: 76.0.3809.62 (Official Build) dev - Couldn't reproduce (Working)
• 0.67.115 Chromium: 76.0.3809.62 (Official Build) beta - Issue reproduced (doesn't work)

@btlechowski @GeetaSarvadnya mind checking to see if you're getting the same results on Windows & Linux?

[GeetaSarvadnya]

@kjozwiak Issue is Reproducible on Windows 10 x64 - 0.67.117

After playing any music, I am seeing the below popup message.

[kjozwiak]

@GeetaSarvadnya does it work on 0.70.x and 0.69.x for you as well?

[GeetaSarvadnya]

@kjozwiak Yup. It's working for me on dev and nightly on versions below:

Dev channel 0.68.106 Chromium: 76.0.3809.62 (Official Build) dev (64-bit)
Dev channel 0.69.92 Chromium: 76.0.3809.62 (Official Build) dev (64-bit)
Nightly channel 0.70.3 Chromium: 76.0.3809.62 (Official Build) nightly (64-bit)

[kjozwiak]

As per the above, seems like this has been fixed and is working as expected. Assuming this has been fixed via #4793. Also verified it's working with 0.68.131 Chromium: 76.0.3809.100.

@srirambv mind taking a look as well as you originally reported the issue? Thanks!

[kjozwiak]

Verification PASSED on macOS 10.14.6 x64 using the following build:

Brave	0.68.131 Chromium: 76.0.3809.100 (Official Build) (64-bit)
Revision	ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS	Mac OS X

• Verified test cases outlined under Amazon music shows outdated Chrome message even with shields down #3308 (comment).

Verification passed on

Brave	0.68.131 Chromium: 76.0.3809.100 (Official Build) (64-bit)
Revision	ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS	Ubuntu 18.04 LTS

Verified test plan from the description.

Verification passed on

Brave	0.68.131 Chromium: 76.0.3809.100 (Official Build) (64-bit)
Revision	ed9d447d30203dc5069e540f05079e493fc1c132-refs/branch-heads/3809@{#990}
OS	Windows 10 OS Version 1803 (Build 17134.523)

• Verified test plan from the description.

[rsc3]

I'm getting a similar issue on Fedora38 in 2023. Accepted the wildvine install popup.

[rsc3]

Ah now I see that wildvine didn't actually install. Same issue with Firefox :(