You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing past CDN releases, it seems that this bug was introduced in 2.9.0-beta.1
Expected behavior
When a object is set to display in the categories format, and properties are added or removed, then only the currently navigated-to tab of properties will remain displayed.
Actual behavior
When an object is set in the categories format, then adding or removing properties causes all of the tabs' divs to display on the page. While they're normally all in the DOM, typically all but the currently navigated-to tab are marked with style="display: none;". Toggling properties via the property button causes all the tabs to display.
I think that this is a bug, not an enhancement request. The UI should not display multiple tabs at once if a new one is checked. I've fixed this in PR #1497
General information
Expected behavior
When a object is set to display in the categories format, and properties are added or removed, then only the currently navigated-to tab of properties will remain displayed.
Actual behavior
When an object is set in the categories format, then adding or removing properties causes all of the tabs' divs to display on the page. While they're normally all in the DOM, typically all but the currently navigated-to tab are marked with
style="display: none;"
. Toggling properties via the property button causes all the tabs to display.Steps to reproduce the behavior
Direct link to example: https://jsfiddle.net/jLpytsv0/
The text was updated successfully, but these errors were encountered: