Not possible to change or create custom fields in "{} biblatex source" tab

JabRef version

Latest development branch build (please note build date below)

Operating system

GNU / Linux

Details on version and operating system

JabRef 100.0.0 Linux 5.4.0-113-generic amd64 Java 18.0.1 JavaFX unknown

Checked with the latest development build

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. Go to {} biblatex source tab
2. Try to add a new custom field e.g. whatever = {whatevernot},
3. Switch to a new tab or select another entry in the maintable
4. Switch back to {} biblatex source tab

What happens:

New custom entry has not remained. It has vanished.

Additional info:

• It is possible to change whatever is WITHIN a field (withing the curly braces { }).
• Changing anything OUTSIDE of a field is not possible anymore and will be deleted upon switching. E.g. changing the field title by typing date will lead to vanishing.

Cause: I tested some recent commits and found it was caused by 7257350b60427fbd6ee5b6f65641fe912ae8e78a

What to do:

Not sure. We have the choice between pest and cholera.

• Revert: We gain the feature back, but we also got an indexoutofbounds issue.
• Have commit: Fixes an index out of bounds issue, but we loose the feature.
  • Also it is still possible to create customized fields. Very lengthy workarounds:
    • Fields can be created under options > customize entry types
    • Customized Fields can be edited directly in the library file (via texteditors) and imported into JabRef

Appendix

No response

[LIM0000]

Hi team, I have done some researches on this issue again and would like to share my findings here.

After digging much deeper of this issue, I have found that the cause of UnsupportedOperationExpection is due to inconsistency of modifying ObservableMap from FXCollections. For some reason, only the steps to reproduce issue in https://github.com/JabRef/jabref/issues/8012 trigger ObservableMap to be immutable and throw exception if any methods try to modify it.

Both remove() and put() which modifies the ObservableMap. If immutable, both the methods will throw exception.

Additional information: Apologize that I have to raise my findings from technical perspective here instead of creating a new PR as I could not find a solution for this issue just yet.

[ThiloteE]

Closing this issue, as the commit was reverted.