Tino631 Floating Video

No. It supports HTML5 videos with controls, standard WordPress MediaElement video containers, supported YouTube embed iframes with the JavaScript API enabled, and Vimeo video iframes. Other providers, advertising players, shadow-DOM players, and heavily customized player wrappers need separate compatibility work. Background videos without controls are excluded.

In the block editor's Advanced panel, add tino631fv-ignore to Additional CSS class(es) on the video or containing block. Custom markup can use data-tino631fv="off" on the video or an ancestor.

It must be playing and completely above the viewport. Mobile support and external integrations must be enabled separately. Fullscreen or native picture-in-picture suspends floating. Layouts with transformed, filtered, or paint-containing ancestors stay inline because moving an iframe out of that layout can restart playback. Videos in custom overflow-scrolling containers are not supported.

Docking changes the existing element's CSS without moving its DOM node or changing its source. Provider behavior, browser restrictions, and other plugins can still affect playback. If an API is blocked, the embed remains inline.

WordPress content and block-widget embeds are prepared automatically when integration is enabled. Custom or dynamically inserted YouTube iframes must already contain enablejsapi=1 and an appropriate origin parameter. Tino631 Floating Video never modifies the source of a live iframe to add API support.

Pause returns the video to its original page position. Close also disables floating for that particular video until the next page load. Back to video scrolls to the original player and leaves playback running. No dismissal cookies are stored.

Each site has its own settings. Deleting the plugin removes its saved settings across the network. Deactivation preserves settings.