181–190 of 311 posts
Earlier quoted context omitted.
I am sorry you have to go through this painful exercise. But, how would an alternative rendering engine fix this problem?
"Our product doesn't work in safari, use chrome or firefox instead"
Earlier quoted context omitted.
"Our product doesn't work in safari, use chrome or firefox instead"
The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?
When people want to get their work done, opening another browser while the original one is being fixed (which might take a couple weeks), for certain applications, is extremely reasonable for business people just trying to get their work done.
There are of course a lot of nice built-in solutions to things, but having a quick-and-easy modal mechanism allows people to have cleaner code for something they're gonna try to do one way or another.
Earlier quoted context omitted.
And just like that, Safari has surpassed Chrome in interop 2022 https://wpt.fyi/interop-2022
Webkit is not committed to fully implementing the HTML Living Standard, or more precisely, they are committed to killing off the parts they don't like by declining to implement them. They point-blank refuse to implement Customized Built-in Elements, for example, and in such (unusually, for the context) vehement, uncompromising, and unconstructive language¹ that I can only surmise some Apple apparatchik's fragile ego…
When will they support webp on macOS 10? I guess never?
I wish they'd add an option to disable webp, it's really annoying to save a photo and get it in a format that's supported almost nowhere.
Earlier quoted context omitted.
I am sorry you have to go through this painful exercise. But, how would an alternative rendering engine fix this problem?
Webkit would have to compete with other engines to retain its market share rather than abuse its monopoly power.
Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…
I know people like to complain about Safari, but:
1. It’s absolutely common to ask developers for a minimal repro case in a bug report.
2. There are four major Safari releases under 15.x.
3. Apple OS upgrades, especially iOS, are as close to total as one could imagine. The overlap between people who buy iPhones and people who go out of their way to turn off OS upgrades is really small.
I want Apple to stop tying (some) Safari releases to OS upgrades, but this honestly feels like you’re tired and it’s been a long day, and you could use a break. Take the night off. Safari will still be imperfect but improving tomorrow, even if it’s not at the pace we’d prefer.
Earlier quoted context omitted.
"Our product doesn't work in safari, use chrome or firefox instead"
The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?
This foundation is provided by browsers and is also broken by browsers. If safari's foundation is broken then safari is the one not fulfilling that fundamental promise, not the websites now broken. So yes, don't use a browser if it doesn't work.
Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…
Aaaand they introduced WebGL bugs that broke our product, and iPhone users will experience these bugs until we can hack a workaround in, or until Apple acknowledges a bug report (that I have to make a minimal test case for and report, and haven't narrowed down yet), patches the issue in Safari, and decides if it's important enough to release as a 15.4.1 (which they probably won't, which means I'm stuck finding a work…
[1] https://twitter.com/jensimmons/status/1491064075987873792