I'm currently in the middle of creating a website for my company. The website displays perfectly in Firefox, IE and Chrome but in Safari is seems to display with borders around almost all the text and content and the website appears distorted. I've tried almost everything but can't put my finger on it. I've uploaded some screen shots of the website in Safari. Any ideas?? Cheers!
I've seen that behavior before, but I can't remember what it was that caused it... Typically it's either a unclosed tag, or something inheriting you didn't mean to have inherit. I'd have to see the HTML and CSS to weigh in more. No code, and it becomes a case of "and this is why we can't help you". Though if it's written anything like that train wreck in your signature "Well there's your problem" -- fixed width layout, px metric fonts, line breaks doing padding's job, endless pointeless div with endless pointless classes for nothing, inline level tags wrapping block level tags, static presentation inlined in the markup, tables for layout, nonsensical use of heading tags, presentational images in the markup, some of the most important text on the page (like company hours) delivered as a image instead of as text, incomplete media declarations on your CSS LINK's, pointless use of IE conditionals on a layout that is NOT complex enough to need them -- hardly surprising to see 40 validation errors meaning it's not HTML, it's gibberish... much less the 21.8k of markup to deliver 3.5k of plaintext and maybe three content images? That's at least twice and possibly as much as three time the HTML as should be present. Admittedly, that's what you get if you let anything in ASP make the markup for you... part of why I say I've never seen a well coded accessible site written using ASP. Much like WYSIWYGs it tricks you into thinking you can write a website. So if that new site you're working on is anything like that, well...
Firstly the website in my signature is nothing to do with me, it was built years before I arrived. Secondly I have never been a fan of ASP.net and neither is anybody on my team although our 'head of technology' insists that we use it for some unknown reason. Thirdly I've looked at a lot of posts regarding the problem and apparently it's a bug in the version of Safari which I was using. On version 6 and anything below 5.1.7 the problem doesn't arise (I've checked this) So thank you for your sarcastic, unhelpful comments.....but everything is sorted!
Well, it's hard to give helpful comments without seeing the CODE... and if it doesn't work in "latest" it's not sorted, unless you rejiggered it to not do that... which IMHO usually means you did something wrong in the code. If you had provided the code generating that bug, I wouldn't have resorted to going off making wild educated guesses. SHARING what the bug was, and it's fix, could also be helpful to other users. But as I've determined, some people don't actually want help, they want a pat on the back saying "everything's fine".