# ✅ Disable "Autofill On Page Load" option for specific logins

**URL:** <https://community.bitwarden.com/t/disable-autofill-on-page-load-option-for-specific-logins/22>\
**Category:** Password Manager\
**Tags:** app:browser, released\
**Created:** [March 8, 2018, 1:27am UTC](https://community.bitwarden.com/t/disable-autofill-on-page-load-option-for-specific-logins/22 "2018-03-08T01:27:44Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![eliykat](https://sea1.discourse-cdn.com/flex001/user_avatar/community.bitwarden.com/eliykat/32/5865_2.png) [@eliykat](https://community.bitwarden.com/u/eliykat)\
**Post date:** [September 17, 2020, 12:08am UTC](https://community.bitwarden.com/t/disable-autofill-on-page-load-option-for-specific-logins/22/23 "2020-09-17T00:08:20Z")

</div>

@tgreer Would this be suitable for a Github Contribution? I could look at:

- disabling autofill on page load for excluded URIs (per this thread)
- implementing different match detection options, so that users can exclude certain URIs more precisely (currently it is domain level matching only)

My pending PR for [managing Excluded Domains](http://community.bitwarden.com/t/ability-to-manage-excluded-domains/14194/) would be amended as part of these changes. I think this would really flesh out this functionality.

However, I also understand if you want to leave it for the internal team - I’m not sure how your internal backlog interacts with community contributions.

---

_[View the full topic](https://community.bitwarden.com/t/disable-autofill-on-page-load-option-for-specific-logins/22)._
