PluginProbe
OpenStation: Desktop Windows, Dock & Virtual Desktops for WP Admin / 1.1.13
OpenStation: Desktop Windows, Dock & Virtual Desktops for WP Admin v1.1.13
1.1.13 1.1.12 1.1.11 1.1.10 1.1.9 1.1.8 1.1.7 1.1.6 1.1.5 1.1.4 1.1.3 1.1.2 1.1.1 1.1.0 1.0.1 1.0.0 0.9.8 0.9.7 0.9.6 0.9.4 0.9.5 0.9.3 0.9.2 0.9.1 0.9.0 All 37 releases
← All changes | assets/css/desktop.css +1451 -366 0.9.2 → 1.1.13 View file →
@@ -1,8 +1,8 @@
1 1 /**
2 - * Desktop Mode — Shell Layout.
2 + * OpenStation — Shell Layout.
3 3 *
4 - * When desktop mode is active, the classic admin chrome still renders
4 + * When OpenStation is active, the classic admin chrome still renders
5 5 * server-side (for hook compatibility) but is hidden with CSS. The
6 6 * plugin-injected shell floats above it, positioned just below the
7 7 * fixed admin bar, covering the rest of the viewport.
8 8 *
@@ -8,17 +8,57 @@
8 8 *
9 9 * @since 0.1.0
10 10 */
11 11
12 -/* Solid backdrop behind the shell. */
13 -body.desktop-mode-active {
14 - background: #1d2327;
12 +/*
13 + * Solid backdrop behind the shell. Reads the backstop token rather
14 + * than a literal so it moves with the desk: this is the colour a
15 + * dropped frame shows, and it has to be the same one the shell paints
16 + * or the seam is visible at exactly the wrong moment.
17 + */
18 +body.os-active {
19 + background: var( --os-backstop, #1d2327 );
15 20 overflow: hidden;
16 21 }
17 22
18 23 /*
19 - * Cursor policy — default arrow everywhere in desktop mode.
24 + * Text selection.
20 25 *
26 + * The shell had no ::selection rule at all, so every selection in it
27 + * was the browser default — a colour chosen for a white page, landing
28 + * on a near-black one. In Chrome that is a dark translucent blue over
29 + * Obsidian, which is roughly 1.3:1 against the surface and leaves the
30 + * selected text at a contrast the UA never checked, because the UA
31 + * assumed a light background. Dragging across a paragraph produced no
32 + * visible change at all on some displays.
33 + *
34 + * Both halves are set on purpose. `background` alone is the common
35 + * half-fix: the UA then keeps its own selected-text colour, which is
36 + * frequently forced to black and lands on this violet at ~2:1.
37 + *
38 + * Scoped to the shell document. `variables.css` is a dependency of
39 + * `chromeless.css` and so loads inside every iframe window, but this
40 + * file does not — a wp-admin page in a window keeps the selection
41 + * colour it has outside one, which is the same promise the palette
42 + * makes about everything else.
43 + *
44 + * `::-moz-selection` is a separate rule rather than a second selector
45 + * on this one: an unrecognised pseudo-element invalidates the entire
46 + * selector list, so pairing them would leave Chrome unstyled too.
47 + */
48 +body.os-active ::selection {
49 + background: var( --os-ui-selection-bg, rgba( 159, 152, 255, 0.6 ) );
50 + color: var( --os-ui-selection-fg, #fffbff );
51 +}
52 +
53 +body.os-active ::-moz-selection {
54 + background: var( --os-ui-selection-bg, rgba( 159, 152, 255, 0.6 ) );
55 + color: var( --os-ui-selection-fg, #fffbff );
56 +}
57 +
58 +/*
59 + * Cursor policy — default arrow everywhere in OpenStation.
60 + *
21 61 * Per user preference (since 0.20.0): no hand/pointer/grab/grabbing/
22 62 * copy/no-drop cursors on icons, tiles, dock items, dock peek,
23 63 * window chrome, or any other clickable surface. The default arrow
24 64 * is the only "neutral" cursor we render.
@@ -38,46 +78,46 @@
38 78 * drag-state declarations elsewhere in the codebase have the same or
39 79 * higher specificity. The resize-handle exceptions use `!important`
40 80 * for the same reason.
41 81 *
42 - * Shadow-DOM web components (`wpd-*`) define their own cursors
82 + * Shadow-DOM web components (`os-*`) define their own cursors
43 83 * inside their shadow trees; those internal rules win regardless of
44 84 * what we set on the host. Anything visible on the desktop shell
45 85 * (light DOM) is covered by this policy.
46 86 */
47 -body.desktop-mode-active,
48 -body.desktop-mode-active * {
87 +body.os-active,
88 +body.os-active * {
49 89 cursor: default !important;
50 90 }
51 91
52 -body.desktop-mode-active input:not([type="checkbox"]):not([type="radio"]):not([type="range"]):not([type="color"]):not([type="file"]):not([type="button"]):not([type="submit"]):not([type="reset"]):not([type="image"]),
53 -body.desktop-mode-active textarea,
54 -body.desktop-mode-active [contenteditable=""],
55 -body.desktop-mode-active [contenteditable="true"] {
92 +body.os-active input:not([type="checkbox"]):not([type="radio"]):not([type="range"]):not([type="color"]):not([type="file"]):not([type="button"]):not([type="submit"]):not([type="reset"]):not([type="image"]),
93 +body.os-active textarea,
94 +body.os-active [contenteditable=""],
95 +body.os-active [contenteditable="true"] {
56 96 cursor: text !important;
57 97 }
58 98
59 -body.desktop-mode-active .desktop-mode-window__resize-handle--se,
60 -body.desktop-mode-active .desktop-mode-window__resize-handle--nw,
61 -body.desktop-mode-active .desktop-mode-widgets__resize--se,
62 -body.desktop-mode-active .desktop-mode-widgets__resize--nw {
99 +body.os-active .os-window__resize-handle--se,
100 +body.os-active .os-window__resize-handle--nw,
101 +body.os-active .os-widgets__resize--se,
102 +body.os-active .os-widgets__resize--nw {
63 103 cursor: nwse-resize !important;
64 104 }
65 105
66 -body.desktop-mode-active .desktop-mode-window__resize-handle--sw,
67 -body.desktop-mode-active .desktop-mode-window__resize-handle--ne,
68 -body.desktop-mode-active .desktop-mode-widgets__resize--sw,
69 -body.desktop-mode-active .desktop-mode-widgets__resize--ne {
106 +body.os-active .os-window__resize-handle--sw,
107 +body.os-active .os-window__resize-handle--ne,
108 +body.os-active .os-widgets__resize--sw,
109 +body.os-active .os-widgets__resize--ne {
70 110 cursor: nesw-resize !important;
71 111 }
72 112
73 -body.desktop-mode-active .desktop-mode-widgets__resize--n,
74 -body.desktop-mode-active .desktop-mode-widgets__resize--s {
113 +body.os-active .os-widgets__resize--n,
114 +body.os-active .os-widgets__resize--s {
75 115 cursor: ns-resize !important;
76 116 }
77 117
78 -body.desktop-mode-active .desktop-mode-widgets__resize--e,
79 -body.desktop-mode-active .desktop-mode-widgets__resize--w {
118 +body.os-active .os-widgets__resize--e,
119 +body.os-active .os-widgets__resize--w {
80 120 cursor: ew-resize !important;
81 121 }
82 122
83 123 /*
@@ -86,19 +126,19 @@
86 126 * The markup still exists in the DOM so server-side action hooks that
87 127 * target these regions (admin_notices, in_admin_footer, etc.) continue
88 128 * to fire — we just take them out of the visual flow.
89 129 */
90 -body.desktop-mode-active #adminmenuwrap,
91 -body.desktop-mode-active #adminmenuback,
92 -body.desktop-mode-active #wpbody,
93 -body.desktop-mode-active #wpfooter,
94 -body.desktop-mode-active .wp-responsive-toggle,
95 -body.desktop-mode-active #collapse-menu {
130 +body.os-active #adminmenuwrap,
131 +body.os-active #adminmenuback,
132 +body.os-active #wpbody,
133 +body.os-active #wpfooter,
134 +body.os-active .wp-responsive-toggle,
135 +body.os-active #collapse-menu {
96 136 display: none !important;
97 137 }
98 138
99 139 /*
100 - * The admin bar is the ONLY escape hatch in desktop mode — it hosts the
140 + * The admin bar is the ONLY escape hatch in OpenStation — it hosts the
101 141 * "Switch to Classic Admin" toggle. Any plugin CSS, Gutenberg state,
102 142 * user preference, or stray `display:none` that hides it would strand
103 143 * the user inside the shell with no way out. Hard-pin it visible.
104 144 *
@@ -105,9 +145,9 @@
105 145 * The exception: while a window is in immersive fullscreen, we *want*
106 146 * the bar hidden (macOS convention). That rule lives below and wins on
107 147 * specificity because it also targets #wpadminbar under a body class.
108 148 */
109 -body.desktop-mode-active #wpadminbar {
149 +body.os-active #wpadminbar {
110 150 display: block !important;
111 151 visibility: visible !important;
112 152 opacity: 1 !important;
113 153 position: fixed !important;
@@ -116,8 +156,314 @@
116 156 inset-inline-end: 0 !important;
117 157 }
118 158
119 159 /*
160 + * No top-level item may be taller than the bar.
161 + *
162 + * Core lays the two item groups out as floats, and a float that
163 + * overflows the 32px bar overflows invisibly. A host may lay a group
164 + * out as a flex row instead — WordPress.com's Debug Bar does, to
165 + * order its own item first — and then every item stretches to the
166 + * tallest one and the group's background paints the difference under
167 + * the windows' title bars. Our own items were that tallest one once
168 + * (an `inline-flex` item on a 32px line box grew to 37px; fixed at
169 + * the source in `includes/admin-bar.php`), but any item from any
170 + * plugin can be, so the cap lives here: the bar's own height token,
171 + * which is also the 46px mobile bar. Submenus are absolutely
172 + * positioned and unaffected.
173 + */
174 +body.os-active #wpadminbar .ab-top-menu > li {
175 + max-height: var(--wp-admin--admin-bar--height, 32px);
176 +}
177 +
178 +/*
179 + * Admin-bar presentation modes — OS Settings → Appearance → Admin bar,
180 + * persisted as `adminBarMode` and emitted as a
181 + * `os-admin-bar-<mode>` body class by PHP on first paint and
182 + * re-written by the shell's apply pass on every change.
183 + *
184 + * `static` is the absence of rules: the pin above stands and the shell
185 + * starts below the bar. The two modes below both take the bar out of
186 + * the shell's way, so the shell reclaims the full viewport in each.
187 + *
188 + * Every selector here carries two body classes, so it outranks the
189 + * one-class pin rule above on specificity; the one property the pin
190 + * marks `!important` (`inset-block-start`) is re-declared `!important`
191 + * where a mode moves the bar, and wins the same way.
192 + */
193 +
194 +/*
195 + * Dynamic — the bar parks off the top edge leaving a peek strip, and
196 + * slides back in when the pointer reaches the top of the viewport or
197 + * something inside it takes keyboard focus. The classic Windows
198 + * auto-hide taskbar.
199 + *
200 + * It parks by moving its `inset-block-start`, NOT by a `transform`,
201 + * and that is load-bearing. A transformed element becomes the
202 + * containing block for every `position: fixed` descendant, and the
203 + * bar has descendants like that which it does not own: the
204 + * WordPress.com notifications panel is `position: fixed; top: 32px;
205 + * bottom: 0` inside `#wp-admin-bar-notes`. Measured against a
206 + * transformed 32px bar instead of the viewport, that panel computes to
207 + * zero height — the button "did nothing" in this mode and worked in
208 + * `static`. `translate`, `filter`, `perspective`, `contain` and
209 + * `will-change: transform` all create the same containing block;
210 + * `tests/vitest/admin-bar-dynamic.test.ts` keeps every one of them off
211 + * this rule. Moving `inset-block-start` hit-tests the same way — the
212 + * part above the viewport is simply outside it — so what catches the
213 + * pointer is still only the peek strip plus the reveal zone below.
214 + *
215 + * The pin above sets `inset-block-start: 0 !important`; these carry
216 + * `!important` too and win on specificity. The bar's height is Core's
217 + * own token, so the parked offset follows the 46px mobile bar as well.
218 + */
219 +body.os-active.os-admin-bar-dynamic #wpadminbar {
220 + /* One number for the slide; the reveal zone below waits on it. */
221 + --os-admin-bar-slide: 180ms;
222 + inset-block-start: calc(
223 + var(--os-admin-bar-peek, 4px) - var(--wp-admin--admin-bar--height, 32px)
224 + ) !important;
225 + transition: inset-block-start var(--os-admin-bar-slide, 180ms) ease;
226 +}
227 +
228 +body.os-active.os-admin-bar-dynamic #wpadminbar:hover,
229 +body.os-active.os-admin-bar-dynamic #wpadminbar:focus-within,
230 +body.os-active.os-admin-bar-dynamic #wpadminbar:active {
231 + inset-block-start: 0 !important;
232 +}
233 +
234 +/*
235 + * Reveal zone — an invisible extension of the bar's hit area, hanging
236 + * below the parked peek strip.
237 + *
238 + * Hovering a pseudo-element counts as hovering its originating
239 + * element, so this widens what `:hover` above responds to WITHOUT
240 + * widening the visible seam. The two wants are genuinely different:
241 + * the seam should be a hairline, the target should be forgiving, and
242 + * `--os-admin-bar-peek` alone can't be both.
243 + *
244 + * Core ships no bare `#wpadminbar::before/::after` rule, so this
245 + * claims the slot rather than fighting one.
246 + */
247 +body.os-active.os-admin-bar-dynamic #wpadminbar::after {
248 + content: "";
249 + position: absolute;
250 + inset-inline: 0;
251 + inset-block-start: 100%;
252 + height: var(--os-admin-bar-reveal-zone, 16px);
253 + /*
254 + * The zone changes size only once the bar has come to rest — a
255 + * step, not a slide, held back for the length of the bar's own
256 + * slide. That delay is what keeps the reveal stable. Collapsed the
257 + * instant hover began, the zone was gone while the bar was still
258 + * on its way down: a pointer resting in the band the zone had
259 + * covered was outside the bar's box for the rest of the slide, so
260 + * hover dropped, the bar turned back, the zone returned under the
261 + * pointer, hover resumed — the bar flickered up and down for as
262 + * long as the pointer stayed near the edge. Held for the slide,
263 + * the zone still hangs off the moving bar and the two together
264 + * always cover the pointer that tripped it; by the time the zone
265 + * goes, the bar's own box is over that pointer. The same delay on
266 + * the way back keeps the zone from reappearing under a pointer
267 + * that just left the bar while the bar is still retracting.
268 + */
269 + transition: height 0s linear var(--os-admin-bar-slide, 180ms);
270 +}
271 +
272 +/*
273 + * ...but only while the bar is parked. Left standing once the bar is
274 + * out, the zone would hang over the top of the desktop and swallow
275 + * clicks on whatever window is up there.
276 + *
277 + * Collapsing it is also what keeps the reveal stable: the pointer
278 + * that tripped the zone is, post-reveal, inside the bar's real box,
279 + * so `:hover` holds without the zone's help — and it collapses only
280 + * once the bar is there (the transition above).
281 + */
282 +body.os-active.os-admin-bar-dynamic #wpadminbar:hover::after,
283 +body.os-active.os-admin-bar-dynamic #wpadminbar:focus-within::after,
284 +body.os-active.os-admin-bar-dynamic #wpadminbar:active::after {
285 + height: 0;
286 +}
287 +
288 +/*
289 + * Coarse pointers have no hover state and a much fatter contact patch,
290 + * so a 4px seam is neither discoverable nor tappable. Widen both the
291 + * seam and the zone — `:active` above is what actually reveals the bar
292 + * there. Kept under the 32px bar height, same ceiling as the default.
293 + */
294 +@media (hover: none) {
295 + body.os-active.os-admin-bar-dynamic #wpadminbar {
296 + --os-admin-bar-peek: 10px;
297 + --os-admin-bar-reveal-zone: 20px;
298 + }
299 +}
300 +
301 +@media (prefers-reduced-motion: reduce) {
302 + body.os-active.os-admin-bar-dynamic #wpadminbar,
303 + body.os-active.os-admin-bar-dynamic #wpadminbar::after {
304 + /* The bar jumps, so the zone has nothing to wait for. */
305 + transition: none;
306 + }
307 +}
308 +
309 +/*
310 + * Hidden — the bar is gone. This removes the "Switch to Classic Admin"
311 + * toggle, which is why it is safe: the dock's core rail always carries
312 + * an "Exit OpenStation" tile (src/exit-os.ts) hitting the
313 + * same endpoint. Do not add a mode that removes both.
314 + */
315 +body.os-active.os-admin-bar-hidden #wpadminbar {
316 + display: none !important;
317 +}
318 +
319 +/*
320 + * Both non-static modes: the shell owns the whole viewport. Two body
321 + * classes beat the `.os-shell` base rule AND its <783px
322 + * media-query variant on specificity, so source order doesn't matter.
323 + */
324 +body.os-active.os-admin-bar-dynamic .os-shell,
325 +body.os-active.os-admin-bar-hidden .os-shell {
326 + inset-block-start: 0;
327 +}
328 +
329 +/*
330 + * Core reserves the bar's height as `padding-top` on <html>. In both
331 + * non-static modes the bar is out of flow (or absent) and the shell
332 + * covers the viewport anyway, so the reserve is dead space — release
333 + * it so any classic content behind the shell isn't pushed down by a
334 + * bar that isn't sitting there. Same idiom as chromeless.css.
335 + */
336 +html.wp-toolbar:has(body.os-admin-bar-dynamic),
337 +html.wp-toolbar:has(body.os-admin-bar-hidden) {
338 + padding-top: 0 !important;
339 +}
340 +
341 +/*
342 + * A desktop theme that draws the toolbar.
343 + *
344 + * The toolbar's colours normally belong to the user's admin colour
345 + * scheme, whose own stylesheet paints it. A theme takes them over only
346 + * when it declares an `--os-toolbar-*` token, which is what puts
347 + * `os-toolbar-themed` on the body (PHP on first paint, the theme apply
348 + * pass on a live switch). Without that class none of this matches, so
349 + * a scheme's toolbar stays the scheme's under every other theme.
350 + *
351 + * The fallbacks are Core's own values for the default scheme.
352 + */
353 +body.os-active.os-toolbar-themed #wpadminbar {
354 + background: var(--os-toolbar-bg, #1d2327);
355 + box-shadow: var(--os-toolbar-shadow, none);
356 + -webkit-font-smoothing: var(--os-font-smoothing, subpixel-antialiased);
357 +}
358 +
359 +body.os-active.os-toolbar-themed #wpadminbar :not(.ab-icon):not([class*="dashicons"]) {
360 + font-family: var(--os-toolbar-font, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen-Sans, Ubuntu, Cantarell, "Helvetica Neue", sans-serif);
361 + font-size: var(--os-toolbar-font-size, 13px);
362 +}
363 +
364 +/*
365 + * Core sets the bar's line heights in ems against its 13px type. A
366 + * face at another size keeps Core's pixel lines (the bar's height for a
367 + * top-level item, 26px for a menu row), or its labels ride high or low
368 + * against the icons. A face whose metrics sit differently from the
369 + * system font's nudges its labels with `--os-toolbar-line-height`.
370 + */
371 +body.os-active.os-toolbar-themed #wpadminbar .ab-top-menu > li > .ab-item,
372 +body.os-active.os-toolbar-themed #wpadminbar .ab-top-menu > li > .ab-item :not(.ab-icon):not(img) {
373 + line-height: var(--os-toolbar-line-height, var(--wp-admin--admin-bar--height, 32px));
374 +}
375 +
376 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul li .ab-item {
377 + line-height: 26px;
378 +}
379 +
380 +body.os-active.os-toolbar-themed #wpadminbar .ab-empty-item,
381 +body.os-active.os-toolbar-themed #wpadminbar a.ab-item,
382 +body.os-active.os-toolbar-themed #wpadminbar > #wp-toolbar span.ab-label,
383 +body.os-active.os-toolbar-themed #wpadminbar > #wp-toolbar span.noticon {
384 + color: var(--os-toolbar-fg, #f0f0f1);
385 +}
386 +
387 +body.os-active.os-toolbar-themed #wpadminbar .ab-icon::before,
388 +body.os-active.os-toolbar-themed #wpadminbar .ab-item::before,
389 +body.os-active.os-toolbar-themed #wpadminbar #adminbarsearch::before {
390 + color: var(--os-toolbar-icon, rgba(240, 246, 252, 0.6));
391 +}
392 +
393 +body.os-active.os-toolbar-themed #wpadminbar:not(.mobile) .ab-top-menu > li > .ab-item:focus,
394 +body.os-active.os-toolbar-themed #wpadminbar:not(.mobile) .ab-top-menu > li:hover > .ab-item,
395 +body.os-active.os-toolbar-themed #wpadminbar .ab-top-menu > li.hover > .ab-item {
396 + background: var(--os-toolbar-hover-bg, #2c3338);
397 + color: var(--os-toolbar-hover-fg, #72aee6);
398 +}
399 +
400 +body.os-active.os-toolbar-themed #wpadminbar:not(.mobile) > #wp-toolbar li:hover span.ab-label,
401 +body.os-active.os-toolbar-themed #wpadminbar > #wp-toolbar li.hover span.ab-label,
402 +body.os-active.os-toolbar-themed #wpadminbar li:hover .ab-icon::before,
403 +body.os-active.os-toolbar-themed #wpadminbar li:hover .ab-item::before,
404 +body.os-active.os-toolbar-themed #wpadminbar li.hover .ab-icon::before,
405 +body.os-active.os-toolbar-themed #wpadminbar li.hover .ab-item::before {
406 + color: var(--os-toolbar-hover-fg, #72aee6);
407 +}
408 +
409 +body.os-active.os-toolbar-themed #wpadminbar .menupop .ab-sub-wrapper {
410 + background: var(--os-toolbar-menu-bg, #2c3338);
411 + box-shadow: var(--os-toolbar-menu-shadow, 0 3px 5px rgba(0, 0, 0, 0.2));
412 +}
413 +
414 +/* The WordPress menu's lower group sits on a darker panel of its own. */
415 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul.ab-sub-secondary,
416 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul.ab-sub-secondary .ab-submenu {
417 + background: var(--os-toolbar-menu-bg, #3c434a);
418 +}
419 +
420 +body.os-active.os-toolbar-themed #wpadminbar .ab-submenu .ab-item,
421 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul li a,
422 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul li a strong {
423 + color: var(--os-toolbar-menu-fg, rgba(240, 246, 252, 0.7));
424 +}
425 +
426 +/*
427 + * The account menu's name lines. Core colours them by ID, which
428 + * out-ranks the rows above, so they are restated here, hover included.
429 + */
430 +body.os-active.os-toolbar-themed #wpadminbar #wp-admin-bar-user-info .display-name {
431 + color: var(--os-toolbar-menu-fg, #fff);
432 +}
433 +
434 +body.os-active.os-toolbar-themed #wpadminbar #wp-admin-bar-user-info .username {
435 + color: var(--os-toolbar-menu-fg-muted, #a7aaad);
436 +}
437 +
438 +body.os-active.os-toolbar-themed #wpadminbar #wp-admin-bar-user-info a:hover span,
439 +body.os-active.os-toolbar-themed #wpadminbar #wp-admin-bar-user-info a:focus span {
440 + color: var(--os-toolbar-menu-hover-fg, #72aee6);
441 +}
442 +
443 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul li a:hover,
444 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop ul li a:focus,
445 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop.hover ul li a:hover,
446 +body.os-active.os-toolbar-themed #wpadminbar .quicklinks .menupop.hover ul li a:focus {
447 + background: var(--os-toolbar-menu-hover-bg, transparent);
448 + color: var(--os-toolbar-menu-hover-fg, #72aee6);
449 +}
450 +
451 +/*
452 + * The time, for a theme that draws the toolbar as a menu bar
453 + * (`src/desktop-themes/toolbar-clock.ts`). It is not a control, so it
454 + * does not light up under the pointer.
455 + */
456 +body.os-active.os-toolbar-themed #wpadminbar #wp-admin-bar-os-clock {
457 + display: var(--os-toolbar-clock-display, none);
458 +}
459 +
460 +body.os-active.os-toolbar-themed #wpadminbar #wp-admin-bar-os-clock > .ab-item {
461 + background: none;
462 + color: var(--os-toolbar-fg, #f0f0f1);
463 +}
464 +
465 +/*
120 466 * Align the admin-bar W logo with the dock below it.
121 467 *
122 468 * Without this rule the admin bar's leftmost item (the WordPress W)
123 469 * renders at its Core-dictated ~44 px width, while the dock below it
@@ -125,17 +471,21 @@
125 471 * preference. The misalignment reads as "two disconnected left
126 472 * regions" — visually scruffy on an otherwise tight shell.
127 473 *
128 474 * We size the logo's <li> to match the dock's width and center the
129 - * W inside, so the two columns share an axis. `--desktop-mode-dock-width`
475 + * W inside, so the two columns share an axis. `--os-dock-width`
130 476 * is now set on :root (see settings.ts → apply()) so it reaches
131 - * siblings of #desktop-mode-shell like the admin bar.
477 + * siblings of #os-shell like the admin bar.
132 478 */
133 -body.desktop-mode-active #wpadminbar #wp-admin-bar-wp-logo {
134 - width: var( --desktop-mode-dock-width, 56px );
479 +body.os-active #wpadminbar #wp-admin-bar-menu-toggle {
480 + display: none;
135 481 }
136 482
137 -body.desktop-mode-active #wpadminbar #wp-admin-bar-wp-logo > .ab-item {
483 +body.os-active #wpadminbar #wp-admin-bar-wp-logo {
484 + width: var( --os-dock-width, 56px );
485 +}
486 +
487 +body.os-active #wpadminbar #wp-admin-bar-wp-logo > .ab-item {
138 488 display: flex !important;
139 489 align-items: center;
140 490 justify-content: center;
141 491 padding-inline: 0 !important;
@@ -145,19 +495,27 @@
145 495 * The W glyph is painted via a ::before pseudo on `.ab-icon`. Center
146 496 * it within the flex cell so varying dock widths don't leave it
147 497 * visually offset.
148 498 */
149 -body.desktop-mode-active #wpadminbar #wp-admin-bar-wp-logo > .ab-item > .ab-icon {
499 +body.os-active #wpadminbar #wp-admin-bar-wp-logo > .ab-item > .ab-icon {
150 500 margin: 0;
151 501 }
152 502
153 503 /*
504 + * Core nudges the W down 2px to centre it from the top of its cell.
505 + * The flex cell above already centres it, so the nudge would sit it low.
506 + */
507 +body.os-active #wpadminbar #wp-admin-bar-wp-logo > .ab-item > .ab-icon::before {
508 + top: 0;
509 +}
510 +
511 +/*
154 512 * Classic wpcontent carries a `margin-left: 160px` for the sidebar. With
155 513 * the sidebar hidden we let wpcontent fall back to flush — the shell is
156 514 * fixed-positioned anyway so this doesn't change the shell's layout, it
157 515 * just prevents a phantom sidebar gutter in any stray visible content.
158 516 */
159 -body.desktop-mode-active #wpcontent {
517 +body.os-active #wpcontent {
160 518 margin-inline-start: 0;
161 519 padding-inline-start: 0;
162 520 }
163 521
@@ -164,12 +522,26 @@
164 522 /*
165 523 * Desktop shell — fills the viewport below the admin bar.
166 524 * Uses position: fixed so it's unaffected by any containing-block
167 525 * quirks in #wpwrap/#wpcontent.
526 + *
527 + * The inset is the bar's MEASURED bottom edge, `--os-admin-bar-height`
528 + * (written on <html> by `src/admin-bar-height.ts`), with Core's own
529 + * token behind it for the first paint. Core's token is Core's promise
530 + * about Core's bar; a host can make the bar taller, give it a border
531 + * or push it down under a strip of its own — WordPress.com's staff
532 + * debug chrome does — and the shell then started under the bar by
533 + * exactly the difference. The measured token is absent whenever the
534 + * bar has no box at the top edge (hidden, mobile, solo, fullscreen,
535 + * parked in the dynamic mode), so every mode that rebinds Core's
536 + * token below still resolves through it.
168 537 */
169 -.desktop-mode-shell {
538 +.os-shell {
170 539 position: fixed;
171 - inset-block-start: var(--wp-admin--admin-bar--height, 32px);
540 + inset-block-start: var(
541 + --os-admin-bar-height,
542 + var(--wp-admin--admin-bar--height, 32px)
543 + );
172 544 inset-inline-start: 0;
173 545 inset-inline-end: 0;
174 546 inset-block-end: 0;
175 547 display: flex;
@@ -174,9 +546,33 @@
174 546 inset-block-end: 0;
175 547 display: flex;
176 548 flex-direction: column;
177 549 overflow: hidden;
178 - z-index: var(--desktop-mode-z-base);
550 + z-index: var(--os-z-base);
551 + /*
552 + * Opaque floor. The wallpaper paints over this and is what anyone
553 + * actually sees — but the wallpaper is one layer among several,
554 + * and behind this shell is the classic admin page, which is WHITE.
555 + * Without a background here, any frame in which the wallpaper
556 + * doesn't paint flashes that white through the whole viewport.
557 + * See `--os-backstop`.
558 + */
559 + background: var(--os-backstop, #1d2327);
560 + /*
561 + * A bitmap face drawn on whole pixels wants plain greyscale
562 + * smoothing; the fallback is what the shell inherits from Core's
563 + * `#wpwrap` anyway.
564 + */
565 + -webkit-font-smoothing: var(--os-font-smoothing, subpixel-antialiased);
566 + /*
567 + * Shell typeface. Every piece of chrome that doesn't set its own
568 + * face inherits from here — dock labels, desktop icon labels,
569 + * widgets, the overview. Windows override with `--os-ui-font` on
570 + * their body, so a theme can run a display face on the desk and a
571 + * text face inside windows. `inherit` is the no-theme value, i.e.
572 + * identical to not declaring the property at all.
573 + */
574 + font-family: var(--os-font, inherit);
179 575 }
180 576
181 577 /*
182 578 * Wallpaper layer — first child of the shell, sits behind the dock
@@ -181,9 +577,9 @@
181 577 /*
182 578 * Wallpaper layer — first child of the shell, sits behind the dock
183 579 * and desktop area so a translucent dock shows through to the
184 580 * background (macOS pattern). CSS wallpapers paint via the
185 - * `--desktop-mode-bg` custom property; canvas wallpapers mount their
581 + * `--os-bg` custom property; canvas wallpapers mount their
186 582 * own DOM (typically a <canvas>) into this element via JS.
187 583 *
188 584 * z-index: 0 keeps it below the shell body flex row which has no
189 585 * explicit z-index of its own but establishes its own local
@@ -189,25 +585,177 @@
189 585 * explicit z-index of its own but establishes its own local
190 586 * stacking context via `position: relative`, so the dock + windows
191 587 * always render above the wallpaper regardless of DOM order.
192 588 */
193 -.desktop-mode-wallpaper {
589 +.os-wallpaper {
194 590 position: absolute;
195 591 inset: 0;
196 592 z-index: 0;
197 - background: var(--desktop-mode-bg);
593 + background: var(--os-bg);
198 594 overflow: hidden;
199 595 pointer-events: none;
200 596 }
201 597
202 598 /*
599 + * Mio layer — the desk companion.
600 + *
601 + * A sibling of the wallpaper inside the shell, but at the far end of
602 + * the stack: Mio paints ABOVE windows (it perches on them)
603 + * and below the dock (it must never cover navigation). Created on
604 + * demand by `src/mio/controller.ts`. A shell whose user has never
605 + * switched Mio on has no extra element at all; switching it off
606 + * hides this one rather than removing it, because the instance is
607 + * parked (WebGL context intact) rather than destroyed — see the
608 + * `parked` field there.
609 + *
610 + * The layer and its <canvas> are permanently inert. Making a
611 + * full-shell canvas interactive — even conditionally, from a
612 + * per-frame hit test — would swallow clicks meant for the window
613 + * underneath. Only the small round `__handle` inside it takes
614 + * pointer events, and it rides on the blob.
615 + */
616 +.os-mio {
617 + position: absolute;
618 + inset: 0;
619 + z-index: var(--os-z-mio);
620 + overflow: hidden;
621 + pointer-events: none;
622 +}
623 +
624 +.os-mio__handle {
625 + position: absolute;
626 + /*
627 + * PHYSICAL `top` / `left`, deliberately — the one place in this
628 + * sheet that isn't logical. The handle is positioned every frame
629 + * by a `translate3d()` carrying the body's canvas coordinates,
630 + * and `transform` is always physical. Anchoring with
631 + * `inset-inline-start` would flip the origin to the right edge
632 + * under RTL while the translation kept pushing rightwards, and
633 + * the handle would walk off screen.
634 + */
635 + top: 0;
636 + left: 0;
637 + border-radius: 50%;
638 + pointer-events: auto;
639 + cursor: grab;
640 + /* Promote to its own layer: the handle is re-positioned via
641 + * `transform` on every animation frame. */
642 + will-change: transform;
643 + touch-action: none;
644 +}
645 +
646 +.os-mio__handle.is-dragging {
647 + cursor: grabbing;
648 +}
649 +
650 +/*
651 + * "Make it yours" panel — a live-preview dialog, not a modal.
652 + *
653 + * `<os-modal>` is built for the usual case: dim the page, blur it
654 + * slightly, put the decision in front of everything. Every one of
655 + * those defaults is wrong here, because the thing being edited is
656 + * ON the page and the whole point is watching it change.
657 + *
658 + * - No scrim and no `backdrop-filter`, or the companion the sliders
659 + * are driving is a blurred grey smudge behind them.
660 + * - `pointer-events: none` on the scrim so the desk stays live: Mio
661 + * can still be picked up and thrown while the panel is open, and a
662 + * click on the wallpaper doesn't dismiss the panel mid-adjustment.
663 + * `::part(dialog)` puts them back for the box itself.
664 + * - Parked against the inline end rather than centred, so it isn't
665 + * sitting on top of the subject.
666 + *
667 + * Mio never treats the panel as an obstacle: the collision set comes
668 + * from `getWallpaperSurfaces()`, which seeds windows, the shell floor,
669 + * docks and widget cards — a dialog on `document.body` is none of
670 + * those, so there is nothing to bump into.
671 + */
672 +.os-mio-panel {
673 + background: transparent;
674 + background-image: none;
675 + backdrop-filter: none;
676 + pointer-events: none;
677 + justify-content: flex-end;
678 + padding-inline-end: clamp(16px, 4vw, 64px);
679 +}
680 +
681 +/*
682 + * Both halves are required, and the second one is easy to miss.
683 + *
684 + * `::part(dialog)` reaches the box in the modal's SHADOW tree — its
685 + * header, title and close button inherit from there. But the controls
686 + * are slotted LIGHT-DOM children of `<os-modal>`, and slotted content
687 + * inherits from its light-DOM parent (the host) rather than from the
688 + * shadow ancestor it is projected into. So the host's
689 + * `pointer-events: none` reaches them regardless of what the part
690 + * says, and without this second rule every slider and button in the
691 + * panel is inert while looking perfectly normal.
692 + */
693 +.os-mio-panel::part(dialog),
694 +.os-mio-panel > * {
695 + pointer-events: auto;
696 +}
697 +
698 +/*
699 + * Overview (Exposé) hides the desk furniture so the window grid
700 + * reads cleanly — Mio goes with the widgets and the notes.
701 + * `:has()` rather than a descendant selector because Mio
702 + * layer is a sibling of `.os-shell__body`, not a child of
703 + * the desktop area.
704 + */
705 +.os-mio {
706 + transition: opacity 160ms ease;
707 +}
708 +
709 +.os-shell:has( .os-area--overview ) .os-mio {
710 + opacity: 0;
711 +}
712 +
713 +/*
714 + * Reduced motion is handled in the simulation, not here: the runtime
715 + * zeroes the idle float and the hue drift so Mio holds still
716 + * until the user actually interacts with it. Hiding it would be
717 + * wrong — the user switched it on deliberately.
718 + */
719 +
720 +/*
721 + * Desktop-theme wallpaper texture (DESKTOP slot).
722 + *
723 + * On a `::before` rather than this element's own background, because
724 + * `--os-bg` is set by the wallpaper picker and can be a
725 + * gradient — i.e. a background-IMAGE. Overriding `background-image`
726 + * here would silently erase every gradient wallpaper the moment a
727 + * theme was active. The pseudo-element layers instead of replacing.
728 + *
729 + * Resulting precedence, bottom to top:
730 + * CSS wallpaper (`--os-bg`)
731 + * → theme DESKTOP texture (this rule)
732 + * → canvas wallpapers, which mount as CHILDREN of the layer and
733 + * therefore paint above both.
734 + *
735 + * A theme that wants the user's wallpaper to remain visible ships a
736 + * texture with transparency; an opaque one takes the desk over.
737 + * With no theme active the image is `none` and this paints nothing.
738 + */
739 +.os-wallpaper::before {
740 + content: "";
741 + position: absolute;
742 + inset: 0;
743 + pointer-events: none;
744 + background-image: var(--os-desktop-image, none);
745 + background-repeat: var(--os-desktop-image-repeat, repeat);
746 + background-size: var(--os-desktop-image-size, auto);
747 + background-position: var(--os-desktop-image-position, center);
748 +}
749 +
750 +/*
203 751 * Canvas children fill the layer and ignore pointer events by
204 752 * default — a wallpaper is presentational chrome, not an interactive
205 753 * element. Plugins that genuinely need a clickable wallpaper can
206 754 * override `pointer-events` on their own mounted node.
207 755 */
208 -.desktop-mode-wallpaper > canvas,
209 -.desktop-mode-wallpaper > * {
756 +.os-wallpaper > canvas,
757 +.os-wallpaper > * {
210 758 width: 100%;
211 759 height: 100%;
212 760 display: block;
213 761 }
@@ -213,10 +761,13 @@
213 761 }
214 762
215 763 /* Below 783px WP collapses the admin bar to 46px. */
216 764 @media screen and (max-width: 782px) {
217 - .desktop-mode-shell {
218 - inset-block-start: var(--wp-admin--admin-bar--height, 46px);
765 + .os-shell {
766 + inset-block-start: var(
767 + --os-admin-bar-height,
768 + var(--wp-admin--admin-bar--height, 46px)
769 + );
219 770 }
220 771 }
221 772
222 773 /*
@@ -230,18 +781,18 @@
230 781 * The window's title bar remains visible because the window itself is
231 782 * position: fixed at top: 0, so the focus/exit-fullscreen button is
232 783 * still reachable.
233 784 */
234 -body.desktop-mode-has-fullscreen-window #wpadminbar {
785 +body.os-has-fullscreen-window #wpadminbar {
235 786 display: none !important;
236 787 }
237 788
238 -body.desktop-mode-has-fullscreen-window .desktop-mode-shell {
789 +body.os-has-fullscreen-window .os-shell {
239 790 inset-block-start: 0;
240 791 }
241 792
242 793 /* Shell body: contains dock + desktop area side by side. */
243 -.desktop-mode-shell__body {
794 +.os-shell__body {
244 795 flex: 1;
245 796 display: flex;
246 797 overflow: hidden;
247 798 position: relative;
@@ -252,18 +803,27 @@
252 803 * because the wallpaper renders in the shell-level layer behind
253 804 * both this area and the dock. Stacking context via position: relative
254 805 * ensures children (windows) sit above the wallpaper.
255 806 *
256 - * `padding-bottom` reserves room for the floating bottom dock pill
257 - * that every layout (Classic, Unified, Spatial) puts at the bottom
258 - * — 40px icons + 16px padding + 12px gap below + 8px breathing room.
807 + * The padding reserves the band the floating bottom dock pill covers.
808 + * It reads the work-area insets `src/work-area/index.ts` writes on
809 + * `#os-shell` from the pill's LIVE geometry, so it is 0 with a side
810 + * dock (which is a flex sibling and already narrows the area) and
811 + * tracks the dock-size preference with the pill at the bottom. The
812 + * `80px` literal is the pre-measurement floor: 40px tile + 16px pill
813 + * padding + 12px gap below + 8px breathing room, what the rule
814 + * hardcoded before the work area existed, in force until the shell
815 + * has measured once.
259 816 */
260 -.desktop-mode-area {
817 +.os-area {
261 818 flex: 1;
262 819 position: relative;
263 820 overflow: hidden;
264 821 background: transparent;
265 - padding-bottom: 80px;
822 + padding-top: var( --os-work-area-inset-top, 0px );
823 + padding-right: var( --os-work-area-inset-right, 0px );
824 + padding-bottom: var( --os-work-area-inset-bottom, 80px );
825 + padding-left: var( --os-work-area-inset-left, 0px );
266 826 transition: opacity 180ms ease;
267 827 }
268 828
269 829 /*
@@ -270,9 +830,9 @@
270 830 * Boot reveal gate.
271 831 *
272 832 * On F5 the shell paints in stages: the dispatcher's
273 833 * `repaintIcons()` lands the server-rendered wallpaper icons
274 - * synchronously from `desktopModeConfig.desktopIcons`, then the
834 + * synchronously from `openStationConfig.desktopIcons`, then the
275 835 * files-layer mounts and momentarily renders an empty bucket while
276 836 * REST `listPlacements(0)` is in flight, then folders/posts/links
277 837 * slot in on the next paint. The user reads that as "plugins show
278 838 * first, then everything blinks and the rest arrives."
@@ -285,9 +845,9 @@
285 845 *
286 846 * `desktop.ts` removes the class inside a `requestAnimationFrame`
287 847 * after the root files-layer's `hydrated` promise resolves (with a
288 848 * 2 s JS safety timeout). The opacity transition declared on
289 - * `.desktop-mode-area` smooths the reveal.
849 + * `.os-area` smooths the reveal.
290 850 *
291 851 * The fallback animation is a resilience layer for the case where
292 852 * the shell JS never runs (network error mid-load, ad-blocker
293 853 * tearing down a bundle, …). The animation holds the area
@@ -301,15 +861,15 @@
301 861 * a tile that's about to reposition once REST returns.
302 862 *
303 863 * @since 0.18.x
304 864 */
305 -.desktop-mode-area--booting {
865 +.os-area--booting {
306 866 opacity: 0;
307 867 pointer-events: none;
308 - animation: desktop-mode-area-boot-fallback 3s forwards;
868 + animation: os-area-boot-fallback 3s forwards;
309 869 }
310 870
311 -@keyframes desktop-mode-area-boot-fallback {
871 +@keyframes os-area-boot-fallback {
312 872 0%,
313 873 90% {
314 874 opacity: 0;
315 875 pointer-events: none;
@@ -333,14 +893,25 @@
333 893 * click) while individual tiles re-enable pointer events so they
334 894 * remain clickable.
335 895 * --------------------------------------------------------------- */
336 896
337 -.desktop-mode-icons {
897 +.os-icons {
338 898 position: absolute;
339 - inset-block-start: 16px;
340 - inset-block-end: 16px;
341 - inset-inline-start: 16px;
342 - inset-inline-end: 16px;
899 + /*
900 + * 16px of gutter inside the WORK AREA, not inside the desktop
901 + * area: an absolutely positioned box ignores its parent's
902 + * padding, so without the insets the grid's last row sat under
903 + * the bottom dock pill. Same tokens `.os-area` reserves with.
904 + *
905 + * Physical `left` / `right`, not the logical pair: the insets are
906 + * measured from rects, so `-left` is the visual left whichever
907 + * way the locale reads. The gutter is 16px on both sides, so
908 + * nothing is lost by going physical here.
909 + */
910 + top: calc( var( --os-work-area-inset-top, 0px ) + 16px );
911 + bottom: calc( var( --os-work-area-inset-bottom, 80px ) + 16px );
912 + left: calc( var( --os-work-area-inset-left, 0px ) + 16px );
913 + right: calc( var( --os-work-area-inset-right, 0px ) + 16px );
343 914 display: grid;
344 915 /*
345 916 * Column-major flow: icons fill the first column top-to-bottom,
346 917 * then start the next column. Matches the macOS / Finder
@@ -370,9 +941,9 @@
370 941 */
371 942 overflow: auto;
372 943 }
373 944
374 -.desktop-mode-icon {
945 +.os-icon {
375 946 pointer-events: auto;
376 947 display: flex;
377 948 flex-direction: column;
378 949 align-items: center;
@@ -380,22 +951,33 @@
380 951 gap: 6px;
381 952 width: 88px;
382 953 padding: 8px 4px;
383 954 border: 0;
384 - background: transparent;
385 - color: var(--desktop-mode-fg, #fff);
955 + background-color: transparent;
956 + /*
957 + * ICON_TILE texture slot — a plate behind each wallpaper icon.
958 + * Painted under the icon image and its label, so a theme can give
959 + * desktop shortcuts a physical tile the way a phone home screen
960 + * does. Unset = `none` = the transparent tile we always had.
961 + */
962 + background-image: var(--os-tile-image, none);
963 + background-repeat: var(--os-tile-image-repeat, no-repeat);
964 + background-size: var(--os-tile-image-size, auto);
965 + background-position: var(--os-tile-image-position, center);
966 + /* Also the glyph: silhouette art is masked with `currentColor`. */
967 + color: var(--os-desk-fg, var(--os-fg, #fff));
386 968 cursor: pointer;
387 969 border-radius: 8px;
388 970 transition: background-color 0.15s ease;
389 - /* Positioning context for `.desktop-mode-icon__badge`. */
971 + /* Positioning context for `.os-icon__badge`. */
390 972 position: relative;
391 973 }
392 974
393 975 /*
394 - * Icon badge — symmetric to `.desktop-mode-dock__badge` but anchored
976 + * Icon badge — symmetric to `.os-dock__badge` but anchored
395 977 * to the wallpaper-icon image. Same gradient, same ring, slightly
396 978 * larger so it reads at the longer wallpaper viewing distance.
397 - * Painted by `wp.desktop.icons.setBadge( id, count )` — see
979 + * Painted by `wp.os.icons.setBadge( id, count )` — see
398 980 * `src/desktop-icons.ts` for the imperative API and
399 981 * `src/recycle-bin/badge.ts` for the canonical multi-rail
400 982 * consumer. The class name is part of the stable contract; the
401 983 * positioning, color, and shadow are not — themes or future
@@ -400,24 +982,40 @@
400 982 * consumer. The class name is part of the stable contract; the
401 983 * positioning, color, and shadow are not — themes or future
402 984 * shell builds may restyle freely.
403 985 */
404 -.desktop-mode-icon__badge {
986 +.os-icon__badge {
405 987 position: absolute;
406 988 top: 4px;
407 989 inset-inline-end: 14px;
408 - min-width: 18px;
409 - height: 18px;
410 - padding: 0 5px;
990 + /* Same derivation as the dock badge, sized off the wallpaper icon
991 + * rather than the dock icon. The default resolves to 18px / 11px —
992 + * exactly the old values. */
993 + --os-icon-badge-computed-size: var(
994 + --os-icon-badge-size,
995 + calc( var( --os-icon-image-size, 48px ) * 0.375 )
996 + );
997 + min-width: var( --os-icon-badge-computed-size );
998 + height: var( --os-icon-badge-computed-size );
999 + padding: 0 var(
1000 + --os-icon-badge-padding,
1001 + calc( var( --os-icon-badge-computed-size ) * 0.28 )
1002 + );
411 1003 box-sizing: border-box;
412 1004 border-radius: 999px;
413 - background: linear-gradient( 180deg, #ff5a5a 0%, #d63638 100% );
414 - color: #fff;
1005 + background: var(
1006 + --os-icon-badge-bg,
1007 + linear-gradient( 180deg, #ff5a5a 0%, var( --os-ui-danger, #d63638 ) 100% )
1008 + );
1009 + color: var( --os-icon-badge-fg, var( --os-ui-fg-on-accent, #fff ) );
415 1010 display: inline-flex;
416 1011 align-items: center;
417 1012 justify-content: center;
418 - font-size: 11px;
419 - font-weight: 700;
1013 + font-size: var(
1014 + --os-icon-badge-font-size,
1015 + calc( var( --os-icon-badge-computed-size ) * 0.611 )
1016 + );
1017 + font-weight: var( --os-icon-badge-font-weight, 700 );
420 1018 line-height: 1;
421 1019 font-variant-numeric: tabular-nums;
422 1020 box-shadow:
423 1021 0 0 0 1.5px rgba( 0, 0, 0, 0.4 ),
@@ -424,200 +1022,56 @@
424 1022 0 1px 3px rgba( 0, 0, 0, 0.35 );
425 1023 pointer-events: none;
426 1024 }
427 1025
428 -.desktop-mode-icon[ data-icon-id="desktop-mode-recycle-bin" ] > .desktop-mode-icon__badge {
429 - top: 39px;
430 - inset-inline-end: 20px;
431 - min-width: 15px;
432 - height: 15px;
433 - padding: 0 4px;
434 - border-radius: 999px;
435 - background: rgba( 29, 35, 39, 0.74 );
436 - color: rgba( 255, 255, 255, 0.96 );
437 - font-size: 9px;
438 - font-weight: 700;
439 - letter-spacing: 0;
440 - box-shadow:
441 - inset 0 0 0 1px rgba( 255, 255, 255, 0.28 ),
442 - 0 1px 2px rgba( 0, 0, 0, 0.28 );
443 -}
444 -
445 -.desktop-mode-icon:hover,
446 -.desktop-mode-icon:focus-visible {
447 - background: rgba(255, 255, 255, 0.12);
1026 +.os-icon:hover,
1027 +.os-icon:focus-visible {
1028 + /* background-COLOR, not the shorthand: the shorthand would reset
1029 + * the ICON_TILE texture declared above, so a themed tile would
1030 + * vanish on hover. */
1031 + background-color: var(--os-icon-hover-bg, rgba(255, 255, 255, 0.12));
448 1032 outline: none;
449 1033 }
450 1034
451 -.desktop-mode-icon:focus-visible {
1035 +.os-icon:focus-visible {
452 1036 box-shadow: 0 0 0 2px var(--wp-admin-theme-color, #2271b1);
453 1037 }
454 1038
455 -.desktop-mode-icon__image {
1039 +.os-icon__image {
456 1040 display: inline-flex;
457 1041 align-items: center;
458 1042 justify-content: center;
459 - width: 48px;
460 - height: 48px;
461 - font-size: 32px;
1043 + /* Tokenized so a theme can scale wallpaper icons — and so the
1044 + * badge above has something to derive its own size from. */
1045 + width: var( --os-icon-image-size, 48px );
1046 + height: var( --os-icon-image-size, 48px );
1047 + font-size: calc( var( --os-icon-image-size, 48px ) * 0.667 );
462 1048 line-height: 1;
463 1049 }
464 1050
465 -.desktop-mode-icon__image img {
1051 +.os-icon__image img {
466 1052 max-width: 48px;
467 1053 max-height: 48px;
468 1054 object-fit: contain;
469 1055 }
470 1056
471 -.desktop-mode-icon__label {
472 - font-size: 12px;
1057 +.os-icon__image {
1058 + filter: var(--os-icon-glyph-shadow, none);
1059 +}
1060 +
1061 +.os-icon__label {
1062 + font-size: var(--os-icon-label-font-size, 12px);
473 1063 text-align: center;
474 - text-shadow: 0 1px 2px rgba(0, 0, 0, 0.45);
1064 + background: var(--os-icon-label-bg, transparent);
1065 + border-radius: var(--os-icon-label-radius, 6px);
1066 + /* Inline only: a two-line caption already fills the 96px grid row. */
1067 + padding: var(--os-icon-label-padding, 0 6px);
1068 + text-shadow: var(--os-icon-label-shadow, 0 1px 2px rgba(0, 0, 0, 0.45));
475 1069 line-height: 1.2;
476 1070 word-break: break-word;
477 1071 }
478 1072
479 1073 /* ---------------------------------------------------------------
480 - * Sticky notes — Gutenberg `wp_guideline` artifacts tagged with the
481 - * sticky guideline type. Notes sit above wallpaper icons/widgets and
482 - * below windows, so they behave like desktop objects rather than app
483 - * chrome.
484 - * --------------------------------------------------------------- */
485 -
486 -.desktop-mode-sticky-notes {
487 - position: absolute;
488 - inset: 0;
489 - z-index: 2;
490 - pointer-events: none;
491 - transition:
492 - opacity 0.22s ease,
493 - transform 0.28s cubic-bezier( 0.2, 0, 0.2, 1 );
494 -}
495 -
496 -.desktop-mode-area--overview .desktop-mode-sticky-notes {
497 - opacity: 0;
498 - transform: translateY( 12px );
499 - pointer-events: none;
500 -}
501 -
502 -.desktop-mode-sticky-note {
503 - position: absolute;
504 - display: flex;
505 - flex-direction: column;
506 - pointer-events: auto;
507 - background: #fff09a;
508 - color: #2a2513;
509 - border: 1px solid rgba( 84, 67, 0, 0.24 );
510 - border-radius: 4px;
511 - box-shadow:
512 - 0 12px 28px rgba( 0, 0, 0, 0.22 ),
513 - 0 2px 5px rgba( 0, 0, 0, 0.16 ),
514 - inset 0 1px 0 rgba( 255, 255, 255, 0.55 );
515 - overflow: hidden;
516 - resize: both;
517 -}
518 -
519 -.desktop-mode-sticky-note--dragging {
520 - opacity: 0.92;
521 - resize: none;
522 - user-select: none;
523 -}
524 -
525 -.desktop-mode-sticky-note__header {
526 - display: flex;
527 - align-items: center;
528 - gap: 5px;
529 - min-height: 30px;
530 - padding: 4px 6px 4px 8px;
531 - background: rgba( 82, 64, 0, 0.06 );
532 - border-bottom: 1px solid rgba( 82, 64, 0, 0.14 );
533 - cursor: grab;
534 - touch-action: none;
535 - user-select: none;
536 -}
537 -
538 -.desktop-mode-sticky-note--dragging .desktop-mode-sticky-note__header {
539 - cursor: grabbing;
540 -}
541 -
542 -.desktop-mode-sticky-note__grip {
543 - flex: 0 0 auto;
544 - width: 8px;
545 - height: 14px;
546 - background-image: radial-gradient(
547 - circle,
548 - rgba( 60, 48, 0, 0.5 ) 1.2px,
549 - transparent 1.5px
550 - );
551 - background-size: 4px 4px;
552 - background-position: 0 1px;
553 - background-repeat: space;
554 - opacity: 0.42;
555 -}
556 -
557 -.desktop-mode-sticky-note__title {
558 - flex: 1;
559 - min-width: 0;
560 - font-size: 11px;
561 - font-weight: 650;
562 - overflow: hidden;
563 - text-overflow: ellipsis;
564 - white-space: nowrap;
565 -}
566 -
567 -.desktop-mode-sticky-note__status {
568 - flex: 0 0 auto;
569 -}
570 -
571 -.desktop-mode-sticky-note wpd-window-button {
572 - --wpd-btn-color: rgba( 42, 37, 19, 0.7 );
573 - --wpd-btn-color-hover: #2a2513;
574 - --wpd-btn-bg-hover: rgba( 42, 37, 19, 0.1 );
575 - --wpd-btn-bg-active: rgba( 42, 37, 19, 0.16 );
576 - --wpd-btn-danger-hover: rgba( 214, 54, 56, 0.18 );
577 - --wpd-btn-outline: var( --wp-admin-theme-color, #2271b1 );
578 -}
579 -
580 -.desktop-mode-sticky-note__open.is-disabled {
581 - opacity: 0.34;
582 - pointer-events: none;
583 -}
584 -
585 -.desktop-mode-sticky-note__editor {
586 - flex: 1;
587 - min-height: 0;
588 - --desktop-mode-window-bg: transparent;
589 - --desktop-mode-border: transparent;
590 - --desktop-mode-text: #2a2513;
591 - --desktop-mode-muted: rgba( 42, 37, 19, 0.62 );
592 - font-family:
593 - -apple-system,
594 - BlinkMacSystemFont,
595 - "Segoe UI",
596 - sans-serif;
597 -}
598 -
599 -.desktop-mode-sticky-note__editor::part(textarea) {
600 - height: 100%;
601 - min-height: 100%;
602 - padding: 10px 12px 12px;
603 - background: transparent;
604 - border: 0;
605 - border-radius: 0;
606 - box-shadow: none;
607 - color: #2a2513;
608 - font-size: 13px;
609 - line-height: 1.4;
610 - resize: none;
611 -}
612 -
613 -.desktop-mode-sticky-note__editor::part(textarea):hover,
614 -.desktop-mode-sticky-note__editor::part(textarea):focus-visible {
615 - border-color: transparent;
616 - box-shadow: none;
617 -}
618 -
619 -/* ---------------------------------------------------------------
620 1074 * Widgets column — right-edge glass strip that paints above the
621 1075 * wallpaper but beneath windows. Hosts stacked widget cards and a
622 1076 * trailing "Add widget" tile. Interactive only on its own cards +
623 1077 * the add tile; every other pixel is pointer-transparent so window
@@ -623,14 +1077,39 @@
623 1077 * the add tile; every other pixel is pointer-transparent so window
624 1078 * drag / resize / click-through behaviour is unaffected.
625 1079 * --------------------------------------------------------------- */
626 1080
627 -.desktop-mode-widgets {
1081 +.os-widgets {
628 1082 position: absolute;
629 - top: 16px;
630 - bottom: 16px;
631 - inset-inline-end: 16px;
1083 + /*
1084 + * Inside the work area vertically — see `.os-icons` for why the
1085 + * insets are here. The inline edge is logical: the column hugs
1086 + * the trailing side, while the side insets are physical; and a
1087 + * side rail never claims one anyway (it is a flex sibling, the
1088 + * area is already narrower).
1089 + *
1090 + * The cards sit 16px in from the area's top and trailing edges
1091 + * and 16px above the work area's foot, but the box reaches
1092 + * further than that and pads back in. The column scrolls, and a
1093 + * scroll container clips everything inside it to its padding
1094 + * box, the cards' drop shadow included: with the box hugging the
1095 + * cards, the shadow ended in a hard rectangle the size of the
1096 + * column, easy to see on a light wallpaper. The padding is the
1097 + * room the shadow needs (it reaches 28px out and 36px down, more
1098 + * on hover). The trailing side only gets the 16px to the area's
1099 + * edge, since the area clips there anyway. The column is
1100 + * pointer-transparent, so the extra room catches nothing; the
1101 + * add-widget pill measures the content box, not this one.
1102 + */
1103 + box-sizing: content-box;
1104 + top: var( --os-work-area-inset-top, 0px );
1105 + bottom: calc( var( --os-work-area-inset-bottom, 80px ) - 24px );
1106 + inset-inline-end: 0;
632 1107 width: 320px;
1108 + --_os-widgets-room-start: 40px;
1109 + --_os-widgets-room-end: 16px;
1110 + padding-block: 16px 40px;
1111 + padding-inline: var( --_os-widgets-room-start ) var( --_os-widgets-room-end );
633 1112 display: flex;
634 1113 flex-direction: column;
635 1114 gap: 12px;
636 1115 z-index: 1;
@@ -648,9 +1127,9 @@
648 1127 opacity 0.22s ease,
649 1128 transform 0.28s cubic-bezier( 0.2, 0, 0.2, 1 );
650 1129 }
651 1130
652 -.desktop-mode-area--overview .desktop-mode-widgets {
1131 +.os-area--overview .os-widgets {
653 1132 opacity: 0;
654 1133 /* Slight slide-off-right so the fade reads as "the column is
655 1134 * stepping back out of the way" rather than flat-dimming. */
656 1135 transform: translateX( 16px );
@@ -656,12 +1135,13 @@
656 1135 transform: translateX( 16px );
657 1136 pointer-events: none;
658 1137 }
659 1138
660 -.desktop-mode-widgets__list {
1139 +.os-widgets__list {
661 1140 display: flex;
662 1141 flex-direction: column;
663 1142 gap: 12px;
1143 + padding: 4px;
664 1144 }
665 1145
666 1146 /*
667 1147 * Individual widget card — glass backdrop matching the dock /
@@ -669,51 +1149,84 @@
669 1149 * content + the remove X land; the column itself stays
670 1150 * pointer-transparent so a drag that grazes the column's margin
671 1151 * falls through to the window beneath.
672 1152 */
673 -.desktop-mode-widgets__card {
1153 +.os-widgets__card {
674 1154 position: relative;
675 1155 padding: 0;
1156 + /* Column layout so the body can flex-shrink and scroll when the
1157 + * frame writes a fixed inline height (floating / resized cards).
1158 + * Without this the body keeps its natural height and content
1159 + * spills past the card's rounded bottom edge. */
1160 + display: flex;
1161 + flex-direction: column;
676 1162 pointer-events: auto;
677 - background: rgba( 20, 20, 22, 0.55 );
678 - backdrop-filter: blur( 18px ) saturate( 140% );
679 - -webkit-backdrop-filter: blur( 18px ) saturate( 140% );
680 - border: 1px solid rgba( 255, 255, 255, 0.08 );
681 - border-radius: 14px;
682 - color: #fff;
683 - box-shadow:
1163 + /*
1164 + * The glass is also `--os-ui-color-surface`, the one name in the
1165 + * widget contract that describes the card itself. Declared in
1166 + * `variables.css` so a widget reading it and the card painting it
1167 + * cannot drift apart.
1168 + */
1169 + background-color: var( --os-ui-color-surface, rgba( 20, 20, 22, 0.55 ) );
1170 + /*
1171 + * WIDGET texture slot — layered over the frosted card colour, so a
1172 + * translucent texture still gets the blur underneath.
1173 + */
1174 + background-image: var( --os-widget-image, none );
1175 + background-repeat: var( --os-widget-image-repeat, repeat );
1176 + background-size: var( --os-widget-image-size, auto );
1177 + background-position: var( --os-widget-image-position, center );
1178 + backdrop-filter: var( --os-widget-card-backdrop, blur( 18px ) saturate( 140% ) );
1179 + -webkit-backdrop-filter: var( --os-widget-card-backdrop, blur( 18px ) saturate( 140% ) );
1180 + border: var( --os-widget-card-border, 1px solid rgba( 255, 255, 255, 0.08 ) );
1181 + border-radius: var( --os-widget-card-radius, 14px );
1182 + /* The widget contract's text colour, which is what a widget's own
1183 + * stylesheet is told to read. */
1184 + color: var( --os-ui-color-text, var( --os-ui-fg-on-accent, #fff ) );
1185 + box-shadow: var(
1186 + --os-widget-card-shadow,
684 1187 0 8px 28px rgba( 0, 0, 0, 0.35 ),
685 - inset 0 0 0 1px rgba( 255, 255, 255, 0.04 );
1188 + inset 0 0 0 1px rgba( 255, 255, 255, 0.04 )
1189 + );
686 1190 transition:
687 - transform 0.18s ease,
688 1191 box-shadow 0.18s ease,
689 1192 opacity 0.18s ease;
690 1193 }
691 1194
692 -.desktop-mode-widgets__card:hover {
693 - transform: translateX( -2px );
694 - box-shadow:
1195 +/* Hover feedback is shadow-only — no transform. Cards must feel
1196 + * anchored; a hover nudge reads as the widget drifting under the
1197 + * pointer (and fought the user's chosen position on floating cards). */
1198 +.os-widgets__card:hover {
1199 + box-shadow: var(
1200 + --os-widget-card-shadow-hover,
695 1201 0 12px 36px rgba( 0, 0, 0, 0.45 ),
696 - inset 0 0 0 1px rgba( 255, 255, 255, 0.08 );
1202 + inset 0 0 0 1px rgba( 255, 255, 255, 0.08 )
1203 + );
697 1204 }
698 1205
699 -.desktop-mode-widgets__card-body {
1206 +.os-widgets__card-body {
700 1207 padding: 16px;
701 1208 min-height: 48px;
1209 + flex: 1 1 auto;
1210 + overflow-x: hidden;
1211 + overflow-y: auto;
1212 + scrollbar-width: thin;
702 1213 }
703 1214
704 -.desktop-mode-widgets__card-close {
1215 +.os-widgets__card-close {
705 1216 position: absolute;
706 1217 top: 6px;
707 1218 inset-inline-end: 6px;
708 - width: 22px;
709 - height: 22px;
1219 + /* 24px is the WCAG 2.2 SC 2.5.8 floor. The glyph inside is unchanged;
1220 + only the target grows. */
1221 + width: 24px;
1222 + height: 24px;
710 1223 display: flex;
711 1224 align-items: center;
712 1225 justify-content: center;
713 1226 padding: 0;
714 1227 border: 0;
715 - background: rgba( 0, 0, 0, 0.55 );
1228 + background: var( --os-ui-scrim, rgba( 0, 0, 0, 0.55 ) );
716 1229 color: rgba( 255, 255, 255, 0.75 );
717 1230 border-radius: 50%;
718 1231 cursor: pointer;
719 1232 opacity: 0;
@@ -722,18 +1235,31 @@
722 1235 background-color 0.15s ease,
723 1236 color 0.15s ease;
724 1237 }
725 1238
726 -.desktop-mode-widgets__card:hover .desktop-mode-widgets__card-close,
727 -.desktop-mode-widgets__card-close:focus-visible {
1239 +.os-widgets__card:hover .os-widgets__card-close,
1240 +.os-widgets__card-close:focus-visible {
728 1241 opacity: 1;
729 1242 }
730 1243
731 -.desktop-mode-widgets__card-close:hover {
732 - background: #d63638;
733 - color: #fff;
1244 +/*
1245 + * The corner close button rests at `opacity: 0` and only the card's
1246 + * hover reveals it, so on touch it is invisible and the widget cannot
1247 + * be dismissed at all. Rest it at the same 0.7 the chrome header's
1248 + * close button uses there, rather than a full 1, so a card that is
1249 + * only being read does not wear a hard × in its corner.
1250 + */
1251 +@media ( hover: none ) {
1252 + .os-widgets__card-close {
1253 + opacity: 0.7;
1254 + }
734 1255 }
735 1256
1257 +.os-widgets__card-close:hover {
1258 + background: var( --os-ui-danger, #d63638 );
1259 + color: var( --os-ui-fg-on-accent, #fff );
1260 +}
1261 +
736 1262 /*
737 1263 * Movable widgets — a thin chrome header at the top of the card holds
738 1264 * the drag grip, the widget's own label, and the × button. The whole
739 1265 * header is the drag handle (except for interactive children — those
@@ -739,10 +1265,11 @@
739 1265 * header is the drag handle (except for interactive children — those
740 1266 * remain clickable as normal). Non-movable widgets keep today's
741 1267 * corner-× layout unchanged.
742 1268 */
743 -.desktop-mode-widgets__chrome {
1269 +.os-widgets__chrome {
744 1270 display: flex;
1271 + flex-shrink: 0;
745 1272 align-items: center;
746 1273 gap: 8px;
747 1274 padding: 6px 8px;
748 1275 border-bottom: 1px solid rgba( 255, 255, 255, 0.06 );
@@ -751,13 +1278,13 @@
751 1278 -webkit-user-select: none;
752 1279 touch-action: none;
753 1280 }
754 1281
755 -.desktop-mode-widgets__card--dragging .desktop-mode-widgets__chrome {
1282 +.os-widgets__card--dragging .os-widgets__chrome {
756 1283 cursor: grabbing;
757 1284 }
758 1285
759 -.desktop-mode-widgets__grip {
1286 +.os-widgets__grip {
760 1287 flex-shrink: 0;
761 1288 width: 10px;
762 1289 height: 16px;
763 1290 background-image: radial-gradient(
@@ -771,13 +1298,13 @@
771 1298 opacity: 0.45;
772 1299 transition: opacity 0.12s ease;
773 1300 }
774 1301
775 -.desktop-mode-widgets__card:hover .desktop-mode-widgets__grip {
1302 +.os-widgets__card:hover .os-widgets__grip {
776 1303 opacity: 0.85;
777 1304 }
778 1305
779 -.desktop-mode-widgets__title {
1306 +.os-widgets__title {
780 1307 flex: 1;
781 1308 font-size: 12px;
782 1309 font-weight: 500;
783 1310 letter-spacing: 0.01em;
@@ -788,17 +1315,17 @@
788 1315 }
789 1316
790 1317 /* When the close button sits inside the chrome it's inline, not
791 1318 corner-absolute — reset position + always-visible opacity. */
792 -.desktop-mode-widgets__chrome .desktop-mode-widgets__card-close {
1319 +.os-widgets__chrome .os-widgets__card-close {
793 1320 position: static;
794 1321 opacity: 0.7;
795 - width: 20px;
796 - height: 20px;
1322 + width: 24px;
1323 + height: 24px;
797 1324 }
798 1325
799 -.desktop-mode-widgets__chrome .desktop-mode-widgets__card-close:hover,
800 -.desktop-mode-widgets__chrome .desktop-mode-widgets__card-close:focus-visible {
1326 +.os-widgets__chrome .os-widgets__card-close:hover,
1327 +.os-widgets__chrome .os-widgets__card-close:focus-visible {
801 1328 opacity: 1;
802 1329 }
803 1330
804 1331 /*
@@ -808,23 +1335,24 @@
808 1335 * expose it (tapping it on a docked card would be a confusing
809 1336 * no-op). The DOM node stays mounted either way so state flips
810 1337 * don't rebuild chrome.
811 1338 *
812 - * Styling mirrors the inline close button: 20×20 round tile,
1339 + * Styling mirrors the inline close button: 24×24 round tile
1340 + * (the WCAG 2.2 SC 2.5.8 target-size floor),
813 1341 * dimmed by default, full-opacity on hover / focus. Distinct hover
814 1342 * color (theme accent, not red) signals "put back" vs. "remove."
815 1343 */
816 -.desktop-mode-widgets__card-redock {
1344 +.os-widgets__card-redock {
817 1345 display: none;
818 1346 align-items: center;
819 1347 justify-content: center;
820 1348 padding: 0;
821 1349 border: 0;
822 - background: rgba( 0, 0, 0, 0.55 );
1350 + background: var( --os-ui-scrim, rgba( 0, 0, 0, 0.55 ) );
823 1351 color: rgba( 255, 255, 255, 0.75 );
824 1352 border-radius: 50%;
825 - width: 20px;
826 - height: 20px;
1353 + width: 24px;
1354 + height: 24px;
827 1355 cursor: pointer;
828 1356 opacity: 0.7;
829 1357 transition:
830 1358 opacity 0.15s ease,
@@ -831,35 +1359,40 @@
831 1359 background-color 0.15s ease,
832 1360 color 0.15s ease;
833 1361 }
834 1362
835 -.desktop-mode-widgets__card--floating .desktop-mode-widgets__card-redock {
1363 +.os-widgets__card--floating .os-widgets__card-redock {
836 1364 display: flex;
837 1365 }
838 1366
839 -.desktop-mode-widgets__card-redock:hover,
840 -.desktop-mode-widgets__card-redock:focus-visible {
1367 +.os-widgets__card-redock:hover,
1368 +.os-widgets__card-redock:focus-visible {
841 1369 opacity: 1;
842 1370 background: var( --wp-admin-theme-color, #2271b1 );
843 - color: #fff;
1371 + color: var( --os-ui-accent-ink, var( --os-ui-fg-on-accent, #fff ) );
844 1372 }
845 1373
846 1374 /*
847 1375 * Floating widgets — absolute-positioned, inline top/left/width/height
848 - * written by the frame. The hover translate-X effect would fight the
849 - * user's chosen position, so disable it.
1376 + * written by the frame.
850 1377 */
851 -.desktop-mode-widgets__card--floating {
1378 +.os-widgets__card--floating {
852 1379 position: absolute;
853 1380 margin: 0;
854 1381 }
855 1382
856 -.desktop-mode-widgets__card--floating:hover {
857 - transform: none;
1383 +/*
1384 + * A liberated card is reparented to the desktop area, so the column's
1385 + * overview fade above no longer reaches it. Direct children only: a
1386 + * card inside a window body belongs to that window's thumbnail.
1387 + */
1388 +.os-area--overview > .os-widgets__card--floating {
1389 + opacity: 0;
1390 + pointer-events: none;
858 1391 }
859 1392
860 -.desktop-mode-widgets__card--dragging,
861 -.desktop-mode-widgets__card--resizing {
1393 +.os-widgets__card--dragging,
1394 +.os-widgets__card--resizing {
862 1395 transition: none;
863 1396 z-index: 2;
864 1397 }
865 1398
@@ -870,14 +1403,14 @@
870 1403 * every handle; a non-movable widget ignores everything except the
871 1404 * `s` (bottom-edge, height-only) handle at the pointer layer, so we
872 1405 * visually hide the mismatched handles via the modifier class.
873 1406 */
874 -.desktop-mode-widgets__resize {
1407 +.os-widgets__resize {
875 1408 position: absolute;
876 1409 z-index: 1;
877 1410 }
878 1411
879 -.desktop-mode-widgets__resize--n {
1412 +.os-widgets__resize--n {
880 1413 top: -3px;
881 1414 left: 8px;
882 1415 right: 8px;
883 1416 height: 6px;
@@ -883,9 +1416,9 @@
883 1416 height: 6px;
884 1417 cursor: ns-resize;
885 1418 }
886 1419
887 -.desktop-mode-widgets__resize--s {
1420 +.os-widgets__resize--s {
888 1421 bottom: -3px;
889 1422 left: 8px;
890 1423 right: 8px;
891 1424 height: 6px;
@@ -891,9 +1424,9 @@
891 1424 height: 6px;
892 1425 cursor: ns-resize;
893 1426 }
894 1427
895 -.desktop-mode-widgets__resize--e {
1428 +.os-widgets__resize--e {
896 1429 top: 8px;
897 1430 bottom: 8px;
898 1431 right: -3px;
899 1432 width: 6px;
@@ -899,9 +1432,9 @@
899 1432 width: 6px;
900 1433 cursor: ew-resize;
901 1434 }
902 1435
903 -.desktop-mode-widgets__resize--w {
1436 +.os-widgets__resize--w {
904 1437 top: 8px;
905 1438 bottom: 8px;
906 1439 left: -3px;
907 1440 width: 6px;
@@ -907,9 +1440,9 @@
907 1440 width: 6px;
908 1441 cursor: ew-resize;
909 1442 }
910 1443
911 -.desktop-mode-widgets__resize--ne {
1444 +.os-widgets__resize--ne {
912 1445 top: -4px;
913 1446 right: -4px;
914 1447 width: 12px;
915 1448 height: 12px;
@@ -915,9 +1448,9 @@
915 1448 height: 12px;
916 1449 cursor: nesw-resize;
917 1450 }
918 1451
919 -.desktop-mode-widgets__resize--nw {
1452 +.os-widgets__resize--nw {
920 1453 top: -4px;
921 1454 left: -4px;
922 1455 width: 12px;
923 1456 height: 12px;
@@ -923,9 +1456,9 @@
923 1456 height: 12px;
924 1457 cursor: nwse-resize;
925 1458 }
926 1459
927 -.desktop-mode-widgets__resize--se {
1460 +.os-widgets__resize--se {
928 1461 bottom: -4px;
929 1462 right: -4px;
930 1463 width: 12px;
931 1464 height: 12px;
@@ -931,9 +1464,9 @@
931 1464 height: 12px;
932 1465 cursor: nwse-resize;
933 1466 }
934 1467
935 -.desktop-mode-widgets__resize--sw {
1468 +.os-widgets__resize--sw {
936 1469 bottom: -4px;
937 1470 left: -4px;
938 1471 width: 12px;
939 1472 height: 12px;
@@ -940,67 +1473,116 @@
940 1473 cursor: nesw-resize;
941 1474 }
942 1475
943 1476 /*
944 - * Non-movable resizable widgets only expose the bottom-edge handle —
945 - * width stays locked to the column width. Hide the other seven so the
946 - * cursor doesn't lie about what's interactive.
1477 + * Only floating cards expose the full 8-direction handle set. A
1478 + * column-docked card — non-movable OR movable-but-not-yet-liberated —
1479 + * resizes on the height axis alone (the frame ignores every other
1480 + * direction while docked), so hide all handles except the bottom
1481 + * edge and the cursor never lies about what's interactive.
947 1482 */
948 -.desktop-mode-widgets__card--resizable:not( .desktop-mode-widgets__card--movable ) .desktop-mode-widgets__resize:not( .desktop-mode-widgets__resize--s ) {
1483 +.os-widgets__card--resizable:not( .os-widgets__card--floating ) .os-widgets__resize:not( .os-widgets__resize--s ) {
949 1484 display: none;
950 1485 }
951 1486
952 1487 /*
953 - * Add-widget tile — matches the "+" tile in the overview top bar.
954 - * Always visible at the bottom of the column; promoted to center
955 - * when the column is otherwise empty so first-run users see a
956 - * friendly target rather than an empty strip.
1488 + * Add-widget tile — a compact pill that trails the widget stack, not
1489 + * a full-width drop zone. Hidden until the pointer comes near the
1490 + * column (the layer toggles `--hovered`), so the desktop stays clean
1491 + * for people who never touch widgets.
1492 + *
1493 + * Absolute rather than in flow because "the bottom of the stack" is
1494 + * not something the column's layout knows: a widget dragged out of
1495 + * the column becomes a floating card parented to the desktop, so it
1496 + * leaves the flex flow while still sitting visually in the column.
1497 + * The layer measures those too and writes `top` — see
1498 + * `positionAddTile()`.
957 1499 */
958 -.desktop-mode-widgets__add {
959 - margin-top: auto;
960 - padding: 14px 12px;
1500 +.os-widgets__add {
1501 + position: absolute;
1502 + top: 0;
1503 + /* Centred over the cards, not over the column's box: the column
1504 + * pads out unevenly to give the card shadows room (see
1505 + * `.os-widgets`), so the box's own middle is off to one side. */
1506 + inset-inline: var( --_os-widgets-room-start, 0px ) var( --_os-widgets-room-end, 0px );
1507 + width: fit-content;
1508 + margin-inline: auto;
1509 + padding: 8px 22px;
961 1510 display: flex;
962 1511 align-items: center;
963 1512 justify-content: center;
964 - gap: 8px;
965 - pointer-events: auto;
966 - background: transparent;
967 - border: 2px dashed rgba( 255, 255, 255, 0.22 );
968 - border-radius: 14px;
969 - color: rgba( 255, 255, 255, 0.72 );
1513 + gap: 7px;
1514 + pointer-events: none;
1515 + /* `.os-widgets__card`'s glass, to the number: the pill trails a
1516 + stack of those cards. Its dashed edge is what makes it a slot. */
1517 + background: var( --os-widgets-add-bg, transparent );
1518 + backdrop-filter: blur( 18px ) saturate( 140% );
1519 + -webkit-backdrop-filter: blur( 18px ) saturate( 140% );
1520 + box-shadow: 0 8px 28px var( --os-widgets-add-shadow, rgba( 0, 0, 0, 0.35 ) );
1521 + border: 1px dashed var( --os-widgets-add-border, rgba( 255, 255, 255, 0.22 ) );
1522 + border-radius: 10px;
1523 + color: var( --os-ui-color-text, var( --os-fg, #fff ) );
970 1524 font: inherit;
971 1525 font-weight: 500;
972 1526 cursor: pointer;
1527 + opacity: 0;
973 1528 transition:
1529 + opacity 0.15s ease,
974 1530 border-color 0.15s ease,
975 1531 background-color 0.15s ease,
976 1532 color 0.15s ease;
977 1533 }
978 1534
979 -.desktop-mode-widgets__add:hover {
1535 +/*
1536 + * Reveal conditions. An empty column is no exception — approaching
1537 + * the right side is the gesture, whether or not there's a card there
1538 + * to aim at. `:focus-visible` keeps it reachable by keyboard, where
1539 + * there is no pointer to bring near.
1540 + */
1541 +.os-widgets--hovered .os-widgets__add,
1542 +.os-widgets--picking .os-widgets__add,
1543 +.os-widgets__add:focus-visible {
1544 + opacity: 1;
1545 + pointer-events: auto;
1546 +}
1547 +
1548 +/*
1549 + * Touch has no hover to approach the column with. The wallpaper's
1550 + * right-click menu carries an "Add widget" entry, but a long-press
1551 + * to reach it is a lot to ask of someone who just wants a clock, so
1552 + * on those devices the pill stays put.
1553 + */
1554 +@media ( hover: none ) {
1555 + .os-widgets__add {
1556 + opacity: 1;
1557 + pointer-events: auto;
1558 + }
1559 +}
1560 +
1561 +.os-widgets__add:hover {
980 1562 border-color: rgba( 255, 255, 255, 0.4 );
981 - background: rgba( 255, 255, 255, 0.06 );
982 - color: #fff;
1563 + background: var( --os-widgets-add-bg-hover, rgba( 255, 255, 255, 0.06 ) );
1564 + color: var( --os-fg, #fff );
983 1565 }
984 1566
985 -.desktop-mode-widgets__add:focus-visible {
1567 +.os-widgets__add:focus-visible {
986 1568 outline: 2px solid var( --wp-admin-theme-color, #2271b1 );
987 1569 outline-offset: 2px;
988 1570 }
989 1571
990 -.desktop-mode-widgets__add-plus {
991 - font-size: 20px;
1572 +.os-widgets__add-plus {
1573 + font-size: 15px;
992 1574 line-height: 1;
993 - font-weight: 200;
1575 + font-weight: 300;
994 1576 }
995 1577
996 -.desktop-mode-widgets__add-label {
1578 +.os-widgets__add-label {
997 1579 font-size: 13px;
998 1580 letter-spacing: 0.02em;
999 1581 }
1000 1582
1001 1583 /* Built-in clock widget */
1002 -.desktop-mode-widget-clock {
1584 +.os-widget-clock {
1003 1585 text-align: center;
1004 1586 /* The time + date are passive glyphs, not content users would
1005 1587 * ever reasonably select — turning it off avoids the accidental-
1006 1588 * highlight mess that happens when a drag starts on the clock. */
@@ -1007,9 +1589,9 @@
1007 1589 user-select: none;
1008 1590 -webkit-user-select: none;
1009 1591 }
1010 1592
1011 -.desktop-mode-widget-clock__time {
1593 +.os-widget-clock__time {
1012 1594 font-size: 34px;
1013 1595 font-weight: 600;
1014 1596 line-height: 1.1;
1015 1597 font-variant-numeric: tabular-nums;
@@ -1015,12 +1597,12 @@
1015 1597 font-variant-numeric: tabular-nums;
1016 1598 letter-spacing: 0.01em;
1017 1599 }
1018 1600
1019 -.desktop-mode-widget-clock__date {
1601 +.os-widget-clock__date {
1020 1602 margin-top: 4px;
1021 1603 font-size: 13px;
1022 - color: rgba( 255, 255, 255, 0.75 );
1604 + color: var( --os-ui-color-text-subtle, rgba( 255, 255, 255, 0.75 ) );
1023 1605 letter-spacing: 0.02em;
1024 1606 }
1025 1607
1026 1608 /* ---------------------------------------------------------------
@@ -1028,11 +1610,15 @@
1028 1610 * registered widget. Positioned fixed so it can extend outside
1029 1611 * the desktop-area clip.
1030 1612 * --------------------------------------------------------------- */
1031 1613
1032 -.desktop-mode-widget-picker {
1614 +.os-widget-picker {
1033 1615 position: fixed;
1034 - width: 320px;
1616 + /* Border-box so the picker script can cap max-height to the
1617 + * room it measured, frame included. 342 = the 320px list plus
1618 + * the padding and border it always carried. */
1619 + box-sizing: border-box;
1620 + width: 342px;
1035 1621 max-height: 60vh;
1036 1622 overflow-y: auto;
1037 1623 padding: 10px;
1038 1624 border-radius: 14px;
@@ -1040,14 +1626,14 @@
1040 1626 backdrop-filter: blur( 22px ) saturate( 160% );
1041 1627 -webkit-backdrop-filter: blur( 22px ) saturate( 160% );
1042 1628 border: 1px solid rgba( 255, 255, 255, 0.1 );
1043 1629 box-shadow: 0 18px 54px rgba( 0, 0, 0, 0.55 );
1044 - color: #fff;
1630 + color: var( --os-ui-fg-on-accent, #fff );
1045 1631 z-index: 9999;
1046 - animation: desktop-mode-widget-picker-in 0.14s ease-out;
1632 + animation: os-widget-picker-in 0.14s ease-out;
1047 1633 }
1048 1634
1049 -@keyframes desktop-mode-widget-picker-in {
1635 +@keyframes os-widget-picker-in {
1050 1636 from {
1051 1637 opacity: 0;
1052 1638 transform: translateY( 4px );
1053 1639 }
@@ -1052,9 +1638,9 @@
1052 1638 transform: translateY( 4px );
1053 1639 }
1054 1640 }
1055 1641
1056 -.desktop-mode-widget-picker__title {
1642 +.os-widget-picker__title {
1057 1643 padding: 4px 8px 8px;
1058 1644 font-size: 11px;
1059 1645 font-weight: 600;
1060 1646 letter-spacing: 0.08em;
@@ -1061,15 +1647,15 @@
1061 1647 text-transform: uppercase;
1062 1648 color: rgba( 255, 255, 255, 0.55 );
1063 1649 }
1064 1650
1065 -.desktop-mode-widget-picker__list {
1651 +.os-widget-picker__list {
1066 1652 display: flex;
1067 1653 flex-direction: column;
1068 1654 gap: 4px;
1069 1655 }
1070 1656
1071 -.desktop-mode-widget-picker__entry {
1657 +.os-widget-picker__entry {
1072 1658 display: flex;
1073 1659 align-items: center;
1074 1660 gap: 12px;
1075 1661 padding: 10px;
@@ -1075,9 +1661,9 @@
1075 1661 padding: 10px;
1076 1662 background: transparent;
1077 1663 border: 0;
1078 1664 border-radius: 10px;
1079 - color: #fff;
1665 + color: var( --os-ui-fg-on-accent, #fff );
1080 1666 cursor: pointer;
1081 1667 text-align: start;
1082 1668 font: inherit;
1083 1669 transition: background-color 0.12s ease;
@@ -1082,23 +1668,23 @@
1082 1668 font: inherit;
1083 1669 transition: background-color 0.12s ease;
1084 1670 }
1085 1671
1086 -.desktop-mode-widget-picker__entry:hover:not( :disabled ) {
1672 +.os-widget-picker__entry:hover:not( :disabled ) {
1087 1673 background: rgba( 255, 255, 255, 0.08 );
1088 1674 }
1089 1675
1090 -.desktop-mode-widget-picker__entry:focus-visible {
1676 +.os-widget-picker__entry:focus-visible {
1091 1677 outline: 2px solid var( --wp-admin-theme-color, #2271b1 );
1092 1678 outline-offset: 1px;
1093 1679 }
1094 1680
1095 -.desktop-mode-widget-picker__entry--added {
1681 +.os-widget-picker__entry--added {
1096 1682 opacity: 0.55;
1097 1683 cursor: default;
1098 1684 }
1099 1685
1100 -.desktop-mode-widget-picker__entry-icon {
1686 +.os-widget-picker__entry-icon {
1101 1687 flex-shrink: 0;
1102 1688 font-size: 20px;
1103 1689 width: 20px;
1104 1690 height: 20px;
@@ -1104,9 +1690,9 @@
1104 1690 height: 20px;
1105 1691 line-height: 1;
1106 1692 }
1107 1693
1108 -.desktop-mode-widget-picker__entry-text {
1694 +.os-widget-picker__entry-text {
1109 1695 display: flex;
1110 1696 flex-direction: column;
1111 1697 gap: 2px;
1112 1698 flex: 1;
@@ -1112,9 +1698,9 @@
1112 1698 flex: 1;
1113 1699 min-width: 0;
1114 1700 }
1115 1701
1116 -.desktop-mode-widget-picker__entry-label {
1702 +.os-widget-picker__entry-label {
1117 1703 font-size: 13px;
1118 1704 font-weight: 500;
1119 1705 white-space: nowrap;
1120 1706 overflow: hidden;
@@ -1120,9 +1706,9 @@
1120 1706 overflow: hidden;
1121 1707 text-overflow: ellipsis;
1122 1708 }
1123 1709
1124 -.desktop-mode-widget-picker__entry-description {
1710 +.os-widget-picker__entry-description {
1125 1711 font-size: 11px;
1126 1712 color: rgba( 255, 255, 255, 0.6 );
1127 1713 line-height: 1.35;
1128 1714 white-space: normal;
@@ -1127,9 +1713,9 @@
1127 1713 line-height: 1.35;
1128 1714 white-space: normal;
1129 1715 }
1130 1716
1131 -.desktop-mode-widget-picker__entry-status {
1717 +.os-widget-picker__entry-status {
1132 1718 flex-shrink: 0;
1133 1719 font-size: 11px;
1134 1720 color: rgba( 255, 255, 255, 0.5 );
1135 1721 text-transform: uppercase;
@@ -1135,9 +1721,9 @@
1135 1721 text-transform: uppercase;
1136 1722 letter-spacing: 0.08em;
1137 1723 }
1138 1724
1139 -.desktop-mode-widget-picker__empty {
1725 +.os-widget-picker__empty {
1140 1726 padding: 12px 8px;
1141 1727 font-size: 12px;
1142 1728 color: rgba( 255, 255, 255, 0.6 );
1143 1729 line-height: 1.4;
@@ -1146,12 +1732,12 @@
1146 1732 /**
1147 1733 * Chromeless mode: pages loaded inside iframes.
1148 1734 * Remove all shell chrome and let content fill the frame.
1149 1735 */
1150 -.desktop-mode-chromeless {
1736 +.os-chromeless {
1151 1737 margin: 0;
1152 1738 padding: 0;
1153 - background: var(--desktop-mode-window-bg);
1739 + background: var(--os-window-bg);
1154 1740 }
1155 1741
1156 1742 /*
1157 1743 * Chromeless #wpbody-content, #adminmenuwrap, #wpfooter overrides are in
@@ -1159,9 +1745,9 @@
1159 1745 */
1160 1746
1161 1747 /*
1162 1748 * Hide WordPress core's built-in command palette (`@wordpress/commands`).
1163 - * Desktop mode force-enqueues `wp_enqueue_command_palette_assets()` so
1749 + * OpenStation force-enqueues `wp_enqueue_command_palette_assets()` so
1164 1750 * the `core/commands` data store is populated for our shell harvester
1165 1751 * (see `src/commands/shell-harvester.ts`); the side effect is that WP
1166 1752 * also mounts its own `<CommandPalette>` to the document body. We
1167 1753 * already block its Cmd+K handler in `src/palette-registry.ts`, but if
@@ -1172,5 +1758,504 @@
1172 1758 */
1173 1759 .commands-command-menu,
1174 1760 .commands-command-menu__overlay {
1175 1761 display: none !important;
1762 +}
1763 +
1764 +/*
1765 + * ---- Links slotted into <os-notice> ---------------------------
1766 + *
1767 + * `<os-notice>` styles its slotted links from inside its shadow root,
1768 + * through `::slotted( a )` and the `--os-ui-notice-link` tokens. That
1769 + * rule cannot win here, and no amount of specificity on it would help.
1770 + *
1771 + * A slotted element lives in the DOCUMENT tree; the shadow root only
1772 + * borrows it for rendering. When declarations from two trees collide,
1773 + * CSS Scoping resolves normal (non-`!important`) ones in favour of the
1774 + * OUTER tree regardless of specificity — so `wp-admin/css/common.css`,
1775 + * which sets `a { color: #2271b1 }` and `a:hover { color: #135e96 }` on
1776 + * every anchor in the admin, beats `::slotted( a )` every time. The
1777 + * shell renders inside wp-admin, so it always loses: the link painted
1778 + * WordPress Blue at rest and a darker blue on hover, the second of
1779 + * which is close to illegible on a notice's dark wash.
1780 + *
1781 + * Hence a document-tree rule. It reads the same tokens the component
1782 + * documents, so a theme still restyles the link by setting them; this
1783 + * only moves the declaration into a tree that can win. `a:hover` is
1784 + * (0,1,1), so the hover selector has to carry its own pseudo-class to
1785 + * outrank it — matching `os-notice a` alone would lose the hover state
1786 + * while winning the base one, which is exactly the inert-looking link
1787 + * the component's own styles already went out of their way to avoid.
1788 + */
1789 +os-notice a {
1790 + color: var(--os-ui-notice-link, #ec9bff);
1791 +}
1792 +
1793 +os-notice a:hover,
1794 +os-notice a:focus,
1795 +os-notice a:active {
1796 + color: var(--os-ui-notice-link-hover, #fffbff);
1797 +}
1798 +
1799 +/* --------------------------------------------------------------------
1800 + * The workspace hop — cross-document view transitions between shells.
1801 + *
1802 + * Loaded only on the SHELL screen (this sheet never reaches chromeless
1803 + * iframes), so only shell→shell navigations transition: hopping between
1804 + * a site's desktop and the network admin's crossfades the two desktops
1805 + * instead of hard-cutting, which is what makes the per-admin sessions
1806 + * read as workspaces. Classic admin pages never opt in, so entering or
1807 + * leaving the shell stays a plain navigation, and reloads are excluded
1808 + * by the spec. Browsers without cross-document view transitions ignore
1809 + * all of this and navigate plainly. See docs/multisite.md.
1810 + */
1811 +@view-transition {
1812 + navigation: auto;
1813 +}
1814 +
1815 +/* Reduced motion swaps instantly — the hop still happens, the
1816 + * animation does not. */
1817 +@media ( prefers-reduced-motion: reduce ) {
1818 + @view-transition {
1819 + navigation: none;
1820 + }
1821 +}
1822 +
1823 +/* A gentle zoom-through: the desktop being left recedes as the one
1824 + * arriving settles in. Subtle on purpose — this runs on a full page
1825 + * swap, and anything louder reads as a reload effect. */
1826 +::view-transition-old(root) {
1827 + animation: os-workspace-hop-out 220ms cubic-bezier( 0.4, 0, 1, 1 ) both;
1828 +}
1829 +
1830 +::view-transition-new(root) {
1831 + animation: os-workspace-hop-in 280ms cubic-bezier( 0, 0, 0.2, 1 ) both;
1832 +}
1833 +
1834 +@keyframes os-workspace-hop-out {
1835 + to {
1836 + opacity: 0;
1837 + transform: scale( 0.985 );
1838 + }
1839 +}
1840 +
1841 +@keyframes os-workspace-hop-in {
1842 + from {
1843 + opacity: 0;
1844 + transform: scale( 1.015 );
1845 + }
1846 +}
1847 +
1848 +/* The instance hop's two halves, on either side of that page swap.
1849 + * The switcher slides this desk out towards the site it picked
1850 + * (`os-shell--hop-out-next` / `-prev`, for the beat before it
1851 + * navigates), and a shell asked to boot into overview arrives with its
1852 + * desk hidden (`os-shell--arriving`, stamped server-side) until overview
1853 + * is up, then slides it in from the same side (`-next` / `-prev`, the
1854 + * hint the switcher left in sessionStorage; no hint, a plain fade). The
1855 + * wallpaper never moves, which is what makes it read as the tiles
1856 + * changing rather than the page. `src/multisite/instance-transition.ts`
1857 + * drives the classes. */
1858 +.os-shell--hop-out-next #os-area,
1859 +.os-shell--hop-out-prev #os-area {
1860 + opacity: 0;
1861 + transition:
1862 + opacity 220ms cubic-bezier( 0.4, 0, 1, 1 ),
1863 + transform 220ms cubic-bezier( 0.4, 0, 1, 1 );
1864 +}
1865 +
1866 +.os-shell--hop-out-next #os-area {
1867 + transform: translateX( -48px );
1868 +}
1869 +
1870 +.os-shell--hop-out-prev #os-area {
1871 + transform: translateX( 48px );
1872 +}
1873 +
1874 +.os-shell--hop-out-next .os-dock,
1875 +.os-shell--hop-out-prev .os-dock,
1876 +.os-shell--arriving .os-dock {
1877 + opacity: 0;
1878 + transition: opacity 220ms ease;
1879 +}
1880 +
1881 +.os-shell--arriving #os-area {
1882 + opacity: 0;
1883 + transition: none;
1884 +}
1885 +
1886 +.os-shell--arriving-next #os-area {
1887 + transform: translateX( 48px );
1888 +}
1889 +
1890 +.os-shell--arriving-prev #os-area {
1891 + transform: translateX( -48px );
1892 +}
1893 +
1894 +/* The reveal: the arriving classes come off and this goes on in the
1895 + * same frame, so the desk transitions from hidden to its resting
1896 + * place. */
1897 +.os-shell--revealing #os-area {
1898 + transition:
1899 + opacity 360ms cubic-bezier( 0, 0, 0.2, 1 ),
1900 + transform 360ms cubic-bezier( 0, 0, 0.2, 1 );
1901 +}
1902 +
1903 +.os-shell--revealing .os-dock {
1904 + transition: opacity 360ms ease;
1905 +}
1906 +
1907 +/* A desk must never stay hidden: if the boot that reveals it never
1908 + * runs, the area and the dock come back on their own a few seconds
1909 + * in. */
1910 +@keyframes os-instance-arrive-fallback {
1911 + to {
1912 + opacity: 1;
1913 + transform: none;
1914 + }
1915 +}
1916 +
1917 +.os-shell--arriving #os-area,
1918 +.os-shell--arriving .os-dock {
1919 + animation: os-instance-arrive-fallback 1ms linear 6s forwards;
1920 +}
1921 +
1922 +@media ( prefers-reduced-motion: reduce ) {
1923 + .os-shell--hop-out-next #os-area,
1924 + .os-shell--hop-out-prev #os-area,
1925 + .os-shell--arriving-next #os-area,
1926 + .os-shell--arriving-prev #os-area {
1927 + transform: none;
1928 + }
1929 +
1930 + .os-shell--hop-out-next #os-area,
1931 + .os-shell--hop-out-prev #os-area,
1932 + .os-shell--hop-out-next .os-dock,
1933 + .os-shell--hop-out-prev .os-dock,
1934 + .os-shell--revealing #os-area,
1935 + .os-shell--revealing .os-dock {
1936 + transition: none;
1937 + }
1938 +}
1939 +
1940 +/* A residency frame follows the window body without scrolling with its contents. */
1941 +.os-mio-residence {
1942 + position: absolute;
1943 + z-index: 50;
1944 + pointer-events: none;
1945 + overflow: hidden;
1946 + container-type: inline-size;
1947 +}
1948 +
1949 +.os-mio-residence[hidden],
1950 +.os-mio-chat-launcher[hidden] {
1951 + display: none;
1952 +}
1953 +
1954 +.os-mio-chat-launcher {
1955 + position: absolute;
1956 + inset-inline-end: 20px;
1957 + inset-block-end: 18px;
1958 + pointer-events: auto;
1959 +}
1960 +
1961 +.os-mio-chat {
1962 + position: absolute;
1963 + inset-inline-end: 16px;
1964 + inset-block-end: 16px;
1965 + inline-size: min(380px, calc(100% - 32px));
1966 + max-block-size: calc(100% - 32px);
1967 + box-sizing: border-box;
1968 + display: flex;
1969 + flex-direction: column;
1970 + gap: 12px;
1971 + padding: 18px;
1972 + pointer-events: auto;
1973 + color: var(--os-mio-chat-fg, #1d2327);
1974 + background: var(--os-mio-chat-bg, #fff);
1975 + border: 1px solid var(--os-mio-chat-border, #c3c4c7);
1976 + border-radius: var(--os-mio-chat-radius, 16px);
1977 + box-shadow: 0 8px 40px var(--os-mio-chat-glow, #00000020);
1978 + animation: os-mio-chat-enter 180ms ease-out;
1979 +}
1980 +
1981 +.os-mio-chat header {
1982 + display: flex;
1983 + align-items: center;
1984 + gap: 12px;
1985 +}
1986 +
1987 +.os-mio-chat header strong {
1988 + letter-spacing: .14em;
1989 +}
1990 +
1991 +.os-mio-chat header span {
1992 + flex: 1;
1993 + font-size: 11px;
1994 + color: var(--os-mio-chat-muted, #646970);
1995 +}
1996 +
1997 +.os-mio-chat__log {
1998 + position: relative;
1999 + min-block-size: 60px;
2000 + max-block-size: 300px;
2001 + overflow: auto;
2002 + overscroll-behavior: contain;
2003 +}
2004 +
2005 +.os-mio-chat__message {
2006 + margin-block: 0 10px;
2007 + padding: 10px 12px;
2008 + line-height: 1.6;
2009 + white-space: pre-wrap;
2010 + overflow-wrap: anywhere;
2011 +}
2012 +
2013 +.os-mio-chat__message--user {
2014 + border-radius: 16px 16px 4px 16px;
2015 + background: var(--os-mio-chat-user-bg, #f0f0f1);
2016 +}
2017 +
2018 +.os-mio-chat__composer {
2019 + display: flex;
2020 + align-items: center;
2021 + gap: 8px;
2022 +}
2023 +
2024 +.os-mio-chat__composer os-textarea {
2025 + flex: 1;
2026 + min-inline-size: 0;
2027 +}
2028 +
2029 +.os-mio-chat__status,
2030 +.os-mio-chat small {
2031 + margin: 0;
2032 + font-size: 11px;
2033 + line-height: 1.5;
2034 + color: var(--os-mio-chat-muted, #646970);
2035 +}
2036 +
2037 +@keyframes os-mio-chat-enter {
2038 + from { opacity: 0; transform: translateY(6px) scale(.98); }
2039 + to { opacity: 1; transform: translateY(0) scale(1); }
2040 +}
2041 +
2042 +@media (prefers-reduced-motion: reduce) {
2043 + .os-mio-chat { animation: none; }
2044 +}
2045 +
2046 +.os-mio-residence > .os-mio { z-index: 0; }
2047 +.os-mio-chat, .os-mio-chat-launcher { z-index: 1; }
2048 +
2049 +.os-mio-chat [hidden] {
2050 + display: none !important;
2051 +}
2052 +
2053 +.os-mio-chat__message--assistant {
2054 + white-space: normal;
2055 +}
2056 +
2057 +.os-mio-chat__message p {
2058 + margin-block: 0 8px;
2059 +}
2060 +
2061 +.os-mio-chat__message ul,
2062 +.os-mio-chat__message ol {
2063 + margin-block: 8px;
2064 + padding-inline-start: 20px;
2065 +}
2066 +
2067 +.os-mio-chat__message a {
2068 + color: inherit;
2069 + text-decoration: underline;
2070 +}
2071 +
2072 +/* Shared MIO chrome: the same portrait with a softly revealed off-state slash. */
2073 +.os-mio-window-toggle svg {
2074 + width: 20px;
2075 + height: 20px;
2076 + overflow: visible;
2077 +}
2078 +
2079 +.os-mio-window-toggle__slash {
2080 + fill: none;
2081 + stroke: currentColor;
2082 + stroke-width: 2.4;
2083 + stroke-linecap: round;
2084 + opacity: 0;
2085 + stroke-dasharray: 26;
2086 + stroke-dashoffset: 26;
2087 + transition: opacity 240ms ease, stroke-dashoffset 240ms ease;
2088 +}
2089 +
2090 +.os-mio-window-toggle[data-mio-disabled="true"] .os-mio-window-toggle__slash {
2091 + opacity: 1;
2092 + stroke-dashoffset: 0;
2093 +}
2094 +
2095 +.os-mio-chat__activity {
2096 + display: flex;
2097 + align-items: center;
2098 + gap: 8px;
2099 + min-height: 18px;
2100 +}
2101 +
2102 +.os-mio-chat__thinking {
2103 + display: inline-flex;
2104 + align-items: center;
2105 + gap: 3px;
2106 + width: 24px;
2107 + flex-shrink: 0;
2108 + opacity: 0;
2109 + color: var(--os-mio-chat-muted, #646970);
2110 + transition: opacity 240ms ease;
2111 +}
2112 +
2113 +.os-mio-chat[data-thinking="true"] .os-mio-chat__thinking {
2114 + opacity: 1;
2115 +}
2116 +
2117 +.os-mio-chat__thinking i {
2118 + width: 4px;
2119 + height: 4px;
2120 + border-radius: 50%;
2121 + background: currentColor;
2122 + animation: os-mio-thinking 1.6s ease-in-out infinite;
2123 + animation-play-state: paused;
2124 +}
2125 +
2126 +.os-mio-chat__thinking i:nth-child(2) { animation-delay: 160ms; }
2127 +.os-mio-chat__thinking i:nth-child(3) { animation-delay: 320ms; }
2128 +.os-mio-chat[data-thinking="true"] .os-mio-chat__thinking i { animation-play-state: running; }
2129 +.os-mio-window-toggle[data-mio-thinking="true"] circle { animation: os-mio-thinking 2.4s ease-in-out infinite; }
2130 +
2131 +@keyframes os-mio-thinking {
2132 + 0%, 100% { opacity: 0.45; }
2133 + 50% { opacity: 1; }
2134 +}
2135 +
2136 +@media (prefers-reduced-motion: reduce) {
2137 + .os-mio-window-toggle__slash,
2138 + .os-mio-chat__thinking { transition: none; }
2139 + .os-mio-chat__thinking i,
2140 + .os-mio-window-toggle[data-mio-thinking="true"] circle { animation: none; }
2141 +}
2142 +
2143 +.os-mio-window-toggle {
2144 + max-inline-size: 30px;
2145 + opacity: 1;
2146 + visibility: visible;
2147 + transition: opacity 180ms ease, max-inline-size 240ms ease, visibility 0s;
2148 +}
2149 +
2150 +.os-mio-window-toggle[data-mio-available="false"] {
2151 + max-inline-size: 0;
2152 + opacity: 0;
2153 + visibility: hidden;
2154 + overflow: hidden;
2155 + pointer-events: none;
2156 + transition: opacity 180ms ease, max-inline-size 240ms ease, visibility 0s 180ms;
2157 +}
2158 +
2159 +@media (prefers-reduced-motion: reduce) {
2160 + .os-mio-window-toggle,
2161 + .os-mio-window-toggle[data-mio-available="false"] { transition: none; }
2162 +}
2163 +
2164 +/* The launcher stays available; the companion only speaks when invited. */
2165 +.os-mio > canvas,
2166 +.os-mio > .os-mio__handle {
2167 + transition: opacity 180ms ease, visibility 180ms;
2168 +}
2169 +
2170 +.os-mio[data-mio-visible="false"] > canvas,
2171 +.os-mio[data-mio-visible="false"] > .os-mio__handle {
2172 + opacity: 0;
2173 + visibility: hidden;
2174 + pointer-events: none;
2175 +}
2176 +
2177 +.os-mio-callout {
2178 + position: absolute;
2179 + z-index: 2;
2180 + display: flex;
2181 + align-items: center;
2182 + gap: 10px;
2183 + max-inline-size: calc(100% - 16px);
2184 + box-sizing: border-box;
2185 + padding-block: 6px;
2186 + padding-inline: 15px 6px;
2187 + border: 1px solid var(--os-mio-callout-border, #d6b8cb);
2188 + border-radius: 22px;
2189 + background: var(--os-mio-callout-bg, #ffe0cf);
2190 + color: var(--os-mio-callout-fg, #382b38);
2191 + box-shadow: 0 4px 16px var(--os-mio-chat-glow, #00000020);
2192 + font-size: 12px;
2193 + line-height: 1.5;
2194 + font-weight: 500;
2195 + pointer-events: auto;
2196 + animation: os-mio-chat-enter 180ms ease-out;
2197 +}
2198 +
2199 +.os-mio-callout os-button::part(button) {
2200 + inline-size: 26px;
2201 + block-size: 26px;
2202 + font-size: 17px;
2203 + line-height: 1;
2204 +}
2205 +
2206 +/* A small rounded tail joins the companion without a second outlined shape. */
2207 +.os-mio-callout::after {
2208 + content: "";
2209 + position: absolute;
2210 + inset-block-end: -4px;
2211 + inset-inline-end: 18px;
2212 + inline-size: 8px;
2213 + block-size: 8px;
2214 + background: inherit;
2215 + border-inline-end: inherit;
2216 + border-block-end: inherit;
2217 + border-end-end-radius: 3px;
2218 + transform: rotate(45deg);
2219 +}
2220 +
2221 +.os-mio-callout[hidden] { display: none; }
2222 +
2223 +@media (prefers-reduced-motion: reduce) {
2224 + .os-mio > canvas,
2225 + .os-mio > .os-mio__handle { transition: none; }
2226 + .os-mio-callout { animation: none; }
2227 +}
2228 +
2229 +/* Response controls belong to their message; all layout follows inline flow. */
2230 +.os-mio-chat__actions {
2231 + display: flex;
2232 + flex-wrap: wrap;
2233 + gap: 8px;
2234 + margin-block-start: 12px;
2235 +}
2236 +
2237 +.os-mio-chat__action {
2238 + display: flex;
2239 + flex-direction: column;
2240 + align-items: flex-start;
2241 + gap: 4px;
2242 + min-inline-size: 0;
2243 + max-inline-size: 100%;
2244 +}
2245 +
2246 +.os-mio-chat__action os-button::part(button) {
2247 + white-space: normal;
2248 + overflow-wrap: anywhere;
2249 +}
2250 +
2251 +.os-mio-chat__action-status {
2252 + font-size: 12px;
2253 + color: var(--os-mio-chat-muted, #646970);
2254 + overflow-wrap: anywhere;
2255 +}
2256 +
2257 +.os-mio-chat__composer os-textarea::part(textarea) {
2258 + white-space: pre-wrap;
2259 + overflow-wrap: anywhere;
2260 + overflow-x: hidden;
1176 2261 }