Closed
Bug 365407
Opened 18 years ago
Closed 18 years ago
Reorder tabs in userprefs.cgi
Categories
(Bugzilla :: User Accounts, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.0
People
(Reporter: LpSolit, Assigned: LpSolit)
Details
(Keywords: ue)
Attachments
(1 file)
2.00 KB,
patch
|
justdave
:
review+
|
Details | Diff | Splinter Review |
justdave and I agree that the "General Preferences" panel (a.k.a user prefs) should now be the default panel when accessing userprefs.cgi. I suggest the following order for tabs: user pref / email pref / saved searches / account pref / permissions In other words, the first panel now becomes the 4th one.
Assignee | ||
Comment 1•18 years ago
|
||
Assignee: user-accounts → LpSolit
Status: NEW → ASSIGNED
Attachment #250000 -
Flags: review?(justdave)
Comment 2•18 years ago
|
||
Comment on attachment 250000 [details] [diff] [review] patch, v1 Yeah, this is what I had in mind. Perhaps we should rename the tab to "Name and Password" while we're at it. Account Preferences is too generic to be identifiable. (I know you can change the email there, too, but it doesn't fit ;)
Attachment #250000 -
Flags: review?(justdave) → review+
Assignee | ||
Comment 3•18 years ago
|
||
(In reply to comment #2) > Yeah, this is what I had in mind. Perhaps we should rename the tab to "Name > and Password" while we're at it. Sure, I can do that on checkin.
Flags: approval?
Updated•18 years ago
|
Flags: approval? → approval+
Assignee | ||
Comment 4•18 years ago
|
||
Checking in userprefs.cgi; /cvsroot/mozilla/webtools/bugzilla/userprefs.cgi,v <-- userprefs.cgi new revision: 1.111; previous revision: 1.110 done Checking in template/en/default/account/prefs/prefs.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/account/prefs/prefs.html.tmpl,v <-- prefs.html.tmpl new revision: 1.26; previous revision: 1.25 done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 5•18 years ago
|
||
(In reply to comment #1) >Created an attachment (id=250000) ^^^^^^ ¼ million! Go Party!
You need to log in
before you can comment on or make changes to this bug.
Description
•