Earlier quoted context omitted.
Safari states their position on standards here: https://webkit.org/standards-positions/ IMO they have good reasons for opposing most of the standards
I searched that page and their github repo for "inputmode" (my example from before you posted) and couldn't find anything. https://github.com/WebKit/standards-positions/issues?q=input... I'd love to find out if anyone on the webkit project is aware of that part of the standard, and if so, the project's official position on it. I can't imagine why they'd oppose it.
Is Chrome the New IE? (2023)
111–120 of 316 posts
Re: Is Chrome the New IE? (2023)
#112Yes. If it works on Chrome, no one cares or even tests for other things. If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it. Performs fine in Chrome? Ship it. Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time. Everything has to be Chrome compatible to succeed. That’s th…
Unless you want to have customers on iOS.
Re: Is Chrome the New IE? (2023)
#113Re: Is Chrome the New IE? (2023)
#114Earlier quoted context omitted.
The unstated major premise of this assertion is that the standard is a spec that every browser must comply with exactly. It's not; there's not a single browser that has ever implemented 100% of whatever was the latest standard at the time, and major browsers typically also include many of their own additions that go beyond the standard. This latter bit isn't in conflict with the standard; it's an essential part of th…
> The unstated major premise of this assertion is that the standard is a spec that every browser must comply with exactly. It's not; there's not a single browser that has ever implemented 100% of whatever was the latest standard at the time, and major browsers typically also include many of their own additions that go beyond the standard. Sure, but there is a big difference between implenting 99% of the standard and…
But if developers don't check, then either one could break the site for all the users.
Re: Is Chrome the New IE? (2023)
#115Yes. If it works on Chrome, no one cares or even tests for other things. If there is a JS feature in Chrome they want to use, so it’s impossible to use other browsers (instead of looking wrong) people do it. Performs fine in Chrome? Ship it. Yes, Chrome is the new IE in that it’s the only browsers companies care about, just like IE was for a very long time. Everything has to be Chrome compatible to succeed. That’s th…
Re: Is Chrome the New IE? (2023)
#116Not even close. IE 6 didn’t get any updates or new web features for years. It was closed source. It was dead and everyone used it. float:right; zoom:1; was a common necessity… to compare them is an insult to the immense progress and effort spent over the last 24 years… (yes chrome started in 2007, but the teams from Firefox get credit too, many of them went on to build chrome ). The open source movement won, IE is de…
Ummm ... 2024 - 2007 = 17
Re: Is Chrome the New IE? (2023)
#117No not even close by every single possible measure. I was there, I suffered through it, Google would have to make TONS of hostile moves for that fact to change. I have no interest in the arguments of a closed source subscription service that wants me to switch to the bundled browser of the wealthiest company on earth's most popular consumer OS, lecturing me about using the 4th wealthiest company on earth's browser th…
> using the 4th wealthiest company on earth's browser that I freely installed. 99% of the time I use Chrome it's because some site does not support Firefox (and that often includes Google sites/apps). (The 1% are for APIs that Firefox, consciously or out of resource constraints, does not support.) In what sense am I "freely installing" Chrome in this situation? Just today I had a family member reach out to me, unable…
Re: Is Chrome the New IE? (2023)
#118Safari, the browser that claims to support standards but always comes with caveats, like saying they support transform/transitions and then everything with box shadows flickering
My codebase is full of Safari version-specific bug fixes.
Re: Is Chrome the New IE? (2023)
#119Yes, Chrome is the de facto standard, and often the only browser thoroughly tested against. Even now though it isn't as dominant as IE at its peak though. No, Chrome isn't significantly behind on adopting new standards compared with other major browsers (I'm looking at you Safari). IE6 to IE7 was about five years!
There's a part of my brain I'll never get back devoted to all of these workarounds. So many hours lost to weird corporate networks that had quirks mode enabled, different box models (before the advent of the `box-sizing` CSS attribute), random omissions of standards (no `:hover` on elements besides `a`), etc.