human review required due to ‘deny-connection’ constraint for ‘plug-attributes’ from base declaration. If using a chromium webview, you can disable the internal sandbox (eg, use --no-sandbox) and remove the ‘allow-sandbox’ attribute instead.
What does browser-support do? and which snaps should use the interface?
Would atom, which essentially runs on headless chromium for all practical purposes, need sandboxing support as a browser would?
I see that for brave, the snapcraft file comments out this plug, and uses
--no-sandbox as a command line argument/switch at run time
- Why is sandboxing not enabled for brave?
Lastly, that message itself on the store, for a snap that wishes to plug into sandboxing, doesn’t mean much.
As in isn’t it contradicting?
As a layman , from the docs on snapcraft,
- you can use sandboxing and browser support in general.
After you use it in snapcraft,
At the store upload,
- No! this cant be done. Use
--no-sandbox for turning sandboxing off.
But I want to try and see what sandboxing does