Hello there!
I have noticed an interesting glitch, which seems to be exclusively affecting Chromium based browsers (Firefox and Safari are both fine).
Attachment upload keeps failing with HTTP Error 520 so I can't supply any evidence, but hopefully you can confirm this on your end and I'm not imagining things.
Open the Grid Cell Editing example.
Switch theme to High Contrast Light (Fluent 2 Light also works, but it's more subtle).
Note the cell border between Team and Score columns is thinner than the rest.
Resize any column and the border fixes itself.
Reload the page and the half-pixel border is back!
This effect is only visible on a high-DPI display, that border may completely disappear when viewed on a regular screen. I'm observing this on a 16-inch MacBook, so maybe it is also device specific.
I'm not sure why this glitch only appears in Chrome/Chromium, and why is it visible in this particular demo but not in other demos (or maybe it does, I just didn't check every single one of them). We have had past reports from our customers about disappearing borders but we could never reliably reproduce this until now.
Any ideas?
Thanks!
UPDATE: Claude Code thinks this is because Chromium's compositor performs aggressive per-element pixel snapping when CSS containment is active, breaking the visual continuity between adjacent cells. Firefox uses a different pixel-snapping strategy that preserves adjacency between elements. It also has special DPR-aware border-width compensation in GridBase.js. Safari/WebKit handles subpixel snapping with more tolerance for adjacent absolutely-positioned elements.
The proposed solution, which is working for me, is to replace the .b-windows selector with .b-chrome in SubGrid.css to make the contain: layout; style override a Chromium-specific, rather than a Windows-specific patch.
