Summary

It may be preferable to disable the download and fullscreen button an a video element (even though, in general, it's not hard for someone to script their way around this). In this case we can use controlsList when working with normal HTML.

The other thing we may want to do is disable Picture-In-Picture, which can be achieved using the disablePictureInPicture attribute.

Both things would be supported if the Video component forwarded these web properties, which is done for some other components (despite these being "web-only" properties!).

The reason this doesn't work for video is because the Video element throws away unknown properties here:
https://github.com/expo/expo/blob/main/packages/expo-av/src/ExponentVideo.web.tsx#L144

Despite the following invocations allowing it:
https://github.com/expo/expo/blob/main/packages/expo-av/src/Video.tsx#L355
https://github.com/expo/expo/blob/main/packages/expo-av/src/ExponentVideo.web.tsx#L40

Workaround

The workaround is to use a nativeId and set these properties using JavaScript, each render, because each render it will reset to the old way.

Solution

I think the preferred solution would be to at least allow forwarding these web only properties, just like how many other components have other types of Android or iOS only properties.

What platform(s) does this occur on?

Web

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: Windows 10 10.0.22621
    Binaries:
      Node: 16.19.0 - ~\scoop\apps\nvm\current\nodejs\nodejs\node.EXE
      Yarn: 3.4.1 - ~\scoop\apps\nvm\current\nodejs\nodejs\yarn.CMD
      npm: 8.19.3 - ~\scoop\apps\nvm\current\nodejs\nodejs\npm.CMD
    npmPackages:
      @expo/webpack-config: ^0.17.4 => 0.17.4
      expo: ^47.0.13 => 47.0.13
      react: 18.1.0 => 18.1.0
      react-dom: 18.1.0 => 18.1.0
      react-native: 0.70.5 => 0.70.5
      react-native-web: ~0.18.12 => 0.18.12
    Expo Workflow: managed

Minimal reproducible example

https://snack.expo.dev/@derk-jan/web-video-controlslist