@rio-m3e/styles 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rio-m3e/styles",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Framework-agnostic component styles for Rio",
   "license": "Apache-2.0",
   "author": "LegenLee",

package/src/base/shape-morph.css

@@ -1,9 +1,16 @@
 /*
  * Shape morphing, driven by `attachShapeMorph` from `@rio-m3e/core`. A component sets
- * `--rio-shape-morph-target` to the corner radius it wants in each state, and sets
- * `border-radius` to the same value, so it still works without JavaScript. The primitive reads
- * the target in px, which needs the registration below, and animates the inline radius with a
- * spring. It marks the element with `data-shape-morph`.
+ * `--rio-shape-morph-target` to the corner radius it wants in each state. The primitive reads
+ * the targets in px, which needs the registrations below, and springs the inline radii toward
+ * them. It marks the element with `data-shape-morph`.
+ *
+ * Shapes whose sides differ set `--rio-shape-morph-start-target` and `--rio-shape-morph-end-target`
+ * (the corners at the start and end of the line, in the writing direction) with any class or
+ * attribute selector; otherwise both follow `--rio-shape-morph-target`.
+ *
+ * The component also draws its corners from the per-side targets, so it still works without
+ * JavaScript, and lists both targets in its `transition` as `1ms step-end`, so the springs see
+ * them change (see "Primitives" in docs/conventions.md, and button.css).
  */
 
 @property --rio-shape-morph-target {
@@ -11,3 +18,20 @@
   inherits: false;
   initial-value: 0px;
 }
+
+@property --rio-shape-morph-start-target {
+  syntax: '<length>';
+  inherits: false;
+  initial-value: 0px;
+}
+
+@property --rio-shape-morph-end-target {
+  syntax: '<length>';
+  inherits: false;
+  initial-value: 0px;
+}
+
+:where([data-shape-morph]) {
+  --rio-shape-morph-start-target: var(--rio-shape-morph-target);
+  --rio-shape-morph-end-target: var(--rio-shape-morph-target);
+}

package/src/base/state-layer.css

@@ -41,7 +41,8 @@
   opacity: var(--rio-state-pressed-state-layer-opacity);
 }
 
