State:Dragging->Collapse on threadpane splitter down doesn't set the messagepane collapse attribute

ASSIGNED
Assigned to

Status

()

Core
XUL
--
major
ASSIGNED
17 years ago
15 years ago

People

(Reporter: varada, Assigned: Eric Vaughan)

Tracking

Trunk
All
Windows NT
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
The State change from Dragging->Collapse on the threadpane splitter in mail
doesnt set the collapse attribute on the Messagepane box to true.
(Reporter)

Comment 1

17 years ago
adding nsbeta1 and mailtrack keywords and blocks 76566
Blocks: 76566
Keywords: mailtrack, nsbeta1
(Reporter)

Updated

17 years ago
Blocks: 77506
(Reporter)

Comment 2

17 years ago
A more detailed explanation
When the state of the splitter changes from Dragging->Collapsed then the
messagepanebox (which is the bottom frame) has to have the collapsed attribute
set to true. This should be a mere extension of the existing functionality which
changes the "collapse" attribute of the grippy when the splitter reaches the bottom.
This way we would be only dependant on the visibility of the messagepanebox and
not on the splitter, for the loading of messages.

Comment 3

17 years ago
EVaughan says you have a workaround, so ->0.9.3
Target Milestone: --- → mozilla0.9.3

Comment 4

17 years ago
Doesn't look like this is getting fixed before the freeze tomorrow night.
Pushing out a milestone.  Please correct if I'm mistaken.
Target Milestone: mozilla0.9.3 → mozilla0.9.4

Comment 5

17 years ago
I think we can live without this for 0.9.4.   let me know if this is not right.
Target Milestone: mozilla0.9.4 → mozilla0.9.5
(Assignee)

Comment 6

17 years ago
pushing out.
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.5 → mozilla0.9.6

Updated

17 years ago
Blocks: 104166
(Assignee)

Updated

17 years ago
Target Milestone: mozilla0.9.6 → mozilla0.9.7

Updated

16 years ago
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → ---
You need to log in before you can comment on or make changes to this bug.