What you see is NOT What you Get

Live Preview vs. Read Mode Major Incongruity

I need help. There are a lot of inconsistencies between Live Preview and Read Mode that effect both how I type things out (if I see bullet points) vs. how it looks Read mode (but Obsidian sees it as something else in read mode), and it prints out what Read Mode sees not what I am seeing.

My research into this matter suggests that this is somewhat to be expected; but I am finding the differences to be greater than what I think I am supposed to expect (and some of it appears unfixable with CSS modification).

No matter what theme I use, with or without snippets, these issues exists:


Blockquotes

Blockquote in Read Mode can only handle approximately 96 words, 732 characters. In Live Preview and Source Mode there is not a single indicator that when I go into Read Mode and export to PDF it will not show the entire quote.

Blockquote in Live Mode

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce consectetur sollicitudin ex, molestie pellentesque augue scelerisque tincidunt. Curabitur vestibulum ut arcu sed rhoncus. Cras et elit eget nisl facilisis sodales. Pellentesque condimentum posuere lobortis. Sed tempus commodo varius. Aliquam rhoncus dignissim pellentesque. Praesent tempor blandit metus eget molestie. Integer quis mollis augue, bibendum dapibus ipsum. Aliquam faucibus ligula in sapien commodo, id feugiat libero ullamcorper. Vestibulum sollicitudin elit vel nisl finibus vestibulum. Nulla eget semper turpis. Aliquam ex odio, dictum vitae gravida ut, mollis at ligula. Vestibulum congue libero vel erat pellentesque, vel consequat tellus ullamcorper.

Duis tempor libero eros, nec bibendum tellus pellentesque et. Donec suscipit eget lectus quis convallis. Pellentesque id consequat erat. Cras magna leo, bibendum vel bibendum non, faucibus vel turpis. Nunc quis purus ut massa aliquam egestas. Morbi sed suscipit eros, et iaculis velit. Nam tempus neque eu sapien maximus, quis vestibulum mi euismod. In hac habitasse platea dictumst.

Maecenas faucibus eget urna et semper. Ut convallis lorem a elit cursus tristique. Aliquam purus mi, imperdiet sit amet luctus quis, tempor at arcu. Morbi dignissim, ligula id dignissim tincidunt, dolor nulla molestie metus, vitae vehicula elit nulla in ante. Ut sit amet interdum leo. Cras pharetra lorem in nibh varius tempor. Ut sagittis tortor eu varius dapibus. Mauris posuere libero at luctus ultricies. Etiam dapibus ligula vitae sollicitudin gravida. Sed id erat a ipsum ultricies pretium a tincidunt neque. Donec in magna congue, mollis ligula vel, maximus libero.

Blockquote in Preview Mode

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Fusce consectetur sollicitudin ex, molestie pellentesque augue scelerisque tincidunt. Curabitur vestibulum ut arcu sed rhoncus. Cras et elit eget nisl facilisis sodales. Pellentesque condimentum posuere lobortis. Sed tempus commodo varius. Aliquam rhoncus dignissim pellentesque. Praesent tempor blandit metus eget molestie. Integer quis mollis augue, bibendum dapibus ipsum. Aliquam faucibus ligula in sapien commodo, id feugiat libero ullamcorper. Vestibulum sollicitudin elit vel nisl finibus vestibulum. Nulla eget semper turpis. Aliquam ex odio, dictum vitae gravida ut, mollis at ligula. Vestibulum congue libero vel erat pellentesque, vel consequat tellus ullamcorper.

Duis tempor libero eros, nec bibendum tellus pellentesque et. Donec suscipit eget lectus quis convallis. Pellentesque id consequat erat. Cras magna leo, bibendum vel bibendum non, faucibus vel turpis. Nunc quis purus ut massa aliquam egestas. Morbi sed suscipit eros, et iaculis velit. Nam tempus neque eu sapien maximus, quis vestibulum mi euismod. In hac habitasse platea dictumst.

Maecenas faucibus eget urna et semper. Ut convallis lorem a elit cursus tristique. Aliquam purus mi, imperdiet sit amet luctus quis, tempor at arcu. Morbi dignissim, ligula id dignissim tincidunt, dolor nulla molestie metus, vitae vehicula elit nulla in ante. Ut sit amet interdum leo. Cras pharetra lorem in nibh varius tempor. Ut sagittis tortor eu varius dapibus. Mauris posuere libero at luctus ultricies. Etiam dapibus ligula vitae sollicitudin gravida. Sed id erat a ipsum ultricies pretium a tincidunt neque. Donec in magna congue, mollis ligula vel, maximus libero.


Lists

Lists Asterics in Live vs. Read mode

In read Mode: if I indent the ‘disk’ style bullet point, it turns into an asterisks. This gives the illusion of it being a list, but instead creates an ‘italic’, even though I have not closed it with a following asterisk. *italic* .

In Live Preview mode it appears as a list like any other list:

	*Item1
	*Item2
	*Item3

But in Read Mode it appears as:
              Item1
              Item2
              Item3

Incongruity between Read and Live lists

I realize that Read and Live Mode both use separate CSS codes entirely and so when you try to style bullets you have to ‘code’ it twice, once in Live and then again in Read.

As of right now I cannot target Live Modes bullet structure:

* Item1 - style disk
	* Item1 - style disk
		* Item1 Style -disk

But in Read Mode I can target the Live modes so I can see:

  • Item 1- style disk
    • Item2 - style circle
      • Item3 - style square

