-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
New prompt method gets confused when receiving special characters as input [ã] #8239
Comments
Can confirm on Windows on 1.5.1 (In PowerShell, if that has any impact):
Can also confirm that Linux works fine (tested on Ubuntu 20.04)
|
As I pointed out in #8492, |
Cannot reproduce on my computer.
System Info: @pedropaulosuzuki Can you confirm this is still an issue? |
I'd like to, but I dropped Windows on december 31 2020, so now I'm running on Pop!_OS 21.04, on which I cannot test the Windows behaviour with Deno input, unfortunately. Maybe someone with a Windows build could test it and see it the issue persists. |
I can confirm that the problem still occurs on windows.
C:\Users\azusa>deno
Deno 1.12.2
exit using ctrl+d or close()
> const a = prompt('Insert your character');
Insert your character ã
undefined
> console.log(`ã===ã => ${a === 'ã'}`);
ã===ã => false
undefined Maybe C:\Users\azusa>deno
Deno 1.12.2
exit using ctrl+d or close()
> prompt()
Prompt ã
"a"
> prompt()
Prompt こんにちは
"�����"
> |
You're trying to reproduce a Windows bug on a Mac. |
My bad. I am still learning issue triage. |
This is still an issue.
System Info: |
Just tried to reproduce it with the latest Deno release, but wasn't able to. It works as expected for me. Not sure which exact version resolved this, but updating to the latest Deno version will. |
While #8179 got partially fixed by #8199 (nice one btw, thanks for everyone involved!!), the prompt method still has some issues regarding input (related to stdin). For example, the code below doesn't perform as expected when non-ascii characters are used.
Opened a new issue because the other one got closed before this got adressed.
The text was updated successfully, but these errors were encountered: