Bug 262786 - Setting shape-rendering to crispEdges doesn't eliminate thin gaps between hexagon rows
Summary: Setting shape-rendering to crispEdges doesn't eliminate thin gaps between hex...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: WebKit Nightly Build
Hardware: Mac (Apple Silicon) macOS 13
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-10-06 08:26 PDT by quentin
Modified: 2023-10-21 04:23 PDT (History)
5 users (show)

See Also:


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

Note You need to log in before you can comment on or make changes to this bug.
Description quentin 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
Comment 1 Radar WebKit Bug Importer 2023-10-13 08:27:14 PDT
<rdar://problem/116920859>
Comment 2 Said Abou-Hallawa 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?
Comment 3 quentin 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.
Comment 4 quentin 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.