260910 - Modified gtkmozembed built for Mozilla 1.4 doesn't work with 1.7.

Status: RESOLVED INVALID

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

Description

[George Z.]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040817
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040817

Hi, 
I'm working to embedding Mozilla in a Java app/library. On Linux, I'm using the
Gtk Mozilla embedding widget. I modified the test application (located in
directory <MOZILLA_SRC_HOME>/embedding/browser/gtk/tests/) to add features like
profile management, post data, etc.

After building it with Mozilla 1.4, the executable works well with Mozilla
1.4. It also works with 1.7 if the source is built with Mozilla 1.7 source.

But the executable built with Mozilla 1.4 doesn't work with Mozilla 1.7.
there is below error:
~> ./mozembed-test
./mozembed-test: relocation error: ./mozembed-test: undefined symbol:
_ZTV9nsAString

I found it might due to I used the XPCOM APIs, not XPCOM Glue library.

The dependency problem causes the gtkmozembed widget hard to extend.

Thanks for any fixes or comments !

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

this is likely because our embedding samples suck and don't use xpcom glue and
the like...

Comment 2

[George Z.]

Hi Christian:

Thanks for the comments, I feel that's the reason. But I'm not sure if xpcom
glue provides all the required API for the widget and sample app.

The Gtk embedding widget and the sample are great, very easy and stable. But the
problem is, if anybody needs to add any new features, there is the the mozilla
version dependency problem, which make any enhancements only work for a specific
mozilla version. Consider the rapid changes of mozilla/xpcom and the diversity
of installed mozilla, it's quite a trouble and make it less usable.

Any work on this is much appreciated ! 

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Benjamin Smedberg]

gtkmozembed doesn't use frozen APIs.