Open chenmently opened 1 year ago
Thanks for your interest in Portals.
Our current thinking is that some of the original use cases for Portals might be addressed by the combination of the following APIs:
Note that some use cases might require additions to View Transition (e.g. finger-driven transitions).
We are working with partners on verifying this hypothesis, and would love to see the community putting these APIs to the test for the Portals use cases they have in mind.
The more advanced use cases (e.g. composed user experiences relying on adoptPredecessor for instance) don't seem possible by merely extending View Transition, and may still be sufficient motivation for investing in Portals or a different solution if appropriate.
Overall, we are looking for feedback on which use cases may have a different solution in light of recent platform advancements (e.g. View Transition, Prefetch/Prerender, etc), and which use cases are still impossible or too expensive to achieve with available means.
Since the initial trail ended with chrome m110 and according to issue #286 , new implementation will be based on prerendering. Will we have a esteemed time of new portals trail and if possible, tell us more about the problem with original implementation