bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Available interfaces on installer builds differ from those on zip builds.

RESOLVED EXPIRED

Status

()

Firefox
Build Config
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: KENZ (Kenji Irie), Assigned: Blake Ross)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031216 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031216 Firebird/0.7+

I found this problem since a bug is reported to Bugzilla-jp
<http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=3572>, the bug claim that
nsIEditingSession interface is not available on recent builds, original reporter
used the interface for his XUL extension.

I had some investigation, and found the problem comes from the difference
between zip build and installer build. The zip build's xpti.dat has 1011
interfaces entry, but the installer build's one has 1005 interfaces entry, thus
there are 6 interfaces which became unavailable recently (because there are no
Windows zip build today).

All interfaces on non-installer build should be available on installer build, I
think.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
installer builds also may or may not include other features depending on
installed options.

nsIEditingSession is part of the editor component, I'm not sure whether its
needed for Midas though
Component: General → build-config
(Reporter)

Comment 2

15 years ago
I see, I said about case all install options checked.
Official windows builds (zip and installer) has the same build options according
to those 'about:buildconfig'. Full featured installation should have the same
functionality as the zip build, isn't it?

By the way, about nsIEditingSession, it's used in <editor> XUL element's XBL
file <http://lxr.mozilla.org/mozilla/source/toolkit/content/widgets/editor.xml>

 75       <property name="editingSession"
 76                 readonly="true"
 77                 onget="return
this.webNavigation.QueryInterface(Components.interfaces.nsIInterfaceRequestor).getInterface(Components.interfaces.nsIEditingSession);"/>"

for this, XUL element <editor> is available in Mozilla Firebird, but it doesn't
work. This should be fixed at least.

Comment 3

15 years ago
Midas works fine in the installer build from Jan 2.  So either WFM or this bug
doesn't affect Midas.
(Reporter)

Comment 4

15 years ago
Thanks to confirm that Midas works on installer builds, jesse.

yes, nsIEditingSession is a part of editor component.
By the way, the <editor> XUL element is part of the *XUL toolkit*, thus we can
use the <editor> element in our XUL apps/extensions, I think.
But the XUL element uses the nsIEditingSession interface in it, so some of the
element's methods or the properties (the editingSession property, and methods or
properties using it) simply don't work on windows installer builds which don't
have the interface.

Shouldn't XUL apps/extensions authors use the <editor> element since Mozilla
Firebird is built with configure option --disable-composer? Though it works on
official linux builds or Windows zip builds.
(Reporter)

Updated

15 years ago
Depends on: 232651

Comment 5

15 years ago
*** Bug 232651 has been marked as a duplicate of this bug. ***
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.