Closed Bug 11271 Opened 22 years ago Closed 22 years ago

NetsupportConfirm.xul -> NetSupportConfirm.xul


(SeaMonkey :: UI Design, defect, P3)

Windows NT


(Not tracked)



(Reporter: morse, Assigned: davidm)



File in xpfe\browser\resources\content needs to be renamed (upper case S instead
of lowercase).

Also there is another copy of this file in xpfe\browser\src which I presume is
obsolete and probably should be removed from the tree.  Ironically, it had the S
Also NetSupportUserPAssword should be NetSupportUserPassword.

Note that the error is also in so that needs to be updated when
these files are renamed.  The file and the Manifest file are
already correct.
Target Milestone: M9
I already corrected this by checking in the right versions of these files and
also checked in revised  The only thing remaining to be done is to
remove the old names from the tree.  I didn't want to do that because I don't
know what consequence that would have on the mac (are these files in mac project
These files are not in a project only a manifest file. I haven't changed them
since they will be obsolete shortly.
Depends on: 11611
Target Milestone: M9 → M10
Move to m10 wil be removed when new dialog code goes in.
Closed: 22 years ago
Resolution: --- → FIXED
remove files from tree
Using the 1999082016 (M9) build, I still see NetsupportConfirm.xul and not
NetSupportConfirm.xul in the /chrome/navigator/content/default directory. If
this is only supposed to be fixed in M10 builds, please let me know so that I
may check those builds later on. Thanks.
M10 only
Fixed in 1999090908 build (M11 build), Windows NT. Marking verified.
Actually, hang on a second... all I see are two files,
NetSupportConfirmCheckYN.xul and NetSupportConfirmYN.xul. What happened to
NetSupportConfirm.xul? Is this fixed, or is that a bug? Thanks.
Consider this fixed as I removed the plain confirm from the tree as they are  n
longer used
Changing component to XP Apps. (HTML Dialogs is going away.)
Component: HTML Dialogs → XPApps
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.