Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!
When including the Mint JS file in the head, IE6 errors with Operation Aborted. Is it okay to put the include at the end < body > instead, it seems to solve the IE problem.. (this is where I had my Google Analytics include).
Is there any better way to solve this?
same here.
Does not affect, ie7, opera or firefox. But it is a MAJOR issue on ie6. Please fix.
Regards, Pierce
Do you receive this error on shauninman.com or haveamint.com in IE 6? I cannot reproduce this error on my sites or either of yours. Also what OS version are you seeing this on?
I just had this problem as well. It only seems to happen on IE6 sp 2, unfortunately I have updated all my windows machines to IE 7.
This bug caused MAJOR problems for me last week.
Nope, sorry, can’t reproduce it on your sites for some reason. It’s IE6 SP2 under Windows XP (running under VMWare). Also tried on a secondary computer with IE6 SP2, where your sites also worked allright. Maybe a combination of either: 1) other javascripts together with Mint and IE 2) or the fact that I run Mint on a subdomain?
I’ve moved the loading of Mint on my site to the end of the body now, which seems to work fine, or would there be any side effects? The IE error has to do something about the JS modifying the DOM before the page is completely loaded, there’s a lot of information floating around, but I haven’t had the need to look into the issue more deeply.
Anything more I can do?
Are you certain that you place the Mint JavaScript include inside the <head> tag (and not before)?
Mine was definitely placed within the head tag.
It was listed right alongside my prototype link, and a link to my own js doc.
If you (and anyone else experiencing this problem) can post a sample page that results in the error and post (or email me) a link, I will take a look.
Ok, minioffroad.se is showing the problem now, please let me know as soon as possible so I can move the include back down again..
i cannot, as its a high traffic forum and would kill about 80 members.
It only happened after i updated to the latest mint/secreat crush/default.
Regards, Pierce
Guys, a sample page will do just fine, no need to reenable it on your public site. Copy the generated HTML from a single page that exhibited the problem and add the Mint JavaScript include (or reposition if you found the problem went away after moving it to the body). Save it in the same directory as the original you copied the generated source from from. Nobody has to be able to see it but me.
ive put it on the blog, which isnt busy at all here: http://blog.minimins.com
Pierce
Does that page exhibit the error in your IE 6 Pierce? It loads fine in my copy.
i dont have ie6. But the people on the main forum said they were getting the error which co-insided with the update of mint, and stopped as soon as i removed mint.
I have put up a post asking for a screenshot if anybody gets it from the blog.
I will say though on that forum, im unable to place the code before the due to template restrictions. However the old version worked flawlessly.
I have now placed it before the title.
Pierce
Placing it before the title tag is not an option. That will prevent Mint from being able to access the page name (you will start seeing urls in Mint if you leave it before the title tag).
thats not an issue for me as the urls are SEO, so the title is in the url.
Pierce
Again, having a sample page, the HTML exactly as it was of a page that was known to exhibit the problem, is the only way I can attempt to diagnose the problem. If we can’t reproduce the problem, there is nothing for me to diagnose.
With Pierce’s sample I’ve been able to narrow it down to the presence of a <base> tag in the header. I will continue looking into this tomorrow but in the meantime removing the <base> tag or moving the Mint script tag anywhere inside the <body> tag appears to eliminate the problem.
Update: as does closing the <base> tag with <!--[if IE]></base><![endif]--> (this appears to be required even if the <base> tag is self-closing, eg. <base ... />)
Confirmed fix, great find Shaun! Maybe we could use “LTE IE7” or whatever the syntax is?
For those running Joomla!, you need to modify includes/frontend.php at line 207 (J! 1.0.12).
I’m working on a fix in the JavaScript itself (using conditional comments) to check if there are any <base> tags present. If so (and only in IE), Mint waits until the browser has started parsing the<body> tag before touching the <head> tag. I think IE always treats the <base> tag as an open tag. When it gets to the closing </head> tag it realizes that the <base> tag was left open and closes it, fixing the incorrect nesting and allowing manipulation of the DOM. (That’s just my best guess at what is actually happening under the browser’s hood—don’t take my word on it.)
Also, it turns out that simply moving the <base> tag below the Mint JavaScript include eliminates the problem as well.
have you got a roadmap as to when an update that fixes this will be released?
Thanks, Pierce
It will be available in the next update.
This is a big problem for me as well, I cannot use this software until that bug is fixed.
You must be logged in to reply. Login above or create an account
