From eba2d94359308ccdf958078351e95c58e88ba1bd Mon Sep 17 00:00:00 2001 From: Julian Molina Date: Sun, 24 Jan 2021 20:13:17 +0100 Subject: [PATCH] Investigating Issues - Check for Errors at the Browser --- ...ssues-check-for-errors-at-the-browser.json | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-012-investigating-issues-check-for-errors-at-the-browser.json diff --git a/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-012-investigating-issues-check-for-errors-at-the-browser.json b/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-012-investigating-issues-check-for-errors-at-the-browser.json new file mode 100644 index 000000000..e7b5e4763 --- /dev/null +++ b/Projects/Superalgos/Schemas/Docs-Topics/troubleshooting-012-investigating-issues-check-for-errors-at-the-browser.json @@ -0,0 +1,20 @@ +{ + "topic": "Troubleshooting", + "pageNumber": "12", + "type": "Investigating Issues - Check for Errors at the Browser", + "definition": { + "text": "When errors occur in the frontend application, you should either get an on-screen error, or an error should be logged in the browser console.", + "updated": 1611515570461 + }, + "paragraphs": [ + { + "style": "Text", + "text": "Open Chrome’s DevTools with the F12 key (when the browser is in focus) and click the Console tab. Then go back to Superalgos and reproduce the issue. The console may display network errors and warnings of different sorts. Those are not important and you may safely ignore them.", + "updated": 1611515578715 + }, + { + "style": "Text", + "text": "Do pay attention to other kinds of errors, such as files that can not be loaded, or errors in specific system components." + } + ] +} \ No newline at end of file