# \[Announce\] Dashboard Version 2.14.0

**URL:** https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469
**Category:** Dashboard
**Created:** [28 February 2019 12:30 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469 "2019-02-28T12:30:13Z")
**Posts on this page:** 5
**Page:** 1

<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: [28 February 2019 12:30 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469/1 "2019-02-28T12:30:13Z")

</div>

Usual mix of incremental features and small fixes.

**Enhancements**

- Allow Tabs to be hidden or disabled dynamically from a ui\_control msg.
- Finally remove deprecated second output from ui\_chart node.
- Allow ui\_form to be submitted with empty fields (if they are not required)

**Fixes**

- Don't try to close non-existent menu at start (logging issue only) - Issue #470
- Add startsWith polyfill for IE11
- Ensure active sidebar menu item is highlighted - Issue #472
- Sanitise display of html input - Issue #473
- Respect msg.socketid to return msg back to selected session when using ui\_template
- Allow dropdown to have 0 pre-configured values, by removing validation.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [28 February 2019 13:49 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469/2 "2019-02-28T13:49:52Z")

</div>

On a Point of Order, isn't removing a deprecated feature classed as a breaking change?

---

<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: [28 February 2019 14:01 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469/3 "2019-02-28T14:01:35Z")

</div>

Good Q... My thoughts are only if it breaks something... if you had something connected to that port - it will leave it there and keep working... so existing users won't break. But new users won't have the option.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [28 February 2019 14:09 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469/4 "2019-02-28T14:09:00Z")

</div>

You mean if there is a flow using it the second output will still work, but if you place a new node then you won't be able to access a second output? Not a breaking change in that case 🙂

---

<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: [28 February 2019 14:41 UTC](https://discourse.nodered.org/t/announce-dashboard-version-2-14-0/8469/5 "2019-02-28T14:41:06Z")

</div>

yes exactly.
