nwjs
Feature Request to create API like electron's win.setContentProtection()
NWJS Version : 0.46.2 Operating System : Windows feature request: there should be some api like electron's win.setContentProtection() in NWJS. Electron has an api called win.setContentProtection, but nwjs has no similar feature.
Link of the feature: https://www.electronjs.org/docs/all#winsetcontentprotectionenable-macos-windows
@rogerwang this can be closed content protection is not a thing anymore got architectural solved inside chromium got droped also from electron.
https://www.electronjs.org/docs/latest/api/browser-window#winsetcontentprotectionenable-macos-windows @frank-dspeed looks like its still present in Electron
funny thing it was a Mac Windows future thats why i not saw it in the chromium code under linux related ok that clears the dust thanks this is simply editing the registry and mac settings i know what to do thanks
but anyway we can close this this is out of scope for NWJS as Core Project as this is Windows Mac Specific Electron software we need to make that compatible with NWJS i am currently working on future parity between NWJS Electron and Chrome it Self.
So i move the whole usefull API' parts into chromium directly and also change the complet Chromium Architecture so we can more easy do modular builds.
i moved the new link from your comment to the electron parity issue. The Electron Parity Issue is the only one that matters. The new split will be relativ simple and gives us many features out of the box.
we split /content => IPC =>
You can then even connect the same content frame with more then 1 window or even stream that remote
https://chromium.googlesource.com/chromium/src/+/main/mojo/README.md#FAQ
moving on: Project Fugu
- https://github.com/stealify/web-platform/components/ContentProtection/modules
- https://github.com/stealify/web-platform/components/ContentProtection/components/macos
- https://github.com/stealify/web-platform/components/ContentProtection/components/windows
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/modules
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/GTK
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/Qt
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/Clutter
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/SDL2
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/GLFW
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/GLEW
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/EFL
- https://github.com/stealify/web-platform/components/ContentProtection/components/wayland/components/winit
I was trying to implement this with ffi on windows using SetWindowDisplayAffinity and getting no where. I think it is because node is not considered the same process as the chromium window.
https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwindowdisplayaffinity
The window must belong to the current process.
I was trying to implement this with ffi on windows using SetWindowDisplayAffinity and getting no where. I think it is because node is not considered the same process as the chromium window.
https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwindowdisplayaffinity
The window must belong to the current process.
I think once https://github.com/nwjs/nw.js/issues/7468 is implemented, this should be easy to do.