Request for human-review for vivaldi snap release candidate

[vivaldi]

Hi there,

we’re in the process of preparing the vivaldi browser snap, we have a release candidate that requires two connections that are by default not automatic (and we would kindly request them to be ), and the release system stops us from going further without a human review.

The two connections are:

• vivaldi:browser-sandbox (interface browser-support)

  • this is needed so sandboxing is reported as working inside the browser (chrome://sandbox) - we know snap provides sandboxing by itself, but the all-red sandboxing page when using --no-sandbox does not paint a trustable picture.

• vivaldi:chromium-ffmpeg-115016 chromium-ffmpeg:chromium-ffmpeg-115016

  • this connection is for additional codec support
  • in the future we’d like to upgrade this to newer revisions as this plug is name-versioned to align with the interface needs

Thank you,

Filip (Team Vivaldi)

[alexmurray]

+1 from me for both of these requests - vivaldi is a well-known browser so the use of browser-support with allow-sandbox is self-explanatory.

+1 also for the auto-connect of the chromium-ffmpeg-115016 content interface from the chromium-ffmpeg snap (given this snap is published by Canonical I wonder if we should just grant global auto-connect for these content interfaces?)

[ruario]

Just wanted to link from here to our request for additional architectures for “chromium-ffmpeg”

Using chromium-ffmpeg in third-party browser snaps

Hi, Vivaldi browser (who I work for) is looking at adding our product to the snap store. Like Opera, we would use “chromium-ffmpeg”. However unlike Opera we support three architectures amd64, arm64 and armhf. Since only amd64 binaries are provided for “chromium-ffmpeg”, this prevents install of a local, test Vivaldi snap on the arm based architectures. Would you be open to supporting arm64 and armhf for “chromium-ffmpeg” in the future? [Screenshot showing failure to install a Vivaldi snap o…

Though it is worth noting that @nteodosio has already kindly offered to help us with that:

@nteodosio

Yes, I will let you know when they are available.

[nteodosio]

@alexmurray

given this snap is published by Canonical I wonder if we should just grant global auto-connect for these content interfaces?)

Would be nice. [20 more characters]

[sahnaseredini]

+1 from me for auto-connect of browser-support interface and chromium-ffmpeg-115016 content interface to vivaldi snap.

[sahnaseredini]

+2 votes for, 0 against. Granting auto-connect of browser-support interface and chromium-ffmpeg-115016 content interface to vivaldi snap. This is now live.

Thanks.

[vivaldi]

Thank you! [20 Characters]