In #strike[#text(mycontent, fill: gray)] I have strike outside of the colour setting (where I still have black.) But it gets permuted to the inside, magically also turning gray. This is obviously not what I want, or I would have nested it the other way round!
I see that the strike height is fetched from the font, so apparently this gets delegated to font rendering. Might be tricky to get this right, but still, please fix! Thanks a lot!
Thanks for the quick reply. Its still inside out, since it’s not in the current colour as the doc states, but in the colour that will be current by the time it’ll render.
Oh my bad! I was in a hurry to go and read “current” into the wrong context.
However I later realised that I found another inconsistency: I had been trying successfully to make the text gray with its stroke – only to find the smaller the font the more it withered away. Only when zooming in, did I notice that on text stroke means the outline, whereas here, even though this is tightly linked to text, it means the fill colour.
Seeing as this is still an unstable v0, I guess a breaking change to bring consistency (e.g. stroke and fill mean the same thing everywhere,) would still be ok. If that’s hard to swallow, transitionally hide it behind an opt in, later turn it into a warning and even later activate it by default.
I think “stroke” already is quite consistent. In the page for the stroke type it
Defines how to draw a line.
It’s unfortunate that “strike” is so similar to “stroke”. I would say if anything should/could change it would be “strike” to something like “strike-out”, “strike-through”, or “cross-out”.
Actually the page for strike already calls it “strikethrough”.