Give help. Get help.

  • # March 9, 2012 at 6:51 pm

    Well, it’s safe to say that I am stumped here. Note how the page renders very differently in regards to the fixed div in Chrome and Firefox. Firefox (and Opera, for that matter) are displaying expected behaviour. Why is Chrome giving me trouble?

    Any help would be greatly appreciated!

    # March 9, 2012 at 7:19 pm

    thats very weird, Looks like a bug in webkit
    Is this right?

    # March 9, 2012 at 7:20 pm

    Oh nevermind, that works in chrome but broke it in firefox

    # March 9, 2012 at 7:21 pm

    Think I got it now

    # March 9, 2012 at 7:39 pm

    Ah! Interesting choice of using the margin. I still think that’s not really solving it, but it’s a smart one! I actually went a different route:

    The code might not be complete, but you should get the idea!

    # March 9, 2012 at 7:46 pm

    I guess because you don’t define a left position for #sidebar, you leave it open for interpretation. Seems like Webkit defines the left position the same as the original location of it’s parent #sidebar-wrap (and not follow the new position that is controlled by it’s relative move), whereas Mozilla “follows” the location of its parent.

    @karlpcrowley ‘s solution works because it takes the position:relative out of the equation and that’s where both browser types disagree.

    I think :)

    # March 11, 2012 at 10:57 pm

    Hey Andy, the example provided was a super simplified version just to show the browser differences. The actual site is a little more complex and requires a small set of icons to always be visible.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.