Closed Bug 80686 Opened 24 years ago Closed 6 years ago

Embedding layer shouldn't assume it's starting up toolkits

Categories

(Core Graveyard :: Embedding: GTK Widget, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: tvl, Assigned: blizzard)

References

Details

widget/src/gtk/nsAppshell.cpp

nsAppShell::Create initializes a bunch of gtk & gdk things.  In the embedded 
world, my application has already initialized these things.  As a result, we 
appear to get a few more leaks from these layers, but worse, the feeding of the 
gtkrc to the app causes our apps look to suddenly change.  When we start up, we 
initialize gtk with a canned gtkrc and don't feed it the one in $HOME.  mozilla 
shouldn't assume that this should be done.  Their should either be a way to 
configure the appshell so it doesn't do this, or maybe their should be an 
embeddign appshell that doesn't do this.
Blocks: 77421
Status: UNCONFIRMED → NEW
Ever confirmed: true
I raised the severity because we are very concerned with this.
Severity: normal → major
hrm.  this is an interesting problem.  I do need to start up an appshell
instance because that's how the event loop is initialized.
Any bright ideas?  How about a pref so that it doesn't read the gtkrc?
Or moving the rc reading down to the app layer?
pref sounds dangerous since change the value could cause all sorts of problems 
for apps.  it's more of a build time decision.

seems like moving to the app layer make more sense.  with the goal of an embedder 
being able to use the embedding apis for startup and not have to worry about 
something they've already done getting done again on them.
this bug has not been touched since 2001-08-06, therefore this reminder.

Reporter could you please retest with a current mozilla build and let us know if
the problem is still present or the bug can be closed.
QA Contact: pavlov → gtk-widget
Product: Core → Core Graveyard
Embedding: GTK Widget isn't a thing, closing.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.