syscall/js: panic: not a number #26170
Labels
arch-wasm
WebAssembly issues
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
release-blocker
Milestone
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version devel +6780042 Sun Jul 1 08:07:47 2018 +0000 linux/amd64
What operating system and processor architecture are you using (
go env
)?What did you do?
I tried to rebuild my app after all the new changes in master. The app responds to events from
input[type=range]
and acts accordingly.When I try to take the
.Float()
of thejs.Value
, I get the above-mentioned panic. The value is a perfectly fine float. And it even works fine if I take.String()
and do astrconv.ParseFloat
of it.The problem goes away if I go back to the commit before 8997ec1 (syscall/js: use stable references to JavaScript values)
I believe this is an inadvertent mistake, please let me know if I am wrong.
What did you expect to see?
The app to run successfully after moving to new API.
What did you see instead?
Very minimal repro, without releasing callbacks -
The text was updated successfully, but these errors were encountered: