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

241–250 of 393 posts

Re: Safari tries to fill username

#241

Post by lucb1e »

musingsole wrote: post #235
lucb1e wrote: post #229

Earlier quoted context omitted.

What is the "pedestrian" approach to self-driving cars? You mean walking rather than driving?

Rail or line following might be a more "pedestrian" approach to self-driving cars.

Ah I see, yeah, to be honest I don't get why we aren't simply doing that already. Adaptive cruise control we already have, draw one more line in the center of highway lanes, and have some warning system for 'accident up ahead, drive manually', and we could drive autonomously for any large distance without magic and without needing to have constant attention to take control when needed. This could easily have been implemented decades ago, but we didn't/don't and now we're still not at that level. So yeah, agree with the person I was replying to about the preference of non-magic there.

Re: Safari tries to fill username

#242

Post by yabones »

everydaypanos wrote: post #200

Imagine how much code like this is inside our "lightweight" browsers. All the code reviews that passed this on to production make you wonder how competent these browser makers actually are.. I think that the browser should not treat every input field as a personal info form for the current user. There are plenty of cases of web apps I can think of where disabling autocomplete is best user experience overall.

It scares the hell out of me thinking about this type of hacky trash anywhere near crypto or sandbox code. I like to think that they have more experienced people working on that, but I'm not quite naive enough to really believe it.

Re: Safari tries to fill username

#243

Post by alistairSH »

Retric wrote: post #159
Cthulhu_ wrote: post #131

Earlier quoted context omitted.

After 15 minutes, or 15 minutes of inactivity? The latter is defensible at least, in e.g. a public area where there is a risk of people leaving their desktops without locking them. I mean that's another policy issue that can be addressed (a policy that locks a system after x amount of inactivity), but as an app developer you can't know much about the system things are running on.

Careful. Filling out a long form isn’t 15 minutes of inactivity, but a huge range of websites assume it is.

Ugh, a form that takes 15 minutes or more to fill out, without any feedback or other interaction, is itself a UX problem. It should at least be auto-saving.

Re: Safari tries to fill username

#244

Post by OldTimeCoffee »

dvtrn wrote: post #201
_jal wrote: post #196

Earlier quoted context omitted.

It is no different than doctors or mechanics or lawyers. Reputation is your best guide. In security-land, there are some certifications that are fairly rigorous; some of those can serve as a distant second.

Doctors and lawyers are professions that are regulated by licensure, of which unauthorized practice comes with actual real and not made up legal consequences. Where is the similar licensure that tech security professionals are regulated by? I think that’s a big difference.

You may have missed the point being made. You find a good security professional the same way you find a good lawyer or doctor. Ask around for a reference for a good one. Then check their credentials (e.g., what certifications they have).

I believe there was an article on HN recently about a startup that used a "lawyer" that wasn't because they didn't check their credentials after getting a great reference. Just because there are consequences doesn't mean it doesn't happen.

Re: Safari tries to fill username

#245

Post by burlesona »

newbie578 wrote: post #41

Why would someone even use Safari instead of Chrome? Hell I would rather use Edge.

Safari is noticeably faster and drains significantly less battery life. Those are big reasons. There’s also a lot of nice integration between desktop and mobile Safari if you use both a Mac and an iPhone.

Re: Safari tries to fill username

#247

Post by HatchedLake721 »

wildrhythms wrote: post #222
HatchedLake721 wrote: post #170

Earlier quoted context omitted.

Can you share details?

Everyone loves CSS grid layout now, right? On Safari (both iOS and OS X) Safari does not support grid-gap, i.e. "gap" CSS property. https://developer.mozilla.org/en-US/docs/Web/CSS/gap#support... I use the fullscreen API to give prototype demos of a product to clients, and iOS [iPhone] Safari doesn't support the fullscreen API. https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_...

Looks like gap support landed last month in Safari 14.1 https://css-tricks.com/safari-14-1-adds-support-for-flexbox-...

Re: Safari tries to fill username

#248

Post by flats »

1337shadow wrote: post #23
Tokelin wrote: post #3

Earlier quoted context omitted.

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.

As a web developer, I, too, have had moments fixing a Safari bug that reminded me of dealing with IE in the past. But only passing moments, and I don’t blame Safari.

Supporting multiple browsers is a uniquely annoying aspect of web development, and almost every developer uses Chrome for development (I’m a Safari user and it’s kind of a running gag at work). This means that for most developers, Safari is the main browser they have to support that isn’t the one they use for development, which is a recipe for resentment.

Also, I bristle at this comparison a bit because Safari is wayyyyy better than IE ever was about adopting (and helping to draft) standards. They’re slower than the Chrome team and adopting new standards, but that’s because Alphabet and Apple’s business models are different, not because it’s an inherently good idea to adopt every new standard immediately (especially when many are focused on turning the web into a crappy replacement for native app platforms).

Re: Safari tries to fill username

#249

Post by ROARosen »

heinrichhartman wrote: post #56
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

I tend to side with Chrome here. IMHO, the decision of whether to show auto-complete should be with the user and not with the website. When I install an auto-complete add-on or activate a browser feature, I expect the AC to be available on ALL input fields, whether the site owner thought that would be a good idea or not. Now, there is a valid question on how the user should be able to configure the AC behavior, and h…

> IMHO, the decision of whether to show auto-complete should be with the user and not with the website

It;s fundamentally wrong to decide what 'rights' website users have (aside from when it comes to privacy).

There are myriad ways how a website can become un-user friendly to the point of being unusable not the least is of which you can completely disable the cursor or completely not display certain parts which are really there (e.g. display: none).

Point being there is a fundamental 'trust' which a user gives to a website developer, that the website they visit will behave as 'the developer' intended. The user even expects to get the site just s the developer created it, however 'bad' that may be.

Now of course it is in the interest of the web developer to make their site user-friendly if they want to appeal to a wide populace. But it is totally in the purview of the developer to make the site even completely unusable.

I don't understand how a browser has the audacity to force their assumptions on site behavior on the user/developer.

Re: Safari tries to fill username

#250

Post by pwinnski »

fvold wrote: post #72
alisonkisk wrote: post #24

Earlier quoted context omitted.

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.

I wonder what would happen if compilers/interpreters/lexers of various programming/scripting languages had this attitude. Why do web page authors get a pass? I mean, most web page authors today at least also do JavaScript, where a single out-of-place character can cause the whole thing to simply break. Yeah yeah, legacy and all that, but that's why we have doctypes.

The entire history of web browsers, from just about day two, demonstrates the folly of this approach.

The strictest, most standards-compliant browser in the world dies a quick death, every time. The most widely-used and popular browser play fast and loose with everything. If they're powerful enough, they retroactively get their fast-and-loose playing recognized as a standard.

Post reply on HN