OOPIFs require 2 clicks to play an embedded YouTube video |
|||
Issue descriptionREPRO STEPS: 1. Launch Chrome with or without --site-per-process flag 2. Navigate to https://www.khanacademy.org/computing/computer-science/internet-intro/internet-works-intro/v/the-internet-wires-cables-and-wifi 3. Click *once* on the video (on the big play icon/triangle inside the green circle) 4. Verify if the video has started playing EXPECTED BEHAVIOR: The video starts playing ACTUAL BEHAVIOR: - Without --site-per-process, the video starts playing as expected - With --site-per-process, the video doesn't start playing after the first click. A second click is required to start the video playback. NOTES: - I've reproed with a ToT Chromium build (at r529521) - I've reproed yesterday on a ChromeOS opted into site-per-process (still at M63 AFAIR, but take this with a grain of salt).
,
Mar 6 2018
I was wondering if this bug should be considered ship blocking for Site Isolation (i.e. if we should add the Proj-SiteIsolation-LaunchBlocking label). On one hand, this bug is not blocking any functionality - users can still play videos by clicking one more time. On the other hand, having to click a second time is a little bit disruptive (and probably affects various metrics like user engagement of click-throughs). FWIW, I've checked that the bug still repros with 66.0.3355.0.
,
Mar 19 2018
I cannot repro on Linux 67.0.3371.0 (Official Build) dev (64-bit) and on Windows 67.0.3372.0 (Official Build) canary (64-bit). Unless someone else can repro this, I will close it as WontFix in couple of days.
,
Mar 20 2018
No repro for me as well on 66.0.3359.26 (Dev, Linux). OTOH, I wasn't able to repro yesterday on a Chromebook (Stable, 65.something) - this probably means that something changed on the website, rather than in Chrome. At any rate, closing as WontFix sounds good to me. |
|||
►
Sign in to add a comment |
|||
Comment 1 by lukasza@chromium.org
, Feb 7 2018