- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 14 Oct 2025 21:37:23 +0000
- To: public-css-archive@w3.org
> Some folks use transition: all 1s, so this change will not be backwards compatible. Existing sites might experience a new unexpected transition as a result, not to mention the unexpected stacking context change side effect. Folks using `transition: all 1s` will have transition side-effects regardless. In the current spec, it'll (presumably) delay the hiding for 1s, assuming `visibility:force-hidden` adopts the same transition behavior as `visibility:hidden`. Having it instead fade out over that 1s is probably less confusing anyway. Probably more importantly, though, there's no back-compat issue at all, since this is a new feature. > Using opacity instead of visibility also has accessibility implications afaik Both have a11y implications; the effect is just different between them. (But see @fantasai's later comments on this.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12732#issuecomment-3403703401 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 14 October 2025 21:37:24 UTC