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

Issue 784887 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Update BrowserPlugin to work only with valid FrameSinkIds

Project Member Reported by jonr...@chromium.org, Nov 14 2017

Issue description

Similar to the work done on RenderFrameProxy, BrowserPlugin will need to begin sending its FrameSinkId information in the --mus path.

Additionally BrowserPlugin::WasResized should only send its data if there is a valid FrameSinkId set.

The caveat to this being that the following must occur, even with no valid FrameSinkId, as it is required to begin the embedding process:

if (delegate_ && size_changed)
    delegate_->DidResizeElement(frame_rect().size());


 
Status: Available (was: Assigned)
Status: WontFix (was: Available)
BrowserPlugin has since been updated to only process valid FrameSinkIds. The DidResizeElement aspect has been updated to always send.

This was a part of the BrowserPlugin::SynchronizeVisualProperties rework.

Sign in to add a comment