@aparte/core 0.7.0 → 0.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.css CHANGED
@@ -299,6 +299,12 @@
299
299
 
300
300
  /* Viewport */
301
301
  --aparte-viewport-padding: 16px;
302
+ /* Breathing room UNDER the composer, so it does not sit flush against the bottom
303
+ edge of a full-height chat. Same 16px the viewport already puts between the last
304
+ bubble and the composer — this restores the symmetry rather than inventing a
305
+ value. Set it to 0 for a flush composer (a full-bleed mobile shell with a docked
306
+ keyboard is the legitimate case). */
307
+ --aparte-chat-bottom-gap: var(--aparte-space-8, 16px);
302
308
 
303
309
  /* Content */
304
310
  --aparte-content-line-height: var(--aparte-line-height-loose, 1.7);
@@ -435,6 +441,12 @@ aparte-chat,
435
441
  height: 100%;
436
442
  width: 100%;
437
443
  overflow: hidden;
444
+ /* The composer used to touch the bottom edge as soon as a conversation started: the
445
+ viewport gives 16px above the composer and there was nothing below it. An app
446
+ cannot fix this from outside without padding the container, which also shrinks the
447
+ scroll area — so the transcript would stop before the edge instead of scrolling to
448
+ it. That makes the gap ours. */
449
+ padding-block-end: var(--aparte-chat-bottom-gap, var(--aparte-space-8, 16px));
438
450
  }
439
451
 
440
452
  /* The viewport takes the space left by the composer; the standalone height:100%
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aparte/core",
3
- "version": "0.7.0",
3
+ "version": "0.7.1",
4
4
  "description": "High-performance AI conversation engine - Zero-dependency Web Components",
5
5
  "type": "module",
6
6
  "//sideEffects": "The BROWSER entry defines the custom elements and imports CSS at module scope, so it must never be tree-shaken; the Node entry (`index.node`) and every other module are pure. Listing them explicitly is what lets a bundler drop the rest — the whole package was implicitly side-effectful before, the only one of the 14 without this field.",