Kibana: [devtools] Clicking into devtools noops when console is disabled

[epixa]

Kibana version: master

Elasticsearch version: master

Server OS version: darwin

Browser version: Chrome

Browser OS version: 55.0.2883.95

Original install method (e.g. download page, yum, from source, etc.): source

Description of the problem including expected versus actual behavior:

Steps to reproduce:

1. Run Kibana with x-pack so search profiler is in dev tools
2. Disable console via kibana.yml
3. Click on dev tools app

Expected: Loads the search profiler
Actual: Navigates back to discover regardless of what app you were on before

Errors in browser console (if relevant):

Object {CourierFetchRequestStatus: "aborted"}

[epixa]

@jbudz Can you take a look at this when you get a chance? It'll become much more common to encounter this when we ship tribe.

[tylersmalley]

This is due to linkToLastSubUrl. When you last visit Console before disabling it, Kibana will try to redirect to Console then eventually redirect to Discovery due to the route not existing.

@epixa, any reason we can't disable this functionality for Dev Tools?

[epixa]

I'm all for this not existing in DevTools.

[spalger]

We attempted to solve this in https://github.com/elastic/kibana/pull/9912 but time constraints have caused it to stall. I've closed the PR but the changes should be valid in the future when we're ready to pick it back up again.

[cjcenizal]

When we pick this up again we should backport this a few versions. This bug goes back to at least 6.2.

[elasticmachine]

Pinging @elastic/es-ui