161736 - we should register components if mozilla.exe is newer than the component registry

Status: RESOLVED DUPLICATE of bug 162593

(SeaMonkey :: General, defect)

Description

[timeless]

Error:
Components.classes['@mozilla.org/appshell/component/browser-status-filter;1']
has no properties
Source File:
chrome://global/content/bindings/tabbrowser.xml#tabbrowser.addProgressListener()
Line: 17

Comment 1

[timeless]

i've been using bugzilla and bonsai and ... and this build (2002080807)
generally will not update the urlbar. this is causing me all sorts of pain since
i use the urlbar to go from a keyword (gu pref-navigator.js) to a cvsblame url
which i then feed to cvs co so that i can write a patch.

someone else on #mozillazine (rkaa?) also was experiencing problems.

in littlemozilla the back/forward buttons aren't working either, i think in
newclassic they were but the urlbar is definitely not working well in either.

Comment 2

[timeless]

i can't click back either.
2002080807w32

Comment 3

[timeless]

the error comes from tabbrowser, i think this is darin's mess.

Comment 4

[R.K.Aa.]

if i right-click and force a contex menu to appear, that seems to "clear" the
situation and urlbar etc. are once again "listening" to me

Comment 5

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Do you need to rerun regxpcom?  (Is this in your own opt build?)

Comment 6

[timeless]

talkback nightly. running regxpcom cleared things up. let's fix this so that a
newer mozilla.exe automatically registers components

Comment 7

[Doug Turner (:dougt)]

this should be done from inside bootstrap of the application, not xpcom.  

Comment 8

[Wesha]

Related - bug 130793

Comment 9

[Wesha]

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

Comment 10

[timeless]

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