After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 543577 - Does not provide navigator.productSub
Does not provide navigator.productSub
Status: RESOLVED FIXED
Product: galeon
Classification: Deprecated
Component: Mozilla interaction
unspecified
Other Linux
: Normal normal
: ---
Assigned To: galeon-maint
galeon-maint
Depends on:
Blocks:
 
 
Reported: 2008-07-18 11:17 UTC by Joachim Breitner
Modified: 2008-09-30 15:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Joachim Breitner 2008-07-18 11:17:37 UTC 
Hi,

recently, probably with the new xulrunner, the WYSIWYG editor of
serendipity stopped working, claiming that I should use at least
Mozilla-1.3. It seems that this is caused by the lack of support for the
javascript variable navigator.productSub.

This can also be checkable using the Javascript console. The value is
undefined. Typing in navigator.productSub in current Debian’s iceweasle, I
get 2008062910.

Thanks,
Joachim

(from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491100)
Comment 1 Joachim Breitner 2008-09-02 17:35:23 UTC 
Hi again,

I’m trying to debug this problem. Strangely, epiphany does have a value for the productSub, but grep’ing through either epiphany’s or galeon’s source, I find no mention of productSub. Any pointers where to continue looking?
Comment 2 Joachim Breitner 2008-09-02 21:06:28 UTC 
Ok, I did some more investigation. It seems that you have to implement a nsIXULAppInfo class to make this work cleanly, as done by the epiphany guys in this commit: http://svn.gnome.org/viewvc/epiphany?view=revision&revision=8228

I assume it’s just a matter of copying their class file, adjusting the values and plugging it in. I hope at least :-)
Comment 4 Joachim Breitner 2008-09-03 08:16:05 UTC 
Ah, cool :-)

Thanks for the work! I think the bug can be closed, or do you close them when the fix is actually released?
Comment 5 Yanko Kaneti 2008-09-30 15:18:13 UTC 
I guess this was released in 2.0.7. Closing.