Looking at the Blink bug, it seems their feature-flag for this was called `SnapBorderWidthsBeforeLayout` which shipped to release in v109 per https://chromestatus.com/feature/4651561863610368 and seems to have stuck. I think that's the thing that Emilio was referring to in comment 12 as other-browsers-going-to-match-us (correct me if I'm wrong though). I think the last paragraph of my comment 3 is still an accurate description of the compat situation here -- Firefox optimizes for crisp borders even in the face of `transform` with fractional scales, whereas other browsers do not (and hence scaled-down borders still show up [albeit in a fuzzy/antialiased form] for them, whereas they entirely disappear for us).
Bug 1258112 Comment 14 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Looking at the [Blink bug about border-snapping](https://issues.chromium.org/issues/40178820), it seems their feature-flag for this was called `SnapBorderWidthsBeforeLayout` which shipped to release in v109 per https://chromestatus.com/feature/4651561863610368 and seems to have stuck. I think that's the thing that Emilio was referring to in comment 12 as other-browsers-going-to-match-us (correct me if I'm wrong though). I think the last paragraph of my comment 3 is still an accurate description of the compat situation here -- Firefox optimizes for crisp borders even in the face of `transform` with fractional scales, whereas other browsers do not (and hence scaled-down borders still show up [albeit in a fuzzy/antialiased form] for them, whereas they entirely disappear for us).
Looking at the [Blink bug about border-snapping](https://issues.chromium.org/issues/40178820), it seems their feature-flag for this was called `SnapBorderWidthsBeforeLayout` which shipped to release in v109 per https://chromestatus.com/feature/4651561863610368 and seems to have stuck. I think that (and the associated WebKit changes) are the thing that Emilio was referring to in comment 12 as other-browsers-going-to-match-us (correct me if I'm wrong though). I think the last paragraph of my comment 3 is still an accurate description of the compat situation here -- Firefox optimizes for crisp borders even in the face of `transform` with fractional scales, whereas other browsers do not (and hence scaled-down borders still show up [albeit in a fuzzy/antialiased form] for them, whereas they entirely disappear for us).
Looking at the [Blink bug about border-snapping](https://issues.chromium.org/issues/40178820), it seems their feature-flag for this was called `SnapBorderWidthsBeforeLayout` which shipped to release in v109 per https://chromestatus.com/feature/4651561863610368 and seems to have stuck. I think that (and the associated WebKit changes) are the thing that Emilio was referring to in comment 12 as other-browsers-going-to-match-us (correct me if I'm wrong though). I think the last paragraph of my comment 3 is still an accurate description of the compat situation here -- Firefox optimizes for keeping borders crisp, even in the face of `transform` with fractional scales, whereas other browsers do not (and hence scaled-down borders still show up [albeit in a fuzzy/antialiased form] for them, whereas they entirely disappear for us).