Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(271)

Issue 594015: Don't send frame update messages for non-browser RWHVs (Closed)

Created:
10 years, 10 months ago by stuartmorgan
Modified:
9 years, 7 months ago
CC:
chromium-reviews_googlegroups.com
Visibility:
Public.

Description

Don't send frame update messages for non-browser RWHVs BUG=35141 TEST=Trigger an autocomplete popup; watch the renderer not crash. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=38520

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+10 lines, -6 lines) Patch
M chrome/browser/renderer_host/render_widget_host_view_mac.mm View 2 chunks +10 lines, -6 lines 1 comment Download

Messages

Total messages: 3 (0 generated)
stuartmorgan
10 years, 10 months ago (2010-02-09 21:53:17 UTC) #1
rohitrao (ping after 24h)
LGTM I'm still interested in learning how the rest of the code avoids sending messages ...
10 years, 10 months ago (2010-02-09 21:56:50 UTC) #2
stuartmorgan
10 years, 10 months ago (2010-02-09 22:05:00 UTC) #3
On 2010/02/09 21:56:50, rohitrao wrote:
> I'm still interested in learning how the rest of the code avoids sending
> messages to widgets that aren't views.  I'll dig when I have time and report
> back.

I think it's just that the triggering things would never happen in a non-browser
RWHV. The problem here was that I wired it directly to an intermediate-level
native view, which is used in both cases.

> Why did this move?

Because that line moves the view into the window; if we haven't given the view
enough information to know it's a popup before we do that, there's nothing it
can check.

Powered by Google App Engine
This is Rietveld 408576698