Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for issue preventing default layers from being loaded #109

Merged
merged 3 commits into from
Oct 29, 2019

Conversation

wietze
Copy link
Contributor

@wietze wietze commented Oct 29, 2019

In v2.3 of the navigator, even when the Navigator is opened without the layerURL parameter set, it assumes it was (due to a logic error) and will never check if the enabled option under default_layers in config.json is set to true.

This commit fixes the issue by checking if the result of getNamedFragmentValue() is not null and its length greater than 0.

Tested in Chrome 77.

@isaisabel isaisabel self-assigned this Oct 29, 2019
@isaisabel isaisabel changed the base branch from master to develop October 29, 2019 12:50
@isaisabel
Copy link
Contributor

Hi @wietze,

Thank you for finding this bug and submitting the merge request. Everything looks good and I'll be merging it into develop, and then master, later today.

@isaisabel isaisabel merged commit 214c765 into mitre-attack:develop Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants