Inconsistent "New note" name behavior in web UI
Open
Nobody has claimed this yet.
bug
need to reproduce
- Dominant language
- JavaScript
- Stars
- 738
- Forks
- 162
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 35
Description
This is a very minor bug.
Steps to reproduce
- Ensure no notes are named "New note"
- Create a new note in the web UI (I will call this note A)
- Observe the note is named "New note"
- Write "foo" in the note body
- Click on the check icon to save the note
- Observe the note is renamed to "foo"
- Edit "foo" in the note body to "foobar"
- Click on the check icon to save the note
- Observe the note is renamed to "foobar"
- Create a new note in the web UI (I will call this note B)
- Observe the note is named "New note"
- Write "bar" in the note body
- Create a new note in the web UI (I will call this note C)
- Observe note B is still named "New note"
- Observe note C is named "New note (1)"
- Write "baz" in the note body
- Create a new note in the web UI (I will call this note D)
- Observe note B is still named "New note"
- Observe note C is named "New note (1)"
- Observe note D is named "New note (2)"
- Write "quux" in the note body
- Click on the check icon to save note D
- Observe note D is renamed to "quux"
- Click on note B
- Edit "bar" in the note body to "bar bar"
- Click on the check icon to save note B
- Observe note B is renamed to "bar bar"
- Edit "bar bar" in the note body to "bar bar bar"
- Click on the check icon to save note B
- Observe note B is renamed to "bar bar bar"
- Click on note C
- Write "baz baz" in the note body
- Click on the check icon to save note C
- Observe note C is still named "New note (1)"
- Click on note B
- Edit "bar bar bar" in the note body to "bar bar bar bar"
- Click on the check icon to save note B
- Observe note B is still named "bar bar bar"
- Question my sanity after writing this
Expected behaviour
Consistent
Actual behaviour
Inconsistent
Server
- Notes app version: 4.12.3
- Nextcloud version: 32.0.0.13
- OS: Debian 12.11
- Web server: apache2 2.4.62
- PHP version: 8.2.28
- Database: MariaDB 10.11.11
Nextcloud configuration:
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"nextcloud.example.com"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "32.0.0.13",
"overwrite.cli.url": "https:\/\/nextcloud.example.com",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"memcache.local": "\\OC\\Memcache\\APCu",
"memcache.distributed": "\\OC\\Memcache\\Redis",
"redis": {
"host": "***REMOVED SENSITIVE VALUE***",
"port": 0,
"dbindex": 0,
"password": "***REMOVED SENSITIVE VALUE***",
"timeout": 1.5
},
"maintenance": false,
"maintenance_window_start": 1,
"theme": "",
"loglevel": 2,
"default_phone_region": "US",
"mail_smtpmode": "smtp",
"mail_smtpsecure": "ssl",
"mail_sendmailmode": "smtp",
"memories.exiftool": "\/var\/www\/nextcloud.example.com\/apps\/memories\/bin-ext\/exiftool-amd64-glibc",
"memories.vod.path": "\/var\/www\/nextcloud.example.com\/apps\/memories\/bin-ext\/go-vod-amd64",
"memories.db.triggers.fcu": true
}
}
Client
Please complete the following information.
- Browser (incl. version): Firefox 142.0 (64-bit)
- OS: Debian forky/sid (using KDE)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the note-creation and save sequence in the web UI, then trace the code handling note titles during creation and saving. The fix is done when notes created as “New note” receive consistent names and later edits follow one consistent naming behavior across the reported sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100