bugfix:The Mintlify navbar (logo + search bar with ⌘K) scrolls away w… (#2445)

* bugfix:The Mintlify navbar (logo + search bar with ⌘K) scrolls away when scrolling down the documentation, so it disappears from view.

* fix(docs): keep navbar visible on scroll (#2445) (thanks @chenyuan99)

---------

Co-authored-by: vignesh07 <vigneshnatarajan92@gmail.com>
This commit is contained in:
Yuan Chen
2026-01-26 20:39:10 -05:00
committed by GitHub
parent 2f7fff8dcd
commit 27174f5d82
4 changed files with 36 additions and 3 deletions

View File

@@ -39,6 +39,7 @@ Status: unreleased.
- Telegram: allow caption param for media sends. (#1888) Thanks @mguellsegarra.
- Telegram: support plugin sendPayload channelData (media/buttons) and validate plugin commands. (#1917) Thanks @JoshuaLelon.
- Telegram: avoid block replies when streaming is disabled. (#1885) Thanks @ivancasco.
- Docs: keep docs header sticky so navbar stays visible while scrolling. (#2445) Thanks @chenyuan99.
- Security: use Windows ACLs for permission audits and fixes on Windows. (#1957)
- Auth: show copyable Google auth URL after ASCII prompt. (#1787) Thanks @robbyczgw-cla.
- Routing: precompile session key regexes. (#1697) Thanks @Ray0907.

View File

@@ -115,6 +115,9 @@ body::after {
}
.shell {
position: sticky;
top: 0;
z-index: 100;
padding: 22px 16px 10px;
}

View File

@@ -1,9 +1,10 @@
---
title: "Node.js + npm (PATH sanity)"
summary: "Node.js + npm install sanity: versions, PATH, and global installs"
read_when:
- You installed Clawdbot but `clawdbot` is “command not found”
- Youre setting up Node.js/npm on a new machine
- `npm install -g ...` fails with permissions or PATH issues
- "You installed Clawdbot but `clawdbot` is “command not found”"
- "Youre setting up Node.js/npm on a new machine"
- "npm install -g ... fails with permissions or PATH issues"
---
# Node.js + npm (PATH sanity)

View File

@@ -0,0 +1,28 @@
import { readFileSync } from "node:fs";
import { join } from "node:path";
import { describe, expect, test } from "vitest";
function readTerminalCss() {
// This test is intentionally simple: it guards against regressions where the
// docs header stops being sticky because sticky elements live inside an
// overflow-clipped container.
const path = join(process.cwd(), "docs", "assets", "terminal.css");
return readFileSync(path, "utf8");
}
describe("docs terminal.css", () => {
test("keeps the docs header sticky (shell is sticky)", () => {
const css = readTerminalCss();
expect(css).toMatch(/\.shell\s*\{[^}]*position:\s*sticky;[^}]*top:\s*0;[^}]*\}/s);
});
test("does not rely on making body overflow visible", () => {
const css = readTerminalCss();
expect(css).not.toMatch(/body\s*\{[^}]*overflow-x:\s*visible;[^}]*\}/s);
});
test("does not make the terminal frame overflow visible (can break layout)", () => {
const css = readTerminalCss();
expect(css).not.toMatch(/\.shell__frame\s*\{[^}]*overflow:\s*visible;[^}]*\}/s);
});
});