Safari doesn't show every setting in property Editor #4136
Comments
|
I can confirm I have the same behaviour (have tested File Write, and the HTTP Request Node) I should note: The console is not producing anything of concern Forum Post: Node RED: 3.0.0 File Write Demo |
|
@marcus-j-davies are you also running node v19? @FlorianRueb can I ask why you are running a non LTS version of NODE please? Typically we recommend the LTS version of node (we do not test against odd numbered versions of node) |
|
Sorry, should have put Node version. Node V - v16.15.1 Safari 16.4 is stable/current (comes with OSX) |
|
Hi Steve, yes, that's because it is the installation via the standard routine in DietPi. |
|
I think I have found where the problem may lie This of course is happening both with, the file write node and the HTTP request node - maybe other nodes also 🤷♂️ Return type <select type="text" id="node-input-ret" style="width:70%;">
<option value="txt" data-i18n="node-red:httpin.utf8">a UTF-8 string</option>
<option value="bin" data-i18n="node-red:httpin.binary">a binary buffer</option>
<option value="obj" data-i18n="node-red:httpin.json">a parsed JSON object</option>
</select>Method <select type="text" id="node-input-method" style="width:70%;">
<option value="GET">GET</option>
<option value="POST">POST</option>
<option value="PUT">PUT</option>
<option value="DELETE">DELETE</option>
<option value="HEAD">HEAD</option>
<option value="use" data-i18n="node-red:httpin.setby">- set by msg.method -</option>
</select>This shows my findings
|
|
But it must be more nodes. |
|
Lots of speculation here; I'll add another one - which is as well visible in the example Marcus posted: The focus is jumping around wildly. When double clicking on the node, initially 'Nodes filtern' at the top of the left hand palette is focused, then the focus jumps on the incoming property window ... and thus eliminates - sometimes !! - the selection: The third time (in the example below) the value is displayed in the select element.
No really. With a sharp eye on your screen cast, you can see that the values are present, when the window is incoming ... but then changed! |
|
Weird weirdness. Thanks for the info guys. Plenty of clues. @marcus-j-davies if you know how to put break points on a dom element sub tree modification, perhaps you could see what call is clearing the list? Also, do you happen to have the 3.1.0 beta running somewhere? (To see if this is present in Safari on the latest beta too) |
|
I see the exactly same behavior with the |
|
I'm off the computer thingy for the night, but the only constant I'm seeing, is the difference between a select option using i18n and one that is not. If you select an option that is not using i18n, then it's fine. Example in the HTTP Request method. PUT, POST, GET etc etc do not use i18n - and they remain, but - use msg.method - does, and is not restored - or you have to click it to refresh the value. It seems (from my limited testing) that any select element value using i18n will be affected. 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. |
Oh, maybe it has something to do with that thing, where you open a function node, click inside the code and get many lines selected. I'll try to make a screen capture... marking.mov |
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 |
|
Thank you very much to all for the feedback and clues. It is certainly looking like it is a safari 16.4 thing - or somewhere to start digging :) |
|
@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. |
|
And with that. Here are the change logs for Safari 16.4 |
|
When I have the node properties open and then change MacOS to Dark Mode (or to Light from Dark) the captions reappear, but not the properties itself. After closing and opening the properties again the captions are gone again. |
|
Having the same problem with Node-red 3.0.2 and Safari 16.4. If I open Node Red in Brave/chrome Browser then it works fine |
|
It seems this issue may be resolved with safari 16.5. Can one other person please confirm? |
|
I cant test right now, as haven't updated to latest OS But!
Could be related 🤷♂️ |
|
Yes - 16.5 fixes it for me. |
|
Thank for confirming. Closing this issue. |
|
But not for me. Still empty properties in the forms. Running maxOS Ventura 13.4 (22F66) on Apple M2 Pro.
|
|
which node is that ? |
|
This is a state node. I see similar with a poll state node.
|
|
No I think I'm wrong now. It was the property caption not showing before. I was staring at empty properties that are not properties... This looks OK now. |
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
Environment
The text was updated successfully, but these errors were encountered: