Focused crawls are collections of frequently-updated webcrawl data from narrow (as opposed to broad or wide) web crawls, often focused on a single domain or subdomain.
Access new note on desktop app - Title display is different from mobile and data has been lost
Edit note on desktop + sync
Sync mobile + access note - Now only has single title line, overflow has been moved to body but the "1CR" line has been lost
Mobile seems happy to display the title including the CRLF:
Notes panel:
Viewer:
Desktop puts extra lines into the body of the note (but not all of it - "1CR" is missing):
Content of desktop database ("1CR" has been lost):
sqlite>SELECT title,
...> body
...>FROM notes
...>WHERE id ="db7daac4e933415c93aaf1c0939df9b1";
Title|2cr
Line after return
Line after return and 2 spaces
Note body line 1
Content of sync target md file:
Title 1cr 2cr
Line after return
Line after return and 2 spaces
Note body line 1
Describe what you expected to happen
Mobile should not be allowed to put CRs into titles. If it is allowed to then all the data should be visible to the desktop app - current behaviour casuses some data to be lost.
Behaviour of pressing return on mobile keyboard should move cursor to note body
Environment
Mobile
Joplin 2.3.4
Database v39
Android 11
USING BETA EDITOR
Desktop
Joplin 2.3.5 (prod, win32)
Client ID: a4ed20b9be424a1c8c3e5f3cc355c345
Sync Version: 3
Profile Version: 39
Keychain Supported: Yes
Revision: 819af3c
Windows 10
Steps to reproduce
Mobile seems happy to display the title including the CRLF:
Notes panel:


Viewer:
Desktop puts extra lines into the body of the note (but not all of it - "1CR" is missing):
Content of desktop database ("1CR" has been lost):
Content of sync target md file:
Describe what you expected to happen
Mobile should not be allowed to put CRs into titles. If it is allowed to then all the data should be visible to the desktop app - current behaviour casuses some data to be lost.
Behaviour of pressing return on mobile keyboard should move cursor to note body
Logfile
syncReport-1632085837890.txt
log.txt
The text was updated successfully, but these errors were encountered: