School is a twelve-year jail sentence where bad habits are the only curriculum truly learned.
John Taylor Gatto
New forum topics
Recent comments
- found OpenCMS better than
19 weeks 4 days ago - For me it was citype not
19 weeks 5 days ago - I would rather not worry
20 weeks 1 day ago - Hi there ,
i have integrate
21 weeks 2 days ago - Works a treat. I recommend
22 weeks 6 days ago - Any updates on a Drupal 6
24 weeks 5 days ago - Are you people really that
25 weeks 19 hours ago - video display quality in
26 weeks 3 days ago - yes it's true. joomla is hard
26 weeks 3 days ago - About Twitter.
27 weeks 10 hours ago
It feels so good getting rid of that many long Javascript lines, sorry, ECMAscript, and playing with some jQuery and DOM. Well, at least until you meet with that browser which ignores so many web standards: Internet Explorer, unfortunately still used by a big bunch of naive users who don't know there are way better options out there.
This week I had to modify a lot of jQuery code to get it working with that horrible browser from Redmond. And the job is even harder without a tool like Firebug. Internet Explorer just spits a line number when there's an error, often without a file name, or just cryptic messages.
I refuse to install any other Microsoft application just to debug their errors, I prefer thinking, changing some code and seeing if line numbers change. It's a very old fashion way of debugging but it works.
One of the problems I found while working with Internet Explorer and jQuery involved using the html() method to change some element's content. I was able to solve this by modifying some parent() or even using remove() and then append() or after() (see jQuery docs). However, I haven't found any logic for most of these issues yet, in some cases html() worked but quite often Internet Explorer died showing a run time error.
Also, while designing a jQuery enabled calendar using an HTML table I realized that correctly using thead and tbody could make a difference. It's better to have a correctly structured table to avoid Internet Explorer complaining.
Making your web application run with Internet Explorer is not an impossible task but takes a good amount of time and can make you think about killing yourself while listening to a Steve Ballmer interview, yeah, that horrible.
I guess that many web developers, like myself, are already thinking on increasing their fees when some job requires dealing with Internet Explorer, not a bad idea, really.
Join the conversation
developer tools for IE
Hi,
For debugging under IE, you can use DebugBar (http://www.debugbar.com/) and Companion.JS (http://www.my-debugbar.com/wiki/CompanionJS/HomePage).
Those tool add some useful features to IE, similar to firebug (but not as good so far).
Hope this helps.
Regards.
JFR
A couple ideas
Hi Alexis,
For debugging in Internet Explorer, you might want to check out DebugBar. I just started using it, and it works pretty well. Also, Ajaxian recently reported that version 5 beta has some really nice new features that bring it a step closer to Firebug in terms of functionality.
On the topic of your jQuery problem, one possibility is that you're trying to inject invalid markup with .html(). I noticed this causing problems with a plugin I wrote. For example, inserting something like
<div>this is a divwith no closing div tag caused IE to churn. The actual html was more complex than that, but the point is that it was an incomplete DOM of sorts. Anyway, I hope this helps you a bit with your troubleshooting.Cheers.
Indeed
Indeed, IE6 is a ECMA killer. That's because it only implements like 70% at best of the standard DOM-processing functions, not to mention there are DOM elements still a stranger to IE6. IE7 does somewhat better though it's still a headache. (I'm not even going into CSS-rant)
And yeah, I'm already negotiating a stress bonus on projects involving JS apps and IE6. Kudos to the DebugBar team, it's a long way to Firebug, but it's a damn good step.
JQUERY AND IE HELP NEEDED
Hi,
i was wondering if anyone could help.
$(document).ready(function(){
$('#thumbnails2 a').click(function(){
$(this).children('img').effect("transfer", { to: "#bigimage" },500, function() {
$('#bigimage').attr('src', $(this).parent().attr('href'));
});
$('.ui-effects-transfer').css('background-image','url('+$(this).attr('href')+')');
return false;
});
});
this code works perfectly in mozilla and safari, however it doesn't work in ie. it redirects to a blank page with only the picture that was clicked on it..
Try to view the HTML as XML
... just for debugging i wrote the ajax HTML into a text file. I found that my mistake was a not close comment.
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
A comment was not closed. Error processing resource 'file:///C:/Daten/xml_reply_action_tilg.xml'. Line 10, Position 5
Yeah, you're right...
You're right. I have a lot of coding in jQuery. My firefox works fine. Opera and Safari are fun, too, with jQuery. I didn't realize that I have to check IE... and the disaster coming.. IE didn't recognize most of my jQuery!
Doh! I just say to my client, move to another browser better than IE :)
Thank you, thank you, thank
Thank you, thank you, thank you. I was using an id tag under table, worked in firefox fine, not in ie. Switched to using tbody instead, worked a treat. Again, thank you.
Don't you think its kinda
Don't you think its kinda stupid to not download a Microsoft tool to debug Internet Explorer yet be ok with downloading a Firefox extension to debug Firefox?
That's a good point. I think
That's a good point. I think you are right, if it's valid to download a Firefox only tool for debugging on Firefox then it should be ok to do the same with Internet Explorer.
Firebug is a free extension for Firefox, I'm not sure if that's always the case with debugging tools for Internet Explorer.
Uhh.. the two of you above my
Uhh.. the two of you above my comment are missing the point.
IE fails horribly at following standards. This isn't a debate about justifying Firebug as an extension. I'd prefer Opera or Chrome above anything mentioned in previous comments!
Point is, I'm google'ing how to fix a jQuery issue in IE, after having sorted out a CSS nightmare with IE failing to implement 90% of the CSS standard set of selectors.
Even IE 8 is trash, in this light. I was hoping more from MS with IE8. Even though it's still in beta, it's the incarnation of Dread.
Thanks for the blog post, by the way.
With hard to find bugs it's
With hard to find bugs it's also usefull
to check your code at http://www.jslint.com
It's a bit *nal, but it does help.
Sometimes a missing ; can make IE loose itself.
This is because IE is running
This is because IE is running the $(document).ready() before the rest of the page is actually rendered. If you move this function to the bottom of your page, it should be fine.
Thanks for the article.
Thanks for the article. Helped me realize that it wasn't my code, but IE being incompetent.
Man that tip rocks! Ive been
Man that tip rocks!
Ive been banging my head against loads of jQuery not working in IE. Ive moved my scripts to below the body tag and they all work perfectly. Go buy yourself a beer and pretend it's from me!
I hate IE, but I love your
I hate IE, but I love your funny comments about it :)
thanks matt! but there r
thanks matt! but there r still some problems like if we include some needed variables in ready.function, script says document_root is undefined!
For me it was citype not
For me it was citype not class that was reserverd in ie, and of course no explicit error message, i changed it to mycitype and that work now
thanks to all of you