1"use strict";(globalThis.webpackChunk_atlas_docs_zen=globalThis.webpackChunk_atlas_docs_zen||[]).push([[1130],{4056(e,t,o){o.d(t,{R:()=>i,x:()=>a});var r=o(2155);const s={},n=r.createContext(s);function i(e){const t=r.useContext(n);return r.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function a(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:i(e.components),r.createElement(n.Provider,{value:t},e.children)}},7373(e,t,o){o.r(t),o.d(t,{assets:()=>l,contentTitle:()=>a,default:()=>d,frontMatter:()=>i,metadata:()=>r,toc:()=>c});const r=JSON.parse('{"id":"address-lookup/prevent-autofill","title":"Prevent Autofill","description":"Sets the autocomplete= attribute of the input element. Setting this attribute aims to prevent some browsers (particularly Chrome) from providing a clashing autofill overlay.","source":"@site/docs/address-lookup/prevent-autofill.mdx","sourceDirName":"address-lookup","slug":"/address-lookup/prevent-autofill","permalink":"/docs/address-lookup/prevent-autofill","draft":false,"unlisted":false,"tags":[],"version":"current","frontMatter":{"title":"Prevent Autofill","sidebar_label":"Prevent Autofill"}}');var s=o(5723),n=o(4056);const i={title:"Prevent Autofill",sidebar_label:"Prevent Autofill"},a=void 0,l={},c=[];function u(e){const t={a:"a",code:"code",p:"p",...(0,n.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsxs)(t.p,{children:["Sets the ",(0,s.jsx)(t.code,{children:"autocomplete="})," attribute of the input element. Setting this attribute aims to prevent some browsers (particularly Chrome) from providing a clashing autofill overlay."]}),"\n",(0,s.jsxs)(t.p,{children:["The best practice for this attribute changes over time (see ",(0,s.jsx)(t.a,{href:"https://stackoverflow.com/questions/15738259/disabling-chrome-autofill",children:"https://stackoverflow.com/questions/15738259/disabling-chrome-autofill"}),") and is specific to different forms. If you are observing Chrome's autofill clashing on your form, update this attribute to the best practice du jour."]}),"\n",(0,s.jsxs)(t.p,{children:["Defaults to ",(0,s.jsx)(t.code,{children:'"none"'}),"."]})]})}function d(e={}){const{wrapper:t}={...(0,n.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(u,{...e})}):u(e)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.