bunnyquery 1.8.6 → 1.8.9

package/src/widget.css

@@ -757,7 +757,7 @@
     cursor: pointer;
     z-index: 1;
 }
-.bq-attach-btn:hover:not(:disabled) { color: var(--bq-main); }
+.bq-attach-btn:hover:not(:disabled) { color: var(--bq-main);transform: none; }
 .bq-attach-btn:disabled { opacity: 0.5; cursor: not-allowed; }
 .bq-attach-input { display: none; }
 .bq-input {
@@ -821,6 +821,40 @@
     pointer-events: none;
 }
 .bq-attachment.is-uploading > * { position: relative; z-index: 1; }
+/* The two indeterminate phases, both drawn as a barber pole over the full chip
+   because neither has a percentage to show (mirror of agent.vue):
+     is-preparing:  before the first byte-progress event, while get-signed-url
+                     is in flight. A bar at 0% here reads as a stalled upload.
+     is-finalizing: bytes done, post-upload work (signed url, src:: record,
+                     indexing dispatch) still running. A bar frozen at a solid
+                     100% reads as hung.
+   Between them the bar is determinate and driven by --att-progress. */
+.bq-attachment.is-preparing::before,
+.bq-attachment.is-finalizing::before {
+    width: 100%;
+    background: repeating-linear-gradient(
+        -45deg,
+        color-mix(in srgb, var(--bq-main) 22%, transparent) 0 8px,
+        color-mix(in srgb, var(--bq-main) 10%, transparent) 8px 16px
+    );
+    background-size: 22.6px 100%;
+    animation: bq-att-barber 0.8s linear infinite;
+    transition: none;
+}
+.bq-attachment.is-preparing .bq-attachment-meta::after,
+.bq-attachment.is-finalizing .bq-attachment-meta::after {
+    content: ".";
+    display: inline-block;
+    width: 1.1em;
+    text-align: left;
+    animation: bq-att-dots 1.2s steps(1) infinite;
+}
+@keyframes bq-att-barber { to { background-position: 22.6px 0; } }
+@keyframes bq-att-dots {
+    0%  { content: "."; }
+    33% { content: ".."; }
+    66% { content: "..."; }
+}
 .bq-attachment.is-error { border-color: var(--bq-danger); background: var(--bq-danger-bg); }
 .bq-attachment.is-error .bq-attachment-meta,
 .bq-attachment.is-error .bq-attachment-name { color: var(--bq-danger); }

package/styles/chat.css

@@ -28,6 +28,7 @@
 .bq-message.is-assistant { justify-content: flex-start; }
 
 .bq-bubble {
+    max-width: 100%;
     padding: 0.55rem 0.7rem;
     border: 1px solid var(--bq-line);
     white-space: pre-wrap;
@@ -222,6 +223,24 @@
    state does not know. A slow fade says "pending" without claiming progress. */
 .bq-index-group.is-resolving .bq-index-icon svg { animation: bq-index-fade 1.6s ease-in-out infinite; }
 @keyframes bq-index-fade { 0%, 100% { opacity: 1; } 50% { opacity: 0.35; } }
+/* Expand-triggered history fetch: spinning arrows in the row head while the
+   run's passes are being paged in. A SEPARATE element from the status icon on
+   purpose — the row keeps its verdict (green check, grey clock) and this only
+   says "fetching more detail about it", whatever that verdict is. */
+.bq-index-fetch {
+    width: 0.85rem;
+    height: 0.85rem;
+    flex: none;
+    margin-left: 0.35rem;
+    color: var(--bq-muted);
+    display: inline-flex;
+}
+.bq-index-fetch svg { width: 100%; height: 100%; display: block; animation: bq-index-spin 1.1s linear infinite; }
+/* The in-row loading note under an OPEN row while its passes stream in. */
+.bq-index-note .bq-loader { margin-left: 0.15rem; }
+@media (prefers-reduced-motion: reduce) {
+    .bq-index-fetch svg { animation-duration: 3s; }
+}
 @media (prefers-reduced-motion: reduce) {
     .bq-index-group.is-active .bq-index-icon svg { animation-duration: 3s; }
     /* A fade has no end state to settle on, so it stops rather than slows. */
@@ -259,7 +278,7 @@
     line-height: 1.3;
     letter-spacing: 0.02em;
     cursor: pointer;
-    box-shadow: none;
+    box-shadow: 2px 2px rgba(0, 0, 0, 0.12);
     opacity: 0.8;
 }
 .bq-index-cancel:hover:not(.is-disabled) { background: var(--bq-warning-bg); color: var(--bq-warning); opacity: 1; }
@@ -313,10 +332,12 @@
     font-size: 0.78rem;
     color: var(--bq-muted);
 }
-/* An open row animates for as long as the file is indexing, which can be minutes.
-   Readers who ask for less motion get the static end state. */
+/* An open row animates for as long as the file is indexing, which can be
+   minutes, and the user-side drafting bubble animates for as long as a draft
+   sits in the composer. Readers who ask for less motion get the static dots. */
 @media (prefers-reduced-motion: reduce) {
-    .bq-index-tail .bq-loader::after { animation: none; content: '...'; }
+    .bq-index-tail .bq-loader::after,
+    .bq-user-drafting .bq-loader::after { animation: none; content: '...'; }
 }
 .bq-index-note {
     padding: 0 0.6rem 0.45rem;
@@ -482,3 +503,38 @@
 .bq-md strong { font-weight: 600; }
 .bq-md em { font-style: italic; }
 .bq-md del { text-decoration: line-through; }
+/* ---- host-page insulation -------------------------------------------------*/
+/* The markdown above renders into whatever page this chat sits in: the admin
+   app with its own global stylesheet, or - for the embedded widget - a HOST
+   page with arbitrary CSS. Element-level globals leak straight into it, and
+   form controls are the class nothing above styles on purpose: the admin app
+   styles every <input> as a 3rem bordered mono text field, which turned a GFM
+   task-list checkbox into a giant text box. `revert` rolls each property back
+   to the BROWSER default (as if no author CSS existed), which is the honest
+   baseline for a control the markdown produced; `initial`/`unset` would
+   instead strip even the user-agent's own control styling. */
+.bq-md input,
+.bq-md select,
+.bq-md textarea,
+.bq-md button {
+    all: revert;
+}
+/* GFM task list: `- [x] item` renders as a disabled checkbox in the list item.
+   Re-state the little we DO want on top of the revert: sit on the text
+   baseline with a small gap, brand accent. The geometry (width/height/
+   min-height/padding) is pinned explicitly, at higher specificity than the
+   revert rule, so a host sheet whose input rules are more specific than
+   `.bq-md input` still loses the properties that actually break layout. */
+.bq-md input[type="checkbox"] {
+    width: auto;
+    height: auto;
+    min-height: 0;
+    padding: 0;
+    margin: 0 0.4em 0.1em 0;
+    vertical-align: middle;
+    accent-color: var(--bq-main);
+}
+/* GitHub-style: a task-list item shows the checkbox INSTEAD of a bullet, not
+   next to one. :has() is safe here - every supported browser ships it, and a
+   miss only means a redundant bullet. */
+.bq-md li:has(> input[type="checkbox"]:first-child) { list-style: none; }