9 ms·

Posting reply here for more visibility. Folks who can reproduce the "sketch" --> "sketchers.com" behavior or the "realty.com" --> "realtor.com" behavior, would

by om2 6y ago

Posting reply here for more visibility. 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.

PostPlummer 6y ago
> but I can't reproduce either behavior myself 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.
- diminish 6y ago
  Apple is targeting the average user as usual and breaking the world wide web standards.
- piyush_soni 6y ago
  Shh ... Don't give them ideas, or else very soon Safari might be converted to a Chromium based browser as well :P - and that will be the end of browser war forever (yeah, Firefox is giving a tough fight but not in terms of market share).
  - nl 6y ago
    Well they are already both Webkit and that aspect is the problem (yes I know about Blink vs Webkit, but still).
    - piyush_soni 6y ago
      Yes, I know it's webkit based, but not entirely Chromium based like Microsoft Edge is. And as you already know Chromium is Blink based now.
- om2 6y ago
  Any specific feedback on completion behaviors that feel wrong?
  - foolmeonce 6y ago
    I recently ran into input fields being autocorrected and autocapitalized at 2 different levels (disabled it with an attribute and this caused a delayed capitalization by autocorrect instead of an immediate one) by safari in the iOS emulator.. 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.
    - om2 6y ago
      Input fields is a different thing than the location field. Please file that one too, if you have a reproducible case of autocorrect/autocapitalize that you don't expect.
  - Whitespace 6y ago
    Visit a url with the same work in the title and the url, ie https://github.com/Whitespace/Glome https://github.com/Whitespace/Glome 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 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/ https://github.com/ is filled out, then option delete the repo and type in the one I want to go to.
    - om2 6y ago
      Thanks for the specific example!
- lupinglade 6y ago
  A separate search and URL field would be nice, it’s just not the same thing. Issues with autocomplete and with copy and paste abound.
mh- 6y ago
I can reliably reproduce the "sketch" example on iOS 13. Is there anything helpful I can provide re: that?
- shuckles 6y ago
  You can probably get a sysdiagnose from your iOS device with: https://www.jessesquires.com/blog/2018/02/08/how-to-sysdiagnose-ios/ https://www.jessesquires.com/blog/2018/02/08/how-to-sysdiagn...
- om2 6y ago
  sysdiagnose, screen recording, file via Feedback Assistant if possible and share the FB#.Is this a relatively new device, or one you have been using for a while>
  - mh- 6y ago
    it's my daily driver, and I upgraded and restored from iCloud for the last few devices in a row so it's hardly pristine. I'll see if I can do a sysdiagnose tomorrow.
drevil-v2 6y ago
Unable to reproduce on iOS 13.5.1 FWIW I have none of those sites “sketch, sketchers, realty, realtor” in my history or bookmarks
heyoo 6y ago
I have another one. "b.dk" turns into "eb.dk". Two different Danish newspapers. Can't be true I can only use one of them :)
joshjdr 6y ago
I was able to stop this behavior by deactivating options in Settings > Siri & Search > Safari.
saagarjha 6y ago
Yes, you’re right, I did neglect to actually put a specific search term that was doing this for me. That was almost a year ago so I can’t completely remember why I didn’t, but I think it had to do with it being history-specific so I didn’t really think it would be all that helpful for reproducing the issue. Still, my mistake, and if it helps I think that I took that sysdiagnose right after reproducing that issue. As for the other bug: according to my history I first hit that on the 16th on my iPad. I didn’t file it at that point because 1. we don’t have tap-to-Radar so I’m a bit lazier about filing bugs when I’m not at my computer and 2. submitting bugs for something you saw once the week before WWDC is a surefire way to get it ignored. 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.
baxtr 6y ago
I want to stress the point that autocomplete on iOS Safari is not well designed either. It is one of these things that "customers will never tell you", but they still are annoyed every time .
dervjd 6y ago
Filed a report here: FB7796744 This has driven me absolutely nuts as well...occurs when trying to visit wbay.com (instead sends me to ebay.com)
- dpcx 6y ago
  I just triggered this myself - if I specifically type out the https portion, Safari won't change the URL, and from that point on I can get to wbay.com by just typing wbay.com.
- joenathanone 6y ago
  Wow, I just tried wbay.com and it sent me to eBay.com, I find this very disturbing.
  - qeternity 6y ago
    None of the others triggered for me but this does. I’m running the Big Sur beta and notice that spotlight search is comically wrong as well. What gives Apple?
    - om2 6y ago
      If you're curious why this happens, it's overzealous typo fixes.
  - sixhobbits 6y ago
    this happens to me too using safari on ipados
