-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[devtools] Clicking into devtools noops when console is disabled #9889
Comments
@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. |
This is due to @epixa, any reason we can't disable this functionality for Dev Tools? |
I'm all for this not existing in DevTools. |
We attempted to solve this in #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. |
When we pick this up again we should backport this a few versions. This bug goes back to at least 6.2. |
Pinging @elastic/es-ui |
Tested this on current master and it appears to be fixed. Not exactly sure on which version this was fixed. Possibly this PR #49349. Which would mean all versions that have planned releases should contain the fix. Closing this for now. |
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:
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"}
The text was updated successfully, but these errors were encountered: