Skip to content
This repository has been archived by the owner on Jan 4, 2019. It is now read-only.

[Question] Is this fork usable as a drop-in replacement for upstream Electron? #87

Closed
lostfictions opened this issue Nov 5, 2016 · 2 comments

Comments

@lostfictions
Copy link

Nativefier is a utility in the vein of Fluid or Mozilla's defunct Prism that uses Electron to create site-specific browsers. They're isolated from each other in terms of cookies, storage, etc. and lack the usual browser chrome.

I tried to briefly touch on some of the security challenges of using Electron in a browser-like capacity in nativefier/nativefier#288 -- challenges I'm sure the Brave team is familiar with. Would your fork of electron-prebuilt potentially be usable as a drop-in for Nativefier's use case?

@posix4e
Copy link
Contributor

posix4e commented Dec 2, 2016

I am not sure. Our fork is more targeted as a webbrowser than an app platform. No reason why it shouldn't work. Certainly we have some security advantages.

@bridiver
Copy link
Collaborator

bridiver commented Dec 5, 2016

our fork is mostly compatible at the moment, but will have some significant changes with the chromium54 update. In particular we will no longer support running node in any renderer process. Node will only run in the browser process. Things like ipc are supported in the renderer process through custom chrome.* apis. Our goal is to have a project that can be re-used by people looking for more "browser-like" features than electron provides, but right now our resources are focused 100% on Brave

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants