Closed
Bug 98100
Opened 24 years ago
Closed 24 years ago
gtkmozembed embedding clients are sent extremely large resize calls for PSM XUL Dialogs
Categories
(Core Graveyard :: Embedding: GTK Widget, defect)
Tracking
(Not tracked)
People
(Reporter: mozillabugs.philipl, Assigned: blizzard)
References
()
Details
I'm not sure whether this is a PSM or embedding issue, hope I got it right. :-)
In all gtkmozembed clients ( we've tested galeon, skipstone and TestGtkEmbed )
when a PSM XUL dialog appears, an incorrect resize call gets sent after the
correct one. Here is the console output from TestGtkEmbed.
loading url https://207.71.92.193/
open_uri_cb https://207.71.92.193/
load_started_cb
net_state_change_cb 458753
new_window_orphan_cb
chromemask is -134216698
new_gtk_browser
new browser is 0x41407e40
open_uri_cb jar:resource:///chrome/pippki.jar!/content/pippki/domainMismatch.xul
load_started_cb
location_changed_cb
*** size_to_cb 321 224
*** size_to_cb 71582793 71582792
load_finished_cb
*** size_to_cb 71582793 71582792
visibility_cb 1
After which, it crashes out as GDK can't handle that large a window.
( The url in question is simply grc.com, but using the ip address provokes a
domain mismatch error, causing a dialog to appear )
This bug is not in 0.9.3 and appeared in a cvs a couple of weeks ago, I think.
I don't see this in my optimized build from yesterday.
Reporter | ||
Comment 3•24 years ago
|
||
Just to make clear, there is no problem in mozilla-the-browser, only in the
embedding context does this problem arise.
Yeah, I was using TestGtkEmbed.
Comment 5•24 years ago
|
||
just tried with TestGtkEmbed from a hour old anoncvs
the bug is real for me too
Comment 6•24 years ago
|
||
so i did test with the patch attached to #72152
it fixes this crash so i guess its really the same thing
Reporter | ||
Comment 7•24 years ago
|
||
*** This bug has been marked as a duplicate of 72152 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•13 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•