1903555 - Floating player option is missing from videos on tiktok.com

Status: ASSIGNED

(Web Compatibility :: Site Reports, defect, P2)

Description

[Calin Tanase]

Attachment: Floating player FF vs Chrome.mp4

Environment:
Operating system: Windows 10
Firefox version: Nightly 129.0a1 (2024-06-18)

Steps to reproduce:

1. Go to https://www.tiktok.com/@argenby/video/7377415282358324481
2. Observe the media player.

Expected Behavior:
The media player has the "Floating Player" option.

Actual Behavior:
The media player is missing the "Floating Player" option.

Notes:

1. Screen rec attached
2. Reproducible regardless of the ETP status
3. Reproducible on Firefox Release as well
4. Not reproducible on Chrome
5. Issue found during WebCompat team [Top100] websites testing

Comment 1

[James Graham [:jgraham]]

Note that our PiP mode doesn't work here because the videos are short.

Comment 2

[Thomas Wisniewski [:twisniewski]]

Niklas, Katherin, could we just make an exception in our PiP implementation to ~always show PiP on all videos on TikTok URLs, even if they're short? That seems to be reasonable in their case (and possibly also YouTube Shorts, since I think those are relatively easy to detect as well?)

Comment 3

[Vincent Hilla [:vhilla]]

Testing this with a build from central, the "Floating Player" is still missing. TikTok only enables it for Chrome user agents:

isDocumentPipSupporting:"undefined"!=typeof window&&"documentPictureInPicture"in window&&(i=(r=navigator.userAgent.match(/Chrom(?:e|ium)\/([0-9]+)\./))?Number(r[1]):-1)>=126&&133!==i

Comment 4

[Calin Tanase]

Still an issue with the latest Nightly.

Comment 5

[Raul Bucata]

The option is now located in the meatball menu, top right corner( 3 dots, horizontal). Clicking on it does not show the option in Firefox.

Comment 6

[Jeff Muizelaar [:jrmuizel]]

The platform bug has been fixed and this works with Chrome mask. Ideally TikTok would just drop the UA sniffing.

Comment 8

[AutoWebCompat]

Attachment: Reproduction script generated by autowebcompat bot

On tiktok.com video pages, the player's meatball (three-dots) menu offers no "Floating Player" entry in Firefox, so document Picture-in-Picture is unreachable; the menu instead shows Speed, Quality, Captions, Not interested and Report. Chrome's menu at the same spot lists "Floating Player" alongside the other entries. Firefox exposes window.documentPictureInPicture, so the capability is present but the option is never offered.

Comment 9

[Bernadett Farkas]

Attachment: Picture-in-picture when right-clicking the video - Nightly vs Chrome

This issue is still reproducible on the latest Nightly 158.0a1 (2026-09-13).

• When selecting the hamburger menu, the Picture-in-Picture(Floating) mode is not displayed.
• Right-clicking the video displays the Picture-in-Picture option, but the feature does not work.

Comment 10

[Bernadett Farkas]

Attachment: Picture-in-picture when right-clicking the video - Nightly vs Chrome

Comment 11

[Jim Mathies [:jimm]]

See comment 3.

Comment 12

[Raul Bucata]

The issue is still reproducible.

Tested with:

Browser / Version: Firefox Nightly 161.0a1 (2026-10-22) (64-bit)
Operating System: Windows 10 PRO x64

Comment 13

[Thomas Wisniewski [:twisniewski]]

We don't want to ship a simple UA override here, but we might be able to target this specific check using a JS intervention similar to how our FastClick intervention works: https://searchfox.org/firefox-main/source/browser/extensions/webcompat/injections/js/disable_FastClick.js

Comment 14

[Hackbot [:hackbot]]

Attachment: Bug 1903555 - Add webcompat intervention for tiktok.com; r?ksenia

TikTok only offers its document Picture-in-Picture "Floating Player" when isDocumentPipSupporting is true, which requires documentPictureInPicture plus a Chrome/Edge/Opera browser-name sniff and navigator.userAgent.match(/Chrom(?:e|ium)\/([0-9]+)\./) >= 126.

As requested in comment 13, this does not ship a UA override. Instead, a bug-specific script (in the same style as disable_FastClick.js) makes navigator.userAgent return a Chrome UA only when it is read from the L.isDocumentPipSupporting function (SpiderMonkey's inferred function name in the stack), and for the single synchronous read right after it (the version match, which sits outside that function). The extra read is cleared in a microtask. Everywhere else, the UA and the HTTP header are unchanged. The script only runs when documentPictureInPicture is supported, on www.tiktok.com, on desktop.

Comment 15

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/66b804079c62
https://hg.mozilla.org/integration/autoland/rev/4c687dd29e22
Add webcompat intervention for tiktok.com; r=ksenia,webcompat-reviewers

Comment 16

[pstanciu]

https://hg.mozilla.org/mozilla-central/rev/4c687dd29e22