Hi guys,
I'm currently working on a new site for a client but I've noticed some issues with different browsers (as we do)
The site is http://www.neilcawse...testarea/peter/
IE6(windows) - needs work, IE6 is a nightmare.
IE7(windows) - issue with breadcrumbs and form.
IE8(windows) - PERFECT.
IE9(windows) - PERFECT.
Chrome 13(windows) - right aligned breadcrumbs and half sized top nav bar.
Chrome 14(windows) - right aligned breadcrumbs and half sized top nav bar.
Firefox5(OS X) - PERFECT.
Firefox5(Windows) - PERFECT.
Firefox7(OS x) - PERFECT
Firefox7(windows) - PERFECT
Safari 5.1 (OS X) - right aligned breadcrumbs and half sized top nav bar.
I'm thinking the breadcrumbs are falling victim to the double margin?
I'm a bit stumped at the mo with the half nav main menu...
any help would be appreciated...
many thanks in advance!
Page 1 of 1
Browser issues...
#2
Posted 03 February 2012 - 07:34 AM
Are you going to bother with ie6? I wouldn't. Check the browser stats of the current site (if there is one) and see if it's worth while.
Regarding the menu. It's obviously something web kit dislikes and I find that web kit is usually the better at rendering code. Have you cleared the float on the menu?
Regarding the menu. It's obviously something web kit dislikes and I find that web kit is usually the better at rendering code. Have you cleared the float on the menu?
#4
Posted 03 February 2012 - 02:21 PM
MikeChipshop, on 03 February 2012 - 07:34 AM, said:
Are you going to bother with ie6? I wouldn't. Check the browser stats of the current site (if there is one) and see if it's worth while.
Regarding the menu. It's obviously something web kit dislikes and I find that web kit is usually the better at rendering code. Have you cleared the float on the menu?
Regarding the menu. It's obviously something web kit dislikes and I find that web kit is usually the better at rendering code. Have you cleared the float on the menu?
I've added clear:both , and a float:left to the navr, its seems to have fixed the issue in chrome 13+14,
might have an issue with Safari 5.1 (OS X) - but I'll look into that now, thanks for the help
Share this topic:
Page 1 of 1
Help















