3 ms·

"Sorry, OldWeb.today can not run in this emulator in your current browser. Please try the latest version of Chrome or Firefox to use this emulator. " Wow, it r

"Sorry, OldWeb.today can not run in this emulator in your current browser. Please try the latest version of Chrome or Firefox to use this emulator. " Wow, it really does feel like using an old browser. (Safari Version 15.2 (17612.3.6.1.6))

kreeben 5y ago
Oldweb saved from incursion by the shear fact js is not backwards compatible ;)
ricardobayes 5y ago
Arguably, Safari is the IE of our times. Safari somehow always have rendering issues. I use Firefox as that's closest to standards, I hate bending standard code to fit a garbage browser's special needs.
- jmkni 5y ago
  On iOS you have to use Safari if you want to use a content/ad blocker, which means I’m kind of stuck with it on my iPhone/iPad. Then you bring macOS into play, and the way Safari on mobile syncs with Safari on desktop is really nice. Password sharing in particular is great, so you end up getting sucked in to Safari!
- michalstanko 5y ago
  I wouldn't go as far as calling it an "IE", because those of us who lived through that know it was a completely different experience. But yes, Safari is slow in implementing new features a bit and it does get annoying from time to time. But it's nowhere near the IE hell from ~2000 - 2008.
  - MatmaRex 5y ago
    It totally is. I used to write custom CSS for IE to make drop shadows work (it didn't support the standard syntax). Now I write custom CSS for Safari to make drop shadows work (there's a bug where if you remove the node, its shadow sometimes stays behind).
    - shukantpal 5y ago
      And? Single data point.
      - conductr 5y ago
        Everyone else in the world writing CSS has to jump through the same hoops they are referring to... does that really fall under "single data point"?
twsted 5y ago
Absurd. Most of the time I think it is just dev laziness. Can anyone tell us which web feature is blocking the compatibility with Safari?
defanor 5y ago
Same message in FF 78, but works after reloading the page and choosing Ruffle (Flash).

kreeben 5y ago

Oldweb saved from incursion by the shear fact js is not backwards compatible ;)

ricardobayes 5y ago

Arguably, Safari is the IE of our times. Safari somehow always have rendering issues. I use Firefox as that's closest to standards, I hate bending standard code to fit a garbage browser's special needs.

jmkni 5y ago
On iOS you have to use Safari if you want to use a content/ad blocker, which means I’m kind of stuck with it on my iPhone/iPad. Then you bring macOS into play, and the way Safari on mobile syncs with Safari on desktop is really nice. Password sharing in particular is great, so you end up getting sucked in to Safari!
michalstanko 5y ago
I wouldn't go as far as calling it an "IE", because those of us who lived through that know it was a completely different experience. But yes, Safari is slow in implementing new features a bit and it does get annoying from time to time. But it's nowhere near the IE hell from ~2000 - 2008.
- MatmaRex 5y ago
  It totally is. I used to write custom CSS for IE to make drop shadows work (it didn't support the standard syntax). Now I write custom CSS for Safari to make drop shadows work (there's a bug where if you remove the node, its shadow sometimes stays behind).
  - shukantpal 5y ago
    And? Single data point.
    - conductr 5y ago
      Everyone else in the world writing CSS has to jump through the same hoops they are referring to... does that really fall under "single data point"?

twsted 5y ago

Absurd. Most of the time I think it is just dev laziness. Can anyone tell us which web feature is blocking the compatibility with Safari?

defanor 5y ago

Same message in FF 78, but works after reloading the page and choosing Ruffle (Flash).