xF2 Add-on s9e Media Sites 2.18.6

Added support for MLB.com's new URLs.

Added missing rule to limit dynamic embeds to 100% width.

This update introduces a new experimental feature: a floating miniplayer. A button has been added to YouTube videos as well as other video players. When clicked, the video is minimized and floats in the bottom-right corner of the page. It allows the user to keep an eye on the video while reading the rest of the page. Closing the miniplayer or clicking on the video's original location returns it to normal.


Some details:

• The miniplayer adds less than 1 KiB of JavaScript and less than 2 KiB of CSS. (unminified and uncompressed)
• The feature is meant for desktop browsers and thus is only active in wide layout.
• The button is intentionally placed outside the original player to avoid blocking its interface.
• Leaving the page terminates the playback normally.
• If you don't like the new feature, you can disable it in the add-on's options.

On a related topic, the add-on's CSS has been overhauled to better accomodate those changes and most of the inline CSS has been removed. Hopefully there shouldn't be any visual changes.

Added support for playlist URLs that don't specify the user's name.
Also, unused phrases have been removed.

Added TikTok. Removed old template modifications related to Instagram/Twitter resizing that are not needed anymore.

Click to expand...

Updated Gfycat, The Guardian and Tumblr

Replaced PHP callback with a standard XenForo template.​

This is a maintenance update.​

The new definition uses two different embed URLs as some documents can only be embedded with one or the other.

When visiting the last post of a thread, dynamically-sized embeds (such as tweets) from previous posts will expand upward even if they fully appear on the screen. It will keep the post the user is reading at the same position on the screen and prevent the useful content from moving around as the result of other elements loading.

A bug has been fixed that caused the lazy loader to incorrectly determine which way the page was being scrolled. It didn't really have any impact on the user experience and is only mentioned for completeness.

At this point I'm happy with the behaviour of the lazy loader and I don't have any more changes planned. The lazy loader is meant to be almost invisible so I may write a full description of the multiple ways it improves the user experience behind the scenes.