Closed
Bug 112065
Opened 23 years ago
Closed 14 years ago
Need a UI spec for better communicating sidebar state to users
Categories
(SeaMonkey :: Sidebar, defect)
SeaMonkey
Sidebar
Tracking
(Not tracked)
RESOLVED
EXPIRED
mozilla1.2alpha
People
(Reporter: samir_bugzilla, Assigned: marlon.bishop)
References
Details
Per item 1 in the usability discussion documented below we need a UI spec addressing all the subitems listed under item 1. See: <http://www.mozilla.org/xpapps/sidebar/proposals/usability.html> Marlon, when do you think you'll be able to supply this to engineering so we can incorporate it into our plan? Thanks.
Reporter | ||
Updated•23 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Assignee | ||
Comment 1•23 years ago
|
||
i think we hit this issue, see implementable checklist summary soon.
Target Milestone: --- → mozilla0.9.9
Assignee | ||
Comment 2•23 years ago
|
||
the one open issue is - search sidebar discreetness. samir, do you feel confident that the other issues on that list are getting taken care of at this point? If so can we close this bug and open a new one, or retarget this to hit the one item we have left?
Comment 4•23 years ago
|
||
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
i'm pretty sure someone already resolved the relevant bug as wontfix which would imply a magical spec was conjured up...
Reporter | ||
Comment 6•22 years ago
|
||
Marlon, Unfortunately we haven't yet addressed a design to eliminate hidden vs. collapsed states. If the splitter still exists (and the new personal toolbar button which is only an idea at this point) then we still need to address whether to remove the grippy. Also, does this mean we remove the close button to reduce states? These are the open-ended issues.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 7•15 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 8•14 years ago
|
||
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•