I have found no work-around to fix it so that what I see in Read Mode matches up with Live Lists

Is this how it is supposed to work?

I do not know if these are bugs or how Obsidian is supposed to work, but I desperately need help to find a work around as it has added an extra layer of challenge for me as “What you see is not what you get” adding a layer of complexity when it comes to formatting and prepping each note for export. I am happy to work around it, but, I don’t know how to fix it.

Also my blockquotes often are longer than the character limit with <br> and I currently have no work around to fix that. (Is there some code I can tweak to adjust the character limit and add spaces?)

I had attempted to request help finding a work-around here (Help Changing List-style) but no one responded; This has gotten bad enough that I can no longer rely on exporting through Obsidian as it has rendered Read mode inconsistent and only semi-useful.

Conclusion

I would be grateful for any help, worker around and insight.

1 Like

Moved to help for not following bug report template.
I suggest you search the forum some of these issue have Bug Reports/Feature Requests open.

Thank you for helping me understand better what I have done that was inconsistent with forum guidelines.

If some of these issues have bug reports or feature requests open then I need help from anyone who can point me in the direction to these threads.

I did (before I posted) and have again searched the forum but wasn’t sure what exactly to type into the search bar, or if what I found was what I was dealing with my search terms were:

“What you see is not what you get”
“Incongruity between live and read mode”
“mismatch between live and read mode”

Did not bring up desired results.

Typing also:

“Inconsistency between live and read mode”
“Inconsistency between live and edit mode”

This brought up some results but I am having difficulty figuring out if the bugs are the same as what I am reporting example Preview mode syntax discrepencies, example is this an example of what you mean when you say it is a Bug Report or Feature Request?

Nothing I typed appeared as a ‘feature request’.

Which suggests that my search terminology is inadequate. I am having difficulty in these areas:

  • I am not quite sure what search terms or terminology I am supposed to use to bring up the correct results for the problem that I have.
  • It is also difficult when I am not sure if what I’m looking at is a Bug (the way Obsidian is supposed to work) or a Feature Request (if it IS supposed to be the way it is supposed to work).

I know using other notetaking apps this is not a problem; but maybe Obsidian was designed with different thoughts in mind on how it should work. If this is the case I am open to it. So, I come here to understand.

You mentioned you moved to HELP for not following bug Report template form

Is it a bug though? Or is it the way Obsidian is supposed to work?

  • If it is how Obsidian should work then Help is the right category for this post, as I am not requesting any features, and just need help.
  • If it is truly a ‘bug’ and I formatted wrong I am happy to have the post deleted or archived (whichever is deemed fit) so I can correct my error and try again following the proper ‘bug report template’ (however)
  • If it has already been brought up before and is simply a duplicate of already existent posts then I would not like to type it up again, instead, if someone could point me in the right direction to the issue that has being tracked.

You mention some of these issues have Bug Reports / Feature Requests open? Could you or anyone really, help point me to the right terminology to use to find those forums/ posts? (or) the posts already tracking this issue?

The shortest answer to your many points, is that yes, this is expected. Mostly, you just need to learn some of the Markdown syntax. A 100% match in formatting is not expected.

There is no limit to the length of a block quote. Just make sure you include a > in the lines separating your paragraphs. If you still have your block quote being truncated, then can you please paste your text in a code block so we can see and copy your exact input formatting? Surround your entire text with triple backticks to use a code block.

(Unless you are talking about when you export to another format? See my final question.)

> Paragraph 1
> 
> Paragraph 2
> 
> Paragraph 3

Again, this is a Markdown syntax issue. To make a bullet, you must put space between the asterisk and the word. *Item1 is incorrect. * Item1 is correct. But if you indent the line with 4 spaces:

    * Item1

you are telling Markdown you intend a “pre-formatted” block.

You are pasting formatted code into the forum, so it isn’t possible to see what you are trying to do in Obsidian. Again, if you surround your text in triple backticks, we can see exactly what you are inputting into Obsidian, and attempt to reproduce and offer suggestions. Otherwise, I’m not sure what you intend it to look like.

Same with your other thread. You pasted formatted code into the forum. It’s difficult to tell what you intended. Code or screenshots would help.


What exactly are you trying to do? What is your final export target? Some context might help people give you useful suggestions.

1 Like

u r not wrong about having to “code twice”, but to me it’s just adding additional selectors. if u need to have disc-circle pattern, u can include this snippet. u can go crazy on the symbols (in my code below, using hex code, similar to how obsidian use for disc i.e. \2022 (technically it’s &#x2022;)

.mod-cm6 span.cm-list-2 span.list-bullet::after { content: "\25E6"; } /* circle */
.mod-cm6 span.cm-list-3 span.list-bullet::after { content: "\25fd"; } /* square */
2 Likes

Oh my gosh, thank the both of you for your help and understanding.

@rigmarole wow!! It was indeed an error in my markdown syntax (needing to learn more how it works). Every tip you gave relating to understanding the syntax helped me learn where my errors are and to correct them.

Before this post my markdown abilities are your basic bold, italic, and headers! And my proper syntax was no good. Your corrections in my syntax fixed the error I was having. Crazy! (how) Such little things caused such big discrepancies, I can’t thank you enough.

@efemkay Oh my gosh; thank you, thank you, thank you!!!

I cannot say enough how much I appreciate this. I was pulling my hair trying to figure all of this out.

You both resolved my post.

I am bowing gasshō . Thank you both again.

3 Likes