Bug 134627 - SVG webfont can be clipped when using translate3D
Summary: SVG webfont can be clipped when using translate3D
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Text (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-04 02:53 PDT by Antoine Pultier
Modified: 2022-06-30 13:45 PDT (History)
6 users (show)

See Also:


Attachments
Screenshot on iOS 7.1.2 (81.52 KB, image/png)
2014-07-04 02:53 PDT, Antoine Pultier
no flags Details
JsFIDDLE reproducing the bug (26 bytes, text/plain)
2014-07-04 02:54 PDT, Antoine Pultier
no flags Details
Safari 15.5 behaves like Chrome but differ slightly from Firefox (709.03 KB, image/png)
2022-06-30 13:41 PDT, Ahmad Saleem
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Pultier 2014-07-04 02:53:43 PDT
Created attachment 234395 [details]
Screenshot on iOS 7.1.2

I tested it with Chrome, iOS 7.1.2 and Chrome Canary (I don't have a recent mac).
Comment 1 Antoine Pultier 2014-07-04 02:54:28 PDT
Created attachment 234396 [details]
JsFIDDLE reproducing the bug
Comment 2 Antoine Pultier 2014-07-04 04:30:24 PDT
As additional information, I have also the issue if I have an opacity CSS3 animation on an element below the icon. But it's harder to reproduce the bug outside my application.
Comment 3 Ahmad Saleem 2022-06-30 13:41:47 PDT
Created attachment 460588 [details]
Safari 15.5 behaves like Chrome but differ slightly from Firefox

I tweaked the JSFiddle by removing -webkit- prefix and changing translate3D with translate3d into this:

Link - https://jsfiddle.net/ugmxarfL/show

I am not able to reproduce it on Safari 15.5 on macOS 12.4 and also on iOS 15.5 on iPhone 13 Pro Max. As per screenshot, it is matching with Chrome but Firefox has slight deviation and moving the text upward.

There is no clipping like as attached in the screenshot of iOS behavior.

I think it was fixed along the ways and can be marked as "RESOLVED CONFIGURATION CHANGED" unless if I am testing it incorrectly, in latter case, please retest accordingly. Thanks!