# Editing nodes - inconsistency where the NAME is

**URL:** <https://discourse.nodered.org/t/editing-nodes-inconsistency-where-the-name-is/33481>\
**Category:** Feature Requests\
**Created:** [28 September 2020 22:32 UTC](https://discourse.nodered.org/t/editing-nodes-inconsistency-where-the-name-is/33481 "2020-09-28T22:32:06Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [30 September 2020 05:52 UTC](https://discourse.nodered.org/t/editing-nodes-inconsistency-where-the-name-is/33481/10 "2020-09-30T05:52:31Z")

</div>

In the early days I used to add the name at the bottom of my config screen, because I considered my own properties much more important ...  
However now I tend to put it on top, because for large config screens it becomes a bit lost at the bottom. Especially when e.g. an editableList is not filling the height correctly (due to some lack of CSS knowledge 🤫), because then the name field might disappear from the screen ...

But when having a (useful) discussion like this, it somehow feels like an (optional) name field should have been (fixed) somewhere at the top of the config screen. Since most nodes have such a name field. But no need to discuss that (!!), since it would be too late to introduce that now anyway.

---

_[View the full topic](https://discourse.nodered.org/t/editing-nodes-inconsistency-where-the-name-is/33481)._