Closed rugk closed 4 years ago
Also affects StreetComplete_quest_crossing.svg
.
You can workaround this by selecting the figure and selecting "Stroke to path", cut the newly created path, undo, paste it at the same position. Then, remove the stroke paint from the original figure. (So you have one shape for the stroke and one shape for the fill)
Uh, interesting you know a workaround. (And thanks for your info.) Still, I'd (first) rather first try to figure out the root cause and at least create some issues at Inkscape or so, as this is just a bug somehow/somewhere…
So actually just clicking on "Stroke to path" did the trick. Thanks for that. (As far as I see/kinow the object is just converted to a path then, so there is no duplicate object I may remove.)
BTW if you are on Stackexchange (and want to gain some upvotes or so), feel free to comment on my question with more details or so…
So in the end it is an incompatibility with "paint-order", as it turns out. Don't know what to do here. For now, I'll just keep the workaround.
Thus closing this. 😃
This is how it looks in Inkscape:
In the repo and on https://wiki.openstreetmap.org/wiki/File:StreetComplete_quest_tactile_paving_crossing.svg in Firefox 55.0.2 on Linux it looks strange here:
Note that
StreetComplete_quest_tactilepaving.svg
looks fine.