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

31–40 of 393 posts

Re: Safari tries to fill username

#31

Post by realusername »

bryanrasmussen wrote: post #25
rimliu wrote: post #11

Earlier quoted context omitted.

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…

Yes that's it, I don't think I encountered a bug which is truly "unfixable" on Safari, there's always been some workaround one way or another but all of those random nonsense issues do take a lot of time to investigate so there's a lot of developers who will just give up.

Re: Safari tries to fill username

#33

Post by vincnetas »

yvoschaap wrote: post #18
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

Yes. The Chrome devs refuse to accept there are viable cases for not allowing autocomplete.

It's not up to Chrome devs to accept or deny viable use cases. As someone from comments mentions, it's in the spec, and chrome devs should not deviate from that irrelevant if what they think is accepted or not accepted use case. Or they should go and push for spec change.

Re: Safari tries to fill username

#34

Post by plasma »

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

tip: Using autocomplete="new-password" at least fixes the change password forms (so it wont pre-fill the password there).

See https://developer.mozilla.org/en-US/docs/Web/Security/Securi...

Re: Safari tries to fill username

#35

Post by eitland »

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

No. This is a small but important detail: Chrome is the new IE.

IE wasn't mainly a problem because it didn't support things, rather because it was - in the beginning - superior, but also had all sorts of non standard behaviour that Microsoft pushed and that made competition crazy hard.

Oh, and also because they pushed it relentlessly in all ways including - as was later confirmed in court - illegal ways.

Exactly like Chrome today except the multi billion fine and forced changes to Chrome is still only barely visible in the horizon.

But we will keep pushing, won't we? For the record: I think I have contacted local authorities twice officialy over the last 18 months and maybe once over twitter. If two more people do the same here in Norway that is starting to make a difference.

Same if ten people in France or Germany do it. Or if someone makes a story that goes viral or reaches the headlines somehow.

Don't give up everyone! Chrome is an excellent browser but don't think for a moment that Google won't close it down the very moment it has finally crushed competition.

Re: Safari tries to fill username

#36

Post by eru »

vincnetas wrote: post #33
yvoschaap wrote: post #18

Earlier quoted context omitted.

Yes. The Chrome devs refuse to accept there are viable cases for not allowing autocomplete.

It's not up to Chrome devs to accept or deny viable use cases. As someone from comments mentions, it's in the spec, and chrome devs should not deviate from that irrelevant if what they think is accepted or not accepted use case. Or they should go and push for spec change.

Why? The spec ain't God given.

Re: Safari tries to fill username

#37

Post by pilsetnieks »

reynard_le_faux wrote: post #21
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!

This smacks of a special case processing for some specific site. I suspect there's some wildly popular service which presents a page with just a password input for returning users who haven't logged in for a while but still have their cookies/sessions active; the page is oddly coded and the standard approach doesn't work so it needs this workaround; and the page is valuable enough for Apple users that this was deemed reasonable.

The first comment threads are all echoing derision of Safari as a janky browser but I feel that this is something that could be dissected 20 years later in a Raymond Chen-like blog [1] with how they had to painstakingly add a workaround in a newer version somewhere deep inside to make some questionable piece of software not crash or something.

[1] https://devblogs.microsoft.com/oldnewthing/

Re: Safari tries to fill username

#38

Post by bipson »

vincnetas wrote: post #33
yvoschaap wrote: post #18

Earlier quoted context omitted.

Yes. The Chrome devs refuse to accept there are viable cases for not allowing autocomplete.

It's not up to Chrome devs to accept or deny viable use cases. As someone from comments mentions, it's in the spec, and chrome devs should not deviate from that irrelevant if what they think is accepted or not accepted use case. Or they should go and push for spec change.

I guess there are just too many pages that break autocomplete, e.g. for username/password as a "security feature".

I encountered quite a few myself and was very annoyed. I guess devs took the "usability" side of the question.

EDIT: phrasing

Re: Safari tries to fill username

#39

Post by mjthompson »

yvoschaap wrote: post #18
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

Yes. The Chrome devs refuse to accept there are viable cases for not allowing autocomplete.

I'm sure there are valid reasons. Unfortunately, many sites disable it without a good reason, and in those cases, I am glad Chrome hinders their misguided efforts. Many banks, for instance, think password managers are bad and disable it. Chrome preventing them doing so is a good thing.

Re: Safari tries to fill username

#40

Post by irjustin »

eru wrote: post #36
vincnetas wrote: post #33

Earlier quoted context omitted.

It's not up to Chrome devs to accept or deny viable use cases. As someone from comments mentions, it's in the spec, and chrome devs should not deviate from that irrelevant if what they think is accepted or not accepted use case. Or they should go and push for spec change.

Why? The spec ain't God given.

That's how we ended up with decades of Internet Explorer.
Post reply on HN