Amazon music shows outdated Chrome message even with shields down

on Chrome

Same behaviour as Chrome
Easy
Happens on all release/beta/dev channel builds
Does it reproduce on brave-browser dev/beta builds?
Yes
Does the issue resolve itself when disabling Brave Shields?
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
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 https://github.com/brave/brave-browser/issues/1940.
We already landed the new UX for making Widevine more obvious, so I'm closing this.
Looks like this is still an issue, and unlikely related to Widevine.

Doesn't appear to work with shields down.
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:

Looks like this has been fixed on dev & nightly:
@btlechowski @GeetaSarvadnya mind checking to see if you're getting the same results on Windows & Linux?
@kjozwiak Issue is Reproducible on Windows 10 x64 - 0.67.117
After playing any music, I am seeing the below popup message.

@GeetaSarvadnya does it work on 0.70.x and 0.69.x for you as well?
@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)
As per the above, seems like this has been fixed and is working as expected. Assuming this has been fixed via https://github.com/brave/brave-browser/issues/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!
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
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)
Most helpful comment
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 https://github.com/brave/brave-browser/issues/1940.