Use of the effective TLD service in the new location bar binding had to be disabled because the eTLD service causes leaks and uses a lot of memory (see blocking bugs). When those issue are fixed, we need to re-enable the location bar code that uses it, in urlbarBindings.xml.

Not going to block on this for now, we're going to avoid grey text for present.

(In reply to comment #1) > Not going to block on this for now, we're going to avoid grey text for present. Even if it's just for the subdomain as in attachment 272298 [details]?

mem usage & leaks have been fixed; it's down to the "grey text" argument now.

in that case, someone should remove the dead code at http://mxr.mozilla.org/mozilla/source/browser/base/content/urlbarBindings.xml#234.

(In reply to comment #4) > in that case, someone should remove the dead code at > http://mxr.mozilla.org/mozilla/source/browser/base/content/urlbarBindings.xml#234. Why is that dead code?

> > in that case, someone should remove the dead code at > > http://mxr.mozilla.org/mozilla/source/browser/base/content/urlbarBindings.xml#234. > > Why is that dead code? Not that. That: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/browser/base/content/urlbarBindings.xml&rev=1.37#234 Already removed by bug 400809.