# 🎉 Node-RED 1.1.0-beta.3 released
**URL:** https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461
**Category:** News
**Created:** [17 June 2020 10:00 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461 "2020-06-17T10:00:12Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [17 June 2020 10:00 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/1 "2020-06-17T10:00:12Z")
Slightly sooner than planned, we've have just released the third **beta** release of Node-RED 1.1.0
This fixes all of the reported [rendering issues from yesterday's beta](https://discourse.nodered.org/t/node-red-1-1-0-beta-2-released/28417).
**Fixed in this release**
- Fix wiring nodes from input back to output (including on touch-screens)
- Fix sometimes unable to keyboard-move group to left/up
- Fix group position in outliner
- Handle unknown nodes with no icon
- Prevent node creep when switching tabs
**Not yet fixed**
- Node icons turning blue randomly (think this is due to the latest Chrome changing its default form/focus CSS)
## Installing the beta
If you want to try out the beta, you will need specify node-red@next when you use npm to update. Without the `@next` you'll still get 1.0.x.
So on a Pi you'd do:
```auto
sudo npm install -g --unsafe-perm node-red@next
```
## Reporting problems
If you hit any problems, please report them either as a reply on this topic, or in the #dev slack channel. Please do not post new topics to the forum regarding the beta as that could confuse users who are not using the beta.
## Outstanding work
### Sort options on the outliner
Planning to add options to select how the items in the outliner tree are sorted
### Add examples flows for the core nodes
We have three PRs still being reviewed that include around 60 example flows for the core nodes... hoping to get them all in.
### Documentation
Need to update the docs and user guide to cover the new features.
---
### Author:  [@ghayne](https://discourse.nodered.org/u/ghayne)
#### Post date: [17 June 2020 10:10 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/2 "2020-06-17T10:10:56Z")
Thanks Nick, time to round up them escaped nodes!
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [17 June 2020 10:29 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/3 "2020-06-17T10:29:16Z")
Excellent stuff, working well for me so far.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [17 June 2020 10:32 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/4 "2020-06-17T10:32:46Z")
@ristomatti i did fix the basic wiring issues you reported on Android. I also noticed how the workspace scrolled whilst dragging nodes/wires around - that's not much fun. Will see if we can improve that. But it should now be just as functional as 1.0 was.
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [17 June 2020 10:50 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/5 "2020-06-17T10:50:32Z")
Technical stuff all OK so far
Got a comment on grouping - I'd vote for having the label default to show instead of hide
This is due to me adding the name - pressing deploy and then realising I needed to show as well.
---
### Author:  [@ristomatti](https://discourse.nodered.org/u/ristomatti)
#### Post date: [17 June 2020 10:58 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/6 "2020-06-17T10:58:10Z")
Thanks, I already tested and everything is working as before! And thanks also for taking a note on the scrolling issue. I was just planning on creating a separate post about it / considering taking a look at the code. I would like to mention also deleting wires via touch interface but that's more of a feature request than a bug. I can create a post about that to keep track if it'd help?
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [17 June 2020 10:59 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/7 "2020-06-17T10:59:51Z")
> [@ristomatti](#):
>
> . I would like to mention also deleting wires via touch interface but that's more of a feature request than a bug
Already doable - long press on a wire to bring up the radial-menu, and select delete.
If you wanted to pool your feedback on the touch-screen experience into a new topic, that would be good.
---
### Author:  [@ristomatti](https://discourse.nodered.org/u/ristomatti)
#### Post date: [17 June 2020 11:04 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/8 "2020-06-17T11:04:31Z")
> [@knolleary](#):
>
> Already doable - long press on a wire to bring up the radial-menu, and select delete.
I haven't been able to summon the menu over a wire at any point, hence reporting. But I'll create a separate topic once I come up with the next big annoyance. I've already created one which hasn't received any comments: [Tablet - node long press menu "select" to select nodes in flow](https://discourse.nodered.org/t/tablet-node-long-press-menu-select-to-select-nodes-in-flow/27823)
---
### Author:  [@juzam](https://discourse.nodered.org/u/juzam)
#### Post date: [17 June 2020 11:52 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/9 "2020-06-17T11:52:58Z")
I have an instance of `node-red-node-suncalc` that reports invalid configuration (similar to the UI
nodes with beta.1, now fixed in beta.3) suncalc version is the latest `1.0.1`.
If I hover over the triangle it reports `soff` and `eoff` as invalid properties.
---
### Author:  [@JGKK](https://discourse.nodered.org/u/JGKK)
#### Post date: [17 June 2020 12:21 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/10 "2020-06-17T12:21:52Z")
Works for me on ios the long press to select a wire and open the context menu.
---
### Author:  [@ristomatti](https://discourse.nodered.org/u/ristomatti)
#### Post date: [17 June 2020 16:37 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/11 "2020-06-17T16:37:08Z")
Ok strange, then it might be an Android issue... Or the fact my tablet is running an old Android version like 5.0 or something (not upgradable anymore).
---
### Author:  [@ghayne](https://discourse.nodered.org/u/ghayne)
#### Post date: [17 June 2020 16:59 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/12 "2020-06-17T16:59:41Z")
> [@ristomatti](#):
>
> Or the fact my tablet is running an old Android version like 5.0 or something (not upgradable anymore).
LineageOS?
---
### Author:  [@ristomatti](https://discourse.nodered.org/u/ristomatti)
#### Post date: [17 June 2020 17:16 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/13 "2020-06-17T17:16:48Z")
Last time I checked I could've upgraded only to a single version newer using a custom ROM. I pretty much only use Opera, Kindle and YouTube so the benefits wouldn't be worth the trouble I think. Thanks for the tip anyway, I'll need to check if I change my mind.
But this is way off topic, my apologies.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [17 June 2020 17:16 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/14 "2020-06-17T17:16:49Z")
so yes - Android 5 is lower on the list than IE11,,,
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [17 June 2020 22:19 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/15 "2020-06-17T22:19:58Z")
NR on Win10/Chromium on Pi4 browser
Did CTRL-A to select all nodes - clicked and dragged on the On Device Activity node to move them down - some wires didn't come with the nodes
Did browser empty cache and hard reload - did the same again
---
### Author:  [@cinhcet](https://discourse.nodered.org/u/cinhcet)
#### Post date: [17 June 2020 22:38 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/16 "2020-06-17T22:38:54Z")
Firefox 76.0.1 on Ubuntu 16.04
labels are not centered. (console not showing something in particular)
With chrome everything is centered.
---
### Author:  [@cymplecy](https://discourse.nodered.org/u/cymplecy)
#### Post date: [17 June 2020 22:57 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/17 "2020-06-17T22:57:06Z")
Confirmed on Firefox on Win10
(see previous post for comparison with Chromium on Pi4)
---
### Author:  [@cinhcet](https://discourse.nodered.org/u/cinhcet)
#### Post date: [17 June 2020 23:04 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/18 "2020-06-17T23:04:16Z")
this commit [https://github.com/node-red/node-red/commit/61d9ccf26328ab77db374c0f7331b7850f2adeaa](https://github.com/node-red/node-red/commit/61d9ccf26328ab77db374c0f7331b7850f2adeaa) broke it (so was already in beta 2, for some reason I haven't noticed it back then)
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [18 June 2020 09:00 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/19 "2020-06-18T09:00:09Z")
I have just noticed an issue with disabled debug nodes. On a browser refresh disabled nodes show with the button on the right pushed in, but the centre still shows green. Moving the mouse over the button clears it. I see that it also affects others as it is visible in @cymplecy's image above, the FILTERED node is disabled but the button is filled in.
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [18 June 2020 09:20 UTC](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461/20 "2020-06-18T09:20:17Z")
- Label misaligned in FF - **fixed**
- Debug toggle button initial state wrong - **fixed**
[Next page](https://discourse.nodered.org/t/node-red-1-1-0-beta-3-released/28461.md?page=2)