Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Safari tries to fill username

github.com

Post reply on HN
Print view View original

21–30 of 393 posts

Re: Safari tries to fill username

#21

Post by reynard_le_faux »

brandrick wrote: post #13

The assumption here that this is being triggered because Safari assumes any page with this phrase must be a login page sounds plausible (if odd) to me. However, anecdotally I imagine there will be an uptick in sites using similars phrases — as following easing of Covid restrictions around the world even little brick and mortar stores will be making such welcoming statements on/across their homepages. :D

Exactly, and isn't it likely to be used equally as a post login phrase? Which is how I discovered this "bug" in the first place!

Re: Safari tries to fill username

#22

Post by reynard_le_faux »

raverbashing wrote: post #20

I can see the PM with this story "As a user I want to feel welcome back to my websites hence my login information will be auto-filled if the sites welcome me back" (Though the real issue here seems to be field identification, not the auto-fill)

Yes. I thought changing the field to type="search" may avoid it but alas no.

Re: Safari tries to fill username

#23

Post by 1337shadow »

Tokelin wrote: post #3
realusername wrote: post #2

Just another day in web development with Safari, I'm not even surprised anymore. I've encountered so many of those "total nonsense" moments.

Looks more and more like Safari is the "modern" IE

As a webdev I can confirm that I have exactly the same experience supporting Safari that I had supporting IE 15 years ago.

Re: Safari tries to fill username

#24

Post by alisonkisk »

captainmuon wrote: post #5

Too much magic if you ask me. There are often two ways you can do something. In this case: - Explicit clean markup and a deterministic GUI or - Tons of heuristics and a magic GUI that works great most of the time but fails in ways that are hard to understand. I feel you get this tradeoff a lot in "clever" systems. Whether it is just finding the main text on a page, blocking ads, doing search, or even self-driving car…

Safari doesn't write the HTML, and web page authors don't write explicit clean markup, so the pedestrian approach doesn't work in the real world.

Re: Safari tries to fill username

#25

Post by bryanrasmussen »

rimliu wrote: post #11
realusername wrote: post #8

Earlier quoted context omitted.

Like SVG background issues https://stackoverflow.com/questions/40986798/repeated-svg-ba... clicking issues https://stackoverflow.com/questions/24077725/mobile-safari-s... (yeah even clicks are broken) background jank https://stackoverflow.com/questions/9983520/webkit-animation... (not sure it's exactly this bug but I do have fixes in the codebase for that) round corners https://stackoverflow.com/questions/50995411/ca…

There is a browser without bugs?

so - is this your defense of IE11 as well?

There are several questions regarding bugs - how many are there, how difficult are they to find, how difficult are they to fix.

It seems that there are many Safari bugs that are difficult to find, and to fix, which makes them worse than other browsers.

In this case I believe the bug is actually difficult to find, this guy found it but I bet a lot of developers just went and ahead and wrote it down as a bug with safari, can't or won't fix. But now we know it's an easy fix - don't write Welcome Back in a page if you don't want this behavior.

My question is if your language is another one - like lang="DE" will it then have the same behavior on a page with the German version of Welcome Back.

Are there other magic strings that serve the same purpose as Welcome Back in Safari's mind.

on edit: changed difficult to fix to difficult to find.

Re: Safari tries to fill username

#30

Post by reynard_le_faux »

WayToDoor wrote: post #7

Related, there is a "bug" in chrome that disabled autocomplete="off" on input elements, marked as won't fix https://bugs.chromium.org/p/chromium/issues/detail?id=587466

Safari also completely ignores autocomplete="off" when it thinks something is a username or password field. Even when, as a dev, I know it definitely isn't.
Post reply on HN