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

Issue 803614 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

element.blur() steals focus from iframe

Project Member Reported by blois@google.com, Jan 18 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
Sample:
https://peteblois.github.io/tmp/isolated_iframe_focus/

This may rely on site-isolation being enabled.

1. Focus an element outside of an isolated iframe
2. Shift the focus to an element inside the isolated iframe
3. Call element.blur() on the element outside of the iframe

What is the expected behavior?
The focused element within the iframe continues to be focused after the call to element.blur() outside of the iframe.

What went wrong?
The focused element lost focus.

Did this work before? Yes 63.0.3239.86

Does this work in other browsers? Yes

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 
Flash Version: 

This appears to have been fixed in Chrome 64 beta.

 

Comment 1 by creis@chromium.org, Jan 18 2018

Cc: creis@chromium.org alex...@chromium.org wjmaclean@chromium.org
Components: Internals>Sandbox>SiteIsolation
Labels: -Pri-3 M-63 OS-Chrome OS-Linux OS-Mac OS-Windows Pri-2
Owner: creis@chromium.org
Status: Assigned (was: Unconfirmed)
I can repro the bug on Windows Chrome 63.0.3239.132 and ChromeOS 63.0.3239.140 when running with --isolate-origins=https://googleusercontent.com or --site-per-process.

I cannot repro it on Windows Chrome 64.0.3282.85 or ChromeOS 65.0.3319.0.  This suggests it was fixed somewhere in Chrome 64.  I'll try to bisect it to confirm.
Cc: aval...@chromium.org
Might be fixed by r520215, which was initially in 64.0.3281.0?

Comment 3 by creis@chromium.org, Jan 22 2018

Labels: M-64
Owner: aval...@chromium.org
Status: Fixed (was: Assigned)
Yep, that's correct.  Just confirmed it with a bisect looking for the fix.  (Ignore the good/bad text in the bisect results below.)

Thanks avallee@!

---
You are probably looking for a change made after 520214 (known good), but no later than 520215 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/fbe8c9a11f561c42fcc2d5d4218b887216719758..7da6ada25be4cdb742dddbfd6762bd90d872f4cf

Sign in to add a comment