SimonC Simon-CR

Universal Window Position & Dimension Persistence for Chromium / Chrome PWAs on KDE Plasma 6 (Wayland)

Executive Summary / The Problem

When running Chromium or Google Chrome Progressive Web Apps (PWAs) — such as Gmail, Messenger, Facebook, Slack, or YouTube — on KDE Plasma 6 under Wayland, users frequently encounter a severe window geometry issue. PWAs fail to remember their previous window dimensions and positions across sessions, often defaulting to arbitrary, maximized, or stretched sizes (e.g., spanning entire multi-monitor arrays or opening as a full vertical column).

This forces the user to manually resize and reposition web apps every time they are launched, severely degrading the desktop experience.

Deep Technical Root Cause

The problem stems from a combination of Wayland protocol restrictions, Chromium's rendering pipeline, and KWin's window matching logic:

ACE 2 Pro — additional findings (V1.1.31)

Additions and two corrections to hakimio's ACE2 firmware analysis, from running an ACE 2 Pro on a Voron Trident under Klipper and building custom firmware for it.

All of this builds directly on hakimio's work. The protocol, the .proto schema, the OTA updater and the MCU analysis are his; every address below was found by following his map. Full write-up, patches and tooling: https://github.com/Simon-CR/ace2-pro-firmware-research

	#!/bin/sh
	# This script graceful reloads the Caddy server inside the docker container. Graceful means that caddy reloads its configuration with zero downtime.
	# Warning: Only works on Linux
	caddy_container_id=$(docker ps \| grep caddy \| awk '{print $1;}')
	docker exec $caddy_container_id caddy reload --config /etc/caddy/Caddyfile --adapter caddyfile