News for hackers. Stuff that matters.

A comment on Starting January 4 Google will block sign-ins from embedded browser frameworks. Parent comment

Re:Starting January 4 Google will block sign-ins from embedd... by Wowfunhappy on Thursday November 19, 2020 @09:52PM (#25156923)
Actually, when I was reading Google's blog post, this rule jumped out to me:

> The browser must not provide automation features. This includes scripts that automate keystrokes or clicks, especially to perform automatic sign-ins.

Automating keystrokes and/or clicks could absolutely be necessary for accessibility.

[ Parent | on HN ]
Re:Starting January 4 Google will block sign-ins from embedd... by nitrogen on Thursday November 19, 2020 @10:16PM (#25157027)
Doesn't Chrome itself provide automation features that are used by integration testing frameworks?
[ Parent | on HN ]
Re:Starting January 4 Google will block sign-ins from embedd... by thayne on Friday November 20, 2020 @12:14AM (#25157502)
yes it does.
[ Parent | on HN ]
Re:Starting January 4 Google will block sign-ins from embedd... by User23 on Thursday November 19, 2020 @11:12PM (#25157238)
Sounds like they're worried about fake ad clicks.
[ Parent | on HN ]
Re:Starting January 4 Google will block sign-ins from embedd... by Semaphor on Thursday November 19, 2020 @11:18PM (#25157268)
What does logging into google have to do with fake adclicks?
[ Parent | on HN ]
Re:Starting January 4 Google will block sign-ins from embedd... by londons_explore on Thursday November 19, 2020 @11:40PM (#25157350)
The ad clickspam system uses the logged in user (or lack of) as a strong signal.
[ Parent | on HN ]
Re:Starting January 4 Google will block sign-ins from embedd... by Semaphor on Thursday November 19, 2020 @11:55PM (#25157424)
Thanks.
[ Parent | on HN ]