Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Bug in rendering CSS ::first-line ?

more options

Firefox produces erroneous output in connection with ::first-line if individual words in a Hebrew character set are used in the same html-doc (at any position).

In order not to have to describe it in a lengthy way, I have included an html example in which the different results can be easily generated and observed.

The essential effect: In certain situations Firefox doubles the space needed for a character when rendering the output. This causes the following text to be shifted to the right and possibly even beyond the boundary of a div box.

Am I doing something wrong? In other browsers it works perfectly!

Example for testing : example test-first-line.html

Please use the source code to modify and test.

Best regards Reiner

Firefox produces erroneous output in connection with ::first-line if individual words in a Hebrew character set are used in the same html-doc (at any position). In order not to have to describe it in a lengthy way, I have included an html example in which the different results can be easily generated and observed. The essential effect: In certain situations Firefox doubles the space needed for a character when rendering the output. This causes the following text to be shifted to the right and possibly even beyond the boundary of a div box. Am I doing something wrong? In other browsers it works perfectly! Example for testing : [https://www.stilkunst.de/videotemp/test-first-line.html example] test-first-line.html Please use the source code to modify and test. Best regards Reiner

Modified by Reiner Makohl

All Replies (2)

more options

Looks like sth is wrong indeed.

Can you file a bug on a https://bugzilla.mozilla.org/enter_bug.cgi ? Thanks.

more options

Thank you for confirming this problem.

I have now reported this as a bug and hope that a solution can be offered soon.

In my web site many hundreds of pages are affected by this and I would like to finally get rid of the previous, quite bad bypass.

Thanks!