313835 - cannot set up latest xforms build on latest seamonkey

Status: VERIFIED WORKSFORME

(Core Graveyard :: XForms, defect)

Description

[alexander :surkov (:asurkov)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

xforms build ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-10-25-14-mozilla1.8/windows-xpi/

seamonkey build 
ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/2005-10-25-10-trunk/

Setup is completed ok. Install log is the next:

Mozilla XForms (version 0.2)
     --------------

     ** initInstall: 0
     ** addDirectory components: 0
     ** addDirectory chrome: 0
     [1/9]	Installing: C:\Program Files\mozilla.org\mozilla\components\xforms.xpt
     [2/9]	Installing: C:\Program Files\mozilla.org\mozilla\components\schemavalidation.xpt
     [3/9]	Installing: C:\Program Files\mozilla.org\mozilla\components\nsSchemaValidatorRegexp.js
     [4/9]	Installing: C:\Program Files\mozilla.org\mozilla\components\xforms.dll
     [5/9]	Installing: C:\Program Files\mozilla.org\mozilla\components\schemval.dll
     [6/9]	Replacing: C:\Program Files\mozilla.org\mozilla\chrome\chromelist.txt
     [7/9]	Installing: C:\Program Files\mozilla.org\mozilla\chrome\xforms.jar
     [8/9]	Register Package: jar:resource:/chrome/xforms.jar!/content/xforms/
     [9/9]	Register Locale: jar:resource:/chrome/xforms.jar!/locale/en-US/xforms/
     ** performInstall() returned: 0

     Install completed successfully  --  2005-10-26 11:53:03


But when I open xforms test then it looks like xforms processor isn't ran (there is no one method of xforms interfaces on xforms elements).

Reproducible: Always

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

*** This bug has been marked as a duplicate of 313662 ***

Comment 2

[alexander :surkov (:asurkov)]

Is it really a duplicate? I don't build seamonkey. I download seamonkey without enable-extenstion="xforms" build option and I set up xforms package.

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

That might not be supported.  You're trying to install a Firefox-specific XPI into SeaMonkey.  See http://www.mozilla.org/projects/xforms/#HowDownloadNightly.  Reopening, since I screwed up on the DUPing.  Sorry about that, but I'm still not sure the XPI for Firefox works in SeaMonkey trunk.

Comment 4

[alexander :surkov (:asurkov)]

(In reply to comment #3)
> That might not be supported.  You're trying to install a Firefox-specific XPI
> into SeaMonkey.  See
> http://www.mozilla.org/projects/xforms/#HowDownloadNightly.  Reopening, since I
> screwed up on the DUPing.  Sorry about that, but I'm still not sure the XPI for
> Firefox works in SeaMonkey trunk.
> 

Package xforms.xpi contains install.js file for installation on seamonkey. Moreover it seems to me it was worked for previous realizes.

Comment 5

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #4)
> Package xforms.xpi contains install.js file for installation on seamonkey.
> Moreover it seems to me it was worked for previous realizes.

So did this break on builds after bug 298431 landed on the 22nd?  i.e., are the 10-23 builds broken, but the 10-22 morning builds fine?

Comment 6

[alexander :surkov (:asurkov)]

(In reply to comment #5)

> So did this break on builds after bug 298431 landed on the 22nd?  i.e., are the
> 10-23 builds broken, but the 10-22 morning builds fine?
> 

Do you mean xforms build? Problem is lying in seamonkey build because previous xforms builds are not work too (f.x. september build).

Comment 7

[Stephen Donner [:stephend] Not actively reading bugmail]

Yes, I meant in the XPI itself...

Comment 8

[Stephen Donner [:stephend] Not actively reading bugmail]

OK.  This worksforme if I install:

File: xforms.xpi  	112 KB  	10/25/2005  	1:06:00 PM from ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-10-25-06-trunk/windows-xpi

using SeaMonkey trunk build 2005-10-25-09 on Windows XP.

I found this out by reading news://news.mozilla.org:119/[e-mail] where Allan says, "Sounds bad. You need to make sure that the XPI and the nightly build of firefox is from the exact same time. The link Aaron posted is for Deer Park alpha 1, not a random nightly build."

I found this to be true for SeaMonkey too, and now it's working for me.  Alexander, can you please try this?

Comment 9

[alexander :surkov (:asurkov)]

(In reply to comment #8)
> OK.  This worksforme if I install:
> 
> File: xforms.xpi        112 KB          10/25/2005      1:06:00 PM from
> ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2005-10-25-06-trunk/windows-xpi
> 
> using SeaMonkey trunk build 2005-10-25-09 on Windows XP.
> 

Please provide a link on seamonkey. I cannot find 2005-10-25-09 build.


> I found this out by reading
> news://news.mozilla.org:119/[e-mail]
> where Allan says, "Sounds bad. You need to make sure that the XPI and the
> nightly build of firefox is from the exact same time. The link Aaron posted is
> for Deer Park alpha 1, not a random nightly build."
> 
> I found this to be true for SeaMonkey too, and now it's working for me. 
> Alexander, can you please try this?
> 

I can it understand for firefox but not for seamonkey: chrome.rdf specifies required firefox version but install.js doesn't do it.

Comment 10

[alexander :surkov (:asurkov)]

Mark as worksforme. Seamonkey build 2005-10-25-10 and xforms build 2005-10-25-06 works together. It is interesting why some build are not compatible?

Comment 11

[Allan Beaufour]

(In reply to comment #10)
> Mark as worksforme. Seamonkey build 2005-10-25-10 and xforms build
> 2005-10-25-06 works together. It is interesting why some build are not
> compatible?

Could be changes to the Gecko version, or to core APIs changing. The latter would probably make us crash though. Whatever, if it works for you now I'm happy :)

Comment 12

[Stephen Donner [:stephend] Not actively reading bugmail]

verified, as this worksforme as I've already mentioned.  Sorry for the spam while trying to figure this out.

Comment 13

[Olli Pettay [:smaug][[e-mail]]]

(In reply to comment #11) 
> Could be changes to the Gecko version, or to core APIs changing. The latter
> would probably make us crash though. 

Just a change to nsIContent's or nsIDocument's IID is enough to make
some QIs to fail.