Ayushman Chhabra

I'd be willing to help out. Have you considered moving the repo under NW Utils? Tbh I have a spare laptop but it's not ARM based - and I'm assuming...

hi @ddreharov been a bit busy lately, i'll try to look at this by this Sunday

A workaround could be to chmod the NW.js files after they're moved. For example, `chmod /path/to/nw/**/*`

I was able to [reproduce](https://bugs.chromium.org/p/chromium/issues/detail?id=1329707#c5) on Ubuntu 22.04. This is a Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1329707&q=remote%20debugging&can=2

I'm going to close this since this PR doesn't look like it's making any progress. I'm going to open a bunch of PRs to update the docs.

@rebeccasf @panther7 can we continue this thread in the [Gitter](https://gitter.im/nwjs/nw.js)/[Google](https://groups.google.com/g/nwjs-general)/ [Discord](https://discord.gg/tyx267vKRH) chatroom? I'm trying to build NW.js on my local machine and having a tough time.

@rebeccasf it seems I got a similar error to you, were you able to figure this out? ```shell # set env variables export GYP_DEFINES=target_arch=x64 building_nw=1 clang=1 nwjs_sdk=1 disable_nacl=0 buildtype=Official export...

I agree > IMHO, i felt the release is too frequent and a lot of changes in the components are not being tracked properly, hence the downstream users are having...

Just read up on the [Pointer Lock API](https://developer.mozilla.org/en-US/docs/Web/API/Pointer_Lock_API) and played around with the [demo](https://mdn.github.io/dom-examples/pointer-lock/) to get an understanding. To make sure I understand, do you want to use the `Esc`...

Closing this since there hasn't been any movement/progress made. Ping me here if you have any more Pointer Lock related queries.