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

Issue 696389 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Adding iframe with chrome-extension:// src to top window triggers blur in child frame inputs

Reported by s...@fillr.com, Feb 27 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Create a web page that loads a child frame. The child frame contains 1 text input with 'autofocus' attribute set
2. In the parent web page should contain a script that defines the creation of an iframe element with the src attribute "chrome-extension://<your extension id>/<some web accessbile file>.html.  Use document.body.appendChild(new_frame_element) to add the created frame to the DOM
3. Load the parent web page in the browser.

This flow is fully demo'd in an example project:

1. Install the test extension from https://github.com/Fillr/chrome-ext-iframe-blur
2. run the server (./run/server from project root)
3. Observe the console after loading http://localhost:6969/top.html

What is the expected behavior?
The field in the subframe with autofocus should remain focussed. 
No blur event should be raised at all

What went wrong?
It feels like any url loaded in to the parent frame over chrome-extension scheme triggers a blur on child frames.  The demo project shows that urls loaded over http/https do not trigger the same blur behaviour.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.12.2
Flash Version: 

Please refer to the readme at https://github.com/Fillr/chrome-ext-iframe-blur for a full test case and steps to reproduce

 

Comment 1 by s...@fillr.com, Feb 27 2017

Video of my test case running can be seen here: https://monosnap.com/file/5l7psbKRwbhXa2Lq5Bajj0kQ2UxYsF
Labels: Needs-Triage-M56

Comment 3 by hdodda@chromium.org, Feb 27 2017

Cc: hdodda@chromium.org
Labels: -Needs-Triage-M56 TE-NeedsTriageHelp

Comment 4 by a...@chromium.org, Feb 27 2017

Components: Blink
Components: -Blink Blink>Input

Comment 6 by rbyers@chromium.org, Feb 27 2017

Components: Platform>Extensions
Labels: -Hotlist-Interop -TE-NeedsTriageHelp
This is specific to Chrome extensions, right?  Removing Hotlist-Interop, but keeping Blink>Input in case it is ultimately an issue in the generic focus handling code.
Labels: Needs-Triage-M56
Labels: -Needs-Triage-M56 TE-NeedsTriageHelp
Components: -Blink>Input Blink>Focus
Status: Available (was: Unconfirmed)
Components: Blink>HTML>Focus
Components: -Blink>Focus
Project Member

Comment 13 by sheriffbot@chromium.org, Oct 1

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
>  https://github.com/Fillr/chrome-ext-iframe-blur 

The URL isn't available.  We can't investigate this issue.

Sign in to add a comment