Troubleshooting SlashSnip: Common Issues and Fixes

Troubleshoot SlashSnip by separating trigger detection, insertion, variables, and host-site console noise before changing settings or blaming the extension.

What should you check if the shortcut did nothing?

Check:

• the extension is enabled;
• the stored shortcut exists;
• the current field is a normal input, textarea, or supported contenteditable surface;
• alias trigger settings match what you typed.

The menu opened in the wrong place

This usually points to a caret anchoring problem, not a total product failure.

Validate:

• whether the editor is contenteditable;
• whether the same page has a simpler input field;
• whether the problem only appears with /// or also with direct insert.

Variables looked wrong

Check that the snippet contains supported markers only:

• {cursor}
• {{date}}
• {{time}}
• {{clipboard}}

If {{clipboard}} is empty or stale, the current clipboard state is often the real issue.

Console is noisy

Do not blame all console output on SlashSnip. Separate:

• host-site warnings and errors;
• unrelated browser extension noise;
• actual SlashSnip regressions in detection, insertion, or caret placement.

What should you read next?

• Recheck the shortcut and trigger model.
• Use the compatibility playbook for a surface-by-surface verification pass.