Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Đã lưu trữ

Subtitles and rewind/fast-forward not following Picture-in-Picture mode for Disney+

amyemonsen

I've been having an issue with picture-in-picture (PiP) mode where the subtitles and rewind/fast-forward buttons (rr/ff) won't follow the video into the small player for Disney+ specifically. I have no issues with YouTube or any other site. The subtitles and rr/ff just stay with the original video player on the site while the video is in PiP mode. I can see the subtitle button on the PiP player, but it is grayed out and I can't click it. I've updated both Firefox and my computer (Windows 11) and reinstalled Firefox, cleared cookies and cache, and still no dice. Any advice? Thanks!

(In the screenshot, the PiP player isn't showing video, but I think that's just because of Disney's anti-piracy software - I can see the video in the PiP player on my screen.)

I've been having an issue with picture-in-picture (PiP) mode where the subtitles and rewind/fast-forward buttons (rr/ff) won't follow the video into the small player for Disney+ specifically. I have no issues with YouTube or any other site. The subtitles and rr/ff just stay with the original video player on the site while the video is in PiP mode. I can see the subtitle button on the PiP player, but it is grayed out and I can't click it. I've updated both Firefox and my computer (Windows 11) and reinstalled Firefox, cleared cookies and cache, and still no dice. Any advice? Thanks! (In the screenshot, the PiP player isn't showing video, but I think that's just because of Disney's anti-piracy software - I can see the video in the PiP player on my screen.)
Đính kèm ảnh chụp màn hình

Tất cả các câu trả lời (2)

Right, there's open bug for this, unfortunately without assigned developer.

https://bugzilla.mozilla.org/show_bug.cgi?id=1829812

It will be fixed in version 139, see https://bugzilla.mozilla.org/show_bug.cgi?id=1958974