Bug 241781 - Google slides presentation does not render well in Safari (misplaced SVG arrows)
Summary: Google slides presentation does not render well in Safari (misplaced SVG arrows)
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: https://docs.google.com/presentation/...
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-06-20 06:09 PDT by youenn fablet
Modified: 2023-02-22 11:18 PST (History)
8 users (show)

See Also:

Attachments
Chrome screenshot (209.36 KB, image/png)
2022-06-20 06:11 PDT, youenn fablet 		no flags Details
Safari screenshot (197.42 KB, image/png)
2022-06-20 06:11 PDT, youenn fablet 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2022-06-20 06:09:21 PDT 
But it does render well in Chrome and Firefox.
I am not sure why.
Comment 1 Radar WebKit Bug Importer 2022-06-20 06:09:41 PDT 
<rdar://problem/95533642>
Comment 2 youenn fablet 2022-06-20 06:10:36 PDT 
This does not render well on STP either on Monterey.
Comment 3 youenn fablet 2022-06-20 06:11:25 PDT 
Created attachment 460354 [details]
Chrome screenshot
Comment 4 youenn fablet 2022-06-20 06:11:41 PDT 
Created attachment 460355 [details]
Safari screenshot
Comment 5 Simon Fraser (smfr) 2022-06-20 11:14:46 PDT 
It looks like the arrows are rendered in the wrong place.
Comment 6 youenn fablet 2022-06-20 11:23:55 PDT 
There is another issue on the same prez, a few slides before. Not sure this is svg in that slide.
Comment 7 jib 2022-06-21 10:23:08 PDT 
It looks to me like the arrows are rendered in the right place, but that text got pushed down because the first line got wordwrapped in Safari but not Chrome.
Comment 8 Ahmad Saleem 2023-02-22 11:18:23 PST 
I am not sure whether it is fixed something on Google end because now I am now not able to reproduce this bug in Safari 16.3, STP161 and WebKit Trunk. I remember in the past, I was able to reproduce this.

Do we need to track this since it seems to be fixed now. Thanks!