News for hackers. Stuff that matters.
Re:Issue 914451: Autofill does not respect autocomplete="off" by donatj on Tuesday October 15, 2019 @03:22AM (#21256264)
You misunderstand. Specifically on sites without cross-user visible content, the JavaScript needs to get into the system via an input, POST or GET. When every user input is named something different, you have no ability to send a link with a JavaScript payload.
Re:Issue 914451: Autofill does not respect autocomplete="off" by Thorrez on Tuesday October 15, 2019 @10:22PM (#21266447)
Hmm, I guess it could provide some protection against some types of XSS, but it's not comprehensive. It doesn't provide any protection against stored XSS. And even for reflected XSS, it assumes the only dynamic thing in your URL is form inputs.

An example of something dynamic in your URL that's not a form input would be links to various articles posted through some type of CMS. For example http://example.com/article?id=foo or even http://example.com/article/foo . In both cases if foo doesn't exist, a badly-written error page could print out "Error, foo was not found" without escaping foo.