Bug 241781

Summary: Google slides presentation does not render well in Safari (misplaced SVG arrows)
Product: WebKit Reporter: youenn fablet <youennf>
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: ahmad.saleem792, bfulgham, jib, sabouhallawa, simon.fraser, webkit-bug-importer, zalan, zimmermann
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
URL: https://docs.google.com/presentation/d/1-SgzfMAeVG3u5vErJncC7OKDTGNDzSOMg_78LP8SULk/edit#slide=id.g133845ed595_0_2
Attachments:
Description Flags
Chrome screenshot
none
Safari screenshot none

youenn fablet
Reported 2022-06-20 06:09:21 PDT
But it does render well in Chrome and Firefox. I am not sure why.
Attachments
Chrome screenshot (209.36 KB, image/png)
2022-06-20 06:11 PDT, youenn fablet
no flags
Safari screenshot (197.42 KB, image/png)
2022-06-20 06:11 PDT, youenn fablet
no flags
Radar WebKit Bug Importer
Comment 1 2022-06-20 06:09:41 PDT
youenn fablet
Comment 2 2022-06-20 06:10:36 PDT
This does not render well on STP either on Monterey.
youenn fablet
Comment 3 2022-06-20 06:11:25 PDT
Created attachment 460354 [details] Chrome screenshot
youenn fablet
Comment 4 2022-06-20 06:11:41 PDT
Created attachment 460355 [details] Safari screenshot
Simon Fraser (smfr)
Comment 5 2022-06-20 11:14:46 PDT
It looks like the arrows are rendered in the wrong place.
youenn fablet
Comment 6 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.
jib
Comment 7 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.
Ahmad Saleem
Comment 8 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!
Note You need to log in before you can comment on or make changes to this bug.