Improve map/zone navigation #19740
Improve map/zone navigation #19740
Conversation
| .tabs=${this._searchParms.has("noTabs") | ||
| ? configSections.areas.filter((page) => page.component === "zone") | ||
| : configSections.areas} |
There was a problem hiding this comment.
I don't think we should do this... Is it that much of an distraction?
It is also weird that noTabs on the areas config page will give you the zone title 🙃
There was a problem hiding this comment.
No it's not that bad, could revert it if you prefer.
Just thought it made the interface a little cleaner when you're editing zones from the map, it just didn't seem like the tabs belonged there in that case. If user happens to click on Areas, then he can't use the back button to go back to the map anymore.
It is also weird that noTabs on the areas config page will give you the zone title
I don't understand how you got in this situation. If you're on the areas config page, isn't a different page being loaded that doesn't have this code, and this arg has no effect?
There was a problem hiding this comment.
In the interest of moving this forward, I dropped the changes to tabs, so now this just simply implements the back button logic.
… map-zone-navigation
Proposed change
When editing zones from map, don't show theAreastab, which typically shares the zones page. It's not relevant to editing zones, seems a general distraction, and clicking on it interferes with the historyBack navigation.Type of change
Example configuration
Additional information
Checklist
If user exposed functionality or configuration variables are added/changed: