Homepage has invisible parts

[Usmanzahidcode]

The Symfony homepage (https://symfony.com/) appears to have a display issue in the Symfony Cloud section. Please see the attached screenshot for reference:

[javiereguiluz]

I can't reproduce this. Which browser do you use? Have you tried browsing it in "incognito mode" to disable most browser extensions in case some extension is blocking this content?

[Link1515]

I have the same problem, and I'm using Microsoft Edge (version 136.0.3240.76) in incognito mode.

[Usmanzahidcode]

I had Chrome latest, on Windows. But the error seems to be gone on the Chrome on Ubuntu.

[javiereguiluz]

Folks, does this issue only happen in Windows then?

That's a problem because I don't have a Windows machine to test this. Could anyone please try to debug this or give me a clue I can follow? Thanks!

[jennevdmeer]

It's the asciinema-player element thingy that has a massive size, it should not stretch that far to the left.

[Stirreg]

Can confirm: (Microsoft Edge Version 136.0.3240.92 (Official build) (64-bit))

Looks like it is missing a width for the negative right position on .symfony-cloud-player #prompt, I suggest something along the lines of either replacing right: -10px; with left: 50% or keep positions as is and adding width: 50% or so to it.

[wotta]

Also happens on Apple M3 Pro.
macOS: 14.3 (23D56)
Browser: Brave Version 1.78.102 Chromium: 136.0.7103.113 (Official Build) (arm64)

[Link1515]

I found the problem — it’s caused by the font. If I remove the 'Fira Code' font from the .ap-terminal element, the style returns to normal.

asciinema-player uses the ch unit to render the terminal width. If we use the font file /assets/fonts/FiraCode/FiraCode-Regular-Latin-727edd72be005fe5b70c460e2a09dd00.woff2, which is downloaded on the homepage, the terminal becomes excessively wide.

I also noticed that the font downloaded on the homepage has a "Latin" suffix. When I tried using a different Fira Code font from the official GitHub release (v6.2) locally, asciinema-player worked fine. So I suspect it might be a language or character set issue.

[javiereguiluz]

Thanks a lot to all the folks who helped debug this. We just deployed some changes and this should be fixed now.

[Usmanzahidcode]

It's fixed and working.