Re-enable effective TLD functionality for new location bar

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
12 years ago
11 years ago

People

(Reporter: Gavin, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph
Bug Flags:
blocking-firefox3 -

Firefox Tracking Flags

(Not tracked)

Details

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.
Flags: blocking-firefox3?
Not going to block on this for now, we're going to avoid grey text for present.
Flags: blocking-firefox3? → blocking-firefox3-
(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]?

Comment 3

12 years ago
mem usage & leaks have been fixed; it's down to the "grey text" argument now.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WONTFIX

Comment 4

11 years ago
in that case, someone should remove the dead code at http://mxr.mozilla.org/mozilla/source/browser/base/content/urlbarBindings.xml#234.
Depends on: 400809
(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?
You need to log in before you can comment on or make changes to this bug.