If you’re doing child themes you should be able to fix it using respond.js.
Edit: it looks like that’s being discussed here. Note the required placement of the script.
I looked at respond.js before, BUT it does not work locally in IE8, it must be on an online server to work. makes local testing difficult
Al
What a _wonderful_ introduction to WordPress…NOT! I guess I figured wrong that the latest theme would be the best place to start. I have only had a hosted system to learn on for a couple of weeks, but I had not seen this kind of an error.
Since I see the same incredibly bad menu behavior on all of the Windows 7 machines with IE9 that I have access to (several counting the VMs), in addition to the older machines/Vms with BOTH IE7 and IE8, so this is a failure to support Internet Explorer properly at all. With a menu that inludes many pages and child pages, IE displays my menu as a 25-item vertical list! That is simply not usable.
http://www.genealogydentontexas.org/
Yes it works fine in Safari and Firefox, which tripped me up since I was developing mostly on iMacs, but the vast majority of the genealogists my web site will serve use Windows XP through 7 and don’t install third party browsers. I need some sort of a hack to fix this, or I not only need to dump the theme (which I have been waiting for since nothing else I looked at seemed to fit my needs), but maybe WordPress as well.
Somebody please help me out here – someone who has actually fixed this bug successfully. We cannot go live with the site behaving like this! I have pulled the plug on enterprise application deployments over less severe problems than this.
End Rant – sorry – been awake for several nights doing this after 3 days of ITIL certification training – not a healthy combination.
@shapeshifter 3
You page don’t even list the correct list of current browsers! You have got IE10 as current while in fact it is not!
I am talking about this page: http://toolbox-4-websites.com/browser-updates/current-browsers
When will you be updating it?
A Trac ticket was created this morning covering this very issue: http://core.trac.wordpress.org/ticket/22044.
And this patch enqueues Respond.js for IE8 if you want it now: http://core.trac.wordpress.org/attachment/ticket/22044/22044.2.patch
“… the default theme isn’t trying to be an end-all-be-all theme. It won’t please everyone.” from @lancewillett’s post on the themes make blog, Why Default Themes Change Each Year. I encourage you to read it.
playing2012,
I forgot to mention that I am running the Windows 8 Release Preview: Build 8400 on my laptop. Internet Explorer 10 is the default browser in that version. If you are running an older version of Windows, you will get an older, compatible version of Internet Explorer when you click on my link. When I click on it, access to IE 10 shows up. Microsoft tailors the IE down link depending upon which version of Windows each person is using.
I just tried to list the most recent “Stable” version of each browser. Google Chrome has 4 separate versions: Stable, Beta, Developer, and Canary. I think Firefox has 3 versions, and Opera only 2. I sometimes make the assumption that others have the same interest in browsers that I do. Evidently, I’m wrong.
You know, if anyone would take the time to look at how much effort the Core Developers went through to produce this theme, you would be impressed. I admire them for what they have accomplished. Don’t kick a gift-horse in the mouth. If you don’t like the theme: choose another.
Windows XP is over a decade old, and Microsoft has always supported backwards compatibility to retain their corporate and governmental clients. At the same time, they have received loud condemnation from those that wanted them to keep up with the most modern market advances.
Do you want the WordPress Core Developers to always look behind them waiting for their customers to catch up, OR would you prefer that they constantly look towards the future.
I prefer the second choice.
I had a very humbling experience regarding “moving forward”. Three years ago, I was hired by a nonprofit organization that provides at risk youth a supportive environment to get their GED and learn employment skills.
I redesigned their website and decided not to even worry about coding for IE6. Then after the site had been up for a month, I checked the site’s Google Analytics stats and found the 50% of the users were accessing the site from IE6. I realized then that many of their students and potential students didn’t have access to the latest and the greatest technology. Of course, I promptly added IE6 support to the site.
We can always choose another theme, but this is the new theme that will appear with a new WP installation with the next upgrade. So it is more than a gift theme. It represents the face of WP and best practices in coding. Best practices in my opinion, shouldn’t leave such a great percent of users behind.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
I hope this theme will push forward technology, force old-fashioned users to keep-up with the evolving web and provide empathy for developers who are still developing for old browsers.
I’m afraid that any application that is released today that does not support today’s technology (that would be IE9) is a mistake. Usually I have these discussions with people pushing out apps that ONLY work in IE9 and leave Safari and Firefox out to dry. I understand dropping support for outdated browsers, but IE9 is NOT outdated, and cannot be treated as such.
The acid test is that the Twenty Twelve menus do not work properly in IE9, therefore they must be considered defective – and that needs to be corrected – fast!
Twenty Twelve menus do not work properly in IE9
IE 9 shows the full menu for me in both Windows Vista and Windows 7. If it doesn’t for you, perhaps you have Compatibility View enabled.
IE is finicky and I’ve seen it using Compatibility Mode when it really shouldn’t be. I believe it’s possible to override that by adding the following line to the header, which tells IE to use its latest rendering engine.
<!-- [if IE]> <meta http-equiv="X-UA-Compatible" content="IE=Edge"/> <! [endif]-->
Oh yeah. Compatibility Mode will kill the menu too, won’t it? *sigh*
As I understand it, the meta tag has to go immediately after <head> and it shouldn’t be wrapped in a conditional, because… well, because it’s IE, so who really knows.
I have to point out that in the past, using the default theme was recommended as a troubleshooting tool to eliminate as many confusing variables as possible. As it stands, I would never consider using this theme in a troubleshooting situation.
1. Obviously nobody really tested Twenty Twelve on “real life pc-systems” at all. Only one week before 1.0 release I downloaded 0.9 and spotted clearly visible layout problems after a 5 minutes test in Firefox and Chrome, didn’t do any tests in IE, otherwise there would have been more bugs in tracker…
The IE disaster now confirms this assumption.
2. A responsive design should be written completely the other way round. Default look should be available without media queries, with maybe some conditionals for older browsers (which also can be added by third party). “Narrow” look should be done with media queries.
These two major problems make the really nice looking Twenty Twelve (props to the designer) in the current version unfortunately a total failure which will also give WordPress itself a bad name.
Many big companies are “lightyears” away from migration to Windows 7 and run mostly XP on their desktops, maybe even with IE7. My various stats have over 50% IE7/IE8. This is not a problem with Twenty Ten and Twenty Eleven (and the child themes which are based on them). But all these users are basically kicked out with current Twenty Twelve if it ships like this as default with next WordPress.
Having worked at for a couple of NHS Trusts before, I can also confirm that XP and IE 6/7(and at a push 8) are still very much in use; the NHS as a whole is certainly one of the largest employers in the UK.
And as a Windows XP user on an old computer, I get by on Chrome and Firefox but sadly can’t upgrade to beyond IE8.
I love the new Twenty Twelve theme and I am very glad that at least response.js can come to the rescue in this instance (not tried it yet myself but this is my understanding from this thread and Trac?) – this coming from someone who decided to skip past Twenty Eleven since Twenty Ten was my first love ;P
Having worked at for a couple of NHS Trusts before, I can also confirm that XP and IE 6/7(and at a push 8) are still very much in use; the NHS as a whole is certainly one of the largest employers in the UK.
This may be very true but a website creator has to be pragmatic and decide “Am I dealing with NHS or what is the chance that NHS staff would be interested in my website” If the answer is zilt then clearly he has to move on and cater for the customers who are likely to bring in some do$h.
People in South Korea are still using IE6 (about 86% last time I saw the IE6 count-down figures) but that does not mean I should continue supporting IE6 because I don’t have customers in South Korea.
IE8 is a different matter because XP is still being used widely and some companies are not willing to use Mozilla products because of its open architecture. They think hackers can exploit it easily though I can’t live without FF.
