commit | 76f41a5c24c36011c5251dd96694342381231a2c | [log] [tgz] |
---|---|---|
author | Daniel Libby <dlibby@microsoft.com> | Thu Jun 04 00:22:05 2020 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Jun 04 00:43:10 2020 |
tree | 4ff0c9a55ef8c564c5d9c78ac9ae0ee7beba94ee | |
parent | 7810613a0254e37a268cbf20058c4a249daa5ecc [diff] |
Repaint remote frames when new layer is set Remote frames in CAP can end up incorrectly sized 0,0 on initial render which makes the iframes content not show up. The initial RenderFrameProxy::SynchronizeVisualProperties can come in before the RemoteFrameView has updated its compositing rect, which leaves the created SurfaceLayer with a 0,0 size. The RemoteFrameView compositing rect is only updated after Paint in the document lifecycle (see LocalFrameView::UpdateLifecyclePhasesInternal) and RenderFrameProxy::SynchronizeVisualProperties is called during intersection observer steps (also after paint). Since the synchronized properties have changed, a new SurfaceLayer is created at the correct size. When setting this SurfaceLayer on RemoteFrame, the existing invalidation of SetNeedsCompositingUpdate is not sufficient in CAP to have a new frame generated with the updated layer. In pre-CAP, this is not an issue - the oopif content appears with the first frame produced due to the ContentsLayer size update via CompositedLayerMapping::UpdateContentsRect in the compositing phase of the document lifecycle. To fix this for CAP, we add a SetNeedsPaint on the frame owner element's paint layer, and schedule another frame to ensure this gets picked up, since these updates typically will come in outside of the document lifecycle. R=pdr@chromium.org Bug: 1078255 Change-Id: I7333a79b3cfbca303fe388bea6d7df176b0e1f41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227897 Reviewed-by: Stefan Zager <szager@chromium.org> Commit-Queue: Daniel Libby <dlibby@microsoft.com> Cr-Commit-Position: refs/heads/master@{#774868}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
In the vast majority of cases the only upstream branch that you should need to care about is master
. If you see other branches in the repository, you can generally safely ignore them.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!