A problem repeatedly occurred with Safari 14.1
discussions.apple.com
discussions.apple.com
The cause was calling focus/setSelectionRange on a textfield within a click handler. When I commented these out then the problem disappeared.
Not a rare combination and I’d have thought beta-testing should have flushed this out, but there you go.
Edit:
If you want to try reproducing this, go to https://cycle.travel/map/mobile?debug=1 , and click within the 'From' or 'To' field. It crashes every time on my iPad running iOS 14.5.
https://community.atlassian.com/t5/Trello-questions/Re-Trell...
Does the following work for you in Safari 14.1?
new Intl.NumberFormat('en-US', {notation: 'compact'}).format(1825602)
In Chrome this gives "1.8M"
I get (macOS 10.14.6, Safari 14.1):
> new Intl.NumberFormat('en-US', {notation: 'compact'}).format(1825602)
< TypeError: Failed to initialize NumberFormat since used feature is not supported in the linked ICU versionIt's probably not a Safari bug.
A browser shouldn't be so integral, that if it breaks the only option is to wipe your computer and start again.
Telling users to re-install the system seems a little drastic and seems like the last thing Apple would recommend were you take your machine to the genius bar...
Everything else was optional.
Macs, to boot today, need, at a minimum:
* three partitions
* two OS installations comprising dozens/hundreds of files (three separate macOS installations on M1 macs)
* T2/M1 hardware-specific activation data
* BridgeOS (on T2 systems)
I remember being worried when OS X was first previewed (btw, everyone, for the last time it's pronounced "ten") that they would ruin the "drag and drop two files and a folder" simplicity that the mac was known for with this complicated new system.
Indeed I was right. It's a real bummer how non-modular macOS is these days. It's a giant ball of mud, and the only recommended method of modifying it is format and reinstall, which burns a couple hours: just like Windows.
What I don't understand is why the apple installer and updater seems to do a lengthy installation, when it seems to be effectively creating a "sealed image". Does anyone know of a good resource explaining the modern MacOS installer?
It strikes me Apple could ship a delta image for the system subvolume, and just ensure the hash is correct before rebooting. That seems to not be what's being done, given the length of time an update takes. I wonder why they don't do this though, given it seems nothing can edit the system volume, so it ought to be shipped as an image?
The installer being better isn't going to sell more computers; it ain't really broken, so there would need to be some real incentive to do anything other than incrementally fixing it. (This is not to discount the small amounts of polish they add to these tools bit by bit over time as they are incrementally improved, such as the black full screen background for the system updater.) A total overhaul of such a central system (used regularly by millions of machines during updates) is a gigantic risk, to put it mildly. They also just took one such big risk with the whole APFS migration/system volume thing, which to their credit went well.
Every now and then Apple will actually rewrite an app, like they did to Disk Utility not long ago. This usually makes it worse, and relegates anyone serious to the command line tools (which are fortunately quite complete and comprehensive, even if their man pages aren't).
I have a feeling they spend the most high-quality application developer resources on things like iWork and FCP and stuff that users actually live and breathe every day, not stuff they run a few times a year unattended.
As for Safari, I switched to Firefox when they disabled uBlock Origin, so I don't know how it works these days.
Fwiw: Im using safari on both iOS and MacOS, macos with kablock and iOS with firefox focus and the experience has been good.
It's not as bad as no adblocking altogether, but very far from firefox with ubo on Android.
It's good enough to use however, and android has it's own issues.
FF's extension interface allows more sophisticated rules & blocking behavior, and uBO takes advantage of that. You may be fortunate that you don't happen to spend time on sites where it makes a difference, but I'll say from experience that I do see ads and annoyances on some sites on my iPad that I do not see on my laptop or Android phone (both running FF with uBO). It's not a huge difference - as was said above, Safari with content blockers is certainly usable, but uBO is still better.
I am speculating a bit here because I haven't dug too deeply to confirm this, but I think one technique sites use to work around ad blockers that Apple-platform content blockers don't handle well but uBO does is serving ad content from the same origin as real content (and even with similar paths as real assets). Last I looked, Safari content blockers were mostly limited to old-style rules of "block assets matching this URL" and "block this css selector on this site", so when sites do the work to make ad assets look the same as real content assets, that can't be blocked as effectively with content blockers. uBO can inspect the DOM and other aspects of the page content blockers can't, so it can do more to detect those techniques and block them.
Your users aren't always tech savvy. Sometimes quite the opposite. A single change, even if it isn't a bug, can render your program unusable by some because it's so different.
Which is the underlying cause of the universal “I didn’t do anything” disclaimer before they even start explaining the issue. And the aggressivity if that tension is not defused before replaying their actions to get the context.
Solving issues requires way more social skills than people assume.
The UX of my son's iPad is almost enough to drive me insane. So many counter intuitive ways to do things, such as completely invisible (ZERO freaking indicators) swipes needed to access extra info etc.
My present favourite is how the current keypad for entering extra time on an app (yes I managed to set up parental guidelines for that POS) is cropped in half so that you have to rotate the screen in order to see the full keypad.
Plenty of room on the lock screen that's displayed for this purpose, only showing the numbers keypad - they just made it so tiny you can't pick half the numbers some of which are in my parent pin.
How they're selling this crap for billions of dollars is beyond me.
Too many ways to accidentally make crap pop up or get stuck in weird states on iOS, now. Even the old folder behavior, that "split open" the screen to reveal the folder, made it much, much clearer to navigate for non-tech-geeks. Lots of little things like that, plus tons of gesture-initiated overlays and switching-about.
One example to prove your point was that I needed to disable/restrict the fingerprint auth as he was using that to get himself more time; his old device that died didn't have one.
Everything said yeah just go to "Face ID & Passcode" under settings. Except it wasn't there. An inordinate amount of effort later I learned there was a setting knee deep in Screen Time > Content & Privacy Restrictions that would allow it to be displayed.
Why TF not just display the Touch settings tab still and then a message saying its use is disabled in that part of their jungle hell? I mean that'd actually be user friendly.
(Setting up Docker in WSL2 is a breeze compared to the guesswork that's becoming their new norm.)
However, you can run a Terminal command to disable it again, which works great...except for the new version of Safari, where all the fonts look ridiculously bold [0]
[0] https://imgur.com/a/IJBGjHu The top comment of this thread; Safari on the left, Firefox on the right.
Subpixel antialiasing has been disabled and steadily pruned from the OS since Mojave if that's what you're talking about:
With that toggle gone, it can still be toggled using the "AppleFontSmoothing" defaults key.
Turns out Imgur adds random stuff under your post, because now it's a social network and not an image host. Validates my decision to make my own image host.
https://i.imgur.com/Dwd5Dzg.png - much better!
Here's a screenshot off the laptop display (2560x1600 running at 2x scaling—the "looks like 1280x800" setting): https://imgur.com/a/zS0dyF6
Click to zoom—imgur's thumbnails are garbage quality.
* {
-webkit-font-smoothing: antialiased !important;
}
But see also: https://tonsky.me/blog/monitors/
I'm not saying the problem doesn't exist and/or that it's not Apple's fault, but, possibly, it's not strictly related to Safari.
DEBUGGING MINDSET: On MacOS, this Safari update was pushed along a MacOS update. (and maybe in iOS as well, along the 14.5 iOS?). How can you say the problem is within Safari? There's even a user complaining about a problem in Apple mail (a network timeout).
This problem could lie anywhere in the network stack, and maybe Safari is using a specific pattern that triggers the bug very often on some specific hardware. It could be a driver issue for what we know.
Now I'm trying to update my other machine (2015 Macbook Pro 15").
Every time it crashes in the same place and leaves this in the logs:
Dyld Error Message:
Symbol not found: __ZN6webrtc24setVideoDecoderCallbacksEPFPvRKNS_14SdpVideoFormatEEPFiS0_EPFiS0_jPKhmttEPFiS0_S0_E
Referenced from: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/WebKit
Expected in: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/../../../libwebrtc.dylib
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 dyld 0x000000011767f3ba __abort_with_payload + 10
1 dyld 0x000000011767ebac abort_with_payload_wrapper_internal + 82
2 dyld 0x000000011767ebde abort_with_payload + 9
3 dyld 0x000000011763ea9d dyld::halt(char const*) + 343
4 dyld 0x000000011763ebc7 dyld::fastBindLazySymbol(ImageLoader\*, unsigned long) + 167
5 libdyld.dylib 0x00007fff60f4f32e dyld_stub_binder + 282
6 ??? 0x0000000108649008 0 + 4435775496
7 com.apple.WebKit 0x00000001083c758d WebKit::LibWebRTCProvider::createEncoderFactory() + 27
8 com.apple.WebCore 0x000000010ae7bdc9 WebCore::LibWebRTCProvider::createPeerConnectionFactory(rtc::Thread*, rtc::Thread\*) + 153
[0] https://forums.macrumors.com/threads/safari-14-1-is-complete...
It’s a browser I want to love – especially for its performance – but it’s becoming harder.
It feels like every dev tool sucks for me though. Chrome regularly froze the whole tab and crashes the tools on my old computer. Firefox I don’t remember exactly but also it was a PITA
It seems to be a rather erratic problem. (Maybe, it's related to some framework corruption and the advice to reinstall isn't that bad, after all?)
New bugs in OS + new bugs in Safari is not a good combination.
So in this case, less than ideal.
I was actually pleased they’ve finally implemented date/time inputs so I can stop using JS calendars now.
How would the reporter know if the issue is specific to them or applies to everyone without posting a thread about it?
Not saying macOS wasn't great. It was. But Apple aren't investing in it anymore.
https://daringfireball.net/linked/2021/04/28/aapl-q2-2021-re...
If you think that increases in Mac sales mean that macOS is a growing part of Apple's revenue: it isn't: macOS is dwarfed by other products more every year.
https://www.statista.com/statistics/382136/quarterly-segment...
According to https://www.apple.com/newsroom/2021/04/apple-reports-second-..., Apple “posted a March quarter record revenue of $89.6 billion, up 54 percent year over year …”.
Mac, on the other hand, grew by 69 percent year over year.
You're speaking about raw numbers.
From that report:
$47.94 billion: iPhone (Up 65%) $9.1 billion: Mac (Up 70% YOY) $7.81 billion: iPad (up 79% YOY)
To let us know what Apple prioritises, though, we need to look at percentages of the operating unit as a percent of Apple revenue.
Mac revenue was 4.8 in 2014, 5.2% in the most recent figure I could find.
https://barefigur.es/companies/apple/products/
We can also look at company reorgs like getting rid of the macOS team, advertisements steering customers away from macOS, and other public facts.
There's only "an app for that" if you have developers.
Having said that Apple needs only to meet the very, very low bar of having a better ecosystem than Android.