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.
Discussion
Loading...
Post
@rysiek This brings back the pain of delivering video on CD-ROM. We tested on Mac and three flavours of Windows but there was always an end user with a setup which couldn’t play it. When DVD arrived it was such a relief.
@allypally did I say "all rendering engines" though?
@rysiek
I don't consider Webkit and Blink different rendering engines. More like different versions of the same engine.
I also consider Firefox dead, killed by Mozilla.
So to fulfil your requirement, kI would have to make sure that my website works in a Webkit(Blink) based browser as well as something like Lynx.
And while in theory my web site IS designed to work in Lynx, that is not something I test every time I make a change, and there are parts that probably don't work as well, primarily anything involving some kind of image.
@rysiek It’s not a website, it’s a Googsite.
@rysiek Dedicated Firefox user. (I know, and I don't care) and lately, a lot of sites just do not work. I am forced to open them on Edge. DO NOT LIKE. Fix this, people. Please.
@rysiek Back in secondary school in the late 2000s early 2010s we learned to test our website made in dreamweavever in Internet explorer, chrome, Firefox, opera and safari.
Now developers don't do that. They just test in edge and chrome. When I get a browser not supported often changing the user agent often results in the website working fine.
@Goldmaster yeah, that last bit is even worse! they are actively shutting out browsers explicitly. It's not just that they do not test on them, they actively block them.
incompetence and cargo culting, is what that is.
@rysiek oh better than that!
Must use the app and then everyone wonders why their phones are littered with 500 apps.
@rysiek
Christ don't remind me.
"Please use chrome for the website TO RENDER BASIC FUCKING HTML
@rysiek i'd argue you should only get to call your website as working correctly if all features function as intended on at least blink, gecko and webkit
@rysiek Also? Edge doesn’t count. Still chromium.
@foobarsoft I did say "different rendering engines" for a reason
@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
@rysiek
what was *fun* was trying to make a site that was standards-compliant and used CSS properly but also rendered as intended on Netscape 4
so many tears caused by Netscape 4 back when I was doing webdev stuff...
@rysiek I can still hear the developers from back then yelling "just use a shim! a shim will solve everything! shims! shims stacked on shims! more shims!" which I still feel is how that whole "1kb website with 1mb worth javascript" era began we're still in today 
@anthropy for real. Sometimes shims were necessary, but man were they overused.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled