New lines are always bold (but only at the bottom)

Follow

Benjamin Welch

• October 03, 2020 13:05
• Edited

Hi WF Team,

I've noticed new lines are always bold in this one particular item's notes I'm working on. This only happens in the desktop version and not the web version. And it only happens in this note and it only happens if it's a totally new line. If I create a new line in the middle of my notes, it isn't bold.

I'm on MacOS Mojave and have the most recent version of WF. 

I have these experimental features enabled:

• Open links in app
• Dates
• Full width page
• Better interaction for cards in boards
• Templates

I hope this helps. 

0

• 

  Frank (Workflowy Support)

  • October 06, 2020 04:07

  Hi Benjamin,

  Would you try duplicating the item (Alt+Shift+D) and seeing if the duplicate has the same behavior?

  And/ or... would you try cutting the entire content of your note and then pasting it back without formatting (Ctrl+Shift+V).

  My thinking is that maybe you can get rid of the original offending node/ note by copying/ cutting/ nuking... whatever gets the job done.

   

  0

  Comment actions Permalink
• 

  Benjamin Welch

  • October 20, 2020 15:25

  Hi Frank,

  Thanks for the tips. The duplicate had the same exact behavior. Pasting the entire note without formatting solved the issue. However, this is a very, very long comment with formatting and so though this solves the bold ever new line, it will require a lot of work to reformat everything.

  Not sure there's anything else I can do here except try to find the culprit and delete it. Either way, seems like a bit of a bug since this keeps happening on new lines regardless of the formatting for the previous line.

  Thanks again for the help.

  0

  Comment actions Permalink
• 

  Benjamin Welch

  • October 20, 2020 18:22

  Hi Frank,

  After writing a bit more, I realized I used this symbol "↑" and notice that it made everything after it bold. Even in this comment field. Now I'll use another one "↑". 

  So, I think that arrow symbol had something to do with it. All fixed now.

  Cheers!

  0

  Comment actions Permalink

Please sign in to leave a comment.