Revision e9f36aa0be6522db24e0d27b293a78ba68214d02 authored by Ehsan Karamad on 25 April 2018, 15:35:03 UTC, committed by Blink WPT Bot on 25 April 2018, 15:45:19 UTC
If 'vertical-scroll' is disabled for an <iframe>, then it should not be
able to affect the vertical scroll position. One way to block is to use
scripted scrolling by calling "element.scrollIntoView()".

To block such frames (whose feature's disabled), programmatic recursive
scroll calls are not forwarded to parent frames. This means if a given
<iframe> is blocked, then all the calls to scrollIntoView() are limited
to the scope of frame (i.e., elements becoming visible in the frame).
This applies to all the nested <iframe>'s of a disabled frame as well
since they would have the feature disabled as part of propagating the
container policy.

Link to explainer/design document for "vertical-scroll":
https://docs.google.com/document/d/1qiWelnMlsOHuT_CQ0Zm_qEAf54HS5DhoIvEDHBlfqps/edit?usp=sharing

Bug: 611982
Change-Id: I0e06b399ad890e263128b997cfbb04eb3bdd1494
Reviewed-on: https://chromium-review.googlesource.com/1014191
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553561}
1 parent 6c62c5b
History
File Mode Size
certs
ci
gitignore
html5lib
lint
manifest
pywebsocket
runner
scripts
serve
six
sslutils
third_party
webdriver
wpt
wptrunner
wptserve
.coveragerc -rw-r--r-- 333 bytes
.gitattributes -rw-r--r-- 26 bytes
.gitignore -rw-r--r-- 114 bytes
.gitmodules -rw-r--r-- 371 bytes
OWNERS -rw-r--r-- 20 bytes
__init__.py -rw-r--r-- 40 bytes
appveyor.yml -rw-r--r-- 770 bytes
conftest.py -rw-r--r-- 912 bytes
localpaths.py -rw-r--r-- 802 bytes
pytest.ini -rw-r--r-- 110 bytes
tox.ini -rw-r--r-- 1.9 KB

back to top