New issue
Advanced search Search tips

Issue 823478 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 817419



Sign in to add a comment

interactive_ui_tests + MacViews BrowserCommandControllerInteractiveTest.KeyEventsShouldBeConsumedByWebPageInJsFullscreenExceptForF11

Project Member Reported by robliao@chromium.org, Mar 19 2018

Issue description

BrowserCommandControllerInteractiveTest.KeyEventsShouldBeConsumedByWebPageInJsFullscreenExceptForF11

[FullscreenToolbarController enterFullscreenMode] when _inFullscreenMode_ is YES.

Check failed: !inFullscreenMode_. 


 

Comment 1 by lgrey@chromium.org, Mar 21 2018

Owner: lgrey@chromium.org
Status: Assigned (was: Available)

Comment 2 by lgrey@chromium.org, Mar 21 2018

Status: Fixed (was: Assigned)
This is passing locally and on the bot, so I'm assuming it got fixed by something else
Some of these are flaky, so I'd keep an eye out on this one.
Cc: lgrey@chromium.org
Owner: ----
Status: Available (was: Fixed)
This is still DCHECK'ing for me as of Wed Mar 21 17:03:40 2018 +0000 68f5aab1de53ef35ec92eddbe59d3155e3db53b6
Labels: MacViews-Browser
Project Member

Comment 6 by bugdroid1@chromium.org, Mar 22 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/31d079820cf4b53ccb2319b93aa8a4401dc8112d

commit 31d079820cf4b53ccb2319b93aa8a4401dc8112d
Author: Robert Liao <robliao@chromium.org>
Date: Thu Mar 22 12:50:40 2018

Disable Test on MacViews - BrowserCommandControllerInteractiveTest.KeyEventsShouldBeConsumedByWebPageInJsFullscreenExceptForF11

BUG=823478

Change-Id: I926882274251a6ba554594f993f82cec9bd26cbe
Reviewed-on: https://chromium-review.googlesource.com/974452
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#545048}
[modify] https://crrev.com/31d079820cf4b53ccb2319b93aa8a4401dc8112d/chrome/browser/ui/browser_command_controller_interactive_browsertest.cc

Labels: MacViews-Tests
Labels: Target-68
Owner: ellyjo...@chromium.org
Status: Assigned (was: Available)

Comment 9 by gov...@chromium.org, Apr 13 2018

Labels: Proj-MacViews
Labels: -Pri-1 M-68 Pri-2
Pls mark the bug as fixed if CL is landed in trunk and nothing else is pending. Thank you.
Labels: -Target-68 Target-69
Labels: -M-68 Group-Tests
Labels: M-68
Labels: -M-68 M-69
Labels: -M-69 -Target-69 M-70 Target-70
Labels: -Target-70 -M-70 M-74 Target-74
I've been looking some at this test. It looks like it enters real, actual fullscreen - the JS "fullscreen" keypress leads back to Widget::SetFullscreen() which creates a real _NSWindowEnterFullScreenTransitionController. We then appear to exit it via the fake fullscreen path, which accidentally "works", but doesn't know that in this case a real transition is happening which is asynchronous.

Sign in to add a comment