Transition from Muon to Electron

[kura52]

Muon is scheduled to cease development, as in Issue below.
Question: what's the future of Muon with the upcoming move to Chromium frontend

Therefore, it is necessary to migrate to Electron, but there is a possibility that functions derived from Muon's own function can not be used.

We aim to make the transition with compatibility as much as possible.

[Koetype]

As per the referenced issue, how are you handling Electron's security concerns? I'm interested to know as Muon was created in part to address that.

I hope the development migration has been going well, and thank you for your work on Sushi Browser, Kura.

[kura52]

Thank you for your question.
We are proceeding with the migration work with the following policy.
As a security measure, I enabled the sandbox option and disabled node integration. (Improve performance at the same time)
Also, we use webFrame.executeJavaScriptInIsolatedWorld to run Content Scripts with Context Isolation like chrome.
In addition, we have modified some of the core logic of Electron, making Chrome Extensions as usable as the current Sushi Browser available.
Since webview is not recommended, I am using browserview with modifications.

[kura52]

We released the alpha version of the Electron edition!
https://github.com/kura52/sushi-browser/releases/tag/0.23.a1

[kura52]

Close by releasing the official version of the chrome edition.