Nevkontakte

Hi @Michael-F-Ellis, thanks for a well-written report! This is probably a regression that happened when we upgraded to Go 1.17... Neither of the current maintainers use Macs, so this happens...

Hi @dithmer, sorry for getting back to you so late. I've tried to reproduce this issue with the latest version of GopherJS using https://github.com/dithmer/fzf/tree/gopherjs, but I'm getting build errors for...

I have read through this issue, but I'm not quite sure what action is proposed here. Is it just that someone writes a document explaining how to make a Go-idiomatic...

As a side note, GopherJS's support of `unsafe` is very ambiguous right now. In the compatibility table we state that it isn't supported, but we do support certain aspects of...

> Not all JS functions are methods. Reading the `jsbuiltin` code, all functions that it provides access to are actually accessed through `js.Global.Call`, so I'm not sure this statement is...

I think this requires a deeper investigation. For example, in the Chrome console `window.btoa` is defined: ``` > window.btoa ƒ btoa() { [native code] } > window.btoa("11101") 'MTExMDE=' ``` Maybe...

FWIW, GopherJS supports _some_ uses of unsafe, albeit inconsistently and not very safely. I think this is a good candidate for something like ‘gopherjs lint’, since linters seem to be...

It appears that this is no longer reproducible in the current GopherJS 1.16.x versions. Please feel free to reopen if I'm mistaken.

The issue can still be reproduced in GopherJS 1.17.0. After fiddling a little bit with the example in the playground, it seems that the fact that `Proto` embeds `*js.Object` field...

Copying @broady from https://github.com/gopherjs/gopherjs/issues/525: > It might sound strange, but I'd like some way to hook into `mainFinished` - kind of as a finalizer. > > The Node.js runtime can...