On Mon, Mar 17, 2014 at 7:40 AM, John <j...@coffeeonmars.com> wrote: > > On 3/17/14 12:35 AM, MiB wrote: >> >> Absolute positioning is relative to the nearest Positioning context. That >> is the first parent — going inside out from the current element — that has a >> "position". > > > In my current page, the parent to the item that misbehaves in FF does have > position:relative > > Shouldn't this be enough information for all browsers to render the children > with position:absolute;top:x;right/left:x; correctly? > So, I don't get why FF is doing something different with that information > compared to the other browsers. > > Thank you, > > John >
One thing that may be happening is that you are spacing the icons with ems, which is tied to font sizing. The math involved with the spacing of the elements in #social is tight enough where browser font rendering differences may be playing a part. Spacing those elements with px (you can use px more safely here because they are imgs) may bring results that are more similar. This is just my gut feeling here. No science to back it up. HTH -- Tom Livingston | Senior Front-End Developer | Media Logic | ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
