The browser shown in the screen cast is Chrome (66.0.3359.181) but the same issue occurs on Chromium (same version)

For completeness, I've repeated the test on GNOME on X11 session (instead of Wayland) and the issue does not show up; also rendering is as smooth as expected.

I think this discussion is also relevant
https://www.reddit.com/r/archlinux/comments/8lbf4o/arch_gnome_wayland_screen_tearing_artifact_issue/

and also this one:
https://www.reddit.com/r/archlinux/comments/8kmekd/dell_xps_13_9350_screen_tearing_on_bottom_edge_of/

Unable to reproduce the issue reported chrome version on 66.0.3359.181, latest stable 67.0.3396.62 and chromium  using Ubuntu 14.04 LTS. Attaching Screencast for reference.

Steps 
--------
1. Lauched Chrome and chromium.
2. Opened application as mentioned in the comment #0 and aslo navigated some site which is having scrolling.
3. Window maximized by hitting F11 and scrolled down.
We are able to see the pages loading without gliches.

We don't have Wayland on Arch Linux to test this hence cc'ing thomasanderson@ for help in further triaging.

Thanks! 

Deleted: 845795.ogv 30.7 MB

845795.ogv 30.7 MB Download

I believe this is resolved when you pass in the following flag:
--disable-gpu-driver-bug-workarounds

Reference:
https://bbs.archlinux.org/viewtopic.php?id=237383

Please give this a shot and see if it resolves your issue temporarily.  

yes it works here too.
I only got a rendering glitch after coming back to fullscreen the first time (part of the title bar was rendered in the window client area) but it only occurred the first time, then I wasn't able to reproduce.
I'll use this temporary workaround for now, many thanks!

Just for information: look at the attached video. The title bar is messed up when I come back from fullscreen with '--disable-gpu-driver-bug-workarounds'.
However with that workaround rendering is now as smooth as expected also in fullscreen mode

Deleted: chrome.mp4 956 KB

	chrome.mp4 956 KB View Download

The link in c#5 says that this happens with other apps too, so it is not chromium-specific.  Also, you pointed out that this regressed in Wayland 1.15, not because of a Chromium update.  I'd try reporting this with Gnome Wayland and seeing if you have better luck, but I'm closing this issue out because there's probably nothing we can do about this on Chromium's side.

Hello Thomas,

Both of those reddit links are my specific threads.  I think there are actually 2 issues here:

Issue #1 - Chromium / Chrome Issue In Full-Screen Mode:
This is the issue with the screen tearing that happens when watching videos in full-screen mode.  As I said previously, passing in the "--disable-gpu-driver-bug-workarounds" corrects the issue.  I am unsure if this is a specific Chromium/Chrome issue, but I do not have this issue with other browsers (FireFox, Opera, etc.) in Linux.  It appears there may be other performance related issues as well, all documented here:
https://bbs.archlinux.org/viewtopic.php?id=237383

 Issue #2  - Linux Applications Not Rendering Correctly:
This issue appears to have specific artifacts be displayed with certain applications inside Linux.  Possibly, something to do specifically with the Gnome Desktop Environment under Wayland.  It appears to be related to a package update (mesa) or a possible Intel video driver update.

Regardless, I believe these are 2 separate issues.  If you are able to reproduce this issue under Arch-Linux (under Gnome and Wayland), and able to see the issue corrected using the flag mentioned in Issue #1, that would most likely be a good starting point to start the troubleshooting process.

Please let me know if I can assist you with any additional information or screenshots.  Thank you!

+evangelos@ for arch
+tonikitoo@ for wayland
+piman for gpu

If I can get confirmation that the regression is in Chromium, I'd be happy to reopen.  Though "Not actually a regression in Chromium but an issue introduced with Wayland 1.15" has me convinced otherwise :)

The contents of about:gpu might be useful, especially if --disable-gpu-driver-bug-workarounds changes things (pleas attach the page when the flag isn't set).

But agreed with thomasanderson@, it sounds like a Wayland/XWayland issue.

Also see https://bugs.chromium.org/p/chromium/issues/detail?id=849682#c9