Closed Bug 52560 Opened 25 years ago Closed 25 years ago

Desktop Integration pref dialog uses refers to "Mozilla"

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 95
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: verah, Assigned: jglick)

Details

(Keywords: polish, Whiteboard: nsbeta3+)

This text is in the Desktop Integration preferences dialog: "Select the types of files you want to view using Mozilla. Windows will use Mozilla when you open any files of the selected types." "Select the types of Internet Shortcuts you want to view using Mozilla. Windows will use Mozilla when you open any shortcuts of the selected types." Can we change this to: "Select the types of files you want to view using Navigator. Windows will use Navigator when you open any files of the selected types." "Select the types of Internet Shortcuts you want to view using Navigator. Windows will use Navigator when you open any shortcuts of the selected types."
Adding polish and nsbeta3 keywords.
Keywords: nsbeta3, polish
can we file these bugs to UI Design Feedback or Preferences or some place other than Browser General.
Are you getting tired of this? Yes, if there are any more, I'll file them under Preferences. But this was the last one, I think.
verah, OK, I can handle it if there aren't many more :) I just didn't want Browser General to become the dumping ground for all future spelling error bugs.
question - is this nsonly or should it be navigator for mozilla builds as well?
Reassign to myself
Assignee: asa → jglick
Marking nsbeta3+ since jglick has this bug fix in hand.
Whiteboard: nsbeta3+
jennifer checked this in...
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
The Mozilla build says "Mozilla" and the commercial build says "Netscape".
so, not "navigator"?
Correct. I spoke with Vera about this bug before she filed it. She originally wanted the wording to match the commercial vs mozilla build ("Mozilla" and "Netscape" wording), but because that was more difficult to implement, she wrote the bug up using wording that both builds could use. I was able to figure out how to get the Mozilla and Netscape builds to use different wording, so I did that.
verified on mozilla, I assume this correct on commercial.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.