- From: Martin \ <sysbot+gh@w3.org>
- Date: Thu, 20 Apr 2023 19:44:57 +0000
- To: public-css-archive@w3.org
I've worked on creating choreographic page transitions in SPAs for a long while now and it was nostalgic going over the options described here as being quite familiar to when I was agonising over the different approaches. Eventually I've come to greatly appreciate the last option most in my web apps, with the named page types, as being most maintainable and logical. Storing weird state or depending on URLs has always been painful and awkward depending on designs and nested/hierarchical info architecture that don't conveniently match up. So the separation with it's own system via named page types helps with the motion design. -- Rambling thoughts: However there can still be some challenges with nested transitions, in my use case for example where some anchor link in content would change to the next page and show a certain tab or popup on that page. For example a healthcare professional would click on a medical article on a link to the results of a trial or a mode of action for a drug in a section on a different page. So having the page-page transition and then transition for the section/popup/tab/whathaveyou in staggered sequence. I don't know if that's something VT would be capable of handling but hey food for thought after playing around with nested named cascade layers. -- GitHub Notification of comment by Martin-Pitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8683#issuecomment-1516858469 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 April 2023 19:44:59 UTC