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
The bug is the extra </span> inserted into the text.
I can see a way of working around this, and I probably will do so; but this is new behavior that is affecting a longstanding web site of mine (though I can't specify the kramdown update in which the problem started, sorry) so perhaps it counts as a genuine bug.
The text was updated successfully, but these errors were encountered:
This behaviour has changed in version 1.11.0 - have you been running a version older than this before? Have to dig a bit to find out why this behaviour changed because it probably shouldn't have.
Why are you using markdown="1" in the first <span> element? This seems to be causing the issue.
Yes, clearly I was using an older version of kramdown the last time I built my site. The change seems surprising; what I'm doing was never obviously forbidden by the kramdown syntax rules — nested <span> is legal, and kramdown probably shouldn't care at what level the markdown="1" occurs — and injecting </span> into my text seems just wrong. The workaround from my end is to move that markdown="1" into the inner <span> element, or remove the nesting entirely (i.e. have just one level of <span>). There is more going on here at kramdown's end; for example, if you remove the outer <div> the issue doesn't arise.
mattneub
added a commit
to mattneub/RubyFrontier
that referenced
this issue
Jan 13, 2020
Run the following:
The output is:
The bug is the extra
</span>
inserted into the text.I can see a way of working around this, and I probably will do so; but this is new behavior that is affecting a longstanding web site of mine (though I can't specify the kramdown update in which the problem started, sorry) so perhaps it counts as a genuine bug.
The text was updated successfully, but these errors were encountered: