Find dialog won't open in Navigator for me anymore in a new tip build (works in Editor): JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x8 0040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIInterfaceRequestor.getInterface]" nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame : : chrome://global/content/xulBindings.xml#browser.webBrowserFind (getter) :: ong et :: line 0" data: no]

Removing my component.reg fixes this. This is the second time in the past 2 or 3 days where I've needed to remove my component.reg. Did something change?

Converting this to a component.reg bug. Why do we have to keep removing this file? looking for a new owner in case smfr doesn't want to be on the hot seat...

dbaron says to look at bug 46863

apparently, optimized builds don't run regxpcom, so if some module {load,unload} callbacks change you will have problems. This was done to save startup time. How about doing this only for the official build case?

*** Bug 78054 has been marked as a duplicate of this bug. ***

nsIWebBrowserFind moved to a different module, so I guess I should have changed its IID. I'll do that. Other than this Find issue, I'm not the person to own a general 'need to remove XPCOM registry' bug.

This won't affect installed builds, where the components reg is recreated.

i haven't encountered this, so [rubberstamp] vrfy. still a problem for anyone?