Skip to content

".theme-light .markdown-rendered :not(pre) > code" interferes with Meta Bind plugin #1

Description

@CorvusPenn

Firstly, love your theme! it's really easy on the eyes and nice to work in.

However, I ran into an issue where the rendered markdown styles for code create visual overlays on the Meta Bind plugin's inline code features (Buttons, Inputs, Views). As far as I can tell, the way the styles are coded in HearthCode override Meta Bind's styles that hide inline code and render it's own features instead.

I was able to solve this by editing the theme file, commenting out both .theme-light .markdown-rendered :not(pre) > code and .theme-dark .markdown-rendered :not(pre) > code sections and creating my own css snippet:

.theme-dark {
    --code-normal: var(--hearth-md-inline-code);
    --background-color: var(--code-background);
    --code-radius: 5px;
    --code-border-width: 1px;
    --code-border-color: var(--hearth-md-code-border);
}

.theme-light {
    --code-normal: var(--hearth-md-inline-code);
    --background-color: var(--code-background);
    --code-radius: 5px;
    --code-border-width: 1px;
    --code-border-color: var(--hearth-md-code-border);
}

.markdown-rendered code {
    padding: 0.05em 0.34em;
}

Which left regular inline code styled as the theme intends without forcing an override on Meta Bind.

But editing the theme itself isn't great when an update will reset the patch job.
I wanted to let you know this was happening and perhaps request an alteration to how the styles are applied so they don't conflict/overlay other plugins' added features.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions