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
Let's say I have a figure with an image, and with CSS I make that figure float right. If I then put a <figure><pre><code> section in the body after the floated <figure>, all is well; the code fragment figure is displayed to the left of the floated-right figure.
Now the non-floating figure completely ignores the floating figure, and appears on top of the floating element. Presumably the CSS tricks played by the coy theme are so brute force that the don't accommodate floating elements.
(I can make a wild guess and say that maybe this is yet another repercussion of the shadows, because otherwise I don't see why the other styling would be so inflexible as to not play nicely with floats.)
The text was updated successfully, but these errors were encountered:
Hmmm... no, I was wrong. I don't think this is about the shadow, about coy, or even about Prism. It seems that my figure is taking up the entire width anyway --- I only notice it when I turn on Prism, as it gives my figure a background. I guess I'll just have to float the figure containing the <pre><code> as well. That seems to work.
OK, you can close this issue as invalid; I don't think Prism or coy is at fault here.
Let's say I have a figure with an image, and with CSS I make that figure float right. If I then put a
<figure><pre><code>
section in the body after the floated<figure>
, all is well; the code fragment figure is displayed to the left of the floated-right figure.But the I then bring in Prism with the coy theme:
Now the non-floating figure completely ignores the floating figure, and appears on top of the floating element. Presumably the CSS tricks played by the coy theme are so brute force that the don't accommodate floating elements.
(I can make a wild guess and say that maybe this is yet another repercussion of the shadows, because otherwise I don't see why the other styling would be so inflexible as to not play nicely with floats.)
The text was updated successfully, but these errors were encountered: