What gives Apple?
Two different Danish newspapers. Can't be true I can only use one of them :)
Me neither.
manOS Catalina, Version 10.15.5. Safari Version 13.1.1 (15609.2.9.1.2)
EDIT: Still can't get used to Safari's URL completion behaviour. It is completely unnatural and hard to feel as useful, unlike chrome's which is very handy and behaves like I expect.
Close safari and reopen it.
Type in "Whitespace" then "Bookmarks and History" shows up. Highlight a result, then go to the end of the line and delete that work, thinking you'll be editing the url directly to get: https://github.com/Whitespace
It matches on the title and allows you to edit that, leaving you with the option to search on "Whitespace/glome: Glome! Powered by " which is extremely baffling.
My expectation is that it matches the url and allows me to edit it, which is something I do very often for github repos: type the name of the user, highlight a history result so https://github.com/ is filled out, then option delete the repo and type in the one I want to go to.
Safari expects me to "arrow right" or my (more or less) carefully crafted search will be auto removed (since the text will be "selected"). I fall for this x times per day (probably says more about me then about safari). Chrome will allow me to move to one of the suggestions and happily append my text without the need to "deselect" the text.
But there are more "usability" issues with Safari:
Why is the "x" to close a tab, on the left instead of right? Why do I need to press the ALT key to get the option to open a link in private mode (after a right click on the link)? Why can I not drag a URL to a bookmark folder directly? Why can I not re-attach a browser window as a tab in an open window?
I think these are both just macOS convention.
> Why can I not re-attach a browser window as a tab in an open window?
This seems to work for me?
Luckily the field in question was an actual email so I could fix it by changing the type, since all the official and apple custom attributes I tried failed to turn off the correction..
I would like the security of a non-android device, but using apple products is utterly infuriating with all the damn "help" missfiring all the time.
Speaking of that, I’d just like to say one more thing on this topic while I still have your attention here. While the things I mentioned here could have been filed a bit better, aside from that I really do try my best to report things I find, often in great detail and depth that I specifically take time out of my day for. I run Safari Technology Preview ten hours a day, every day, on whatever the latest developer beta is. (Yes, I’m running Big Sur and using yesterday’s build.) I think Safari is a great browser; I know everyone on the team is passionate and cares about making it better, and I’m sure they’d be disappointed to hear that I’m going around calling some part of it “totally broken” on a reasonably sized social website and that my experience is clearly shared by many of the people here.
But the usual Apple complaint still applies here: they need to be more responsive to reports, and yes they need to actually fix their stuff. I know this is not your team, and that you probably don’t have much control over this, but you’re surely in contact with them often and I’d appreciate it if you could remind them. I have filed literally dozens of Safari bugs in the last few years. It’s probably the component I file bugs against the most because I use it so much and because I care very much that it works right. But it’s disheartening to see maybe half of them getting any response at all, and of those just a couple with actual responses that are not just “please attach a sysdiagnose” or “this bug has been marked as a duplicate”. It’s disheartening to find bugs in Safari Technology Preview running on a developer seed and have them be ignored as they slowly make their way into public beta Safari and then into an official release where other people run into it. It’s disheartening when I can go a month without being able to launch Safari Technology Preview with it crashing immediately until I literally take a binary diff of Safari.framework, disassemble it, and find the exact change made and the circumstances that made it crash, and highlight it in a red circle along with a suggested patch to get it fixed correctly (Safari Technology Preview releases 37 and 38, rdar://problem/33815640, rdar://problem/34167199). More recently I was having crashes every two hours-or under load, even more frequently-because of something which I will bet you $10 is a data race in Safari’s Remote Web Inspector Lockdown code (this has stopped crashing but now causes an infinite loop, and I’ve become accustomed to attaching a debugger to Safari, breaking in the offending code, and suspending the lockdown queue from there; FB7660529). When you put out these prerelease builds and I take the time and effort to use them and file issues about them, I think the least I can expect is the bugs actually being fixed or barring even that just some acknowledgement of the issue. Thanks.
Folks who can reproduce the "sketch" --> "sketchers.com" behavior or the "realty.com" --> "realtor.com" behavior, would any of you be willing to file the issue via Feedback Assistant (only needs a free developer.apple.com account) with a sysdiagnose and a screen recording? Then give me the FB number.
I can get the Safari team to look at this, but I can't reproduce either behavior myself. Any other examples of bogus/unexpected autocomplete also welcome.
I looked at the FB# cited in the parent, but it doesn't have a specific example or a sysdiagnose. Since may of these things only reproduce for some users, we need all the data we can get to resolve these issues.