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

Issue 924262 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Inconsistent behaviour with visual properties in OOPIFs

Project Member Reported by danakj@chromium.org, Today (9 hours ago)

Issue description

Visual properties always route through RenderWidget, though some are meant for the WebView.

In the OOPIF case, the RenderWidget has no owner delegate, so it does not make use of these properties. This prevents them from behaving properly in the OOPIF's context.

An example:

When resizing the window, the popup is expected to be closed. If you resize the window (without clicking the mouse, which does close the popup separately):
- A popup in the main frame's WebView will be closed, but
- A popup in an OOPIF frame will not.

Because visual properties go to each RenderWidget with the intent of reaching each WebView, the branch based on owner delegate may be entirely problematic.

Either
A) We should route this through each RenderView instead of to each RenderWidget (yes)
B) We need a call path from each RenderWidget to the WebView, not just the main frame's

Note that in the B) case we send properties to multiple RenderWidgets in a single WebView and they all update the WebView redundantly.
 

Sign in to add a comment