Doug Turner wrote: > There has been some discussion in bug 93222 regarding backward > compatibility of non frozen interfaces. Sounds like a bad thing to do, > but Mozilla has to support some of these unfrozen and soon-to-be > obsolete interface since plugins have shipped using these interfaces. > Duh! If we don't support these interfaces, existing plugins will break. > This is unacceptable for many.
So you're saying that there _are_ existing, shipped plugins that will be broken by nsIClassInfo changes, in spite of the fact that we've already broken binary compatibility once? Which existing (shipped, working with existing Mozillas today) plugins break if we change which interfaces? Let's get all the cards on the table before we decide that we need to retrospectively freeze these interfaces. Mike
