Closed Bug 319861 Opened 20 years ago Closed 20 years ago

hardcoded string "Firefox" used

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: chpe, Unassigned)

References

Details

For users of the strings defined in http://lxr.mozilla.org/seamonkey/source/browser/locales/en-US/chrome/overrides/appstrings.properties#40 they should use the branding bundle instead (since those strings are also shown in embedding apps).
That bundle is a Firefox-specific override... the file that should be used for embedding is http://lxr.mozilla.org/seamonkey/source/dom/locales/en-US/chrome/appstrings.properties . See bug 305998.
(In reply to comment #1) > That bundle is a Firefox-specific override... the file that should be used for > embedding is > http://lxr.mozilla.org/seamonkey/source/dom/locales/en-US/chrome/appstrings.properties > . See bug 305998. The problem is specifically that this override bundle *is* used in embedding apps. Steps to repro: 0) Build ff gtk2 1) Start TestGtkEmbed (or a gtkmozembed embedding app like epiphany, galeon or kazehakase) 2) Load "test:/" Result: Alert: "Firefox doesn't know how to open this address, because the protocol (test) isn't associated with any program."
Well, embedding apps shouldn't be using Firefox (i.e. not building /browser), they should be using XULRunner, but I don't know what the the official stance is on supporting the use of FF as a base for embedding apps at this point.
Hardware: PC → All
Yep, and if you're using gtkmozembed from a firefox build that's what you'll get.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
(In reply to comment #3) > Well, embedding apps shouldn't be using Firefox (i.e. not building /browser), > they should be using XULRunner, but I don't know what the the official stance > is on supporting the use of FF as a base for embedding apps at this point. > I'm afraid the situation around branding have changed from that a year ago, as described at bug 362902. There are a lot of bugs to solve this problem (e.g. bug 30636, bug 30120, bug 302309 etc.), but none of them is working effectively since this bug was initially regressed by bug 305998, because those background problems are rather complicated. So, this bug might be a dupe, but I think should be fixed anyway.
You need to log in before you can comment on or make changes to this bug.