summaryrefslogtreecommitdiff
path: root/chromium/docs/media
diff options
context:
space:
mode:
authorAllan Sandfeld Jensen <allan.jensen@qt.io>2017-07-17 13:57:45 +0200
committerAllan Sandfeld Jensen <allan.jensen@qt.io>2017-07-19 13:44:40 +0000
commit6ec7b8da05d21a3878bd21c691b41e675d74bb1c (patch)
treeb87f250bc19413750b9bb9cdbf2da20ef5014820 /chromium/docs/media
parentec02ee4181c49b61fce1c8fb99292dbb8139cc90 (diff)
downloadqtwebengine-chromium-6ec7b8da05d21a3878bd21c691b41e675d74bb1c.tar.gz
BASELINE: Update Chromium to 60.0.3112.70
Change-Id: I9911c2280a014d4632f254857876a395d4baed2d Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Diffstat (limited to 'chromium/docs/media')
-rw-r--r--chromium/docs/media/autoplay.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/chromium/docs/media/autoplay.md b/chromium/docs/media/autoplay.md
index 0312713f9ca..3d0594a7b93 100644
--- a/chromium/docs/media/autoplay.md
+++ b/chromium/docs/media/autoplay.md
@@ -14,6 +14,13 @@ There are two ways of initiating autoplay:
* Autoplay by `play()` method: Explicitly calling the `play()` method without
user gesture.
+All the autoplay logic is handled by the AutoplayPolicy class. When the media
+element wants to perform some action (like unmute, autoplay by attribute or
+`play()` method), it will send a request to AutoplayPolicy, and if the request
+is approved, the element can autoplay, otherwise it should be paused. Also the
+media element should inform the AutoplayPolicy about relevant changes such as
+"the element has been moved to a new document".
+
## User gesture lock
Each media element has a user gesture lock. If the element is allowed to