New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 844454 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

"opacity" property for animate.attributeName causes iFrame in video to jitter (shake)

Reported by bob.mer...@voicezam.com, May 18 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36

Steps to reproduce the problem:
1. Navigate to example here: https://jsfiddle.net/mediazam/rzwp278a/
* Note: 2 example iFrames are shown with differing video playback platforms.
2. Run
3. Play both videos
* iFrame shake occurs in both iFrames
4. Remove 'attributeName="opacity"' in code at line 11
5. Run
6. Play both videos
* NO iFrame shake occurs

What is the expected behavior?
Video in iFrame should remain stable and has in the past

What went wrong?
Video "shake' in iFrame now occurs during playback and mouse movement within the frame.

Did this work before? Yes No sure exactly. I'm guessing about 1-2 months ago.

Chrome version: 66.0.3359.181  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 29.0 r0

Shake occurs at the same rate as animate.dur=".5s"

Not sure if this is related to videos but it occurs on with Vimeo and YouTube

Live production example: https://www.voicezam.com/csplayer/csplayer.aspx?o=5ad90b1c-ed6e-4502-9bdf-12a76d0f9f41&c=5ad90b1c-ed6e-4502-9bdf-12a76d0f9f41&cc=0&cf=0&ap=0&portal=Demos%20page%20for%20Michael%20Grant&IsPartner=False
 

Comment 1 by woxxom@gmail.com, May 18 2018

This is fixed in Chrome 68.0.3403.0 by fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd
"Make --site-per-process the default on ToT via fieldtrial_testing_config"

The fix wasn't merged into 67.
You can force it manually by enabling chrome://flags/#enable-site-per-process
Beware site isolation causes some bugs in 66 (definitely) and 67 (probably).

Comment 2 by woxxom@gmail.com, May 18 2018

This was broken in Chrome 66.0.3345.0 by 96f85b68747a679ea1ac4cd05d6743ae5f7142b7
"Enable root layer scrolling."

The underlying bug was introduced earlier.
Bisected with --enable-blink-features=RootLayerScrolling
https://chromium.googlesource.com/chromium/src/+log/187cdc97..13e9d344?pretty=fuller
Suspecting 13e9d344a202ab2d800c64f9c3f0beef605651d9 = https://crrev.com/2728273002 by skobes@chromium.org
"[RLS] Don't create PaintLayerCompositor layers."
Landed in Chrome 59.0.3037.0 (disabled behind RLS feature)
Cc: pdr@chromium.org skobes@chromium.org trchen@chromium.org
Components: -Blink Blink>Compositing Blink>Scroll
Status: Available (was: Unconfirmed)
Almost certainly this is a layer positioning issue when a compositing layer is created for the opacity animation.

I didn't see the issue on M-67 Linux.

Comment 4 by skobes@chromium.org, May 18 2018

Possible dupe of  issue 825775 .
Verified fixed - Version 67.0.3396.87 (Official Build) (64-bit)

Sign in to add a comment