Explore mode in Discovery select issue

[tercer]

When in explore mode, triggered with the Discovery table open, the current problem highlighted in the table can be explored, but no other problem can be clicked/selected.

[aaron-lebo]

@tercer I can't recreate this, can you give some more details about how you triggered it?

[tercer]

@aaron-lebo If I press the following buttons everything is fine:
"Discovery" -> Select a problem -> "Explore" -> "Go"
and I get the right graphs.

If I go:
"Discovery" -> Select a problem -> "Explore" -> Click some other problem on the explore page

Then nothing is highlighted pink, and "Go" leads to a blank page.

[aaron-lebo]

Still not getting an error on 350-rp. Is this on develop? It ran fine on Chromium, too. Trying to narrow down what the difference could be.

…

On Wed, Aug 8, 2018 at 2:20 PM James Honaker ***@***.***> wrote: @aaron-lebo <https://github.com/aaron-lebo> If I press the following buttons everything is fine: "Discovery" -> Select a problem -> "Explore" -> "Go" and I get the right graphs. If I go: "Discovery" -> Select a problem -> "Explore" -> Click some other problem on the explore page Then nothing is highlighted pink, and "Go" leads to a blank page. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#390 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4RCMSOUsyu02sOyF_q_rsmlncMyMtsks5uOzn8gaJpZM4Vy5rG> .

[tercer]

Interesting. I was running Develop, with Safari and Chrome.

[tercer]

Oh - so I should test in 350-rp?

[tercer]

Yes. Can confirm it's not a problem in 350-rp.

[tercer]

So 350-rp is now merged into develop, but the problem seems have come back in develop.

[tercer]

Fixed with 13d7a3f. Thanks @aaron-lebo !