#9627 closed bug (wontfix)
Adding Object.toString causes $(handler) not to run handler
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | support | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Adding Object.toString causes $(handler) not to run handler
Commenting this out removes issue Object.prototype.toString = function() { };
Here's the jQuery Without this, ie5 throws exception Might be nice to do this on jQuery load failure? try { $() } catch(e) { $ = false } alert(true) not run if($) $(function() { alert(true) })
Change History (6)
comment:1 Changed 12 years ago by
comment:2 follow-up: 3 Changed 12 years ago by
Component: | unfiled → support |
---|---|
Priority: | undecided → low |
Resolution: | → wontfix |
Status: | new → closed |
jQuery's current browser support is as follows:
- Chrome Current - 1
- Safari 3+
- Firefox 3.6.x, 4.0.x, 5.0.x
- IE 6,7,8,9
- Opera Current - 1
comment:3 Changed 12 years ago by
Sorry, maybe I wasn't clear
Object.prototype.toString = function() { }
Causes complete failure of jQuery in Firefox 3.6.17. i.e. no jquery works.
The secondary, more minor issue, is that attempting to load jquery into ie5.5 throws an exception. I've got no problem with jquery not working here. It would just be nice not to get exceptions
comment:4 follow-up: 5 Changed 12 years ago by
Writing to or configuring of Object.prototype is generally considered a bad practice and outside of jQuery's scope.
comment:6 Changed 12 years ago by
Also still the same response as above.
Making changes to Object.prototype will cause unexpected behaviour across all UAs and jQuery is not responsible for that.
Above code didn't format well, let's try this: