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

Issue 601060 link

Starred by 1 user
Status: Duplicate
Merged: issue 600395
Owner:
█ aval...@chromium.org
Last visit > 30 days ago
Closed: May 2016
Cc:
wjmaclean@chromium.org
█ aval...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Focus is not working for OOPIF-<webview>

Project Member Reported by ekaramad@chromium.org, Apr 6 2016 
Version: 51.0.2701.0 (Developer Build) (64-bit)
OS: All

What steps will reproduce the problem?
(1) Download the attached app. Got to chrome:://extensions, enable "Developer Mode", and load the app as an unpacked extension.
(2) Start the app and create a <webview>. Navigate the <webview> to a web page.
(3) Focus the text input field on the embedder (app) and press tab until <webview> takes focus.

What is the expected output?
The webview should take focus.

What do you see instead?
The webview does not take focus.

This seems to be a regression issue.

Comment 1 by ekaramad@chromium.org, Apr 6 2016 

Forgot to attach the app...although this should be reproducible on any app with a <webview> navigated to a page with focusable elements.
webview.zip
1.5 KB Download

Comment 2 by aval...@chromium.org, Apr 7 2016

Cc: aval...@chromium.org
Looking at the inspector, the tag looks like: <webview tabindex="-1">... This is probably it can't be focused with the tab key.

Comment 3 by ekaramad@chromium.org, Apr 7 2016 

I believe the behavior is different for <webview>. First, this does not happen in BrowserPlugin-based <webview>. Second, even clicking mouse does not give <webview> focus. However, if calling "document.querySelector('webview').focus()" in the inspector window will make this work although the caret still does not show (but you can type in the input fields).

Comment 4 by ekaramad@chromium.org, Apr 7 2016 

This should be tested with --use-cross-process-frames-for-guests switch.

Comment 5 by ekaramad@chromium.org, Apr 7 2016 

I also think the tabindex="-1" is there to avoid the <webview> frame itself taking focus and the transition from embedder to the guest becomes seamless. wjmclean@ should have a better opinion on this.

Comment 6 by aval...@chromium.org, May 5 2016

Mergedinto: 600395
Owner: aval...@chromium.org
Status: Duplicate (was: Available)
Duping into  issue 600395  which is where I've been keeping up to date.
►

Sign in to add a comment