diff --git a/Cargo.lock b/Cargo.lock
index 369c59c..bb7e54d 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1382,7 +1382,7 @@ dependencies = [
 
 [[package]]
 name = "rs_maps"
-version = "0.0.3"
+version = "0.0.4"
 dependencies = [
  "anyhow",
  "argon2",
diff --git a/Cargo.toml b/Cargo.toml
index 4557655..958b9ea 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,7 +1,7 @@
 # Cargo.toml
 [package]
 name = "rs_maps"
-version = "0.0.3"
+version = "0.0.4"
 edition = "2021"
 
 [dependencies]
diff --git a/frontend/style.css b/frontend/style.css
index f3e8089..a0ae35d 100644
--- a/frontend/style.css
+++ b/frontend/style.css
@@ -201,7 +201,10 @@ button.link:hover { color: var(--paper); background: none; }
 .bar {
   position: absolute;
   top: 0; left: 0; right: 0;
-  z-index: 500;
+  /* Above .rail (500) so the account menu isn't painted behind the
+     Places/Routes tabs. .bar sets a stacking context, so raising .menu alone
+     would have no effect — the parent is what has to come up. */
+  z-index: 700;
   display: flex;
   align-items: center;
   gap: 10px;
@@ -210,6 +213,12 @@ button.link:hover { color: var(--paper); background: none; }
   padding-bottom: 22px;
 }
 
+/* The bar's gradient extends 22px past its contents. Now that it sits above
+   the rail, that transparent strip would intercept clicks meant for the tabs
+   beneath it, so the bar ignores pointer events and its children take them back. */
+.bar { pointer-events: none; }
+.bar > * { pointer-events: auto; }
+
 .search { display: flex; gap: 6px; flex: 1 1 auto; max-width: 420px; }
 .search input { margin-top: 0; background: var(--panel); }
 .search button { flex: none; background: var(--panel); border-color: var(--hair); }