-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Multiple users reporting that HBO Max is broken, likely due to kVideoPlaybackQuality being disabled #13183
Comments
I can confirm, hbomax isn't working in Release, Beta or Nightly. |
Here is a Tampermonkey script to re-add the missing function on HBO Max plays fine with it enabled. It's pretty hacky because the page is constructed dynamically so I had to use the It seems like the complete removal of a feature now supported by all browsers is likely to cause websites to break. Fingerprinting can be prevented by returning dummy values instead. In this particular case I would expect the number of dropped frames to be a way to track certain users. Brave could return 0 in all cases here, but of course that's a more involved change than just removing the feature entirely. I hope Brave developers will consider replacing functions that could lead to fingerprinting with versions that return constant values, or random ones whenever appropriate. This would seem like a better way to do this than their blunt removal. Then again I'm not a browser developer, but hey. Please just think about it. |
cc: @pes10k |
@fmarier can you say more about why this was removed? |
We should re-enable. It sounds like a potential fingerprinting vector, but if it leads to breakage, we should figure out a better way to mess with the fingerprint. |
I agree we should re-enable, but I'm curious about the fingerprinting vector. Whats the threat / concern here? |
Fixes brave/brave-browser#13183 Manual revert of #4479
Created brave/brave-core#7437 to re-enable. @pes10k I'll create a privacy review |
The feature can be re-enabled from the command line ( |
Thanks for sharing @mkarolin 😄 @ryanbr will give that a go soon and verify if that fixes. If so, we can accept brave/brave-core#7437 |
Just tested HBO Max with |
Fixes brave/brave-browser#13183 Manual revert of #4479
Fixes brave/brave-browser#13183 Manual revert of #4479
How do you do this? |
@macp92 This Brave support article explains how to run Brave with custom command-line parameters. |
for mac folks you can enable this flag with:
|
Confirmed 1.18.77rc works with HBO Max, tested before (1.18.75) and after (1.18.77). Playback now works |
Thanks @ryanbr 👍 Labeling this as passed as per #13183 (comment). Unfortunately QA doesn't have an HBO account but the above was checked on @LaurenWags @rebron we don't need to check |
Checked on MacOS also, Playback of the new release now works |
This issue has popped back up in 1.19.86. |
Description
HBO Max no longer plays video. Several users are reporting hitting this issue on Reddit as well as on Brave forums.
Steps to Reproduce
Actual result:
The video never starts playing.
Expected result:
Entertaining content.
Reproduces how often:
Always.
Brave version (brave://version info)
Reproduced on Version 1.19.54 Chromium: 87.0.4280.101 (Official Build) beta (64-bit)
Version/Channel Information:
I've only tried the beta channel but I suspect this reproduces everywhere.
Other Additional Information:
Miscellaneous Information:
#8029 seems to show that
getVideoPlaybackQuality
was removed from Brave back in February as a follow-up to Chromium 80 being released. From what I am reading of the stack traced logged on the HBO Max page, it seems like their web app may have started using this API without checking if it's available. If this is indeed the issue it probably also means that users of Chrome < 80 who haven't upgraded since February would also be seeing this issue.The removal in Brave was hardcoded so there is no easy way for me to try turning this feature back on.
/cc @fmarier and @mkarolin who created or are mentioned on the original Brave issue.
The text was updated successfully, but these errors were encountered: