I see nothing wrong.

In order to better assist you with your issue please provide us with a screenshot. If you need help to create a screenshot, please see How do I create a screenshot of my problem?

Once you've done this, attach the saved screenshot file to your forum post by clicking the Browse... button below the Post your reply box. This will help us to visualize the problem.

Thank you!

I see it now. The first picture is from v84.0.1 The second is from Firefox v54 (my primary).

Zoom has no effect.

I created a stripped down example of what they are doing:

https://jsfiddle.net/es4fox1g/

Not sure why the text doesn't overlap the floated border line in Firefox.

You could submit a web (in)compatibility report on the following site:

https://webcompat.com/

Safe mode has no effect.

Seems Firefox is reluctant to move the text into space creating by using margins to move the floated content down:

https://jsfiddle.net/4extu9qy/

This could be caused by optimizing layout calculations so they don't run more often than needed. Sometimes the extra run is needed.

That is a weird problem that only seems to happen in Firefox 68.

This seems to be about a float:left rule for the "H4::before" selector that seems to be applied to the H4 container. When I open the Inspector then it is instantly corrected.

This code in userContent.css fixes it for me.

• http://kb.mozillazine.org/userContent.css

@-moz-document domain(www.imdb.com){
.dataHeaderWithBorder::before {
    content: "";
    border-bottom: 1px dotted #CCC;
    width: 100%;
    float: none !important;
}

jscher2000 said

I created a stripped down example of what they are doing: https://jsfiddle.net/es4fox1g/ Not sure why the text doesn't overlap the floated border line in Firefox. You could submit a web (in)compatibility report on the following site: https://webcompat.com/

I've done that: https://webcompat.com/issues/37344 thanks

I only see this happen with Firefox 68. Firefox 67 and 69 work properly, so it looks that this is a regression in 68 that has been fixed, but that hasn't been back ported.