feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
<!DOCTYPE html>
|
|
|
|
|
|
<html lang="en">
|
|
|
|
|
|
<head>
|
|
|
|
|
|
<meta charset="utf-8" />
|
|
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
|
|
|
|
|
<title>WEFT Desktop</title>
|
|
|
|
|
|
<style>
|
|
|
|
|
|
:root {
|
|
|
|
|
|
color-scheme: dark;
|
|
|
|
|
|
--surface-bg: rgba(255, 255, 255, 0.07);
|
|
|
|
|
|
--surface-border: rgba(255, 255, 255, 0.12);
|
2026-10-09 16:00:38 +00:00
|
|
|
|
/* weft-servo-shell reserves this strip (TASKBAR_HEIGHT); keep them equal. */
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
--taskbar-height: 48px;
|
|
|
|
|
|
--text-primary: rgba(255, 255, 255, 0.92);
|
|
|
|
|
|
--text-secondary: rgba(255, 255, 255, 0.55);
|
|
|
|
|
|
--accent: #5b8af5;
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
--focus-ring: #9db8ff;
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
*, *::before, *::after {
|
|
|
|
|
|
box-sizing: border-box;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
body {
|
|
|
|
|
|
margin: 0;
|
|
|
|
|
|
overflow: hidden;
|
|
|
|
|
|
background: #0f1117;
|
|
|
|
|
|
font-family: system-ui, -apple-system, sans-serif;
|
|
|
|
|
|
color: var(--text-primary);
|
|
|
|
|
|
height: 100dvh;
|
|
|
|
|
|
width: 100dvw;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-desktop {
|
|
|
|
|
|
display: grid;
|
|
|
|
|
|
grid-template-rows: 1fr var(--taskbar-height);
|
|
|
|
|
|
height: 100dvh;
|
|
|
|
|
|
width: 100dvw;
|
|
|
|
|
|
contain: layout;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-wallpaper {
|
|
|
|
|
|
display: block;
|
|
|
|
|
|
grid-row: 1;
|
|
|
|
|
|
background: linear-gradient(
|
|
|
|
|
|
145deg,
|
|
|
|
|
|
#0f1117 0%,
|
|
|
|
|
|
#161b2e 40%,
|
|
|
|
|
|
#0d2040 70%,
|
|
|
|
|
|
#0a1a30 100%
|
|
|
|
|
|
);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-taskbar {
|
|
|
|
|
|
display: flex;
|
|
|
|
|
|
align-items: center;
|
|
|
|
|
|
grid-row: 2;
|
|
|
|
|
|
height: var(--taskbar-height);
|
|
|
|
|
|
padding: 0 12px;
|
|
|
|
|
|
gap: 8px;
|
|
|
|
|
|
background: var(--surface-bg);
|
|
|
|
|
|
border-top: 1px solid var(--surface-border);
|
|
|
|
|
|
backdrop-filter: blur(20px);
|
|
|
|
|
|
-webkit-backdrop-filter: blur(20px);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
button {
|
|
|
|
|
|
font: inherit;
|
|
|
|
|
|
color: inherit;
|
|
|
|
|
|
border: 0;
|
|
|
|
|
|
margin: 0;
|
|
|
|
|
|
background: transparent;
|
|
|
|
|
|
cursor: pointer;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
:focus-visible {
|
|
|
|
|
|
outline: 2px solid var(--focus-ring);
|
|
|
|
|
|
outline-offset: 2px;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
#launcher-btn {
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
display: flex;
|
|
|
|
|
|
align-items: center;
|
|
|
|
|
|
justify-content: center;
|
|
|
|
|
|
width: 36px;
|
|
|
|
|
|
height: 36px;
|
|
|
|
|
|
border-radius: 8px;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
#launcher-btn:hover {
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
background: var(--surface-border);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-taskbar-clock {
|
|
|
|
|
|
margin-left: auto;
|
|
|
|
|
|
font-size: 13px;
|
|
|
|
|
|
color: var(--text-secondary);
|
|
|
|
|
|
font-variant-numeric: tabular-nums;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-launcher {
|
|
|
|
|
|
display: none;
|
|
|
|
|
|
position: fixed;
|
|
|
|
|
|
inset: 0;
|
|
|
|
|
|
bottom: var(--taskbar-height);
|
|
|
|
|
|
background: rgba(10, 12, 20, 0.85);
|
|
|
|
|
|
backdrop-filter: blur(32px);
|
|
|
|
|
|
-webkit-backdrop-filter: blur(32px);
|
|
|
|
|
|
z-index: 100;
|
2026-03-11 10:23:46 +00:00
|
|
|
|
padding: 24px;
|
|
|
|
|
|
overflow-y: auto;
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-launcher:not([hidden]) {
|
|
|
|
|
|
display: block;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2026-03-11 10:23:46 +00:00
|
|
|
|
weft-app-grid {
|
|
|
|
|
|
display: grid;
|
|
|
|
|
|
grid-template-columns: repeat(auto-fill, minmax(96px, 1fr));
|
|
|
|
|
|
gap: 16px;
|
|
|
|
|
|
max-width: 640px;
|
|
|
|
|
|
margin: 0 auto;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
.app-icon {
|
2026-03-11 10:23:46 +00:00
|
|
|
|
display: flex;
|
|
|
|
|
|
flex-direction: column;
|
|
|
|
|
|
align-items: center;
|
|
|
|
|
|
gap: 6px;
|
|
|
|
|
|
padding: 12px 8px;
|
|
|
|
|
|
border-radius: 12px;
|
|
|
|
|
|
color: var(--text-primary);
|
|
|
|
|
|
font-size: 12px;
|
|
|
|
|
|
text-align: center;
|
|
|
|
|
|
word-break: break-word;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
.app-icon:hover {
|
2026-03-11 10:23:46 +00:00
|
|
|
|
background: var(--surface-border);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
.app-icon svg {
|
2026-03-11 10:23:46 +00:00
|
|
|
|
flex-shrink: 0;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2026-03-11 10:40:25 +00:00
|
|
|
|
weft-taskbar-app {
|
|
|
|
|
|
display: inline-flex;
|
|
|
|
|
|
align-items: center;
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
gap: 2px;
|
2026-03-11 10:40:25 +00:00
|
|
|
|
font-size: 12px;
|
|
|
|
|
|
color: var(--text-secondary);
|
|
|
|
|
|
border-radius: 6px;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-taskbar-app:hover {
|
|
|
|
|
|
background: var(--surface-border);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
weft-taskbar-app .task-activate {
|
|
|
|
|
|
padding: 4px 2px 4px 6px;
|
|
|
|
|
|
border-radius: 6px;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2026-03-11 10:40:25 +00:00
|
|
|
|
weft-taskbar-app .task-close {
|
|
|
|
|
|
opacity: 0;
|
|
|
|
|
|
font-size: 11px;
|
|
|
|
|
|
line-height: 1;
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
padding: 3px 4px;
|
2026-03-11 10:40:25 +00:00
|
|
|
|
border-radius: 3px;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
/* Shown on hover and whenever the entry has keyboard focus. */
|
|
|
|
|
|
weft-taskbar-app:hover .task-close,
|
|
|
|
|
|
weft-taskbar-app:focus-within .task-close {
|
2026-03-11 10:40:25 +00:00
|
|
|
|
opacity: 1;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-taskbar-app .task-close:hover {
|
|
|
|
|
|
background: rgba(255,80,80,0.3);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
weft-taskbar-app .task-close.force {
|
|
|
|
|
|
color: #ff6b6b;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
weft-notification-center {
|
|
|
|
|
|
position: fixed;
|
|
|
|
|
|
top: 8px;
|
|
|
|
|
|
right: 8px;
|
|
|
|
|
|
width: 360px;
|
|
|
|
|
|
display: flex;
|
|
|
|
|
|
flex-direction: column;
|
|
|
|
|
|
gap: 8px;
|
|
|
|
|
|
z-index: 200;
|
|
|
|
|
|
pointer-events: none;
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
weft-window {
|
|
|
|
|
|
display: none;
|
|
|
|
|
|
}
|
|
|
|
|
|
</style>
|
|
|
|
|
|
</head>
|
|
|
|
|
|
<body>
|
|
|
|
|
|
<weft-desktop>
|
|
|
|
|
|
<weft-wallpaper></weft-wallpaper>
|
|
|
|
|
|
<weft-taskbar>
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
<button id="launcher-btn" type="button" title="Apps" aria-label="Apps"
|
|
|
|
|
|
aria-haspopup="dialog" aria-expanded="false" aria-controls="launcher">
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
<svg width="18" height="18" viewBox="0 0 18 18" fill="none"
|
|
|
|
|
|
xmlns="http://www.w3.org/2000/svg" aria-hidden="true">
|
|
|
|
|
|
<rect x="1" y="1" width="6" height="6" rx="1.5"
|
|
|
|
|
|
fill="rgba(255,255,255,0.7)" />
|
|
|
|
|
|
<rect x="11" y="1" width="6" height="6" rx="1.5"
|
|
|
|
|
|
fill="rgba(255,255,255,0.7)" />
|
|
|
|
|
|
<rect x="1" y="11" width="6" height="6" rx="1.5"
|
|
|
|
|
|
fill="rgba(255,255,255,0.7)" />
|
|
|
|
|
|
<rect x="11" y="11" width="6" height="6" rx="1.5"
|
|
|
|
|
|
fill="rgba(255,255,255,0.7)" />
|
|
|
|
|
|
</svg>
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
</button>
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
<weft-taskbar-clock id="clock"></weft-taskbar-clock>
|
|
|
|
|
|
</weft-taskbar>
|
|
|
|
|
|
</weft-desktop>
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
<weft-launcher hidden id="launcher" tabindex="-1" role="dialog" aria-modal="true" aria-label="Apps">
|
2026-03-11 10:23:46 +00:00
|
|
|
|
<weft-app-grid id="app-grid"></weft-app-grid>
|
|
|
|
|
|
</weft-launcher>
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
<weft-notification-center id="notifications" role="status" aria-live="polite"></weft-notification-center>
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
|
|
|
|
|
|
<script>
|
|
|
|
|
|
(function () {
|
|
|
|
|
|
var clockEl = document.getElementById('clock');
|
|
|
|
|
|
function updateClock() {
|
|
|
|
|
|
clockEl.textContent = new Date().toLocaleTimeString([], {
|
|
|
|
|
|
hour: '2-digit',
|
|
|
|
|
|
minute: '2-digit',
|
|
|
|
|
|
});
|
|
|
|
|
|
}
|
|
|
|
|
|
updateClock();
|
|
|
|
|
|
setInterval(updateClock, 10000);
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
var launcher = document.getElementById('launcher');
|
|
|
|
|
|
var launcherBtn = document.getElementById('launcher-btn');
|
|
|
|
|
|
var appGrid = document.getElementById('app-grid');
|
|
|
|
|
|
|
|
|
|
|
|
function launcherOpen() {
|
|
|
|
|
|
return !launcher.hasAttribute('hidden');
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
// Opening the launcher moves keyboard focus into it; closing it
|
|
|
|
|
|
// returns focus to the Apps button.
|
|
|
|
|
|
function openLauncher() {
|
|
|
|
|
|
launcher.removeAttribute('hidden');
|
|
|
|
|
|
launcherBtn.setAttribute('aria-expanded', 'true');
|
|
|
|
|
|
focusInLauncher(null);
|
|
|
|
|
|
if (ws && ws.readyState === WebSocket.OPEN) {
|
|
|
|
|
|
ws.send(JSON.stringify({ type: 'QUERY_INSTALLED_APPS' }));
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
}
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
function closeLauncher() {
|
|
|
|
|
|
if (!launcherOpen()) return;
|
|
|
|
|
|
launcher.setAttribute('hidden', '');
|
|
|
|
|
|
launcherBtn.setAttribute('aria-expanded', 'false');
|
|
|
|
|
|
launcherBtn.focus();
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
// Focuses the icon of `appId`, else the first one, else the dialog.
|
|
|
|
|
|
function focusInLauncher(appId) {
|
|
|
|
|
|
var icons = appGrid.querySelectorAll('.app-icon');
|
|
|
|
|
|
var target = null;
|
|
|
|
|
|
icons.forEach(function (icon) {
|
|
|
|
|
|
if (icon.dataset.appId === appId) target = icon;
|
|
|
|
|
|
});
|
|
|
|
|
|
(target || icons[0] || launcher).focus();
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
launcherBtn.addEventListener('click', function () {
|
|
|
|
|
|
if (launcherOpen()) closeLauncher(); else openLauncher();
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
});
|
2026-03-11 08:01:54 +00:00
|
|
|
|
|
2026-03-11 10:39:21 +00:00
|
|
|
|
document.addEventListener('keydown', function (e) {
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
// The compositor brings the shell to the front when a Super key is
|
|
|
|
|
|
// tapped, then delivers the tap here; it opens or closes the
|
|
|
|
|
|
// launcher.
|
|
|
|
|
|
if (e.key === 'Meta' && !e.repeat && !e.altKey && !e.ctrlKey && !e.shiftKey) {
|
|
|
|
|
|
e.preventDefault();
|
|
|
|
|
|
if (launcherOpen()) closeLauncher(); else openLauncher();
|
|
|
|
|
|
} else if (e.key === 'Escape' && launcherOpen()) {
|
|
|
|
|
|
e.preventDefault();
|
|
|
|
|
|
closeLauncher();
|
|
|
|
|
|
} else if (e.key === 'Tab' && launcherOpen()) {
|
|
|
|
|
|
// The launcher is modal: Tab cycles through its apps, and Escape
|
|
|
|
|
|
// leaves it.
|
|
|
|
|
|
var icons = Array.prototype.slice.call(appGrid.querySelectorAll('.app-icon'));
|
|
|
|
|
|
e.preventDefault();
|
|
|
|
|
|
if (icons.length === 0) { launcher.focus(); return; }
|
|
|
|
|
|
var at = icons.indexOf(document.activeElement);
|
|
|
|
|
|
var next = at === -1 ? 0 : (at + (e.shiftKey ? icons.length - 1 : 1)) % icons.length;
|
|
|
|
|
|
icons[next].focus();
|
2026-03-11 10:39:21 +00:00
|
|
|
|
}
|
|
|
|
|
|
});
|
|
|
|
|
|
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
// weft-servo-shell calls this when the shell loses keyboard focus, as
|
|
|
|
|
|
// when an application window is clicked; the launcher closes, so the
|
|
|
|
|
|
// next Super tap opens it.
|
|
|
|
|
|
window.weftShellBlurred = closeLauncher;
|
|
|
|
|
|
|
|
|
|
|
|
launcher.addEventListener('click', function (e) {
|
2026-03-11 10:39:21 +00:00
|
|
|
|
if (e.target === this) {
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
closeLauncher();
|
2026-03-11 10:39:21 +00:00
|
|
|
|
}
|
|
|
|
|
|
});
|
|
|
|
|
|
|
2026-10-09 07:45:49 +00:00
|
|
|
|
// weft-servo-shell supplies weft-appd's port and system token through
|
|
|
|
|
|
// window.weftAppdEndpoint once weft-appd is running, and again after it
|
|
|
|
|
|
// restarts. Nothing connects before then.
|
|
|
|
|
|
var appd = null;
|
2026-03-11 08:01:54 +00:00
|
|
|
|
var ws = null;
|
|
|
|
|
|
var wsReconnectDelay = 1000;
|
2026-10-09 07:45:49 +00:00
|
|
|
|
var wsReconnectTimer = null;
|
|
|
|
|
|
|
|
|
|
|
|
window.weftAppdEndpoint = function (port, token) {
|
|
|
|
|
|
if (appd && appd.port === port && appd.token === token) return;
|
|
|
|
|
|
appd = { port: port, token: token };
|
|
|
|
|
|
wsReconnectDelay = 1000;
|
|
|
|
|
|
if (ws) {
|
|
|
|
|
|
// The close handler reconnects with the new endpoint.
|
|
|
|
|
|
ws.close();
|
|
|
|
|
|
} else {
|
|
|
|
|
|
clearTimeout(wsReconnectTimer);
|
|
|
|
|
|
wsReconnectTimer = null;
|
|
|
|
|
|
appdConnect();
|
|
|
|
|
|
}
|
|
|
|
|
|
};
|
2026-03-11 08:01:54 +00:00
|
|
|
|
|
|
|
|
|
|
function appdConnect() {
|
2026-10-09 07:45:49 +00:00
|
|
|
|
wsReconnectTimer = null;
|
|
|
|
|
|
if (!appd || ws) return;
|
|
|
|
|
|
var endpoint = appd;
|
|
|
|
|
|
var socket;
|
2026-03-11 08:01:54 +00:00
|
|
|
|
try {
|
2026-10-09 07:45:49 +00:00
|
|
|
|
socket = new WebSocket('ws://127.0.0.1:' + endpoint.port + '/appd');
|
2026-03-11 08:01:54 +00:00
|
|
|
|
} catch (e) {
|
|
|
|
|
|
scheduleReconnect();
|
|
|
|
|
|
return;
|
|
|
|
|
|
}
|
2026-10-09 07:45:49 +00:00
|
|
|
|
ws = socket;
|
2026-03-11 08:01:54 +00:00
|
|
|
|
|
2026-10-09 07:45:49 +00:00
|
|
|
|
socket.addEventListener('open', function () {
|
|
|
|
|
|
if (ws !== socket) return;
|
2026-03-11 08:01:54 +00:00
|
|
|
|
wsReconnectDelay = 1000;
|
2026-10-09 07:45:49 +00:00
|
|
|
|
socket.send(JSON.stringify({ type: 'HELLO', role: 'system', token: endpoint.token }));
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
document.querySelectorAll('weft-taskbar-app').forEach(removeEntryElement);
|
2026-10-09 07:45:49 +00:00
|
|
|
|
socket.send(JSON.stringify({ type: 'QUERY_RUNNING' }));
|
|
|
|
|
|
socket.send(JSON.stringify({ type: 'QUERY_INSTALLED_APPS' }));
|
2026-03-11 08:01:54 +00:00
|
|
|
|
});
|
|
|
|
|
|
|
2026-10-09 07:45:49 +00:00
|
|
|
|
socket.addEventListener('message', function (ev) {
|
|
|
|
|
|
if (ws !== socket) return;
|
2026-03-11 08:01:54 +00:00
|
|
|
|
var msg;
|
|
|
|
|
|
try { msg = JSON.parse(ev.data); } catch (e) { return; }
|
|
|
|
|
|
handleAppdMessage(msg);
|
|
|
|
|
|
});
|
|
|
|
|
|
|
2026-10-09 07:45:49 +00:00
|
|
|
|
// A failed socket also fires close, so reconnection is handled there.
|
|
|
|
|
|
socket.addEventListener('close', function () {
|
|
|
|
|
|
if (ws !== socket) return;
|
2026-03-11 08:01:54 +00:00
|
|
|
|
ws = null;
|
|
|
|
|
|
scheduleReconnect();
|
|
|
|
|
|
});
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
function scheduleReconnect() {
|
2026-10-09 07:45:49 +00:00
|
|
|
|
if (wsReconnectTimer !== null) return;
|
|
|
|
|
|
wsReconnectTimer = setTimeout(appdConnect, wsReconnectDelay);
|
2026-03-11 08:01:54 +00:00
|
|
|
|
wsReconnectDelay = Math.min(wsReconnectDelay * 2, 16000);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
function handleAppdMessage(msg) {
|
2026-03-11 10:23:46 +00:00
|
|
|
|
if (msg.type === 'INSTALLED_APPS') {
|
|
|
|
|
|
renderLauncher(msg.apps || []);
|
|
|
|
|
|
} else if (msg.type === 'APP_READY') {
|
2026-03-11 09:51:16 +00:00
|
|
|
|
var label = msg.app_id ? msg.app_id.split('.').pop() : String(msg.session_id);
|
|
|
|
|
|
showNotification(label + ' is ready');
|
2026-03-11 08:01:54 +00:00
|
|
|
|
} else if (msg.type === 'APP_STATE') {
|
|
|
|
|
|
if (msg.state === 'stopped') {
|
|
|
|
|
|
removeTaskbarEntry(msg.session_id);
|
2026-10-09 16:41:30 +00:00
|
|
|
|
} else if (msg.state === 'stopping') {
|
2026-10-09 17:10:15 +00:00
|
|
|
|
setTaskbarEntryClosing(msg.session_id);
|
2026-03-11 08:01:54 +00:00
|
|
|
|
}
|
|
|
|
|
|
} else if (msg.type === 'RUNNING_APPS') {
|
2026-03-11 09:42:40 +00:00
|
|
|
|
msg.sessions.forEach(function (s) {
|
|
|
|
|
|
ensureTaskbarEntry(s.session_id, s.app_id);
|
2026-03-11 08:01:54 +00:00
|
|
|
|
});
|
|
|
|
|
|
} else if (msg.type === 'LAUNCH_ACK') {
|
2026-03-11 09:46:54 +00:00
|
|
|
|
ensureTaskbarEntry(msg.session_id, msg.app_id || null);
|
feat: appd IPC relay, WIT interfaces, UI kit, gesture routing, and CI hardening
- weft-appd: per-session IPC socket paths; bidirectional Wasm-HTML JSON relay
via spawn_ipc_relay; SO_PEERCRED UID check on Unix socket connections;
PanelGesture request and NavigationGesture broadcast for compositor gestures
- weft-runtime: weft:app/ipc, weft:app/fetch, weft:app/notifications WIT
interfaces; IpcState non-blocking Unix socket host functions; ureq-backed
net:fetch host function (net-fetch feature); notify-send notifications host
- weft-file-portal: spawn a thread per accepted connection for concurrent access
- weft-app-shell: weft-system:// URL translation; WEFT UI Kit UserScript
injection; resolve_weft_system_url helper
- weft-servo-shell: forward compositor navigation gestures to weft-appd
WebSocket as PanelGesture; WEFT UI Kit UserScript injection
- infra/shell: weft-ui-kit.js with 11 custom elements (weft-button, weft-card,
weft-dialog, weft-icon, weft-list, weft-list-item, weft-menu, weft-menu-item,
weft-progress, weft-input, weft-label); system-ui.html handles
NAVIGATION_GESTURE messages and dispatches weft:navigation-gesture CustomEvent
- infra/systemd: add missing env vars to weft-appd.service; correct
servo-shell.service binary path and system-ui.html argument
- .github/workflows/ci.yml: exclude weft-servo-shell and weft-app-shell from
cross-platform job; add them to linux-only job with libsystemd-dev dependency
2026-03-12 11:49:45 +00:00
|
|
|
|
} else if (msg.type === 'NAVIGATION_GESTURE') {
|
|
|
|
|
|
document.dispatchEvent(new CustomEvent('weft:navigation-gesture', {
|
|
|
|
|
|
detail: {
|
|
|
|
|
|
gesture_type: msg.gesture_type,
|
|
|
|
|
|
fingers: msg.fingers,
|
|
|
|
|
|
dx: msg.dx,
|
|
|
|
|
|
dy: msg.dy,
|
|
|
|
|
|
},
|
|
|
|
|
|
}));
|
2026-03-11 11:06:56 +00:00
|
|
|
|
} else if (msg.type === 'ERROR') {
|
fix(appd): move only real app data and never replace a directory
weft-pack treated any top-level data directory in a package as app
data from the earlier layout, in every store and for every app: a
package shipping data/ lost that content to the app data directory on
uninstall and could then no longer be uninstalled. Data is now moved
only from ~/.local/share/weft/apps/<id>/data, the only place earlier
versions wrote it, and only for packages declaring an app-data
capability; packages may no longer contain a top-level data entry.
The move left an empty package directory behind, which then blocked
weft-pack install although nothing was listed; an emptied package
directory is now removed, and install accepts an empty leftover. The
rename uses RENAME_NOREPLACE, so a target created after the check is
reported as a conflict instead of being replaced, and a move across
filesystems is refused with a message naming both locations instead of
a bare OS error. Directories moved by weft-pack are made private too,
and a symbolic link at the target is refused rather than followed.
The system UI now shows launch refusals, which it only logged, and the
weft-appd unit may write under ~/.local/share/weft, which
ProtectSystem=strict made read-only. check_app_data.py also types into
Notes after the move and requires the save to reach the moved file, and
checks that no empty package directory remains.
2026-10-09 08:52:09 +00:00
|
|
|
|
// Launch refusals (missing package, capability or data conflict)
|
|
|
|
|
|
// must reach the user; the launcher otherwise looks unresponsive.
|
2026-03-11 11:06:56 +00:00
|
|
|
|
console.warn('appd error', msg.code, msg.message);
|
fix(appd): move only real app data and never replace a directory
weft-pack treated any top-level data directory in a package as app
data from the earlier layout, in every store and for every app: a
package shipping data/ lost that content to the app data directory on
uninstall and could then no longer be uninstalled. Data is now moved
only from ~/.local/share/weft/apps/<id>/data, the only place earlier
versions wrote it, and only for packages declaring an app-data
capability; packages may no longer contain a top-level data entry.
The move left an empty package directory behind, which then blocked
weft-pack install although nothing was listed; an emptied package
directory is now removed, and install accepts an empty leftover. The
rename uses RENAME_NOREPLACE, so a target created after the check is
reported as a conflict instead of being replaced, and a move across
filesystems is refused with a message naming both locations instead of
a bare OS error. Directories moved by weft-pack are made private too,
and a symbolic link at the target is refused rather than followed.
The system UI now shows launch refusals, which it only logged, and the
weft-appd unit may write under ~/.local/share/weft, which
ProtectSystem=strict made read-only. check_app_data.py also types into
Notes after the move and requires the save to reach the moved file, and
checks that no empty package directory remains.
2026-10-09 08:52:09 +00:00
|
|
|
|
showNotification('Cannot open: ' + msg.message);
|
2026-03-11 08:01:54 +00:00
|
|
|
|
}
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2026-03-11 10:23:46 +00:00
|
|
|
|
function renderLauncher(apps) {
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
var grid = appGrid;
|
|
|
|
|
|
// Replacing the icons would drop keyboard focus; it returns to the
|
|
|
|
|
|
// same app's new icon.
|
|
|
|
|
|
var focused = grid.contains(document.activeElement) ? document.activeElement.dataset.appId : null;
|
|
|
|
|
|
var active = document.activeElement;
|
|
|
|
|
|
var refocus = launcherOpen() && (!active || active === document.body || launcher.contains(active));
|
2026-03-11 10:23:46 +00:00
|
|
|
|
grid.innerHTML = '';
|
|
|
|
|
|
if (apps.length === 0) {
|
|
|
|
|
|
var empty = document.createElement('p');
|
|
|
|
|
|
empty.textContent = 'No apps installed';
|
|
|
|
|
|
empty.style.cssText = 'color:var(--text-secondary);font-size:13px;';
|
|
|
|
|
|
grid.appendChild(empty);
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
if (refocus) focusInLauncher(null);
|
2026-03-11 10:23:46 +00:00
|
|
|
|
return;
|
|
|
|
|
|
}
|
|
|
|
|
|
apps.forEach(function (app) {
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
var icon = document.createElement('button');
|
|
|
|
|
|
icon.type = 'button';
|
|
|
|
|
|
icon.className = 'app-icon';
|
2026-03-11 10:23:46 +00:00
|
|
|
|
icon.dataset.appId = app.app_id;
|
2026-03-11 12:15:09 +00:00
|
|
|
|
icon.title = app.app_id + (app.version ? ' v' + app.version : '');
|
2026-10-09 07:45:49 +00:00
|
|
|
|
// Names come from package manifests; they are set as text, never markup.
|
2026-03-11 10:23:46 +00:00
|
|
|
|
icon.innerHTML =
|
|
|
|
|
|
'<svg width="40" height="40" viewBox="0 0 40 40" fill="none"' +
|
|
|
|
|
|
' xmlns="http://www.w3.org/2000/svg" aria-hidden="true">' +
|
|
|
|
|
|
'<rect width="40" height="40" rx="10" fill="rgba(91,138,245,0.25)"/>' +
|
|
|
|
|
|
'<text x="20" y="27" text-anchor="middle" font-size="18" fill="rgba(255,255,255,0.8)">' +
|
2026-10-09 07:45:49 +00:00
|
|
|
|
'</text></svg><span></span>';
|
|
|
|
|
|
icon.querySelector('text').textContent = app.name ? app.name.charAt(0).toUpperCase() : '?';
|
|
|
|
|
|
icon.querySelector('span').textContent = app.name || app.app_id;
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
icon.setAttribute('aria-label', 'Open ' + (app.name || app.app_id));
|
2026-03-11 10:23:46 +00:00
|
|
|
|
icon.addEventListener('click', function () {
|
|
|
|
|
|
if (ws && ws.readyState === WebSocket.OPEN) {
|
|
|
|
|
|
ws.send(JSON.stringify({ type: 'LAUNCH_APP', app_id: app.app_id, surface_id: 0 }));
|
|
|
|
|
|
}
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
closeLauncher();
|
2026-03-11 10:23:46 +00:00
|
|
|
|
});
|
|
|
|
|
|
grid.appendChild(icon);
|
|
|
|
|
|
});
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
if (refocus) focusInLauncher(focused);
|
2026-03-11 10:23:46 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
2026-10-09 17:10:15 +00:00
|
|
|
|
// Longer than weft-appd's close timeout, so an app that neither closes
|
|
|
|
|
|
// nor declines has already been terminated.
|
|
|
|
|
|
var FORCE_QUIT_DELAY = 6000;
|
2026-10-09 17:16:42 +00:00
|
|
|
|
var FORCE_QUIT_OFFER = 20000;
|
2026-10-09 17:10:15 +00:00
|
|
|
|
|
2026-03-11 09:42:40 +00:00
|
|
|
|
function ensureTaskbarEntry(sessionId, appId) {
|
2026-03-11 08:01:54 +00:00
|
|
|
|
var id = 'task-' + sessionId;
|
|
|
|
|
|
if (document.getElementById(id)) { return; }
|
2026-03-11 09:42:40 +00:00
|
|
|
|
var label = appId ? appId.split('.').pop() : String(sessionId);
|
2026-03-11 08:01:54 +00:00
|
|
|
|
var el = document.createElement('weft-taskbar-app');
|
|
|
|
|
|
el.id = id;
|
|
|
|
|
|
el.dataset.sessionId = sessionId;
|
2026-03-11 09:42:40 +00:00
|
|
|
|
if (appId) { el.dataset.appId = appId; }
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
el.setAttribute('role', 'group');
|
|
|
|
|
|
el.setAttribute('aria-label', label);
|
2026-03-11 09:42:40 +00:00
|
|
|
|
el.title = appId ? appId + ' (session ' + sessionId + ')' : 'Session ' + sessionId;
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
var span = document.createElement('button');
|
|
|
|
|
|
span.type = 'button';
|
|
|
|
|
|
span.className = 'task-activate';
|
2026-03-11 10:40:25 +00:00
|
|
|
|
span.textContent = '● ' + label;
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
span.setAttribute('aria-label', 'Show ' + label);
|
|
|
|
|
|
var close = document.createElement('button');
|
|
|
|
|
|
close.type = 'button';
|
2026-03-11 10:40:25 +00:00
|
|
|
|
close.className = 'task-close';
|
|
|
|
|
|
close.textContent = '×';
|
2026-10-09 16:41:30 +00:00
|
|
|
|
close.title = 'Close';
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
close.setAttribute('aria-label', 'Close ' + label);
|
2026-10-09 17:10:15 +00:00
|
|
|
|
// The first click asks the app to close; it may decline, for example
|
|
|
|
|
|
// to offer saving. An app still running once it has had time to
|
|
|
|
|
|
// answer can then be force quit, losing what it has not saved.
|
2026-10-09 17:16:42 +00:00
|
|
|
|
var closeTimer = null;
|
2026-03-11 10:40:25 +00:00
|
|
|
|
close.addEventListener('click', function (e) {
|
|
|
|
|
|
e.stopPropagation();
|
2026-10-09 17:10:15 +00:00
|
|
|
|
if (!ws || ws.readyState !== WebSocket.OPEN) { return; }
|
|
|
|
|
|
var force = close.dataset.force === '1';
|
|
|
|
|
|
ws.send(JSON.stringify({ type: 'TERMINATE_APP', session_id: sessionId, force: force }));
|
|
|
|
|
|
if (force || close.dataset.asked) { return; }
|
|
|
|
|
|
close.dataset.asked = '1';
|
2026-10-09 17:16:42 +00:00
|
|
|
|
closeTimer = setTimeout(function () {
|
2026-10-09 17:10:15 +00:00
|
|
|
|
if (!document.getElementById(el.id) || el.dataset.closing) { return; }
|
|
|
|
|
|
close.dataset.force = '1';
|
|
|
|
|
|
close.textContent = 'Force quit';
|
|
|
|
|
|
close.title = 'Force quit: changes the app has not saved are lost';
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
close.setAttribute('aria-label', 'Force quit ' + label + '; changes it has not saved are lost');
|
|
|
|
|
|
close.classList.add('force');
|
|
|
|
|
|
showNotification(label + ' did not close; its close button now force quits it');
|
2026-10-09 17:16:42 +00:00
|
|
|
|
// Offered only for a while: an app that declined to let the user
|
|
|
|
|
|
// keep working is closed normally next time.
|
|
|
|
|
|
closeTimer = setTimeout(resetClose, FORCE_QUIT_OFFER);
|
2026-10-09 17:10:15 +00:00
|
|
|
|
}, FORCE_QUIT_DELAY);
|
2026-03-11 10:40:25 +00:00
|
|
|
|
});
|
2026-10-09 17:16:42 +00:00
|
|
|
|
function resetClose() {
|
|
|
|
|
|
clearTimeout(closeTimer);
|
|
|
|
|
|
closeTimer = null;
|
|
|
|
|
|
delete close.dataset.asked;
|
|
|
|
|
|
delete close.dataset.force;
|
|
|
|
|
|
close.textContent = '×';
|
|
|
|
|
|
close.title = 'Close';
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
close.setAttribute('aria-label', 'Close ' + label);
|
|
|
|
|
|
close.classList.remove('force');
|
2026-10-09 17:16:42 +00:00
|
|
|
|
}
|
2026-03-11 10:40:25 +00:00
|
|
|
|
el.appendChild(span);
|
|
|
|
|
|
el.appendChild(close);
|
2026-10-09 15:36:55 +00:00
|
|
|
|
// Choosing the entry brings the app's window to the front.
|
|
|
|
|
|
el.addEventListener('click', function () {
|
2026-10-09 16:45:25 +00:00
|
|
|
|
if (el.dataset.closing) { return; }
|
2026-10-09 17:16:42 +00:00
|
|
|
|
resetClose();
|
2026-10-09 15:36:55 +00:00
|
|
|
|
if (ws && ws.readyState === WebSocket.OPEN) {
|
|
|
|
|
|
ws.send(JSON.stringify({ type: 'ACTIVATE_APP', session_id: sessionId }));
|
|
|
|
|
|
}
|
|
|
|
|
|
});
|
2026-03-11 08:01:54 +00:00
|
|
|
|
var taskbar = document.querySelector('weft-taskbar');
|
|
|
|
|
|
var clock = document.getElementById('clock');
|
|
|
|
|
|
taskbar.insertBefore(el, clock);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
2026-10-09 17:10:15 +00:00
|
|
|
|
// The session is ending; its entry stays until it has stopped.
|
|
|
|
|
|
function setTaskbarEntryClosing(sessionId) {
|
2026-10-09 16:41:30 +00:00
|
|
|
|
var el = document.getElementById('task-' + sessionId);
|
2026-10-09 17:10:15 +00:00
|
|
|
|
if (!el || el.dataset.closing) { return; }
|
|
|
|
|
|
el.dataset.closing = '1';
|
|
|
|
|
|
el.style.opacity = '0.5';
|
|
|
|
|
|
el.title += ' (closing)';
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
var activate = el.querySelector('.task-activate');
|
|
|
|
|
|
activate.setAttribute('aria-disabled', 'true');
|
|
|
|
|
|
activate.setAttribute('aria-label', activate.getAttribute('aria-label') + ' (closing)');
|
2026-10-09 16:41:30 +00:00
|
|
|
|
var close = el.querySelector('.task-close');
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
if (close) {
|
|
|
|
|
|
if (document.activeElement === close) { activate.focus(); }
|
|
|
|
|
|
close.style.display = 'none';
|
|
|
|
|
|
}
|
2026-10-09 16:41:30 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
2026-03-11 08:01:54 +00:00
|
|
|
|
function removeTaskbarEntry(sessionId) {
|
|
|
|
|
|
var el = document.getElementById('task-' + sessionId);
|
fix(shell): make the system UI operable from the keyboard
The launcher button, app icons and taskbar entries were custom elements
with click handlers only: none could be focused, named or activated from
the keyboard, and the launcher overlay neither took nor returned focus.
They are now buttons with accessible names and a visible focus ring. The
launcher is a modal dialog that a Super tap or the Apps button opens
with focus on its first app; Tab moves between apps, Enter opens one and
Escape or another Super tap closes it, returning focus to the Apps
button. Each taskbar entry has an activate and a close button reachable
with Tab, and focus moves to a remaining control when an entry closes or
goes away. Notifications, including the offer to force quit, are
announced as status.
Servo does not tell the document when its window loses keyboard focus,
so weft-servo-shell calls window.weftShellBlurred() then and the launcher
closes; the next Super tap opens it again. Servo does not evaluate
prefers-reduced-motion either, so the page has no transitions.
tests/frame/check_system_ui.py drives the real page on the nested
desktop with keys: opening apps from the launcher, reaching the shell
with a Super tap from an application, a Super chord that stays with the
app and leaves no Super modifier held there, activating and closing apps
from the taskbar, the launcher closing when the shell loses focus, and
toggling it. It fails without the compositor's Super handling or the
focus-loss call.
2026-10-09 20:21:26 +00:00
|
|
|
|
if (el) { removeEntryElement(el); }
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
// Focus on a removed entry would be lost; it moves to the Apps button.
|
|
|
|
|
|
function removeEntryElement(el) {
|
|
|
|
|
|
var hadFocus = el.contains(document.activeElement);
|
|
|
|
|
|
el.remove();
|
|
|
|
|
|
if (hadFocus) { launcherBtn.focus(); }
|
2026-03-11 08:01:54 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
function showNotification(text) {
|
|
|
|
|
|
var center = document.getElementById('notifications');
|
|
|
|
|
|
var note = document.createElement('div');
|
|
|
|
|
|
note.textContent = text;
|
|
|
|
|
|
note.style.cssText = [
|
|
|
|
|
|
'background:var(--surface-bg)',
|
|
|
|
|
|
'border:1px solid var(--surface-border)',
|
|
|
|
|
|
'border-radius:8px',
|
|
|
|
|
|
'padding:10px 14px',
|
|
|
|
|
|
'font-size:13px',
|
|
|
|
|
|
'color:var(--text-primary)',
|
|
|
|
|
|
'pointer-events:auto',
|
|
|
|
|
|
'backdrop-filter:blur(20px)',
|
|
|
|
|
|
].join(';');
|
|
|
|
|
|
center.appendChild(note);
|
|
|
|
|
|
setTimeout(function () { note.remove(); }, 4000);
|
|
|
|
|
|
}
|
|
|
|
|
|
|
feat(servo-shell): add servo-shell skeleton, system UI, service unit, and Wayland input audit
Includes winit Wayland input audit for servo-shell integration planning.
New files:
- crates/weft-servo-shell/: new workspace member
- Cargo.toml: anyhow + tracing deps; no servo dep yet (requires git
dependency on github.com/servo/servo with multi-minute build; deferred
until embedder contract is confirmed)
- src/main.rs: reads WAYLAND_DISPLAY and WEFT_SYSTEM_UI_HTML, locates
system-ui.html from packaged path, calls embed_servo() stub that
returns a descriptive error explaining the integration work remaining
- infra/shell/system-ui.html: system UI document per blueprint Section 5
DOM structure (weft-desktop, weft-wallpaper, weft-taskbar, weft-launcher,
weft-notification-center, weft-window); includes clock and launcher toggle
- infra/systemd/servo-shell.service: Requires+After weft-compositor.service,
Type=simple, Restart=on-failure
- docs/architecture/winit-wayland-audit.md: audit of winit 0.30.x Wayland
backend against WEFT input requirements; identifies keyboard shortcut
inhibit gap, touch gesture gap, IME incomplete (zwp_text_input_v3),
frame pacing absent (wp_presentation_time), DMA-BUF unverified;
none block initial integration; all tracked as pre-GA work items
Modified:
- Cargo.toml: add weft-servo-shell to workspace members
- scripts/wsl-check.sh: switch to --workspace for all three gates
2026-03-10 23:34:26 +00:00
|
|
|
|
}());
|
|
|
|
|
|
</script>
|
|
|
|
|
|
</body>
|
|
|
|
|
|
</html>
|