- om2 6y ago
  Thanks for filing. I can reproduce this one!

by om2 6y ago

PostPlummer 6y ago

> but I can't reproduce either behavior myself 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.

diminish 6y ago
Apple is targeting the average user as usual and breaking the world wide web standards.
piyush_soni 6y ago
Shh ... Don't give them ideas, or else very soon Safari might be converted to a Chromium based browser as well :P - and that will be the end of browser war forever (yeah, Firefox is giving a tough fight but not in terms of market share).
- nl 6y ago
  Well they are already both Webkit and that aspect is the problem (yes I know about Blink vs Webkit, but still).
  - piyush_soni 6y ago
    Yes, I know it's webkit based, but not entirely Chromium based like Microsoft Edge is. And as you already know Chromium is Blink based now.
om2 6y ago
Any specific feedback on completion behaviors that feel wrong?
- foolmeonce 6y ago
  I recently ran into input fields being autocorrected and autocapitalized at 2 different levels (disabled it with an attribute and this caused a delayed capitalization by autocorrect instead of an immediate one) by safari in the iOS emulator.. 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.
  - om2 6y ago
    Input fields is a different thing than the location field. Please file that one too, if you have a reproducible case of autocorrect/autocapitalize that you don't expect.
- Whitespace 6y ago
  Visit a url with the same work in the title and the url, ie https://github.com/Whitespace/Glome https://github.com/Whitespace/Glome 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 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/ https://github.com/ is filled out, then option delete the repo and type in the one I want to go to.
  - om2 6y ago
    Thanks for the specific example!
lupinglade 6y ago
A separate search and URL field would be nice, it’s just not the same thing. Issues with autocomplete and with copy and paste abound.

mh- 6y ago

I can reliably reproduce the "sketch" example on iOS 13. Is there anything helpful I can provide re: that?

shuckles 6y ago
You can probably get a sysdiagnose from your iOS device with: https://www.jessesquires.com/blog/2018/02/08/how-to-sysdiagnose-ios/ https://www.jessesquires.com/blog/2018/02/08/how-to-sysdiagn...
om2 6y ago
sysdiagnose, screen recording, file via Feedback Assistant if possible and share the FB#.Is this a relatively new device, or one you have been using for a while>
- mh- 6y ago
  it's my daily driver, and I upgraded and restored from iCloud for the last few devices in a row so it's hardly pristine. I'll see if I can do a sysdiagnose tomorrow.

drevil-v2 6y ago

Unable to reproduce on iOS 13.5.1 FWIW I have none of those sites “sketch, sketchers, realty, realtor” in my history or bookmarks

heyoo 6y ago

I have another one. "b.dk" turns into "eb.dk". Two different Danish newspapers. Can't be true I can only use one of them :)

joshjdr 6y ago

I was able to stop this behavior by deactivating options in Settings > Siri & Search > Safari.

saagarjha 6y ago

Yes, you’re right, I did neglect to actually put a specific search term that was doing this for me. That was almost a year ago so I can’t completely remember why I didn’t, but I think it had to do with it being history-specific so I didn’t really think it would be all that helpful for reproducing the issue. Still, my mistake, and if it helps I think that I took that sysdiagnose right after reproducing that issue. As for the other bug: according to my history I first hit that on the 16th on my iPad. I didn’t file it at that point because 1. we don’t have tap-to-Radar so I’m a bit lazier about filing bugs when I’m not at my computer and 2. submitting bugs for something you saw once the week before WWDC is a surefire way to get it ignored. 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.

baxtr 6y ago

I want to stress the point that autocomplete on iOS Safari is not well designed either. It is one of these things that "customers will never tell you", but they still are annoyed every time .

dervjd 6y ago

Filed a report here: FB7796744 This has driven me absolutely nuts as well...occurs when trying to visit wbay.com (instead sends me to ebay.com)

dpcx 6y ago
I just triggered this myself - if I specifically type out the https portion, Safari won't change the URL, and from that point on I can get to wbay.com by just typing wbay.com.
joenathanone 6y ago
Wow, I just tried wbay.com and it sent me to eBay.com, I find this very disturbing.
- qeternity 6y ago
  None of the others triggered for me but this does. I’m running the Big Sur beta and notice that spotlight search is comically wrong as well. What gives Apple?
  - om2 6y ago
    If you're curious why this happens, it's overzealous typo fixes.
- sixhobbits 6y ago
  this happens to me too using safari on ipados
om2 6y ago
Thanks for filing. I can reproduce this one!