Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Safari 17 issues on macOS 12.7 Monterey
- Thread starter msephton
- Start date
- Sort by reaction score
They can't answer tens of thousands of reporters, but they do analyse and note crash reports. Probably store these as well somehow.
To get a response you talk to Apple support. The quality of which varies wildly, but see it as a sport.
Last edited:
Reiterating that it's kinda important to report issues directly to Apple, using their Feedback forms. I'm convinced they affect the development teams, but we should know our issues aren't the only issues. There is a priority. Sometimes its skewed to say the least, but staying silent is guaranteeing nothing will happen.
To give feedback on Safari use Feedback form Safari.
I just sent this:
"Safari 17.3.1:
Prerequisite:
having duckduckgo as primary search engine in Settings.
Do:
search by entering terms in the address bar and press return-key.
Happens:
results are shown at duckduckgo.com, but scrolling doesn't work as all content is frozen in place.
Expected:
results being shown at duckduckgo.com and scrolling to work normally."
To give feedback on Safari use Feedback form Safari.
I just sent this:
"Safari 17.3.1:
Prerequisite:
having duckduckgo as primary search engine in Settings.
Do:
search by entering terms in the address bar and press return-key.
Happens:
results are shown at duckduckgo.com, but scrolling doesn't work as all content is frozen in place.
Expected:
results being shown at duckduckgo.com and scrolling to work normally."
Just an idea:
If people post sites where scrolling doesn't work, others can try to see if this is true also for them. This could be useful info for tracking down the cause for this no scroll issue. Workable?
For me, this basically only happens with duckduckgo.com when searching from the address bar.
If people post sites where scrolling doesn't work, others can try to see if this is true also for them. This could be useful info for tracking down the cause for this no scroll issue. Workable?
For me, this basically only happens with duckduckgo.com when searching from the address bar.
Still happening in Apple's Safari 17.3.1. Unfortunately this is the garbage you get when a company is more obsessed with yearly upgrades instead of fixing the existing problems. The blue bar below is supposed to show black text.
i’m running safari 17.3 with monterey totally sans issue, so i fail to understand why some users are having problems.
that said, i find duckduckgo’s new browser to be much easier and secure to use.
just a personal preference.
a suggestion, if i may - move away from googlay as your search engine.
they’re snoops and possible part of the prob?
just have to look at the memory hog ‘chrome’ to realise their weird intent
I don't have problems with safari freezing, the issue I have with safari is some websites like the national weather service chicago page opens, but if wanting to open another tab in that site, the new tab constantly closes with this website has repeatedly encountered a problem and was closed. It does not do that in firefox, or ddg browsers or ew chrome browser. That is really my main annoyance with safari.... I actually prefer safari over the others.
I have freezing issues on Safari 17.3 and I isolated the problem to the AdGuard for Safari extension. I disabled it and left the other AdGuard content blocker extensions active to fix the issues.
OK, but I don't see that in Safari 17.3.1 on macOS 13.6.4. This means this is not systemic to Safari. Could still be a bug, certainly for Monterey, but it's not reproducible for everyone using Safari 17.3.1.
Or it could be a setting. What about extensions?
No extensions installed. Duplicated on two systems with fresh installs of Monterey 12.7.2.
For those still on Monterey (as of Oct 31 '24) the issue still persists on Safari 17.6 and macOS 12.7.6.
Whether I haven't found a permanent fix (and probably never will on this config), I've discovered the next best thing: toggling reader mode unfreezes the page.
So pressing `Cmd+Shift+R` (enter Reader mode) followed by `Esc` (exit Reader mode) makes current tab responsive again.
Whether I haven't found a permanent fix (and probably never will on this config), I've discovered the next best thing: toggling reader mode unfreezes the page.
So pressing `Cmd+Shift+R` (enter Reader mode) followed by `Esc` (exit Reader mode) makes current tab responsive again.