Hi, Hi, There is something really "strange" with the Notes field of 1Password. Eventually I see an "Italic" in the middle of the text. I always considered Notes as a Plain Text field, but I guess there is some formatting inside it. The problem is that some password just "start" this "Italic" formatting and do not show some chars while not editing. Also, the spaces I insert at the beginning of line are not shown when not editing. For instance, below you find a small part of a password... When I am editing, I see this: lw*ru When I am not editing, I see this: lw_ru_ (ru is Italic and * is not shown) (looks like _ is not converted to Italic in this editor) I have the images to show the case above, but there is no attachment in this discussion. Why ? IMHO Notes should be a Plain Text field. I save a lot of information there and eventually Passwords. Thanks 1Password Version: 8.10.46 Extension Version: Not Provided OS Version: Not Provided Browser: Not Provided

Siegmar I'm sorry that notes aren't being rendered properly in the latest version of 1Password. I've been able to reproduce the issue using my own device when markdown formatting is turned off and I've filed an internal work item with our development team so that they can get this fixed. For the time being, enabling markdown is an available workaround for the issue. -Dave ref: dev/core/core#33725

Siegmar Thanks for reaching out. The issue that my colleague GreyM1P mentioned in their post has been fixed in the latest version of 1Password for Windows: We’ve fixed an issue where spaces were not properly formatted after a Secure Note was saved. Please update if you haven't already to 8.10.58 or later: How to keep 1Password up to date Support If you still see an issue then please post a screenshot of what you see (make sure that it doesn't contain any sensitive information) and I can help further. -Dave

Hello Siegmar! 👋 Thank you for reaching out! Secure Notes, and the notes field in items, in the 1Password app supports markdown which is a method of formatting your notes with additional styles. You can read more about markdown here: Format your secure notes with Markdown Does some of the text that you entered correspond to this markdown formatting? I recommend that you save your passwords in a passwords field, not the notes field. However you can also turn off markdown so that your notes render in plain text by following these steps: Open and unlock 1Password for Windows. Click your account or collection at the top of the sidebar and click Settings. Click General. Turn off "Format secure notes using Markdown". I hope that helps. 🙂 -Dave

Hi, Some weeks ago I removed the Markdown setting and everything worked fine. But today, out-of-nothing the end-of-line is removed from text in VIEW mode: the EDIT mode works fine. The only way to show the end-of-line in VIEW mode is enabling Markdown again. Did something change in 1Password? Thanks

Hi Is there any schedule for this BUG to be fixed? Thanks

1Password Notes field with "strange" formatting

1P_Dave
Moderator
2 months ago
Siegmar

Thanks for reaching out. The issue that my colleague GreyM1P mentioned in their post has been fixed in the latest version of 1Password for Windows:

We’ve fixed an issue where spaces were not properly formatted after a Secure Note was saved.

Please update if you haven't already to 8.10.58 or later: How to keep 1Password up to date Support

If you still see an issue then please post a screenshot of what you see (make sure that it doesn't contain any sensitive information) and I can help further.

-Dave
Siegmar
New Contributor
2 months ago
Hi Dave,

Any news about this fix?

I use Markdown a lot in my GitHub repos, but I just want to use plain text.
IMHO, using Markdown is a little bit too much for password observation: it is not something I will publish, it just an observation.

Thanks
GreyM1P
1Password Team
2 months ago
Siegmar

Thanks for letting us know. We're already working on this particular issue, and I'm sorry for the inconvenience. In the meantime, you could enclose text like that in ``` three backticks (above and below) so that it appears as pre-formatted text, like this:

Pre-formatted text won't be interpreted as Markdown and so will be forced into a plain text rendering mode.

— Grey

ref: dev/core/core#34364
Siegmar
New Contributor
3 months ago
Hi,

Hi,
After 5 minutes 1Password Desktop shows the same error :-(
The version is "1Password for Windows 8.10.56 (81056028)" and there are no updates.

When I use the Web (Browser) version, everything works fine (no Markdown).

When I use the Desktop version, the text below...

```
ABC BOLD ABC

H1

H2

ABC
{
123 <- there are 2 spaces at the beginning
123
}
```

... is shown as ...

ABC **BOLD **ABC

H1

H2

ABC
{
123
123
}

The BOLD and HEADINGs Markdown syntax is, correctly, rendered when Markdown is enabled and not rendered when disabled.
But the spaces at before "123" are removed in both cases.
Looks like, it's a small BUG with spaces: please, do not remove spaces at the beginning.

Thanks
Siegmar
New Contributor
3 months ago
Working fine now :-)
Thanks
1P_David
1Password Team
3 months ago
Siegmar

The fix should now be available in 1Password for Windows version 8.10.56.

How to keep 1Password up to date

Let me know if you're still experiencing any trouble.

-David
Siegmar
New Contributor
3 months ago
Hi,
Any news about this fix?
Thanks
1P_Dave
Moderator
4 months ago
Siegmar

The team is currently testing a fix for the issue in the nightly version of 1Password. Once testing is complete, the fix will graduate to the beta and then to the stable version as soon as possible.

-Dave
Siegmar
New Contributor
4 months ago
Hi
Is there any schedule for this BUG to be fixed?
Thanks
1P_Dave
Moderator
5 months ago
Siegmar

I'm sorry that notes aren't being rendered properly in the latest version of 1Password. I've been able to reproduce the issue using my own device when markdown formatting is turned off and I've filed an internal work item with our development team so that they can get this fixed.

For the time being, enabling markdown is an available workaround for the issue.

-Dave

ref: dev/core/core#33725