Closed
Bug 30156
Opened 25 years ago
Closed 24 years ago
Delete Profile dialog should match N4.7's
Categories
(SeaMonkey :: Startup & Profiles, defect, P1)
Tracking
(Not tracked)
Future
People
(Reporter: bugs, Assigned: paulkchen)
References
Details
(Keywords: polish, Whiteboard: [nsbeta3+][nsbeta2-])
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
In the aftermath of 30119 it seems that we need to put up a dialog at the lowest
level before deleting a profile to show what folder is about to be deleted to
allow the user to abort the procedure, to prevent against foo caused by future
updates to the profile manager.
e.g. "you are about to delete all files and folders in the folder c:\foo, they
will be unrecoverable. click cancel to abort this operation" or similar.
(requested by jar)
Updated•25 years ago
|
Whiteboard: [PDT+] w/b minus on 3/7
Comment 2•25 years ago
|
||
[PDT+] w/b minus on 3/7
Comment 3•25 years ago
|
||
Bhuvan, any update?
On backend, we are initialized before the hidden window activities are done.
Common diaog services are based on having hidden window initialization.
So, currently looking at the other alternative of passing the directory name to
frontend for the confirmation....
I spoke to davidm regarding the chnages I can do in the backend using nsIPrompt.
It is too destabilizing for beta for that changes. We can work this out via
front end once we start using nsIRegistry and have GetProfileDir scriptable.
Once gayatri lands i18n changes, we should do this from the frontend as
nsIRegistry can be used to query for directory name. Then a javascript confirm
dialog can be put up. Will talk to ben regarding this one.
Target Milestone: M14 → M15
With gayatri's changes in, now nsIRegistry can be used to query the registry for
profile directory name. A confirm dialog can be thrown with the obtained
directory name. Displaying confirm dialog is much easier and convenient to
achieve i18n compatability and to alter messgae as required. As per the
directory name, we are getting it from the registry and it is accurate.
Posting the patch (next update). Reassigning to ben.
Assignee: racham → ben
Status: ASSIGNED → NEW
Comment 11•25 years ago
|
||
changing the component to front-end.
Component: Profile Manager BackEnd → Profile Manager FrontEnd
Comment 12•25 years ago
|
||
Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may
pull this for PR2.
Whiteboard: [PDT-] w/b minus on 3/7 → [nsbeta2+][6/01]
Reporter | ||
Comment 13•25 years ago
|
||
some slight modification of delete profile dialog required + bhuvan's patch.
Time to complete: 2 hours.
Status: NEW → ASSIGNED
Comment 14•25 years ago
|
||
Changing from [6/01] to [6/15]
Whiteboard: [nsbeta2+][6/01] → [nsbeta2+][6/15]
Comment 16•24 years ago
|
||
Cleaning up status whiteboard by marking beta2 minus (6/15 has passed)
Folks are too doomed to handle this for beta2
Whiteboard: [nsbeta2+][6/15] → [nsbeta2-]
Comment 17•24 years ago
|
||
Per nav triage team: We have a dialog now. It's imperfect, but its good enough.
Keywords: polish
Whiteboard: [nsbeta2-] → [nsbeta2-] [nsbeta3-]
Updated•24 years ago
|
Severity: major → normal
Target Milestone: M19 → Future
Reporter | ||
Comment 18•24 years ago
|
||
Starting in N4.7, the Delete profile dialog displayed the path of the profile
about to be deleted. Adding 4xp keyword, nominating for nsbeta3.
Assignee | ||
Comment 19•24 years ago
|
||
nav triage team:
taking this one for the gipper
Assignee: ben → pchen
Status: ASSIGNED → NEW
Whiteboard: [nsbeta2-] → [nsbeta3+]
Comment 21•24 years ago
|
||
make that n*s*beta2-
Whiteboard: [nsbeta3+][nebeta2-] → [nsbeta3+][nsbeta2-]
Comment 22•24 years ago
|
||
PDT marking this bug a dup. Delete profile prompt is fine for Semaonkey RTM.
*** This bug has been marked as a duplicate of 37387 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 24•24 years ago
|
||
*** Bug 32810 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 25•24 years ago
|
||
*** Bug 32810 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•