- This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- The forum ‘CSS’ is closed to new topics and replies.
The forums ran from 2008-2020 and are now closed and viewable here as an archive.
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!
thats very weird, Looks like a bug in webkit
Is this right? http://dabblet.com/gist/2009425
Oh nevermind, that works in chrome but broke it in firefox
Think I got it now
http://dabblet.com/gist/2009433
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:
http://dabblet.com/gist/2009473
The code might not be complete, but you should get the idea!
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 :)
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.