- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Jul 2024 18:50:05 +0000
- To: public-css-archive@w3.org
> > Is this something that (in theory) could be improved and customized with view transitions? Nice idea! > > Yea. We need a new opt-in to do a same-document ViewTransition for the fullscreen case. Authors can't do it using the `document.startViewTransition` API since that needs to be called _before_ the DOM change. And by the time the author is notified of the fullscreen event, it's already too late. Why not? `document.startViewTransition(() => element.requestFullscreen())` > > There's also the problem that we currently abort transitions if the "snapshot containing block" size changes [here](https://drafts.csswg.org/css-view-transitions-1/#ref-for-viewtransition-initial-snapshot-containing-block-size%E2%91%A1:~:text=Return.-,If%20transition%E2%80%99s%20initial%20snapshot%20containing%20block%20size%20is%20not%20equal%20to%20the%20snapshot%20containing%20block%20size%2C%20then%20skip%20the%20view%20transition%20for%20transition%2C%20and%20return.,-Update%20pseudo%2Delement). Instead likely the cached transforms need to be adjusted so the elements stay-in-place when the viewport size changes. Note that an element becomes full-screen, not a document. Perhaps this would work better with element-scoped transitions? I think we can find a way to deal with the changes SCB. > > @nt1m @noamr @vmpstr -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10609#issuecomment-2243605388 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 July 2024 18:50:06 UTC