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

Issue 864840 link

Starred by 1 user
Status: Fixed
Owner:
█ acondor@chromium.org
Last visit > 30 days ago
Closed: Jul 20
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-VR
Proj-XR
Proj-XR-VR



Sign in to add a comment

VR testWebInputFocus flaky

Project Member Reported by bsheedy@chromium.org, Jul 18 
VrBrowser/VrShellWebInputEditingTest#testWebInputFocus has been pretty flaky (~30% chance of failure) recently. Bisect points to https://chromium-review.googlesource.com/1134088 as the culprit.

It appears that the patch somehow affected the test's ability to reliably send clicks to the content quad, as the text box is not getting focus, and thus the keyboard is not becoming visible.

Repros on the bots on a Pixel XL with N and locally on a Pixel 2 with O, both using the following GN args

ffmpeg_branding = "Chrome"
is_component_build = false
is_debug = true
proprietary_codecs = true
strip_absolute_paths_from_debug_symbols = true
symbol_level = 1
target_cpu = "arm64"
target_os = "android"
use_goma = true

Comment 2 by bsheedy@chromium.org, Jul 19 

Hhmm... I managed to get the same flake locally with the fix in place, although the bot looks healthy.

What's more worrying is that I'm seeing a 2D keyboard pop up mid-test now. I'll file a separate issue for that.

Comment 3 by acondor@chromium.org, Jul 20

Status: Fixed (was: Assigned)

Comment 4 by bsheedy@chromium.org, Aug 29

Labels: -VR-Caught-By-Test XR-Caught-By-Test
►

Sign in to add a comment