-
Notifications
You must be signed in to change notification settings - Fork 7
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
Let's get rid of Flash [Due: 09/2018] #33
Comments
Oh, that's a bummer. I've expected more from Amazon. Could you check whether Flash is also required in the genuine Chrome and then ask Amazon Cloud Player support whether there are any plans to get rid of Flash? You can say that Chrome makes more and more difficult to use Flash and there is a roadmap for its removal. Meantime, we could switch to Chromium, where Flash is more stable. Could you test following requirements under Wayland? The first line is a comment linking this issue for me not to forget Flash is still required.
|
I get the same message in Chrome. I will send them a message. |
I wrote an email to Amazon support. I got a standard reply ignoring my questions and telling me to clear my cookies or use a different browser. Trying again, worded for idiots. |
Still no luck. They keep telling me to call them. I don't fancy my chances of getting any operator that has a clue. |
The Amazon support seems to be unbelievably incompetent :-( |
Let's check the progress every 4 months - next check September 2018. |
I believe this issue is now resolved too! :-D |
Sure :-) |
Released with Nuvola 4.16.0, more info: Nuvola 4.16 Brings Libre.FM Scrobbling, Ivoox Service, and more |
Since this script is compatible with the Chromium backend, we could proceed further: Replace
"requirements": "Codec[MP3] Feature[Flash]"
with"requirements": "Codec[MP3] Feature[MSE] Chromium[63]"
. For this, we need to check:Feature[Flash]
removed). I guess this will be okay presuming that Amazon detected functional MSE and didn't bother to use Flash plugin at all during your tests of the Chromium backend.The text was updated successfully, but these errors were encountered: