A problem repeatedly occurred with Safari 14.1(discussions.apple.com)
discussions.apple.com
A problem repeatedly occurred with Safari 14.1
https://discussions.apple.com/thread/252705424
119 comments
A bit off topic but I just want to thank you for such a great site. Just this morning I had been linked to it for a travel diary of LEJOG.
Thank you! I love working on it, and hearing about people enjoying cycling holidays they've planned with the site is the best reward.
Confirmed the bug on an iPhone XS running 14.5. I had to focus the from field twice before it crashed.
Looks like a fix is in the works at https://bugs.webkit.org/show_bug.cgi?id=225259 using your site as the reproduction case :)
I've got a fully-updated iPhone 11 with iOS 14.5 and your site works perfectly well with my device in Safari.
Maybe because they commented out the code on their site that triggered the issue?
I did, yes - or rather I put it behind a UA check. I've just put up a reproducible case behind a query-string flag - see edit above.
This does cause a crash on my iPhone XR running iOS 14.5
I confirm not crashing for me on MacOS Mojave with Safari 14.1:
https://streamable.com/5jn41o
https://streamable.com/5jn41o
That's interesting - so a Mobile Safari issue but not a desktop one. Cheers.
That's not surprising, I've seen a lot of cases where Mobile Safari has different bugs than the desktop one.
OP said the bug appeared on iOS 14.5
The main linked article is about Safari 14.1 on MacOS. If it is "exactly the same issue" as OP says, then how come it doesn't appear on Safari 14.1 on MacOS?
It's probably not a Safari bug.
It's probably not a Safari bug.
Possibly. But then there's no way to confirm it happens on a lot of devices. So far I've been unable to reproduce the issue on any of my MacOS and iOS devices on any problem-related URL I was given in this thread or linked discussions.
Trello evidently had a bug (or rather, Safari 14.1 evidently has a bug which manifested on Trello) related to Intl.NumberFormat:
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"
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 encounter the same issue which for me breaks Microsoft's documentation, e.g. https://docs.microsoft.com/en-us/dotnet/api/system.io.memory...
I get (macOS 10.14.6, Safari 14.1):
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 versionIs that even the same issue?
It is the root cause of some issue with Trello that appeared with Safari 14.1, but perhaps not the same issue causing other sites to break; if so, perhaps there are multiple bugs with the update.
Happens on my iPhone 12 also, reloading and eventually an error message about a repeating problem.
This also crashes on iPhone 8 running iOS 14.4.2.
I can't believe the recommended solution is "backup and reinstall your operating system".
A browser shouldn't be so integral, that if it breaks the only option is to wipe your computer and start again.
A browser shouldn't be so integral, that if it breaks the only option is to wipe your computer and start again.
I remember when everyone laughed when Windows XP's update tool ran as ActiveX applet inside IE6. Guess Apple didn't learn anything from that.
You awakened neurons for me that I think are impaired from disuse. I can picture progress bars in Internet Explorer and Windows XP colors but not much more.
Well, for a long time internet explorer was the same in Windows. And probably still is, as in they use it internally for a lot of things even if Edge is now the actual user facing browser.
As for Safari, I switched to Firefox when they disabled uBlock Origin, so I don't know how it works these days.
As for Safari, I switched to Firefox when they disabled uBlock Origin, so I don't know how it works these days.
same here. I completely forgot how to use the internet without uBO or another decent adblocker. same reason i can't switch to iphone, they don't have a firefox with addon support.
There are decent adblockers for safari on both macOS and iOS.
Mozilla makes one for iOS, Firefox Focus, which you can setup as a content blocker. KaBlock exists for safari on both macos and ios. And there are many more.
Fwiw: Im using safari on both iOS and MacOS, macos with kablock and iOS with firefox focus and the experience has been good.
Fwiw: Im using safari on both iOS and MacOS, macos with kablock and iOS with firefox focus and the experience has been good.
I got an ipad pro from 2020 and tried all these, but have to disagree.
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.
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.
What am I missing on iOS safari + content blocker compared to firefox + ubo then? I used ubo on chrome on the desktop, but not a chrome user anymore. Honestly don’t see the difference compared to macos + kablock (and hush).
It's not surprising you wouldn't see much difference between Kablock/Safari on desktop and content blockers/Safari on mobile - I believe they're basically the same kind of interface for providing blocking rules.
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.
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.
Wipr works very well for me as an adblocker on iOS/iPadOS/macOS.
Quick correction- reinstalling does not constitute a wipe, at least not on macOS, and will generally fix any os-level weirdness you’re experiencing at a given moment. Definitely still ridiculous.
In macOS system 8 and before, the way you made a disk bootable for a mac was you would partitoin/format it with the standard filesystem (HFS), create a directory in that filesystem called "System Folder", and put two files in it: "Finder", the app that launches on boot, and "System", the OS bundle. Doing so in the Finder would "bless" the System Folder and let the OS know it had everything it needed to boot.
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.
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.
Entirely agreed the loss of simplicity is a shame. I do wonder though if the current "APFS subvolume" approach is an acceptable alternative.
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?
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?
I think (a guess from experience) that a huge amount of Apple work is done under intense time pressure, and prioritized as related to the bullet point list of new features being pushed for that release's marketing communications.
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.
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.
I don't exactly know what the MacOS installed does - but I do know that as recent as Catalina having MacTeX installed in /usr/local would cause it to flip out and take hours and hours to install.
It's insane how tightly coupled such crucial apps are to the OS. The first time I tried to make an iOS app and learned that you needed to download all of XCode and its updates (tons and tons of GB!) just to use some console commands and compile an app I spent a while searching for alternatives thinking that I must have not understood correctly.
Is that user an Apple employee? I though the forums were a free for all?
I mean, independent of that, that answer is flagged as "Apple recommended"...
Is that because the user has a certain amount of karma? I tried to dig into it but I am not sure how it got that flag.
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...
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...
Regardless of whether the flag was applied deliberately by an employee, or by an automated process, it's still showing up as 'Apple recommended' on their official support forum: any way you slice it, Apple is recommending exactly that.
Apple employees are not allowed to comment on these forums.
Looks like this is just some random guy's suggestion though? Not like these are the official help pages.
There is big "Apple recommended" text next to it.
I cant believe it is the only solution, and strongly doubt it is the only option. But for many users it is the easiest to do unfortunately, to get back to a clean working slate.
this is also the default genius bar solution.
The seniors on there that are beside themselves unable to use some of their sites is something I think of when designing software.
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.
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.
I'm a near 50s guy who grew up on Vic20s and hasn't stopped since.
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.
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.
iOS discoverability/usability tanked when iOS7 came out and hasn't recovered. It went from being the only OS I'd happily give to my 80-something can-barely-email grandma, to "um... well, shit, I guess we'll get you a Chromebook... but it's gonna suck."
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.
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.
Thanks, yes it's almost like a cult thing - you're supposed to stab and poke and just _discover_ the hidden features.
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.)
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.)
At least communicate. Users aren't stupid but they approach the web with fear most of the time, so anything out of the ordinary is a sign of a problem they don't understand nor know how to restore and most of the time .. they think they caused the issue.
> they think they caused the issue.
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.
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.
there should be a "if you made a mistake, it means the company did something wrong" message on computers
Yes, it's really a disservice to have "Please contact your administrator for assistance" messages, putting the user in a "you should get some help" position that rubs a lot of people the wrong way.
Font smoothing is messed up too. For some utterly inexplicable reason, starting with Big Sur Apple turned on font smoothing by default, and then removed the toggle in settings to turn it off, despite the fact that it looks like complete crap.
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.
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.
What do you mean by "font smoothing"?
Subpixel antialiasing has been disabled and steadily pruned from the OS since Mojave if that's what you're talking about:
https://gankra.github.io/blah/text-hates-you/
Subpixel antialiasing has been disabled and steadily pruned from the OS since Mojave if that's what you're talking about:
https://gankra.github.io/blah/text-hates-you/
I think it's separate to subpixel anti-aliasing. It's whatever was controlled by the old "Use LCD font smoothing where available" in System Preferences > General.
With that toggle gone, it can still be toggled using the "AppleFontSmoothing" defaults key.
With that toggle gone, it can still be toggled using the "AppleFontSmoothing" defaults key.
Jeez, imgur sucks. I looked for a minute at an unrelated meme trying to figure out where in its comments your example was, and then I noticed the thin image at the top (yours).
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.
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.
Yeah, I haven't used imgur for a while and it took me a hot second to work out how to upload an image—a button labelled "new post" is completely contrary to what imgur is in my head.
Yeah, and AFAIK they took out the easy-upload API as well (last time I checked). It's kind of inevitable when you have to make money, though.
That why I always prefer to share the image, not the imgur link:
https://i.imgur.com/Dwd5Dzg.png - much better!
https://i.imgur.com/Dwd5Dzg.png - much better!
What screen resolution are you using?
That was taken on my external monitor which is 2560x1440 (1x scaling/non-retina).
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.
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.
Try putting this in a file with a `.css` extension:
But see also: https://tonsky.me/blog/monitors/
* {
-webkit-font-smoothing: antialiased !important;
}
But see also: https://tonsky.me/blog/monitors/
It was the Tonsky post that drove me to always making sure I had the smoothing disabled. I didn't know about the custom CSS though, thanks!
After “upgrading” to Big Sur the first thing I searched for was disabling font smoothing. The default looks ridiculously ugly. I was shocked that they removed the toggle from the system preferences. Apple is all about design and then they double down on something this ugly?
Everything works for me (Mojave with Safari 14.1).
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").
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").
ebay.com crashes like clockwork [0]. cnn.com also used to crash, but not anymore. Maybe something with the tracking updates.
[0] https://streamable.com/9thaf7
[0] https://streamable.com/9thaf7
The error message that Safari is showing means that the web content process is crashing. This should leave logs in ~/Library/Logs/DiagnosticReports (easily viewable in Console, under "Crash Reports"). Without those it's unlikely that anybody will be able to provide any further information as to what is happening here.
Thanks for this comment! I applied this security update yesterday and it updated Safari and I get the same reliable crashes on some web pages. The really annoying thing is after it crashes a couple of times it blanks out the whole page. Normally there's a small banner that says "this page crashed" sure, but now it is a full screen error message saying "this page crashed too many times", making the site entirely unusable.
Every time it crashes in the same place and leaves this in the logs:
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
owyn: Same here! Did some digging and noticed something that might help. Notice in the "Symbol not found" the WebKit is looking in the dylib for a big honkin' symbol with "_jPKhmttEPFiS0_" near the end. When I opened the libwebrtc.dylib file in TextEdit, I see a very similar big honkin' symbol, but it's missing "tt" near the end. So that part of the symbol reads, "_jPKhmEPFiS0_". Don't know who's to blame, the WebKit or dylib file, but these two parts of Safari appear to identify some "setVideoDecoderCallbacks" code by 2 different names, and that's causing this crash!
Someone found a fix for it and it worked for me. If you re-install the Safari package again, it resolves the issue. Looks like it was the "combo" update that broke safari by installing things in the wrong order, which probably is why only some people were affected. Also "why software is hard".
[0] https://forums.macrumors.com/threads/safari-14-1-is-complete...
[1] https://www.macupdate.com/app/mac/15675/apple-safari
[0] https://forums.macrumors.com/threads/safari-14-1-is-complete...
[1] https://www.macupdate.com/app/mac/15675/apple-safari
Slightly off topic rant: Safari’s dev tools are completely unusable too: most of the times the line number of a (JS) error is absent or wrong, especially if the error originates from an ES module (I submitted several bugs to webkit).
It’s a browser I want to love – especially for its performance – but it’s becoming harder.
It’s a browser I want to love – especially for its performance – but it’s becoming harder.
I’ll add. Fresh Big Sur install on the fastest MacBook 16” in store now: After changing the selected DOM element it takes several seconds to show its CSS on the right sidebar.
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 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
Give Firefox dev tools another chance. I use them exclusively wherever I can.
Is this really a big thing? I went expecting hundreds of angry comments but there are 11 comments in this discussion and 11 on the macrumors discussion that someone mentioned?
I have gone from zero Safari crashes anywhere to multiple times a day Safari crashes. I didn't start a thread on it; I switched to using Edge and Firefox for sites that crash Safari.
Well, it sure is for me. I immediately noticed it and started ranting about it on a tech channel at work. This security update just went out a couple of days ago so it probably isn't widely distributed yet. One of my co-workers also applied the update just out of curiosity and ran into the same issue. Maybe it depends on what sites matter to you perhaps but it makes my bank web site unusable for instance.
What is completely broken for me since macOS 11/iOS 14 update is iCloud tabs. They simply don't sync between Mac and iPhone anymore, the list is almost always empty. Sometimes it contains some random out-of-date links, but touching any of them make them all disappear.
Another discussion at https://forums.macrumors.com/threads/safari-14-1-is-complete...
... which is also unreadable with Safari!
No, it renders perfectly.
Same here (Big Sur 11.3 / M1), also ebay, etc work perfectly.
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?)
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?)
Apple should work on being able to update Safari, Podcasts, etc independently of the OS.
New bugs in OS + new bugs in Safari is not a good combination.
New bugs in OS + new bugs in Safari is not a good combination.
This happens to me every day of the week on various sites, multiple times a day. I assumed it was because I had a large number of tabs open (anywhere from 50 to 200), but it's very frustrating. Only thing I can do is quit Safari and re-open, then it goes away for a few hours, then it'll happen again. After a few rounds of that my only choice is to restart the iPad. That buys me a few more hours, but it eventually happens again. Supremely frustrating. Started happening maybe a year ago, never once happened before that. My guess is poor quality control or testing on an update, bug or memory leak was introduced and just never fixed. Very frustrating. Apple stuff is supposed to "just work" but in this case, the browser crashes multiple times a day which is an awful user experience.
I got the "a problem repeatedly occurred" error in Mobile Safari on iOS 14.5 just a moment ago when playing with this demo: https://replidraw.vercel.app/d/orx5hodjsll
The problem with Iphone is in addition that Apple only allows their own browser to exist. I mean yes, you can get another browser, but it is just a skin of safari. You can't switch to another engine.
So in this case, less than ideal.
So in this case, less than ideal.
[deleted]
This happened to my dad when he upgraded the other day and I spent hours painstakingly trying to fix it and it seems like the recommended fix is reinstalling OSX. Well, he's on Firefox now but what the fuck - this basically affects all the websites he goes to. I can't believe this made it out through testing.
[deleted]
Well, I'm running 14.1 and it seems fine. So, as usual with these hyperbolic titles, the problem is either something else, or a combination of separate issues.
The title isn't hyperbolic if the software is completely unusable for the people reporting the issue, which it is. What part of "tabs crash repeatedly and then go away, preventing you from visiting websites" sounds usable to you?
How would the reporter know if the issue is specific to them or applies to everyone without posting a thread about it?
How would the reporter know if the issue is specific to them or applies to everyone without posting a thread about it?
Of course it is. If it would happen 100% of the time it would've never been released. But judging from the amount of comments there and on macrumours it doesn't seem to be a too exotic cause either.
Yeah all the sites in question seem to be working fine for me too.
I was actually pleased they’ve finally implemented date/time inputs so I can stop using JS calendars now.
I was actually pleased they’ve finally implemented date/time inputs so I can stop using JS calendars now.
ebay.com crashes like clockwork [0]. cnn.com also used to crash, but not anymore. Maybe something with the tracking updates.
[0] https://streamable.com/9thaf7
[0] https://streamable.com/9thaf7
Can’t say I’ve had any significant issues yet other than it duplicating all of my bookmarks after the upgrade for some reason.
Apple's premier operating system is worse than Windows 95. How the mighty have fallen.
macOS isn't a growth area for Apple. It's a legacy product, which no longer has it's own team, and macOS contributes to a tiny portion of Apple revenue. It basically only exists for software developers. Apple's advertising pushes people who were thinking about laptops to use iOS devices.
Not saying macOS wasn't great. It was. But Apple aren't investing in it anymore.
Not saying macOS wasn't great. It was. But Apple aren't investing in it anymore.
> Mac sales went from $5.4B to a record $9.1B year-over-year.
https://daringfireball.net/linked/2021/04/28/aapl-q2-2021-re...
https://daringfireball.net/linked/2021/04/28/aapl-q2-2021-re...
Not sure how that responds to or invalidates anything above.
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...
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...
I don’t have access to the statistic you are referring to, so we might be talking past each other. But, as far as I can tell, macOS is a growing part of Apple’s revenue, at least over the last year:
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.
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.
Sorry about that, the site lets users in from Google for free, but puts ad walls up for direct links. Sneaky.
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.
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.
It basically only exists for software developers.
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.
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.
Sure. I don’t think anyone said developers were unnecessary, they’re just not a big chunk of apple’s revenue or business plans.
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.