node-red: Safari doesn't show every setting in property Editor

Current Behavior

Opening the property dialog of a random node doesn’t show every settings field.

Expected Behavior

Open a property dialog, edit the settings fields, reopen the dialog > see what you’ve done.

Steps To Reproduce

Take a new flow, take a HTTP request node, open the property dialog, set up “GET” and “a UTF-string” as return, confirm the dialog. Then open up the dialog again and see: no method and no return to see!

Example flow

paste your flow here

Environment

Node-RED version: 3.0.2
Node.js version: 19.9.0
npm version: 9.6.3
Platform/OS: DietPi v8.16.2 (Node-RED Host) / macOS 13.3.1 (Client)
Browser: Safari Version 16.4 (18615.1.26.11.23)

About this issue

Original URL
State: closed
Created a year ago
Comments: 26 (10 by maintainers)

Most upvoted comments

@Steve-Mcl - Marcus requested that I test this.

I have a Mac with Safari 16.3 and the issue is not happening on Safari 16.3.

On the same NR system using my Safari 16.4 updated MacBook - the issue is there.

Hope that maybe helps narrow things down. I’ll hold off updating the 16.3 Mac in case you have more questions.

crxporter on Apr 12, 2023

And with that.

Here are the change logs for Safari 16.4 https://developer.apple.com/documentation/safari-release-notes/safari-16_4-release-notes <- Needle in here somewhere

marcus-j-davies on Apr 12, 2023

Has this been an issue since Safari 16.4 🤷‍♂️. Have only just noticed it - since its orginal report

My thoughts entirely. Would be good if someone still on 16.3 could check.

Safari 15.6.1 : The problem does not appear to be apparent.

It maybe note worthy, my 15.6.1 safari is on an x86 processor (its a dated Mac), and my 16.4 safari is using Apple Silicon.

Unless there are some wasm modules in use with all this? - I can’t imagine that will make any difference, but thought I’d mention it

marcus-j-davies on Apr 12, 2023

I see the exactly same behavior with the beta.1 & beta.2. Safari @ 16.4

ralphwetzel on Apr 11, 2023