Front matter metadata are capitalised in a preview mode (regression)

Steps to reproduce

Disable all community plugins, set theme to the “Default” one

Enable “Show frontmatter” under “Editor” section of settings.

In source mode, create markdown file like this one (note 2 levels of publications field):

---
nice_title: "A Beautiful Art Piece"
---

# Art Piece

some content

Switch to preview mode.

Now, nice_title from front matter is shown as Nice_title (note first character became upper case)

Expected result

Fields are rendered with their names unchanged. For example nice_title should be shown as nice_title

Actual result

Fields are rendered with their names changed. For example nice_title is shown as Nice_title

Environment

  • Operating system: macOS Ventura 13.0.1
  • Debug info:
SYSTEM INFO:
	Obsidian version: v1.1.8
	Installer version: v0.15.9
	Operating system: Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 22.1.0
	Login status: logged in
	Catalyst license: none
	Insider build toggle: off
	Live preview: off
	Legacy editor: off
	Base theme: dark
	Community theme: none
	Snippets enabled: 1
	Restricted mode: off
	Plugins installed: 21
	Plugins enabled: 0

RECOMMENDATIONS:
	Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

Additional information

  • I consider it a regression, therefore categorized it as a bug.

  • I think it changed somewhere around introduction of Obsidian 1.0

  • source mode vs preview mode on a more complex case (my real note)

1 Like

You can sort this out with a css snippet:

.frontmatter-container .frontmatter-section-label {
   text-transform: none; 
}

Thanks! It works great for me! :grinning:

just in case: I will keep this forum thread open, since I consider recent changes to front matter as breaking and am not fully satisfied with a workaround solution instead of a change of approach in a native way the Obsidian treats front matter

2 Likes

There are ongoing changes to frontmatter, so I am not gonna take this as a bug.

As a user who just uses Obsidian (I mean: do not involve in active tracking of changelogs etc.) I perceive such changes as breaking ones. Especially when they come under label of new big 1.0 release, which makes me no longer think of it as of something that is subject to ongoing changes :thinking:

This changed in 1.1 and the yaml/frontmatter is being reworked.