LadybirdBrowser
LibWeb: Implement view transitions
This implements the CSS view-transitions-1 spec.
Opening this as a draft so people can look at it if they want to, and to link to it in various other bug reports.
Your pull request has conflicts that need to be resolved before it can be reviewed and merged. Make sure to rebase your branch on top of the latest master.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions!
This pull request has been closed because it has not had recent activity. Feel free to open a new pull request if you wish to still contribute these changes. Thank you for your contributions!
@Psychpsyo is there any part of this that can be chunked up into mergable commits?
@Psychpsyo is there any part of this that can be chunked up into mergable commits?
I started on that with https://github.com/LadybirdBrowser/ladybird/commit/ad0da8ffa39611264948ae2c5fc61b7483104009 a while back. That one is a pre-requisite for any further work here. (Ran into a SEGFAULT there and debugging it was tedious enough for me to put it aside for a while. Would love help but also feel bad about just making it someone else's problem.)
Though technically the stuff in here could be merged with some small changes right now, it just wouldn't be a sensible or useful amount of feature.
It needs a bit more work plus that other commit to be in a state where an invisible view transition can be started and actually ends on its own.
After that, more stuff can comfortably be in its own PRs
Sounds good; So we can leave this PR closed without any work getting super lost?
Sounds good; So we can leave this PR closed without any work getting super lost?
My plan was to re-open it once I got that other commit figured out. This PR was a draft before being closed anyways.