My apologies; I sometimes lose track of what sorts of technical knowledge is common among the Less Wrong crowd.
“Inline” and “block” are the two types (layout-wise) of elements in HTML (and many other systems). More or less, this means:
An “inline” element appears in the flow of text (a hyperlink, for example, is an inline element)
A “block” element is like its own paragraph (i.e., it’s like a block of text)
All of this is not specific to Less Wrong’s editor, or to any editor or website or anything; it’s just how HTML works.
So an inline image will be inserted right into the middle of a paragraph. A block image will be, basically, its own paragraph.
In a Markdown editor (whether LW’s or GW’s), whether an image is inline or block depends on whether the image syntax is in the middle of some other text, or whether it’s on a line by itself.
Thanks, but that doesn’t mean anything to me. Is this documented anywhere? Is this page the best documentation for the editor?
Is your comment even intended for users, or is it a hint for debugging?
My apologies; I sometimes lose track of what sorts of technical knowledge is common among the Less Wrong crowd.
“Inline” and “block” are the two types (layout-wise) of elements in HTML (and many other systems). More or less, this means:
An “inline” element appears in the flow of text (a hyperlink, for example, is an inline element)
A “block” element is like its own paragraph (i.e., it’s like a block of text)
All of this is not specific to Less Wrong’s editor, or to any editor or website or anything; it’s just how HTML works.
So an inline image will be inserted right into the middle of a paragraph. A block image will be, basically, its own paragraph.
In a Markdown editor (whether LW’s or GW’s), whether an image is inline or block depends on whether the image syntax is in the middle of some other text, or whether it’s on a line by itself.
In Less Wrong’s draft.js editor… well, see this comment by habryka.
I hope that helps. Feel free to ask me to explain further if anything’s not clear!