- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 21 Jan 2026 17:47:14 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-view-transition-1] `visibility: hidden` analogy is misleading, elements remain keyboard-focusable and accessible``, and agreed to the following: * `RESOLVED: change to "as opacity:0"` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> vmpstr: this is skirting the line of editorial<br> <TabAtkins> vmpstr: in the spec we say that elements that are eparticipating in a view transition don't paint where they're ac Tually positioned<br> <TabAtkins> vmpstr: in parens, "as if they're visibility:hidden".<br> <TabAtkins> vmpstr: person filing the issue said hidden comes with other implications, like keyboard-focus. suggested we rephrase to "as opacity:0". fine with that<br> <flackr> +1<br> <bramus> +1<br> <emilio> sgtm<br> <TabAtkins> I think this is indeed editorial, and go for it<br> <TabAtkins> astearns: k, so proposed resolution: change to "as opacity:0"<br> <TabAtkins> RESOLVED: change to "as opacity:0"<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12629#issuecomment-3780065875 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 January 2026 17:47:15 UTC