ah ok I see, that’s from the topic New search operator "not"
It looks like it might have something to do with our lazyloaded images… it has the correct positioning applied inline (looks like this is all from lazy-load-images.js.es6),
position: absolute;
top: 82px;
left: 28px;
but the width and height are out of whack at
width: 500px;
height: 500px;
I just tried the “rebuild html” option on that post and that corrected it. That post predated our lazyload feature, so I wonder if it was just a fluke when we rebuilt all the posts after that feature was added?
Oh I spoke too soon, now it’s broken in a different way… and it just fixed itself again. Something a bit odd is going on… if I do a hard refresh I will temporarily see the huge image…
@dan it looks like you recently made some changes there… could this possibly be related?
Trying another onebox…
and this is what it looks like in the composer preview
