4 ms·

Huh? View Transitions are an entirely new API supported only by Chrome currently. (And Edge, which is a flavor of Chrome.)

by mholt 3y ago

nsonha 3y ago
you're being too hung up on native APIs, view transition as a concept is nothing new and has existed in front-end frameworks for ages
- deleted 3y ago
  [deleted]
- danielvaughn 3y ago
  I'm not aware of a framework that has first-class support for animating between application states, and I've used all the most prominent ones. But regardless, the fact that it's leveraging a native API is significant; it means (a) the browser engine can optimize for it, (b) less code needs to ship to the browser to use it, and (c) native behavior means a standardized API for a complex task.
  - danbulant 3y ago
    In which way does svelte(kit) not have first class support for animating between states? You can animate items being added to page, removed from page or reordered in a keyed each. This also includes pages themselves in layout files. And you can also animate an item being moved from one place to another by being removed in one place and added in another place.
- sirius87 3y ago
  Do you have an example? My understanding is that without browsers doing the tweening between visible states, it would require complex DOM manipulation and animation to make it look good. The native API is an essential part of making this happen for the web.
- afavour 3y ago
  I think you need to read the API docs again. View transitions as a concept are not new but the View Transitions API offers functionality not previously available in browsers.
asu_thomas 3y ago
> View Transitions are an entirely new API supported only by Chrome currently. (And Edge, which is a flavor of Chrome.) https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API https://developer.mozilla.org/en-US/docs/Web/API/View_Transi...

4 ms·

Huh? View Transitions are an entirely new API supported only by Chrome currently. (And Edge, which is a flavor of Chrome.)

by mholt 3y ago

Huh? View Transitions are an entirely new API supported only by Chrome currently. (And Edge, which is a flavor of Chrome.)

nsonha 3y ago
you're being too hung up on native APIs, view transition as a concept is nothing new and has existed in front-end frameworks for ages
- deleted 3y ago
  [deleted]
- danielvaughn 3y ago
  I'm not aware of a framework that has first-class support for animating between application states, and I've used all the most prominent ones. But regardless, the fact that it's leveraging a native API is significant; it means (a) the browser engine can optimize for it, (b) less code needs to ship to the browser to use it, and (c) native behavior means a standardized API for a complex task.
  - danbulant 3y ago
    In which way does svelte(kit) not have first class support for animating between states? You can animate items being added to page, removed from page or reordered in a keyed each. This also includes pages themselves in layout files. And you can also animate an item being moved from one place to another by being removed in one place and added in another place.
- sirius87 3y ago
  Do you have an example? My understanding is that without browsers doing the tweening between visible states, it would require complex DOM manipulation and animation to make it look good. The native API is an essential part of making this happen for the web.
- afavour 3y ago
  I think you need to read the API docs again. View transitions as a concept are not new but the View Transitions API offers functionality not previously available in browsers.
asu_thomas 3y ago
> View Transitions are an entirely new API supported only by Chrome currently. (And Edge, which is a flavor of Chrome.) https://developer.mozilla.org/en-US/docs/Web/API/View_Transitions_API https://developer.mozilla.org/en-US/docs/Web/API/View_Transi...