You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JoKalliauer
changed the title
removing h0 in pathdata leads to not rending marker-start="url(#a)" in chromium
convertPathData removs h0 in pathdata leading to not rending marker-start="url(#a)" in chromium
Jan 6, 2023
I checked the spec, but I don't see an explicit answer on how to handle marker-start and marker-end for zero sized paths.
Here are my observations across clients, ✅ means it rendered something, otherwise the marker didn't render at all:
Firefox
marker-start
marker-end
M5 5
✅
M5 5h0
✅
✅
M5 5m0
✅
M5 5z
✅
✅
Chromium
marker-start
marker-end
M5 5
✅
M5 5h0
✅
✅
M5 5m0
✅
M5 5z
✅
✅
Eye of GNOME
marker-start
marker-end
M5 5
M5 5h0
✅
✅
M5 5m0
M5 5z
✅
✅
I'm thinking we optimize it as usual. However, post-optimization, we'll check was it a marker only path with a none M/m command. If so, we'll tack a z on the end to preserve the behavior with markers that can be seen consistently across clients.
The reason for z is that it's the shortest way to arbitrarily add a vertex for path markers.
Identical issue in scour-project/scour#282
Input
Output
Difference
compare in Chromium
settings
Copyright
source https://commons.wikimedia.org/wiki/File:2014_West_Africa_Ebola_Epidemic_-_New_Cases_per_Week.svg
author https://commons.wikimedia.org/wiki/User:Delphi234
license https://creativecommons.org/publicdomain/zero/1.0
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: