__Version information:__
go-ipfs version: 0.4.13
Browser: Firefox, Chrome (reproducible on all)
__Type: Bug__
__Severity: Low__
__Description:__
The X remove buttons on the Files page of the web ui are broken. If you click any of them, then the web UI goes to the front page (because the remove button is a link to "#" and the preventDefault() method is never called on the click event object), and this error appears in the console: "TypeError: t.preventDefault is not a function"
(I just copied it from https://github.com/ipfs/go-ipfs/issues/4269 and updated go-ipfs version to the one I use)
Hello @sickill! Thanks for reporting this! 馃槃 Fortunately, I can tell you that the latest version of WebUI (the one in this repository) doesn't contain this issue anymore. I think this should be closed. /cc @diasdavid
@whyrusleeping @lgierth @Kubuxu can we ship the new (fixed) webui with the next release of go-ipfs?
Sure! Pin it, then update core/corehttp/webui.go
@hacdias wanna do the honors? @lgierth can @hacdias have pinbot perms?
@diasdavid !befriend <nick> pin
@lgierth I tried but it didn't work:

@hacdias you are now a pinbot friend. Wanna update go-ipfs hash?
Also, wanna add this route to js-ipfs daemon?
@diasdavid
@hacdias you are now a pinbot friend. Wanna update go-ipfs hash?
Sure, but how? I know I have to pin an hash with a name. The name is go-ipfs, right? But what will be the hash in this case?
Also, wanna add this route to js-ipfs daemon?
Yes, but where? I'm not yet familiarized with everything 馃槢
@hacdias on the root of this repo do npm run build (see https://github.com/ipfs/webui#building) that will create a folder. Then do ipfs add -r dist and make sure your daemon is on.
With your daemon on go to pinbot and do !pin <the hash you got from ipfs add -r> webui
Once that is finished, you can now submit a PR to https://github.com/ipfs/go-ipfs/blob/master/core/corehttp/webui.go
Add a route here for /webui https://github.com/ipfs/js-ipfs/blob/master/src/http/gateway/routes/gateway.js
For go-ipfs
Done! https://github.com/ipfs/go-ipfs/pull/4449
For js-ipfs
I'll see that later hopefully 馃槃
@diasdavid, adding a route for /webui on gateway.js won't work since /webui tries to connect to the API in that same domain in that same port. It tries to connect to the API on 127.0.0.1:9090 instead of 127.0.0.1:5002.
The same happens with go-ipfs, but go-ipfs has /webui also available on :5001 so it works. Am I doing something wrong?
@hacdias you got it right. You should indeed create that endpoint on the API which is on the folder next to the gateway -> https://github.com/ipfs/js-ipfs/tree/master/src/http/api
@diasdavid done: https://github.com/ipfs/js-ipfs/pull/1124 馃巿
Thank you @hacdias ! :D Closing this issue then :)