RESOLVED CONFIGURATION CHANGED21327
@font-face: <length>'s specified in 'ex' units are ignored 
https://bugs.webkit.org/show_bug.cgi?id=21327
Summary @font-face: <length>'s specified in 'ex' units are ignored
Philippe Wittenbergh
Reported 2008-10-02 23:13:30 PDT
... and defaults to the initial values. For a block that uses a font loaded through @font-face, properties whose length values are specified in 'ex' are reset to their initial values. Properties affected (or tested so far…): padding, margin, line-height, border, -webkit-border-radius, webkit-box-shadow, text-shadow, width/height (does strange things, sometimes the width is '0'), letter-spacing, word-spacing. test case (requires Ahem installed): http://dev.l-c-n.com/css3/font-face/ex-ahem_a.html In the linked test case, within each grey block: the first red line uses @font-face, the second line uses the installed copy of Ahem. Both red lines should be identical. Note, the most recent Minefield nightly builds (Gecko .9.1b1pre) with @font-face enabled, appear to use the font-metrics of the fall back font.
Attachments
zipped copy of the testcase (10.68 KB, application/octet-stream)
2008-10-02 23:14 PDT, Philippe Wittenbergh 		no flags
Details
screen shot of test case (37.18 KB, image/png)
2008-10-02 23:14 PDT, Philippe Wittenbergh 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Philippe Wittenbergh
Comment 1 2008-10-02 23:14:13 PDT
Created attachment 24039 [details] zipped copy of the testcase
Philippe Wittenbergh
Comment 2 2008-10-02 23:14:56 PDT
Created attachment 24040 [details] screen shot of test case
Philippe Wittenbergh
Comment 3 2008-12-08 17:04:08 PST
Gecko has now fixed their implementation completely. Using 'ex' for <length> now works correctly in that rendering engine. https://bugzilla.mozilla.org/show_bug.cgi?id=458878
Ahmad Saleem
Comment 4 2022-12-30 13:18:32 PST
Took test case from the Mozilla bug from Comment 04 and used 'ahem.js' to change it into following JSFiddle: Link - https://jsfiddle.net/hv4xLpmj/show I am not able to see the issue in Safari Technology Preview 160 compared to reference screenshot and it is matching Chrome Canary 111 and Firefox Nightly 110. Marking tis as "RESOLVED CONFIGURATION CHANGED". Please reopen, if it is not fixed. Thanks!
Note You need to log in before you can comment on or make changes to this bug.