# Odd problem with function node in v1.1.3. Bug?

**URL:** <https://discourse.nodered.org/t/odd-problem-with-function-node-in-v1-1-3-bug/33636>\
**Category:** General\
**Created:** [1 October 2020 16:51 UTC](https://discourse.nodered.org/t/odd-problem-with-function-node-in-v1-1-3-bug/33636 "2020-10-01T16:51:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [1 October 2020 16:54 UTC](https://discourse.nodered.org/t/odd-problem-with-function-node-in-v1-1-3-bug/33636/2 "2020-10-01T16:54:48Z")

</div>

I replied in the previous thread, but it appears to have all been deleted, so has been lost.

In my reply I linked to another discussion that explains what you are seeing:

> As part of another fix (discussed [here](https://discourse.nodered.org/t/function-node-issues-invalid-properties-noerr-chrome-closing-editor-while-in-setup-or-close-tab/33128/8) with an explanation), some code was added to ensure ace errors would always be displayed (as they could sometimes be reported against line numbers outside of your actual code).

---

_[View the full topic](https://discourse.nodered.org/t/odd-problem-with-function-node-in-v1-1-3-bug/33636)._