3 ms·

Unlocking view transitions in SvelteKit 1.24

45 points by miohtama 3y ago

deleted 3y ago
[deleted]
turnsout 3y ago
Neat! It will be even neater when Safari/WebKit adds support (seems semi-promising)
- CharlesW 3y ago
  caniuse says it's Chrome-only for now, making the claim that it's "sweeping the web development world" a bit suspect. Maybe it'll be ubiquitous by 2025?
  - turnsout 3y ago
    Sadly, these days you can be Chrome-only and still sweep the web dev world. As a desktop Safari user (we exist), I wish it were otherwise!
    - iansinnott 3y ago
      Web devs still have to pay an unfortunate amount of attention to Safari if they want to support mobile. Admittedly, they're unlikely to test against desktop Safari but it's the same engine as the mobile version if I'm not mistaken.
      - turnsout 3y ago
        Ah yes, why bother testing? Safari must behave exactly the same on mobile and the desktop, right? Let's not even bother testing that assumption, it sounds correct.
        aacid 3y ago
        I think "why bother testing?" is more about desktop safari users are such a small demographics that most developers (especially small ones) won't bother.
        turnsout 3y ago
        Yep, and then they cross Firefox off the list, and pretty soon they're not web devs, they're Chrome devs.
  - ttfkam 3y ago
    Chrome, Opera, and Edge all now use the same engine. The mobile world has a strong showing from Mobile Safari, but the desktop world is far more… homogeneous. Desktop Safari made a run from 10% to 14% in the last year. Firefox went from 9% to 7% in the same timeframe. Chrome is around 65%. Edge is around 10%. Opera is about 6%. So the desktop Blink engines combined are close to 80%. That's pretty damn close to ubiquitous if you're on a desktop or laptop.
userbinator 3y ago
Great, more crap to block... IE had an "Enable page transitions" setting in its advanced options (which I always kept off.) It's quite telling that "modern" browsers don't, and even user CSS support is slowly disappearing. Back then, sites didn't have to ask about "prefers reduced motion" or anything like that, because the user agent was on the side of the user.
- michaelteter 3y ago
  Watching the little video on the SvelteKit page, it just looks like it adds some ghosting and latency to the action. Those are things we've tried to fix with faster systems and faster refresh displays. Adding them back on purpose seems like a feature that designers who are non-users would like.
butz 3y ago
And what is up with scrollbars that are as narrow as a hair?

45 points by miohtama 3y ago

deleted 3y ago

[deleted]

turnsout 3y ago

Neat! It will be even neater when Safari/WebKit adds support (seems semi-promising)

CharlesW 3y ago
caniuse says it's Chrome-only for now, making the claim that it's "sweeping the web development world" a bit suspect. Maybe it'll be ubiquitous by 2025?
- turnsout 3y ago
  Sadly, these days you can be Chrome-only and still sweep the web dev world. As a desktop Safari user (we exist), I wish it were otherwise!
  - iansinnott 3y ago
    Web devs still have to pay an unfortunate amount of attention to Safari if they want to support mobile. Admittedly, they're unlikely to test against desktop Safari but it's the same engine as the mobile version if I'm not mistaken.
    - turnsout 3y ago
      Ah yes, why bother testing? Safari must behave exactly the same on mobile and the desktop, right? Let's not even bother testing that assumption, it sounds correct.
      - aacid 3y ago
        I think "why bother testing?" is more about desktop safari users are such a small demographics that most developers (especially small ones) won't bother.
        turnsout 3y ago
        Yep, and then they cross Firefox off the list, and pretty soon they're not web devs, they're Chrome devs.
- ttfkam 3y ago
  Chrome, Opera, and Edge all now use the same engine. The mobile world has a strong showing from Mobile Safari, but the desktop world is far more… homogeneous. Desktop Safari made a run from 10% to 14% in the last year. Firefox went from 9% to 7% in the same timeframe. Chrome is around 65%. Edge is around 10%. Opera is about 6%. So the desktop Blink engines combined are close to 80%. That's pretty damn close to ubiquitous if you're on a desktop or laptop.

userbinator 3y ago

Great, more crap to block... IE had an "Enable page transitions" setting in its advanced options (which I always kept off.) It's quite telling that "modern" browsers don't, and even user CSS support is slowly disappearing. Back then, sites didn't have to ask about "prefers reduced motion" or anything like that, because the user agent was on the side of the user.

michaelteter 3y ago
Watching the little video on the SvelteKit page, it just looks like it adds some ghosting and latency to the action. Those are things we've tried to fix with faster systems and faster refresh displays. Adding them back on purpose seems like a feature that designers who are non-users would like.

butz 3y ago

And what is up with scrollbars that are as narrow as a hair?