Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344171

Summary:	[client] common margins around auxpane and mainpane classes
Product:	[ECD] Orion	Reporter:	Susan McCourt <susan>
Component:	Client	Assignee:	Susan McCourt <susan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	simon_kaegi
Version:	0.2	Keywords:	polish
Target Milestone:	0.4 M2
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Susan McCourt

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

2011-05-25 12:26:00 EDT

moving styling bugs to RC1

Comment 2 Susan McCourt

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

2012-06-08 17:08:37 EDT

this was fixed with the 0.4 banner