-.rio-state-layer[data-dragged]::before {
+/* `attachDrag` from `@rio-m3e/core` marks an element with `data-dragging` while it moves. */
+.rio-state-layer[data-dragging]::before {
   opacity: var(--rio-state-dragged-state-layer-opacity);
 }
 

package/src/button-group.css

@@ -0,0 +1,98 @@
+/*
+ * M3E button group: a row of buttons and icon buttons (`button.css`, `icon-button.css`). The group
+ * has no color of its own. It carries `data-variant`, `data-size`, and `data-shape`, which
+ * `createButtonGroup` from `@rio-m3e/core` sets; the size and shape reach the buttons through the
+ * framework adapter, so these rules read the buttons' own `data-size` and `data-shape`.
+ *
+ * Values come from Material Web's component tokens (`_md-comp-button-group-standard-*.scss` and
+ * `_md-comp-button-group-connected-*.scss`, Material 3 v34.0.21). The pressed button's width
+ * change in standard groups is JavaScript (`attachButtonGroup` from `@rio-m3e/core`).
+ */
+
+.rio-button-group {
+  /* Standard, small */
+  --_between: 12px;
+
+  display: inline-flex;
+  align-items: center;
+  gap: var(--_between);
+  vertical-align: middle;
+}
+
+/* Standard: the space keeps every button's 48px target clear of its neighbors' */
+
+.rio-button-group:where([data-size='xsmall']) {
+  --_between: 18px;
+}
+
+.rio-button-group:where([data-size='medium'], [data-size='large'], [data-size='xlarge']) {
+  --_between: 8px;
+}
+
+/*
+ * Connected: 2px apart, and as wide as the space it's given, shared equally by its buttons. The
+ * ends of the row keep the group's shape; the facing corners are smaller, tighten when pressed,
+ * and open up fully when the button is selected. Each button springs its two sides separately
+ * (see base/shape-morph.css).
+ */
+
+.rio-button-group:where([data-variant='connected']) {
+  --_between: 2px;
+
+  display: flex;
+}
+
+.rio-button-group[data-variant='connected'] > .rio-button {
+  /* Small, medium, and extra small */
+  --_inner: var(--rio-shape-corner-small);
+  --_inner-pressed: var(--rio-shape-corner-extra-small);
+  /* Corners that face another button, and corners at the ends of the row */
+  --_inner-now: var(--_inner);
+  --_outer: var(--_round);
+  --_start: var(--_inner-now);
+  --_end: var(--_inner-now);
+
+  flex: 1 1 0;
+  /* The corners show these targets (button.css). */
+  --rio-shape-morph-start-target: var(--_start);
+  --rio-shape-morph-end-target: var(--_end);
+}
+
+.rio-button-group[data-variant='connected'] > .rio-button:where([data-size='large']) {
+  --_inner: var(--rio-shape-corner-large);
+  --_inner-pressed: var(--rio-shape-corner-medium);
+}
+
+.rio-button-group[data-variant='connected'] > .rio-button:where([data-size='xlarge']) {
+  --_inner: var(--rio-shape-corner-large-increased);
+  --_inner-pressed: var(--rio-shape-corner-large);
+}
+
+/* A square group's ends use the same radius as its facing corners. */
+.rio-button-group[data-variant='connected'] > .rio-button[data-shape='square'] {
+  --_outer: var(--_inner);
+}
+
+.rio-button-group[data-variant='connected'] > .rio-button:first-child {
+  --_start: var(--_outer);
+}
+
+.rio-button-group[data-variant='connected'] > .rio-button:last-child {
+  --_end: var(--_outer);
+}
+
+.rio-button-group[data-variant='connected'] > .rio-button[data-selected='true'] {
+  --_inner-now: var(--_round);
+  --_outer: var(--_round);
+}
+
+/* After selected, so a pressed selected button still tightens its facing corners */
+.rio-button-group[data-variant='connected'] > .rio-button[data-pressed] {
+  --_inner-now: var(--_inner-pressed);
+}
+
+/* Extra small and small icon buttons keep a 48px minimum width, matching their target. */
+.rio-button-group[data-variant='connected']
+  > .rio-icon-button:where([data-size='xsmall'], [data-size='small']) {
+  min-inline-size: 48px;
+}

package/src/button.css

@@ -42,9 +42,19 @@
   block-size: var(--_height);
   padding-inline: var(--_padding);
   border: var(--_outline-width) solid var(--_outline);
-  /* The shape-morph primitive springs the inline radius toward this target. */
+  /*
+   * The shape-morph primitive springs the inline radii toward these targets. The corners show the
+   * targets, not `--_radius`: when the state changes, a target holds its old value until the
+   * spring takes over (see `transition` below), so the new shape doesn't flash first. Button
+   * groups and split buttons set the per-side targets.
+   */
   --rio-shape-morph-target: var(--_radius);
-  border-radius: var(--_radius);
+  --rio-shape-morph-start-target: var(--rio-shape-morph-target);
+  --rio-shape-morph-end-target: var(--rio-shape-morph-target);
+  border-start-start-radius: var(--rio-shape-morph-start-target);
+  border-end-start-radius: var(--rio-shape-morph-start-target);
+  border-start-end-radius: var(--rio-shape-morph-end-target);
+  border-end-end-radius: var(--rio-shape-morph-end-target);
   background-color: var(--_container);
   box-shadow: var(--_elevation);
   color: var(--_content);
@@ -54,11 +64,20 @@
   vertical-align: middle;
   cursor: pointer;
   user-select: none;
-  /* No border-radius transition: corners move with the fast-spatial spring (see base/shape-morph.css). */
+  /*
+   * No border-radius transition: corners move with the fast-spatial spring (see
+   * base/shape-morph.css). The spring targets get an instant transition instead, which is how the
+   * spring sees them change (core's spring-property). `--rio-spring-targets` is public: an app
+   * that sets its own `transition` on a button keeps the morphing by including it, and
+   * stylesheets that spring more targets on a button extend it.
+   */
+  --rio-spring-targets:
+    --rio-shape-morph-start-target 1ms step-end, --rio-shape-morph-end-target 1ms step-end;
   transition:
     background-color var(--rio-motion-fast-effects),
     color var(--rio-motion-fast-effects),
-    box-shadow var(--rio-motion-fast-effects);
+    box-shadow var(--rio-motion-fast-effects),
+    var(--rio-spring-targets);
 }
 
 /* Sizes */
@@ -189,7 +208,6 @@
 
 .rio-button[data-pressed] {
   --rio-shape-morph-target: var(--_pressed);
-  border-radius: var(--_pressed);
   box-shadow: var(--_elevation);
 }
 
