# Prevent Chrome from autofilling username in node name

**URL:** <https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551>\
**Category:** Core Development\
**Created:** [7 December 2018 01:24 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551 "2018-12-07T01:24:55Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![imnotknow](https://avatars.discourse-cdn.com/v4/letter/i/90ced4/32.png) [@imnotknow](https://discourse.nodered.org/u/imnotknow)\
**Post date:** [7 December 2018 01:24 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/1 "2018-12-07T01:24:55Z")

</div>

If I have my password to my node-red server saved in Chrome, Chrome will insert my username into the "Name" field of every node that I edit that does not have this field populated. On dashboard nodes, it inserts my username into the icon field.

There is likely a way to instruct Chrome to disable password management after login via javascript or css. If so, this could be an easy fix.

---

<div class="post-metadata">

**Author:** ![Marooned](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marooned/32/2858_2.png) [@Marooned](https://discourse.nodered.org/u/Marooned)\
**Post date:** [7 December 2018 10:36 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/2 "2018-12-07T10:36:56Z")

</div>

Back in the days, you could add `autocomplete="off"` to input field however, now it's ignored by modern browsers.  
But browser store data using input name, so if you can, change that name to something more unique than `name`, eg: `<input name="myUniqueName">` etc.

---

<div class="post-metadata">

**Author:** ![mrvladis](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mrvladis/32/14688_2.png) [@mrvladis](https://discourse.nodered.org/u/mrvladis)\
**Post date:** [3 October 2019 09:00 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/3 "2019-10-03T09:00:33Z")

</div>

Did anyone found a solution for this problem in NodeRed and Chrome?

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 October 2019 09:12 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/4 "2019-10-03T09:12:48Z")

</div>

@mrvladis in NR1.0 we've added a couple more tricks to discourage Chrome from 'helping' in this regard.

---

<div class="post-metadata">

**Author:** ![mrvladis](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mrvladis/32/14688_2.png) [@mrvladis](https://discourse.nodered.org/u/mrvladis)\
**Post date:** [3 October 2019 09:25 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/5 "2019-10-03T09:25:34Z")

</div>

hi @knolleary

Yes, I have seen on GitHub, however didn't make any difference to me :(((

I am on nodered/node-red:1.0.0-1-12 and it still put my username into the entity field.

Thanks.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 October 2019 09:26 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/6 "2019-10-03T09:26:21Z")

</div>

Which node in particular? Or does it happen with all nodes?

---

<div class="post-metadata">

**Author:** ![mrvladis](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mrvladis/32/14688_2.png) [@mrvladis](https://discourse.nodered.org/u/mrvladis)\
**Post date:** [3 October 2019 09:34 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/7 "2019-10-03T09:34:21Z")

</div>

Hi @knolleary,

I mainly automate HomeAssistant (node-red-contrib-home-assistant-websocket  
0.15.0)

Thanks.

---

<div class="post-metadata">

**Author:** ![ammmze](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ammmze/32/16763_2.png) [@ammmze](https://discourse.nodered.org/u/ammmze)\
**Post date:** [5 February 2020 04:23 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/8 "2020-02-05T04:23:13Z")

</div>

Only one I notice it on is in that node-red-contrib-home-assistant-websocket module, in particular the `Entity ID` field. The others are fine. But it treats it as if its a username field, so the autocomplete that is given is saved credentials. And it's rather annoying because i've got a list of credentials for my domain. It looks like chrome only compares the last 2 segments of the domain name when suggesting credentials. So if i'm on `nodered.example.com` and i have saved credentials for `foo.example.com`, it suggests both the credentials for `nodered.example.com` and `foo.example.com`.

---

<div class="post-metadata">

**Author:** ![elyancorrea](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/elyancorrea/32/27497_2.png) [@elyancorrea](https://discourse.nodered.org/u/elyancorrea)\
**Post date:** [24 January 2024 20:37 UTC](https://discourse.nodered.org/t/prevent-chrome-from-autofilling-username-in-node-name/5551/9 "2024-01-24T20:37:27Z")

</div>

Anyone solve this? I've some progress using this code [security - Disable browser 'Save Password' functionality - Stack Overflow](https://stackoverflow.com/a/37292424) on ui-template node. But MS Edge still suggesting saved passwords if I click twice.

Maybe, this is a starting point.