+ 7

Can I remove the annoying console window on the sololearn web playground (output)?

There is this annoying console window on the output window of the sololearn web playground when using my phone. It covers content. Do you also have it? Is there a way to remove it?

17th Apr 2017, 2:09 PM
lulugo
lulugo - avatar
14 Answers
+ 7
you are not the first to be annoyned by this :/ i emailed sololearn a while ago and been told the next update should hide empty console logs (unsure about server generated logs and how those will be handled) https://www.sololearn.com/discuss/317824/?ref=app https://www.sololearn.com/discuss/304101/?ref=app https://www.sololearn.com/discuss/291731/?ref=app https://www.sololearn.com/discuss/310791/?ref=app
17th Apr 2017, 4:51 PM
Burey
Burey - avatar
+ 11
I too have that problem. Just put a <br><br><br> at the end or give a padding bottom to 'body'.
17th Apr 2017, 2:39 PM
Krishna Teja Yeluripati
Krishna Teja Yeluripati - avatar
+ 11
@Burey Not for me, for the codes I've checked
20th Apr 2017, 10:01 PM
Jafca
Jafca - avatar
+ 10
@Burey Nope, it's gone
20th Apr 2017, 10:08 PM
Jafca
Jafca - avatar
+ 7
Hm. My import (2-3m old) was intended to minimize the console's drawbacks, correcting/detecting more than the app (you can even infer the engine's deadlocked). But...it didn't go terribly far and I didn't really push it. Instead, you can leverage the new default (OFF) state yourself, permanently: Just include this in your code early -- in <head>: window.onerror=function(message, source_document, line, column, error_message) { /* Do stuff with the variables - Intercepts everything. - Just ignore line numbers (they may be skewed) if you know the code - Handle or discard errors however you want; you can probably write a fancier popup than I did. */ return true; // false: cancel event bubble }
30th Apr 2017, 9:40 PM
Kirk Schafer
Kirk Schafer - avatar
+ 7
@Andrew Grider - "fix rather than hide" -- yes, plus: In production, shown only to devs. Error messages reveal unnecessary/risky data; rarely does anyone (but the dev) need to know exactly what happened. These should stay ON the server; NEVER shipped out the client side...minimizing consumer interaction. A good example: php.ini..."production setting". Look at all the stuff they hide. Or for apps: Crashlytics; some crashes you never, even, notice. They just get fixed--the pros at work.
30th Apr 2017, 10:08 PM
Kirk Schafer
Kirk Schafer - avatar
+ 6
Thank you guys for the information 😊
17th Apr 2017, 10:00 PM
lulugo
lulugo - avatar
+ 6
any new information about the console logs? still appearing? [edit] just checked and it seemed much better accelerometer handlers no longer cause console logs!! also it seems that the keyboard will now open much less frequently in the code editor :)
20th Apr 2017, 9:56 PM
Burey
Burey - avatar
+ 6
@Jafca console still there for you?
20th Apr 2017, 10:07 PM
Burey
Burey - avatar
+ 6
\o/
20th Apr 2017, 10:18 PM
Burey
Burey - avatar
+ 5
on my device console visible only when I use console.log or have errors
17th Apr 2017, 2:12 PM
Yaroslav Pieskov
Yaroslav Pieskov - avatar
+ 5
do you have latest version of app?
17th Apr 2017, 2:13 PM
Yaroslav Pieskov
Yaroslav Pieskov - avatar
+ 5
@andrew it is easy to say find error . . . when it throws up error on line 16000 in external lib
17th Jul 2017, 6:12 PM
Abdur-Rahmaan Janhangeer
Abdur-Rahmaan Janhangeer - avatar