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

Issue 113545: Linux: Don't unparent unselected tab contentses.... (Closed)

Created:
11 years, 7 months ago by Evan Stade
Modified:
9 years, 6 months ago
CC:
chromium-reviews_googlegroups.com
Visibility:
Public.

Description

Linux: Don't unparent unselected tab contentses. Instead, hide them. Sometimes an unselected tab contents can get unhandled keyboard events after it's been deselected (if the renderer was really slow in handling and returning the event). http://crbug.com/12178 Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=16329

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+18 lines, -5 lines) Patch
M chrome/browser/gtk/browser_window_gtk.cc View 1 chunk +2 lines, -3 lines 0 comments Download
M chrome/browser/gtk/tab_contents_container_gtk.h View 1 chunk +3 lines, -0 lines 0 comments Download
M chrome/browser/gtk/tab_contents_container_gtk.cc View 3 chunks +13 lines, -2 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
Evan Stade
11 years, 7 months ago (2009-05-18 20:42:57 UTC) #1
willchan no longer on Chromium
Took me a second to grok this. I'm still confused as to how the focus ...
11 years, 7 months ago (2009-05-18 21:01:02 UTC) #2
Evan Stade
yea. After investigating I found that something slightly different is happening: 1) user presses ctrl-pgdn, ...
11 years, 7 months ago (2009-05-18 21:16:23 UTC) #3
willchan no longer on Chromium
11 years, 7 months ago (2009-05-18 21:34:21 UTC) #4
On 2009/05/18 21:16:23, Evan Stade wrote:
> yea. After investigating I found that something slightly different is
happening:
> 
> 1) user presses ctrl-pgdn, we forward to webkit
> 2) user presses ctrl-pgdn, we forward to webkit
> 3) webkit returns with UnhandledKeyboardEvent for (1). We switch to a new tab
> contents.
> 4) webkit returns with UnhandledKeyboardEvent for (2), but by this time the
tab
> contents has been deselected and unparented, hence we get a null toplevel
> window.
> 
> so, fix is still the same :). This should also make getting the top level for
> the tab contents view more reliable in general (which is used for various
things
> like focus).

Ok, this makes sense.  Thanks for the explanation.

Powered by Google App Engine
This is Rietveld 408576698