Fix: abstract field loses markdown formatter after resetting default preview style

[LoayGhreeb]

After PR #10896, the abstract field now supports markdown.
If I try to reset the default preview style from the preferences, the abstract loses the markdown formatter.

• Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (for UI changes)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[LoayGhreeb]

There is also a related issue for the same PR, when running the program from IntelliJ pasting HTML code into fields works fine but when running the latest development release, it causes an exception:

java.lang.IllegalAccessError: class com.vladsch.flexmark.html2md.converter.FlexmarkHtmlConverter (in module 
org.jabref.merged.module) cannot access class org.jsoup.Jsoup (in module org.jsoup) because module org.jabref.merged.module 
does not read module org.jsoup

[Siedlerchr]

Thanks for the hint, this looks like some modularity issue (happens whe not all libraries are modularized). I'll take a look at it. (You can build executables of JabRef also manually using ./gradlew jlink or ./gradlew jpackage)

I'll prepare a fix

[Siedlerchr]

#10943

[koppor]

Nice catch.

Re-thinking, I think, MARKDOWN should be removed from abstract and added to review

[koppor]

@LoayGhreeb Could you please do more (as suggested at #10942 (review))? Meaning: No Markdown support for abstract, but for review!

[LoayGhreeb]

@koppor I'm not sure what the benefit of supporting MARKDOWN for the review field is, since it's not visible in the preview.
Are these the needed changes?

[koppor]

Are these the needed changes?

Changes are fine, thank you!

@koppor I'm not sure what the benefit of supporting MARKDOWN for the review field is, since it's not visible in the preview.

Ah, this reminds me, that we silently change the field review to comment 🙈. Refs #10370. This needs to be changed soon.

Thus, adding MARKDOWN to review is not that senseful, but maybe, we bring back the field and then it has the "right" properties.