137039 - [minimo]move nsIXULChromeRegistry out of "chrome" module

Status: RESOLVED FIXED

(Minimo Graveyard :: General, defect, P3)

Description

[Alec Flett]

so now that nsIChromeRegistry has been split into nsIXULChromeRegistry and
nsIChromeRegistry, we can do a little REQUIRES cleanup such that rdf/chrome
doesn't have to be pulled/built for embedding purposes.

basically, once we have an embedding-only nsIChromeRegistry implementation, the
actual interface can live somewhere more public than "chrome" like possibly
webBrowser_core. XUL's chrome implementation can go do its own thing with
nsIXULChromeRegistry..

Here's what needs to be done:
1) move the nsIXULChromeRegistry interface to its own .idl file in
rdf/chrome/public/nsIXULChromeRegistry.idl
2) move the resulting nsIChromeRegistry interface/idl into something like
embedding/browser/webBrowser/nsIChromeRegistry.idl
3) copy or share the nsChromeProtocolHandler implementation in an embedding dll.

Comment 1

[Alec Flett]

anyway, this is a ways off

Comment 2

[Alec Flett]

actually for now I think we'll move nsIXULChromeRegistry..

Comment 3

[Alec Flett]

pushing a few bugs out to 1.2beta - too much stuff on my 1.2alpha plate!

Comment 4

[Alec Flett]

moving some stuff out to mozilla1.2beta that didn't make the mozilla1.2alpha train

Comment 5

[Alec Flett]

mozilla 1.1alpha is more or less done, so I'm moving non-critical mozilla1.2beta
bugs out to the next milestone to make room for the mozilla1.1alpha bugs that
didn't make it.

Comment 6

[Alec Flett]

moving non-critical 1.3alpha bugs to 1.4alpha

Comment 7

[Alec Flett]

mass moving lower risk 1.4alpha stuff to 1.4beta

Comment 8

[Doug Turner (:dougt)]

moving minimo bugs to the new bugzilla product.

Comment 9

[Benjamin Smedberg]

This got fixed (by me) a long time ago, to avoid toolkit forkage.