Unvisible output (also an internal vs. external problem somehow)- a virtual keyboard problem

Question

The "virtual-keyboard-problem" here is as simple as it sounds: internal code works - external code doesn't.

Very likely it has something to do with Sololearn's I/O handling, but:

Can someone explain it further?

https://sololearn.com/compiler-playground/WyG7clMnMdY0/?ref=app

->

https://sololearn.com/compiler-playground/W93Kbu9u464V/?ref=app

Edit:
Now this should be a better example for that problem:

https://sololearn.com/compiler-playground/W37farYOnZ9S/?ref=app

Answer 1

Lisa Yes it does; but all in all (is this a possible english statement? - doesn't really matter - you know what I mean) it's simply about:

It just won't compile...

Answer 2

Now I simply used:
document.addEventListener('DOMContentLoaded', function () {

});

and some different methods to make it work, but the basic problem isn't solved yet - because I tried it in former sessions and got no result...

Answer 3

On my phone, it seems to run: I can click some buttons and get output.

What should "compile"? Or what happens on your device? Just nothing?

Answer 4

Lisa
Do you mean the Virtual Keyboard or the ASCII-Code?

Because the Virtual Keyboard is more like a tryout for the ASCII-Code-Keyboard.

Do you see the ASCII-/Unicode values in the output?

Answer 5

Lisa Oh, thank you! 🙏 I directly overlooked that.
I'll keep it growing.
See you next time ✌️✨️

Answer 6

you try document's load? does it change when using window's load ?

Answer 7

I think, I didn't understand, what your code was supposed to do.

It seems your event listeners are not added but I haven't yet figured out why.

https://sololearn.com/compiler-playground/WcI7jAYQYn4C/?ref=app

Answer 8

It was supposed to print the corresponding ASCII-/Unicode Values on the screen - this may be because if Sololearns input/output-handling.

At the moment I can't test it with another OS but other input/output handlings work fine like in these codes:

https://sololearn.com/compiler-playground/W93Kbu9u464V/?ref=app

https://sololearn.com/compiler-playground/WwNgmpdI1NGN/?ref=app

I tried to use the same logic, but it doesn't work correctly.

Answer 9

The keyboard's absolute position is not set. That's why it is buried under the container and the flame and clicks never reach the button elements despite the eventlisteners being added as intended.

Answer 10

Sorry to ask again, but:
If I make the #output (or other related elements) "absolute" the whole UI is scr*wed.

The UX profits from it, but also won't run properly...

Answer 11

For me, the UI is ... anyway because I have a different screen size.

You could query the user's screen size and use it for setting the keyboard's position.

Answer 12

How about fixating the keyboard at the bottom?
https://sololearn.com/compiler-playground/WTgoF8MmxXKi/?ref=app