Move saving screenshots to the default folder to an IPC call #6636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move saving screenshots to the default folder to an IPC call
Pull Request Type
Description
Currently the code for saving video screenshots to the default save location uses the Node.js
path
andfs/promises
modules in the renderer processes. While it does work, it is one of the reasons that we currently have to havenodeIntegration
turned on in our renderer processes. This pull request moves it to an IPC call, which allows us to add a few security measures like making sure that IPC call can only write inside the users configured folder and gets us one step closer to turning offnodeIntegration
.Just a reminder why having
nodeIntegration
turned on in the renderer is a bad idea. Having that turned on means that you can use any Node.js and Electron APIs in there, which is not ideal considering that we load data, including HTML, from third party sources and have the devtools enabled.P.S. I would recommend turning on the "Hide Whitespace" setting when reviewing this pull request.
Testing
Electron
folder instead of theFreeTube
one.screenshotFolderPath
line from thesettings.db file
.yarn dev
.Desktop