@@ -237,8 +255,10 @@
 /* Extra small and small buttons are shorter than the spec's 48px minimum target. */
 .rio-button__touch {
   position: absolute;
-  inset-block-start: 50%;
-  inset-inline-start: 50%;
+  /* Physical, like `translate`: a logical start would flip in right-to-left layouts and push the
+     target off the button. */
+  top: 50%;
+  left: 50%;
   inline-size: max(100%, 48px);
   block-size: max(100%, 48px);
   translate: -50% -50%;

package/src/split-button.css

@@ -0,0 +1,185 @@
+/*
+ * M3E split button: a leading button and a trailing menu button, 2px apart. Both are buttons
+ * (`button.css`), so they keep the button's sizes, colors, elevation, disabled rules, state layer,
+ * ripple, and touch target. This file adds what differs: the paddings, the trailing button's
+ * width, the corners, and the menu icon. `createSplitButton` from `@rio-m3e/core` sets the
+ * attributes, and the buttons carry `data-size`, `data-variant`, and, on the trailing button,
+ * `data-open`.
+ *
+ * Values come from Material Web's component tokens (`_md-comp-split-button-*.scss`, Material 3
+ * v34.0.21). The menu icon's offset comes from the spec page's measurements, and its direction
+ * (toward the start) from the M3 Design Kit.
+ */
+
+@property --rio-split-button-menu-turn-target {
+  syntax: '<angle>';
+  inherits: false;
+  initial-value: 0deg;
+}
+
+@property --rio-split-button-menu-shift-target {
+  syntax: '<length>';
+  inherits: false;
+  initial-value: 0px;
+}
+
+.rio-split-button {
+  display: inline-flex;
+  align-items: center;
+  gap: 2px;
+  vertical-align: middle;
+}
+
+/*
+ * Both buttons: the corners at the ends of the split button are round, and the facing ones are
+ * small. Hovering, focusing, or pressing a button rounds its facing corners more, and opening the
+ * menu rounds the trailing button fully. Each side springs on its own (see base/shape-morph.css).
+ */
+.rio-split-button > .rio-button {
+  /* Small */
+  --_lead-start: 16px;
+  --_lead-end: 12px;
+  --_menu-size: 22px;
+  --_menu-padding: 13px;
+  --_menu-offset: 1px;
+  --_inner: var(--rio-shape-corner-extra-small);
+  --_inner-active: var(--rio-shape-corner-medium);
+
+  --_inner-now: var(--_inner);
+}
+
+/*
+ * `[data-variant]` is always there; it lifts this above button.css's per-side defaults in any
+ * order. The corners show these targets (button.css).
+ */
+.rio-split-button > .rio-button[data-variant] {
+  --rio-shape-morph-start-target: var(--_start);
+  --rio-shape-morph-end-target: var(--_end);
+}
+
+.rio-split-button > .rio-button:where([data-size='xsmall']) {
+  --_lead-start: 12px;
+  --_lead-end: 10px;
+  --_inner-active: var(--rio-shape-corner-small);
+}
+
+.rio-split-button > .rio-button:where([data-size='medium']) {
+  --_lead-start: 24px;
+  --_lead-end: 24px;
+  --_menu-size: 26px;
+  --_menu-padding: 15px;
+  --_menu-offset: 2px;
+}
+
+.rio-split-button > .rio-button:where([data-size='large']) {
+  --_lead-start: 48px;
+  --_lead-end: 48px;
+  --_menu-size: 38px;
+  --_menu-padding: 29px;
+  --_menu-offset: 3px;
+  --_inner: var(--rio-shape-corner-small);
+  --_inner-active: var(--rio-shape-corner-large-increased);
+}
+
+.rio-split-button > .rio-button:where([data-size='xlarge']) {
+  --_lead-start: 64px;
+  --_lead-end: 64px;
+  --_menu-size: 50px;
+  --_menu-padding: 43px;
+  --_menu-offset: 6px;
+  --_inner: var(--rio-shape-corner-medium);
+  --_inner-active: var(--rio-shape-corner-large-increased);
+}
+
+@media (hover: hover) {
+  .rio-split-button > .rio-button:hover {
+    --_inner-now: var(--_inner-active);
+  }
+}
+
+.rio-split-button > .rio-button:is(:focus-visible, [data-pressed]) {
+  --_inner-now: var(--_inner-active);
+}
+
+/*
+ * Disabled buttons don't react, so their corners stay put. Being open still shows (that rule comes
+ * later): a disabled toggle button keeps its selected shape too.
+ */
+.rio-split-button > .rio-button:is(:disabled, [aria-disabled='true']) {
+  --_inner-now: var(--_inner);
+}
+
+/* Leading button */
+
+.rio-split-button > .rio-split-button__leading {
+  --_start: var(--_round);
+  --_end: var(--_inner-now);
+
+  padding-inline: var(--_lead-start) var(--_lead-end);
+}
+
+/* Trailing button: a square, or 48px wide when shorter, with the menu icon in it */
+
+.rio-split-button > .rio-split-button__trailing {
+  --_start: var(--_inner-now);
+  --_end: var(--_round);
+  --rio-split-button-menu-shift-target: var(--_menu-offset);
+  /* Toward the start: left, or right in right-to-left layouts */
+  --_start-sign: -1;
+
+  inline-size: calc(var(--_menu-size) + 2 * var(--_menu-padding));
+  padding: 0;
+}
+
+.rio-split-button > .rio-split-button__trailing:dir(rtl) {
+  --_start-sign: 1;
+}
+
+/*
+ * Open: fully round, with the icon centered and turned half a circle, its point swinging through
+ * the start side, toward the leading button. The color doesn't change; a state layer shows
+ * instead, at the pressed opacity.
+ */
+.rio-split-button > .rio-split-button__trailing[data-open] {
+  --_inner-now: var(--_round);
+  --rio-split-button-menu-turn-target: 180deg;
+  --rio-split-button-menu-shift-target: 0px;
+}
+
+.rio-split-button > .rio-split-button__trailing[data-open]:dir(rtl) {
+  --rio-split-button-menu-turn-target: -180deg;
+}
+
+.rio-split-button
+  > .rio-split-button__trailing[data-open]:not(:disabled, [aria-disabled='true'])::before {
+  opacity: var(--rio-state-pressed-state-layer-opacity);
+}
+
+/*
+ * The springs in `attachSplitButtonMenuIcon` write `--_menu-turn` and `--_menu-shift` while they
+ * move; at rest the targets apply. The targets are registered and don't inherit, so they are
+ * passed down through these.
+ */
+.rio-split-button > .rio-split-button__trailing {
+  --_menu-turn-rest: var(--rio-split-button-menu-turn-target);
+  --_menu-shift-rest: var(--rio-split-button-menu-shift-target);
+  /* The button's spring targets (button.css), and the menu icon's. */
+  --rio-spring-targets:
+    --rio-shape-morph-start-target 1ms step-end, --rio-shape-morph-end-target 1ms step-end,
+    --rio-split-button-menu-turn-target 1ms step-end,
+    --rio-split-button-menu-shift-target 1ms step-end;
+}
+
+.rio-split-button__menu-icon {
+  display: inline-flex;
+  flex: none;
+  inline-size: var(--_menu-size);
+  block-size: var(--_menu-size);
+  rotate: var(--_menu-turn, var(--_menu-turn-rest));
+  translate: calc(var(--_menu-shift, var(--_menu-shift-rest)) * var(--_start-sign)) 0;
+}
+
+.rio-split-button__menu-icon > :is(svg, img) {
+  inline-size: 100%;
+  block-size: 100%;
+}

package/src/switch.css

@@ -4,7 +4,8 @@
  * Values come from Material Web's component tokens (`_md-comp-switch.scss`, Material 3 v34.0.21),
  * which match the spec's measurements table. The handle's center and size are declared as targets
  * for each state; `attachSwitchHandle` from `@rio-m3e/core` springs `--_handle-x` and
- * `--_handle-size` toward them. Without JavaScript the handle simply jumps.
+ * `--_handle-size` toward them, which show the targets at rest. The targets get an instant
+ * transition so the springs see them change. Without JavaScript the handle simply jumps.
  *
  * The root carries `data-selected`, plus `data-pressed` (from the ripple), `data-dragging` (from
  * the drag), and `data-icon` when the handle shows an icon. State rules sit inside `:where()` so
@@ -72,9 +73,14 @@
   /* Horizontal drags belong to the handle; vertical ones still scroll the page. */
   touch-action: pan-y;
   -webkit-tap-highlight-color: transparent;
+  /* The handle's spring targets get an instant transition, which is how the springs see them
+     change (core's spring-property). Public, as on the button (button.css). */
+  --rio-spring-targets:
+    --rio-switch-handle-x-target 1ms step-end, --rio-switch-handle-size-target 1ms step-end;
   transition:
     background-color var(--rio-motion-fast-effects),
-    border-color var(--rio-motion-fast-effects);
+    border-color var(--rio-motion-fast-effects),
+    var(--rio-spring-targets);
 }
 
 /* States */
@@ -196,8 +202,10 @@
 /* The track is 32px tall, below the spec's 48px minimum target. */
 .rio-switch__touch {
   position: absolute;
-  inset-block-start: 50%;
-  inset-inline-start: 50%;
+  /* Physical, like `translate`: a logical start would flip in right-to-left layouts and push the
+     target off the switch. */
+  top: 50%;
+  left: 50%;
   inline-size: max(100%, 48px);
   block-size: max(100%, 48px);
   translate: -50% -50%;