AnonymousMarch 26, 2013 at 10:55 pm #7136
There are two updates running which clear the error flags in the status bar of IE8
The first is in loop.php regarding an incomplete
spanis supposed to be self closing if the second one was added it should be compatible with all browers
It’s in loop.php so best not to add to a child theme as it will avoid any theme updates?
The second one in web-fonts.php
This may need an
Again is it best not to add to a child theme as it will avoid any theme updates?
Is It worth considering these for inclusion in the next release?Mod
The future of the web is HTML5 and CSS3, so future updates will probably aim at making the theme compatible with current standards, rather than with browsers which are currently losing ground.
As of this point, IE is only 44% of web browser usage, and IE8 is only 40% of that, which make IE8 market share somewhere around 20%. Not miniscule, but not insignificant, either. Either way, Windows 8 and IE10 (which supports current standards better than its predecessors) gaining ground.Quote:It’s in loop.php so best not to add to a child theme as it will avoid any theme updates?
Since you are only adding a single item with regard to the first issue, I don’t see why you couldn’t add a loop.php to your child theme. You could simply rename the file temporarily with the next Graphene update to see if the issue still persists. If it does, you can copy the new loop.php over and make the same change. I believe this would also apply to the second issue, although I haven’t looked at that too closely because backwards compatibility is not something I lose sleep over.Mod
AnonymousMarch 27, 2013 at 9:35 am #37092
yes I realise that but at the moment anyone that has users with IE8 has to incorporate these two fixes in order for their site to be error free.
The first one about spans is particularly interesting. There are two spans there. the first has been completed, the second hasnt. OK in theory neither have to be completed if we’re using the latest spec (completing the span is optional) but IE8 gives an error on the second one as it isn’t complete.
Why not add the second span for consistency? ( and because it clears the error)
Obviously both spans could be removed for consistency but that would give 2 errors!Mod
AnonymousMarch 27, 2013 at 11:58 am #37094
I thought I’d covered that argument with why not remove both spans if they’re not necessary and give two errors!
One of the reasons for choosing graphene over other themes is that it does work with IE8 ( save for these two) and I think it has
If IE8in places to make it work.
In this case the version of the code would need to be something like
<span content=""> If IE8 Then </span>
so just typing
is leaner and shorter
and works with all browsers ( assuming the other /span works with all browsers)
Is it best practice to make it work?Mod
AnonymousMarch 27, 2013 at 1:07 pm #37096
It’s when the page displays for real
I’ve added the test site to my profile name
I’m working on the footer (so I can credit graphene) but weve discussed that issue separately
Even if nothing changes other sites with IE8 users can use the two opening reportsMod
Okay, I’m at work now, where I have IE8 installed.
I have just checked the test site you referenced (http://184.108.40.206/cleeveramblers.org.uk/) as well as the eight sites I run with WordPress in IE8 and have not seen this error in any of them. Since only three people have reported this issue (and people with IE issues usually make themselves heard), I am now wondering if this is less of an issue of IE8 compatibility and more of an issue related to that particular install of IE.
1) Have you examined your site on a different computer?
2) Have you examined your site from a different ISP?
In any event, this is not a theme bug.
AnonymousMarch 29, 2013 at 9:21 pm #37099
Thanks for looking but you wont see those errors on my site because I’ve already incorporated the above two fixes
They did exist before. That’s why I raised this to help anyone else 🙂
No need to quote my site
Agreed it’s only a theme bug if the theme claims to work with IE8
If anyone wants their Graphene site to work with IE8 and these errors are flagged this is the way to fix them
The site still runs even if the errors are flagged with the yellow triangle in the status bar
This forum shows the error flag in IE8 – but it looks as though it could be fixed in a similar way if necessary
Viewing 10 posts - 1 through 10 (of 14 total)
- You must be logged in to reply to this topic.