---
title: "Discussion on \"DRM PiP Loophole: How Picture-in-Picture Bypasses DRM\" | Hashnode"
description: "Discussion on \"DRM PiP Loophole: How Picture-in-Picture Bypasses DRM\". In the last post on why JioHotstar goes black when you screen share, DRM keeps decrypted video off the capture surface most of the time. In practice, people sometimes notice a gap: after popping the s"
url: "https://hashnode.com/posts/drm-pip-loophole-how-picture-in-picture-bypasses-drm/69e573985f6f8ed5f81d2d6a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [DRM PiP Loophole: How Picture-in-Picture Bypasses DRM](https://helloashish.hashnode.dev/drm-pip-loophole-how-picture-in-picture-bypasses-drm?utm_source=hashnode&utm_medium=feed)

In the last post on why JioHotstar goes black when you screen share, DRM keeps decrypted video off the capture surface most of the time. In practice, people sometimes notice a gap: after popping the s

Apr 20 · 4 min read · helloashish.hashnode.dev  
Read the article

-   [#drm](https://hashnode.com/tag/drm)
-   [#widevine](https://hashnode.com/tag/widevine)
-   [#streaming](https://hashnode.com/tag/streaming)
-   [#webplatform](https://hashnode.com/tag/webplatform)
-   [#chrome](https://hashnode.com/tag/chrome)

## Written by

[Ashish Kumar](https://hashnode.com/@helloashish)

@helloashish · Delhi, India

  
[View profile](https://hashnode.com/@helloashish)

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
