I think you might actually be on the right track with this... I'm running Xubuntu 18.04.1 64-Bit for these tests. The browsers I have installed are Firefox Quantum 62.0 and Chromium 68.0.3440.106....
I think you might actually be on the right track with this...
I'm running Xubuntu 18.04.1 64-Bit for these tests. The browsers I have installed are Firefox Quantum 62.0 and Chromium 68.0.3440.106. As others have said, in Firefox I do not see the scrollbar, however it is visible in Chromium.
Upon comparing the differences between the two, the <p> tags in the topic text on my system are rendered using DejaVu Sans in Firefox, and Noto Sans in Chromium. Upon changing the font in Chromium to DejaVu Sans via the web inspector, the scrollbar disappears. Why the two browsers choose to render using different fonts, I don't know, but this seems to be the issue.
I will try to look into this if I get a chance later and make a merge request if I'm able to fix it. As a quick fix, disabling the below CSS rule also seems to alleviate the issue.
p:last-child{margin-bottom:0;}
This obviously has side-effects, so maybe a custom rule to eliminate it would be better...
I think you might actually be on the right track with this...
I'm running Xubuntu 18.04.1 64-Bit for these tests. The browsers I have installed are
Firefox Quantum 62.0
andChromium 68.0.3440.106
. As others have said, in Firefox I do not see the scrollbar, however it is visible in Chromium.Upon comparing the differences between the two, the
<p>
tags in the topic text on my system are rendered usingDejaVu Sans
in Firefox, andNoto Sans
in Chromium. Upon changing the font in Chromium toDejaVu Sans
via the web inspector, the scrollbar disappears. Why the two browsers choose to render using different fonts, I don't know, but this seems to be the issue.I will try to look into this if I get a chance later and make a merge request if I'm able to fix it. As a quick fix, disabling the below CSS rule also seems to alleviate the issue.
This obviously has side-effects, so maybe a custom rule to eliminate it would be better...
But ideally we can find and fix the font issue instead.