Hello, if I see my site www.scuoleinsieme.net with firefox, chrome, opera it's all ok.

If I use IE 9.0 it's all ok.

But with IE 8.0 or less after some click on menu, link or other the browser stop working and in the nav bar appear :


I've tryed also to change theme and make the same clik on IE 8.0 and all is ok :(.

Do you have any idea ?

#6 28-10-2011 23-15-51.png171.9 KBnamberone
Members fund testing for the Drupal project. Drupal Association Learn more


Jeff Burnz’s picture

I searched and I think its a conflict with an IE Toolbar, maybe conflicting with Superfish if you are using it, or some other plugin?


namberone’s picture

Thanks but I can not tell all the visitors to perform the steps on their computer to see my site.
I think it's a problem of this theme, because if I change the theme the site see it well.

Jeff Burnz’s picture

Status: Active » Closed (cannot reproduce)

Well 9000 other users don't have this problem which tells me its your computer, as does the MS help page.

namberone’s picture

Good analisys ;)

Jeff Burnz’s picture

Yeah, but honestly I can't debug it because I can't reproduce it, that's the problem - I am always testing in IE7/8/9 etc and I can't make this problem occur.

namberone’s picture

171.9 KB

If you use IETester with the DEMO SITE of your theme, this is the results for the varios IE versions.

With IE 8.0 don't work. (see attach)

So I think that the problem is not only mine.


Jeff Burnz’s picture

I can run this in IE Tester and IE8 for real in XP Mode - IE Tester uses an ancient beta version and crashes insistently regardless of what site I load in it so generally don't use it much because its so unstable on Win 64bit systems.

That is a scripting error - the theme (Adaptivetheme core) only loads two scripts - the html5shiv from Google code and respond.js, now if either of those had a problem in IE8 it would be fixed in a jiffy, since the developers of both those scripts are very active and they are specifically designed to work in IE8 or lower.

There are a couple of others, a theme override of cores vertical tags js, which only changes a class name, and Superfish, and the core JS - jQuery and a jQueryUI script. The problem is in all that somewhere, but untangling that requires me to be able to generate the error, but I can't.

I am running my tests on Win 7 Ultimate, with XP Mode, which is about as close I can get to running IE8 on XP itself without running a virtual machine with XP or dragging out some dusty old box.

What you are not looking at is IE Tester - I have found this to be buggy as hell, maybe the bug is there?

namberone’s picture

hello, I do not understand your question.
however, to solve my problem, I decided to change the theme of the site.
Thanks anyway for your answers.

Jeff Burnz’s picture

Title: Background image on body causes respond.js to crash IE8 » Crash with Microsoft Explorer 8.0
Component: Code » User interface
Priority: Critical » Normal
Status: Needs review » Closed (cannot reproduce)


ar-jan’s picture

Title: Crash with Microsoft Explorer 8.0 » Pixture reloaded crashes IE8: res://ieframe.dll/acr_error.htm
Component: User interface » Code
Status: Closed (cannot reproduce) » Active

I hit this problem too, and I hope to find out what's causing it. I noticed it after updating from AdaptiveTheme and Pixture 1.x to 2.x series.

In addition to the link in #1, here's some more threads on the problem: answers.microsoft.com, stackoverflow.

From reading these and other threads, a lot of different possible causes and solutions are suggested, and most 'solutions' I've seen so far focus on changing something about IE8 / Windows updates / the registry, but it seems to me something about the website (scripts?) must be wrong, or at least triggering this error.
I've completely removed and re-installed IE8, and I thought this did the trick, but in fact the site was only loading because I'd enabled compatibility view during installation. Without compatibility view, it's still not working. I'm not using any plugins. Flash and Java are at the latest versions. I've also tried all the suggested changes to IE security settings that I've seen in various threads, without result.

There are no errors showing up in the Event Viewer log for Explorer. Enabling script debugging (under Advanced tab) does not make a difference, no script errors show up.

When I set AdaptiveTheme Core (2.1) as default theme, the site loads fine.

Any ideas how to narrow this down?

--- Some extra info: ---

  • I'm running IE8 on Windows XP Pro, latest updates, no IE plugins.
  • IE says: "We were unable to return you to domainname.com", with the url: res://ieframe.dll/acr_error.htm#domainname.com,http:www.domainname.com.
  • Sometimes, after clearing all IE caches and settings, the site loads ok one time, then displays the same error again. I haven't been able to determine under what conditions the site does load this one time, it's not exactly reproducable.
iPenguin’s picture

Just wanted to chime in and say I'm having the same problem. IE 8 on win XP crashes, but not IE 8 on Win7. I narrowed it down by turning off modules one at a time. It only started working when I switched themes. (Both OSes are in virtual machines.)

If there is anything I can do to help please let me know as I really like this theme and want to be able to use it.

Edited: If you're willing to help I'm willing to dig into the code.


manyacs47’s picture

Assigned: Unassigned » manyacs47

I just upgraded to Drupal 7 and followed directions to be able to use Pixture Reloaded, an absolutely beautiful theme, made even better in appearance and functionality

However, running IE8 or Firefox and Windows Vista gave me the same crash issue and the same messages.

All other themes working, but would love to use the Pixture Reloaded

Jeff Burnz’s picture

Assigned: manyacs47 » Unassigned
Status: Active » Needs review

OK, I did some more reading on this, tonnes of it, and I am 99% sure this is respond.js crashing the browser because this theme uses a background image on the body, either I can move that to a child element or try putting it on the html element.

Could someone try this please - open up the colors.css file for PR and the very first entry is for body, change that to html selector so it looks like this:

