New issue
Advanced search Search tips

Issue 692641 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug

Blocking:
issue 583347



Sign in to add a comment

didAcquirePointerLock, didNotAcquirePointerLock and didLosePointerLock should be plumbed through WebFrameWidget instead of WebViewImpl

Project Member Reported by lfg@chromium.org, Feb 15 2017

Issue description

Issue came up in https://codereview.chromium.org/2696523003/ , we need to cleanup the interface once RenderWidget can be associated with a WebFrameWidget instead of the WebViewImpl.

 
Project Member

Comment 1 by sheriffbot@chromium.org, Feb 16 2018

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by lfg@chromium.org, Feb 27 2018

Labels: -Hotlist-Recharge-Cold

Comment 3 by lfg@chromium.org, Feb 27 2018

Status: Available (was: Untriaged)
Status: Assigned (was: Available)

Sign in to add a comment