[TriLUG] CSS question
bdmc at bdmcc-us.com
Wed Feb 1 08:54:56 EST 2012
On Tue, Jan 31, 2012 at 10:07:53AM -0500, Mitchell Amiano wrote:
> If by "position: nothing" you mean absence of the property,
> the formatting will be "static", which is not the same as relative, so it makes sense that it would differ.
> "top" and "left" properties are ignored in static positioning.
Those were not set in any case.
> Relative positioning offsets elements out of the position they would have been at in the normal flow. The layout flow can be affected by whether the element is being treated as a block, an inline-block, or an inline-element, whether line-breaking spaces are present,
The structure was, as I said in the beginning, nested Divs, without anything to modify that, that I could see. ( Firebug agreed. )
I do like inline-block and use it a lot, but this code that I inherited didn't use that.
> and whether you're using a browser that has serious layout bugs like IE6 or IE7 (see <http://www.positioniseverything.net/explorer.html> for examples.)
IE7 and IE8 were my primary targets for these clients, although some of us use Firefox and Chrome, too.
Moving the Position attribute down one level ( deeper into the nesting ), seemed to solve the situation.
More information about the TriLUG