[Drum Machine] Test 3 about testable-projects-fcc

[no-stack-dub-sack]

@christophherr that really is unexpected, I had been under the impression that innerText would target the text content of the inner most node. Very strange. Looking into alternatives

[no-stack-dub-sack]

And yeah, to your other point, I have to admit I never once even came close to thinking about that in designing these tests

Not sure what the best thing to do about it is though. I have to think on that one

[no-stack-dub-sack]

Ok, so both tests 3 and 4 were failing for me when I made this change to my project, and I figured out why. In mine at least, the problem has to do with react and how babel compiles a <p> element vs. a <span> - I THINK (but not totally sure). Ultimately, I believe a span is kept inline, while a <p> ends up on a new line, and innerText was picking up these newline characters, i.e. \n. So in the end, I just added a regex, which eliminates any white space, so that all we will get is the text content itself. This fixed it on my project, but again, this is React and not sure what you're using. I'm pushing the changes in a few, and feel free to use the DEV cdn to see if the changes fixed it on your end.

Thanks!

[no-stack-dub-sack]

@christophherr Ok, the changes should be live in a few minutes on the DEV cdn and a few hours on the PROD cdn - can you check and let me know if this fixes the issue on your end and if not re-open?

[christophherr]

@no-stack-dub-sack
Thank you!
The test is passing with p tags now. (using vanilla JS)

Regarding the keyboard layout, QWERTY is by far the most common.
I´m not sure if a change would be necessary or even more confusing.
(Looks like ert - dfg - cvb should be the same for QWERTY, QWERTZ, AZERTY and QZERTY.)