Bug 344171 - [client] common margins around auxpane and mainpane classes
Summary: [client] common margins around auxpane and mainpane classes
Status: RESOLVED FIXED
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.4 M2   Edit
Assignee: Susan McCourt CLA
QA Contact:
URL:
Whiteboard:
Keywords: polish
Depends on:
Blocks:
 
Reported: 2011-04-28 14:02 EDT by Susan McCourt CLA
Modified: 2012-06-08 17:08 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Susan McCourt CLA 2011-04-28 14:02:42 EDT 
Right now our content margins are done in the HTML of each page (the divs inside the content panes).  The content panes themselves have common classes, "auxpane" and "mainpane" which do not have margins.  

At one time I recall problems getting content panes to respect margins that were in CSS classes vs. specified inline.  Not sure what the state of the world is now.  We also were driven by the behavior of the collapsing splitter, but we have since nested that splitter.

Need to revisit all this so that the content margins are consistent and the individual pages don't have to do anything.
Comment 1 Susan McCourt CLA 2011-05-25 12:26:00 EDT 
moving styling bugs to RC1
Comment 2 Susan McCourt CLA 2011-06-13 16:55:41 EDT 
The 44px margins that we hardcoded in the various pages are no longer needed.
Fixed those in RC1 when we changed the header layout.

For post 0.2, I'd like to look at getting rid of BorderContainer and if we do this, it should be straightforward to include all other margins in CSS.
Comment 3 Susan McCourt CLA 2012-06-08 17:08:37 EDT 
this was fixed with the 0.4 banner