@bytebrand/fe-ui-core-autobahn 1.0.115 → 1.0.116

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bytebrand/fe-ui-core-autobahn",
-  "version": "1.0.115",
+  "version": "1.0.116",
   "description": "auto.de md3 (Autobahn) design system — UI primitives, cards, chrome, VDP modules, theme CSS and locales. Ships raw TypeScript source (like fe-ui-core before it); each consumer's bundler compiles it.",
   "main": "index.ts",
   "license": "UNLICENSED",

package/theme/md3.css

@@ -5336,6 +5336,11 @@ line-height: 31px;
 .md3 .card-cta-row .mbtn { font-size: 12.5px; padding: 0 10px; gap: 5px; min-width: 0; }
 .md3 .card-cta-row .mbtn span, .md3 .card-cta-row .mbtn { overflow: hidden; text-overflow: ellipsis; }
 .md3 .card-cta-row .mbtn .lucide { width: 15px; height: 15px; flex: none; }
+/* the phone/"Rate anpassen" outlined buttons set their own explicit `border` (1.6px solid) inline —
+   .mbtn--outlined's inset box-shadow (the DEFAULT way that class draws its border everywhere else)
+   stacks on top of it as a second, slightly offset ring ("double border"). Suppress just the
+   shadow here; the real border keeps rendering from each button's own inline style. */
+.md3 .card-cta-row .mbtn--outlined { box-shadow: none; }
 /* muted buyer activity (#5) */
 .md3 .pp-activity {
   display: flex;
@@ -6767,16 +6772,30 @@ line-height: 31px;
   }
   .md3 .srp-bar {
     position: sticky;
-    /* was 64px (docked under the always-visible header) — now 0: once the header slides away
-       (autoHideOnScroll, TopBar.tsx) this bar takes its place at the very top instead of leaving
-       a gap, and sits flush under it again the moment the header slides back in. */
-    top: 0px;
+    /* default: docked directly under the always-visible header (its 64px height). Same 0.25s
+       duration as .topbar's own transform transition (below) — the header slides in/out over
+       0.25s, so this bar's top must animate in step with it, not jump instantly, or a gap (bar
+       already at 64px, header still sliding in) or an overlap (bar already at 0, header still
+       sliding out) flashes for that quarter-second. */
+    top: 64px;
+    transition: top 0.25s;
     z-index: 20;
     background: #fff;
     padding: 8px 0;
     margin: 0 0 8px;
     box-shadow: 0 6px 8px -8px rgba(0, 0, 0, 0.3);
   }
+  /* once the header slides away on scroll-down (autoHideOnScroll, TopBar.tsx adds
+     .topbar--hidden), this bar takes its place at the very top instead of leaving a 64px gap.
+     The header's box stays in the layout flow even while hidden (transform doesn't affect
+     `position: sticky`'s slot — see the .topbar--hidden rule above), so without this override
+     the bar's own sticky top would also need to jump — and it must jump BACK to 64px the moment
+     scroll-up brings the header back (topbar--hidden removed), or the reappearing header
+     (z-index 50) sticks at the same top:0 slot and paints over/hides this bar (z-index 20)
+     underneath it instead of sitting above it. */
+  .md3:has(.topbar--hidden) .srp-bar {
+    top: 0px;
+  }
   /* full-bleed white to the true viewport edges, WITHOUT moving .srp-bar's own text — it stays
      inside .srp-main's own side padding, this pseudo-element just paints white past it on both
      sides so no gap of page background shows while the bar is sticky. NOT a box-shadow spread
@@ -7327,7 +7346,7 @@ line-height: 31px;
    no separate per-element rule to keep in sync with this one. */
 @media (max-width: 600px) {
   .md3 .vdp-main {
-    padding: 0 10px 48px !important;
+    padding: 0 14px 48px !important;
   }
   .md3 .vdp-push-badges {
     gap: 6px;

package/ui/Dropdown.tsx

@@ -330,6 +330,15 @@ const Dropdown: React.FunctionComponent<DropdownProps> = ({
 
   const editing = searchable && open;
 
+  // Bug 53/37: "Rate bis" / "km bis" allow a hand-typed amount the preset rungs don't cover
+  // (allowCustomValue) — that typed number never matches any option label, so filteredOptions
+  // comes back empty and the popover would show "Keine Treffer", reading as "no cars match this"
+  // to the customer even though the typed value is perfectly valid input. Once there's an actual
+  // typed query with zero matches on an allowCustomValue field, suppress the popover entirely
+  // (not just the "Keine Treffer" row) — an empty floating box would be just as confusing. Plain
+  // (non-custom) searchable dropdowns, e.g. Make/Model, are unaffected and keep showing it.
+  const suppressEmptyMenu = allowCustomValue && searchable && query.trim() !== '' && filteredOptions.length === 0;
+
   // shared between the in-place popover and the menuPortal one — identical option list either way.
   const renderMenuList = () => (
     <ul
@@ -407,7 +416,7 @@ const Dropdown: React.FunctionComponent<DropdownProps> = ({
           <Icon name="chevron-down" cls="mselect-chev" />
         </button>
       )}
-      {open && (menuPortal && portalRoot
+      {open && !suppressEmptyMenu && (menuPortal && portalRoot
         ? ReactDOM.createPortal(
             <div
               ref={menuElRef}