Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://floss.social/users/curtmack/statuses/113398311517562809">curtmack (curtmack@floss.social)'s status on Monday, 16-Dec-2024 03:02:18 JST</a><a href="https://floss.social/@curtmack" title="curtmack@floss.social"><img src="https://gnusocial.jp/avatar/244812-48-20240224022447.webp" width="48" height="48" alt="curtmack" style="position: absolute; left: 0; top: 0;">curtmack</a></section><article><p>So, to recap: it is the opinion of Chrome's and Edge's developers that they can ignore autocomplete="off", and any workarounds you deploy today may not work in the future. In fact, the only reason they recognize that a website would want to disable autocomplete is... to provide its own autocomplete implementation.<br>Chromium delenda est.<br><a href="https://karsep5.hashnode.dev/browser-autofill-for-web-developers" rel="nofollow noreferrer">https://karsep5.hashnode.dev/browser-autofill-for-web-developers</a><br><a href="https://floss.social/tags/webDev" rel="tag">#webDev</a> <a href="https://floss.social/tags/wtf" rel="tag">#wtf</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4191816#notice-8193188">In conversation</a><time datetime="2024-12-16T03:02:18+09:00" title="Monday, 16-Dec-2024 03:02:18 JST">about 2 months ago</time> <span>from <span><a href="https://floss.social/@curtmack/113398311517562809" rel="external" title="Sent from floss.social via ActivityPub">floss.social</a></span></span><a href="https://floss.social/@curtmack/113398311517562809">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3706204">Edge (and other Chromium based browsers like Chrome) does make a controversial decision on autocomplete=off and chooses to support autocomplete. As the HTML spec indicates that “off” is a hint to the browser rather than a rule to be followed, this implementation still stays within the spirit of the document.Some web developers have been employing a workaround to this behavior by providing non-standard values to the autocomplete attribute. While it works to prevent the browser from showing autofill suggestions today, it is not advisable as the behavior could change in future. One of the primary reasons to suppress browser autofill is when the website has its own autosuggest implementation. To handle this case, use ariaHasPopup or ariaAutoComplete attributes which are recognized by Edge and avoids showing suggestions for that input box.</a></label><br><a href="https://cdn.masto.host/floss/media_attachments/files/113/398/262/104/916/167/original/df59e8ce78a15330.png" rel="external">https://cdn.masto.host/floss/media_attachments/files/113/398/262/104/916/167/original/df59e8ce78a15330.png</a></li><li><article><header><div>Domain not in remote thumbnail source whitelist: karsep5.hashnode.dev</div><h5><a href="https://karsep5.hashnode.dev/browser-autofill-for-web-developers">Browser autofill/autocomplete for website developers</a></h5><div> from <span>https://hashnode.com/@karsep5</span></div></header><div>How chromium and edge handle autofill, autocomplete, autosuggestions in web forms</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
curtmack (curtmack@floss.social)'s status on Monday, 16-Dec-2024 03:02:18 JST curtmack
So, to recap: it is the opinion of Chrome's and Edge's developers that they can ignore autocomplete="off", and any workarounds you deploy today may not work in the future. In fact, the only reason they recognize that a website would want to disable autocomplete is... to provide its own autocomplete implementation.
Chromium delenda est.
https://karsep5.hashnode.dev/browser-autofill-for-web-developers
#webDev #wtf
In conversationabout 2 months ago from floss.socialpermalink
Attachments
1. Edge (and other Chromium based browsers like Chrome) does make a controversial decision on autocomplete=off and chooses to support autocomplete. As the HTML spec indicates that “off” is a hint to the browser rather than a rule to be followed, this implementation still stays within the spirit of the document. Some web developers have been employing a workaround to this behavior by providing non-standard values to the autocomplete attribute. While it works to prevent the browser from showing autofill suggestions today, it is not advisable as the behavior could change in future. One of the primary reasons to suppress browser autofill is when the website has its own autosuggest implementation. To handle this case, use ariaHasPopup or ariaAutoComplete attributes which are recognized by Edge and avoids showing suggestions for that input box.
  https://cdn.masto.host/floss/media_attachments/files/113/398/262/104/916/167/original/df59e8ce78a15330.png
2. Domain not in remote thumbnail source whitelist: karsep5.hashnode.dev
  Browser autofill/autocomplete for website developers
  from https://hashnode.com/@karsep5
  How chromium and edge handle autofill, autocomplete, autosuggestions in web forms

Public

Embed Notice

HTML Code

Corresponding Notice