Bug 262786

Summary: Setting shape-rendering to crispEdges doesn't eliminate thin gaps between hexagon rows
Product: WebKit Reporter: quentin
Component: SVGAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: sabouhallawa, simon.fraser, webkit-bug-importer, zalan, zimmermann
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Mac (Apple Silicon)   
OS: macOS 13   
Attachments:
Description Flags
SVG test file along screenshots for Safari, Firefox and Chrome none

quentin
Reported 2023-10-06 08:26:08 PDT
Created attachment 468089 [details] SVG test file along screenshots for Safari, Firefox and Chrome Hi, I created a test SVG file containing an hexagon grid. When I set shape-rendering to crispEdges, the hexagon grid look perfect in Firefox (118.0.1) and Chrome (117.0.5938.149), there are no visible gaps between hexagons. However with Safari, a thin gap exists between hexagon rows as shown in the attached screenshot. WebKit build: 268988@main
Attachments
SVG test file along screenshots for Safari, Firefox and Chrome (15.30 KB, application/zip)
2023-10-06 08:26 PDT, quentin 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2023-10-13 08:27:14 PDT
<rdar://problem/116920859>
Said Abou-Hallawa
Comment 2 2023-10-13 09:20:58 PDT
Thanks for reporting this bug. Unfortunately I cannot reproduce it on iMacPro/macOS Sonoma or MacBookPro(M1 2021)/macOS Sonoma. So I think this is hardware and macOS specific bug. Can you please specify the hardware and the macOS version in which you can reproduce this bug?
quentin
Comment 3 2023-10-14 02:13:32 PDT
I could not reproduce it either on a MacBook Pro 13' (2018 - Core i7) running Monterey 12.6.2 and Safari 15.6.1 (17613.3.9.1.16). The machine where it occurs is a MacBook Air 13' (M1 2020) running Ventura 13.1. I'm going to update to the latest Ventura version and see whether the issue persists.
quentin
Comment 4 2023-10-21 04:23:28 PDT
I updated my MacBook Air 13' (M1 2020) to Sonoma 14.0 and the issue is still visible with the built-in Safari version.
Note You need to log in before you can comment on or make changes to this bug.