Side navigation
#4460 closed bug (wontfix)
Opened March 31, 2009 02:04PM UTC
Closed May 09, 2009 04:26PM UTC
setting some css values generates a error in IE
Reported by: | ThomasCr | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | 1.4 |
Component: | core | Version: | 1.3.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
IE 7 generates me a error, when I try to set as example display=table.
The setup should be wrapped around a try statement.
I made a patch gains the current nightly build.
Attachments (3)
Change History (5)
Changed April 01, 2009 03:25AM UTC by comment:1
Changed April 01, 2009 07:38AM UTC by comment:2
why should i try to do this?
I need to set a value, and when a browser can not understand it, it should not stop the script.. its also possible to make a console log message in the catch block with key and value - when you need to debug it.
But jquery should not break the execution.
In this special case its fact: I want to set this on every browser who understand the css value display=table and when IE cannot handle it - it is ok with the default value for display.
Changed April 01, 2009 11:46PM UTC by comment:3
That patch would silently accept any invalid string, number, or object for a css value. Would you really want that?
Changed April 02, 2009 09:44AM UTC by comment:4
yes, shure. I think this patch in combination with a jQuery.log() in the catch block is a very good solution. like this...
try {style[ name ] = value;} catch(e) {jQuery.log('invalid style: ' + name + '=' + value);}
Changed May 09, 2009 04:26PM UTC by comment:5
resolution: | → wontfix |
---|---|
status: | new → closed |
There aren't any other places in jQuery that use
console.debugand this doesn't seem like the right place to start. I'll close this for now. There are other tickets and threads open that suggest a more complete "debugging" version of jQuery and it seems that something like this belongs there.
If jQuery traps and ignores the error, how would you diagnose the problem?