WordPress.tv video is overlapping content

[karmatosed]

This only seems on the archive pages perhaps:

Seen in Chrome on ​https://wordpress.tv/event/wordcamp-europe-2018/. Props to @melchoyce for discovering this.

[Otto42]

Not happening in Windows 10 Chrome Version 70.0.3528.4 (Official Build) dev (64-bit).

[tellyworth]

Looks fine to me in Chrome 68.0.3440.106 and Safari 11.1.2, both on Macos 10.13.6.

[netweb]

Also not seeing this with Chrome Version 70.0.3528.4 (Official Build) dev (64-bit) on Mac

[ryelle]

It looks like this is only an issue for Automatticians. I can reproduce it when logged in to WP.com + proxied, but it's fine when not logged in, or not proxied. The iframe code itself is different (width & src domain), and incorrectly wider when logged in.

Not logged in, looks correct (Chrome/Mac):

<iframe width="575" height="323.1404958677686" src="https://videopress.com/embed/qjOKaoL2?hd=1&amp;autoPlay=0&amp;permalink=0&amp;loop=0" frameborder="0" allowfullscreen=""></iframe>

Logged in, broken (Chrome/Mac):

<iframe width="605" height="340" src="https://video.wordpress.com/embed/qjOKaoL2?hd=1&amp;autoPlay=0&amp;permalink=0&amp;loop=0" frameborder="0" allowfullscreen=""></iframe>

I'm not sure if this is a problem with the way the theme embeds videos, or if the issue is with videopress, though.

[dd32]

In 7698:

WordPress.TV: Define the actual width of the non-single videos as 575px.

This fixes the VideoPress player width for Automatticians whose VideoPress player differs slightly from the public player.

Fixes #3779.

[dd32]

Just noting that although I've closed this, it won't be live on WordPress.TV until I sync the open-sourced theme changes to the production copy used by WordPress.TV.

[dd32]

I should also add that this could be taken as a bug in either the theme, or the a8c VideoPress player, or both.

I wasn't able to determine what would be needed in VideoPress to fix it, the public JS has some code to restrict it to the width of the parent element, where as the a8c player appears to skip that code for an unknown reason - Perhaps due to the different domain name as mentioned in comment 4..