# Safari doesn't show every setting in property Editor

**URL:** https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463
**Category:** General
**Created:** [11 April 2023 17:01 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463 "2023-04-11T17:01:29Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![FloRu](https://avatars.discourse-cdn.com/v4/letter/f/db5fbb/32.png) [@FloRu](https://discourse.nodered.org/u/FloRu)
#### Post date: [11 April 2023 17:01 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/1 "2023-04-11T17:01:29Z")

</div>

Hi!

I wonder if someone else sees this problem:  
When I open up the properties of any nodes, Safari doesn't show every settings that I set up before.

Looks like this. The first time I open up the properties:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/e/2ea857466aa456112a1a7da42e34c2654bfe709e.png)

and the second time I open it up:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/9/f943ea66db50ebac3b690204061493e096fbfce3.png)

In this particular case it doesn't show the "action"...

When I use Firefox, everything shows up right.

My Mac uses Ventura 13.3.1 / Safari Version 16.4 (18615.1.26.11.23) (with content blocker disabled) (all new), and Node-RED is Version 3.0.2 with Node.js Version 19.9.0 on top of a dietpi system.

Do you have any ideas?  
Thanks in advance!  
Florian

---

<div class="post-metadata">

### Author: ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)
#### Post date: [11 April 2023 17:24 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/2 "2023-04-11T17:24:42Z")

</div>

Hi @FloRu - Welcome to the forums.

I can confirm the same behaviour (Safari).  
Are you able to log an issue in Github?

> **[GitHub - node-red/node-red: Low-code programming for event-driven applications](https://github.com/node-red/node-red)**
>
> Low-code programming for event-driven applications - GitHub - node-red/node-red: Low-code programming for event-driven applications

any non-safari users?

![Apr-11-2023 18-21-46](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/c/dc417d47e37f40c60e3f696703af4838488f574a.gif)

---

<div class="post-metadata">

### Author: ![FloRu](https://avatars.discourse-cdn.com/v4/letter/f/db5fbb/32.png) [@FloRu](https://discourse.nodered.org/u/FloRu)
#### Post date: [11 April 2023 17:58 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/3 "2023-04-11T17:58:14Z")

</div>

Thanks Marcus for your reply and your confirmation.

I logged an issue... [here](https://github.com/node-red/node-red/issues/4136)

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [11 April 2023 19:13 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/4 "2023-04-11T19:13:21Z")

</div>

Safari is the new IE 😂

Do you see any errors in the browsers console?

---

<div class="post-metadata">

### Author: ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)
#### Post date: [11 April 2023 19:21 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/5 "2023-04-11T19:21:44Z")

</div>

IE 🤮

I was happy to know Edge is now using the same webkit engine (I think right?), but can't bring myself to use it.

But nope - Console is empty

---

<div class="post-metadata">

### Author: ![FloRu](https://avatars.discourse-cdn.com/v4/letter/f/db5fbb/32.png) [@FloRu](https://discourse.nodered.org/u/FloRu)
#### Post date: [11 April 2023 19:29 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/6 "2023-04-11T19:29:31Z")

</div>

In Safari I can see a 404:

> [Error] Failed to load resource: the server responded with a status of 404 (Not Found) (gridstack.min.map, line 0)

and it's the URL:

> [https://192.168.198.120:1880/admin/gridstack.min.map](https://192.168.198.120:1880/admin/gridstack.min.map)

---

<div class="post-metadata">

### Author: ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)
#### Post date: [11 April 2023 19:31 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/7 "2023-04-11T19:31:46Z")

</div>

That can be ignored - it's normal (for most `.map` files)  
its for debugging purposes

I think webkit browsers try to load them when the debugging consoles are open - safe to ignore

---

<div class="post-metadata">

### Author: ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [11 April 2023 21:15 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/8 "2023-04-11T21:15:46Z")

</div>

> [@FloRu](#):
>
> Node.js Version 19.9.0

Try downgrading to node.js v18

---

<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: [11 April 2023 21:29 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/9 "2023-04-11T21:29:36Z")

</div>

The version of node.js being used is irrelevant to the behaviour in the editor.

We have an open issue for this now. It appears to be easily recreated.

If anyone has anything material to add, please do so on the issue. But at this point, it just needs debugging and fixing.

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [12 April 2023 10:21 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/10 "2023-04-12T10:21:27Z")

</div>

Does anyone have Safari v16.0 ~ 16.3

There is a working theory in the [GitHub issue](https://github.com/node-red/node-red/issues/4136#issuecomment-1505027052) that Safari 16.4 may have unearthed this issue.

**EDIT/UPDATE:**

Confirmed. Safari 16.4 is the reason. Thanks everyone, this will greatly help us focus in on the issue and understand the problem.

---

<div class="post-metadata">

### Author: ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [22 May 2023 20:17 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/11 "2023-05-22T20:17:56Z")

</div>

The GitHub issue seems to have been closed.

It appears that the issue has been fixed in macOS 13.4, Safari version 16.5.

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [22 May 2023 21:03 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/12 "2023-05-22T21:03:59Z")

</div>

Yes - now seems fixed to me. (on Safari 16.5)

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [22 May 2023 23:20 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/13 "2023-05-22T23:20:24Z")

</div>

> [@marcus-j-davies](#):
>
> I was happy to know Edge is now using the same webkit engine (I think right?), but can't bring myself to use it.

No, Edge uses Chromium which uses the same engine as Chrome and various other browsers. Though browsers on iOS have to use webkit. Chromium uses Blink which was a fork of webkit but is generally more current with web standards.

Edge has some excellent features, especially if you use other Microsoft cloud services. And it has the major advantage of not sending all your data to Google (though it does send some data to Microsoft of course - but Microsoft's main revenue does not come from advertising like Googles does).

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [5 June 2023 23:20 UTC](https://discourse.nodered.org/t/safari-doesnt-show-every-setting-in-property-editor/77463/14 "2023-06-05T23:20:59Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