html {
  color: #555555;
  background: #fdeaf7 url("../images/bg-wall.png") repeat-x left top;

This might fix the issue, it has for others with issues of IE8 crashing. An alternative is to move respond.js to the footer, which requires an update to Adaptivetheme core, which I would rather avoid if possible - but I do have patch ready that does it.

iPenguin’s picture

Hi Jeff,

I tried changing the css file as suggested. No luck. I flushed the cache and switched themes back and forth. I even commented out the html block in the css file. :(

If you want me to try the patch I'd be happy to do so.


ar-jan’s picture

Confirming #14 - the change didn't work.

Jeff Burnz’s picture

Are you guys saving the theme settings to re-write the color files? Its one thing to change the colors.css file, but thats not the file Drupal uses, it has to be re-written by the color module and saved to the files directory etc - that is the file that Drupal uses.

ar-jan’s picture

Should have thought of that - this fixes it! ;)

Thanks for troubleshooting this!

iPenguin’s picture

Oops, yeah, it does work. Sorry for the confusion.


Jeff Burnz’s picture

OK, thats GREAT news, I'll wait a little bit before I push something up to the dev version (some days probably, see if we can get some more feedback), but this is the fix I will most likely go with for now. I'll keep investigating loading respond.js in the footer as a more robust fix (since a lot of other themes could run into this issue), and if that looks like a good fix I'll need to release a new version of Adaptivetheme core as that is a serious wtf.

Jeff Burnz’s picture

Priority: Normal » Critical

Now we know this is certainly a theme issue I am marking this as critical, if I get no feedback in the next day or so I will commit this and release a new version. Cheers.

Jeff Burnz’s picture

Title: Pixture reloaded crashes IE8: res://ieframe.dll/acr_error.htm » Background image on body causes respond.js to crash IE8

BTW, this is the main thread that gave me answers, this could also have something to do with PIE, if anyone is using that as well.


Jeff Burnz’s picture

Title: Crash with Microsoft Explorer 8.0 » Background image on body causes respond.js to crash IE8
Component: User interface » Code
Priority: Normal » Critical
Status: Closed (cannot reproduce) » Fixed

I've committed two fixes for this:

1 - moved the body background image to the html element (for Pixture Reloaded)
2 - loading respond.js in the footer (for Adaptivetheme base)

Both are now in the DEV versions. I will keep tracking this issue and testing with respond.js in the footer, and hopefully will get some feedback, also I will open a new issue for it specifically.

twelch’s picture

Hi, don't know how relevant it is to this problem but I broke the cardinal rule of changing more than 1 thing at a time. I was experiencing the IE8 issue that others in this thread were.

I was implementing the change outlined in item #13 above and then when also going to look into the responder.js fix outlined in item 22 I noticed that I had two instances of adaptive theme, one nested inside the other. So an adaptive theme directory inside of the adaptive theme directory. Each adaptive theme directory had a set of the usually sub directories.

This would have occurred when I let drupal update to the 7.x-2.1 update from the update interface.

So, I disabled the theme and its dependants and did a clean manual reinstall on my dev installation. This fixed the ie8 errors, but I wasn't sure if it was from the fix in #13 or the theme reinstall.

So, I also did the disable/reinstall of the theme on my live server, but not the #13 fix, and it solved the problem there as well. So it is worth checking on IE8 errors whether the drupal update page has nested the theme installs.


ar-jan’s picture

I didn't have any nested themes in the themes folder, so that wouldn't explain the problem.
I do have a folder sites/all/themes/adaptivetheme/adaptivetheme, but that's because the project contains three themes in subfolders.

(If you installed the -dev version of adaptivetheme that would also explain why the problem was solved.)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

xbrianx’s picture

What does respond.js even do the only way to get it to work was to delete that file.

Jeff Burnz’s picture

xbrianx - what it does is enable media queries to work in IE8 and below. This is crucial in a theme like this to get the responsive layout and styles working. However its rather complicated and its taken a long time to get to the root of the problems (in respond.js I mean) and to figure out all the possible scenarios that might cause IE8 to crash, such as images on the body element. You have to understand that this responsive design concept is very young and pretty cutting edge, and to even get media queries to work in an ancient browser is no mean feat.

dimitriseng’s picture

Hi all, just to note that I had the same issue with AT 7.x-2.2 and PR 7.x-2.2. I have upgraded PR to the latest dev (28/02/2012) and everything now seems to be working correctly in IE8, thank you!

I would also like to mention that I had the issue mentioned in #23, when I upgraded AT from 7.x-2.1 to 7.x-2.2 using the Drupal UI. The "adaptivetheme" files where within "adaptivetheme/adaptivetheme/adaptivetheme/" directory, instead of "adaptivetheme/adaptivetheme". This is not related to this issue but I guess that this is an issue that could cause problems and possibly a new issue should be opened in the AT queue. I had to uninstall AT and install 7.x-2.2 again. Also note that doing this did not fix this issue, I had to upgrade to the latest PR dev version.

Jeff, thank you for all the great work you are doing on this!

earnie’s picture

AT 2.x-dev, PR 2.x-dev, no joy. IE-8 crashes and reloads unless "Compatibility Mode" is enabled. The site isn't in production yet so if the maintainers want to take a look, private message me for the details to how to view the site.

EDIT: After installing the -dev module you need to go and update your colors. Then the fix takes hold.

AdrianB’s picture

Just a related sidenote: Using AT 7.x-2.2 and Sky 7.x-2.3 and Footheme 7.x-2.0 I ran into this issue as well, I had manually added a background to body in my css file, and moving it to html instead and setting background to none on body solved the IE8 crashes.

criterion’s picture

Excuse me but I can't find the colors.css... to resolve this IE8 crash!
Does anyone to help me?
Tks !