[Bug]: first search layer turns on automatically
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 232
- Forks
- 77
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 17
Description
Checked for duplicates
Yes - I've already checked
Describe the bug
I entered a search variable in a layer, but set the visibility off. When I opened the Mission, the first search layer automatically turned on. It was a large layer and it slowed down loading the map.
What did you expect?
I expected the search to not load the layer automatically, but wait until the search was done, THEN load the layer and zoom/pan to the feature.
Reproducible steps
1. Make a layer with a search variable, but make layer visibility off.
2. Open the Mission containing the layer.
Environment
- Version of this software: 2.11
- Operating System: Windows 11
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
Reproduce the issue by creating a layer with a search variable, disabling its visibility, and opening the Mission on Windows 11. Trace the first search layer's visibility and loading behavior, then verify that it remains off until a search completes and the map zooms or pans to the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100