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!
Hello @Daniel_Pfeiffer,
If you look at the documentation for strikethrough, you will find the stroke parameter which defaults to auto.
If set to
auto, takes on the text’s color and a thickness defined in the current font.
Setting stroke to black or any other color will do the trick.
#let mycontent = "Test"
#strike(
stroke: black,
text(mycontent, fill: gray),
)
As a side note, if you could please follow the guidance for naming questions:
We hope that by adhering to this, other users will find it easier to answer the same question in the future.
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.
But ok, at least it works now. 
I have updated my previous post. The documentation mentions that auto will take the text’s color.
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.