Closed
Bug 91221
Opened 23 years ago
Closed 23 years ago
Turbo mode not enabled after disabling to replace file in use
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.4
People
(Reporter: jimmykenlee, Assigned: dead)
References
Details
Build: 2001-07-17-05-0.9.2(WIN) 1. From http://jimbob/trigger3.html, click on Functional drop-down and select f_addfile_notepad 2. Click Trigger case button 3. Click OK button from Items to Install dialog 4. From Netscape directory, open addFile_notepad, launch notepad.exe 5. From http://jimbob/trigger3.html, click on Functional drop-down and select f_addfile_notepad_inuse 6. Click Trigger case button 7. Click OK button from Items to Install dialog 8. Exit browser 9. Exit notepad 10. Launch browser RESULT: Turbo mode is not enabled. Checking Preferences shows that it is marked as enabled. EXPECTED RESULT: Turbo mode is renabled, so it would be desirable to launch under this mode since the user did not initiate the disabling for replacing a file in use.
Comment 2•23 years ago
|
||
Let us know if the install code needs to do something for this
Comment 3•23 years ago
|
||
Nope. Fix for this is in bug 89504.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.4
nav triage team: Marking nsbeta1+ and p2
Keywords: nsbeta1+
Priority: -- → P2
Comment 5•23 years ago
|
||
please verify this case also when 89504 is closed. *** This bug has been marked as a duplicate of 89504 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 6•23 years ago
|
||
Please leave these open, they need to be verified separately anyways.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 7•23 years ago
|
||
Fixed.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Build: 2001-08-17-06-trunk(WIN) Turbo is enabled after replacing file in use. Cool! Marking Verified!
Status: RESOLVED → VERIFIED
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•