New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
developers.google.com - design is broken #8499
Comments
Thanks @mkaply I can reproduce this in Firefox 56 for OSX. <div class="devsite-landing-row-item-youtube">
<iframe data-autohide="1" data-showinfo="0" allowfullscreen="" class="devsite-embedded-youtube-video" id="ytplayer0" data-enablejsapi="1" src="//www.youtube.com/embed/m-sCdS0sQO8?autohide=1&showinfo=0&enablejsapi=1" origin="https://developers.google.com" frameborder="0"></iframe>
</div> Looks like the padding bottom is cutting off the viewing area of the video. .devsite-landing-row-50 .devsite-landing-row-item-youtube {
padding-bottom: calc((100% - 40px)/2*.5625);
} |
This is another instance of that unfortunate intentional flexbox incompatibility (see bug 958714) where percentage paddings/margins are considered to not be interoperable by spec:
So we're stuck unless Google wants to fix their page to use a technique that's cross browser, or Firefox decides to adopt Chrome's behavior. I'll set this to needscontact in case Google can fix their page more quickly. |
Just adding this line will fix it. .devsite-landing-row-50 .devsite-landing-row-item-code, .devsite-landing-row-50 .devsite-landing-row-item-image, .devsite-landing-row-50 .devsite-landing-row-item-video, .devsite-landing-row-50 .devsite-landing-row-item-youtube {
width: calc((100% - 40px)/2);
height: 100%;
} |
sent an email today to Google. |
This is fixed now. |
URL: https://developers.google.com/web/progressive-web-apps/
Browser / Version: Firefox 56.0
Operating System: Mac OS X 10.12
Tested Another Browser: Yes
Problem type: Design is broken
Description: Video on the right side is very small vertically. Works on Chrome
Steps to Reproduce:
From webcompat.com with ❤️
The text was updated successfully, but these errors were encountered: