# Odd behaviour or error with Safari 27 on Mac
**URL:** https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788
**Category:** General
**Created:** [15 September 2026 16:17 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788 "2026-09-15T16:17:11Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@SteveD](https://discourse.nodered.org/u/SteveD)
#### Post date: [15 September 2026 16:17 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/1 "2026-09-15T16:17:11Z")
My Mac updated to Safari 27 today and now I get an annoying behaviour. When I first open the NodeRED editor in a fresh Safari I can't navigate away from the first tab. Whenever I click another tab it displays the new tab and then an error causes Safari to reload the page which takes me back to the first tab again. It isn't catastrophic because oddly if I manually reload the webpage the problem goes away.
After messing around with the dev console settings I managed to catch the error that seems to be causing it:
TypeError: undefined is not an object (evaluating '(0,Ot.fz)().navigator.clipboard.write')
If you're thinking the solution would be to use another browser, a proper browser, or Chrome, then thanks in advance 🙂
Thought someone might be interested.
Steve
P.S. That's in editor.js
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [15 September 2026 19:13 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/2 "2026-09-15T19:13:49Z")
> [@SteveD](#):
>
> `.navigator.clipboard.write`
Do you have that somewhere in your flows? If not, it seems rather suspect. Nothing should be trying to do a clipboard action until a user has interacted with the page.
---
### Author:  [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)
#### Post date: [15 September 2026 19:48 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/3 "2026-09-15T19:48:46Z")
> [@TotallyInformation](#):
>
> somewhere in your flows
It's used by the Monaco editor ...
> [@SteveD](#):
>
> P.S. That's in editor.js
... as Steve mentioned.
---
### Author:  [@SteveD](https://discourse.nodered.org/u/SteveD)
#### Post date: [15 September 2026 22:04 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/4 "2026-09-15T22:04:38Z")
Thanks for replying. To be clear I'm very confident that this was brought on by Safari 27. I've been working with this set of flows for weeks in Safari 26.
I know it's just the reality of web-based applications - having to deal with different browsers which should provide the same runtime environment, but don't. It's just as likely to be a bug in Safari 27, but I think it's a bit more likely that one of the NodeRED guys will code around it, than Apple will address it. That's just the way of the world.
Cheers
Steve
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [16 September 2026 06:03 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/5 "2026-09-16T06:03:40Z")
Just checking I understand the concern. You are saying that when you click on a workspace tab (e.g. flow 2), your browser refreshes?
Could you tell me which version of Node-RED you are running?
Could you try to capture the full error and its stack trace from the development console?
---
### Author:  [@azetat](https://discourse.nodered.org/u/azetat)
#### Post date: [16 September 2026 09:10 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/6 "2026-09-16T09:10:38Z")
I do have the same issue.
After upgrading to Safari 27, the reload issue happened.
I also can confirm the Workaround: manually reload the page and the tabs are working.
Issue and workaround: [https://app.screencast.com/4COMug2cPcvKl](https://app.screencast.com/4COMug2cPcvKl)
---
### Author:  [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [16 September 2026 09:59 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/7 "2026-09-16T09:59:33Z")
in @azetat instance, I can see you are not using https or localhost. that will cause an issue accessing clipboard. There is a long standing issue on the monaco repo ([[Bug] Safari: non-https site reports `undefined is not an object (evaluating 'navigator.clipboard.write')` · Issue #4496 · microsoft/monaco-editor · GitHub](https://github.com/microsoft/monaco-editor/issues/4496)) and it has (last week) had a fix applied - but this is not yet live/released by the monaco team. When it is, i will update node-red monaco editor to use latest. Until that time, this is an upstream issue we cannot fix easily. Using Chrome works ok (in my experience). Note: I have seen similar behaviour in FireFox (though it may not be the same issue as I have never managed to catch the dev console)
---
### Author:  [@SteveD](https://discourse.nodered.org/u/SteveD)
#### Post date: [16 September 2026 11:32 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/8 "2026-09-16T11:32:19Z")
Thanks Steve.
I did discuss it with Claude (really just to find out what the strange zero-comma syntax was), but in any case it suggested that Apple had probably tightened security in Safari 27 and was now enforcing the clipboard accessibility for http connections differently. It suggested I get a letsEncrypt certificate for my NodeRED server.
I'll live with it until the Monaco fix comes through.
---
### Author:  [@azetat](https://discourse.nodered.org/u/azetat)
#### Post date: [17 September 2026 08:10 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/9 "2026-09-17T08:10:33Z")
Some additional findings from my side (Safari 27, Node-RED 5.0.7 as Home Assistant add-on, accessed via plain http in the LAN):
- I switched the code editor to ACE (editorTheme.codeEditor.lib: "ace" in settings.js) and restarted Node-RED.
- Result: the TypeError about navigator.clipboard.write no longer appears in the console – but the reload on the first tab switch still happens.
- The console only shows "Page navigated to [http://192.168.0.158:1880/#flow/](http://192.168.0.158:1880/#flow/)..." followed by a full page load. No "This webpage was reloaded because a problem occurred" banner.
- Same behaviour in a private window with all extensions disabled.
- With "Pause on all exceptions" enabled, the debugger stopped at a SyntaxError in vendor.js:2:9023 (inside the jQuery $ function), which is probably a caught exception and not related.
- Workaround still works: after one manual reload (Cmd+R), tabs can be switched without any reload.
So in my case the clipboard error seems to be a side effect rather than the cause of the reload. I have reverted to Monaco for now.
---
### Author:  [@azetat](https://discourse.nodered.org/u/azetat)
#### Post date: [17 September 2026 09:14 UTC](https://discourse.nodered.org/t/odd-behaviour-or-error-with-safari-27-on-mac/101788/10 "2026-09-17T09:14:17Z")
Test: I opened an SSH tunnel so Node-RED was reachable via [http://localhost:1880](http://localhost:1880) (localhost counts as a secure context in Safari). Result: no reload on tab switch at all. So the missing secure context is the trigger, even with the ACE editor.