Closed Bug 430090 Opened 16 years ago Closed 15 years ago

Collapsed state of Today pane is not remembered when dragging the splitter

Categories

(Calendar :: Lightning Only, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: giermann, Assigned: bv1578)

References

Details

This is a spin-off from bug 389150 comment #77 and #78:

When I collapse the pane (by dragging the edge of the today pane) and then switch to mail mode and then switch back to the calendar mode the today pane expands. It does not remember it's last expanded/collapsed state. However, it works as expected when I use the F11 shortcut key to collapse and expand the pane.

This actually happens for panes in all modes (mail/calendar/task).
Since Christian agreed with bug 390982 comment #9, that is to still display the splitter an leave the button state active when only dragging the splitter - this might end up to be a duplicate of the request "Store Today Pane width Mode dependent" in bug 429687.
We just would need to remember the width to be zero...
Flags: wanted-calendar0.9?
Flags: wanted-calendar0.9? → wanted-calendar0.9-
Depends on: 445304
(In reply to comment #1)
> We just would need to remember the width to be zero...

Setting dependency to bug 445304 because of this. Maybe this bug will be auto-resolved with mode dependent widths.
Still an issue using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090608 Lightning/1.0pre Shredder/3.0b3pre.
Assignee: giermann → nobody
Status: ASSIGNED → NEW
Flags: wanted-calendar0.9-
Decathlon, Sven, has bug 445304 also resolved this one?
(In reply to comment #4)
> Decathlon, Sven, has bug 445304 also resolved this one?

It works for me as requested in comment #0 and comment #1 for the behavior of the todaypane button related to the collapsed/hidden splitter state.
Fixed by checkin of patch from bug 445304.
Assignee: nobody → bv1578
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
You need to log in before you can comment on or make changes to this bug.