The last thread won't accept any more posts and I'm not getting replies to emails, so I'll try starting a continuation thread/ ...
Here are the emails:
6th Aug:
Hi Maria,
In response to your email:
'Hi David
Have you made any changes to your site as it appears to be working
fine now across IE8, IE9 and IE10?
Regards
Maria'
I've not done anything since our last communication. I've viewed the
site on my version of IE10 and it looks fine (as it always did), but
when I view it in the browser mode IE9, 8 or 7, it looks like the
screenshot I've attached. In fact I've attached a screenshot of a
page viewed in Chrome (which looks the same in IE10) and one viewed in
IE9. Screenshots taken just before 17.30 today.
I can see that this might be frustrating, but why should it look fine
when you view it and not fine when my client views it?
Best wishes,
David G
(I've also posted this on the forum)
2 attachments — Download all attachments View all images
Screenshot Chrome.png Screenshot Chrome.png
1384K View Download
Screenshot IE 9.png Screenshot IE 9.png
1169K View Download
__________________________________________________
6th Aug:
Hi David
Please find attached a screenshot how we are currently viewing your site with IE9. I have edited the doctype of your template to ensure quirks mode is not been activated in your clients browser
_________________________________________________
6th Aug:
Thank you Ciaran,
I'll speak to the client in the morning. Does this mean that I don't
need to put the warning code about old browsers into the Custom Code
area of the template, or is it still wise to do it for IE7?
By the way, the forum doesn't seem to want to go beyond two pages.
The last post I made isn't showing ... not that it matters, as long as
you are happy to communicate via email.
I'll let you know how I get on with the client.
With best wishes,
David G
____________________________________________________
7th Aug:
Hi Ciaran,
I've spoken to the client, who is using IE version 9 and I'm afraid
it's bad news! Nothing has improved!
She is happy to send you a screenshot or to talk to you on the phone
if that helps. At the moment she is being very cooperative, but I'm
aware that her goodwill will only last for so long.
I'm sorry to drop this on you and I can see that this must be very
frustrating, but this is a real situation and not the theoretical
scenario which is being presented by the IE browser modes.
Let me know what you need from me, if anything.
With best wishes,
David G
_________________________________________________________
7th Aug:
Hi David
It does make it nearly impossible to remedy when we are unable to replicate the issue. The only way we can duplicate the issues demonstrated in your screenshot is by viewing the site in an IE5 emulator in quirks mode.
IE usually enters quirks mode if there is an issue with the doctype on the page. One issue I notice in your page source is the following code appearing before the doctype, any code appearing before a doctype can enable quirks mode in IE.
<meta
name="google-site-verification"
content="raBL4D-Yhp0D_yJIBqluy_tyI98iPET4ZE_JUONgsXE" />
Have you any idea where this code may be coming from?
__________________________________________________________________
7th Aug:
Hi Ciaran,
Thank you for persevering with this one! I'm afraid, I'm afraid I
don't recognise the code. I'm not a programmer myself, so could it
have come from cut-and-pasting into the site? Is it more complicated
that simply deleting that code?
If it is resolvable simply by deleting the spurious code, perhaps you
could tell me where I need to look, so that I can keep this part of
the site clean in the future.
Best wishes,
David G
__________________________________________________________
8th Aug:
Hi Ciaran,
I wondered whether you've had any more thoughts on this?
regards,
David G
_______________________________________________________________
8th Aug:
Hi Ciaran,
I've found this post online which talks about this same issue. It's here:
http://stackoverflow.com/questions/6529728/html5-doctype-putting-ie9-into-quirks-mode
one of the contributers suggests this:
'Placing:
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
in the <head> tag should do it.'
Do you agree?
If this would work, are you able to make this change? You still have
access to the backend of the site and the FTP login details.