I was wondering about that too. I noticed the IE skin had broken. I thought that the XUL API was frozen for RC2. So if the IE skin worked on RC2 what was changed that messed it up for RC3? Will theme developers need to update again for 1.0? Is this what is meant by evolving standards? They keep changing when you turn your back...
Does anyone know if you can hack out the Spellchecker XPI form Netscape 7 and get it to work in Mozilla RC3? I want a good spellchecker but I don't want to have all my preferences disabled in Netscape 7. -Mark Red Drag Diva wrote: >On Fri, 24 May 2002 22:48:36 -0500, >Jay Garcia <[EMAIL PROTECTED]> wrote: >:::: On 24.05.02 07:07, Gervase Markham Replied Excitedly ::: > >:> It is not true that these features have never worked. In previous >:> releases, the Netscape spell-checker and AIM modules have worked with >:> the corresponding Mozilla. Perhaps something has been done this time to >:> prevent that. That would be a shame. > >: I've been with the project since the very beginning. You mean this >: slipped in somewhere ??? I've never seen AIM or Spellcheck working in >: Mozilla. Mebbe I was on hiatus at the time ya think ?? > > >Some themes have broken with 1.0rc3. Which is impossible, of course, >because the XUL API is *fixed* now. > >*ahem* > >Could be subtle changes since whenever NS7 branched off - somewhere before >rc2? > > > >
