Questions/Problems

Sticky Note Toolbar Callouts disappear when scrolling through a long note...

Unfortunately this is due to how the editor (which uses CodeMirror) manages the viewport ↗ when scrolling, in order to manage memory and performance.

There no known workaround, other than perhaps repeating your toolbar further down your note, or consider using non-callout toolbars instead (depending on your use case).

If you're impacted by this, feel free to comment on issue #121. I'm open to exploring other features (e.g., heading-level toolbars) that might address your use case.

Settings are not synchronizing between devices...

Enable Load settings on change on the device you want to receive updates on.

If syncing stopped, try re-enabling that setting (if it's disabled). Failing that, check if your sync service is working, disable/enable the plugin, or restart the app.

Toolbar isn't sticking to the top of the note (or there's a gap)...

In Reading mode, the sticky style does not work. See issue #20 for any updates.

Themes and CSS snippets can affect the placement of the toolbar. Consider trying Style Settings plugin to adjust the top offset. Or, if you would rather create a snippet to override the top position, search for "sticky" in the CSS.

I am interested in any conflicts with themes (and plugins), so feel free to submit specifics here.

The styling of my toolbar looks weird...

First look at notes in the Styles documentation around precedence. If you're using Style Settings plugin please consult their documentation as well.

However, if you use other plugins, themes, or snippets that modify how callouts behave or look, they may have an effect on this plugin.

As noted, toolbars are a special form of callout, designed to fit naturally with Obsidian's look and feel. The plugin inserts toolbars between the metadata and content portions of the editor view, or at the top of the editor, assuming certain criteria are met.

Please log an issue if you think there’s a conflict with a theme, for example, that can be resolved in the plugin itself (e.g., missed a style that needs to be overridden). Pull requests are also welcome.

If you prefer to workaround any issues in the short term, styling is handled in styles.css by .callout[data-callout="note-toolbar"].

I'm using the Cyber Glow theme and the toolbar is being obscured by the note's filename...

This is because the header is set to position: absolute. Try this CSS snippet:

.workspace-leaf-content[data-type="markdown"] .view-header {
    position: inherit;
}

I want to link a toolbar item to a note...

Three approaches:

• Enter the name of the file (with folder and extension) in a File type link.
• Enter the name of the note in URI type link. If it doesn't exist on click, a new one will be created (per Obsidian's default behavior).
• Link to items within your vault by getting a URL to a note via Copy Obsidian URL or from a plugin (e.g., Advanced URI).

I was using a beta and my settings disappeared...

When using a beta, please always remember to back up the plugin's data.json first.

Note Toolbar does not make changes to vault data, but it's always a good idea to have a backup of your vault when testing any plugin betas.

Pre-1.3.0

I changed the ID of the plugin from obsidian-note-toolbar to note-toolbar for 1.3.0. To migrate your settings:

1. Find the old data.json in YOURVAULT/.obsidian/plugins/obsidian-note-toolbar/data.json
2. Copy its contents to data.json for the new plugin: YOURVAULT/.obsidian/plugins/note-toolbar/data.json

(If you installed via BRAT, simply renaming the folder and updating again with BRAT might work as well.)

Other plugin support

If you're having an issue with commands or URIs for a particular plugin, please test outside of toolbar (to make sure they work), and double-check their help documentation first.

I am interested in any conflicts with themes (and plugins), so feel free to submit specifics here.

Still need help? 🛟

Ask a question or request a feature! If you run into something that looks like a bug, please log an issue. If you don't have a GitHub account, use this Google form ↗.