The problem here is that they've got a `max-height: fit-content` declaration applying to the div `<div class="text-content mdn-Col-lg-6">`, in view-source:https://configuraraparelhos.claro.com.br/assets/css/usecase.css Firefox doesn't currently honor `fit-content` for `max-height` -- that's bug 1672559. And in Chrome, if I untick that declaration (in a browser window that's wide enough to trigger this problem), then the same issue shows up there too. (In reply to Thomas Wisniewski [:twisniewski] from comment #5) > This doesn't seem to affect Android, so I'll make a desktop-only intervention. Indeed, that's because the site has media queries, and only their styles for the widest viewports seem to have this problem.
Bug 1999770 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The problem here is that they've got a `max-height: fit-content` declaration applying to the div `<div class="text-content mdn-Col-lg-6">`, in https://configuraraparelhos.claro.com.br/assets/css/usecase.css Firefox doesn't currently honor `fit-content` for `max-height` -- that's bug 1672559. And in Chrome, if I untick that declaration (in a browser window that's wide enough to trigger this problem), then the same issue shows up there too. (In reply to Thomas Wisniewski [:twisniewski] from comment #5) > This doesn't seem to affect Android, so I'll make a desktop-only intervention. Indeed, that's because the site has media queries, and only their styles for the widest viewports seem to have this problem.
The problem here is that they've got a `max-height: fit-content` declaration applying to the div `<div class="text-content mdn-Col-lg-6">`, in https://configuraraparelhos.claro.com.br/assets/css/usecase.css , and they're depending on the browser honoring that style, in order to achieve the proper layout. Firefox doesn't currently honor `fit-content` for `max-height` -- that's bug 1672559. And in Chrome, if I untick that declaration (in a browser window that's wide enough to trigger this problem), then the same issue shows up there too. (In reply to Thomas Wisniewski [:twisniewski] from comment #5) > This doesn't seem to affect Android, so I'll make a desktop-only intervention. Indeed, that's because the site has media queries, and only their styles for the widest viewports seem to have this problem.