Steps to reproduce:
- Open Settings → Appearance (sandbox vault, restricted mode on — no plugins involved)
- Hover over a sub-page row (e.g. CSS snippets)
- For contrast, hover over an action-style row elsewhere in settings (e.g. Add secret under Keychain), which highlights on hover
Did you follow the troubleshooting guide? Yes — reproduces in the sandbox vault with restricted mode on.
Expected result: the page row shows hover feedback. The app stylesheet declares exactly that intent:
.setting-item.mod-navigable {
align-items: center;
cursor: var(--cursor);
transition: background-color 0.15s ease-in-out, color 0.15s ease-in-out;
}
Actual result: no hover feedback — there is no :hover rule for .mod-navigable anywhere in app.css, so the declared background-color transition is dead code on desktop. The two sibling states both work, which makes the gap look like an oversight rather than a design choice:
/* action rows hover… */
@media (hover: hover) {
.setting-item.mod-action:hover {
background-color: var(--background-modifier-hover);
}
}
/* …and navigable rows highlight on mobile tap */
.setting-item.mod-navigable.mobile-tap {
background-color: var(--background-modifier-hover);
}
So a page row animates its background on touch devices but never on desktop hover, while the action row two groups down hovers normally. The likely intended rule is the one-line analog of the mod-action one:
@media (hover: hover) {
.setting-item.mod-navigable:hover {
background-color: var(--background-modifier-hover);
}
}
Noticed while migrating a plugin to getSettingDefinitions() (page rows sit next to an action row and the inconsistency is conspicuous); we ship that rule scoped to our own groups as a workaround.
Environment: Obsidian 1.13.4 (installer 1.13.4), macOS. Reproduces with restricted mode on.