- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Jul 2024 20:35:01 +0000
- To: public-css-archive@w3.org
> Why not? document.startViewTransition(() => element.requestFullscreen()) requestFullscreen() is async. It's not necessary that the next frame after the update callback runs is a fullscreen frame. There's also the fact that exiting fullscreen can be triggered using browser/OS UI. > I think we can find a way to deal with the changes SCB. +1. We have to for most use-cases of element-scoped transitions. Just wanted to point that this is also a dependency. > Not super enthusiastic of giving up UA control of this transition, especially given different platforms may have different ideas how fullscreen works. Happy to hear the details on the kind of control you think the UA should keep. We have heard this feature request from other developers as well, being able to animate elements when the layout changes is helpful in re-orienting users. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10609#issuecomment-2243768472 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 20:35:02 UTC