Closed tripleee closed 5 years ago
This is actually how the code is in the SO post, where is the problem?
@double-beep Are you sure? I'm not seeing it on the actual post.
@Undo1 you are right. I misunderstood the issue. Speaking of extra spaces in FIRE, I found:
where post is:
where that is a little bit strange. Spaces are added and I think it is related.
Actually @double-beep is correct. See below - note the blue selected area where I have selected the spaces:
The spaces are in the original post, so not a FIRE problem.
Also present in metasmoke:
The extra space is present on all code blocks, be it ````, ~~~, or the standard four spaces:
Examples - code with ~~~
Code indented with four spaces:
Reopening with a title change.
This is a CSS issue with an easy fix. I'll push an update. The problem is that the
.fire-popup .fire-popup-body code {
padding: 1px 5px;
}
has strange effects when it's within a <pre>
. That's easily solved.
It seems that code formatted with four spaces gets indented an extra space on the first line.
Sample screenshot from Chrome on MacOS Mojave, input is https://metasmoke.erwaysoftware.com/post/166877
I originally though this was because of the recent code formatting update in Stack Overflow's Markdown (and maybe it is) but this seems to affect the traditional code markup.