| From: Helmut Januschka <helmut@januschka.com> | |
| Subject: HID: magicmouse: report the device timestamp as MSC_TIMESTAMP | |
| The Magic Mouse and Magic Trackpad touch reports carry an 18-bit | |
| timestamp from the device's 1 kHz clock, which the driver documented | |
| but discarded. Over Bluetooth, reports arrive in bursts whose wall- | |
| clock spacing says nothing about when the touches were sampled, so | |
| any userspace consumer computing velocity from arrival times sees | |
| spikes. Accumulate the device clock wrap-aware into microseconds and | |
| emit it as MSC_TIMESTAMP, like hid-multitouch does for other devices. |
Reintroduces a kashida value to the text-justify property and adds a companion text-kashida-space property to css-text-4.
text-justify: kashida — justify by inserting cursive elongation (kashida) at a limited number of positions per word, with inter-word spacing as fallback.text-kashida-space: <percentage> — controls the ratio of elongation to word-separator expansion. Initial 100%.
| From: Helmut Januschka <helmut@januschka.com> | |
| Subject: [PATCH] platform/x86/amd/pmc: firmware-handled LPS0 quirk for MINISFORUM MS-S1 MAX | |
| The MINISFORUM MS-S1 MAX (SHWSA, Strix Halo) ships firmware whose LPS0 | |
| PEP device only implements the Microsoft _DSM UUID; its entry/exit | |
| functions trap into SMM (port 0xB2, 0xEA/0xEB) and perform the platform | |
| sleep handshake there. The AMD _DSM UUID advertises no entry/exit | |
| functions at all (function mask 0x3). | |
| When amd_pmc additionally sends OS_HINT, s2idle never resumes: with both |
| name | chromium-autoreview-no-ch |
|---|---|
| description | Autoreview-style Chromium code review without the ch CLI. Uses git/local files and public Chromium Gerrit REST only. |
| compatibility | No ch dependency. Requires Python 3 and optional local Chromium checkout. Public Gerrit CLs only unless browser/auth cookies are added manually. |
You are doing practical issue-finding for Chromium-style code review. This is
modeled after public Chromium autoreview comments, but does not require the ch
Decode with: base64 -d sddm.png.b64 > sddm.png
iVBORw0KGgoAAAANSUhEUgAAB4AAAASwCAIAAACVUsChAAEAAElEQVR4nOz96ZokuXEgiprBIzKrqtkrF5HUSmnmSud+333/F7mLzhxpRkcUxRHZe3dVLhEOuz+wOPbdl8hOE1Ud6Q4YDIDBYBvg+NFffwwAiAhDwUGIyAAQgAAIAIgIAAC5XZKMGhwAAEStFOYeqkzg8VqC2nS75VQhIiIKnHIcAJCB+adoFoA0WkYAAIRIgEQEtDQnfi4EICECkRjbKUoHN9sCFPUVYsLxLOEDgmyDIk1R+LGq7lGYoJhoNssX9s4hbIMxyUIhDSY/6yqyO8bU29iIgEdGidRssABFwIjI5F7J5MBzcxiCeAeDLxgBRxDNBwenf9bshTkYuYnEweYM4KiOxJqrxgbAKUxeAjMRmW/12BIRQ0ah/i5y0t1WcvRzLlgRADjRxOEdx0+v7PML++V1ejtzJADghMSIzpxOBEhIiNxDvMbaRzK7K5sIDk4KSRlhqBZuFTNjTDQ3AUW4Rbwsp6ofYhyYaAtbJFkc2wG2ki0Bk7vzKwhIis25CaW/X2uEYaG6JSS07qNBiSjWJUtMBhcYxlpJzJQ2JUZBHFsTkxBKuy8gPaNk83iHSobU6UJi0yGlEleNYZs2iJwAgBDNgbTMQPuVeI4Qt+BSwGDhQ626L9yCLMVmy5+E2jR0kMsySOANoDQlk6OUmKPgE0SciduUBAbbw4OOCZfUQPR0gM+cWcYjRKkjeE0seqzGvvwbFoFEZKqgzpAWqogut6u/TIVHl/QHHKT6J/02RKQwcAAQfxAoDhBcQQhIQuMWLog0hQ1QIYe9/uarJJpDsY5cjhLvTPFoNkcsZQcFnwdWByxsY3KCYx+llAdPsETfGWVEc9J64
This is a small example of the kind of work I think the SOCBB metadata RFP is asking for.
It is not uploaded to Chromium yet. I am keeping it as a concrete sample while checking whether this category of work is in scope.
Chromium still has this WebDXFeature counter:
A while back I wrote about building Chromium for Windows on a Linux box, driven entirely by my own RBE backend — no Google RBE, no Google-hosted toolchain. It worked beautifully and the obvious next question landed in my inbox more than once:
"Cool. Now do macOS."
My gut reaction was: no chance. macOS means Apple's toolchain, xcrun,
Short verification of the current integration on
https://www.alstertal-einkaufszentrum.de/newsletter-registration/unsubscribe/?subId=…
(same code path as Rheinparkcenter and other ECE centers).
The captcha SDK works correctly. The intermittent rejection comes from a custom submit listener that is registered before KROT.interceptForm(form) and calls e.stopImmediatePropagation(). When that branch is taken, the SDK's own submit listener never runs, so no token is computed and no token is sent.
On https://www.rheinparkcenter-neuss.de/newsletter-registration/, the current integration sometimes logs a generated captcha solution but the final POST request does not include it.
Root cause is the custom click-based orchestration around KROT.getSolution() plus KROT.interceptForm(form, true).
Current code: