Closed
Bug 327737
Opened 20 years ago
Closed 18 years ago
inconsistent hiding/disabling of thunderbird toolbar buttons in Lightning views
Categories
(Calendar :: Lightning Only, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: gekacheka, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: version 1.6a1 (20060218) + Lightning nightly 20060218
Bug 324194 moved the Thunderbird messages filter and messages search box to the toolbar, and bug 325140 hid the search box when viewing a calendar grid instead of messages.
Inconsistent:
- The search box seems to be the only toolbar item HIDDEN.
- The message toolbar items are usually DISABLED if no message is selected.
- Some items remain showing and enabled even though they are inapplicable (such as the filter box).
Suggest that while calendar views are showing, all message related toolbar items should either be ALL DISABLED or ALL HIDDEN, not a mixture.
(Since there is only one toolbar and thus a shortage of toolbar space, hiding might help make more room available for lightning toolbar items that are hidden while messages are displayed. But currently the lightning toolbar items are all potentially useful when messages are displayed. Maybe the go-to-today button could be visible only in lightning mode, but the view buttons are useful for switching to a lightning view, and the new task/new event buttons are useful for creating new tasks/events while reading a message.)
Reproducible: Always
Steps to Reproduce:
switch between message view to a lightning view via say menu Calendar | month view
Actual Results:
Disabled:
Most message toolbar buttons: reply, forward, next, delete
Hidden:
Message Search box
Remains visible and enabled:
Message Filter box.
Previous message button.
Expected Results:
Either
inapplicable toolbar items ALL DISABLED
or
inapplicable toolbar items ALL HIDDEN
Comment 1•18 years ago
|
||
This bug should be INVALID with the new Calendar mode.
You need to log in
before you can comment on or make changes to this bug.
Description
•