Michał "rysiek" Woźniak · 🇺🇦Nov 11

No, your website is not "working correctly" unless it is working correctly on two *different* rendering engines.

I lived through the IE6 era, I do not want to live through that kind of bullshit again. And trust me, neither do you.

#WebDev

Show threadkimaprNov 11
@rysiek i’d argue it should be 3 different engines even, if a website works on firefox and chromium but not safari/webkit it’s still broken
Show threadCadenNov 11
@kimapr @rysiek fair, but it's a lot harder to test for that one given that you either need specific hardware, or you need to get an ISO from someone with specific hardware and run a VM, which is against Apple's EULA
Show threadkimaprNov 11
@tarix29 @rysiek you don’t need apple-specific hardware to use webkit. you can just grab GNOME Web, Midori, surf, or any other of the billions of open source webkit-based browsers
Show threadCaden
@kimapr @rysiek true that will work for the baseline. I was thinking of Safari specifically, which has some differences. You definitely won't totally break Safari support by only testing on other WebKit browsers, but you can still get styling discrepancies, I ran into some last week. Even MacOS vs iOS Safari can have differences, iirc scrolling behavior is one of them
Nov 11 at 3:08pmWeb
Show threadMichał "rysiek" Woźniak · 🇺🇦Nov 11

@tarix29 @kimapr if it works and looks the same on webkit, gecko, and blink, I'm willing to say it's on Safari to get its shit together.

It's not like Apple lacks the resources to do this well.