Odd bug in comment node

[drmibell]

Node-RED version: v1.3.5
Node.js version: v12.19.0

[{"id":"51ea8e42.9005c","type":"comment","z":"3cd40fb9.7975d","name":"hasOwnProperty","info":"","x":510,"y":620,"wires":[]},{"id":"fedb34cd.f530b8","type":"comment","z":"3cd40fb9.7975d","name":"hasOwnProperty()","info":"","x":730,"y":620,"wires":[]}]

This may be due to the fact that hasOwnProperty is a defined JS method name, but a quick look has not turned up any other cases. Please don't ask how I stumbled on this.

[dceejay]

please raise it as an issue so we can track it... thanks
(PS and same with other nodes like function etc...)

[knolleary]

Now fixed in git. Will be in the next 1.3.x and 2.x releases.

[Steve-Mcl]

Nick, does that also fix entering the comment __proto__.

I found that particular comment causes an array of issues e.g.

• after OKing the comment and clicking elsewhere, you cant get into the quick add popup (CTRL+Click),
• you cant delete the comment.
• Sometimes cannot get into any nodes UI
• And this is in the console log...
  

[knolleary]

Yes - it prevents all prototype pollution of the internal text dimension cache.