Description of the issue:
Going to Cast Screen and casting to Chromecast will initially work but drops the connection within minutes.
Able to be reproduced on any browser using Chromium 1.37.xx or later. Was working on Edge while it was on 1.36.xx but it started having the same issue after updating
How can this issue be reproduced?
- Cast Screen
- See it appear on Chromecast
- Within a couple minutes, it no longer will cast.
Expected result:
Content will continue casting until I choose to disconnect or exit the browser.
Brave Version( check About Brave
):
1.79.118 Chromium: 137.0.7151.61 (Official Build) (64-bit)
Additional Information:
Have open Chromium issue at https://issues.chromium.org/issues/421273247
cc: @Mattches
1 Like
I thought I was going mad, or that this was due to the solar storm going on. Thanks for posting. For me, it’s disconnecting about every 20 seconds, but when using “Cast Tab”, rather than “Cast Screen”, there’s no issue, so it seems confined only to Cast Screen. Please fix this, Brave team. I use Cast Screen on YouTube to avoid ads with Brave, so this is pretty aggravating.
@NotABot123 if you could do a favor and reply to that chromium issue that I linked to as well, that is where it’s most likely gonna have to be fixed since it’s an upstream issue. The more noise that can be given that direction means it might get fixed a little sooner
1 Like
Ok, I’ve posted the same message I posted here on the Chromium forum. Let’s hope it gets tended to soon.
1 Like
Just was looking and it has a linked issue that I missed. So they are working on it at https://issues.chromium.org/issues/420678579
@NotABot123 one thing I found interesting was a note in that, which was:
If a user is casting audio/video, the screen casting will continue as expected.
I just tested and that seems to be true. I just had cast YouTube up and was watching with no issues. But if I paused it then it would disconnect as we were seeing. So it might be available at least for content.
1 Like
It looks like they’re on the case, indeed. 
Seems fixed with the update for today, June 11th.
1 Like