./res/xpinstall/progress.html Whenever applicable, please convert HTML files to XUL format so we can externalize localizable resources. Also, refer to the "XUL Coding Style Guidelines" in the URL above for how to make XUL localizable. The target deadline is M9. Thanks!

Hi, Doug: Is this file part of the build? If not, let's not export it to the install directory. (I saw a 'progress.xul', in the same directory.) And, then we can close this bug. Thanks

I am not sure if it is being used any more. Dan?

I am not sure if it is being used any more. Dan?

Hi, Doug/Dan: Are those files part of the build? If not, let's mark them as such and get them out of the radar. M13 is way behind our localization schedule. We won't be able to translate them not to mention about QA verification. Please escalate any priority or resource allocation problem to your managers. Feel free to let me know if I can be of any help. Thanks

This file is going away.

set target milestone to M11, per today's bug meeting.

I believe this is now resolved with dbragg's latest check-in, but I'll let him close it.

Yes. We are no longer using any .html files in our code so technically this bug is closed/fixed. But I'm not going to mark it closed until I remove the progress.html from the build. It is not only obsolete but it's in the wrong area. I need to remove the file and change the makefiles/manifests.

Ok, we're fixed. We're now using the progress.xul from the chrome/xpinstall/content/default directory.

Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine

On dec-15-99 commercial build, the bin/res/xpinstall/ still contain progress.html in additional to progress.xul, which is claimed to be under chrome/xpinstall/content/default/. There is a progress.dtd in "chrome/xpinstall/locale/en-US", though. Mark it verified.