openwisp / openwisp/openwisp-controller
[bug] Device Map UI breaks if "closed"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
Describe the bug
When following these steps (tested on demo openwisp website), the UI in a Device's Map tab doesn't work anymore
Steps To Reproduce
Steps to reproduce the behavior:
- Go to Device -> Map tab
- Click on the cross on the top right in that tab
- Click on the Add Map Location to add one map
- The UI changes, select New or Existing
- Notice the UI that should appear is not there : UI seems to have broken.
Expected behavior
The UI should change to allow the user to enter a new location (New) or to choose and existing location (Existing). Just like it does if the user does not click on the cross to close that UI.
Screenshots
System Informatioon:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the flow in the Device Map tab on the demo site: close the initial UI, choose Add Map Location, and select New or Existing. Trace the Device Map UI entry point and verify that the corresponding form or existing-location chooser appears after either selection, matching the behavior without closing the UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100